BMC Impact Solutions

Service Modeling and Publishing Guide

Supporting
BMC Impact Service Model Editor 7.3 BMC Impact Publishing Server 7.3

February 2009

www.bmc.com

Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada
Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000

Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000

© Copyright 2009 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. Oracle is a registered trademark of Oracle Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”

Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can
s s s s s s s s

read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers

Support by telephone or e-mail
In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC
Have the following information available so that Customer Support can begin working on your issue immediately:
s

product information — — — product name product version (release number) license number and password (trial or permanent)

s

operating system and environment information — — — — — machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level

s s s

sequence of events leading to the issue commands and options that you used messages received (and the time and date that you received them) — — — product error messages messages from the operating system, such as file system full messages from related software

iii

iv

BMC Impact Solutions Service Modeling and Publishing Guide

Contents
Chapter 1 Designing a service model 1 Service model design process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Defining business goals for the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Decomposing a business service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Defining the service catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Defining the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Defining a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Defining a new component class for a component type . . . . . . . . . . . . . . . . . . . . . . 8 Analyzing a component’s critical failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Determining a component’s relationship and dependencies . . . . . . . . . . . . . . . . . 10 Determining the organization of the modeled relationships . . . . . . . . . . . . . . . . . 10 Identifying a component’s critical events and their sources . . . . . . . . . . . . . . . . . . 11 Displaying business key performance indicators (KPIs) . . . . . . . . . . . . . . . . . . . . . 13 Service model design considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Determining cell topology for the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Component property updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Chapter 2 Understanding a service model 17 18 20 20 21 21 22 22 23 23 24 25 26 33 33 35 35 36 37 38 39 39
v

Sources of objects in a service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rules for service model data modification and deletion . . . . . . . . . . . . . . . . . . . . . Using the BMC Atrium CMDB as a source of service model data. . . . . . . . . . . . . Using BMC Performance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Direct Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Precedences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component classes and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component status and substatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component status computation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model component types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service consumers and providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status propagation in relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relationship states. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relationship control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic status mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bringing events from the resource into the cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents

Event alias associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service schedules example with exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3

40 42 43 43

Understanding a service model created in BMC Impact Service Model Editor 45 46 46 51 52 52 52 53 54 54 55 57

Role of the BMC Atrium CMDB in service modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . Service model and the Common Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sandboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model execution on cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-model and not-in-model component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Business Time Segments from BMC Remedy AR System . . . . . . . . . . . . . Chapter 4 Building a service model in BMC Impact Service Model Editor

Service model creation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Launching BMC Impact Service Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Working with service component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Creating service component instances in BMC Impact Service Model Editor . . . 60 Switching sandbox View modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Viewing properties for a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Editing component instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Performing actions on multiple objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Copying component instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Hiding a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Deleting a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Finding component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Defining relationships between component instances . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Creating a component relationship in BMC Impact Service Model Editor . . . . . 79 Assigning related component instances to cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Updating relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Deleting relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Associating events with a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Working with timeframes and service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Icons used in the service schedule and timeframes editors . . . . . . . . . . . . . . . . . . 92 Working with timeframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Working with service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Assigning components to service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Granting access to service model objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Granting permissions to individual service model objects . . . . . . . . . . . . . . . . . . . . . 100 Testing the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Testing component relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Testing event associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Promoting the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Contents vi

About the publishing process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before you promote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Submitting a promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying promotion status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with publication logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying and deleting service model data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organizing service component instances for monitoring . . . . . . . . . . . . . . . . . . . . . . Working with BMC Impact Service Model Editor Views . . . . . . . . . . . . . . . . . . . . . . Saving, opening, renaming, and deleting Views . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding visual cues in a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repositioning objects in a View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling what you see in a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exploring consumer and provider paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Refreshing the View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repositioning the dockable windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Showing topology views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting and importing service model data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting class definitions from the BMC Atrium CMDB to a cells . . . . . . . . . . . . . Chapter 5 Component and relationship status propagation

103 104 104 107 108 110 110 114 115 117 118 118 120 121 122 122 123 124 125 125 126 126 127 128 128 129 129 130 132 132 133 133 135 135 136 137 146 147 149 149 151 152 156 157 157 159
vii

About component and relationship status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How component status computation works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status computation functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status computation algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How status computation algorithms work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About status computation models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Anatomy of a status computation model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The internal status NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quorum algorithm examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relationship status propagation concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How status propagation works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status propagation models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default status propagation models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is a valid status propagation model? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important service components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Impacts priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determination of final priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How cost impact is calculated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How SLA impact is calculated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 6 Managing BMC Impact Service Model Editor

Setting BMC Impact Service Model Editor options . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the topology view in BMC Impact Service Model Editor . . . . . . . . . . . Adding new classes to the BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making your changes visible to applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new service model component class in the BMC Atrium CMDB . . .
Contents

. 168 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 ServiceModelSet attribute for components and management data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Publishing in automated or manual mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 ServiceModelSet attribute for impact relationships . . . . . . . . . . . . . . . . . . 180 High availability and BMC Impact Publishing Server . . . 181 Understanding classes and slots for BMC Impact Publishing Server events . . . . . . . . . . . . 215 About home cell and cell alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Publishing from a Direct Publish source. . . . . . . . . . . . . . . . . . . . 193 Publishing to a BEM cell . . . . . . . . . . 177 Viewing publication history . . . . . . . . . . . . . . . . . . . and cell alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Configuration . . . . . 200 Defining BMC Atrium CMDB classes for SIM . . . . . . 183 About SIM management data . . . . . . . . . . . . . . . . . . . 172 Scheduling a fetch to import HP OVO data. . . . . . . . . . . . . . . . . . . . . . 163 Chapter 7 Creating a service model by importing HP OVO data 167 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Example—creating SIM data in BMC Atrium CMDB from BAROC files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 About publish environments . . . . 178 Sharing a single log directory between two Publishing Servers . . . . . . . . . . . . . . . . . . . . . . . . . 181 Modifying the generation of events . . . . . . . . 204 Initializing the BMC Atrium CMDB with SIM data . . . . . . . . . home cell alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Viewing publication history details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Defining BMC Atrium CMDB attributes for SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Using BMC Impact Service Model Editor . . . . . . . . . . . . . . . . . . . . . . . 168 Installing the integration with HP OVO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 smeserver properties file and parameters. . . . . . . . . . . . . . . . . . . . . . . . 172 High-level data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Purging and deleting service model objects . . . . 191 Understanding publish environments . . . . . . . . . . 218 viii BMC Impact Solutions Service Modeling and Publishing Guide . . . . . . . 205 Initializing a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Examples of advanced environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 About home cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Specifying a port for Service Model Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Steps to import HP OVO data to create a service model . . . . . . . . . . . . . . . . . . . . . . . . . 168 Atrium and non-Atrium environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Creating advanced publish environments . . . . . . . . . . . . . . . . . . . . . . . 216 About class and slot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Monitoring BMC Impact Publishing Server with BMC Impact Manager events . . . . . . . . . . . . . . . . . . . . . . . . 194 Enabling AtriumCMDB Publish publishing . . .Associating a custom icon with a service model component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Importing HP OVO data to create a service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Publishing from the BMC Atrium CMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Enabling Direct Publish publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Documenting your extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Chapter 8 Managing BMC Impact Publishing Server 175 Working with publication logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . Examples—using cell aliases for Direct Publish publishing . . . . . . . . . Verifying that BMC Impact Publishing Server is running . . . . . . . 240 Setting the configuration for a specific CLI command . Using trace files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Understanding return codes for CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 psstat—Displaying status of BMC Impact Publishing Server . . . . . . . . . . . . . . . . . . 234 Configuration file and parameters for CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Notify ARDBC plug-in. . No publication after successful promotion . . . . Securing publish environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Impact Publishing Server service or daemon fails to start . . . . . . . .conf file and parameters . . . . . . . . . . 283 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Notify plug-in for AR server groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . .Creating an environment for component instances and relationships . . . . . . . . . . . . . . . 282 publish—Publishing a service model or viewing instances to be published . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing large service models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing failures and reattempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying home cell and cell aliases . . . 268 pscontrol—Sending a command to BMC Impact Publishing Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pserver. . . . . . . . . . . . . . . . Stopping BMC Impact Publishing Server when JMS is not running . . . . . . . . . . . Other BMC Impact Service Model Editor Troubleshooting Options . . . . . . . . . . 235 Changing the time-out values for all the CLI commands . . . . . . . . . . . . . . . . 241 Understanding common command options for CLIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 pinit—Initializing a cell with service model data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the BMC Impact Service Model Editor log. . . . BMC Impact Publishing Server . . . 249 penv—Managing publish environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 pshowlog—Obtaining the XML log in user-friendly format . . . . . . . . . . . . . 247 Summary of CLI commands for BMC Impact Publishing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 pposter—Sending service model objects to a cell . . . . . . . . . . . . . . . . . . . . . . 261 plog—Obtaining the XML log for a request . . . . . . Initializing a cell from a Direct Publish environment . . . . . . . . . . . 278 pserver—Starting the BMC Impact Publishing Server service . . . . . . . . . . . . . 247 pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Impact Publishing Server does not reply to requests. . . . . . . . . . . . . . . . . . . . . . . . Reconciliation jobs hang . . . . . . . . . . . . . . 285 Appendix A Troubleshooting 287 288 288 292 292 293 293 293 293 295 296 296 297 297 ix BMC Impact Service Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 9 BMC Impact Publishing Server CLIs 219 219 220 220 222 224 229 231 233 Configuring BMC Impact Publishing Server CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Return codes for pserver . . 241 Configuring trace for CLIs . . . . . . . . . . . . . . . . . . . . . . . . 265 plogdisplay—Converting the XML log for a request to text format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Using CLI commands . . . . . . .

. . . . . . . . . . . . 303 Automated publication after reconciling reconciliation failure . . . . . . . . . . . . . 326 BMC_STATUS_TO_SEVERITY data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 BMC_SIM_MATCH_TABLE data class . . . . . . . . 303 Avoiding duplicate CIs . . . . . . . . . . . . . . . . . . . . . . . . . . 324 BMC_TIME_FRAME_TO_SCHEDULE data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 SIM_CellInformation class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 BMC_SERVICE_SCHEDULE_CONFIG data class . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Service model event classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Service model component data classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 BMC_STATUS_COMPUTATION data class . . . . . . 327 BMC_PROMOTION_LOG class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 BMC_SLOT_FORMULAS data class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Limiting HP OVO fetcher trace file growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Root event class . . . . . . . . . . . . . . . . . 313 BMC_DOWNTIME_STATUS_CONFIG data class. . . . . . . . . . . . . . . . . . . . . . . 321 SIM data class descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Appendix B Default service model data classes 305 Service model data structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 BMC_TIME_SCHEDULE data class . . . . . . . . . . . 323 BMC_SIM_ALIAS data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Diagnosing publication failures. . . . . . . . . . . . . . . . . . 330 Impact event class . . . . . . . . . . . . . . . . . . . . . . 322 BMC_SEVERITY_TO_STATUS data class . . . . . . . . . . . . 327 SIM_CellAlias class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 BMC_STATUS_PROPAGATION data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 BMC Impact Service Model Integration with HP OVO . . . . . . 307 BMC_Impact data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Another publish request is ongoing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 SIM_TIME_FRAME class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 CORE_EVENT base class . . . . . . . . . . . 306 Service model data class files . . . . . 331 Index 333 x BMC Impact Solutions Service Modeling and Publishing Guide . . . . . . . 307 BMC_BaseElement data class. . . . . . . . . . . . . 319 BMC_PROPAGATION_MAP data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 History event class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 BMC_SELF_PRIORITY_MAPPING data class . . . . . 302 Using dynamic ports with the ARDBC Notify plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Service model data class overview . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . 162 Adapter cell group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 BMC_BaseElement definitions . . 279 pscontrol automated example . . . . 314 MC_SM_DATA definition . . . . . . . . . . . . . . . . . . 157 BMC_BaseElement default icon image . . . . . . . . . . . . . . . . . . . . . 314 Figures xi . . . . . . . . . . . . . . . .sms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 MC_SM_COMPONENT definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Find Component dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 pscontrol manual example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Impacts priority determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Propagation paths between root cause and important components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Parts of a simple alias formula . . . . . . . . . . . 76 Create Relationship dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Creating an alias association . . . . . . . . . . . . 148 Default value for com. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Schedules Editor section of Edit Component Properties dialog box . 169 pscontrol stop example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Worst SLA method of priority determination . . . . . . . . . . 2 Inserting KPI data into the business_slot with an action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 MC_SM_DATA definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Example of match attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Final priority determination . . . . . . . . . . . . . . . . . 314 MC_SM_RELATIONSHIP definition . . .topoviews parameter . . . 156 Graph definition format . . . . . . . . . . 93 Schedule Edit dialog box . . . . . . . . . . . . 280 BMC Impact Service Model Editor log . . . . . . . . . . . . 89 Timeframe Edit dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Self priority determination . . . . . . . . 14 Impact (status) propagation in relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Defining the events to be processed by the alias formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Drawing relationships . . . . . . . . . . . 157 Example of a graph definition . . . . . . . . 74 Using Conditional Find . . . . . . .sme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Cost priority method of priority determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .bmc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Updating KPI data with a rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Advanced Find dialog box . . . . . . . . . . 99 Changing access for an individual component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 CORE_DATA definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figures Example of a service model . . 310 BMC_Impact definition . . . . . . . . . . . . . 279 pscontrol automated -u example . . . . . . . . . . . .

. . . . . 326 BMC_SERVICE_SCHEDULE_CONFIG definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 BMC_PROPAGATION_MAP definition . . . . . . . . 323 BMC_SIM_MATCH_TABLE definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 BMC_SIM_ALIAS definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .CORE_DATA definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 BMC_SIM_DATA definition . . . . . . . 330 SMC_STATE_CHANGE definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 SIM_TIME_FRAME definition . . . . . . . . . . . 330 MC_SMC_EVENT definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Partial CORE_EVENT definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 SEVERITY_TO_STATUS definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 BMC_SLOT_FORMULAS definition . . . . . . . . . 321 BMC_SIM_DATA definition . . . . . . . . . . . . . . 315 BMC_DOWNTIME_STATUS_CONFIG definition . . . . . . . . . 325 BMC_TIME_FRAME_TO_SCHEDULE definition . . . . . . . . . . . . . 329 MC_SMC_ROOT definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 BMC_SIM_DATA definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 BMC_STATUS_TO_SEVERITY definition . . . . . . . . . . . . . 331 xii BMC Impact Solutions Service Modeling and Publishing Guide . . . . . . . . . . . . . . . . 324 BMC_TIME_SCHEDULE definition . . . 317 BMC_STATUS_COMPUTATION definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 BMC_STATUS_PROPAGATION definition . . . 318 BMC_SIM_DATA definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 BMC_SELF_PRIORITY_MAPPING definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . 26 Main relationship classes . . . . . . . . . . 163 Integration with HP OVO configuration files . . . . . . . . . . . . . . . 49 SIM-qualified attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Advantages and disadvantages of different object sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 View mode switch icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Schedule Edit field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Default user groups and rights for BMC Impact Service Model Editor . . . . 184 Tables xiii . . . . . . . . . . 127 What a function returns when using an available algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 SIM-qualified subclasses of BMC_System . . . . . . . . 19 Service component status definitions . . . . . . . . 5 BMC Impact Service Model Editor values for IT service Sales Logix . . . . . . . . . . 65 Default component properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Topics covered in this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Description of predefined status computation models . . . . . . . . . 88 Service schedule and timeframes editors icons . . . . . . 118 Understanding expansion handles . . 48 SIM-qualified subclasses of BMC_Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Severity level index . . . . .properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Definition of relational operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 smeserver. . . . . . . . . . . . . . . . . . . . . . . . 41 Global and Local timeframe differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 SIM-qualified subclasses of BMC_Collection . . . . . . . 129 How status propagation models work in relationships . . . . . 48 SIM-qualified subclass of BMC_SystemService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Service model component types . . . . . . . . 66 Description of additional search criteria . . . . . . . . . . . . . . . . . . . . . 48 SIM-qualified subclasses of BMC_SystemComponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 BMC Impact Publishing Server event generation . . . . . . . . . . . . . . . 92 Timeframe Edit field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Icons in Objects-to-be-Published pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Tables Example business service model spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 SIM-qualified subclasses of BMC_LogicalEntity . . . . . . . . . . . . . . . . . . . . . . . . 121 Status computation functions and computed component statuses . . . . . . . . . . . . . . . . . . . 9 Occurrence level index . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Common Event Model (CEM) slots . . . . . . . 117 Adjusting the graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 How service model objects get to a SIM cell . . . . . . . . . 115 Visual cues in a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 How an event alias association works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Description of conditional operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 pclassinfo options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Actions commands . . .conf file for initializing the BMC Atrium CMDB . . . . . . 242 BMC Impact Publishing Server CLI error exit codes . . . . . . . . . 281 psstat command options . . . . . . . . . . . . . . . 249 penv options . . . . . . . . . . . . 186 IPS_CONNECT slots . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 IPS_STOP slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .cfg file parameter descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Basic steps to create advanced test environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 pposter return codes . . . . . . 256 Valid parameters for a Direct Publish environment . . . . . . . . . . . . . . . . . . . 186 IPS_CONFIG slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 xiv BMC Impact Solutions Service Modeling and Publishing Guide . . . . . . . . . . . . . . . . . . . . . . . . . 187 IPS_IM_CONNECT slots . . . . . . . . . . .conf file . . . . . . . . . . . . . 307 Slots that define component instances . . . . . . . 319 Status propagation slots in alphabetical order . . . . . . . . . . . . . . 188 IPS_REQUEST slots . . . . . . . . . . . . . . . . 190 IPS_ERROR slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Valid parameters for a Direct Publish environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 publish command options . . . . . . . . . . 225 ar. . 280 pshowlog options . . . . . . . . . 203 Determination of ServiceModelSet value for an impact relationship . . . 206 InitEffectivelyMgmtData parameter values and results . . . . . . . . . . . . . . . . . . . . . . . . . . 191 IPS_ENV slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 plogdisplay options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 pserver. . . . . . . 243 pserver error exit codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 pclient. . . . . . . . . . . . . . . . . . . 310 BMC_Impact slot definitions in alphabetical order . . . . . . . . . . . . . . . . . . . . . . . . . 315 BMC_DOWNTIME_STATUS_CONFIG slot . . . . . . . 267 plogdisplay return codes . . . 208 Basic process of publishing from a Direct Publish source . . 258 pinit options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 IPS_CLASSINFO slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 ServiceModelSet attribute values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 BMC_STATUS_COMPUTATION slots in alphabetical order . . . . . . . . . . . . . 254 Valid parameters for a BMC Atrium CMDB publish environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .conf parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 BMC Impact Publishing Server CLI common command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 pposter options . . . . . . . . 204 Parameters in the pclient. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 plog options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 InitEffectivelyServiceModel parameter settings and results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IPS_START slots . . . . . . . . . . . 320 BMC_PROPAGATION_MAP slot definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 BMC Impact Publishing Server request failure messages . . . . . . . . . 298 Service management data class files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 pscontrol command options . . . . . . . . . . 246 BMC Impact Publishing Server CLI command descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 IPS_PUBLISH slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 pserver command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . and maintaining service models that enable you to manage your IT resources from the perspective of the business services that they provide. . . . . . . . . . . . . . . . 15 Chapter 1 Designing a service model 1 . . . . . . . . . . . . . . 4 Defining the service catalog . . . . . . . . . . . . . . . . . . developing. . . . . . . . . . . . . 6 Defining the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Determining the organization of the modeled relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Analyzing a component’s critical failures . . . . . . . . . . . . . . . . . . . . . 14 Determining cell topology for the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Decomposing a business service . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Defining a component instance . . . . . . . . . . . . . . . . . . . . 7 Defining a new component class for a component type . . This chapter covers the following topics: Service model design process. . . . . . . . . . . 14 Component property updates . . . . . . . . . . . . . . . . . 11 Service model design considerations . . . . . . . . . . . . . . . . . . . . . 10 Identifying a component’s critical events and their sources . . . . . . . . . . . . . . 8 Determining a component’s relationship and dependencies . . . . .Chapter 1 1 Designing a service model This book provides detailed information about designing. . . . . . . . . . . . . . . . . . . . . . . . . publishing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Defining business goals for the service model . . . . . . .

Figure 1 shows an example of a generic service model as it appears in BMC Impact Service Model Editor with business users. decompose it to identify all aspects of the service. achieving the organization’s business availability goals. and IT structure layers. and build a complete service model for that part of your enterprise. The lines between the component instances represent the provider/consumer relationships. Figure 1 Example of a service model business consumers service layer IT infrastructure 2 BMC Impact Solutions Service Modeling and Publishing Guide . its organization. The IT environment. services.Service model design process Service model design process The best service models are enterprise-specific. A cost-effective strategy when you begin the process of building a service model is to select one critical business process/service. and its operational constraints vary significantly among enterprises.

and long-term goals for service impact management for the enterprise. service catalog. These goals guide the design and development of deliverables for all service model development phases and define the amount of time and effort required for development and implementation. Some possible goals for service impact management are: Chapter 1 Designing a service model 3 . Defining business goals for the service model The most basic step involved in defining a service model is defining the specific business goals you hope to achieve with the model.Defining business goals for the service model The following factors determine how a service impact management solution should be designed and implemented: s s s s s the diversity of IT resources and how they are monitored the location of resources and how the management responsibilities for them are distributed within and among IT or information services (IS) groups the relative importance of various resources in the delivery of business services the need for change management the maintainability of the service model over time The service modeling process involves: s s s s s s s s identifying sources of event information gaining familiarity with the structure and content of events identifying core competencies within the organization identifying critical business processes identifying IT services and their components finding relationships and dependencies between IT services building the necessary database of information (asset inventory. conceptual information regarding service models and publishing. mid-term. see the BMC Impact Solutions Concepts Guide. the IT or IS group must engage the business managers in defining shortterm. To do so. and so on) building the service model TIP For basic.

ranging from applications and systems to hard disks and other hardware components. user groups. encompassing the IT components. show how the components are interconnected. and related hardware and software systems. such as services. It consists of a business-centric model in which business processes. business process managers. Each business process can contain several functional applications. and other business objects. business continuity and service availability—This type of implementation is driven from the top and ensures that IT or IS is delivering their services as agreed. and SLAs rely on a small number of vital IT components that measure the pulse of the underlying environment. Sources of information include business unit managers. identify the IT services that support them. each of which can have multiple IT components. 1 Identify business services. It consists of a thin layer of logical groups on top of a large number of IT resources. and the logical components. Services are just logical groupings that provide a convenient way of classifying the technical resources. 4 BMC Impact Solutions Service Modeling and Publishing Guide . a hardware manufacturing organization may identify a business function as microprocessor procurement. a supporting IT service as procurement information storage. a service model is a collection of components that represent a business service.Decomposing a business service s operational efficiency—This type of implementation is run by and for the IT or IS group. services. A business service can have one or more business processes. and staff personnel knowledgeable about the business services. On a high level. Company organization charts might be helpful in identifying the relevant people. A service model will contain the processes. and identify IT components and assets that provide the IT services. databases. It consists of a balanced representation of the operational environment. such as systems and applications. and the supporting IT assets as servers. and show how component failures propagate and impact the upstream services. s s Decomposing a business service The purpose of decomposing a business service is to identify and document business processes. business-focused operational efficiency—This type of implementation is likely to involve various populations and centers of management in the enterprise. The following steps facilitate the process of creating a service model. For example.

Table 1 Example business service model spreadsheet Business functions Marketing Business processes Market research Core competencies Plan and develop products IT services IT component Research product and planning development Manager customer relations Front office sales Customer support Response management Support service requests FTP Server: FTP Chapter 1 Designing a service model 5 . Map the business processes to the functional apps. help desk documents. to specific sub-business processes. 3 Build a business service model. functional applications—Identify the business applications that support the business processes. For each IT service. Examples of IT services include customer support and customer call monitoring.Decomposing a business service The process involves interviewing the managers and identifying the following information: s business processes—Identify key business processes such as Market Research. and purchase orders might be useful in identifying IT components and the business processes that they support. 2 Identify IT services. identify the IT assets that support the service. There can be multiple levels of business processes. The process involves identifying the list of IT assets (components). starting with higher level core competencies and business functions. and link the business processes to the IT services you have identified. Identify the interdependencies among the IT components and formulate a topology map. Map the functional applications to IT service components to create the business service models. s Product Planning. Disaster recovery plans. Interview the IT management and staff. Consider the relationships and dependencies between IT components. or utilize an asset/configuration management database as resources: s s s Create a list of IT services (service catalog). Response Management. discover what IT services are offered to business units through use of IT assets. or Case Management. Sources of information include IT managers and staff.

logical assets. For the Sales Logix IT service example shown in Table 1 on page 5.01 software Tech Support Analysts 6 BMC Impact Solutions Service Modeling and Publishing Guide . Table 2 Compon ent name BMC Impact Service Model Editor values for IT service Sales Logix Provider instances Consumer Status computati Relationsh that instances impact on model ip Policy depending on direct Tech Support Analysts Sales Logix v6. including values for the fields shown in Table 2.01 Sales Logix server bogart in standard increasing Sales Logix server in standard increasing Sales Sales Logix Logix DB v6. and physical assets that support business processes for a company. the detailed IT component information (except for Alias and Alias formula) that are required by BMC Impact Service Model Editor is shown in Table 2.Defining the service catalog Table 1 Example business service model spreadsheet Business functions Business processes Core competencies IT services Sprint Sales Logix IT component Server: Walrus Database: SALLOG Applications: Sales Logix User group: Tech Support dept Servers: Antelope Defining the service catalog A service catalog is a list of IT services.01 Support service requests Tech Support Analysts Compone nt type business process Component description Cell name bogart In/out model in Support Business service function is requests Customer support user Tech Techs communit Support supporting y Analysts service requests applicatio Sales n Logix v6.01 applicatio Sales n server Logix server bogart in standard direct Sales Logix bogart application. The service catalog should list all of the IT services with a summary of their characteristics. v 6.

This information should include: s s each resource’s name or component identification pattern its location or site You use this information later in the design phase and when creating service model components. To do this. Defining the service model involves establishing a list of all the IT resources that should be represented in the service model.Defining the service model Table 2 Compon ent name BMC Impact Service Model Editor values for IT service Sales Logix Provider instances Consumer Status computati Relationsh that instances impact on model ip Policy depending on standard direct SALLOG Sales Logix application Tech Support Analysts Sales Logix db software Tech Support Analysts Compone nt type database Component description Cell name bogart In/out model in Sales Logic Sales database Logix software v6. decomposed your business processes. you are ready to define the actual service model. The first step in developing a service model is to design its logical architecture. Chapter 1 Designing a service model 7 . each individual resource is represented by a component instance. you must analyze the IT environment to s s s identify the resources that make up the service model identify the event sources for the resources and their characteristics determine the functional relationships and dependencies between various resources that can affect services Defining a component instance In decomposing your business services. and created a service catalog. In the BMC service model.0 DB software SALLOG Sales Logix database server database server bogart in standard direct Defining the service model After you have decided on a business goal for service impact management. you have identified the basic building blocks of a service model—its assets or components.

performance. you must distribute the changes to all of the SIM BMC Impact Manager instances (cells) and recompile them. They are created and maintained in the BMC Atrium CMDB. To do so: s s s s identify the cause of failures and degraded performances for the service component categorize the failures into availability. The order in which you create related physical components is unimportant. capacity identify the effects of the failures assign a severity level to each failure Severity level values are listed in Table 3. Analyzing a component’s critical failures After service components and associated functions are identified. you need to monitor their status to analyze their effects and watch for failures. and such logical components as user groups. when you make a change to the SIM classes in the BMC Atrium CMDB. Component classes are displayed in BMC Impact Service Model Editor as templates from which you can create new component types. Classes may identify such physical components as servers or databases. or class. Defining a new component class for a component type Component instances represent an individual occurrence of a component type. 8 BMC Impact Solutions Service Modeling and Publishing Guide . Component instances are created through BMC Impact Service Model Editor.Defining a new component class for a component type Component instances are created as a single instance of a class type that is defined in the BMC Atrium CMDB. In order to maintain service model consistency. You can create an IT system component before or after an application component that runs on it.

network. problem on sending or receiving machine Effect of failure—remote recipients will not receive e-mail while MTA down Severity—significant Occurrence—slight Prevention—monitoring of the system. Table 4 high frequent moderate occasional slight remote Occurrence level index Definition high change of occurrence and needs immediate attention frequent change to happen and needs attention moderate change to consider prevention occasionally might happen slight chance to happen unlikely to happen Occurrence level Sample of failure modes effects and analysis s s s s s s s s s s Component—Message Transfer Agent (MTA) Function—routes and convert messages Point of failure—queue length size growing Issue type—performance Cause of failure—network connection failure.Analyzing a component’s critical failures Table 3 severe significant moderate minor slight minimal Severity level index Definition Permanently disabling critical end user dissatisfaction causes degradation of service causes inconvenience to end user caused annoyance for customer not noticeable by end user Severity level s assign a frequency or occurrence level to each failure Occurrence level index values are listed in Table 4. receiving MTA failure. and exchange services Detection—PATROL NT and Exchange parameters related to the issue Chapter 1 Designing a service model 9 .

for example. for example. within email service. The driving force behind this model is operational efficiency. so that only one IT service would exist for each business process. 10 BMC Impact Solutions Service Modeling and Publishing Guide . Define the resources that are providers and the resources that consume their services in the service delivery stream. web services and email services consider how the same IT components might support more than one service. The grouping of IT systems becomes the IT services. This type of implementation is run by and for the IT or IS group. s s s s s consider relationships and dependencies within the IT service. for example. Examine how the various resources combine to deliver a service on a particular host. ranging from applications and systems to hard disks and other hardware components. Services are just logical groupings that provide convenient way of classifying the technical resources. one server hosting multiple applications consider the dependencies of several business processes on the same service. the hardware component must be the provider and the system component the consumer. Identify the relationships and dependencies among the IT components and the logical components to one another. you identify the underlying dependencies and relationships within the IT Systems. If a system component is to be linked to a hardware component. or call support’s dependency on email consider dependencies on other services. You can organize your service model components using one of these basic organizational strategies: s The IT resource management strategy is to create a thin layer of logical groupings on top of a large number of IT resources.Determining a component’s relationship and dependencies Determining a component’s relationship and dependencies To understand the impact of different components and their status on a service. email used by all consider the relationship between IT services and business processes (the link called business service) Map business processes to each system. for example. Determining the organization of the modeled relationships How you organize service model components depends on the goals that your organization wants to attain through service impact management. The direction of the relationship is important.

and other business objects. Identifying a component’s critical events and their sources Even the most complete service model provides little value if there is not a consistent flow of events into the model to maintain the real-time status of its components. The business continuity and service availability strategy is to implement a business-centric model in which business processes and services rely on a small number of vital IT components to give a status overview of the underlying environment. This type of implementation is driven from the top. The driving force is operational efficiency. and the logical components. This type of implementation is likely to involve various populations and loci of management in the enterprise. The strategy that you choose also affects the amount of time and effort required for its development and implementation. s Although these strategies are only briefly outlined here. encompassing the IT components.Identifying a component’s critical events and their sources s The business-focused operational efficiency strategy is to create a balanced representation of the operational environment. To create the event associations for a component. such as systems and applications. ensuring that IT or IS is delivering their services as agreed. The driving force is business continuity and availability. but with a balanced business perspective. perform the following actions: 1 Analyze the event flow of each real IT resource or group of resources that are instrumented in the same way to identify: s events that provide no value to the service model Chapter 1 Designing a service model 11 . Assuming that there is enough event data consistently available to understand the state of IT resources. they are helpful in understanding that each implementation probably has a different focus. favoring some types of components and having more or less granularity in some branches of the component hierarchy. you must s s identify the event classes that will be associated with the component establish a naming convention for the logical ID (a key value) so that the same identification string can be derived from each event class to be associated with the component You perform event analysis to achieve these goals. Event associations provide the mechanism for a component’s real-time status to reflect the health of the actual resource that it represents. This strategy is similar to BMC Software’s BSM Strategy that is called a Business Service Impact Model. such as services. user groups.

such as an agent. 2 For each significant event. determine whether the event should be associated only with a component or whether it should also participate in the status computation. s Does the monitoring tool send alerts only when something goes wrong? If so. either by not sending them to a cell or by filtering them out when they reach the first cell. you may need to automate their closure through rules containing the appropriate cycle and conditions. s missing events or events that cannot be processed Some situations that you may want to include in your model are not traced by events in the real environment. 12 BMC Impact Solutions Service Modeling and Publishing Guide . such as UP/DOWN. 3 Consider how the monitoring tool. or the events produced cannot be associated with the IT resource. or through New rule updates before entering the service model This includes events that are best represented by a single higher-order event that represents their net effect or represented by event pairs. reports the state of the service’s IT resources. a cause event E1 is associated with the component C1. For example. While it may appear reasonable to elect E1 so that its severity value contributes to the status of C1. electing E2 may be of no use if a relationship propagates the impact of event E1 from component C1 to component C2. does it close the alerts automatically? If the monitoring tool does not close alerts automatically. events can be enriched using Refine and New rules — events that must be processed (using a Regulate rule) so that only the appropriate occurrences reach the service model — events that should be combined through abstraction.Identifying a component’s critical events and their sources Not all events received by a cell provide valuable information to the service model. s events that provide valuable information about the service environment and must be retained by the cell. or script. such as: — events that must be changed or adapted either at the source or in the event adapter that collects them to be usable by the model — events that must be enriched by the cell so that they contain the required information. and a consequence event E2 is associated with the component C2. Identify the events that are of no value and should be ignored. adapter. correlation.

you create a rule or a policy. at regular intervals? Does the monitoring tool handle component availability with some form of heartbeat? When does the IT component representing the resource transition from AVAILABLE to UNKNOWN or from AVAILABLE to UNAVAILABLE. you use the action sim_operations. after the event is associated to a component. To insert data into the business_data slot.set_business_data.business_class=$business_data. you use a rule to transfer the value and the unit to the component in the business_data slot in the MC_SM_COMPONENT class.’Service Operators . not affect event flow. When creating new event propagation paths. Chapter 1 Designing a service model 13 . (For a published CI. s s s Displaying business key performance indicators (KPIs) When an external source sends an event with a business metric to the cell. and back again? What is the reliability of the event flow? Even the most complete service model is of little value if a consistent flow of events into the model cannot be maintained.) Figure 2 shows an example of the action. you should take care to consider whether you can improve or.Senior’.mrl file). Figure 2 Inserting KPI data into the business_slot with an action action sim_operations.set_business_data: { [‘Service Administrators’. you cannot directly modify the business_data slot in BMC Impact Explorer. at least.Displaying business key performance indicators (KPIs) s Does the monitoring tool send status-type events. } END To update the business_data slot. such as ok or not ok. Figure 3 shows an example rule (in the mc_smc_associate.’Service Operators’] } [‘business_data’: STRING($business_data)] : MC_SM_COMPONENT ($A) { $A.

use distributed cells to collect and process the raw events of interest before they enter the model. Determining cell topology for the service model There are three basic approaches to cell topology: s s s centralized domain-based layered The centralized (default implementation) approach is to implement the service model on one cell. # uncomment the following if you want to drop these events # if ($EV.business_data = <an expression that builds kpi from $EV>.mc_smc_id != ‘’] using {MC_SM_COMPONENT ($COMP) where [$COMP. you can represent some resources in more than one cell. including information on cell topology. Lines of business and independently operated sites are good candidates for this approach.mc_smc_id]} triggers { $COMP. component property updates.mc_sm_impact = != 1) then # { # drop_new. # } } END Service model design considerations This section contains information to keep in mind when designing your service model. With this approach. Each part is run on a different cell. and component deletions. or possibly distributed among several cells if geography is a factor. The domain-based approach separates the service model into two or more parts that correspond to clearly established entities or domains in the organization. and users connect to the cells on which the components that they manage reside. with all the service management objects created and maintained in that cell. The layered approach separates the service model into two or more stratified management layers.mc_udid == $EV. provided that the event flow is directed or propagated correctly.Service model design considerations Figure 3 Updating KPI data with a rule new associate_kpi: <EVENT_CLASS_NAME ($EV) where [$EV. 14 BMC Impact Solutions Service Modeling and Publishing Guide . Each layer is contained in a different cell. Then. such as IT components and logical components.

and so forth. However. similarity of function. You can update these properties automatically only if the new values arrive in an event or are added in a data table. component 2 to cell B. network connectivity. and so forth. To determine related component instances This topic addresses the publication of different components of a service model to multiple cells: for example. as long as all the cells are registered with the BMC Impact Portal.Component property updates If you are assigning different components of the same service model across multiple cells. you might group instances based on geographic proximity. You must create a few simple rules to implement this mechanism. Component property updates The cell updates the status of a component as new events are received or when an impact from other components occurs. provider-to-consumer relation. other component properties that can change over time are not maintained by the cell. until all components of the service model have an assigned cell. For example. publishing component 1 to cell A. After you publish the service model. You can assign different component instances to different cells to distribute the processing load. first determine which components are related. or you can make the assignment based on the proximity of the cell to the instance it is monitoring. you can view the entire model from a single Impact Explorer console. You determine related component instances based on your interpretation of the service model. See “Assigning related component instances to cells” on page 83. Chapter 1 Designing a service model 15 . Then assign related components to appropriate cells until you assign all components of the service model.

Component property updates 16 BMC Impact Solutions Service Modeling and Publishing Guide .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic status mapping . . . . Rules for service model data modification and deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the BMC Atrium CMDB as a source of service model data. . Precedences . . . . . . . . . . . . . . . . . . . . . . . . . Relationship control . . . . Component status computation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service components . . . . . . . . Relationship states. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event alias associations. . . . . . . . . . . . . . . . . . . 18 20 20 21 21 22 22 23 23 24 25 26 33 33 35 35 36 37 38 39 40 Chapter 2 Understanding a service model 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using BMC Performance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 2 2 Understanding a service model A BMC impact service model is made up of s s s s s s data classes that describe the various types of physical and logical IT resources that make up an enterprise’s business corresponding data classes in the SIM KB of cells event classes associated with specific resources component instances that represent the unique physical and the logical configuration items that deliver business services impact relationships management data instances This chapter presents the following topics: Sources of objects in a service model . . . . . . . . Component relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component status and substatus . . . . . . . . . . Status propagation in relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service consumers and providers . . . . . . . . . . . . Component classes and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bringing events from the resource into the cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Direct Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model component types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event associations . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . you can mix different sources of data in a SIM cell. . . . . and then add special objects manually using a BAROC file. . . . . . . . . the service model objects in a single cell can originate from multiple sources. So. . . . . . . . . . . . . . . . . as described in Table 5. . . . . . . . . . . . . . . for example. . . . . . . . . . . . . .Sources of objects in a service model Service schedules . . . . . For example. . . . . . . It is also possible to track very dynamically occurring objects. . . . with MRL rules. . . . . . they are reconciled by the BMC Atrium CMDB Reconciliation Engine. . . . . . . . . . . . . . . . . . . . Sources for service model objects in a SIM cell are s s s s s BMC Atrium CMDB BMC Impact Explorer CLI commands pposter and mposter Master Rule Language (MRL) third-party repository The source of the service model data determines the method of delivery into the cell. . . . . . . . . . . Table 5 How service model objects get to a SIM cell How objects are delivered to a cell Delivery method name Atrium Publish Feed objects are discovered using discovery tools or you create them in the BMC Impact Service Model Editor component. . . . . 43 Sources of objects in a service model A service model can contain objects (components and relationships) from different sources. . . . Data that you send from any given environment must be updated and deleted in the context of that environment. . . In addition. . . . . 43 Service schedules example with exceptions. . . and then automatically published to the cell using BMC Impact Publishing Server you create a BAROC source file of object data and Direct Publish Feed send it to the cell using the CLI command pposter. . . . . . . . . . . . . . you may have the bulk of your service model objects come from the BMC Atrium CMDB. . . . . . . which publishes the data to the cell using BMC Impact Publishing Server you create a BAROC source file of object data and source Direct Feed send it to the cell using the CLI command mposter Source for service model objects BMC Atrium CMDB BAROC source file 18 BMC Impact Solutions Service Modeling and Publishing Guide . . . . . 42 Timeframes .

edit. when the objects are saved. they are sent directly to the cell you create a rule that adds objects to the cell on receipt of a trigger event you configure BMC Performance Manager to handle Direct Service Model integration Delivery method name source Direct Feed Source for service model objects BMC Impact Explorer MRL rule BMC Performance Manager tool direct feed source direct feed Table 6 describes some of the advantages and disadvantages of the different sources for service model data. or both in BMC Impact Explorer using the Edit => Create Component menu command. such as BMC Impact Service Model Editor GUI to create. and delete objects. and publish objects BAROC file with pposter CLI command s s s s s useful only for small. Table 6 Advantages and disadvantages of different object sources Advantages s s s Object source BMC Atrium CMDB Disadvantages s s s s handles large. relationships. so data is protected from uncontrolled edits user interface to create and edit components and relationships you can add data to complement other sources complex to implement time factor to discover or create. reconcile. complex service models accepts objects from discovery tools sophisticated features.Sources of objects in a service model Table 5 How service model objects get to a SIM cell How objects are delivered to a cell you create components. and dynamic prioritization data is protected from uncontrolled edits customizable permissions are available easy to set up a simple service model quickly managed by BMC Impact Publishing Server. simple models BAROC file must be created to exact standards requires knowledge of CLIs may not build complete model not as protected from uncontrolled edits no primary copy in external datastore BMC Impact Explorer s s s s s Chapter 2 Understanding a service model 19 .

In other words. If you first create a CI via a pposter and later publish that CI (same ComponentAlias) from BMC Atrium CMDB. then the DirectPublish CI is replaced by a AtriumCMDB CI. If you first create a CI from publish from BMC Atrium CMDB then try to modify it via pposter. Objects delivered to the SIM cell from BMC Atrium CMDB must be edited and deleted in BMC Impact Service Model Editor (or BMC Atrium CMDB) and objects from the CLI command pposter must be changed and deleted using a BAROC source file and pposter. or the mposter command. Published data is protected from modification or deletion by any form of Direct Feed. while published components are visible in BMC Impact Explorer. Using the BMC Atrium CMDB as a source of service model data When service model component and relationship data is stored in BMC Atrium CMDB. preventing cell processing performance degradation s Rules for service model data modification and deletion For published service model data. changes and deletions are restricted to the original source of the data. nor with a rule.Rules for service model data modification and deletion Table 6 MRL rule Advantages and disadvantages of different object sources Advantages s Object source Disadvantages s s s handles highly dynamic changes only practical for special circumstances may not build complete model no primary copy in external datastore Direct Publish Feed s validation of the service model is off-loaded from the cell. you cannot change or delete them in BMC Impact Explorer. you use these products from BMC Impact Solutions to create and manage service models: s s BMC Impact Service Model Editor BMC Impact Publishing Server 20 BMC Impact Solutions Service Modeling and Publishing Guide . this fails because the DirectPublish environment is not the source of the CI.

“Understanding a service model created in BMC Impact Service Model Editor” and Chapter 4. “Building a service model in BMC Impact Service Model Editor”. the CLI command mposter. Service model objects that originate from BMC Performance Manager may be missing relationships. For information about this. change this parameter setting to N (no). This is controlled in the mcell. or rule that sends service model data directly to the cell. Since Direct Feed is enabled by default. you publish service model data to the cells and manage publish environments. when a cell starts. Using Direct Feed A direct feed source of service model data is any application. Sending service model data to the cell from BMC Impact Explorer. Using BMC Performance Manager With both BMC Impact Portal and BMC Performance Manager installed. In BMC Impact Explorer. For more information about creating and editing service model components in BMC Impact Explorer. see BMC Impact Solutions Service Impact Management Guide.conf configuration file by the ServiceModelDirectFeed parameter. Your service model can come solely from BMC Atrium CMDB or you can add objects to it from other sources. executable. making the service model incomplete. and manage your service model environment In the BMC Impact Publishing Server. see Chapter 3. script. the service management data is loaded. Chapter 2 Understanding a service model 21 . For more information about creating service models using BMC Atrium CMDB. or MRL rules is enabled by default. you can send service model components from BMC Performance Manager directly to the cell. you can create an impact relationship between the two components. To disable Direct Feed. see BMC Performance Manager Portal Monitoring and Management Guide. which is set to Y (yes) by default.Using BMC Performance Manager In the BMC Impact Service Model Editor. you build and maintain a service model with component objects.

and component statuses. Direct Publish data has a higher precedence and hence overwrites Direct Feed data. Data modification or deletion is allowed only when the publish environment ID of the requester matches the publish_env_id of the data. Publication will fail if the referred management data is not published. Events that are attached to lower precedence CIs are automatically reattached to overwriting CIs of higher precedence. types of service component instances. modifying. In addition to these rules. then Y is deleted. for example. Between Direct Publish and Direct Feed data. Service components This section contains overview information about components classes and types. These key slot collision rules apply to SIM data and relationships (the keys of a relationships are the provider_id and consumer_id). extra operations are performed when overriding. BMC Performance Manager. has precedence pX with key slot values that collide with existing data Y with precedence pY. pposter. and BMC Atrium CMDB must not create data with the same mc_udid. or deleting CIs to ensure the uniqueness of each alias and to avoid (local) relationships with dangling ends. 22 BMC Impact Solutions Service Modeling and Publishing Guide . otherwise the addition of X fails. Overriding rules When data X. such that pY < pX. Precedences Data published from BMC Atrium CMDB automatically overwrites Direct Publish data and Direct Feed data. Data overrides other data with a lower precedence if s s it has the same key slots or in the case of a MC_SM_COMPONENT.Precedences Management data that comes from DirectFeed cannot be referred to by a service model that is published. Do not modify key slots. when it has the same alias Different system sources like BMC Impact Explorer.

All service model classes and related slots are stored in the BMC Impact Manager’s server/etc/default/SIM/kb directory. You can view a list of subclasses or child classes that are associated with a class. such as attributes. an application. Select the most appropriate subclass for each component that you want to create. “Default service model data classes” on page 305. or any aspect of business for which you want to employ service impact management. BMC_Keyboard). JBoxxServer 123. you can extend the class hierarchy by adding a new subclass definition to the BMC Atrium CMDB Class Manager. Chapter 2 Understanding a service model 23 . you select one of the component types from the Templates dockable window and modify that template to create a component instance that defines a specific logical or physical asset. When you define a new service model component. a service. For a description of data class definitions that support the service model. The component instance is the specific. In BMC Impact Service Model Editor. unique occurrence of a component type. unique version of the type: for example. The class includes information about the object type. you must create it using a subclass of the BMC_BaseElement class. Service components can represent a hardware component. A component type is the generic object: for example. see Appendix B. A service component class is a CDM class that is available for inclusion in a service model. Service component instances In BMC Impact Service Model Editor. The farther down the hierarchy a particular class occurs. There are whole classes of objects that are not visible to SIM because they do not make sense in a service model (for example. server. and so on. Classes and their creation are covered in detail in the BMC Atrium CMDB Installation and Configuration Guide. A service component type is a data class that defines a logical or physical asset that participates in the delivery of a business service. You can also extend an existing class definition by adding one or more slots to store component-specific information.Component classes and types Component classes and types A class is the definition or metadata that describes an object type. customer groups. primary key. Service components are organized in a hierarchy of classes in which each class represents a component type. a component instance is a specific. If an appropriate subclass does not exist or is too generic. the more specific its type. These are the only classes visible in BMC Impact Service Model Editor and BMC IM.

24 BMC Impact Solutions Service Modeling and Publishing Guide . Information about the status of a component instance is stored in the cell in the instance’s status slot. The initial status of a service component instance. Table 7 Service component status definitions Default color value Equivalent BAROC Enumeration status 01 BLACKOUT monitoring of the component dark gray is suspended for a scheduled period status of the component has not yet or cannot be determined nothing has occurred that affects the component’s normal delivery of service awaiting information on the component component is delivering services normally. which is indicated by the color of the component’s icon in BMC Impact Explorer and BMC Impact Portal.Component status and substatus Component status and substatus A service component instance is characterized by its status. but some problem may effect it component’s delivery of service is slightly affected component’s delivery of service is affected component has a failure and is unable to deliver service light gray 10 NONE (no substatus) BLACKOUT Service component status Meaning UNKNOWN 20 UNKNOWN OK green 30 OK INFORMATION WARNING medium blue yellow 40 50 INFO WARNING MINOR IMPACT IMPACTED UNAVAILABLE light orange orange red 60 70 80 MINOR MAJOR CRITICAL NOTE Do not confuse the MC_SM_COMPONENT_STATUS enumeration with the STATUS enumeration that defines event status values. such as OPEN or ACK. just after its creation. Table 7 defines the default service component status values that are available in BMC Impact Explorer. is determined by the default value of its class-level status slot (usually this value is green or OK).

The cell computes a component’s status using a status computation model that you assign to the component instance in the StatusModel attribute. on the Status and Alias tab. in the Status Computation box. or both. For more information about component status computation and status computation models. see Chapter 4. and Self-Preferred. NOTE Whether and how the status of a provider component is propagated through a relationship is controlled by the relationship policy assigned to the component instance. Based on the specific status computation model. You select the status computation model for each component instance in the Create (or Edit) Component dialog box. In contrast. BMC Impact Service Model Editor ensures that each component instance is associated with a valid status computation model. by other components’ status changes. For more information about selecting a relationship policy for a component.Component status computation Component status computation The status of a component instance is computed automatically by the cell when new conditions occur. See “Creating service component instances in BMC Impact Service Model Editor” on page 60. Status Weight is used in impact relationships to determine how much importance (numerically weighted) to give to each provider relationship that impacts a consumer instance. the greater the importance. such as s s s a new event is received that has a direct impact on the component the severity of an event impacting a component changes another component’s status change is propagated to the component Whether the status of a component is influenced directly by events. see Chapter 5. depends on the component’s type and its relative position in a particular service infrastructure. The higher the number. the cell uses an algorithm to calculate the s s s status values propagated by inbound relationships severities of direct events associated with the service component instance impact status and service component self-status The predefined status computation models available are Standard. Cluster. For example. “Component and relationship status propagation” on page 17. The Weighted Cluster status computation model uses the Status Weight attribute of the BMC_Impact object. logical components such as applications or business groups rely on their relationships to IT components to provide their current status. Weighted Cluster. the status of an IT component usually reflects the associated resource events that directly impact its status. Chapter 2 Understanding a service model 25 . “Building a service model in BMC Impact Service Model Editor” on page 17.

and the class of the component as defined in the data model. Table 8 Component superclass Logical Entity Activity Service model component types (part 1 of 7) Icon Component type Component class BMC_LogicalEntity BMC_Activity Activity Decision BMC_Activity ActivityType=ActivityDecision BMC_Activity ActivityType=ActivityEnd BMC_Activity ActivityType=ActivityInteraction BMC_Activity ActivityType=ActivityManual BMC_Activity ActivityType=ActivityStart BMC_BusinessProcess Activity End Activity Interaction Activity Manual Activity Start Business Process Business Service BMC_BusinessService Database BMC_DataBase 26 BMC Impact Solutions Service Modeling and Publishing Guide .Service model component types Service model component types Table 8 lists the component types. the icon that represents the component in BMC Impact Service Model Editor and in the consoles. the superclass of the component. These classes are derived from the class BMC_BaseElement.

Service model component types Table 8 Component superclass Collection Service model component types (part 2 of 7) Icon Component type User Community Component class BMC_Collection BMC_UserCommunity Connectivity Collection BMC_ConnectivityCollection IP Connectivity Subnet BMC_IPConnectivitySubnet IPX Connectivity Network BMC_IPXConnectivityNetwork BMC_LNsCollection BMC_LNsCollection LAN Network BMC_LAN WAN Network BMC_WAN Organization BMC_Organization System Access Server BMC_System BMC_ComputerSystem PrimaryCapability=Access Server BMC_Application Application Application Infrastructure BMC_ApplicationInfrastructure Application System BMC_ApplicationSystem Cluster BMC_Cluster Chapter 2 Understanding a service model 27 .

Service model component types Table 8 Component superclass System Service model component types (part 3 of 7) Icon Component type Communication Server Component class BMC_System BMC_SoftwareServer SoftwareServerType=Communication Server BMC_ComputerSystem Computer System Configuration Management Agent BMC_SoftwareServer SoftwareServerType=ConfigMgmtAgent Database Server BMC_SoftwareServer SoftwareServerType=DataBaseServer BMC_SoftwareServer SoftwareServerType=DNSServer BMC_ComputerSystem PrimaryCapability=File Server BMC_ComputerSystem PrimaryCapability=Firewall BMC_SoftwareServer SoftwareServerType=FTPServer BMC_ComputerSystem PrimaryCapability=Gateway BMC_ComputerSystem PrimaryCapability=Hub BMC_ComputerSystem PrimaryCapability BMC_ComputerSystem PrimaryCapability=JBOD BMC_ComputerSystem PrimaryCapability=Layer 3 Switch DNS Server File Server Firewall FTP Server Gateway Hub Input/Output Device JBOD (Just a Bunch Of Disks) Layer 3 Switch 28 BMC Impact Solutions Service Modeling and Publishing Guide .

Service model component types Table 8 Component superclass System Service model component types (part 4 of 7) Icon Component type LDAP Server Component class BMC_System BMC_SoftwareServer SoftwareServerType=LDAPServer BMC_ComputerSystem PrimaryCapability=LoadBalancer BMC_SoftwareServer SoftwareServerType=MailServer BMC_Mainframe Load Balancer Mail Server Mainframe Message Server BMC_SoftwareServer SoftwareServerType=MessageServer BMC_ComputerSystem PrimaryCapability=Mobile User Device Mobile User Device (a handheld personal data assistant (PDA)) Monitor BMC_Monitor Print Server BMC_ComputerSystem PrimaryCapability=Print BMC_SoftwareServer SoftwareServerType=PrintServer BMC_ComputerSystem PrimaryCapability=RAIDStorageDevice BMC_SoftwareServer SoftwareServerType=ResourceServer BMC_ComputerSystem PrimaryCapability=Router BMC_ComputerSystem PrimaryCapability=SANBridge Print Server RAID Storage Device Resource Server Router SAN Bridge Chapter 2 Understanding a service model 29 .

Service model component types Table 8 Component superclass System Service model component types (part 5 of 7) Icon Component type SAN Director Component class BMC_System BMC_ComputerSystem PrimaryCapability=SANDirector BMC_ComputerSystem PrimaryCapability=SANHub BMC_ComputerSystem PrimaryCapability=SANRouter BMC_ComputerSystem PrimaryCapability=SANSwitch BMC_SoftwareServer SoftwareServerType=SecurityServer BMC_ComputerSystem PrimaryCapability=Server BMC_SoftwareServer SAN Hub SAN Router SAN Switch Security Server Server Software Server Storage BMC_ComputerSystem PrimaryCapability=Storage BMC_ComputerSystem PrimaryCapability=Switch BMC_ComputerSystem PrimaryCapability=TapeLibrary BMC_SoftwareServer SoftwareServerType=TelnetServer BMC_SoftwareServer SoftwareServerType=TransactionServer Switch Tape Library Telnet Server Transaction Server UDDI Server BMC_SoftwareServer SoftwareServerType=UDDIServer 30 BMC Impact Solutions Service Modeling and Publishing Guide .

5.Service model component types Table 8 Component superclass System Service model component types (part 6 of 7) Icon Component type Virtual System Component class BMC_System BMC_VirtualSystem (deprecated as of BMC Atrium CMDB version 7.00) BMC_ComputerSystem PrimaryCapability=Web Caching BMC_SoftwareServer SoftwareServerType=WebServer BMC_SystemService Application Service BMC_ApplicationService Web Cache Web Server System Service System Component BMC_SystemComponent Hardware System Component BMC_HardwareSystemComponent Media BMC_Media CD ROM Drive BMC_CDROMDrive Disk Drive BMC_DiskDrive Floppy Drive BMC_FloppyDrive Tape Drive BMC_TapeDrive Uninterruptible Power Supply BMC_UPS (UPS) Chapter 2 Understanding a service model 31 .

00) BMC_SystemResource System Resource 32 BMC Impact Solutions Service Modeling and Publishing Guide .Service model component types Table 8 Component superclass Service model component types (part 7 of 7) Icon Component type Logical System Component Component class BMC_SystemComponent BMC_LogicalSystemComponent System Component File System BMC_FileSystem Database Storage BMC_DataBaseStorage Local File System BMC_LocalFileSystem Remote File System BMC_RemoteFileSystem Disk Partition BMC_DiskPartition Software BMC_Software System Software BMC_SystemSoftware Operating System BMC_OperatingSystem Virtual System Enabler BMC_VirtualSystemEnabler VMware BMC_VMWare (deprecated as of BMC Atrium CMDB version 7.5.

the provider status naturally impacts the consumer status. NOTE Only BMC_Impact relationships are considered. Chapter 2 Understanding a service model 33 . BMC_Component is used to define composite objects. software. more indirect level. which business services are affected if Router C fails. This relationship defines a composite computer system. This is different from impact relationships in that a dependency can be at a lower direct level. BMC_Dependency BMC_Component BMC_MemberOfCollection BMC_ElementLocation Service consumers and providers A service model relationship is a link between a component that provides a service and the components that consume that service. When you define relationships in a service model. for example. BMC_MemberOfCollection is used to define groupings of instances in a logical manner. In a provider/consumer relationship. or to define the set of component instances that make up a business process or service. Table 9 lists the main relationship classes derived from BMC_BaseRelationship. and so on. maintenance and similar purposes.Component relationships Component relationships Service management relationships are impact relationships. or used. Table 9 Class name BMC_Impact Main relationship classes Class description The BMC_Impact relationship. inventory. network cards. and subinstances of disk drives. It is used to define the network topology. of which only BMC_Impact defines impact relationships for a service model. while an impact is often at a higher. monitors. BMC_Dependency describes component relationships that are dependent on each other. and the subclasses that derive from this class are used to define service impact relationships between component instances. BMC_ElementLocation ElementLocation associates a ManagedElement with a Location for positioning. One key component relationship in the CMD is between the system and system component classes. by SIM. you make it possible to know. which is made up of a computer system instance.

Such a relationship states that a component instance is impacted if something happens to the component instances to which it is related. Important components Some components can be considered “important” components and can be set to propagate their priority back to their provider. Figure 4 Impact (status) propagation in relationships The service model enables a component instance to be related to another component instance by defining the relationship in the BMC_Impact class. 34 BMC Impact Solutions Service Modeling and Publishing Guide . Service model relationships are organized in a hierarchy of data classes in which each class represents a relationship type. In Figure 4. a group of people responsible for accounting will be impacted when the accounting database server is down. For example. Component B is a provider in one relationship and a consumer in another.Service consumers and providers The concepts of provider and consumer are relative to the relationship being considered. The parent class for component relationships is BMC_Relationship. see “Impacts priority” on page 146. For more information about priority propagators. All service model relationship classes are defined in the BMC Atrium CMDB as a subclass of BMC_Relationship.

The consumer does not have a dependency. the cell can automatically propagate the status of a provider component through its outbound impact relationships as new conditions occur. or the dependency is unimportant.Status propagation in relationships Status propagation in relationships Status propagation is the passing of a status or a modified status from one component instance to another through a relationship. No impact relationship exists. see Chapter 5. An impact relationship exists. “Component and relationship status propagation” on page 125. In status propagation models. For more information about status propagation and status propagation models. The service model ensures that each impact relationship instance is associated to a valid status propagation model. a relationship is characterized by its state. A relationship can be either active or inactive. Relationship state values are defined internally in the cell as the enumeration MC_SM_RELATIONSHIP_STATE. such as s s the component’s status changes the state of an outbound impact relationship changes. as shown in the following table: Relationship state value ACTIVE INACTIVE Meaning The consumer component depends on its provider. Chapter 2 Understanding a service model 35 . Depending on the status propagation model assigned to the relationship. the state of a relationship determines whether the provider’s status or a modification of it is passed to the consumer service component. Relationship states Just as a component is characterized by its status. altering the status propagation from the provider component This status can then be propagated to subsequent components within the service model.

Each time an impact relationship instance is submitted for creation. 36 BMC Impact Solutions Service Modeling and Publishing Guide . the cell seeks an BMC_STATUS_PROPAGATION instance that matches s s s the name of the propagation model used by the component relationship the component type of the provider in the relationship the component type of the consumer in the relationship During this process. Otherwise. the creation process is blocked. The BMC_STATUS_PROPAGATION table defines the valid pairs of component types whose instances can participate in a specific type of relationship. the relationship is valid. based on s s the current state of the relationship (active or inactive) the current value of the provider’s status Status propagation models are used only by impact relationships. Relationship control Relationship control is the enforcement of logical rules in creating new service model relationships. the cell uses the component’s class hierarchy to interpret the component types in the BMC_STATUS_PROPAGATION instances.Relationship control Status propagation models A propagation model defines how the status of a provider component must be propagated in an impact relationship. dynamic status mapping—Propagation models translate the computed status of the provider component into a propagated status for input into the impact_function slot of the related consumer component. Status propagation models serve these purposes: s relationship control—Propagation models enforce logical rules in new component relationships so that only valid relationships are created. If there is a matching BMC_STATUS_PROPAGATION instance. The role of the BMC_STATUS_PROPAGATION class instance is to restrict the use of a propagation model to consumer and provider relationships.

an event with a severity of CRITICAL could turn the status of the associated component to UNAVAILABLE by using a severity-tostatus mapping table. The cell can accept event instances from a variety of sources: s s s Events can be manually obtained directly through adapters and the msend and mposter commands. This information can be formatted into events that a cell can process. as described in the following process: 1. With this process in place. When two components participate in an impact relationship and the status of the provider changes. Other sources include third-party products that can be integrated with BMC IM. or capturing the SNMP traps that it sends. The arrival of an event invokes a unique predefined rule that generates a value for the event’s mc_smc_alias slot and searches for the matching service component in the alias table. incoming events can alter the status of the component directly in real time. First. A group of BMC_PROPAGATION_MAP instances sharing the same name form a propagation map that is uniquely bound to the status propagation model with the same name. The actual association is done using a slot-mapping data table. the new status must be propagated to a consumer component. Cells also provide events through propagation rules. For example. you can obtain status information by actively monitoring the resource’s variables. most of which are or can be instrumented. which stores all the slot-mapping formulas for event classes. the cell seeks the BMC_PROPAGATION_MAP instance in which the following value matches occur: Chapter 2 Understanding a service model 37 .Dynamic status mapping Dynamic status mapping Dynamic status mapping translates the main status of the provider component into a propagated status for input into the impact function of the consumer component in a relationship. The BMC_PROPAGATION_MAP table defines the status-mapping instances for the relationships. 2. bringing the events from the monitoring application into the cell For physical resources. associating those events with the service model component instance that represents the resource You can associate events from a resource with the component instance that represents it by using the alias key. parsing its log files.

depending on the current state of the relationship (ACTIVE or INACTIVE). Event association uses the aliases that you assign to service components and event alias associations that you create in BMC Impact Service Model Editor. the cell propagates the appropriate changed status to the consumer component. DBsoftware. Propagation maps affect only the way in which the main status of the provider is propagated in the relationship. For example. consider an impact relationship with service component named XService that is a consumer of an IT component. This event association provides the mechanism for keeping a component instance’s status up-to-date. it matches the corresponding relationship state (ACTIVE). Event associations A production service model requires that the incoming events that contain information about the state of a IT asset be associated with the appropriate service model component instance. The relationship is active and the propagation model assigned to it is INCREASING.Event associations BMC_PROPAGATION_MAP instance slot value Matching class instance name relationship_state provider_status relationship relationship provider component Matching value propagation_model slot value state slot value status slot value Then. the cell obtains the appropriate propagated_status value to propagate. The cell propagates this value to the consumer component for input to the consumer’s status computation. To obtain the appropriate propagated_status value. so that it reflects the real-time health of the actual resource that it represents. you must s bring events from the resource into the cell 38 BMC Impact Solutions Service Modeling and Publishing Guide . Finally. To set up an event association. it searches the INCREASING propagation map to find the instance corresponding to a provider status of IMPACTED. which is a value of UNAVAILABLE in this instance. XService. When the cell needs to propagate DBsoftware’s current status (IMPACTED) to its consumer component. They do not affect how the substatus is propagated from the provider to the consumer.

it is not associated with any object in the service model. Component aliases You designate a component instance as participating in alias activity by entering a value in the Alias attribute when you create or edit a component instance in BMC Impact Service Model Editor. the cell constructs an alias using data in the event’s slots plus any other elements specified in the alias formula. Service component aliases are stored in the BMC Atrium CMDB and are associated with the relevant service component by the component’s universal data identifier (udid). An alias formula defines the content and format of the alias. When an event arrives at the cell.Bringing events from the resource into the cell s associate the events with the service model component instance that represents the resource — enter an alias in the Alias attribute of the component instance — create an appropriate event alias association for the component instance s verify that the event association works correctly Bringing events from the resource into the cell To bring events to a cell. a thirdparty product. A service component instance can have several different aliases so that different event types can be easily associated with it. An alias formula is an object published to the cell. For information about entering component aliases in a component instance. a BMC Impact Integration product. it is management data supporting the service model. or another utility to produce BMC Impact Manager events. to provide the necessary information about its status. you configure the event sources for the resource. An alias identifies a specific component instance. Chapter 2 Understanding a service model 39 . such as a log file or an SNMP trap file. You can use a BMC Impact Event adapter. see “Creating service component instances in BMC Impact Service Model Editor” on page 60.

For example. DATABASE_EVENT. depending on the component instance’s status propagation model. to be considered by the cell. as shown in Figure 5. for an application component instance. After the cell has constructed the event’s alias. [$1. such as SYSTEM_EVENT. you want events of a particular category.mc_object/$1.mc_object. An example of a simple alias formula is EXAMPLE [‘sprintf("%s/%s". Figure 5 Parts of a simple alias formula sprintf format specifications expressions ['sprintf("%s/%s". When you set up the dynamic association of events with a component instance. APPLICATION_EVENT.mc_host])'] 40 BMC Impact Solutions Service Modeling and Publishing Guide .mc_host])'] The order of the sprintf format specifications corresponds to the order of the expressions. you must specify two elements: s s an event class an alias formula The event class identifies which incoming events may affect the status of the component instance. it searches each component instance to see if the value in its ComponentAlias attribute matches the alias constructed from values in the event. It consists of sprintf format specifications (which specify the format for the output) followed by expressions that specify event slots and functions involved in the construction of the alias.$1. The alias formula must have a syntax that can be read by the cell.Event alias associations Event alias associations You set up the dynamic association of events with a component instance by using the Tools => Alias Formulas menu command in BMC Impact Service Model Editor. If it matches.[$1. the event is associated with the component instance in the BMC_SIM_ALIAS class and can change the component instance’s status.

NOTE The BMC_SIM_ALIAS object is part of the SIM management data. with $1 representing the event ID). mc_object='SALES'.store. mc_object_class='C entral Database'. ComponentAlias='SALES/dcsrv02.mc_object/ $1. END The alias links the event DATABASE DOWN to the component instance with the component ID 1234. %s/%s is the data type of the output and $1. END mc_host are output as string values. the alias formula. When the cell finds a match. Other examples of alias formulas: Chapter 2 Understanding a service model 41 .megastore. It is not visible in BMC Impact Service Model Editor.mc_object (which is the value in the mc_object slot of the event. The second format specification %s (a string). corresponds to the second variable expression. the alias that was computed from the data in the event and the alias formula. which in this example matches the computed alias from the event data.mc_object $1.com'.com Component instance alias DATABASE DOWN. Table 10 shows the event data. [$1. $1.com'. an entry is created in the BMC_SIM_ALIAS class.s tore.mc_host are variable expressions. corresponds to the first variable expression $1.mc_host. and the alias stored in the component instance. ComponentID='1234'. msg='Database is down'.Event alias associations In Figure 5. with a slash between them. The first format specification. Table 10 Event How an event alias association works Alias Formula [‘sprintf("%s/%s".mc_host])’] The values in mc_object and Alias SALES/dcsrv02. %s (a string). mc_host='dcsrv02. as shown in this example: EXAMPLE BMC_SIM_ALIAS.

strextract($1. Since there can be more than one matching entry.mc_object. the contains that has its match closer to the beginning of the string wins s s s Service schedules Service schedules are a combination of a defined schedule with a specific service model component that indicates when the component must meet availability or performance goals.mc_object)).$1. — has_suffix.[$1. — any s s for multiple has_prefix matches on the same element. or when it must meet its availability and performance goals.date.strextract($1. — contains.mc_ueid. — has_prefix.1)’] ['sprintf("%s%s%s".1.Service schedules EXAMPLE [‘sprintf(%s.mc_object. the longest suffix wins for multiple contains matches on the same element.adapter_host])'] Precedence rules for alias formulas The most specific matching entry is selected. s Periods when a component instance is in high demand. 42 BMC Impact Solutions Service Modeling and Publishing Guide . are called During Schedule. precedence rules determine the entry that is used: s a match for element nth has precedence over a match for element (nth + 1) for matches on the same element.6))’] [‘sprintf(Mail@robot%s. in the following order: — equals.(len($1.$1. precedence is based on the conditional operator in the formula. Each component is assigned a service schedule (but it can be a schedule shared with other components). the longest prefix wins for multiple has_suffix matches on the same element. the longest contains wins for multiple contains matches on the same element and with the same length.

Also. Periods within During Schedule in which a component is considered to be Off Schedule are called Exceptions Within During Schedule. You create local timeframes and use them only in the BMC Impact Explorer schedules editor. any undefined time is considered Off Schedule. to 5 P. s Table 11 illustrates the differences between Global timeframes and Local timeframes. Table 11 Global Local Global and Local timeframe differences Created in BMC Impact Service Model Editor BMC Impact Explorer Stored in Available to BMC Atrium CMDB all cells a single cell event management policies within a single cell Timeframe type Service schedules example with exceptions Consider a component that is expected to meet its performance goals from 8 A. The same component. to 8 A.M. s Global timeframes are created in the BMC Impact Service Model Editor.M. would be Off Schedule during that time. Two types of timeframes exist: Global and Local. Local timeframes are stored in a single cell and are only available to the event management policies within that cell. are called Off Schedule. each day. These priority changes are discussed in more detail in “Dynamic prioritization” on page 136.M. You create global timeframes and use them in both BMC Impact Service Model Editor and the BMC Impact Explorer. or when the component’s s availability and performance are less important.M. This period is would be considered During Schedule. each day. if not needed from 5 P. s Component attributes such as cost or base priority might have different values depending on whether the component is in high demand (a During Schedule period) or in low demand (an Off Schedule period). Timeframes Service schedules are built of timeframes. Timeframes are blocks of time that specify the times that are During Schedule or Exceptions Within During Schedule. Chapter 2 Understanding a service model 43 . stored in the BMC Atrium CMDB and are available to all cells within an environment.Timeframes s Periods when a component instance is in low demand.

). if the component is scheduled to be taken offline every day from noon to 1 P.M.M. to noon. and another from 1 P. instead of creating two different During Schedule timeframes (one for 8 A. to 5 P..M.M. 44 BMC Impact Solutions Service Modeling and Publishing Guide . you could create an Exceptions Within During Schedule timeframe.Service schedules example with exceptions Within the During Schedule period.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datasets . . . Importing Business Time Segments from BMC Remedy AR System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Promotion . . . . Service model publishing . . . . . . . . . . . . . . . . . . . . . 46 46 51 52 52 52 53 54 54 55 Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 3 This chapter presents the following topics: Role of the BMC Atrium CMDB in service modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-model and not-in-model component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model execution on cells . . . . . . . . . . . . . Service model and the Common Data Model . . . . . . . . . . . . . . . . . . . . . Sandboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

service management. SIM classes BMC Impact Solutions extends the BMC Atrium CMDB CDM with a predefined set of SIM-enabled classes. The ability to capture the raw data from various sources and reconcile it to a controlled dataset enables the interaction between various automation tools. based on what each source is proficient at obtaining. 46 BMC Impact Solutions Service Modeling and Publishing Guide . Service model developers and administrators use the BMC Atrium CMDB Configuration Console and BMC Atrium CMDB Class manager APIs to build and modify the Common Data Model (CDM). The BMC SIM CMDB Extensions also define attributes that are used only for SIM. The asset information you use to define the service model is a subset of all of the configuration data in the CDM. All service component types (classes) are defined in the BMC Atrium CMDB as part of the CDM. This makes it possible for the same component or relationship instances to exist in more than one dataset. such as attributes. Datasets provide a mechanism for storing raw data from multiple resources in discrete locations. The class includes information about the object type.Role of the BMC Atrium CMDB in service modeling Role of the BMC Atrium CMDB in service modeling The BMC Atrium Configuration Management Database (BMC Atrium CMDB) is a multi-component that enables applications to store and share data. Then the reconciliation process takes that data and merges it appropriately to create a composite set of unique data instances that includes information from each source. such as StatusModel and ImpactCostPerSec. each containing component instances and relationships for a given purpose. A class is the definition or metadata that describes an object type. Service model and the Common Data Model The Common Data Model (CDM) is an extensible class schema that represents configuration items and their relationships to each other in an IT enterprise. and so on. With the BMC Atrium CMDB you can divide your configuration data into partitions called datasets. and user information) and to provide a mechanism for linking that information to provide a complete view of how all elements of a company are connected and can affect each other. primary key. It is designed to store asset data (as hardware.

Table 12 SIM-qualified subclasses of BMC_Collection Third Level BMC_ConnectivitySegment BMC_IPConnectivitySubnet BMC_IPXConnectivityNetwork BMC_LNsCollection BMC_Organization BMC_UserCommunity BMC_LAN BMC_WAN Fourth Level Second Level BMC_ConcreteCollection BMC_ConnectivityCollection Table 13 lists the SIM-qualified classes for BMC_LogicalEntity. The following tables list the main data subclasses to BMC_BaseElement that are associated with service impact management. including people. which contains the definition of computer systems. The BMC_Impact subclass of BMC_BaseRelationship comes of the box as part of the core CDM classes for version 7. Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 47 . and virtual systems. BMC_BaseElement and all relationships derive from the BMC_BaseRelationship subclass. which provides mechanisms for grouping components together into logical elements. including business processes and services. application systems. Table 13 SIM-qualified subclasses of BMC_LogicalEntity Third Level BMC_BusinessProcess Second Level BMC_Activity BMC_BusinessService BMC_Database Table 14 lists the SIM_qualified classes for BMC_System. and location information. Table 12 lists the SIM-qualified subclasses for BMC_Collection.Service model and the Common Data Model All components in the data model derive from a single subclass. which tracks other logical elements of a system. All impact relationships are instances of BMC_Impact. mainframes. see the Common Data Model Diagram included with BMC Atrium CMDB documentation. physical plants.5 of the BMC Atrium CMDB CDM. For a graphical representation of the hierarchy of the Common Data Model.

Table 16 Fifth Level BMC_SystemSoftware SIM-qualified subclasses of BMC_Software Sixth Level BMC_OperatingSystem BMC_VirtualSystemEnabler Seventh Level BMC_VMWare 48 BMC Impact Solutions Service Modeling and Publishing Guide . applications like Microsoft Word. This includes physical components like disk drives and monitors. Table 15 SIM-qualified subclasses of BMC_SystemComponent Third Level BMC_ Software BMC_DiskPartition BMC_SystemResource BMC_FileSystem BMC_DataBaseStorage BMC_LocalFileSystem BMC_RemoteFileSystem BMC_CDROMDrive BMC_DiskDrive BMC_FloppyDrive BMC_TapeDrive Fourth Level BMC_SystemSoftware Second Level LogicalSystemComponent HardwareSystemComponent BMC_UPS BMC_Media Table 16 lists the SIM-qualified classes for BMC_SystemSoftware. a continuation of the BMC_SystemSoftware entry in Table 15.Service model and the Common Data Model Table 14 SIM-qualified subclasses of BMC_System Third Level BMC_Application BMC_ApplicationInfrastructure BMC_SoftwareServer BMC_Mainframe Printer BMC_VirtualSystem Second Level BMC_ApplicationSystem BMC_Cluster BMC_ComputerSystem Table 15 lists the SIM-qualified classes for BMC_SystemComponent. The attributes for BMC_SystemComponent are SystemClassId and SystemName. and other soft elements like network drives and file shares. which stores information on the components that comprise the system.

Service model and the Common Data Model Table 17 lists the SIM-qualified class for BMC_SystemService. such as J2EE modules. The most common services are those used by J2EE application systems. which tracks the services used by systems. The data model also provides a set of classes for defining relationships among configuration items. The attributes for BMC_SystemService are SystemClassId and SystemName. Table 17 SIM-qualified subclass of BMC_SystemService Second Level BMC_ApplicationService Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 49 .

SME_Read. SME_Read. SME_ReadWrite] ImpactCostPerSec [SIM. SME_ReadWrite] Floor [SIM. SME_Read. SME_Read. SME_ReadWrite] ImpactCostUnit [SIM. SME_Read. SME_ReadWrite] ClusterType [SIM. SME_ReadWrite] Description [SIM. SME_ReadWrite] ShortDescription [SIM. SME_ReadWrite] BMC. SME_ReadWrite] InstanceId [SIM. SME_ReadWrite] ClassId [SME_Read. SME_ReadWrite] Model [SIM. SME_ReadWrite] Region [SIM. SME_ReadWrite] Item [SIM. SME_ReadWrite] Types [SIM. SME_ReadWrite] ScheduleId [SIM. SME_Read.SIM BMC_Cluster BMC. SME_ReadWrite] PriorityOut [SIM. SME_ReadWrite] Site [SIM. SME_ReadWrite] Notes [SIM. SME_Read. SME_ReadWrite] Priority [SIM. SME_Read. SME_Read. SME_ReadWrite] Type [SIM. SME_Read. SME_ReadWrite] ReconciliationIdentity [SME_Read.Service model and the Common Data Model SIM attributes SIM qualifiers have been added to the attributes listed in Table 18. SME_ReadWrite] CMDBWriteSecurity [SME_Read. SME_Read. SME_ReadWrite] OwnerName [SIM. SME_ReadWrite] ReadSecurity [SIM] WriteSecurity [SIM] ComponentAliases [SIM. SME_ReadWrite] Department [SIM. SME_Read. SME_Read. SME_ReadWrite] OwnerContact [SIM. SME_ReadWrite] Company [SIM.CORE Attributes AccountID [SIM] Category [SIM. SME_ReadWrite] CMDBRowLevelSecurity [SME_Read. SME_Read. SME_ReadWrite] StatusModel [SIM. SME_ReadWrite] MaxNumberOfNodes [SIM. SME_Read. SME_ReadWrite] DatasetId [SIM.AM BMC.CORE 50 BMC Impact Solutions Service Modeling and Publishing Guide . SME_ReadWrite] Room [SIM. SME_Read. SME_ReadWrite] HomeCellAlias [SME_ReadWrite] PriorityWatchdog [SIM. SME_Read. SME_ReadWrite] SiteGroup [SIM. SME_ReadWrite] InterconnectAddress [SIM. SME_ReadWrite] ImpactCostPerSecOut [SIM. SME_ReadWrite] Interconnect [SIM. SME_Read. SME_ReadWrite] MarkAsDeleted [SME_Read. SME_Read. SME_Read. SME_ReadWrite] ManufacturerName [SIM. SME_ReadWrite] Name [SIM. SME_ReadWrite] VersionNumber [SIM. Table 18 Class BMC_BaseElement SIM-qualified attributes Namespace BMC.

allowing you to make multiple edits to the sandbox model until you promote the changes the production dataset. SME_ReadWrite] PrimaryCapability [SIM. SME_Read. and sandboxes persist between user sessions. SME_ReadWrite] DomainName [SIM. SME_Read. SME_ReadWrite] MediaType [SIM.CORE BMC. SME_Read. SME_Read. SME_Read. SME_Read. without affecting the production environment until you are ready to move the changes into the production dataset. SME_ReadWrite] VirtualSystemType [SIM.CORE BMC. Each user has one sandbox associated with the user account.CORE The definitions of the SIM qualifiers are s s s s SIM: 300050 SIM_Internal: 300060 SIM_ReadWrite: 300070 SME_Read: 300080 Sandboxes A sandbox is a personal work area for designing and developing a service model. impact relationships. You can make changes to objects and their relationships. SME_Read.CORE BMC_SystemComponen BMC. and save these changes between work sessions. BMC Impact Service Model Editor users each have their own unique. SME_Read. SME_Read.CORE BMC. SME_Read. SME_ReadWrite] OSType [SIM.CORE ent BMC_OperatingSystem BMC_VirtualSystem BMC_WAN BMC_ComputerSystem BMC. SME_Read. SME_Read. SME_Read. SME_ReadWrite] SystemName [SIM. SME_ReadWrite] SystemType [SIM. SME_ReadWrite] Hostname [SIM. SME_ReadWrite] SystemName [SIM. dedicated sandbox. SME_Read. SME_Read. SME_ReadWrite] WANType [SIM. Changes to your sandbox do not affect sandboxes of other users if those changes are not promoted. or management data instances) in their sandbox because only the values from the sandbox that was promoted last will be in the production dataset. SME_ReadWrite] BMC_ConnectivitySegm BMC. SME_ReadWrite] CapabilityList [SIM. Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 51 . SME_ReadWrite] SystemClassId [SIM.CORE t BMC_Media BMC_SystemService BMC. SME_ReadWrite] MaxMediaSize [SIM. SME_ReadWrite] SystemClassId [SIM.CORE BMC. NOTE No two users should have the same data (components.Sandboxes Table 18 Class SIM-qualified attributes Namespace Attributes ConnectivityType [SIM.

changes in the sandbox are merged with changes from other users and processes in the BMC Atrium CMDB and. You must have sufficient permissions to send data to a test cell. Promotion You move changes that you make in a sandbox (on the overlay dataset) to the production dataset in a controlled process called promotion. then view the generated events in BMC Impact Explorer to determine if the desired result occurs. When a promotion completes successfully. users are making changes to an overlay dataset. Testing Before moving sandbox changes into production. or logical partition of data in the BMC Atrium CMDB. and management data. you could send test data to a test cell. Many of these objects can be out-of-model (they are not yet in BMC Impact Manager cells). relationships. Another type of dataset is the test dataset. BMC Impact Service Model Editor limits promotion to 3000 component instances at a time. As soon as you successfully promote changes to a production dataset. a dataset which is related to and masks the production dataset. shared by SIM and ITSM applications. If you have promote permissions. The production dataset is not limited to objects that are in-model. you can send the changes to a defined test cell and explore service model behavior in the context of various events. the sandboxes of all other users are updated to reflect the new data. in-model data is sent to BMC Impact Manager cells in the environment. For example. The test dataset relays objects from a sandbox view to a test BMC Impact Manager instance.Datasets Datasets The production dataset is the reference dataset. The overlay dataset provides a view of the underlying production dataset masked by changes made by the user in the overlay dataset. if automated publishing is enabled. Objects contained in the production dataset are components. 52 BMC Impact Solutions Service Modeling and Publishing Guide . you also have access to a test cell. When working with objects in a sandbox.

however. the request is queued. followed by the automatic publication process. s s Promotion log objects are created in the BMC Atrium CMDB.PROD dataset. the ID of the reconciliation job. an execution log is generated.IMPACT. the BMC Impact Publishing Server initiates a publish from the production dataset to the BMC Impact Manager cells in the environment. The promotion process is as follows: s After making changes in a sandbox View. After the changes have been published to BMC Impact Manager instances. the BMC Impact Publishing Server is notified of the termination of a reconciliation and starts a publication. BMC Impact Service Model Editor regularly checks the progress of the reconciliation job. the BMC Impact Publishing Server distributes the BMC. if automated publishing is enabled. You can view it from the BMC Impact Service Model Editor Promote and Publish History dialog box. and a list of objects selected for promotion. From the BMC Atrium CMDB. Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 53 . you cannot work in BMC Impact Service Model Editor until the process finishes. which sends that data to appropriate BMC Impact Manager cells.Service model publishing Promotion and automated publishing process Promoting and publishing are a sequence. in which you initiate a process to push objects (new or changed) to the BMC Atrium CMDB. The objects contain the name of the user. When the promotion has ended. a short. start and end dates. When the process is completed. BMC Impact Service Model Editor updates the objects and indicates that the promotion is complete. user-specified description of the promotion. BMC Impact Service Model Editor initiates a reconciliation job. s s s Service model publishing Service model publishing is the process of distributing the service model data to BMC Impact Manager cells.ASSET dataset to cells and stores a master copy in the BMC. After the actual promotion process begins. you start the promotion process from the BMC Impact Service Model Editor interface. If other publish operations are underway at that time. you can stop the promotion or exit the BMC Impact Service Model Editor interface. After a promotion completes.

IMPACT. you might want to create the component instance but not monitor it right away. and can be monitored in BMC Impact Explorer and BMC Impact Portal.) Not-in-model component instances are visible and available in BMC Impact Service Model Editor. the cell uses the values in the event’s slots to construct an alias and then searches for that alias in the cell’s impact component instances. Publishing can be initiated automatically by using BMC Impact Service Model Editor or manually by using the BMC Impact Publishing Server CLI publish. When events that require alias processing enter the cell. 54 BMC Impact Solutions Service Modeling and Publishing Guide . Service model execution on cells Service component instances are associated with events through the use of unique aliases. When the component instances and relationships are published. depending on their status. You can choose to designate component instances as not-in-model at design time. however. You would designate that component as not in model.PROD dataset is updated and maintained only by the BMC Impact Publishing Server. When a match is found. they have not been published. In-model and not-in-model component instances Service component instances that are visible in BMC Impact Service Model Editor are classified as in-model or not-in-model component instances. they might not be visible in BMC Impact Explorer and BMC Impact Portal. the event is associated with the component instance and the instance’s status may be changed. you can monitor the component instances by using BMC Impact Explorer and BMC Portal. It mirrors the last successful publish to the cells.Service model execution on cells The BMC. (At any given time. which you specify for each component instance. published component instances are not seen in BMC Impact Explorer and BMC Impact Portal until the changes are published. In-model service component instances exist in the BMC Atrium CMDB and in the specified cell. For example. are not present in the cell. and cannot be monitored in BMC Impact Explorer and BMC Impact Portal. Changes to in-model.

are published when the next publish occurs. Importing Business Time Segments from BMC Remedy AR System You can import Business Time Segments from BMC Remedy AR System into BMC Impact Service Model Editor to use as timeframes when you define service schedules for service components. all components are assigned to DefaultCell (the cell name provided during installation) and are set to In Model.Importing Business Time Segments from BMC Remedy AR System A component instance that is in model can be monitored in BMC Impact Explorer and BMC Impact Portal. NOTE By default. Imported timeframes. For information on importing Business Time Segments. A component instance that is not in the model cannot be monitored in BMC Impact Explorer or BMC Impact Portal. Chapter 3 Understanding a service model created in BMC Impact Service Model Editor 55 . considered Global timeframes. see BMC Portal Getting Started.

Importing Business Time Segments from BMC Remedy AR System 56 BMC Impact Solutions Service Modeling and Publishing Guide .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Deleting a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Hiding a component instance . . . . . . . . . . . . . . . . . . . . . . 59 Working with service component instances . . . . . . . . . . . . . . . . . . . . . . . . 67 Copying component instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Performing actions on multiple objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Assigning related component instances to cells . . . . . . . . . . . . . . . . . . 92 Working with service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Working with timeframes . . . . . . . . . . . . . . . . 91 Icons used in the service schedule and timeframes editors . . . . . . . . . . . . . . . . . . . . . . . 85 Associating events with a component instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Working with timeframes and service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Viewing properties for a component instance . . . . This chapter covers the following topics: Service model creation process . . . . . . 95 Assigning components to service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Switching sandbox View modes . . . 84 Deleting relationships . . . . . . . . . . . . . 70 Finding component instances . . . . . . . . . . . . . . . . . . . . . . . 99 Granting access to service model objects . . . 100 Granting permissions to individual service model objects . . . . . . . . . . . . . . . . . . . . . . . . 102 Testing event associations . . . . . . . . . . . . . . . . . . . . . . 100 Testing the service model . . . . . . . . . . . . 78 Creating a component relationship in BMC Impact Service Model Editor . . . . . . . . . . . . . 71 Defining relationships between component instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Updating relationships . . . . . . . . . . . . 102 Chapter 4 Building a service model in BMC Impact Service Model Editor 57 . . . . . . . . . . 59 Launching BMC Impact Service Model Editor . . . . . . . . . . . . . . . . . . . .Chapter 4 Building a service model in BMC Impact Service Model Editor 4 This chapter provides detailed procedures on how to build the service model in BMC Impact Service Model Editor. . . . . . . . 60 Creating service component instances in BMC Impact Service Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Editing component instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Testing component relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . 122 Showing topology views. . . . . . . . . . . . . . . . . . . . . . 103 Before you promote . . . . . . . . . . . . opening. . . . . . . . . . 104 Submitting a promotion . . . . . . . . . . . . . . 110 Organizing service component instances for monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Working with BMC Impact Service Model Editor Views. . . 107 Modifying and deleting service model data. . . . . . . . . . . 117 Repositioning objects in a View . . . . 123 Exporting class definitions from the BMC Atrium CMDB to a cells . . . . . . . . . . . . 104 Verifying promotion status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 58 BMC Impact Solutions Service Modeling and Publishing Guide . . . . . . . . . . . . . . . . . . . . . . . . . . and deleting Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Refreshing the View. . . . . . . . 114 Saving. . . . . . . . . . . . . . . . 118 Controlling what you see in a View . . renaming. . . . . . . . . . . . .Promoting the service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 About the publishing process. . . . . . . . 122 Exporting and importing service model data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Repositioning the dockable windows . . . 118 Exploring consumer and provider paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Understanding visual cues in a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

To log on to BMC Impact Service Model Editor from BMC Portal 1 Open a browser. 3 Log on to BMC Portal as a user. all user validation and security is managed by the BMC Portal server. click BMC Impact Service Model Editor. BMC Impact Service Model Editor can reside on the same host computer as the BMC Portal or it can reside on another host computer. For instructions for logging on to BMC Portal. enter the URL in the format https://serverName. you must install it in one of the following ways: s as a stand-alone console from the BMC Portal product installation disk As a stand-alone console.Service model creation process Service model creation process To build a service model in BMC Impact Service Model Editor. However. serverName represents the name of the server on which BMC Portal is installed. you must s s s s s s find or create component instances in the BMC Atrium CMDB assign component instances to a BMC Impact Manager cell define component instance relationships associate events with component instances assign schedules to component instances promote the service model and publish objects to cells Launching BMC Impact Service Model Editor You can open BMC Impact Service Model Editor from the BMC Portal. in the navigation pane on left side. see BMC Portal Getting Started. 2 In the Address box. s as a Java Web Start application from BMC Impact Portal Chapter 4 Building a service model in BMC Impact Service Model Editor 59 . under Tasks. 4 On the Configure tab. Before you can launch BMC Impact Service Model Editor to view and manage services.

Creating service component instances in BMC Impact Service Model Editor You can create a service component instance in BMC Impact Service Model Editor by using the following features of the interface: s s the Template window the Create Component menu command 60 BMC Impact Solutions Service Modeling and Publishing Guide . Working with service component instances To populate the BMC Atrium CMDB with component instances for the service models. or you can manually create the component instances by using the BMC Impact Service Model Editor. you can use discovery tools such as BMC Topology Discovery or BMC Atrium Discovery. To launch BMC Impact Service Model Editor.Working with service component instances As a Java Web Start application. The BMC Impact Service Model Editor component provides a GUI to the reconciled dataset in the BMC Atrium CMDB and provides a workspace for you to create service models using the objects from this dataset. To search for existing component instances.000 service model component instances for each BMC Impact Manager cell. after BMC Impact Service Model Editor is deployed on your local desktop. you must connect to the BMC Portal. you can launch it from — the local desktop icon — a local startup menu — the Java Web Start Application Manager on your local host computer — from the BMC Portal Configure tab as a task User authentication and security is managed centrally by the BMC Portal server. see “Finding component instances” on page 71. NOTE BMC Software recommends creating a maximum of 20.

you can open the appropriate View from the Views panel. Ensure that the BMC Portal product is installed. choose Edit => Create Component. from the menu bar. The service component types are listed in hierarchical order. see the BMC Portal Getting Started guide. See “Repositioning the dockable windows” on page 122. Chapter 4 Building a service model in BMC Impact Service Model Editor 61 . see “To specify component instance attributes” on page 63. When you open BMC Impact Service Model Editor. a new sandbox View opens automatically if you have no saved Views. 2 In the Create Component dialog box. scroll in the Component Type pane until you find the appropriate component type for the instance that you are creating. Find. If you have saved Views. Views. Pan and Zoom. not in alphabetical order. To learn about creating component instances using the Template window. you can hide the dockable windows by clicking the left-pointing quick-expansion arrow located along the right side of the dockable windows. You can also open a new sandbox View at any time by clicking on the toolbar. s To create a service component instance by using the menu command 1 With a sandbox View open. and Console Navigation Bar windows. Properties.Creating service component instances in BMC Impact Service Model Editor Before you begin Ensure that you have the service catalog spreadsheet that lists IT components and their relationships. Where to go from here To enter values for other component instance attributes. You can also undock and move the Templates. continue with the next section. on the General tab. TIP s To free more desktop area for the View.

When placing objects in the sandbox View window. When you open BMC Impact Service Model Editor. right-click the new component icon and select Edit Component Properties. you can open the appropriate View from the Views panel. Large Icon. If you have saved Views. a new sandbox View opens automatically if you have no saved Views. On the General tab.Creating service component instances in BMC Impact Service Model Editor To create a service component instance by using the Template window 1 With a sandbox View open. place consumer instances above provider instances for a hierarchical layout. 3 In the View-Sandbox window. 62 BMC Impact Solutions Service Modeling and Publishing Guide . in the Component Type pane. Note that holding down the 1 key while dragging creates eleven copies of the component type. 2 Drag the component type from the Templates window to the View-Sandbox window. see “To specify component instance attributes” on page 63. The List and Large Icon layouts are sorted alphabetically (you can reverse the sort) and the Tree layout is in SIM class hierarchy order. Create multiple copies of the component type at one time by holding down a number key while dragging the component icon to the View window. to create eight copies of a component. For example. click Cancel and start again with step 2. If you chose the wrong component type. the component type you chose is selected by default. You can change the way the list of components are presented in the Templates window by clicking the appropriate icon for List. You can also open a new sandbox View at any time by clicking on the toolbar. Holding down the 0 key while dragging creates ten copies. hold the number 8 key while dragging the component icon. find the appropriate service component type (class) for the instance that you are creating in the Templates window. and Tree layouts. Where to go from here To enter values for component instance attributes other than component type.

or select the cell that will receive events for the component instance. and in the Contact box. such as a phone number or email address. 2 On the Status and Alias tab. perform the following steps: A In the Component Name box. see “In-model and notin-model component instances” on page 54. For more information about status computation models. B In the Cell box. D (optional) In the Owner section.” Chapter 4 Building a service model in BMC Impact Service Model Editor 63 . select Not In Model. perform the following steps: A In the Status Computation list. see the BMC Portal Getting Started guide for information about adding a cell. C (optional) In the Description box. but if the component instance is created outside of BMC Impact Service Model Editor or if the cell is deleted from BMC Impact Portal after it has been created but before it is published. To not include a component instance in the service model at the present time. see Chapter 5. select a status computation model. in the Name box. which is acceptable for most component instance definitions. accept the default.Creating service component instances in BMC Impact Service Model Editor To specify component instance attributes 1 On the General tab. choose Not In Model or In Model (default): s To include a component instance in the service model. The default selection is Standard. it cannot be published to the cell. data integrity errors may result. enter the name of the individual who is responsible for the component. select In Model. for the individual. it can be published to the cell. WARNING BMC Impact Service Model Editor verifies that the cell name chosen is present in the BMC Impact Portal. unassigned. s For more information about in-model and not-in-model. enter a contact method. enter a component description that is meaningful to your enterprise. BMC Impact Service Model Editor retrieves the list of cell names from the BMC Atrium CMDB. “Component and relationship status propagation. E In the Component Is area. replace the default name with a specific component instance name that is meaningful to your enterprise and that you want to use as the component’s label in a View. If the cell that you need is not listed.

see “Event associations” on page 38. — (optional) Enter additional aliases (one for each event that can potentially affect the status of the component instance) by clicking Add Alias. C In the Priority Propagation area. assign the proper permissions for this component instance to each of the roles listed. if more than one component instance has the same alias.Creating service component instances in BMC Impact Service Model Editor The default status for new component instances is OK. click Add Alias. 3 On the Permissions tab. enter relevant information about the component in the fields listed. B In the Aliases box. enter the alias and press Return or click OK. publishing fails. perform the following steps: A Assign the appropriate service schedules information to the components. 6 To save the component instance in the BMC Atrium CMDB (or save changes if you used the Templates window). For more information. — Enter the cost units per second for During Schedule Timeframes and Off Schedule Timeframes. 64 BMC Impact Solutions Service Modeling and Publishing Guide . 4 On the Schedule tab. — In the Alias box. click OK. B In the Time-variable Properties area — Choose a base priority for the components for During Schedule Timeframes and Off Schedule Timeframes. select s Yes to have the selected components propagate their self priority to their causal components s No (default) if self priority should not be propagated 5 (optional) On the Other tab. Each alias that you enter is listed in the Aliases box. see “Assigning components to service schedules” on page 99. Each component instance must have a unique alias. For information about aliases.

click the Display the properties window icon. On the toolbar. Switching sandbox View modes In the sandbox. Select the Properties dockable window. Components selected in either mode remain selected after you switch to the other mode. you can switch between a model-based view of components that displays the components in a hierarchical graph and a table-based view that displays the components in a table that includes properties.Switching sandbox View modes Where to go from here Continue creating component instances until you have a number of component instances that are related. You can switch View modes by clicking the appropriate toolbar icon. You can select columns (for this session only) by right-clicking any column heading and selecting Configure table columns. To learn more about working with component instances (viewing. deleting. Chapter 4 Building a service model in BMC Impact Service Model Editor 65 . Select a component instance and from the menu bar and choose Windows => Properties. right-click a component instance and select Properties. copying. Table 19 Icon View mode switch icons View mode Topology Component Table Viewing properties for a component instance You can view properties for a component instance. do one of the following: s s s s s In a View window. as shown in Table 19. and then see “Defining relationships between component instances” on page 78. continue with the next section. select a component instance or select a component instance and then click Properties on the Properties dockable window. Switch to Component Table mode . and in a View window. editing. and finding).

you should wait until the edit is complete before proceeding. except the component’s class. as in matching this component instance across datasets You can configure which component properties are displayed for a component in Component Table mode by right-clicking a table column heading and selecting Configure Table Columns. Though you are not locked-out of editing the component. by opening the Edit Component Properties dialog box.” Editing component instances You can change properties (attributes) for a component instance.) For more information about changing properties of a component instance. the name of the BMC Impact Manager to which the component is assigned. the properties shown for a component in Component Table mode include Table 20 Type Type Name Scope Cell Owner Name Company Status Model Priority . (Each section of data has its own Edit button. the name of the person responsible for the component. the name of the component. computer system. or test environment. such as application.Off Schedule Description Reconciliation Identity Default component properties Description the general component type. You can also change the values for a property from the Properties dockable window by clicking the appropriate Edit button. the name of the business associated with the component.Editing component instances By default. 66 BMC Impact Solutions Service Modeling and Publishing Guide . and database. sandbox. see “Editing component instances. status computation model description. The default sort order is by Name. whether the component is in a production. If the component is already being edited. a warning dialog is displayed. such as Standard the base priority of a component (1-5) in a During Schedule timeframe the base priority of a component (1-5) in an Off Schedule timeframe any special notes on the component ID used to reconcile this component.During Schedule Priority .

select the component instances. For example. or in a Table of Components view. Only the object type specific to a particular action is affected and the other type is ignored. select the component property to edit. see “To specify component instance attributes” on page 63.Performing actions on multiple objects To modify component instance properties 1 Either s s in the active View window. or delete multiple component instances). 2 Do one of the following to display the Edit Component Properties dialog: s s Right-click the component instance or property and choose Edit Component Properties from the context menu. 4 Click OK. selected relationships are ignored when you assign multiple objects to a cell. select the component instance to edit. 2 With the mouse pointer. For more information about the properties of components. Performing actions on multiple objects You can perform some actions on multiple objects at the same time (or example. or component instances and relationships. and do use of the following methods: s s On the toolbar. click the add-to-model or remove-from-model Right-click and choose Add to Model or Remove from Model. To select multiple objects 1 On the toolbar. Chapter 4 Building a service model in BMC Impact Service Model Editor 67 . you can add the same cell to several component instances. To change in-model or not-in-model setting quickly In an active View window. . From the menu bar. choose Edit => Edit Component Properties. click and drag to draw a box around all the objects that 3 Right-click and select the action that you want to perform. icon. 3 Make the appropriate changes. click Selection you want to select.

Performing actions on multiple objects To add or change the assigned cell NOTE As of version 7. Changes you make will apply to every component instance in the list. 68 BMC Impact Solutions Service Modeling and Publishing Guide . 2 Right-click and choose Assign Component to Cell. See “To select multiple objects” on page 67. 1 In an active View window. When a new CI is created using the Service Model Editor. make the necessary changes. To edit multiple component instances 1 Select the appropriate component instances. 4 When you have finished making changes. to discard the changes and exit. the Service Model Editor includes the concept of a default cell. If even one cell name is different. If even one component instance has a different value for a property. choose Edit => Edit Component Properties. the field is blank. click Cancel. 2 Take one of the following actions: s s Right-click the component instances and choose Edit Component Properties. the Cell box is blank. all component instances are updated with that cell. 3 Select a cell from the list. From the menu bar.00. making the following procedure optional.3. the cell name is displayed. you are not required to add the CI to a service model and then assign the CI to a cell. When you select a cell. to save and keep the dialog box open. click Apply. The objects you selected appear in the Component List box. 3 In the Edit Multiple Component Properties dialog box. click OK. take on of the following actions: s s s to save and exit. Consequently. the CI is automatically assigned to the default cell. select the component instances. If all the component instances have the same cell.

Chapter 4 Building a service model in BMC Impact Service Model Editor 69 . When this check box is selected. see “To set copy/paste and miscellaneous options” on page 154. When more than one component instance is selected for copying. in the Paste Multiple Components dialog box. 3 Right-click and choose Paste. To configure copy and paste options. Output Preview displays the name of one of the newly pasted component instances.Copying component instances Copying component instances You can copy one or more component instances and paste the copies into the sandbox View. the current option is used until you change it in the Options settings. 4 If you are copying more than one component. When pasting copies. select Do not show this dialog again. add a prefix or suffix to the original component name as needed and click OK. You can replace the default prefix or suffix by changing it in the Options settings. To prevent the Paste Components dialog box from prompting you at each paste. the name of only one of the selected component instances displays. A hidden component instance that has been published to a cell is not deleted from BMC Impact Service Model Editor and can be retrieved with the Find command. 2 Right-click and choose Copy. See “To select multiple objects” on page 67. Hiding a component instance You can hide a component instance so that it is not visible in the current active View or in all Views. Relationships are not copied unless they are also selected. you can automatically rename the pasted components by attaching a prefix or suffix to the original component name. To copy component instances 1 Select one or more component instances that you want to copy. The default prefix is Copy of. but you can specify a prefix by entering a new value in this box. See “To set copy/paste and miscellaneous options” on page 154.

2 To hide the component instances in the active View. Data in the component instance is not modified in any way. The selected component instances are removed from all Views and from the service model. they remain in the service model. NOTE If you want only to remove a component instance from your Views without deleting it permanently. If they are part of the service model. Choose Edit => Hide in All Views. but are still visible in other Views in which they have been saved. the component instance just does not appear in any of the current Views. Choose Edit => Hide in This View. take one of the following actions: s s Right-click and choose Hide in All Views. take one of the following actions: s s Right-click and choose Hide in This View. 3 To hide the component instances in all Views. The selected component instances are removed from the active View. Components that are new in the sandbox (that have no copy in BMC. Components in your sandbox that are marked as deleted appear in BMC Impact Service Model Editor with an “X” icon. Deleting a component instance When you delete a component instance in a View s s s Components in the BMC.ASSET yet) are hard-deleted from the sandbox.ASSET (in the BMC Atrium CMDB) that are marked as deleted (MarkAsDeleted) are not visible in BMC Impact Service Model Editor.Deleting a component instance To hide a component instance 1 Select the component instances to hide. I 70 BMC Impact Solutions Service Modeling and Publishing Guide . use the Hide in All Views command as described in “Hiding a component instance” on page 69.

3 Choose File => Promote All Sandbox Changes. Finding component instances You can search the BMC Atrium CMDB for existing component instances by using the Find command. Only component instances associated with classes that are designated for service impact management in the BMC Atrium CMDB can be found in the BMC Impact Service Model Editor.Finding component instances To delete a component instance 1 In a View window. Chapter 4 Building a service model in BMC Impact Service Model Editor 71 . 4 Review the Objects to be Promoted area to ensure that the component instances that you want to delete are listed. The deleted instances are removed from the service model. choose Edit => Delete from CMDB. from the menu bar. 2 Verify that you want to delete the component instances and click Yes. 5 Click Begin Promotion. they are no longer available in BMC Atrium CMDB. select the component instances you want to delete and take one of the following actions: s s Right-click the component instance and choose Delete from CMDB.

leave the Component Name box blank and click Find. their relationships are also placed in the View. or %Sales). click Find. 2 On the Find tab. 3 (optional) Save the search statement by clicking Add to Saved Finds and reuse it by clicking Open Saved Finds. From the dockable windows. Sales%.Finding component instances Figure 6 Find Component dialog box You cannot search for relationships with the Find command. To display a list of all component instances. %Sales%. or both (for example. in the Component Name box. after it. You can enter a partial name by using the % sign as a wildcard before the partial name. but when related component instances are found and placed in a View. click Find. From the menu bar. 72 BMC Impact Solutions Service Modeling and Publishing Guide . choose Window => Find. To find existing component instances 1 Launch the Find command by taking one of the following actions: s s s On the toolbar. enter the name of the component instance that you want to find.

Chapter 4 Building a service model in BMC Impact Service Model Editor 73 . To sort the values in any column. click Find. click the column heading. review the results of the search. drag the instances into the View window or select them and click Place in Selected View. select the appropriate attributes. 5 (optional) To define the attributes that are displayed in the results table and their order. click Open in New View. To place objects in the active View window. s To change the order of the columns in the final results display. The indicator disappears when the search is complete. a find-activity indicator spins next to the Find button. Sandbox and Production. 7 In the Results pane. the default sort order is creation date and time. if component name is one of the columns you choose to display. If component name is not chosen for display. The default sort order is by component name. While the search is in progress. select one of the instances and take any of the following actions: s s To place objects in a new View window. accept the default. For each user. drag the column headings. To change the order of the columns from left to right. or filter the list of component instances in the results pane by choosing Production Only or Test Only. s 6 To start the search. The attributes shown in the Available Attributes pane are s s listed in alphabetical order common to all component types In the Configure Find Results dialog box. the last-used settings are saved and reapplied at the next logon session. To move the attributes that you want to display into the Attributes to Show pane. use the up and down arrow buttons. right-click in any results-table column heading and select Configure table columns. You might see results before the search is complete. 8 (optional) In the results pane. use the left and right arrow buttons.Finding component instances 4 (optional) In the Look in area.

click Reset to clear all the selection criteria options on the Find tab to the default values (blank component name field. click Show Properties. All Components. For example. 9 (optional) To start another search. To shift the View focus so that you can see the existing object. If you select more than one component instance to move into view. if the object already exists in that View window. you can refine a search based on additional search criteria listed in Table 21 on page 75. Using the Advanced Find feature On the Advanced Find tab. click Go to Component. no results in table). s To view the characteristics of a selected component instance.Finding component instances When you move one instance into a View. the Duplicate Component dialog box opens. in Figure 7. the search will locate objects assigned to the specified cell with a publish date within the past year. Figure 7 Advanced Find dialog box 74 BMC Impact Solutions Service Modeling and Publishing Guide . the Go to Component button is not available.

Chapter 4 Building a service model in BMC Impact Service Model Editor 75 . Table 21 Look in Description of additional search criteria Options Sandbox and Production Selects based on components that are in either sandbox or production (promoted and published) Views components that have been promoted and published and are now in production components that have been assigned to a test cell any component type the specific component type selected from the list any service impact cell the specific cell name selected from the list the date range during which the component instance was last changed the date range during which the component instance was created the user ID who last changed the component instance properties Search criteria Production Only Test Only Component Type All list of component types (classes) Cell All Specific cell names Date Last Edited Date Last Created Date User Last Editor Creator the login ID of the user who created the component instance Using the Conditional Find feature With Conditional Find you can create a custom selection criteria phrase to select the component instances that cannot be located using Find or Advanced Find.Finding component instances Table 21 describes the additional search criteria available in Advanced Find.

(for example: [dcsrvstore2. NOTE When you search on the Aliases attribute. you must use LIKE as the relational operator.Finding component instances Figure 8 Using Conditional Find In the Query Builder area. dcsrvstore3. because if the component instance has more than one alias.cvom. 76 BMC Impact Solutions Service Modeling and Publishing Guide . the values are stored as a string. you define the attributes and specific values on which you want to base the search.com]).

If you have more than one selection criteria line. in the last list box for any selection criteria phrase. Table 22 = != < > <= >= LIKE Definition of relational operators Definition equal to not equal to less than greater than less than or equal to greater than or equal to similar to Relational operators 4 In the text box. you might need the beginning and ending parentheses to define precedence. select the beginning parenthesis. If the statement requires multiple selection criteria phrases. add lines as needed by clicking Add Line. select the ending parenthesis. it is displayed in the Query Display area. Or means either condition must be met for the component instance to be selected. The relational operator describes the relationship between the value in the attribute from step 2 and the value you specify in step 4. As you build the statement. select one from those defined in Table 22. in the first list box in Query Builder. 6 (optional) If needed. 3 In the relational operator list box. in the first list box on the subsequent line. select a component instance attribute.Finding component instances To build selection criteria phrases 1 (optional) If needed. select the appropriate Boolean operator: s s And means both conditions must be met. enter the specific value that must be contained in the attribute. 5 (optional) To create multiple selection criteria phrases. Chapter 4 Building a service model in BMC Impact Service Model Editor 77 . For example. you need the parentheses for a statement like (phrase1 OR phrase2) AND phrase3 2 In the Select list box.

click Find. An active relationship is an impact relationship and indicates that the status of the consumer instance depends on the status of the connected provider instance. 78 BMC Impact Solutions Service Modeling and Publishing Guide . Using “smart” select With “smart” select. Defining relationships between component instances Impact relationships define how status propagation is passed from the provider component instance to the consumer component instance. An inactive relationship means that no dependency exists or that the dependency is irrelevant to the model. The component instances which match the specified attributes are selected. click the Delete Line button that is directly under the line you want to delete. click Add to Saved Finds. you can choose to select only component instances in the current view which match the attributes you specify.Defining relationships between component instances 7 (optional) To delete lines. in either case. choose Edit=>Select. 8 To start the search. The smart select attributes include s s s s s s s In Model (any view) Out of Model (any view) New (sandbox view) Edited (sandbox view) Production Components (sandbox view) Components With No Cell (any view) Components With Cell but Out of Model (any view) To use smart select 1 With a View open. 2 Click on the appropriate attributes to select. an impact relationship does not exist. TIP To save the search statement for reusing later.

press Esc. the cursor changes to . test them to verify that they function in the way that you intended. TIP To delete a graphic line that you have started and do not want to complete. place them such that provider components are below consumer components. and then click again. For each component instance for which you are creating relationships. In draw mode. See “Associating events with a component instance” on page 86. 2 Draw a relationship line from provider to consumer by clicking at the top of the provider component and moving to the bottom of the consumer component. click . The default relationship direction is from provider to consumer. Creating a component relationship in BMC Impact Service Model Editor You can create consumer/provider relationships for components in BMC Impact Service Model Editor by s s drawing lines between components in the View window using the Create Relationship command TIP When you place components in a View. it is propagated to the connected consumer component instance. To create a relationship by using draw mode 1 In the View window. If necessary. you must know s s s whether it is a consumer or a provider for the related component its relationship state value (active or inactive) its status propagation model value (relationship policy) After you have created relationships. on the toolbar. Chapter 4 Building a service model in BMC Impact Service Model Editor 79 . you can change it to consumer to provider by clicking on the arrow next to the tool.Creating a component relationship in BMC Impact Service Model Editor Whenever the status of the provider instance changes.

click Create a new Relationship . 2 In the Create Relationship Properties dialog box. click Selection drew. To learn about creating relationships using the commands. and choose Create Relationship. take one of the following actions: s s s On the toolbar. choose Edit => Create Relationship. continue with the next section. From the menu bar. click Add. In a View window.Creating a component relationship in BMC Impact Service Model Editor 3 On the toolbar. To create relationships by using menu commands 1 In a View with component instances that need relationships defined. and right-click on the relationship line you just Where to go from here To specify other impact relationship attributes. see “To specify other impact relationship attributes” on page 82. in the Consumer List area. right-click on a component. 80 BMC Impact Solutions Service Modeling and Publishing Guide .

Creating a component relationship in BMC Impact Service Model Editor Figure 9 Create Relationship dialog box 3 In the Find window. see “Finding component instances” on page 71. You can add more than one component instance (using basic Windows selection) to either the Consumer List box or the Provider List box. you can add only one provider component instance. 4 In the Provider List area. 5 In the Find window. For information about the Find command. If there are multiple component instances in the Consumer List. locate the component instances that function as the consumer in an impact relationship. the one that is the provider for each of the component instances in the consumer list. Chapter 4 Building a service model in BMC Impact Service Model Editor 81 . click Add. locate and choose the component instance that functions as the provider in the impact relationship.

which is also taken into account. 3 In the Edit Relationship Properties dialog box. Decreasing—the status of the consumer component instance is less critical than that of the provider component instance by one level. the consumer status is MINOR. 82 BMC Impact Solutions Service Modeling and Publishing Guide . 2 Choose Edit Relationship Properties. Inactive—the status of the provider component instance is not propagated to the consumer component instance. click Swap List Contents.Creating a component relationship in BMC Impact Service Model Editor WARNING Avoid creating circular relationships in which an component instance can propagate events to itself. 4 In the Relationship Policy list. Publishing will fail if loops (circular relationships) are created within the service model. For example: instance 1 —> instance 2 —> instance 1 again. Increasing—the status of the consumer component instance becomes more critical than that of its provider component instance by one level. For example. NOTE BMC Impact Service Model Editor verifies that the impact relationship is associated with a valid status propagation model. the consumer status is INFO. select Active or Inactive. select one of the pre-defined status propagation models: s Direct—the status of the consumer component instance may be identical to that s s of its provider component instance. if the provider status is WARNING. depending on the events directly affecting the consumer’s status. 6 (optional) To switch the contents of the two lists (make the consumer the provider and vice versa). To specify other impact relationship attributes 1 On the toolbar. s Active—the status of the provider component instance is propagated to the s consumer component instance. For example. Where to go from here To specify other impact relationship attributes. select Selection and right-click on a relationship line. see “To specify other impact relationship attributes” on page 82. if the provider status is WARNING. for the Activity options.

Assigning related component instances to cells 5 In the Status Weight box. (Status weight is used in the WEIGHTED_CLUSTER status computation model. through BMC Topology Discovery. BMC Impact Service Model Editor displays an error message. 7 Click OK. for example. Chapter 4 Building a service model in BMC Impact Service Model Editor 83 . accept the default value or enter a number for the consumer object. BMC Impact Service Model Editor detects it. Figure 10 shows an example sandbox View after some relationships were created.) 6 (optional) In the Description box. enter an explanation of the relationship that is meaningful to your enterprise. WARNING If you attempt to create a relationship between two components that already have a relationship between them. you are ready to assign the related components to the specified cells. Figure 10 Drawing relationships Assigning related component instances to cells After you have grouped your related component instances of the service model and determined on which cells to publish them. Even if the original impact relationship was created outside of BMC Impact Service Model Editor.

in the Cell box. nor can you swap the consumer and provider nodes. select them in the View window. Where to go from here To continue with the creation of a service model. in the cells that share relationships. make entries in each mcell. From the menu bar. To learn about updating and deleting relationships. choose Edit => Edit Component Properties.dir file of cell should have entries identifying cells 1 and 3. and the mcell. 4. 3.Updating relationships First.dir file to identify the other related cells. 3. continue with the next section. and 5). 84 BMC Impact Solutions Service Modeling and Publishing Guide . 2. select the cell to which you want to publish the components. Updating relationships You can change the properties for an existing relationship. If you chose more than one component instance. For example. 3 To assign other related components to a different cell. you intend to publish different component instances of your model across five different cells (1. The mcell. The General tab of the Edit Component Properties dialog box displays the corresponding component type in the component type hierarchy. 5) share a relationship.dir file of cell 1 should have entries identifying cells 3 and 5. the Edit Multiple Component Properties dialog box is displayed. To assign related component instances to cells 1 In an active View window. The component instance name is displayed in the Component Name box. the mcell.dir file of cell 3 should have entries identifying cells 1 and 5. see “Associating events with a component instance” on page 86. identify the target cells that share component relationships. select one or more of the component instances and do one of the following: s s Right-click and choose Edit Component Properties. 2 In the Edit Component Properties dialog box (or Edit Multiple Component Properties dialog box). Next. but only three cells (1. but you cannot add or delete the consumer or provider instances. and repeat steps 1 and 2.

Deleting relationships To edit one or more impact relationships 1 In the View window. the box is blank the changes you make are applied to all relationships listed in the Edit Multiple Relationship Properties dialog box For more information about the properties. Deleting relationships When you delete a relationship. If more than one relationship was selected: s s for each of the boxes. Select one or more the relationship graph lines. If more than one relationship is selected. However. and click Edit. choose Edit => Edit Relationship Properties from the menu bar. see “To specify other impact relationship attributes” on page 82. if you activate the Show/Hide Deleted Components toggle button in the toolbar. though this option can be changed in the Personal Options dialog. values are filled in if they are the same for all relationships listed. set the focus on the Properties window. all are listed in the Edit Multiple Relationship Properties window. Relationship Policy. TIP You can select multiple components and multiple relationships and then open the Edit Relationship Properties dialog box. prior to promoting the change. the deleted relationship can be seen in the View if you re-expand the graph. Chapter 4 Building a service model in BMC Impact Service Model Editor 85 . The relationship is recorded as to be deleted in the user sandbox and it is immediately removed from the SME View. by default. right-click and choose Edit Relationship Properties. do one of the following: s s s Select one or more relationship graph lines. the component instances remain in the service model. rendered in red. 2 Enter a new value in the Activity. Relationships that are to be deleted are. Select one or more relationship graph lines and from the menu bar. Status Weight. if even one relationship has a different value in a property box. and/or Description boxes.

The constructed alias must match the value you entered in the Alias box on the Status and Alias tab in the Create (or Edit) Component Properties dialog box. If you submit a promotion while a previous promotion is being processed. the second promotion will not start until the second one is complete. the cell uses an alias association formula to construct an alias. choose Tools =>Alias Formulas. choose Edit => Delete from CMDB. For more information about event alias association. click Add. WARNING s Only one promotion can be processed at a time. To delete a relationship 1 In the View window. Event class definitions must be the same in all SIM cells. recompile the KB. 3 Select File=>Promote All Sandbox Changes to remove the relationship from the production model. all relationships referencing the component (provider and consumer) are automatically deleted to maintain the consistency of the service model. and then restart each cell. If this value does not exist. If you add custom event classes. Associating events with a component instance When an event is received by a cell. you must manually modify the KB of each cell. and click OK. 2 In the confirmation window. s To create an event alias association 1 From the menu bar. 86 BMC Impact Solutions Service Modeling and Publishing Guide . 2 In the Event Alias Associations dialog box. This section describes how to create the formula.Associating events with a component instance When a component is deleted. The list of existing alias event associations displays. its event alias slot is checked for a value. click in the column heading. To sort either column. select the relationship line that you want to delete and do one of the following: s s Right-click and choose Delete from CMDB. verify that you are deleting the intended object. From the menu bar. see “Event associations” on page 38.

enter a name for the event association. in the Event Class box. its event class has to match the event class or a subclass of the event class before the alias formula is even considered. BMC Impact Service Model Editor looks at the first available cell and uses its event classes in the list. select an event class from the list. Chapter 4 Building a service model in BMC Impact Service Model Editor 87 . in the Name box. Figure 11 Creating an alias association 4 In the Event Match Criteria area.Associating events with a component instance 3 In the Edit Event Alias Associations dialog box. choose attributes and enter values to refine which events (within the event class) will generate aliases. When an event comes in. 5 (optional) In the Match Attributes box.

88 BMC Impact Solutions Service Modeling and Publishing Guide .19. the search phrase would read: Hostname contains SALLOG and IP address equals 555. For example. Table 23 Conditional operators anything Description of conditional operators Description the attribute can contain any value and is not used as a selection criteria If every attribute listed has anything that means that every incoming event that belongs to the event class will pass through alias formula processing contains has prefix has suffix equals the characters you enter in the text box occur someplace in the value the value starts with the characters you enter in the text box the value ends with the characters you enter in the text box the value exactly matches the characters you enter in the text box If you use more than one attribute.22. and enter a value in the text box to further define the events that are used to generate aliases using this formula. in Figure 13 on page 89. as described in Table 23.105. Both conditions must be true for the event to be selected for alias processing. each condition must test true (the Boolean operator between the selection criteria phrases is AND) before the alias formula process is performed.Associating events with a component instance Figure 12 Defining the events to be processed by the alias formula For each attribute you choose. select one of the conditional operators.

and the preview area is updated to show the syntax of the formula as it currently exists. if you assign the mc_host slot in your formula the value mycomputer.abc. of the CI. TIP If your formula for a component instance (CI) contains the mc_host slot with a host name value. C To insert a function that defines the data type and an expression in the formula. the control shows the attribute name. When an attribute is selected. semi-colon. click the Attribute button. Text. You can check with your system administrator for the correct Domain Name System (DNS) resolution if the object represented by the component instance experiences host name resolution errors.Associating events with a component instance Figure 13 Example of match attributes 6 In the Alias Formula area. For a list of functions you can use. click on the Function button. see BMC Impact Solutions Knowledge Base Development Reference Guide. The attributes shown are those that belong to the event class you selected in the Event Definition area. the word Oracle). a period. Type the function and choose the data type. not the IP address. type the literal text that you want in the alias formula. click on the Text button. use the Attribute. In the text box. not the IP address.com. Literal text appears in the first part of the alias formula with data type definitions. For example. then the mc_host slot of the matching event definition should also contain the host name value. then the mc_host slot of the incoming event should contain the same host name value. Chapter 4 Building a service model in BMC Impact Service Model Editor 89 . B To insert literal text (for example. and Function buttons in any order and as many times as needed to build the formula: A To insert an attribute in the formula.

For details about each field. 4 In the Edit Event Alias Association dialog box.Associating events with a component instance D (optional) To change the order of the elements in the alias formula. continue with the next section. E (optional) To delete one of the elements in the alias formula. and adding an alias to a component instance. 2 In the Event Alias Associations dialog box. 7 When the alias formula is complete. see “To create an event alias association” starting with step 4 on page 87. select the part of the formula you want to delete and click the Delete button. see “Promoting the service model” on page 103. click OK. select an existing alias computing formula. 2 In the Event Alias Associations dialog box. To delete an event alias formula 1 Choose Tools =>Alias Formulas. 5 When your changes are complete. Where to go from here To continue with the creation of a service model. click Save. To learn about editing and deleting an event alias association. 3 Click Delete. select an existing alias computing formula. 90 BMC Impact Solutions Service Modeling and Publishing Guide . select the part of the formula you want to move and click the Move arrow button as appropriate. make changes as needed. 3 Click Edit. To edit an event alias formula 1 Choose Tools => Alias Formulas.

5 (optional) To edit an alias name. You must use LIKE as the relational operator. 7 Click OK. 3 In the Input box. TIP To search for the component instances that use a specific alias. 2 On the Status and Alias tab. select the alias and click Delete. click Add Alias. 4 (optional) Enter additional aliases (one for each event that can potentially affect the status of the component instance). If a schedule is not selected for a component. 6 (optional) To delete an alias. Chapter 4 Building a service model in BMC Impact Service Model Editor 91 . in the Aliases box. Edits on this tab are not saved to the BMC Atrium CMDB until you click OK. enter the alias name and click OK. Schedule information is stored in the BMC Atrium CMDB and can be viewed in BMC Impact Portal and BMC IX. Each alias you enter is listed in the Aliases box. use the Conditional Find tab in the Find dockable window. One of the attributes available in the Select list box is Aliases. select a component instance and either s s right-click the component instance and choose Edit Component Properties choose Edit => Edit Component Properties from the menu bar. Working with timeframes and service schedules You edit service schedules using the Schedules Editor function of BMC Impact Service Model Editor.Working with timeframes and service schedules To add an alias to a component instance 1 In an active View window. continue with the next section. select the alias and click Edit. Where to go from here To learn about creating service schedules and assigning components to service schedules. in the Aliases box. the component will have a default schedule of 24 x 7 x 365 (always in schedule).

If you are creating a new timeframe.Icons used in the service schedule and timeframes editors After service schedules are created. which lists the components and schedules currently associated with the timeframe.Components and Schedule dialog box. you can assign components to schedules in the Edit Component Properties dialog box as described in “Assigning components to service schedules” on page 99. and Service Managers user groups have access to the schedule editor. 92 BMC Impact Solutions Service Modeling and Publishing Guide . Icons used in the service schedule and timeframes editors Table 24 contains descriptions of the functions of icons used in the service schedule and timeframe editors. Opens the Timeframe . Service Administrators. Full Access. Table 24 Icon Service schedule and timeframes editors icons Function Edit the selected service schedule or timeframe Create a new service schedule or timeframe Copy of the selected service schedule or timeframe Show Usages of components assigned to the selected service schedule or timeframe. these lists will not contain any components or schedules. which can be created and edited using the Timeframe Edit dialog box of BMC Impact Service Model Editor as shown in Figure 14. Delete the selected service schedule or timeframe Working with timeframes Service schedules are built from timeframes.

Period when the timeframe begins and ends. If you are creating a new timeframe. which lists the components and schedules currently associated with the timeframe.Components and Schedule dialog box. and the duration of the timeframe. Start. and vice-versa. these lists will not contain any components or schedules. End. Changing the duration will change the value in the End field.Working with timeframes Figure 14 Timeframe Edit dialog box Table 25 provides descriptions of the fields in the Timeframe Edit dialog box. The individual time zone of each component’s BMC Impact Manager will be used in timeframe calculations. and Duration Chapter 4 Building a service model in BMC Impact Service Model Editor 93 . Table 25 Name Description Usages (button) Timeframe Edit field descriptions (part 1 of 2) Name of the timeframe Description of the timeframe Opens the Timeframe .

enter or modify the appropriate information in the fields available in the Timeframe Edit dialog box. modify the fields for the copied timeframe as appropriate. Changing the selection in the left side list changes the options available on the right side. 3 In the Timeframe Edit dialog box. Weekly. 3 Click the Copy icon. choose Tools => Edit Schedules. on the Timeframes tab. Optionally. “Timeframe Edit field descriptions. 2 In the Schedules Editor dialog box. “Timeframe Edit field descriptions. Monthly. 5 Click Save. select a timeframe to copy. To copy a timeframe 1 From the menu bar. 94 BMC Impact Solutions Service Modeling and Publishing Guide . For more information about the Timeframe Edit dialog box. choose Tools => Edit Schedules. 2 In the Schedules Editor dialog box. 4 Click Save to save the timeframe and make it available for use in the Schedules Editor. you can enter the number of recurrences for the timeframe. see Table 25. instead of choosing an end date.” on page 93. Recurrence pattern Range of recurrence Defines the starting and ending date range for the recurrence. The copied timeframe name is appended with the prefix “Copy of. you can select individual dates that are part of the timeframe by selecting Date List and choosing dates from the displayed calendar.” on page 93. click the New icon to create a new timeframe or click the Edit icon to edit an existing timeframe. 4 In the Timeframe Edit dialog box. and Yearly timeframe options. To create or edit a timeframe 1 From the menu bar. see Table 25.” For more information about the Timeframe Edit dialog box. on the Timeframes tab. Besides the Daily.Working with timeframes Table 25 Timeframe Edit field descriptions (part 2 of 2) Defines the frequency in which the timeframe recurs.

Chapter 4 Building a service model in BMC Impact Service Model Editor 95 . 3 Click the Show Usages icon. click Show Usages. select one or more timeframes from the list of timeframes. click the Components tab. 4 Click Close. 4 Click Delete. on the Timeframes tab of the Schedules Editor dialog box. click the Delete icon. 2 In the Schedules Editor dialog box. click the Schedules tab. 3 On the Schedules tab. select a timeframe. — To view service schedules containing the selected component. on the Timeframes tab. See “To list the service schedules and components that are associated with a timeframe” on page 95. 2 In the Schedules Editor dialog box.Components and Schedule dialog box is a list of the components and schedules currently associated with the timeframe.Working with service schedules To list the service schedules and components that are associated with a timeframe 1 From the menu bar. Working with service schedules You create and modify service schedules in the BMC Impact Service Model Editor Schedule Edit dialog box as shown Figure 15. In the Timeframe . To view the schedules that make use of a given timeframe. choose Tools => Edit Schedules. choose Tools => Edit Schedules. — To view components associated with the selected timeframe. To delete a timeframe 1 From the menu bar.

click the New icon to create a new service schedule or click the Edit icon to edit an existing service schedule. Table 26 Schedule Edit field descriptions Name of the service schedule being created or edited Description of the service schedule Opens the Schedules . on the Schedules tab.Components Assigned to this Schedule dialog box. enter or modify the appropriate information in the fields.Working with service schedules Figure 15 Schedule Edit dialog box To create or edit a service schedule 1 From the menu bar. Schedule name Description Usages (button) 96 BMC Impact Solutions Service Modeling and Publishing Guide . 2 In the Schedules Editor dialog box. 3 In the Schedules Edit dialog box. as shown in Table 26. which lists the components and component descriptions currently associated with the selected schedule. choose Tools => Edit Schedules.

Chapter 4 Building a service model in BMC Impact Service Model Editor 97 . Add or remove timeframes from the list by using the arrows between During Schedule Timeframes and Available Timeframes. select a service schedule from the list. 2 In the Schedules Editor dialog box. see Table 26. choose Tools => Edit Schedules. For more information about the Timeframe Edit dialog box. 3 Click the Copy icon. modify the fields for the copied service schedule as appropriate. dates. and recurrence periods of the selected timeframe. Available Timeframes. contains the timeframes during which the associated components are treated as Off Schedule even though the time exists within the During Schedule period.” on page 96. 4 Click Save. and what timeframes are available. the left panel. “Schedule Edit field descriptions. Any time period that is not part of a service schedule is considered Off Schedule. what timeframes are Exceptions Within During Schedule. contains the timeframes during which the associated components exists in the service schedule period (as opposed to being Off Schedule). To copy a service schedule 1 From the menu bar. the right panel. the center panel. Exceptions Within During Schedule. During Schedule Timeframes. on the Schedules tab. contains the timeframes that are available to be added to the During Schedule and Exceptions Within During Schedule periods. 5 Click Save. 4 In the Schedule Edit dialog box. Timeframes in this schedule Timeframe details Opens the Timeframe Details dialog box listing the times.Working with service schedules Table 26 Schedule Edit field descriptions Information on what timeframes are part of the service schedule.

4 Click Delete. 98 BMC Impact Solutions Service Modeling and Publishing Guide .Working with service schedules To display the component instances that are associated with a service schedule 1 From the menu bar. all components using the deleted schedules will be assigned to the current default schedule. 2 In the Schedules Editor dialog box. 3 Click the Show Usages icon. on the Schedules tab of the Schedules Editor dialog box. Where to go from here After you create service schedules. you assign components to the schedules. 2 In the Schedules Editor dialog box. on the Schedules tab. To view the component instances that are associated with a given service schedule. See “To display the component instances that are associated with a service schedule” on page 98. choose Tools => Edit Schedules. click Show Usages. See “Assigning components to service schedules” on page 99. select one or more service schedules from the list. select a service schedule from the list. 3 Click the Delete icon. To delete a service schedule 1 From the menu bar. informing you that after deletion. A Delete Confirmation dialog box is displayed. You can view associated components on the Components tab and associated service schedules on the Schedules tab. 4 Click Close.Components and Schedule dialog box is a list of the components and schedules currently associated with the timeframe. on the Schedules tab. choose Tools => Edit Schedules. In the Timeframe .

click Usages. 2 Choose Edit=>Edit Component Properties. 3 On the Schedule tab. click Select. as shown in Figure 16. components are assigned the always-in-During Service schedule (24 x 7 x 365). — To choose a schedule for the components. Schedule tab. select the schedule from the Schedules pane and click OK. — To edit an schedule. in the Schedule pane. By default. For more information about editing schedules see “To create or edit a service schedule” on page 96. select a schedule and click Edit to display the Schedules Editor.Assigning components to service schedules Assigning components to service schedules You can assign one or more components to service schedules by launching the Schedules Editor from the Edit Component Properties dialog box. Chapter 4 Building a service model in BMC Impact Service Model Editor 99 . click Timeframe Details. The Select a Schedule dialog box contains the During Schedule and Exceptions Within During Schedule timeframes. Figure 16 Schedules Editor section of Edit Component Properties dialog box To assign components to service schedules 1 Select one or more components in the active View to which you want to assign to a service schedule. — To view what component instances are using the selected schedule. — To view the details of what times and dates are specified in a selected timeframe.

Table 27 User role Service Administrators. Table 27 describes default BMC Impact Service Model Editor user groups and their corresponding rights. and under Tasks. Service Executives. open the Configure tab. To add users to these user groups. and under Tasks. select User Groups. Service Manager .Senior. and Service Manager.Senior Service Operators s Granting permissions to individual service model objects By default. go to the BMC Impact Portal. BMC Impact Service Model Editor user groups that have permissions to create and edit component and relationship instances are: Service Administrator. select Users. go to the BMC Impact Portal. see BMC Portal Getting Started. Granting access to service model objects You define and maintain BMC Impact Service Model Editor user groups and permissions in the BMC Impact Portal. For more information. To modify user group permissions. 100 BMC Impact Solutions Service Modeling and Publishing Guide . Service Managers . You can override these default permissions for individual component instances. open the Configure tab.Granting access to service model objects 4 Click OK.Senior Default user groups and rights for BMC Impact Service Model Editor Rights s s s s s s save View create/edit component and relationship instances publish service models view publication history reinitialize to a cell import and export service model data save View create/edit component and relationship instances view publication history read only Service Managers s s s Service Operators .

Chapter 4 Building a service model in BMC Impact Service Model Editor 101 . choose Edit => Edit Component Properties. 2 In the Edit Component Properties dialog box. 3 Click OK. they are effective immediately in BMC Impact Service Model Editor. they must be promoted from BMC Impact Service Model Editor and you must then log out and then log on to Impact Portal. For permissions at the CI (component) level. you need not log out and log into the Portal portal for the permissions to take effect. select the component and do one of the following: s s Right-click and choose Edit Component Properties From the menu bar. NOTE When you modify user access permissions in the BMC Impact Service Model Editor. on the Permissions tab.Granting permissions to individual service model objects To grant permissions to individual component instances 1 With the component instance in an open View. select the appropriate options. For the changes to appear in Impact Portal. Figure 17 Changing access for an individual component instance User groups with Unassigned selected do not see the object.

you need to verify that the association occurs correctly.Testing the service model Testing the service model Before promoting and publishing the components in your sandbox service model. and management data to a cell that has been previously created exclusively for testing by using the Send to Test option on the File menu. If the slots are empty. you may test them by sending the component instances and relationships to a test cell that you have previously created specifically for the purposes of testing. After the test is initiated. or if components exist which are not part of an impact relationship. 102 BMC Impact Solutions Service Modeling and Publishing Guide . you can send component. (if the relationship View option is set to show non-impact relationships. as well as those in the sandbox. check the component alias and the event alias formula. if no impact relationships are visible in the selected view. open the Events tab. In the BMC Impact Service Model Editor.) You can send the sandbox service model to a test cell before promoting it into the production environment. the Send to Test option is not available. a dialog box is displayed warning the user that the test components being sent do not have impact relationships Testing component relationships After you have set up a relationship. including production components. From the BMC Impact Service Model Editor. in the component instance and by creating an alias formula. When an incoming event is associated with a component instance. the mc_smc_type and mc_smc_id slots will have values. the following events occur: s s s existing data in the test environment is cleared components and relationships. Management data is also sent. the event is not associated. BMC Impact Service Model Editor users having the correct permissions (set up in the BMC Portal) have their own individual test environments. relationship. Testing event associations After you have set up event alias associations. you can test it by posting events against the provider component in the relationship and observe the resulting status of the consumer component in the relationship. are sent to the test environment. In the BMC Impact Explorer console.

s s In automated mode. while publication is controlled by BMC Impact Publishing Server. Choose Yes to continue. publication is initiated from CLI commands. In manual mode. If the send to test is successful. About the publishing process Promotion and publishing are decoupled. the BMC Impact Publishing Server updates the BMC.Promoting the service model To send components to a test cell 1 Choose File => Send to Test Objects in Current View. an error dialog box is displayed and the process is stopped.ASSET) in the BMC Atrium CMDB and are automatically published (by default) to the assigned cells. a warning dialog box is displayed. see Chapter 8.” Chapter 4 Building a service model in BMC Impact Service Model Editor 103 . by default.IMPACT. If there are no impact relationships for the components in the current View.PROD dataset. publication is initiated by the completion of a reconciliation job run. Promoting the service model After promoting component instances in BMC Impact Service Model Editor. Management data is copied automatically to the test environment. “Managing BMC Impact Publishing Server. For more details about automated publishing. Note that a successful promotion does not guarantee that the automated publication will also be successful. 2 Close the dialog box. a dialog box is displayed indicating that the test dataset has been populated. Promotion is initiated and controlled from BMC Impact Service Model Editor. these changes are stored in the production dataset (BMC. If there are no test cells available in the current environment. There are two modes of running the BMC Impact Publishing Server. which mirrors the last successful publish to the cells. When you service model data is successfully to the cells. or No to stop. such as after a promotion.

impact relationships.IMPACT. verify that: s s s s s s each component instance is assigned to a cell all target cells that are registered in the BMC Impact Portal are running and have a live connection with the BMC Impact Publishing Server event types are associated with component instances the BMC Impact Publishing Server is running in automated mode by using the CLI command psstat. Service Manager. 104 BMC Impact Solutions Service Modeling and Publishing Guide . your user account belongs to one of these user groups: Service Administrator. the BMC Atrium CMDB. you may change them in the BMC Impact Portal) the SIM class definitions are in sync.PROD and the changes between them are sent to the cell. the Promotion Preview dialog box offers the opportunity to compare your unpromoted sandbox service model component instances and relationships with those that have already been promoted so that you can verify the work done in the current editing session.Before you promote During the publishing of a service model. Before you promote To ensure a successful promotion and publication of the service model. or Service Manager . Before you begin Verify the items listed in the section “Before you promote” on page 104.ASSET dataset in the BMC Atrium CMDB and copied to respective BMC Impact Manager cells. BMC. and management data) shown in the preview are promoted (and subsequently automatically published). The objects in BMC. This command should return Started . service model objects (component instances. Submitting a promotion When you submit a promotion. you can monitor status changes using BMC Impact Explorer or BMC Portal for the published component instances. new or modified service model components and their relationships are selected from the BMC.PROD is then updated with the changes.IMPACT.ASSET are compared to any previously published instance in BMC. When you click Begin Promotion.Senior (these are the default user group assignments. After events that affect service component instances are received by the cell.Automated mode. and the cells before submitting the publication. The BMC Impact Publishing Server validates the class definitions and establishes a live connection with BMC Impact Portal.

The icons in the Action and Type columns are defined in Table 28. see BMC Portal Getting Started. choose All Actions. In the second Show list. you may not have the permissions to promote component instances. not what will be promoted. The icons in the Class column match the icons associated with the component type in the Templates dockable window. or Management Data. 2 In the Promotion Preview dialog box. then Type (component or relationship). Relationships. In a View window. or Deleted Objects. New Objects. The default sort order of objects is by Action. Changed Objects. TIP If promote service model options are unavailable. it only affects what is visible. in the Objects to be Promoted area. click in the column heading. From the menu bar. In the first Show list. and then by Object Name. right-click and choose Promote All Sandbox Changes. For information on configuring user rights. click Promote . review the list of objects. When you filter the list. choose how you want to filter the list of objects that you see. Components and Relationships. Components. Table 28 Action Icons in Objects-to-be-Published pane Icon Description object was deleted object was added object was modified Column heading Chapter 4 Building a service model in BMC Impact Service Model Editor 105 . To change the sort order.Submitting a promotion To promote all sandbox component instances and relationships 1 Start the promotion by doing one of the following: s s s On the toolbar. choose File => Promote All Sandbox Changes. choose All. 3 In the results pane. The component instances and relationships to be promoted are listed in the left pane. All items will be promoted.

select Changed Properties or All Properties for the component instances you selected in the Objects to be Promoted pane. s 6 Click Begin Promotion. click Exit SME. The Promotion in Progress dialog box is displayed. 7 (optional) To stop the promotion. 8 (optional) To exit BMC Impact Service Model Editor. in the Promotion in Progress dialog box. 9 A status message indicates the success or failure of the promotion request. compare the new and previously published property values to verify that the new data is correct before you publish it. 106 BMC Impact Solutions Service Modeling and Publishing Guide . along with the elapsed time since the promotion was started. click on the quick expansion arrows (tiny black arrows) between the panes. TIP s To hide either the Objects to be Promoted pane or the Comparison of New and Promoted Property Values pane. the promotion continues in the background. for the Show options. 5 Select one or more objects in the left pane and. changed. click Stop. the elapsed time will reflect the total time since the promotion was originally started. Closing the dialog box does not stop the promotion. You can compare published and newly created. Even if BMC Impact Service Model Editor is shut down and restarted. in the right pane. or deleted component instances independently of the publication process by choosing Tools => Compare Sandbox to Production. then click the appropriate selection on the confirmation dialog box.Submitting a promotion Table 28 Type Icons in Objects-to-be-Published pane Icon Description component relationship timeframe or service schedule Column heading 4 In the Comparison of Sandbox and Promoted Property Values area.

see “Initial source parameters” on page 208. a dialog box will display indicating whether the promotion succeeded or failed. but can be viewed in the Promote and Publish History dialog box (Tools => Promote and Publish History) or using the pshowlog command. Where to go from here To learn about verifying promotion status. Verifying promotion status After you submit a promotion request. the Promotion Status dialog box declares a promotion failure along with the error. a timestamp. For troubleshooting information. you can view its status in the Promotion in Progress dialog box that displays after a promotion is requested. Note that a publication success or failure is not shown in the dialog box. After the promotion process completes. Click OK to dismiss the dialog box. If the promotion fails. “BMC Impact Publishing Server CLIs”. continue with the next section. see Chapter 9. Chapter 4 Building a service model in BMC Impact Service Model Editor 107 . the service model is available to the specified cells and you can monitor the component instances in BMC Impact Portal and in BMC Impact Explorer.Verifying promotion status If the promotion and subsequent automated publication processes are successful. and the user name of the submitter. For more information about CLI commands.

BMC Atrium CMDB. It is recommended that you give every promotion a unique description because promotion descriptions are found in the publication log and will make locating each publish easier. select the Promotion tab. 2 To view promotion details. the Promotion in Progress dialog box opens automatically. and BMC Impact Managers) it communicates with. More detailed information about each publication is available in BMC Impact Publishing Server log files. Another way to find the correct publication in the log is to use the promotion id. BMC Impact Publishing Server includes detailed messages from the different components (such as BMC Impact Portal. Viewing promotion and publication history At any time. then select the promotion for which you want to see details in the Promote History table area. consult the documentation of those components. enabling you to monitor the progress of the promotion request. including failures. choose Tools => Promote and Publish History. A log exists for every publish request containing detailed information as to why publication failed and can be consulted to diagnose a publication failure. Information in the Publication errors section of the Publish tab can help you troubleshoot publication failures. Publish logs can be retrieved in user-friendly format via the CLI command pshowlog (see “pshowlog—Obtaining the XML log in user-friendly format” on page 281). To view promotion history 1 From the menu bar. All publish logs are available in BMC Impact Service Model Editor's publish history. promotion results dialogs only report success or failure of a promotion and do not offer information about publication status. Publish logs can also be retrieved via the CLI command plog (see “plog— Obtaining the XML log for a request” on page 265). The Promote and Publish History command displays the status and date and time of requests. you can use the Promote and Publish History command in BMC Impact Service Model Editor to review previous promotion and publication information. 108 BMC Impact Solutions Service Modeling and Publishing Guide . To understand and troubleshoot these messages. However.Working with publication logs Working with publication logs This section contains general guidelines to remember when working with publication logs. s s s s s s After you submit a promotion request.

conf to modify the default number of logs saved. but also classinfo (for example. that is. Failures are displayed in red. choose Tools => Promote and Publish History. the first log is deleted. review the failure information. To view publication history 1 From the menu bar. the component type and component name are included. 100 publication log files are saved. You can sort on any column and. select the Publish tab. the most recent is listed first. B On the Publication Errors tab (available only if there were failures associated with the selected publication). that is. export) requests). choose Tools => Promote and Publish History. then select the publication for which you want to see details in the Publication History table area. By default. To open a View with the component instance. the tooltip displays the complete text string. when the 101st log is saved. if the column width limit truncates the text. Viewing publication history details This section contains information on viewing publication history details. that is. To view publication history details 1 From the menu bar. If the failure is the result of a particular component instance. 2 To view publication details. review the detailed information for the publication you selected. The list of recent publications is in reverse chronological order. 2 To view publication details. then select the publication for which you want to see details in the Publication History table area. the most recent is listed first. the most recent is listed first.Working with publication logs The list of recent promotions is in reverse chronological order. All BMC Impact Publishing Server requests are counted (not only publish and initialization. The list of recent publications is in reverse chronological order. select the Publication tab. select the failure and click Open in New View. A On the Publication Details tab. You can change the RequestHistorySize parameter in pserver. Chapter 4 Building a service model in BMC Impact Service Model Editor 109 .

Modifying and deleting service model data For published service model data. Objects delivered to the SIM cell from BMC Atrium CMDB must be edited and deleted in BMC Impact Service Model Editor (or BMC Atrium CMDB) and objects from the CLI command pposter must be changed and deleted using a BAROC source file and pposter. or modify it by editing the pslog_error_solutions. Published data is protected from modification or deletion by any form of Direct Feed. review the action to correct the problem with publish. nor with a rule. while published components are visible in BMC Impact Explorer. click Close. you must populate the console navigation tree in BMC Impact Service Model Editor. 3 To close the dialog box.properties file located in the BMC_PORTAL_KIT_HOME\appserver\websdk\tools\jboss\server\all\conf\resourc es\en_US\smsConsoleServer directory on the server running BMC Portal. this fails because the DirectPublish environment is not the source of the CI. In other words. 110 BMC Impact Solutions Service Modeling and Publishing Guide . or the mposter command. NOTE You can replace the action recommended by BMC Software. then the DirectPublish CI is replaced by a BMC Atrium CMDB CI.Modifying and deleting service model data C In the Recommended Action area. you cannot change or delete them in BMC Impact Explorer. changes and deletions are restricted to the original source of the data. Organizing service component instances for monitoring Before you can monitor service model component instances that are in production (have been published) in the BMC Impact Portal and the BMC Impact Explorer. add to it. If you first create a CI via a pposter and later publish that CI (same ComponentAlias) from BMC Atrium CMDB. If you first create a CI from publish from BMC Atrium CMDB then try to modify it via pposter.

The way you organize the folders and component instances is entirely dependent on your enterprise and the way you want to monitor the component instances in BMC Impact Portal and BMC Impact Explorer. enter the folder name. 5 Click OK. on the Configure tab. 4 Specify the permission levels for the appropriate user groups. To add a folder to the console navigation tree 1 In the Console Navigation Tree dockable window. NOTE You can rename group folders. click Create Folder . You create subfolders that meet the service monitoring requirements for your enterprise.Organizing service component instances for monitoring The Console Navigation Tree dockable window provides a flexible way of organizing your service component instances under folders that you create. with userAccount representing the active BMC Impact Portal user account name. navigate to and select the folder under which you want to create a folders. The top-level folder of the hierarchical directory is userAccount/Business. expand the Business folder under the userAccount folder. These permissions settings enable users to see the folder and its contents in BMC Impact Portal and BMC Impact Explorer. under Properties and in BMC Impact Explorer. 3 In the Create New Folder dialog box. All service component folders must be created under the userAccount/Business folder (which cannot be edited or renamed). the Services Group tab. you can rename them in a View. 2 In the Console Navigation Tree toolbar. Changes that are made to published service model component instances in the console navigation tree are immediately reflected in the BMC Impact Portal. from the Services View. but you cannot rename component instances from the console navigation tree. in the text box. The tree that you create in BMC Impact Service Model Editor is visible in BMC Impact Portal. To rename folders 1 In the Console Navigation Tree dockable window. 2 Select the folder you want to rename. Chapter 4 Building a service model in BMC Impact Service Model Editor 111 .

click Edit Permissions user groups. 3 In the Edit Permissions dialog box. 2 Select the folder or component instance that you want to copy to another folder. . specify the permission level for the appropriate 4 Click OK. 2 Select the folder or component instance that you want to move to another folder. expand the Business folder under the userAccount folder. 112 BMC Impact Solutions Service Modeling and Publishing Guide . NOTE Folder-level permission for the BMC Impact Service Model Editor is controlled by the BMC Portal. expand the Business folder under the userAccount folder. Components which appear as providers to other component instances in the console navigation tree cannot be moved (that would be editing the model). 5 Click OK. 3 Drag the object to the new location. 2 On the Console Navigation Tree toolbar. enter the new name. 1 In the Console Navigation Tree dockable window. To copy folders 1 In the Console Navigation Tree dockable window. 3 Control-drag the object to the new location. To move a folder and its component instances . click Rename Selected Folder 4 In the Rename Folder dialog box. This means that if you create a folder in the BMC Impact Service Model Editor and assign specific access control permissions to that folder. You can only move those component instances which exist directly under a folder.Organizing service component instances for monitoring 3 On the Console Navigation Tree toolbar. the access control permissions from the BMC Portal override the permissions of the BMC Impact Service Model Editor. navigate to and select the folder for which you want to define permissions. To define permissions for folders 1 In the Console Navigation Tree dockable window.

s Chapter 4 Building a service model in BMC Impact Service Model Editor 113 . you must publish them. and if there are changes. locate and select the components to add and click Add. NOTE s When you add a component instance that has providers to a folder. click Yes. 3 On the Console Navigation Tree toolbar. To add a component to the console navigation tree 1 In the Console Navigation Tree dockable window. 2 On the Console Navigation Tree toolbar. see “Finding component instances” on page 71. BMC Impact Service Model Editor checks the BMC Atrium CMDB to see if there are changes to provider component instances. the tree is refreshed. For information on using the Find command. the component instances are automatically saved as part of the console navigation tree. These provider component instances are not saved as part of the console navigation tree. 2 Select the folder you want to remove. click Add a Component . expand the Business folder under the userAccount folder. even if they are not published. 3 In the Find window. When you expand the tree. either click Remove Folders or components or right-click and choose Remove from the context menu. When you click Add.Organizing service component instances for monitoring To remove a folder or a component 1 In the Console Navigation Tree dockable window. you can drill down and see the providers in the console navigation tree. 4 (optional) Continue adding component instances using the Find command. To see component instances in the BMC Impact Portal that you see in the console navigation tree. navigate to and select the folder under which you want to add component instances. 4 In the Confirmation box. You can also undock the Find window and drag component instances from the Find results pane to the console navigation tree.

2 Locate the component instances you want to open in a View. To open component instances in a View 1 In the Console Navigation Tree dockable window. on the toolbar. Working with BMC Impact Service Model Editor Views Table 29 lists the topics covered in this section with page numbers. To refresh the tree To query the BMC Atrium CMDB and redisplay the tree with the latest data. 2 In an open View. You cannot move a folder into a View. s Right-click on the component instances and choose Open in New View or Place in Selected View. navigate to and select the folder under which you want to add component instances. on the Console Navigation Tree toolbar.Working with BMC Impact Service Model Editor Views To add a component to the console navigation tree from a View 1 In the Console Navigation Tree dockable window. including provider component instances. on the Console Navigation Tree toolbar. choose Edit => Add Components to Navigation Tree. click Place the selected components in current view . 114 BMC Impact Solutions Service Modeling and Publishing Guide . select the component instances to add and do one of the following: s s Right-click and choose Add Components to Navigation Tree. click Open the selected components in a new view . On the menu bar. expand the Business folder under the userAccount folder. s To open in the current View. click Refresh navigation tree. 3 Select the component instances and do one of the following: s To open in a new View.

and deleting Views Table 29 Topic Topics covered in this section Page Number 115 116 116 116 117 118 118 120 121 122 122 “To save a View” “To open a saved View” “To rename a View” “To delete a View” “Understanding visual cues in a View” “Repositioning objects in a View” “Controlling what you see in a View” “Exploring consumer and provider paths” “Refreshing the View” “Repositioning the dockable windows” “Showing topology views” Saving. renaming. whether it exists in a sandbox environment. renaming. opening. test environment. It may or may not encompass the entire service model. 3 Click OK. Each View is unique to a user account. 2 In the View Name box. or the production environment. choose File => Save View. To save a View 1 In an open. The name of a saved View displays in the title bar of the View. Chapter 4 Building a service model in BMC Impact Service Model Editor 115 . Each user can create and save multiple Views and multiple users can have many different Views into the same service model. opening. and deleting Views A View is a window into the service model. enter a unique name for the View.Saving. active View. depending on the size of the service model and how the View is set up.

Depending on the number of objects contained in the View. NOTE When you delete a View. If any instance cannot be verified in the BMC Atrium CMDB. Right-click and choose Rename View. Select the View and click on the View toolbar.Saving. 116 BMC Impact Solutions Service Modeling and Publishing Guide . verify that you are deleting the correct View and click Yes. and deleting Views To open a saved View 1 In the dockable panes area. To rename a View 1 In the dockable panes area. opening. Right-click and choose Open View. 2 In the list of Views. its component and relationship instances are verified against the definitions in the BMC Atrium CMDB. click Views. 3 The selected row becomes editable. 2 In the list of Views. click Views. renaming. 3 In the Confirm View Delete box. 2 In the list of Views. not any of the actual component or relationship instances in the BMC Atrium CMDB. locate the View you want to open and do one of the following: s s s Double-click on the View name. it does not affect the service model or the topology view. type a new name and press Enter. When you open a saved View. locate the View you want to delete and do one of the following: s s Select the View and click on the View toolbar. You are deleting only the View window. To delete a View 1 In the dockable panes area. Right-click and choose Delete View. this process can take some time. click Views. the View does not open. locate the View you want to rename and do one of the following: s s Select the View and click on the View toolbar.

Table 30 Visual cue Visual cues in a View Icon Description a component instance that is set to In Model displays the In model Component icon a component instance that is set to Not in Model displays the Not in Model Component icon a component instance that has been edited is flagged with this icon in the top right corner a newly-created component instance is flagged with this icon in the top right corner a component that is set to be deleted becomes semitransparent and is flagged with this icon in the top right corner outline a component instance showing the mouseover effect that results as you drag the mouse cursor over the icon solid background a selected component instance has a solid background and can be moved. Table 30 contains visual cues for components in the View. viewed. border. you have the option of defining colors for background. Additionally.Understanding visual cues in a View Understanding visual cues in a View BMC Impact Service Model Editor is a graphically rich interface. The component types are depicted as unique icons in the Templates dockable window. and edited Chapter 4 Building a service model in BMC Impact Service Model Editor 117 . line styles. The definitions for the icons in Table 30 can be viewed in the Legend. available by choosing Window => Legend.

To select multiple objects as a group. Table 31 Goal automatically align objects Adjusting the graphical view Action s s Toolbar button on the toolbar. ensure that the mouse cursor is in selection mode box around the appropriate objects. To reposition objects manually 1 In an active View. choose a value in the percentage list or from the menu bar. To layout the objects automatically. You can also manually move single or multiple objects in a View as described below. draw a 3 Drag the object to the desired position. click Fit to View or from the menu bar. click objects as needed. choose View => Zoom => value fit all objects in the View window adjust the zoom factor s s s s 118 BMC Impact Solutions Service Modeling and Publishing Guide . click on the toolbar and move s on the toolbar. click Auto-Layout or from the menu bar. . 2 Select an object or multiple objects. To explore a service model you need to know how to s s s adjust the graphical view use pan and zoom to focus on specific areas of the model exploring consumer and provider paths Table 31 describes each method of adjusting the graphical view. choose View => Fit to View on the toolbar. Controlling what you see in a View A service model may become quite large and not be entirely visible in the View window.Repositioning objects in a View Repositioning objects in a View You can move objects in a View using a variety of methods: s To quickly move all the objects in a View. choose View => Layout Objects on the toolbar.

or right-click an area of the model to magnify that area. drag the panner. 2 Capture the service model view in a outlined rectangle (panner) by using one of the following methods: s s From the menu bar. choose View => Zoom In or View => Zoom Out Zoom In grab and move objects magnify an area of the model see “To use the pan and zoom tool” on page 119. 4 (optional) To resize or reposition the window. 3 (optional) To zoom in. Click the Pan and Zoom dockable window. position the cursor over a corner of the panner and reduce the size of the panner. choose Window => Pan and Zoom. 5 (optional) Set the zoom percentage by adjusting the slider bar at the bottom of the Pan and Zoom window. Chapter 4 Building a service model in BMC Impact Service Model Editor 119 . s s click the magnifier icon to turn on magnifier mode left. click the topology view icon to turn on the topology view click the Component Table View icon to turn on the component table view click the Show Deleted Components icon click the Show Modifier Icons icon view the component objects in a topology view view the component objects in component table show or hide deleted components show or hide modifier icons for each component s s s s To use the pan and zoom tool 1 Open a View window. The actions you take in the Pan and Zoom dockable window with the panner rectangle are mirrored on the service model in the View window. To zoom out.Controlling what you see in a View Table 31 Goal Adjusting the graphical view Action s s Toolbar button zoom in or out in predefined percentage intervals Zoom Out on the toolbar. click Zoom Out or Zoom In or from the menu bar. increase the size of the panner.

3 To explore the provider paths. When you click on a + expansion handle. If the component renditions indicate other providers in the chain. 2 To explore the consumer paths. 120 BMC Impact Solutions Service Modeling and Publishing Guide . consumer objects are arranged above and providers are arranged below a specific node. The graph line that connects providers to consumers begins at the expansion handle atop the provider object and connects to the expansion handle at the bottom of the consumer object. By default. ensure that the cursor is in selection mode.Exploring consumer and provider paths Exploring consumer and provider paths The relationships between consumers and providers are depicted with lines between the objects. click the collapsed expansion handle at the top of the component instance you want to explore. you can continue clicking the expansion handles until you reach the last provider node (identifiable because it has no expansion handle). the server is always queried and an up-todate list of consumers or providers is displayed. click the collapsed expansion handle at the bottom of the node. To explore consumer and provider paths 1 In an active View window.

click Refresh . click on the expansion handle. A component instance with two consumer or provider expansion handles indicates that there are other related component instances that are not displayed. Computer System 3. From the menu bar. To refresh the list of component types.symbol above Computer System 3 collapses all of its consumers. do one of the following: s s On the toolbar. as shown. clicking on the expansion handle for Database 1 displays all its providers. To see the consumer (top +) or provider (bottom +) component instances. Clicking the . choose View => Refresh. from the menu bar. as shown. choose Tools => Refresh Component Types. Chapter 4 Building a service model in BMC Impact Service Model Editor 121 . in this case. Clicking on the + symbol above Computer System 3 results in the display of all consumer component instances. Computer System 3 has additional consumers as indicated by the extra + symbol at the top of the component instance icon. For example.Refreshing the View Table 32 Understanding expansion handles A component instance with expansion handles at the top and/or bottom functions as a consumer and/or provider in an impact relationship. Refreshing the View To validate the current component instances against their current class definitions in the BMC Atrium CMDB.

Find. from the menu bar. or Console Navigation Bar windows. choose View. Properties. Showing topology views There are many configuration items in the BMC Atrium CMDB that do not have consumer/provider relationships and are not appropriate for service impact management. To redock an undocked window. See “To define line styles for relationships” on page 153. Pan and Zoom. If non-impact relationships exist between such component instances in your active View. 122 BMC Impact Solutions Service Modeling and Publishing Guide . you can see this topology for the entire View.Repositioning the dockable windows Repositioning the dockable windows To undock and move the Templates. open the Relationship Legend box by choosing Window => Legend. Views. Right-click in the title bar and choose Close. and then choose one of the following: s s s Impact Relationships Non-impact Relationships All Relationships TIP You can redefine the line style for each type of relationship by selecting Tools => Options. do one of the following: s s Click the X in the top right corner of the undocked window. Right-click on the bar and choose Undock. choose another relationship type to view its topology. 2 (optional) In the same View. To show topology 1 In an active View window. 3 (optional) To see a legend of line styles. do one of the following: s s Select one of the bars and drag it into the right pane of BMC Impact Service Model Editor.

choose the directory where you want to save the file. verify the name of the file. choose File => Import. verify that the path is correct. 6 (optional) Close the dialog.ASSET ServiceModelSet = IN You cannot select a subset of this data for export. The data is exported as a series of files in XML format to a user-specified directory. 5 A dialog displays informing you that the import is in progress. choose File => Export. locate the folder and select the file you want to import. 3 In the File Name box. NOTE In the Files of type box. The import process will continue in the background. Chapter 4 Building a service model in BMC Impact Service Model Editor 123 .Exporting and importing service model data Exporting and importing service model data You can export component instance definitions between different BMC Atrium CMDB datasets only if they contain the following values: s s DatasetId = BMC. You can import specified component instance definitions in XML format from another BMC Atrium CMDB dataset. A notification will display when the import process is complete. 4 Click Import. the files must be saved in XML format. To import service model data 1 From the menu bar. 2 In the Look in box. To export service model data 1 From the menu bar. do not change the file type. 2 In the Look in box. 4 Click Export. 3 In the Directory Name box.

Exporting class definitions from the BMC Atrium CMDB to a cells 7 To update the current View with the most recent data from the BMC Atrium CMDB. BMC Impact Service Model Editor sends the export request to the BMC Impact Publishing Server. See “Finding component instances” on page 71.baroc. 8 To search for the new data. The BMC Impact Publishing Server sends this file to BMC Impact Service Model Editor and you can save it to a location you specify. the BMC Impact Publishing Server creates a BAROC-formatted class definition file (mc_sm_object. Next. 124 BMC Impact Solutions Service Modeling and Publishing Guide . For more information on pclassinfo usage. open the Find dockable window. click Refresh . see “pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB” on page 249. which collects the entire hierarchy of component and relationship class definitions from the BMC Atrium CMDB. Alternatively you can export the class definitions with the CLI command pclassinfo -x -o mc_sm_object. Then you must manually copy the file to the appropriate directory of the destination cell and recompile the Knowledge Base of the cell.baroc file) of the component and relationship class definitions so that the BMC Impact Manager cell can interpret the contents of the file. Exporting class definitions from the BMC Atrium CMDB to a cells The Export Cell Meta Data command enables you to synchronize the class definitions in the BMC Impact Manager knowledge bases in the target cells with those from the BMC Atrium CMDB. on the toolbar.

. . Anatomy of a status computation model. . . . . . . . . . . . . . . . . . . . . . Quorum algorithm examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5 Component and relationship status propagation 125 . . . . . The internal status NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self priority . . . . . . . . . . . . . . . How component status computation works . Default status propagation models. . . . . . . . . . . . . Status propagation models. . . . . . . . . . . . . . or by both. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic prioritization . . . . . . . . . . . . . . . . . . . . . . . . . About status computation models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status computation models calculate the new value of component status using these factors. . . . . . . . . . . . . . . . . Determination of final priority . . . . . . . . . . . . . . . . . . . Anatomy of a status computation model. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 5 125 126 128 129 129 129 130 128 130 132 132 133 133 135 136 137 146 147 Component and relationship status propagation 5 This chapter contains the following topics: About component and relationship status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How status computation algorithms work . . . . . . . . Quorum algorithm examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relationship status propagation concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About component and relationship status The status of a component can be influenced directly by the severities of its associated events. . . . . . . . . . . . . . . . . indirectly by the propagated status of its provider components. . . . . . . . . . . . . . . . . . . . . . . What is a valid status propagation model? . . . . . . . . . . . . . Impacts priority . . . . . . . . . . . . . . . How status propagation works . . . . . . . . . . . . . . . . . . . . . . . . . .

Then. The BMC_STATUS_COMPUTATION data class is the basis of all status computation model instances. The service model provides status computation models to support the definition of key component classes. the cell calculates the new component status. their inputs. 126 BMC Impact Solutions Service Modeling and Publishing Guide . Status computation functions The following functions perform status computation: s s s impact_function self_function consolidate_function Table 33 lists the functions. Based on the type of condition that triggered the status computation. such as the reception of a direct impact event. The cell obtains the name of the status computation model to use from the instance’s StatusComputationModel slot. and the type of computed status that each function calculates. To compute component status. the cell selects the appropriate function to use from the status computation model. the cell uses the status computation model assigned to a component instance. enabling the cell to handle status computation appropriately for those objects. It also obtains the algorithm to use with the function to calculate the appropriate status for the component. a status change on a provider component that results in a state change on an inbound relationship.How component status computation works A status computation model’s primary role is to associate an algorithm with each of the status computation functions. The model can be applied to one or more component instances. How component status computation works The cell computes component status automatically as new conditions occur.

in which case. Defining a status computation model includes associating the appropriate algorithm with each function. Status computation algorithms The status computation algorithms define the functions involved in status computation use the cell’s internal algorithms. impact_function returns the average status of the propagated status values. In general. or from the no_alert_status of the status computation model Inputs Output status values propagated by impact_status inbound relationships severities of direct events associated with the component the impact status and the self-status self_status impact_function self_function consolidate_function computed_status All the functions return a status value in the range of the MC_SM_COMPONENT_STATUS enumeration. The algorithms are: Highest Val—Using this algorithm. the less desirable it becomes. a function returns the highest value among those it receives as input. such as HIGHEST_VAL. the higher the value. the highest value for the status of a component is 70 (UNAVAILABLE). Component status is not reflected in the BMC Atrium CMDB. The component instance’s status is set to the computed_status except when you set the component to manual status. or both. The number of active relationships that constitute a quorum correspond to the quorum value of the status model multiplied by the total number of incoming active relationships divided by 100 (rounded up to the next integer if necessary).Status computation algorithms Table 33 Function Status computation functions and computed component statuses Description computes the impact status from status propagated by provider components computes the self_status from direct events computes the component’s computed_status from impact_status and self_status. Chapter 5 Component and relationship status propagation 127 . the component instance’s status is set to manual_status. Average—(impact_function only) Using this algorithm. Only the cell maintains the real-time status of components. Quorum—(impact_function) This impact_function returns the smaller status value among the highest values propagated by a quorum of incoming active relationships. For example.

Table 34 Function self_function What a function returns when using an available algorithm Algorithm HIGHEST_VAL Returns the highest value among the severities of the direct events. 128 BMC Impact Solutions Service Modeling and Publishing Guide . Weighted Cluster. In this case. Standard is the default status computation model. impact_function HIGHEST_VAL AVERAGE QUORUM consolidate_function HIGHEST_VAL SELF_PREFERRED About status computation models In the BMC Impact Service Model Editor product and in the BMC Impact Explorer product. It is used in impact relationships to determine how much importance (numerically weighted) to give to each provider relationship that impacts a consumer instance. for each component instance. after they have been automatically mapped to component status values the highest value among the status values of the provider components the average status of the provider components after weighting each status value. you select one of the predefined status computation models: Standard. How status computation algorithms work Table 34 shows the type of value that a component status computation function returns when using an available algorithm. Self-Preferred—(consolidate_function) computed_status is set to the self_status value except when the self_status is NONE. the computed_status is set to the no_alert_status value of the status computation model (by default OK). Cluster. requiring an integer value. where the “weight” is the number of providers propagating this particular status divided by the total number of providers propagating a status the computed impact status is the lowest status that is propagated by the quorum percentage of providers (ignoring relationships propagating NONE) the higher value between the impact status and the self-status the self_status value except when the self_status is NONE. A higher numerical value indicates a greater importance.How status computation algorithms work Weighted—Status weight is an attribute (StatusWeight) of the BMC_Impact object. and Self-Preferred.

Chapter 5 Component and relationship status propagation 129 . the following results apply to situations in which there is no input to a function or the input value is NONE. The main status of a component should never have a value of NONE. the greater the importance.Anatomy of a status computation model Table 35 Standard Description of predefined status computation models Description computes the status of a component using the HIGHEST_VAL impact_function. For this reason. a quorum percentage that applies only when the impact_function uses the QUORUM algorithm an external algorithm that applies only when the impact_function uses the EXTERNAL placeholder The internal status NONE The status value NONE is an internal status only used in the component status computation function. Anatomy of a status computation model A status computation model defines the following: s s s s the algorithm used by each of the functions involved in status computation a no-alert status value that applies only when the consolidate_function returns NONE. Status computation model Cluster Weighted Cluster Self-Preferred computes the status of a component using the self-preferred algorithm for the consolidation_function The BMC_STATUS_COMPUTATION data class is the basis of all status computation model instances. The higher the number. the impact_status is the highest propagated_status of the incoming relationships computes the status of a component using the QUORUM impact function (see “Quorum algorithm examples” on page 130) computes the status of a component using the Status Weight attribute of the BMC_Impact object Status Weight is used in impact relationships to determine how much importance (numerically weighted) to give to each provider relationship that impacts a consumer instance. The no-alert status is acceptable for all the default status computation functions. see “BMC_STATUS_COMPUTATION data class” on page 317. For a description of BMC_STATUS_COMPUTATION slots.

called the quorum percentage. Inbound relationships propagate NONE as a status. which is described below. Consider the array of propagated_status ordered from highest to lowest status. The quorum value is given by the quorum slot of the BMC_STATUS_COMPUTATION instance.Quorum algorithm examples Function impact_function Input value Component has no inbound relationship. The impact_status is the status corresponding to the element i of this array. The impact_status is the highest propagated_status that a quorum percentage of provider agree upon. Output value NONE NONE NONE self_function consolidate_function No events are associated with the component. 130 BMC Impact Solutions Service Modeling and Publishing Guide . Impact status value is NONE and self-status value is NONE or there are no inputs. When you create a quorum type of StatusModel. you specify a percentage. An easy computation of the quorum status can be done as follows: s s s There are n providers with propagated_status different from NONE: let i be the lowest integer that is greater or equal to quorum*n/100. default no-alert status value from the status computation model Quorum algorithm examples The CLUSTER option for Status Computation uses the QUORUM impact function.

Quorum algorithm examples EXAMPLE CASE A website 1 (quorum-based component status computation) host1 host2 Example A1 QUORUM=50. which breaches the quorum threshold. host1=MINOR. Example B3 quorum_percent=60. OK. host2=IMPACTED 1 < 51*2/100 < 2 => q = 2 array = [IMPACTED. host1=OK. host3=UNAVAILABLE. host4=MINOR 1 < 30*4/100 < 2 => q = 2 array = [UNAVAILABLE. host2=IMPACTED 50*2/100 = 1 => i = 1 array = [IMPACTED. so the status of website 2 is MINOR. OK] The percent of hosts that are not UNAVAILABLE is 25%. so the status of website 1 is OK. host1=OK. host2=OK. so the status of website 2 = MINOR Chapter 5 Component and relationship status propagation 131 . which is less than 30%. OK. host3=UNAVAILABLE. host1=OK. Example B2 quorum_percent=30. MINOR. host1=MINOR. so the status of website 1 is IMPACTED. impact-based component status computation) host1 host2 host3 host4 Example B1 quorum_percent=30. host2=OK. host4=Minor 1<30*4/100<2=>q=2 array = [MINOR. OK] There is at least 60% (actually 75%) of the providers that state a severity at least MINOR. OK. UNAVAILABLE. Example A2 QUORUM=51. MINOR] There is indeed at least 51% of the providers (actually 100%) that state a severity at least MINOR. host2=IMPACTED 1 < 51*2/100 < 2 => q=2 array = [IMPACTED. host3=OK. MINOR. host1=OK. host2=OK. host4=UNAVAILABLE 2 < 60*4/100 < 3 => q=3 array = [UNAVAILABLE. so the status of website 1 = MINOR CASE B website 2 (quorum-driven. OK] The percentage of hosts that are not AVAILABLE is 50%. Example A3 QUORUM=51. which does not breach the quorum threshold. OK] There is at least 30% (actually 50%) of the providers that state a severity of at least MINOR. so the status of website2 is OK. OK] The percentage of hosts that are not AVAILABLE is 50%.

For example.Relationship status propagation concepts Relationship status propagation concepts The cell performs status propagation for relationships and it relies on the status propagation model associated with each impact relationship instance. The result is the propagated_status value. retrieves each outbound impact relationship with its associated state and its status propagation model. for the INCREASING status propagation there will be a number of propagation map instances each of which increases the status propagated by a provider component to a consumer component. 132 BMC Impact Solutions Service Modeling and Publishing Guide . the cell takes the main status (status slot value) of the component. This would be a single propagation map instances . The BMC_STATUS_PROPAGATION data class supports relationship control and. Each status propagation model must have a unique name to identify it. One status propagation model is made up of several instances in both data classes. The name of a single BMC_STATUS_PROPAGATION refers to multiple BMC_PROPAGATION_MAP instances all of which have the same name (a one-tomany relationship). You can create as many status propagation models as needed to control component status propagation. such as a status change on the component or a state change on an outbound relationship. When a status change on a component instance triggers a status propagation. Each BMC_PROPAGATION_MAP instance defines how a provider component status is propagated over a relationship to the consumer component. and searches the propagation map for a matching entry. That model can then be applied to one or more impact relationship instances.one is needed for each status. provides dynamic status mapping. if a provider has status MINOR the status propagated over the relationship to the consumer will be IMPACTED. enabling the cell to handle status propagation appropriately for those objects. Status propagation is based on impact relationships and status propagation models. The role of a status propagation model is to define the status value to be propagated in all possible situations. So. which is passed as an input to the impact_function of each consumer component. together with the BMC_PROPAGATION_MAP data class. How status propagation works The cell automatically propagates the status of component instances through its outbound relationships as new conditions occur.

Status propagation models A propagation model defines how the status of a provider component must be propagated in an impact relationship based on s s the current state of the relationship the current value of the provider’s status Status propagation models are used only by impact relationships. the consumer’s status degrades faster than the provider’s does DECREASING—consumer component can function without provider’s services. When a problem occurs. For more information. Status propagation models serve the following purposes: s s relationship control—enforcement of logical rules in creating new component relationships so that only valid relationships are created dynamic status mapping—translating the main status of the provider component into a propagated status for input into the impact_function of the consumer component in a relationship The impact_function is part of the status computation of a component. The result is the propagated_status value that is then passed as an input to the impact_function of the consumer component. the consumer’s status is less degraded than the provider’s s Chapter 5 Component and relationship status propagation 133 . see “Anatomy of a status computation model” on page 129. When a problem occurs. Default status propagation models The service model provides the following default status propagation models: s DIRECT—consumer component depends on the provider’s services to the extent that its status is the same as the provider’s s INCREASING—consumer component is overly dependent on the provider. and searches the propagation map of the status propagation model for a matching entry. the cell combines the main status of the component with the retrieved state and the status propagation model of the relationship.Status propagation models When a state change on an outbound impact relationship triggers a new status propagation for that component instance.

Table 36 How status propagation models work in relationships Status propagation model Relationship state Result DIRECT ACTIVE INACTIVE propagates the provider’s status without modification to the consumer propagation of the provider’s status is blocked by mapping the provider’s status to NONE This value is ignored by the consumer. JUST_INFO ACTIVE for statuses greater than or equal to INFO. NONE is propagated propagation of the provider’s status is blocked by mapping the provider’s status to NONE This value is ignored by the consumer. OK maps to OK.Default status propagation models s JUST_WARNING—propagates the status of a provider component so that any value less than OK maps to NONE. INFO is propagated. JUST_WARNING ACTIVE INACTIVE for statuses greater than OK. and any value greater than OK maps to WARNING JUST_INFO—propagates the status of a provider component so that any value less than INFO maps to NONE. INACTIVE 134 BMC Impact Solutions Service Modeling and Publishing Guide . and any value greater or equal to INFO maps to INFO s Table 36 describes the how status propagation occurs for a specific model. WARNING is propagated propagation of the provider’s status is blocked by mapping the provider’s status to NONE This value is ignored by the consumer. for statuses less than INFO. DECREASING ACTIVE INACTIVE decreases the impact of the provider’s status on the consumer’s status propagation of the provider’s status is blocked by mapping the provider’s status to NONE This value is ignored by the consumer. INCREASING ACTIVE INACTIVE increases the impact of the provider’s status on the consumer’s status propagation of the provider’s status is blocked by mapping the provider’s status to NONE This value is ignored by the consumer.

Chapter 5 Component and relationship status propagation 135 .What is a valid status propagation model? What is a valid status propagation model? A valid status propagation model is a BMC_STATUS_PROPAGATION instance. all sharing the same name. A valid status propagation model must have: s 8 instances of the data class BMC_PROPAGATION_MAP. Figure 18 depicts this relationship. complemented with the appropriate number of BMC_PROPAGATION_MAP instances. one for each possible provider component status value for the INACTIVE state 1 instance of the BMC_STATUS_PROPAGATION data class that defines the propagation model’s attributes s s Important service components Important service components are components with self_priority slot values that affect the overall impact_priority slot value of their root cause component(s). A BMC_STATUS_PROPAGATION instance is not created if the supporting BMC_PROPAGATION_MAP instances have not yet been created. In return. the self_priority slot values of the important service components are propagated back to their respective root cause component(s). one for each possible provider component status value for the ACTIVE state 8 instances of the data class BMC_PROPAGATION_MAP. Root cause components propagate their status values forward to the important service components that they impact.

impact_status and there is no other such component in the true impact path from A to B. based on whether a component is in demand at the time (as defined in its service schedule).Dynamic prioritization Figure 18 Propagation paths between root cause and important components Component A is considered as a root cause of component B if s s A. The final priority of a component is determined by comparing the component’s self priority and impacts priority. Dynamic prioritization Dynamic prioritization is a system of setting the priority of a component to help you understand what problems to work on first. the severity of its status. 136 BMC Impact Solutions Service Modeling and Publishing Guide . and its impacts.status > OK A.status > A.

A component is considered down from a cost/SLA perspective when its status is greater or equal to a specified value. NOTE Normally. the instance with the lowest status is used. Self priority Self priority is a dynamic priority that changes depending on s s s the status of the component the schedule status associated to the component (during or off schedule) and one of the following three methods of priority computation: s base priority (default) s cost s worst SLA state Both the cost and the worst SLA state methods rely on the concept of down time. only one instance of this table should ever exist. Figure 19 Self priority determination Chapter 5 Component and relationship status propagation 137 . If several instances exist. This value is stored in the slot status of the BMC_DOWNTIME_STATUS_CONFIG BAROC table.Self priority The greater value becomes the final priority value of the component.

Self priority Base priority method Base priority is the default method for computing self priority. if the component is a server that supports a business that is open from 8:00AM to 6:00PM. then the higher During Schedule priority would be applied to the server during the hours that the business is open and the Off Schedule priority would be applied to the server when the business is closed (6:00PM to 8:00AM). Mapping base priority You can map these values by editing the BMC_SELF_PRIORITY_MAPPING BAROC table in the BMC Impact Service Model Editor. How the base priority method calculates priority Each component has two base priority values: s the During Schedule priority. Self priority is determined by mapping the current base priority (depending on whether the component is on or off schedule) against the status value of the component. Enabling the base priority method The base priority method is enabled by default. 138 BMC Impact Solutions Service Modeling and Publishing Guide . modify MC_SM_COMPONENT class to set the SelfPriorityFunction slot to the value BASE_PRIORITY. To specify the base priority method if the default has been changed. The base priority values are static priority values that act as a baseline to determine self priority. which is the priority assigned to the component during the peak hours of its schedule stored in the Priority slot the Off Schedule priority. which is the priority assigned to the component during the hours that are not critical for its operation stored in the PriorityOut slot s For example.

Cost is a user-specified monetary value per unit of time—for example. $5. concomitant cost values.Self priority The self-priority value of the important component is calculated based on a formula that takes into account both the base_priority value and its status value. whether or not the cost method is used to determine the self priority of that component. Cost method The cost method determines priority based on the actual cost of a component being down. the value 5 can indicate $5. Creating a BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING instance The cost model.00 per second of downtime. the higher priority that component will have. The more money it costs for a component to be down. Chapter 5 Component and relationship status propagation 139 . as depicted in the BMC Impact Portal: This mapping is configured in the match table in BMC Impact Service Model Editor. The cost value is typically defined as cost per unit of time: for example.00US per second. and the mappings between cost values and the severity levels of the self_priority value are user defined. NOTE The cost of a component is always computed if the During/Off schedule cost values are set for that component.

which is the cost assigned to the component during the hours that are not critical for its operation. the cell copies one or the other of these values to the slot cost. The cost method first checks to determine if the component is down as specified by the down time definition in SIM_DOWNTIME_STATUS. and its self priority is set the lowest priority (PRIORITY_5). which is the cost assigned to the component during the peak hours of its schedule. the Off Schedule cost. you must modify the following slots in the MC_SM_COMPONENT class: s Self_Priority_Function=COST Self_Priority_Function_Param=name of the cost of downtime priority mapping group (a mapping group is made of a varying number of BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING instances sharing the same name) s How the cost method calculates priority Each component has two cost values: s the During Schedule cost. Otherwise. This value is stored in the ImpactCostPerSec slot. self_priority : MC_PRIORITY. If the cost status is less than the SIM_DOWNTIME_STATUS. the BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING table is used to determine the self_priority value as follows: Let c be the cost of the component and n be the name of a mapping stored in the SelfPriorityFunctionParam slot of the component.Self priority When you create an instance of the BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING. cost: REAL. key=yes. This value is stored in the ImpactCostPerSecOut slot. 140 BMC Impact Solutions Service Modeling and Publishing Guide . s Depending on whether the component is in the During Schedule or Off Schedule timeframe. then the component is not considered to be down. }. you specify the cost parameter as a date type REAL as shown: BMC_PUBLISH_DATA_CLASS : BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING ISA BMC_SIM_DATA DEFINES { name: STRING. END Enabling the cost method To enable the cost method. key=yes.

The status enumeration values for the cost method are stored in the SIM_DOWNTIME_STATUS_CONFIG table in the mc_sm_root. If there is no such instance. the SelfPriorityFunction of the component definition is set equal to COST and the name of the mapping value is test_cost.baroc file of each cell. Chapter 5 Component and relationship status propagation 141 .Self priority If there is an instance i in this table with s s s s name = n cost = costi self_priority = priorityi such that costi < c and there is no other instance j with s such that costj > costi and costj < c then the self_priority of the component is set to priorityi. the self_priority of the component is set to the lowest priority (PRIORITY_5). Figure 20 Cost priority method of priority determination Cost method example In this example.

0 and self_priority maps to PRIORITY_2 off schedule the cost is 1. self_priority=PRIORITY_2. SelfPriorityFunction=COST. cost=5. name=test_cost.Self priority BMC_System. END BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING. ImpactCostPerSec=5. BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING. self_priority=PRIORITY_4. cost=2. END BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING. name=test_cost. if the status is UNAVAILABLE (or at least greater than or equal to the SIM_DOWNTIME_STATUS) then s s during schedule the cost is 5. END This series of mapping table examples associate different cost values with corresponding self_priority values in ascending order.0. cost=1. with 4 as the least severe and 1 as the most severe. self_priority=PRIORITY_1. END BMC_COST_OF_DOWNTIME_PRIORITY_MAPPING. END Based on the sample test_cost mapping table. cost=10. name=test_cost.0 and self_priority maps to PRIORITY_4 142 BMC Impact Solutions Service Modeling and Publishing Guide . PriorityWatchdog=YES. ImpactCostPerSecOut=1. self_priority=PRIORITY_3. SelfPriorityFunctionParam=test_cost.0. mc_udid=comp_r3_c2. name=test_cost. Name=comp_r3_c2.

sla_state: MC_SM_SLM_SLA_STATUS. Creating a BMC_WORST_SLA_STATE_PRIORITY_MAPPING instance When you create an instance of the BMC_WORST_SLA_STATE_PRIORITY_MAPPING. key=yes. whether or not the worst SLA method is used to determine the self priority of that component. key=yes. Possible SLA states are: s s s s NO_SLAS COMPLIANT AT_RISK BREACHED The SLA state for each component is assigned by BMC Service Level Management.Self priority Worst SLA state method NOTE The worst SLA state method can be used only if you are using the BMC Service Level Management product. you specify the sla_state parameter as belonging to the enumeration type MC_SM_SLM_SLA_STATUS as shown: MC_PUBLISH_DATA_CLASS : BMC_WORST_SLA_STATE_PRIORITY_MAPPING ISA BMC_SIM_DATA DEFINES { name: STRING. The rolled up SLA states are stored in the sla_rollup_status slot. The worst SLA state method determines priority based on the Service Level Agreement (SLA) for a component. self_priority : MC_PRIORITY. such as daily or weekly. NOTE The sla_rollup_status of a component is always computed if there is at least one service target associated to that component. END The enumeration MC_SM_SLM_SLA_STATUS is defined as follows: ENUMERATION MC_SM_SLM_SLA_STATUS 0 NO_SLAS 10 COMPLIANT 20 AT_RISK 30 BREACHED END Chapter 5 Component and relationship status propagation 143 . Each SLA is tracked separately within a specified time period. The SLA states are rolled up for the specified period and the worst SLA state is given priority. }.

Self priority Enabling the worst SLA state method To enable the cost method. then the component is not considered to be down. the self_priority of the component is set to the lowest priority (PRIORITY_5). If there is an instance i in this table with s s s name = n sla_state = s self_priority = p then the self_priority of the component is set to p.baroc file of each cell. 144 BMC Impact Solutions Service Modeling and Publishing Guide . If there is no such instance. The worst SLA state method first determines if the component is down according to the down time definition in SIM_DOWNTIME_STATUS_CONFIG. If the cost status is less than the SIM_DOWNTIME_STATUS. Otherwise. you must modify the following slots in the MC_SM_COMPONENT class: s Self_Priority_Function=WORST_SLA_STATE Self_Priority_Function_Param=name of the worst SLA state priority mapping group (a mapping group is made up of a varying number of BMC_WORST_SLA_STATE_PRIORITY_MAPPING instances sharing the same name) s How the worst SLA state method calculates priority To use the cost method to determine priority of a component. set its SelfPriorityFunction slot to the value WORST_SLA_STATE. and its self priority is set the lowest priority (PRIORITY_5). the BMC_WORST_SLA_STATE_PRIORITY_MAPPING BAROC table is used to determine the self_priority value as follows: Let s be the value stored in the sla_rollup_status slot of the component and n be the name of a mapping stored in the SelfPriorityFunctionParam slot of the component. The status enumeration values for the worst SLA state method are stored in the SIM_DOWNTIME_STATUS_CONFIG table in the mc_sm_root.

name=test_sla. sla_state=COMPLIANT. In this example. BMC_WORST_SLA_STATE_PRIORITY_MAPPING. 5 is the least severe and 2 indicates a greater severity. name=test_sla. self_priority=PRIORITY_5. name=test_sla.Self priority Figure 21 Worst SLA method of priority determination Worst SLA state method example This series of mapping table examples associate different sla_state values with corresponding self_priority values arranged in ascending order. self_priority=PRIORITY_2. sla_state=NO_SLAS. END BMC_WORST_SLA_STATE_PRIORITY_MAPPING. sla_state=AT_RISK. END BMC_WORST_SLA_STATE_PRIORITY_MAPPING. name=test_sla. self_priority=PRIORITY_1. self_priority=PRIORITY_5. END Chapter 5 Component and relationship status propagation 145 . END BMC_WORST_SLA_STATE_PRIORITY_MAPPING. sla_state=BREACHED.

BMC_System. The impacts priority is based on the components it is impacting that are marked as priority propagators. Name=compx. mc_udid=compx. Thus.Impacts priority In this example. Figure 22 Impacts priority determination 146 BMC Impact Solutions Service Modeling and Publishing Guide . END Impacts priority The impacts priority of a component reflects the urgency of resolving a problem based on the components it impacts. the impacts priority is a dynamic value which changes as the self-priorities of the impacted components change. which can have the result that the causal component’s problem is considered a more urgent problem than it would have been otherwise. SelfPriorityFunctionParam=test_sla PriorityWatchdog=YES. SelfPriorityFunction=WORST_SLA_STATE. the Self_Priority_Function of the component definition is set equal to WORST_SLA_STATE and the name of the mapping value is test_sla. A component which is a priority propagator can be considered an “important” component in that a priority propagator sends its self priority value back to its causal component.

Determination of final priority Determination of final priority The final priority of a component is the highest value between the self priority and impacts priority. Chapter 5 Component and relationship status propagation 147 . as illustrated in Figure 23 on page 148.

Determination of final priority Figure 23 Final priority determination 148 BMC Impact Solutions Service Modeling and Publishing Guide .

NOTE If the cost and sla_rollup_status data are available for an important service component. Root cause components aggregate the cost of all their impacted important components by summing their cost into the impact_cost slot.How cost impact is calculated How cost impact is calculated The cell propagates the cost of important components to their root causes (causal components). How SLA impact is calculated The cell propagates the sla_rollup_status of important components to their root causes (causal components). Root cause components aggregate the sla_rollup_status of all their impacted important components by propagating the highest value into the impact_sla_rollup_status slot. even if the corresponding cost or worst SLA method is not used to determine the self priority of that important service component. Chapter 5 Component and relationship status propagation 149 . then these values are always propagated downward to the impact_cost and impact_sla_rollup_status slots of its causal component(s).

How SLA impact is calculated 150 BMC Impact Solutions Service Modeling and Publishing Guide .

. . . . . . . . . . . Configuring the topology view in BMC Impact Service Model Editor . . . . . . . . Creating a new service model component class in the BMC Atrium CMDB . . . . . . . . . . This chapter includes the following topics: Setting BMC Impact Service Model Editor options . . . . Making your changes visible to applications . . . . Each component has a ReadSecurity and WriteSecurity set of attributes. .Chapter 6 Managing BMC Impact Service Model Editor 6 Service Management administration is performed in large part within BMC Impact Service Model Editor and its supporting data classes. . . . . . which impose a structure on the organization of service management information. . . . . . . . . . . . . . . . . with some administration also being done in the BMC Impact Portal. . . . . . . . . . . . . Associating a custom icon with a service model component . . . . . . . and each attribute can be associated with a user group that can be assigned either read or write access to a component. . . . . . . . . . . . . . . . . . . . . . . . Additional user control functions in BMC Impact Service Model Editor include console navigation trees. . . and pass this information to the BMC Impact Portal. . . . . 152 156 156 157 157 159 159 163 163 Chapter 6 Managing BMC Impact Service Model Editor 151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding new classes to the BMC Atrium CMDB . . . . . . . . . . . . . . . . . Documenting your extensions. control folder-level rights. . Access control is managed in the service model through individual component instances. . . . . . . . . . . . . . . . . . . . . . . . . Configuring the topology view in BMC Impact Service Model Editor . . . smeserver properties file and parameters . . . . . Administration includes managing all user access to information contained in the service model. . . . . .

choose a drawing mode. choose a number that limits the number of characters to display for component instance name labels. To define component instance icon colors and label styles 1 From the menu bar. If a component name is longer that the maximum number of characters. color. choose a background color for the component instance icon when the component instance is selected. Options that you can change include icon colors and label styles. Opaque results in the component being fully drawn. 4 In the Active Border Color list. choose Tools => Personal Options. type size. regional preferences. in the Maximum Number of Characters to Display box. This value applies to every component instance in every View. copy/paste settings.Setting BMC Impact Service Model Editor options Setting BMC Impact Service Model Editor options The Options command offers numerous configuration settings for user-specific definition as well as global options and is available to any user with access to BMC Impact Service Model Editor. in the Component icon area. line styles. s s Ghost results in a simple rectangular border. Drawing mode affects how the component instance looks when it is being moved. and log file preferences. All personal options are available by choosing Tools => Personal Options. The options settings are saved on BMC Impact Service Model Editor server. choose a color for the border of the component instance icon when the mouse cursor is over it. and style for the label that names the component instance icon. The values specified here are specific to the user and are reapplied when the user logs into BMC Impact Service Model Editor on any computer. 2 On the Components tab. View appearance. 5 In the Component Label area. the name is truncated. s choose a font. s 152 BMC Impact Solutions Service Modeling and Publishing Guide . Personal options Personal options settings are unique to the user. 3 In the Selection Background Color list.

and 3 invisible units. To create a custom line style. choose a predefined line weight or define a custom line weight by entering a decimal number (between 0. 5 In the Line Weight list. choose Tools => Personal Options. choose a format for each. 1 solid unit. 2 On the Regional Settings tab. 4 In Line Style list. a weight of 2.3 creates a repeating line pattern with 9 solid units.01 and 5. choose the option that works best in your environment.3.1. select the relationship type that you want to change. 3 In the Line Color list. For example: 9.0. 2 On the Relationships tab. Chapter 6 Managing BMC Impact Service Model Editor 153 . For example. 3 In the Date Format and Time Format areas.Setting BMC Impact Service Model Editor options To define line styles for relationships 1 From the menu bar. To set regional preferences 1 From the menu bar. choose Tools => Personal Options. but may be different in other languages. enter numbers separated by commas.0) that defines the width of the line. 3 invisible units. TIP When a View is open. you can see a legend of line styles by choosing Window => Legend. the Long and Full options appear the same in English. For the Time Format. in the Locale area.0 creates a line that is twice as thick as one with a weight of 1. select one of the predefined line styles or create a custom line style. The Use Country/Region Specified in BMC Portal User Account option uses the locale specified when BMC Portal was registered as a user. in the Relationship Type pane. choose a predefined color or set a custom color for the line. which alternately define the length of the visible/invisible line segments.

select the appropriate copy/paste options for renaming copied component instances. 4 For the Use Live Server Data During Selection check box. Dismiss Delay. 5 For the Show Tooltips check box. 3 In the Miscellaneous area. see “To copy component instances” on page 69. 4 In the Desktop Background Color list. choose Tools => Personal Options. in the Copy/Paste area. or enter values (in milliseconds) for the Initial Delay. clear this check box to not display paragraph-style instances of Help text that appear in some dialog boxes. in the Production/Sandbox View Background Color list. To set copy/paste and miscellaneous options 1 From the menu bar. This tab also controls the Paste Multiple Components dialog box. and Reshow Delay. options are defined as follows: s s check box selected: as each component is selected in the View. the data is retrieved again from the BMC Atrium CMDB. choose a color for the production and sandbox View background. 154 BMC Impact Solutions Service Modeling and Publishing Guide . choose a color for the test View background. options are defined as follows: s s check box selected: data for all Views is loaded into memory when you log into BMC Impact Service Model Editor check box cleared: data for a View is loaded into memory only when you open that specific View. s 6 For the Show Embedded Help Text check box. 2 On the Other tab. check box cleared: data for all the components in a View is retrieved from the BMC Atrium CMDB when the View is opened. s clear this check box to not see tooltips. 2 On the Appearance tab.Setting BMC Impact Service Model Editor options To set View appearance options 1 From the menu bar. 3 In the Test View Background Color list. for the Load Saved Views at Login check box. Data for an individual component may become outdated. choose Tools => Personal Options. choose a color for the right pane of BMC Impact Service Model Editor before a View is opened.

enter the maximum number of log messages you want to save in memory. set the level of log information you need on the client computer. select Tools => Options => Global Options. choose Tools => Personal Options. 3 In the Buffer Size box. This is a first in. then to the top of column two to the bottom of column two. You can specify a directory to save the files in. when the maximum number of messages is reached. when you open the Edit Component or Edit Relationship dialog boxes. The more detailed the log is. the more disk space is used. the count starts again at zero and the existing files with the same name are written over. the dialog box displays when you use the Find command and want to place found objects in a View (by dragging or clicking Place in Selected View) that already has contains the objects: s s checkbox selected: dialog box displays checkbox cleared: dialog box does not display. The first file saved is numbered 0. but the file name bmc_sme_integer_log# is generated by BMC Impact Service Model Editor. The most detailed log selection is All. 5 For the Show Duplicate Component Dialog checkbox. there is no alert that you are duplicating objects in the View To set log file preferences 1 From the menu bar. select options for saving log files on the client computer. 4 In the Log Files area. When the number of log files saved reaches the value in the Number of Log Files box. Global options To set component instance self-priorities when in a given status. subsequent logs increment by one.Setting BMC Impact Service Model Editor options NOTE Whichever setting is selected. the oldest message is deleted when a new one is added. first out buffer. 2 In the Logging tab. Logging becomes more detailed as you go from the top of column one to the bottom of column one. Chapter 6 Managing BMC Impact Service Model Editor 155 . the latest information is always retrieved from the BMC Atrium CMDB.

impact Each item in the list has two functions: s It is a resource key to a localized name (that can appear in the user interface).sme. s 156 BMC Impact Solutions Service Modeling and Publishing Guide . the self-priority values are automatically changed for the statuses of INFO.topo. and BLACKOUT. To edit service schedule self-priorities 1 In the Options .sme. see Chapter 5. the default is shown in Figure 24.com. For more information. For example.Global dialog box.bmc.topoviews=com.” Configuring the topology view in BMC Impact Service Model Editor You can set the type of topology views displayed by BMC Impact Service Model Editor in the . This parameter has a comma-delimited list of the supported topology views. Figure 24 Default value for com.sms.topoviews parameter com.bmc.application. non. UNKNOWN.properties file for the appropriate locale.sms. see “Service schedules” on page 42.sms.properties file using the com.sms.topoviews parameter. 4 Click OK to save your changes.Configuring the topology view in BMC Impact Service Model Editor For more information on Service Schedules..sme. 3 In the Default Component Types that Propagate Priority box. NOTE If you change the self-priority of the component for an Other status. select the appropriate status level (1-5) for each base priority/status level.bmc.sme. choose the calculation method for the component.\smsIwc\application. 2 In the Impacts Priority Calculation Method. “Component and relationship status propagation.sme. in the Base Priority/Status table. The localized name is defined in the sme_messages.sms. Separate the class names by commas.bmc.topo. It is the base key for the definition of the topology view.bmc. enter the classes of components that will have a default value of Propagate Priority=Yes.

BMC Remedy AR System applications Some BMC Remedy AR System applications. Figure 26 Example of a graph definition com.<RelationshipType>. Making your changes visible to applications When you add classes and attributes to your data model. The general format of a graph definition is shown in Figure 25.topo.application. for a graph type whose key is com.BMC_MemberOf.topo. For information about using this feature.application.0.sms. such as BMC Impact Solutions products or BMC Remedy Asset Management.bmc. such as BMC Remedy Asset Management. maintain their own set of join forms for viewing and modifying BMC Atrium CMDB instance data.sme.1=BMC_BaseElement. The BMC Atrium CMDB now has the ability to generate attribute fields for such an application and arrange the fields according to view templates specified by the application.1 Installation and Configuration Guide. the following graph entries could be defined as shown in Figure 26.sms.BMC_Component.BMC_BaseElement com.BMC_BaseElement A graph definition can include as many types as desired. see the BMC Atrium CMDB 2.sms.BMC_Impact. Figure 25 Graph definition format <ComponentType>.<ComponentType> For example.bmc.topo.application. they are not automatically picked up by BMC Software products that use the BMC Atrium CMDB.BMC_BaseElement Adding new classes to the BMC Atrium CMDB This section contains information about adding new classes and attributes to your data model. For example: BMC_BaseElement. but it must always begin and end with a component type.bmc. You must modify new classes and attributes so they can be used with these applications.sme.sme. Chapter 6 Managing BMC Impact Service Model Editor 157 .Adding new classes to the BMC Atrium CMDB Each base key is appended with an integer (for as many as needed) that defines a graph to traverse for the topology view.2=BMC_BaseElement.

158 BMC Impact Solutions Service Modeling and Publishing Guide . its superclasses. 2 Add custom icons for new classes. BMC:BaseRelationship) must be SIM-enabled as well. not only does the new class need to be SIM-enabled (having the class custom qualifier value of 100050). export cell metadata. For instructions on this step. For more information. see “Creating a new service model component class in the BMC Atrium CMDB” on page 159. For your new class to be a service model component class. Instances with this property are pushed by the BMC Impact Publishing Server to the cells. The new class inherits the attributes of its superclass. import the resulting file into the cell’s Knowledge Base. see “Associating a custom icon with a service model component” on page 159. 3 From BMC Impact Service Model Editor. and recompile the cell. note the following information about classes: s s s s s Classes with the custom qualifier 100050 are SIM-enabled classes. up to the root class (such as BMC:BaseElement. whether concrete or abstract. Perform the following steps to update BMC Impact Solutions to use new classes and attributes: 1 Using the Class Manager. see “Exporting class definitions from the BMC Atrium CMDB to a cells” on page 124. BMC Impact Publishing Server pushes attribute values to the cells. For instructions on this step. see “Exporting and importing service model data” on page 123 and BMC Impact Solutions Knowledge Base Development Reference Guide. BMC Impact Service Model Editor filters out abstract classes. Note the following information about attributes: s s SIM-enabled attributes have the custom qualifier 300050. add these custom qualifiers to the new classes and attributes: s Classes: 1\100050\2\1\ SMEReadWrite attributes: 2\300050\2\1\300070\2\1\ SMEReadOnly attributes: 2\300050\2\1\300080\2\1\ s s For instructions on this step. SIM-enabled class definitions in the BMC Atrium CMDB and the class definitions in the BMC Impact Manager cell must match.Making your changes visible to applications BMC Impact Solutions While updating BMC Impact Solutions to use new classes and attributes.

CORE or BMC.1 Installation and Configuration Guide. BMC Impact Portal.0. which you can view in the Templates dockable window. Chapter 6 Managing BMC Impact Service Model Editor 159 . 4 Specify the Custom Qualifier 1\100050\2\1\ in the General tab. Each component type in BMC Impact Service Model Editor is associated with an icon. Associating a custom icon with a service model component The BMC Impact Service Model Editor.png file format if you rename the file extension from . To create a new service model component class in the BMC Atrium CMDB 1 Use the BMC Atrium CMDB Class Manager to create a new CI class. It is advised not to add new classes to BMC. you can use icons in . see “Service model component types” on page 26. see “Modifying the Data Model” in the BMC Atrium CMDB 2.Creating a new service model component class in the BMC Atrium CMDB 4 Restart the BMC Impact Portal. regardless if they are abstract or concrete. Creating a new service model component class in the BMC Atrium CMDB This section contains steps for creating a new service model component class. up to BMC_BaseElement.png to . User userName should use namespace userName.gif format. For instructions.gif. and BMC Impact Explorer Services views utilize icons to represent service model components. need to be SIM classes. 5 Click Save. For a list of default service model component icons. NOTE Icons must be in .SIM. SIM-enabled classes are listed in “Service model and the Common Data Model” on page 46. All superclasses of a SIM class. However. 3 Select the service model component superclass to which you want to assign the new service model component class. 2 Assign the class to the namespace.

properties file is located in the following directory path: s Solaris— %BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server\all\conf\pr operties\smsConsoleServer\ s Windows— %BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server\all\conf\pr operties\smsConsoleServer\ B Add the following to the component_icon.ClassName=IconFileClassName C Save the component_icon. 160 BMC Impact Solutions Service Modeling and Publishing Guide . 3 Store an identical set of the three icon files—each file in the set designating a different pixel size—under each of the three specified subfolders on the system where the BMC Portal application server is running. 5 Restart the BMC Impact Administration Server.ext. See “Guidelines for associating a custom icon with a service model component class” on page 161. 2 Create a set of the three different-sized icons for the new class. the component_icon. and save them using the file naming convention className_size. 4 Associate the icon with the service model component class by performing the following actions: A Edit the component_icon.Associating a custom icon with a service model component When you create a new component type by adding a new class to the BMC Atrium CMDB.component.properties file: Replace ClassName with the name of the new class you defined in the BMC Atrium CMDB and IconFileClassName with the prefix you used to name the three icon files (className_size.ext). associate an icon with the new component. see “Adding new classes to the BMC Atrium CMDB” on page 157. By default.icon.properties file. 1 Create a new class in the BMC Atrium CMDB. sms.properties file. To associate an icon with a service model component class When adding a custom icon to a newly created class. See “Guidelines for associating a custom icon with a service model component class” on page 161. For instructions. follow this sequence for initializing the new data and synchronizing the class definition with those in the SIM KB of the target cell or cells.

and 128 x 128 pixels. and 128 x 128 pixels. and 128 x 128. you make it available to the SIM KB of the target cell or cells.Associating a custom icon with a service model component 6 Restart the BMC Portal application server and all BMC Impact Service Model Editor client instances. 32 x 32. Follow this naming convention: Chapter 6 Managing BMC Impact Service Model Editor 161 . 9 Create the new class definition in BAROC format by using Tools => Export Cell Meta Data.-n cellname 12 Restart the cell or cells. For example. you must include three sets of identical icons. set two contains the same three icons of 16 x 16. Guidelines for associating a custom icon with a service model component class Follow these guidelines when adding and associating custom icons with service model component classes: s BMC Impact Service Model Editor and BMC Impact Portal accept three sets of pixel sizes for the component icons: 16 x 16. After you convert the class definition to BAROC format. For instructions see “Exporting and importing service model data” on page 123. set one contains three identical icons of 16 x 16.baroc file to the destination directory of the target cell or cells. and so forth. s s Name each custom icon using the same name as the custom class it represents.baroc file is located in the following directory path: s Solaris—$MCELL_HOME/etc/CellName/kb/classes Windows—%MCELL_HOME%\etc\CellName\kb\classes s 11 Recompile each cell’s KB by using the command: mccomp. 8 Synchronize the new service model class definitions with the SIM KB. Use . 10 Manually copy the mc_sm_object. 32 x 32. and 128 x 128.gif format only. The file that is created is named mc_sm_object. 32 x 32. 32 x 32. each set using the three different pixel sizes: 16 x 16. By default. 7 Refresh BMC Impact Service Model Editor templates by using Tools => Refresh Component Types.baroc. For each custom class that you create. the mc_sm_object.

gif className is the name of the custom class you created. If no match is found. or Unknown_128. BMC Impact Service Model Editor uses the default icon Unknown_16. On Windows. By saving an identical set of the three different-sized icon files to the subdirectory.war\images\objects On Solaris. Default icon when no match is found When retrieving component icons.Associating a custom icon with a service model component className_size. Unknown_32. the directory is located as follows: — %BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server\all\modules\ smsConsoleServer. if you created a custom class named BMC_ABCServer. it next searches the images subfolder.gif — BMC_ABCServer_32. you are making them available to both BMC Impact Service Model Editor.png. size refers to the pixel sizes 16.gif s Save a set of the three different-sized custom icons to the following subdirectory under the BMC_Portal_Kit_Home installation directory.png. Figure 27 BMC_BaseElement default icon image 162 BMC Impact Solutions Service Modeling and Publishing Guide .png. and then move all the files in the images directory to the new objects subdirectory. the directory is located as follows: — $BMC_Portal_Kit_Home/appserver/websdk/tools/jboss/server/all/modules/ smsConsoleServer.gif — BMC_ABCServer_128. For example. create it. BMC Impact Service Model Editor first searches its local repository for the icons shipped with the product. If the matching icons are not found. and 128. and BMC Impact Explorer Services View.sar/smsConsoleServer. you would create three corresponding custom icons named as follows: — BMC_ABCServer_16. You can find this directory on the system where the BMC Portal application server is installed.war/images/objects NOTE If the objects subdirectory is missing.sar\smsConsoleServer. gif is the file extension and is required. 32. BMC Impact Portal.

server. publish.requests com. publish.bmc. no limit undefined.limit com.sms.Documenting your extensions Documenting your extensions Just as you need to occasionally look up information about classes in the CDM.server. Table 37 Filename File path Description smeserver. tmpdir undefined.sme.bmc. default temp directory is JBOSS_HOME/ server/all/tmp/ sme ps_requests ps_response ps_notifications com.bmc.server. If you copy the help file for a class with the same superclass as your class. status.properties file and its parameters.find.precache.server.sme.change sets the name for the BMC Impact Publishing Server request queue sets the name for the BMC Impact Publishing Server response queue sets the name for the BMC Impact Publishing Server notification topic Chapter 6 Managing BMC Impact Service Model Editor 163 .sms.queue.sms.server. you won’t need to change the information about inherited attributes and relationships.queue.sms.sme. be sure to make a backup copy of them in a separate location so that they won’t be overwritten when you install a future version of the BMC Atrium CMDB. cmdb. After creating your HTML help files.properties file smeserver.bmc.sms.server. you will need to look up information about classes you create.sme.topic. sets the number (integer) of component instances retrieved as a result of the Find command sets the temp directory of the BMC Impact Service Model Editor server Default value true Parameter name com.sms.sme. smeserver properties file and parameters Table 37 describes the smeserver.response com.properties BMC_PORTAL_KIT_HOME/appserver/webskd/tools/jboss/server/all/conf/properties/smsS me contains all the user configurable BMC Impact Service Model Editor properties Description sets whether the precache applet is run to request component types from the BMC Atrium CMDB if defined. One easy way to document a class is to copy one of the existing HTML files in CMDBInstallationFolder\sdk\doc\cdm and modify it to fit your class.sme.result.bmc.publish. cmdbservice. publish.bmc. componenttypes com.

classes.ping com.timeout com.enable com.bmc.server. publish.sme.sme.date.response.sme.sms.sms.sms.time status on a reconciliation job com. for the Reconciliation ion.publish.sme.extended.sme.bmc.promot sets the amount of time to wait before checking the ion. publish.bmc.bmc.bmc.response.sme.format com.server. in seconds.sms.sms.datasetid com.server.sms. consoleserver: name=LastPubli shManager 60 seconds com.wait.sms.promot sets the timeout. timeout sets the timeout value (the number of seconds to wait) for reception of BMC Impact Publishing Server responses sets the timeout value (the number of seconds to wait) for reception of BMC Impact Publishing Server extended responses 3600 seconds com.bmc.server.bmc.bmc.ASSET 60 seconds smsConsoleServ er enables (true) or disables (false) publishing previews sets the date format for the BMC Impact Service Model Editor defines the dataset (using dataset ID) to use for service model exports sets the polling interval.sms.name com.sme.sms.controller. the publishing controller component of the BMC Impact sme. publish.smeserver properties file and parameters Table 37 smeserver.sme.bmc.server.bmc.sme.sms.sms.cmdb.sms.manager com.timeout Engine to reconcile objects into production com.sme.server: Publishing Server name= PublishService Controller defines the JMX name of the last successful Publishing Manager com.sme.properties file sets the Java Management Extensions (JMX) name for com. export.sms. in seconds.localized. preview.bmc.server.dir 3600000 seconds 1000 seconds true HH:mm:ss z MM/dd/yyyy BMC.bmc. for pinging the BMC Atrium CMDB to ensure that it is available defines the base directory used under SDK_HOME/tools/jboss/server/all/ conf/resources/locale/classesdir to retrieve localized server resources for class names and attributes 164 BMC Impact Solutions Service Modeling and Publishing Guide .lsp.bmc.

kb. Each key is appended with an integer (for as many as needed) that defines a graph to traverse for the topology view.sme.bmc. you must restart the BMC Portal service or daemon for the changes to take effect. Each element in the list has two functions: s See smeserver. The files listed must exist in the SDK_HOME/tools/jboss/server/all/ conf/resources/locale/classesdir kb_deprecated_ resource.topoviews defines a comma-delimited list of supported topology views.properties file lists the names of property files that contain localized classes and attributes. you must restart the BMC Impact Publishing Server service or daemon also. properties com. The files are loaded in the order listed and the files loaded later override settings in files loaded earlier. Chapter 6 Managing BMC Impact Service Model Editor 165 . s If you edit any of these configuration files manually.sms.info.bmc.kb_co re_resource. resources com. It is the base key for the definition of the topology view.smeserver properties file and parameters Table 37 smeserver. If you have edited any of the BMC Impact Publishing Server configuration files. properties.sms.sme. You can define custom files and add them to the list. the UI). properties file for current It is a resource key for a localized name (suitable for default values.

smeserver properties file and parameters 166 BMC Impact Solutions Service Modeling and Publishing Guide .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 7 Creating a service model by importing HP OVO data 167 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . Installing the integration with HP OVO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Steps to import HP OVO data to create a service model. . . . . . . . . . . . . . . . . . . . . . . . Importing HP OVO data to create a service model . . . . . . . . . .Chapter 7 168 168 168 168 169 172 172 172 Creating a service model by importing HP OVO data 7 This chapter covers the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-level data flow . . . . . . . . . . . . . . . . . . . Atrium and non-Atrium environments . . . . . . .

Overview Overview The BMC Impact Service Model Integration with HP OpenView Operations (OVO) provides a mechanism to import an HP OVO node hierarchy and automatically create a service model view of the hierarchy. After selecting the integration with HP OVO and completing the remainder of the installation process. 168 BMC Impact Solutions Service Modeling and Publishing Guide . In a non-Atrium scenario. the BMC Atrium CMDB Reconciliation Engine reconciles objects fetched from HP OVO against the CMDB before automatically publishing the service model to a cell via the Publishing Server. The dataset and rules are installed as part of the SIM CMDB extensions. objects are fetched from HP OVO and the Publishing Server handles publishing the service model directly to a BEM or SIM cell. From the Administration tab of the BMC Impact Explorer. you can create an HP OVO service model view on demand or at scheduled intervals. The integration with HP OVO automatically publishes the service model either directly to a BEM or SIM cell in a non-Atrium environment or to the BMC Atrium CMDB for reconciliation before passing the data to a SIM cell. the installation program installs the integration in the MCELL_HOME directory. For detailed instructions for installing the integration with HP OVO. Installation The integration with HP OVO is installed as an option of the BMC Impact Solutions installation program. see BMC Impact Solutions Installation Guide. the integration with HP OVO requires a BMC Atrium CMDB dataset and reconciliation rules. Installing the integration with HP OVO This section explains general installation information for the integration with HP OVO. Atrium and non-Atrium environments The integration with HP OVO supports service model publishing to cells in both Atrium and non-Atrium environments. If you plan to use an Atrium environment. In an Atrium-enabled environment.

Chapter 7 Creating a service model by importing HP OVO data 169 . you must add an entry for the IAC in the mcell. as shown in Figure 28. If you install the adapter cell on a different computer as the IAC. no configuration is necessary. This adapter cell contains processing rules and handles communication between HP OVO and the Publishing Server. an adapter cell is installed as part of the integration with HP OVO. The registered adapter cell is displayed under the ADAP_Cell group in the navigation pane of the Infrastructure Management tab of the Administrator view of BMC Impact Explorer. The adapter cell is automatically registered with the Impact Administration Cell (IAC) if the two components are installed on the same computer.Configuration During the installation process. Figure 28 Adapter cell group Configuration If you install the adapter cell on the same computer as the Impact Administration Cell (IAC) and the Publishing Server.dir file of the adapter cell and then restart the adapter cell to recognize the entry. the adapter cell is automatically registered with the IAC.

2. 170 BMC Impact Solutions Service Modeling and Publishing Guide . export ORACLE_BASE TNS_ADMIN=/usr/oracle/product/10. 2 Navigate to the adapter cell. A user/password dialog box appears. For example (the values you set for your variables depend on your installation): ORACLE_HOME=/usr/oracle/product/10. export ORACLE_HOME ORACLE_SID=openview export ORACLE_SID ORACLE_BASE=/usr/oracle. To set the HP OVO administrator password 1 Click the Infrastructure Management tab of the Administrator view of BMC Impact Explorer. you must configure the /etc/profile environment variables. NOTE The adapter cell does not support high availability.dir file in the MCELL_HOME/etc/ directory on the computer where the Publishing Server is installed and then restart the Publishing Server.map ovcifetcher. export TNS_ADMIN PATH=$ORACLE_HOME/bin: export PATH The configuration files.0. you must add an adapter cell entry in the mcell. listed in Table 38.2. 3 Right-click on the adapter cell and choose Actions => OVO Adapter => Set OVO User/Password.pass Integration with HP OVO configuration files Purpose configuration file similar to the mcell.1/network/admin.Configuration If you install the adapter cell on a different computer than the Publishing Server.1.conf ovcifetcher.0.conf file map file used for mapping classes and slots between HP OVO and SIM encrypted password file for the HP OVO administrator Setting the password for the HP OVO administrator This section lists the step-by-step instructions for setting the password for the HP OVO administrator user. Table 38 File ovcifetcher. Before you attempt to import HP OVO data. Do not attempt to configure an adapter cell to run in a high availability environment. reside in the MCELL_HOME/etc/ directory.

If these values are not present in both places. Configuration requirement to support CMDB 2. incident creation fails.Configuration 4 Supply your user name and password and click OK. update the values in the ovcifetcher. To use BMC Atrium CMDB version 2. type. These values are customizable.5. To configure the CTI values in the integration for HP OVO map file. IBRSD looks for this CTI mapping in the map file and the Product Company Relationship form.Hardware Type .5 Depending on which version of the BMC Atrium CMDB you use. Chapter 7 Creating a service model by importing HP OVO data 171 . To successfully create an incident. you must edit the ovcifetcher. and item (CTI) values in the integration for HP OVO map file and the corresponding Product Company Relationship form in Remedy ITSM.map file found in $MCELL_HOME/etc folder. the changes must be made in both the map file and the Product Company Relationship form.map file to uncomment only one of the two version support lines.Machine Item .1 or CMDB 7. you must update the category.BMC Discovered These values must match the corresponding values in the Remedy ITSM Product Company Relationship form. uncomment the following line: $DoMap(SetTypeItemForCMDB21Map) To use BMC Atrium CMDB version 7.1. For example: s s s Category . uncomment the following line: #$DoMap(SetTypeItemForCMDB75Map) Configuration requirement to support BMC Remedy ITSM If you employ Remedy ITSM and the Integration for BMC Remedy Service Desk with SIM for automated incident creation. so if you make changes to any of the values.

Fetch Node Group.Importing HP OVO data to create a service model Importing HP OVO data to create a service model This section provides a high-level explanation of how the integration with HP OVO works and lists the detailed steps you take to import HP OVO data into your service model. 5 For Atrium-enabled scenarios. for example. 172 BMC Impact Solutions Service Modeling and Publishing Guide . 2 A fetch routine retrieves the requested node group data from HP OVO and passes that data to the adapter cell for CI de-duplication and creation of CIs and relationships. 3 The adapter cell passes the data to the publishing server. if necessary. Steps to import HP OVO data to create a service model This section lists the step-by-step instructions for importing HP OVO data to create a service model. the Publishing Server publishes the service model data directly to a cell. any subsequent changes made in the Service Model Editor take precedence over subsequent changes made in the HP OVO interface if those changes are for the same attributes. the Publishing Server first sends the service model data to the BMC Atrium CMDB for reconciliation before the final service model data is published to the cell. High-level data flow This section explains in basic terms how the integration with HP OVO imports data into service models in both Atrium and non-Atrium environments. 4 In non-Atrium scenarios. NOTE After a service model has been created by importing HP OVO data. against the adapter cell. 1 A user initiates or schedules a fetch remote action.

6 Click OK. choose the retrieved group or node bank to display the new service model. 7 Click OK to dismiss the status dialog box. the fetch process can take several minutes to execute. 8 Navigate to the Services view of BMC Impact Explorer. A dialog box displays to confirm the fetch operation. 4 Click Fetch to continue the action. An action confirmation dialog box appears. Depending on the number of CIs to retrieve. the publish process might not be complete. a dialog box appears that provides the status of the process. 2 Navigate to the adapter cell. These events can be used for debugging purposes if errors occur during the fetch process.Steps to import HP OVO data to create a service model To import HP OVO data to create a service model 1 Click the Infrastructure Management tab of the Administrator view of BMC Impact Explorer. Chapter 7 Creating a service model by importing HP OVO data 173 . TIP The process generates events as CIs and their relationships are fetched. A user authentication dialog box appears. This dialog box requires your remote execution user name and password. 10 In the Results window in the Find Service Components navigation area. 5 Supply your user name and password and click OK. 3 Right-click on the adapter cell and choose Actions => OVO Adapter => Fetch From OVO. As the fetch process continues. You can view these events in the Events view of BMC Impact Explorer. 9 If not already selected. If the group or node bank does not yet appear. select the cell to which the service model is published.

00# crontab -l 09 14 * * 1-5 . make sure you set the environment /etc/profile/. for example: bash-3. use the UNIX crontab command on the computer where the adapter cell is installed. /etc/profile && sleep 5 && /opt/bmc/Impact/server/bin/cifetcher. every day of the month except Saturday and Sunday. the fetcher runs once at 2:09 p.m. 174 BMC Impact Solutions Service Modeling and Publishing Guide .Scheduling a fetch to import HP OVO data Scheduling a fetch to import HP OVO data To schedule a fetch to import HP OVO data.sh script.sh start In this example. To enable the cifetcher.

. . This chapter provides information on managing the BMC Impact Publishing Server and contains these topics: Working with publication logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About home cell. Examples of advanced environments. . . . . . . . . . . . . . . . . . Defining BMC Atrium CMDB classes for SIM . . . . . Enabling AtriumCMDB Publish publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . home cell alias. . . . ServiceModelSet attribute for components and management data . . . . . . . . . . . . . . . . . . . About SIM management data . . . . . . . . . . . . . . . . . . ServiceModelSet attribute for impact relationships . . . . . . . . . . . . . . . . . . . . . . . About publish environments . . . . . . Defining BMC Atrium CMDB attributes for SIM . . . . . . . Sharing a single log directory between two Publishing Servers. . . . . . Specifying a port for Service Model Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding classes and slots for BMC Impact Publishing Server events . . . . The process of distributing SIM data from the source to the cells is managed and controlled by the BMC Impact Publishing Server component of BMC Impact Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initializing the BMC Atrium CMDB with SIM data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing from the BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing to a BEM cell. . . . . the service model data must be delivered from the BMC Atrium CMDB or the pposter source files to the cells. and cell alias . . . . . . . . . . . . . . . . . High availability and BMC Impact Publishing Server . . . . . . . . . . . Viewing publication history . . . . . . . . . . . . . Chapter 8 Managing BMC Impact Publishing Server 177 177 178 179 180 180 181 181 183 191 192 192 194 193 194 195 195 199 200 202 202 203 204 205 209 175 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using BMC Impact Service Model Editor . Understanding publish environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the generation of events . . . . . . Viewing publication history details . . . . . . . . . . . . . . . . . . . . Creating advanced publish environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring BMC Impact Publishing Server with BMC Impact Manager events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 8 Managing BMC Impact Publishing Server 8 After you create a service model. . Initializing a cell.

. . . . . . . . . . . . . . .Example—creating SIM data in BMC Atrium CMDB from BAROC files . . . . . 213 Publishing from a Direct Publish source. . . . . . . . . 218 Creating an environment for component instances and relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 About class and slot data . . . . . . . . . 219 Initializing a cell from a Direct Publish environment. 220 Examples—using cell aliases for Direct Publish publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Publishing in automated or manual mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 About home cell and cell alias . . . . . . . . . 224 Configuring the Notify ARDBC plug-in . . . . . . . . . . . . . .conf file and parameters . . . . 219 Modifying home cell and cell aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 pserver. . . . . . . . 220 Securing publish environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Enabling Direct Publish publishing . . . . . . . . . . . 231 176 BMC Impact Solutions Service Modeling and Publishing Guide . . . . . . . . . . . . . . . . . . 211 Purging and deleting service model objects . . . . . . . . . . . . . . . . . . . . . 229 Configuring the Notify plug-in for AR server groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BMC Impact Publishing Server includes detailed messages from the different products it communicates with (such as BMC Impact Portal. A request log file exists for every publish request containing detailed information as to why publication failed and must be consulted to diagnose a publication failure. Detailed information about each publication is available in the request log files. It does not offer information about publication status. that is. The Promote and Publish History command displays the status and date and time of requests. The list of recent publications is in reverse chronological order. BMC Atrium CMDB. you can use the Promote and Publish History command in BMC Impact Service Model Editor to review publication information. then select the publication for which you want to see details in the Publication History table area. BMC recommends that you give every promotion a unique description because that makes it easier to locate a specific publish in the BMC Impact Service Model Editor’s publish history. Publish logs can also be retrieved by using the CLI command plog -s <requestId> | plogdisplay -@ (see “plog—Obtaining the XML log for a request” on page 265). Viewing publication history At any time. consult the documentation of the product. choose Tools => Promote and Publish History. s s s s s After you submit a promotion request in BMC Impact Service Model Editor. To view publication history 1 From the menu bar. the promotion results dialog box reports only the success or failure of a promotion. To understand and troubleshoot these messages.Working with publication logs Working with publication logs This section contains general guidelines to remember when working with publication logs. 2 To view publication details. the most recent is listed first. and BMC Impact Managers). including failures. Information in the Publication errors section of the Publish tab can help you troubleshoot publication failures. select the Publish tab. Chapter 8 Managing BMC Impact Publishing Server 177 . Another way to find the correct publication in the publish history is to use the promotion ID. All request logs are available in BMC Impact Service Model Editor's publish history.

By default.properties file located in the BMC_PORTAL_KIT_HOME\appserver\websdk\tools\jboss\server\all\conf\resourc es\en_US\smsConsoleServer directory on the server running BMC Portal. the component type and component name are included. if the column width limit truncates the text. 100 publication log files are saved. You can sort on any column and.conf to modify the default number of logs saved. the first log is deleted. or modify it by editing the pslog_error_solutions. You can change the RequestHistorySize parameter in pserver. To view publication history details 1 From the menu bar. the most recent is listed first. review the failure information. then select the publication for which you want to see details in the Publication History table area. select the failure and click Open in New View. when the 101st log is saved. 3 Click Close. review the detailed information for the publication you selected. A On the Publication Details tab. To open a View with the component instance. choose Tools => Promote and Publish History. 178 BMC Impact Solutions Service Modeling and Publishing Guide . export) requests). The list of recent publications is in reverse chronological order. review the action to correct the problem with publish. Failures are displayed in red. that is. the tooltip displays the complete text string. but also classinfo (for example. NOTE You can replace the action recommended by BMC Software. select the Publication tab. All BMC Impact Publishing Server requests are counted (not only publish and initialization. If the failure is the result of a particular component instance.Viewing publication history details Viewing publication history details This section contains information on viewing publication history details. 2 To view publication details. B On the Publication Errors tab (available only if there were failures associated with the selected publication). add to it. C In the Recommended Action area.

see “pserver. where <host> is the name of the computer on which the Publishing Server is installed. Perform the uninstallation using uninstall_pserver_service. you can share a single log directory between the two instances. For example. you must give both Publishing Servers the same name.Sharing a single log directory between two Publishing Servers Sharing a single log directory between two Publishing Servers If you employ two Publishing Server instances.cmd for Windows or uninstall_pserver_service. then the service must not log on as a "Local System account". To enable two Publishing Servers on different computers to use the same log directory. you can start the other Publishing Server and resume publishing while writing to the same log directory. If the service is allowed to log on using the default.conf file. and %PSName% is ps_<host>. By default.cmd for Windows or install_pserver_service. 2 In the etc/pserver_service. 6 In the pserver. each instance on a separate computer.sh for UNIX. 3 Reinstall the Publishing Server by using install_pserver_service. 4 Update the file MCELL_HOME/etc/pserver. 5 Update the SystemLogDirName attribute for the other Publishing Server. Note that you must use an NFS path name to specify the directory. the account has no access to the remote directory. set the Publishing Server name (variable PS_NAME) to the new name. you must use an NFS path.conf file make sure that the directory path mentioned before SystemLogDirName is accessible. And because the Publishing Server is installed in the MCELL_HOME directory. The service must log on as an account with access to the remote directory. giving it the same shared log directory. which is the default logon.sh for UNIX. When you specify the path for the SystemLogDirName. if the host of a Publishing Server is not up and running.conf to change the attribute SystemLogDirName to the name of the shared log directory. the default path is MCELL_HOME/log/<PSName>. These commands are available from the <MCELL_HOME>/bin directory.conf file. the Publishing Server log directory is at the location %MCELL_HOME%/log/%PSName%. Chapter 8 Managing BMC Impact Publishing Server 179 . To change the name of one Publishing Server to match the other: 1 Uninstall the Publishing Server for which you want to change the name.conf file and parameters” on page 224. NOTE If the log directory is remote and the Publishing Server runs as a service. For more information about the pserver.

you must manually re-execute the publish on the active server with the CLI publish command. you must execute the publish command again. If the specified port is not available when Service Model Manager is started. which means that any port number can be used. change the parameter ServerPort to a specific port number. 180 BMC Impact Solutions Service Modeling and Publishing Guide . High availability and BMC Impact Publishing Server When a publish request is received by the BMC Impact Publishing Server component. For information about the CLI command publish. see “publish—Publishing a service model or viewing instances to be published” on page 283. see “Working with publication logs” on page 108. in the file MCELL_HOME/etc/cellName/smmgr. each cell must have a different port number for the ServerPort parameter in the smmgr. then the publication fails.conf. look in the request log. To determine which server was active for a specific publish. there are default retrials. The default value is 0. but if the specified number of retrials was executed while there was no active server. When the service starts.Specifying a port for Service Model Manager Specifying a port for Service Model Manager The Service Model Manager (smmgr) is a service (or process) that is started by the cell to assist in publishing. then the publish request fails. the Publishing Server automatically connects to the active server (either primary or secondary) and publishes. To specify a fixed port for Service Model Manager. it selects an available ephemeral port. If neither the primary nor the secondary server is active. When a server is active again. You can configure it to listen on a fixed port so that the connection is not prevented when a random port crosses a firewall. and a new retrial will not be executed after one of the servers becomes active. For automated publications.conf file of the cell. If the active server goes down during a publish. start up fails. The request log indicates that neither server is active. If you use more than one cell. For information about publishing logs.

System . and error events. see the Events tab. Table 39 describes the types of events with an example. Users with Full Access and Service Administrator access can monitor the status of BMC Impact Publishing Server in BMC Impact Explorer on the Impact Administration Cell subtab. Also. the IAC creates ADMIN_EVENTs for the control events of BMC Impact Publishing Server.Monitoring BMC Impact Publishing Server with BMC Impact Manager events Monitoring BMC Impact Publishing Server with BMC Impact Manager events This section describes how to monitor the BMC Impact Publishing Server using BMC Impact Manager events. Chapter 8 Managing BMC Impact Publishing Server 181 . For the request. and the location of the configuration file. By default. For more information about Impact Administration Cells. You can view all generated events in BMC IX on the Events tab in the collector "By Location . connection. To modify the BMC Impact Publishing Server events sent to a cell. so you can view the status of the BMC Impact Publishing Server in the Infrastructure Management view of BMC IX. Modifying the generation of events The BMC Impact Publishing Server creates status. and publish request information that describes the internal state of the BMC Impact Publishing Server and its connection to the BMC Atrium CMDB and BMC Impact Manager cells. you should monitor the publish requests to find publication failures. the BMC Impact Publishing Server sends event information to the Impact Administration Cell (IAC). see BMC Impact Solutions Infrastructure Administration Guide. the configuration file for each. If automated AtriumCMDB Publishing is enabled.Publishing Server". you make changes in configuration files. connection.

conf or if this file does not exist. #By default events of all IPS_EVENT concrete subclasses are created #IPSEventClasses=IPS_START.trace Type of event BMC Impact control—status events generated when BMC Impact Publishing Server Publishing Server starts or started stops in a controlled way serverName connection—events connection failure. #IPS_PUBLISH. then MCELL_HOME/etc/pserver.conf file: #--------------------------------------------------------------------------#Events #--------------------------------------------------------------------------#Events tracking Publishing Server’s operation and errors are sent to im #<IPSEventsIM> #IPSEventsIM=<ImpactAdminCell> #By default IPS_EVENTs are generated to the Impact Admin Cell IPSEventsIM=cell.IPS_CONFIG.IPS_CONNECT.trace MCELL_HOME/etc/ps_hostName/ pserver. then MCELL_HOME/etc/pserver. events are sent to the cell named cell. set the IPSEventsIM parameter to the name of the cell that will receive the events.conf MCELL_HOME/etc/ps_hostName/ pserver.conf or if this file does not exist.Admin #Only operation events of the classes listed in IPSEventClasses are created.conf MCELL_HOME/etc/ps_hostName/ pserver.Admin (default Impact Administration Cell). then MCELL_HOME/etc/pserver. then MCELL_HOME/etc/pserver.conf file.Modifying the generation of events Table 39 BMC Impact Publishing Server event generation Example event message Configuration Configuration file location file name on the BMC Impact Manager computer pserver.trace 182 BMC Impact Solutions Service Modeling and Publishing Guide . To modify the generation of events 1 In the pserver.IPS_CLASSINFO #Enabling of error events (IPS_ERROR) is to be configured in pserver.#IPS_IM_CONNECT.conf MCELL_HOME/etc/ps_hostName/ pserver.IPS_STOP.conf pserver.trace or if this does not exist. generated when the BMC Impact Publishing Server makes a connection with one of its surrounding components request—events generated for every publish and classinfo request that is processed by Publishing Server error—events that indicate there is a problem with the correct functioning of the BMC Impact Publishing Server Class validation request failed.conf pserver. EXAMPLE In the relevant section of the pserver. In the example.conf or if this file does not exist.conf serverName exception occurred: xxx pserver.

bmc. Understanding classes and slots for BMC Impact Publishing Server events Table 40 describes the Common Event Model (CEM) slots (defined in CORE_EVENT) and values that are applicable to all events generated by BMC Impact Publishing Server. in the etc/pserver.bmc.com. 2 To generate error events.imobject=DEBUG log4j.ps=DEBUG.imapi=DEBUG #log4j. (a cell name that is not present in the cell directory as it is configured by IMFileDirectoryName).ps=DEBUG. uncomment the following line by removing the # at the beginning of the line.bmc.sms.Understanding classes and slots for BMC Impact Publishing Server events If you enter an incorrect cell name in this file.gw=DEBUG #log4j.logger.trace output file.sms.com.bmc. IPSERROREVENTS 3 Restart the BMC Impact Publishing Server service or process.imapi.imapi.trace file: # Print messages of level DEBUG or above in the package #log4j. Chapter 8 Managing BMC Impact Publishing Server 183 .logger. EXAMPLE In the relevant section of the pserver.sms. the error message is Unable to report ips events to im X: IPSEventsIM points to unregistered im.sms.bmc. then no events are generated.logger.com.bmc. In the tmp/ps_hostname/pserver.logger.sms.com.nls=DEBUG #log4j. #log4j.com.logger.logger.com.sms.trace file. IPSERROREVENTS as shown in the example.

The class hierarchy for IPS_EVENT is 184 BMC Impact Solutions Service Modeling and Publishing Guide .Understanding classes and slots for BMC Impact Publishing Server events Table 40 Slot name Common Event Model (CEM) slots Description high-level normalized category of the object the event represents identifies the class of an object Default value OPERATIONS_MANAGEMENT Slot label in BMC IX mc_event_category Category mc_object_class Object Class s for status events of the publishing server itself = BMC Impact Publishing Server for status events of the automated publishing service of the publishing server = BMC Impact Publishing Server Automated Publishing s mc_object mc_host_class mc_host mc_host_address Object Host Class Host Host Address name of the BMC Impact Publishing Server instance type of host ps_hostname Computer name of the computer on which BMC not defined Impact Publishing Server is running network address of the host computer on which BMC Impact Publishing Server is running identifies the event management system type not defined mc_origin_class mc_origin Origin Class Origin BMC Impact Publishing Server ps_hostName specifies the event management system that is “closest” to the source of the event and is considered to have detected the event mc_tool_class mc_tool Tool Class Tool the way in which the incident is reported to the cell defines where any event is within a value that can further distinguish where the event is coming from within the mc_tool_class value IP address of the host computer on which BMC Impact Publishing Server is running BMC Impact Publishing Server ps_hostName mc_tool_address Tool Address not defined Event classes and slots specific to BMC Impact Publishing Server The event classes that are specific to BMC Impact Publishing Server are subclasses of the class IPS_EVENT.

In addition to operational events. all operational events are generated. Table 41 Slot name process_run_id IPS_START slots Slot label in BMC IX Process Run ID Description All IPS_CONTROL events that are generated from the same processing run of BMC Impact Publishing Server are assigned the same process run ID (guid) for easy correlation of these events. and IPS_CLASSINFO. IPS_STOP. IPS_CONNECT. which are the event classes IPS_START. IPS_CONFIG. located in the MCELL_HOME\etc\default\EM\kb\classes directory.baroc file.Understanding classes and slots for BMC Impact Publishing Server events IPS_EVENT IPS_CONTROL IPS_START IPS_STOP IPS_CONFIG IPS_CNX IPS_CONNECT IPS_IM_CONNECT IPS_ERROR IPS_REQUEST IPS_CLASSINFO IPS_PUBLISH These classes are defined in the ips. IPS_IM_CONNECT. IPS_PUBLISH. value is the string status indicates the status of BMC Impact Publishing Server: s s mc_parameter Status mc_parameter_value Parameter Value as it launches: starting when up and running: started IPS_STOP—Impact Publishing Server stop The IPS_STOP class contains events that occur when the BMC Impact Publishing Server service (or process) is stopped. When you enable event generation to a SIM cell. IPS_START—Impact Publishing Server start The IPS_START class contains events that occur when the BMC Impact Publishing Server service (or process) is started or when automated publishing is started. Chapter 8 Managing BMC Impact Publishing Server 185 . you can also enable the generation of BMC Impact Publishing Server error events of the class IPS_ERROR.

conf is the default file contains the absolute path of the kb directory contains the absolute path of the log directory contains the absolute path of the cell directory file (default is mcell. contains the version of the Publishing Server contains the software build number of the Publishing Server contains the build date of the Publishing Server contains the absolute path of the home directory for the Publishing Server contains the absolute path of the configuration file. as shown in Table 43. default is INFO value is the string status indicates the status of the BMC Impact Publishing Server: s s process_run_id severity mc_parameter Severity Status mc_parameter_value Parameter Value when stopping: stopping when stopped: stopped IPS_CONFIG—Impact Publishing Server configuration file The IPS_CONFIG class contains events that are generated when BMC Impact Publishing Server starts and display configuration information for the Publishing Server instance. seriousness of the event.dir) Process Run ID ps_version ps_build_number ps_build_date home_dir conf_file kb_dir log_dir mcell_dir IPS Version IPS Build Number IPS Build Date Home Directory Configuration File KB Directory Log Directory Cell Directory File 186 BMC Impact Solutions Service Modeling and Publishing Guide . Table 43 Slot name os_class os_version process_run_id IPS_CONFIG slots (part 1 of 2) Slot label in BMC IX OS Class OS Version Description indicates the class of the operating system indicates the version of the operating system All IPS_CONTROL events that are generated from the same processing run of BMC Impact Publishing Server are assigned the same process run ID (guid) for easy correlation of these events. Event generation for this class is enabled by default. pserver.Understanding classes and slots for BMC Impact Publishing Server events Table 42 Slot name IPS_STOP slots Slot label in BMC IX Process Run ID Description All IPS_CONTROL events that are generated from the same processing run of BMC Impact Publishing Server are assigned the same process run ID (guid) for easy correlation of these events.

destination Destination type of the component to which BMC Impact Publishing Server is connecting.trace if the default file trace_conf trace_file IPS_CONNECT—Impact Publishing Server connect The IPS_CONNECT class contains events that occur when BMC Impact Publishing Server tries to establish a connection to other components.trace is the default file contains the absolute path of the trace file. possible values are: s s s CMDB for BMC Atrium CMDB IM for BMC Impact Manager SMM for Service Model Manager dst_name dst_location dst_user Destination Name Destination Location Destination User name of the component to which BMC Impact Publishing Server is connecting host and port number of the computer to which BMC Impact Publishing Server is connecting logon used to connect blank for Impact Manager and Service Model Manager connections because those connections do not require authentication result Result indicates the success or failure of the connection.Understanding classes and slots for BMC Impact Publishing Server events Table 43 Slot name IPS_CONFIG slots (part 2 of 2) Slot label in BMC IX Trace Configuration File Trace File Description contains the absolute path of the trace configuration file. For every request. Table 44 Slot name ips_request_id IPS_CONNECT slots Slot label in BMC IX Request ID Description the ID of the request sent to the BMC Impact Publishing Server The connection is required for the processing of the request. pserver. possible values are s s SCS when the connection succeeds FLR when the connection fails Chapter 8 Managing BMC Impact Publishing Server 187 . pserver. IPS_CONNECT events are created for every component that needs to be connected.

a request for a publishing preview). EnvId=PROD. request_id Request ID the ID of the request sent to the BMC Impact Publishing Server This ID is necessary when you retrieve the request log by using a BMC IX local action and is useful in diagnosing publication failures. 188 BMC Impact Solutions Service Modeling and Publishing Guide . Queue=T) This is the internal communication protocol. the severity is INFO. Table 45 Slot name dst_location2 IPS_IM_CONNECT slots Slot label in BMC IX Destination Secondary Location Description host and port number of the secondary Impact Manager server.Understanding classes and slots for BMC Impact Publishing Server events IPS_IM_CONNECT—Impact Publishing Server connect The IPS_IM_CONNECT class contains events that occur when BMC Impact Publishing Server tries to establish a connection to an Impact Manager cell. Table 46 Slot name severity IPS_REQUEST slots (part 1 of 2) Slot label in BMC IX Severity Description enables you to follow the status of a request When the request is sent to the BMC Impact Publishing Server. if high availability is enabled IPS_REQUEST—BMC Impact Publishing Server request The IPS_REQUEST class contains events that occur when BMC Impact Publishing Server receives a request (for example. When the BMC Impact Publishing Server finishes the processing of this request. this slot displays the ReconJobRunId and the PromotionId. useful for debugging. See “Diagnosing publication failures” on page 298. it updates the severity of the event: s s OK if the request is successful WARNING if the request failed client_data Client Data data coming from the client For automated publishes resulting from a BMC Impact Service Model Editor promotion. request_msg Request Message the content of the request (for example.

this slot displays the BMC Impact Service Model Editor logon user ID. For publishes from a CLI. this slot displays the BMC Impact Service Model Editor promotion comment. user_id User ID the logon user ID of the requestor For automated publishes that are invoked from a BMC Impact Service Model Editor promotion. Chapter 8 Managing BMC Impact Publishing Server 189 . request_result result_msg Result Message brief description of the success or the failure of the handled request For example. You can find more detailed failure messages in the request log. Request failed: Publish verification of IM(s) failed. For publishes from a CLI.Understanding classes and slots for BMC Impact Publishing Server events Table 46 Slot name IPS_REQUEST slots (part 2 of 2) Slot label in BMC IX Request Result Description initially UNK (unknown) Set to SCS (success) or FLR (failure) when processing is terminated. this slot displays the description you enter when using the -s option. this slot displays the user of the CLI or publish@hostname if the CLI is run locally without authentication. description Description the description that comes with the request For automated publishes resulting from a BMC Impact Service Model Editor promotion.

or with the CLI command pclassinfo -x 190 BMC Impact Solutions Service Modeling and Publishing Guide . when you use a CLI to verify the class definitions between a cell and the BMC Atrium CMDB. possible values s s s direct when the publish request is for a DirectPublish init when the publish request is an initialization. as with automated publish or with the publish CLI command selected_publish when a publish request is for selected objects. as with the publish -d CLI command env_id Environment ID ID of the publish environment For example: s PROD for production environment s TEST. Table 47 Slot name publish_type IPS_PUBLISH slots Slot label in BMC IX Description are s Publish Request Type indicates the type of publish. possible values are s validation when the classInfo request happens with the CLI command pclassinfo n cellName s export when the classInfo request is generated with BMC Impact Service Model Editor export meta data functions.user. for example.1 for BMC Impact Service Model Editor test environment IPS_CLASSINFO—BMC Impact Publishing Server class information request The IPS_CLASSINFO class contains events that are generated when information about classes is requested. Table 48 Slot name classinfo_type IPS_CLASSINFO slots Slot label in BMC IX Class Info Request Type Description indicates the type of classinfo.Understanding classes and slots for BMC Impact Publishing Server events IPS_PUBLISH—BMC Impact Publishing Server publish request The IPS_PUBLISH class contains events that occur when a request for a publish is generated. as with the pinit cli publish when the publish request is a delta or incremental publication.

init or close Table 50 Slot name origin_id env_id env_type About SIM management data Management data are the data that are referred to by component instances and impact relationships. Table 49 Slot name severity IPS_ERROR slots Slot label in BMC IX Severity Description indicates the seriousness of the event The default is WARNING IPS_ENV—BMC Impact Publishing Server environment request Each time a penv CLI is issued (except for the action command info). a SIM management data instance can be published once and only once to a cell. Management data is always published to all cells of a publish environment. Chapter 8 Managing BMC Impact Publishing Server 191 . in the case of the same priority publish origin. They report issues that occur with the BMC Impact Publishing Server. while other IPS_EVENTs report information. set. A SIM management data instance of a higher priority publish origin might replace the same SIM management data instance of a lower priority publish origin. an IPS_ENV event is generated. IPS_ENV events are generated for these environment requests: s s s s creation of a publish environment modification of a publish environment initialization of CMDB datasets of a AtriumCMDB? publish environment removal of a publish environment IPS_ENV slots Slot label in BMC IX Origin ID Environment ID Environment Request Type Description contains the origin ID (AtriumCMDB or DirectPublish) of the publish environment contains the IDs of the publish environment contains the action open.About SIM management data IPS_ERROR—BMC Impact Publishing Server errors IPS_ERROR events are different from other events in the IPS_EVENT class. A default set of management data is in the kb/data directory of the cell as well as in the SIM CMDB extension and in the kb/data directory of the BMC Impact Publishing Server. However.

Understanding publish environments A publish environment defines the source of the data and the cells to which the data is sent. If the source of the service model data is a BAROC file and the data goes to a production cell.Understanding publish environments Each component and impact relationship of a cell can refer to each management data instance regardless of the source of the management data in the cell (Direct Feed or AtriumCMDB publishing or DirectPublish publishing or CellPublish publishing). Publish origin BMC Atrium CMDB Publish is initiated from s s s OriginID AtriumCMDB BMC Impact Service Model Editor termination of reconciliation job CLI command publish CLI command pposter HP OVO fetch termination CLI command publish Direct Publish Cell Publish s s s DirectPublish CellPublish 192 BMC Impact Solutions Service Modeling and Publishing Guide . For example. which is referred to as Cell Publish Feed. Direct Feed management data can also be referred to by published CIs and relationships. This set of conditions is referred to as a publish environment. which is referred to as an Atrium Publish Feed. About publish environments A publish is always executed within a set of conditions defined by the requirements of the SIM data. you want to send a service model from BMC Atrium CMDB (one condition) to a test cell (second condition). from BAROC source files using the CLI command pposter. or from a staging cell like the HP OVO adapter cell. which is referred to as Direct Publish Feed. The BMC Impact Publishing Server component supports publishing SIM data (service model data and management data) from three sources or origins: BMC Atrium CMDB. this requires a different environment and is handled differently by BMC Impact Publishing Server. You can secure publish environments by password protecting them. The management data need not be published to be referred to by published CIs and relationships.

CellAliases and HomeCell are parameters of the publish environment. A cell can have multiple cell aliases. for example. However. home cell alias. The environment’s parameter home cell defines the one cell to which all service model data and management data is sent. and the attributes HomeCell and HomeCellAlias are used by BMC Impact Publishing Server to determine the cells to which a component instance is sent. a cell can have only one cell alias. it is simpler and easier to manage if all publish environments in your enterprise have unique identifiers. In other words. The parameters. The environment identifier must be unique within all AtriumCMDB Publish environments or within all Direct Publish environments. Chapter 8 Managing BMC Impact Publishing Server 193 . The component’s attribute home cell alias defines another name for home cell looked up from a table so that the data with a specific home cell alias can be sent to different cells for different publish environments. and cell alias A service model component can be assigned to only one cell at a time. to assign a component to a production cell and. depending on which have values. Specifying the publish origin Publishing from these origins is enabled or disabled with configuration parameters (AtriumCMDBPublishOrigin and DirectPublishOrigin and CellPublishOrigin) in the pserver. If you want. CellAliases. AtriumCMDB Publish is enabled by default and is initiated either through automated publishing or the CLI command publish. at the same time. Direct Publish is enabled by default and is initiated either through an API program or the CLI command pposter. whereas HomeCell and HomeCellAlias are attributes of the component instance. but in a single publish environment. and cell alias An environment is uniquely identified by EnvID plus OriginId. there can be only one cell name. Cell Publish or within all CellPublish environments in a staging cell.conf file. HomeCell. use it in a test cell for impact experiments.About home cell. The mapping of cell alias-to-cell name is one to many per environment. home cell alias. Cell alias defines another name for a cell so that data can be sent to more than one cell. for each environment and for each cell alias. a mechanism is needed to make this possible. About home cell. but many cell aliases can be mapped to the same cell name.

Publishing from the BMC Atrium CMDB In the case of AtriumCMDB Publish environments. the Publishing Server creates a default cell alias mapping to the cell that is configured for the BMC Atrium CMDB PROD publish environment. although you can publish CIs on a BEM cell. then its cell name is used as the default cell. even if it is also used in AtriumCMDB environment. publishing of the objects to the cells 194 BMC Impact Solutions Service Modeling and Publishing Guide . s you can promote SIM objects in the BMC Impact Service Model Editor product.3. 2. the BMC Impact Publishing Server uses the following algorithm: 1. Leaving this parameter empty effectively drops CIs and impact relationships assigned to DefaultCell from publication. that value is used (regardless of the values in the component’s HomeCellAlias attribute).Publishing to a BEM cell A cell name can only be used in one AtriumCMDB Publish environment. Every component that has no HomeCellAlias set is published to this default cell. you can publishing on a BEM cell. Default home cell alias When the parameter DefaultCell is set. The component’s HomeCellAlias is looked up in the CellAliases for the publish environment. which triggers reconciliation and when that terminates. If HomeCell is defined for the publish environment. Determining the cell to which a component is published To determine the cell to which a component is published. Publishing to a BEM cell As of version 7. By default the CIs and impact relationships are assigned to the cell that is set for the DefaultCell parameter.00. the impact relationships of the CIs are not propagated. However. however it can be re-used in many DirectPublish environments. 3. Cell-alias to cell-name values must already be defined when publishing is initiated. If one of the CellAliases defined for the publish environment has empty CellAlias.

based on choices you make in the BMC Impact Service Model Editor you can create other AtriumCMDB Publish environments for advanced staging. BMC Impact Publishing Server defines the proper publishing environment based on choices you make in BMC Impact Service Model Editor and can automatically deliver the SIM data to the cell after you promote the objects in BMC Impact Service Model Editor.) For AtriumCMDB environments. the BMC Impact Publishing Server component can handle all of the requirements for standard publishing. in which case. these changes are sent to the cells. Enabling AtriumCMDB Publish publishing AtriumCMDB Publish is enabled by default. s s During the publishing of a service model.ASSET dataset of BMC Atrium CMDB. This default can have a performance impact if too many CIs exist in non-SIM classes. The Impact Administration Server (IAS) creates this information whenever you administer a cell. located in MCELL_HOME/etc. (Default = T. new or modified service model components and their relationships are selected from the asset dataset in the BMC Atrium CMDB and copied to respective BMC Impact Manager cells. If the impact is too great.Enabling AtriumCMDB Publish publishing s you can reconcile from any BMC Atrium CMDB reconciliation dataset you can use the Send to test function in BMC Impact Service Model Editor. Using BMC Impact Service Model Editor When the source of the service model data is the BMC Atrium CMDB and you are using BMC Impact Service Model Editor.conf file. with a parameter in the pserver. In this case. Chapter 8 Managing BMC Impact Publishing Server 195 . ServiceModelPublish = T. then you can revert and set the default value for ServiceModelSet to OUT. the new objects coming from a discovery source are ignored by the Publishing Server and you must bring In-Model objects in the Service Model Editor. cell information is looked up from the class SIM_CellInformation from the BMC. the parameters of the environment are defined and managed for you. New objects coming from a discovery source (such as BMC Topology Discovery or BMC Foundation Discovery) are flagged by default as In-Model and are therefore published by BMC Impact Publishing Server. If discovery sources provide updates to objects that are flagged as In-Model. for which you define the parameters of the environment using the CLI command penv.

s When you register a cell in BMC Impact Portal and define it as production. For each component’s cell name. it is not necessary for you to understand the concept of cell alias because these values are created and managed for you. When you send service model objects to test in the BMC Impact Service Model Editor (using the Send to test function). testcell1. cellB.Using BMC Impact Service Model Editor About cell alias When you use only the BMC Impact Service Model Editor to create service models. an alias with the same name as the cell name is defined and stored in the SIM_CellAlias CMDB class in the dataset BMC. 196 BMC Impact Solutions Service Modeling and Publishing Guide . In BMC Impact Service Model Editor. and cellC. Cell alias cellA cellB cellC Cell name (prod cell) cellA cellB cellC Cell name (test cell) testcell1 testcell1 testcell1 s Component SL Appl SL DB SL Server In production the three component instances are sent to the production cells: cellA. a cell alias is automatically created and managed by BMC Remedy AR System. all existing aliases are mapped to the test cell you chose for the test in BMC Impact Service Model Editor.ASSET. they are all sent to the same test cell. When you send them to test in BMC Impact Service Model Editor. every component instance that is created or modified must have a value for cell name (required field).

IMPACT.ASSET.PROD upon successful publication. these changes are reconciled in the production dataset and then stored in the production dataset BMC.EnvId and an impact dataset. The production AtriumCMDB publish environment has the following two datasets: Datasets in BMC Atrium CMDB asset dataset: by default. the data in the impact dataset should be managed solely by BMC Impact Publishing Server. BMC.Using BMC Impact Service Model Editor About the production environment An AtriumCMDB Publish environment consists of an asset dataset. by default BMC. WARNING To ensure that the service model data in the BMC Atrium CMDB and in the cell are synchronized. BMC. can be updated only by the CMDB Reconciliation Engine as objects are reconciled not limited to objects that are in-model a service model object is successfully promoted when it is moved from the sandbox to this dataset in the BMC Atrium CMDB read-only: can only be updated by the BMC Impact Publishing Server as objects are published a service model object is successfully published when a copy of it is in this dataset in the BMC Atrium CMDB impact dataset: by default. which mirrors the last successful publish to the cells.ASSET This is the dataset from which service model data is published to cells.EnvId.IMPACT.IMPACT.ASSET. After you promote service model objects in BMC Impact Service Model Editor. Chapter 8 Managing BMC Impact Publishing Server 197 . regular dataset s s Description contains objects to be published Comments s read-only. BMC.PROD contains objects that have been successfully published This dataset is a “master copy” of the service model data in the asset dataset regular dataset s s The production service model data is in the BMC Atrium CMDB in the production dataset BMC.

WARNING To ensure that the service model data in the BMC Atrium CMDB and in the cell are synchronized. The BMC Impact Service Model Editor test publish environments have an overlay asset dataset. The last successful publish to the test cells is mirrored in the impact dataset BMC.user. The test environment consists of two datasets: s s asset dataset BMC.Test. The BMC Impact Publishing Server then looks up the test cell for the cell alias of every component.1 datasets for the environment.IMPACT.user.user.Test. Test objects cannot be added to the Console Navigation Tree in BMC Impact Service Model Editor.user. only the BMC Impact BMC Impact Publishing Server should modify the data in the impact test dataset. Any previous objects are removed.Using BMC Impact Service Model Editor About test environments When you select Send To Test Objects In Current View in BMC Impact Service Model Editor.Test.1.TEST. s 198 BMC Impact Solutions Service Modeling and Publishing Guide .IMPACT. To be able to cut down the test to a limited number of components and impact relationships the publish mode Current is used for PublishModeServiceModel.IMPACT. which means they cannot be monitored in BMC Impact Portal. a request is sent to the BMC Impact Publishing Server to open a test environment. After a successful publish.ASSET.1 impact dataset BMC.user.ASSET.1 BMC Impact Service Model Editor puts the service model data that was sent to test into the asset dataset (BMC.1 and BMC.1) of the new test environment and requests a publication from the BMC Impact Publishing Server.user.Test. The Send to Test function s s s s validates the existence of or creates a test publish environment for the user validates the existence of an available test cell for publishing updates entries in the Cellalias table for the current environment empties test datasets of previous contents A test cell contains only the latest objects sent to test. the BMC Atrium CMDB contains entries in the BMC. s To have all management data instances of the production dataset in the test environment. with the production dataset as underlying dataset.ASSET.TEST. publish mode Overlay is used for PublishModeMgmtData.

you can assign a home cell by s s defining it in the CLI command penv when you define the environment defining it after the environment is opened in a CLI command penv with the action command set Chapter 8 Managing BMC Impact Publishing Server 199 . Determine the source of the service model data (another environment or a BAROC source file). the cell is automatically initialized with SIM management data of the asset dataset of the environment when you execute the CLI command publish. 6. on the Services tab See Appendix A. For more information about these topics. Publish the objects to the cell. If cells are running. this initializes cells with this data.Creating advanced publish environments Creating advanced publish environments To do advanced publishing for SIM data in AtriumCMDB Publish environments. In an AtriumCMDB Publish environment. Register any new cells in BMC Impact See BMC Impact Solutions Infrastructure Portal (which automatically creates them Administration Guide in BMC Atrium CMDB). Troubleshooting Execute a CLI command penv open Execute a CLI command penv init You use the CLI command penv and the pclient. 5. Enter the data in the BMC Atrium CMDB. Monitor services. you need to Table 51 Basic steps 1. 7. 8. Use the penv init parameters SourceEnvMgmtData and SourceEnvServiceModel or SourceBarocMgmtData and SourceBarocServiceModel Create a BAROC source file. Home cell and home cell alias If all component instances and relationships are being published to one cell.conf file to create. see “penv— Managing publish environments” on page 252. modify. Define the environment. 3. Execute a CLI command publish In BMC Impact Explorer. Determine the cells to use and create if necessary. Troubleshoot problems. 4. Basic steps to create advanced test environments How to do See BMC Impact Solutions Infrastructure Administration Guide 2. and delete publish environments.

SIM.CONFIG:SIM_CellAliases. 200 BMC Impact Solutions Service Modeling and Publishing Guide . All service model data in that environment is published to the cell specified in HomeCell. cell aliases. For larger service models. In this way. Examples of advanced environments You use the Send to test function in BMC Impact Service Model Editor to test small service models. s s s set the attribute EnvId to the ID of the publish environment set the attribute CellAlias to the alias set the attribute CellName to the name of a cell that is registered in BMC Impact Portal (registered in the class SIM_CellInformation) You can set a default cell by setting CellAlias to null. then cell aliases are required. The values that are assigned at the time of publishing are also stored in the dataset BMC. The penv command allows for staging scenarios like the following: Example 1—Creating two service models for two departments This approach is best suited for testing large service models where the effort to automate the tasks by script is acceptable in light of the volume of data being tested. Using Remedy User or an API program.ASSET dataset in the BMC Atrium CMDB class BMC.ASSET. you must assign cell alias-to-cell name values (per environment) in the BMC Atrium CMDB in instances of the BMC. you want to test two separate service models for two different departments. At the beginning of a BSM project. even if HomeCellAlias contains a cell alias that points to another cell. are ignored. as defined in the BMC Atrium CMDB.IMPACT. more advanced staging and testing options are available with the CLI command penv.Examples of advanced environments If home cell is defined.SIM. Cell aliases If you do not have home cell defined. the attribute HomeCellAlias for individual CIs is not required to publish.PROD.CONFIG:SIM_Cellaliases like Environment EnvId CellAlias CellName arwad then every CI in BMC. If you create an instance in the BMC Atrium CMDB class BMC.EnvId that has no value in HomeCellAlias is published to the cell arwad.

SIMULATION. For the simulation publish environment. it is possible to publish a single service model (the data in an asset dataset) to multiple environments. Reconcile the staging asset datasets into the production dataset. The last successful publish of the simulation publish environment SIMULATION is saved in BMC. 3.ASSET. execute a command similar to the following: EXAMPLE penv -e SIMULATION -p “AssetDataSetId=BMC.ASSET” -p “HomeCell=simulation” Chapter 8 Managing BMC Impact Publishing Server 201 . After an initial publication. Both the production publish environment and the simulation publish environment use the production asset dataset BMC.ASSET. modifications are published incrementally.dept1 and BMC.IMPACT. Example 2—Publishing a single service model to multiple environments Additionally. by executing the following command: EXAMPLE >penv open -e dept1 >penv open -1 dept2 2. you can send the service model to production cells (for real-life monitoring and impact analysis) and send the same service model data to a test cell to experiment with the impact of component failure.ASSET dataset triggers an automated publish on both environments. A reconciliation merge to the BMC.ASSET. When you are satisfied with the results.Examples of advanced environments 1. the HomeCell parameter of the publish environment is defined.PROD. Reconciliation merges to the BMC.ASSET.ASSET. The components and impact relationships for each department are loaded from BAROC files. then your simulation publish environment would use an overlay asset dataset BMC. Alternatively. if you want to do simulations on a service model that is derived from the production service model.dept2. The last successful publish of the production publish environment is saved in BMC.SIMULATION with underlying dataset BMC. the staging asset datasets can be reconciled into the production dataset.ASSET dataset will trigger an automated publish (if enabled) on the simulation publish environment. To create a simulation publish environment that uses the production asset dataset. in the respective asset datasets BMC.IMPACT. You define two environments for the two different departments. For example.

Export the modified SIM class information by executing the CLI command pclassinfo -x. You can qualify attributes that are not defined as SIM attributes out-of-the-box. In order to be published to SIM. Defining BMC Atrium CMDB attributes for SIM Not all of the CMDB attributes of SIM classes are useful for SIM. In Remedy User's Class Manager Console.Defining BMC Atrium CMDB classes for SIM This command creates only the simulation publish environment. For more information. You can qualify classes that are not defined as SIM classes out-of-the-box. 3. Export the modified SIM class information by executing the CLI command pclassinfo -x. add the value 300050 to the existing Custom Properties. not the production publish environment. add the value 100050 to the existing Custom Properties. see “Adding new classes to the BMC Atrium CMDB” on page 157. 202 BMC Impact Solutions Service Modeling and Publishing Guide . To define a class as a SIM class 1. BMC Atrium CMDB classes must have the attribute Custom Properties = 100050. To define an attribute as a SIM attribute 1. In order to be published to SIM. 2. 2. which should already exist since it is created by default. Update the Knowledge Base of the cells and recompile. To create a simulation publish environment with an overlay asset dataset: EXAMPLE penv -e SIMULATION -p “AssetDataSetType=Overlay” -p “HomeCell=simulation” -p “AutomatedPublish=T” Defining BMC Atrium CMDB classes for SIM Not all BMC Atrium CMDB classes have component instances that are useful for impact analysis. In Remedy User's Class Manager Console. CMDB attributes must have attribute Custom Properties = 300050.

ServiceModelSet attribute for components and management data All SIM classes in the BMC Atrium CMDB have a ServiceModelSet attribute. If your model as a large number of instances of non-SIM classes. You can also create a Remedy AR filter to set ServiceModelSet IN for cases where the instance should automatically be set IN. s WARNING By default. If this increase in retrieval time is prohibitive. default value OUT_OF_IN indicates the data instance was in the model but has since been removed from the model At the next publication.ServiceModelSet attribute for components and management data 3. the instance is removed from the cell. For a component in the BMC Atrium CMDB to be considered for publishing by BMC Impact Publishing Server. Possible values are listed in Table 52. set the default to OUT. OUT indicates the data instance is not in the service model Out-of-model instances are not published to the cell. This attribute makes it possible for data to be in the BMC Atrium CMDB but not be included in any data published to a SIM cell. the ServiceModelSet attribute is set to IN. The value IN indicates that the CI is included in the service model published to a SIM cell. the time required to retrieve those publishable instances can be significant. Chapter 8 Managing BMC Impact Publishing Server 203 . this attribute must contain specific values: s Only CIs with ServiceModelSet IN or OUT_OF_IN are considered by the BMC Impact Publishing Server. Table 52 Value IN ServiceModelSet attribute values Description (default value) indicates the data instance is in the service model In-model component instances are published to the cell. Update the Knowledge Base of the cells and recompile. The value OUT_OF_IN indicates that the CI is not included in the service model published to SIM.

204 BMC Impact Solutions Service Modeling and Publishing Guide . then the ServiceModelSet value for the impact relationship is IN. then the relationship is defined as OUT_OF_IN. then the relationship is defined as OUT. If either or both are assigned OUT_OF_IN. ServiceModelSet attribute for impact relationships For an impact relationship. See also “In-model and not-in-model component instances” on page 54. the value in ServiceModelSet is calculated from the ServiceModelSet values assigned to the relationships consumer and provider component instances and is determined in the manner shown in Table 53 on page 204. Table 53 Determination of ServiceModelSet value for an impact relationship and if component instance 2 Then value of ServiceModelSet has value for the impact relationship is IN IN OUT_OF_IN OUT OUT_OF_IN IN OUT OUT OUT IN OUT_OF_IN If component instance 1 has value IN OUT_OF_IN IN OUT_OF_IN OUT OUT IN OUT The determination is: s s s If both instances are assigned IN. ServiceModelSet cannot be reset to OUT after it has been IN or OUT_OF_IN.ServiceModelSet attribute for impact relationships To ensure synchronization between the impact dataset in BMC Atrium CMDB and the service model in a SIM cell. If either or both are assigned OUT. Every CI that has a ServiceModelSet value of IN or OUT_OF_IN should have a ReconciliationIdentity defined.

Although possible. existing objects are either removed or kept. When you initialize a specific publish environment. the production dataset is initialized with service model management data. InitEffectivelyMgmtData and InitEffectivelyServiceModel reference the attribute ServiceModelSet. it is unlikely that reinitialization of the production environment will be necessary. Chapter 8 Managing BMC Impact Publishing Server 205 . For more information about initializing a publish environment. Table 54 lists and describes the parameters for initializing. objects in the asset and in the impact dataset of that environment are initialized (as well as objects in the datasets of an environment with asset dataset that overlays the asset dataset of the environment that is being initialized): s in the impact dataset. located in the MCELL_HOME/etc directory.conf configuration file. depending on the values in the InitEffectivelyMgmtData and InitEffectivelyServiceModel parameters new initial objects in asset dataset and in impact dataset are copied from the initialization source (see “Initial source parameters” on page 208) s s Objects in the datasets of an environment with asset dataset that overlays the asset dataset of the environment that is being initialized are also initialized. Two of the parameters. existing objects are removed in the asset dataset.ASSET as the underlying dataset.ASSET or overlay asset dataset with BMC. These parameters are defined in the pclient.Initializing the BMC Atrium CMDB with SIM data Initializing the BMC Atrium CMDB with SIM data SIM requires service management data for successful operations. but are moved outof-model. see also the init action command under “penv—Managing publish environments” on page 252. For publish environments other than those with an asset dataset BMC. Using initialization parameters You use the configuration parameters of the CLI command penv (with the -p option) to define the initialization. initialization of the environment with service management data is required for a successful publication. During installation of SIM’s CMDB extensions.

the DatasetId and the ReconciliationIdentity must be unique. 206 BMC Impact Solutions Service Modeling and Publishing Guide . From its datasets the initial components and impact relationships are copied InitEffectively parameters The two InitEffectively parameters determine the retention of the existing instances in the asset dataset when initializing. In BMC Atrium CMDB. Only the IN and OUT values for ServiceModelSet attribute are taken into consideration. When the objects in the BAROC file have a value in the mc_udid slot. InitEffectivelyMgmtData relates to management data instances. InitEffectivelyMgmtData parameter settings and their results Table 55 lists the possible values for the InitEffectivelyMgmtData configuration parameter and the subsequent actions taken during BMC Atrium CMDB reinitialization.Initializing the BMC Atrium CMDB with SIM data Table 54 Parameter Parameters in the pclient. InitEffectivelyServiceModel relates to component instances and impact relationship instances.conf file for initializing the BMC Atrium CMDB Description determines which management data instances are removed from the BMC Atrium CMDB during initialization or reinitialization. based on the value in the ServiceModelSet class attribute relationship instances are removed from the BMC Atrium CMDB during initialization or reinitialization. based on the value assigned in the SeviceModelSet class attribute InitEffectivelyMgmtData InitEffectivelyServiceModel determines which service model component and impact InitMgmtData InitServiceModel SourceBarocMgmtData SourceBarocServiceModel SourceEnvMgmtData SourceEnvServiceModel specifies whether management data is initialized specifies whether service model data is initialized specifies the BAROC files from which the default or initial management data instances are copied specifies the BAROC files from which initial components and impact relationships are copied specifies the publish environment. keeping existing data may be impossible. From its datasets the default or initial management data instances are copied specifies the publish environment.

all current management data instances are removed from the BMC Atrium CMDB. Therefore. Management data instances with the ServiceModelSet attribute value of IN or OUT_OF_IN are removed from the BMC Atrium CMDB.Initializing the BMC Atrium CMDB with SIM data Table 55 InitEffectivelyMgmtData parameter values and results Resulting actions on asset management data during Atrium CMDB reinitialization If set to this default value. these actions occur s Existing management data instances are kept in the BMC Atrium CMDB. you do not want to keep existing management data instances. In order to keep a backup of custom management data instances. Management data instances with the ServiceModelSet attribute value of IN or OUT_OF_IN have their attribute value reset to OUT. s InitEffectivelyMgmtData= If set to an empty list (default). The default management data BAROC files are stored in the file: MCELL_HOME\etc\ps_hostname\kb\data Chapter 8 Managing BMC Impact Publishing Server 207 . which is useful when you must reinitialize the production environment. you do not move management data in and out of model. which makes it impossible to keep them. In fact. s InitEffectivelyMgmtData parameter setting InitEffectivelyMgmtData=IN. some of the default management data instances have a mc_udid set.OUT InitEffectivelyMgmtData=IN InitEffectivelyMgmtData=OUT Management data instances with ServiceModelSet attribute value of OUT are removed from the BMC Atrium CMDB. s Generally. Instances with the ServiceModelSet attribute value of IN or OUT_OF_IN have their values reset to OUT. export them to BAROC files by using the CLI command mquery.

Generally. OUT_OF_IN or OUT. regardless of the value of ServiceModelSet being IN.Initializing the BMC Atrium CMDB with SIM data InitEffectivelyServiceModel parameter settings and their results Table 56 lists the possible values for the InitEffectivelyServiceModel configuration parameter and the subsequent actions taken during BMC Atrium CMDB reinitialization. you need to browse the existing components and decide if they still need to be in model. Initial source parameters The initial data can come from s s BAROC files another publish environment (asset and impact datasets) 208 BMC Impact Solutions Service Modeling and Publishing Guide . OUT All components and impact relationships. InitEffectivelyServiceModel=IN. are removed from the BMC Atrium CMDB. when reinitializing you do not want to lose components and impact relationships that were already defined or that were detected by a discovery tool. When you reinitialize. these actions occur s InitEffectivelyServiceModel parameter setting InitEffectivelyServiceModel= all service model component or impact relationship instances are not removed from the BMC Atrium CMDB components and impact relationships with the ServiceModelSet attribute value of IN or OUT_OF_IN have their attribute value reset to OUT s The default initialization does not contain any component or impact relationship. InitEffectivelyServiceModel=IN Components and impact relationships with the ServiceModelSet attribute value of IN or OUT_OF_IN are removed from the BMC Atrium CMDB. Table 56 InitEffectivelyServiceModel parameter settings and results Resulting actions on service model asset component instances and impact relationships during BMC Atrium CMDB reinitialization If set to an empty list (default).

IMPACT. then effectively no copies are taken. You reinitialize a cell by using the CLI command pinit.ASSET and BMC.load. the source of service management data for the production publish environment (BMC.PROD) is sent by the BMC Impact Publishing Server to the cells. you reinitialize only when s s s a cell is reinstalled (restart the cell with the -i option) a cell must be restarted for recovery purposes SIM data in the cell is no longer in sync with the data in the BMC Atrium CMDB impact dataset or with the data in the Direct Publish source When you add a new cell alias to an AtriumCMDB publish environment. Typically. the type (Overlay or Regular) and the publish mode (Overlay or Current) is taken into account. existing events are associated with new copies of components. then the baroc instances are copied to the asset dataset and the impact dataset. the BMC Impact Publishing Server automatically initializes it with the service model management data upon the first publication to it. When you initialize cells of an AtriumCMDB publish environment. so status information of component instances is not lost. When only DirectPublish publishing is enabled. For an AtriumCMDB publish environment. it sends the contents of the BMC Atrium CMDB impact dataset to the cells. then the instances from the impact dataset of the source publish environment are copied to the impact dataset of the publish environment that is being initialized.IMPACT. the production environment is the source. Initializing a cell Initialization deletes all existing SIM data (service model data and service management data) of the publish environment from the cell.Initializing a cell By default. Chapter 8 Managing BMC Impact Publishing Server 209 . Likewise. If the source is BAROC files. For other AtriumCMDB publish environments. If the asset dataset is an overlay dataset and the publish mode is overlay and the initialization's source is the underlying asset dataset. the instances from the asset dataset of the source publish environment are copied to the asset dataset of the publish environment that is being initialized. then you have to initialize the new cell with management data manually. In copying to the asset dataset. When a cell is initialized.PROD) is the BAROC files in MCELL_HOME/etc/ps_hostname/kb/data/. If the source is a publish environment. the data in the impact dataset (like BMC.

execute the following CLI command: pinit -n cellName For more information about reinitializing a cell. 210 BMC Impact Solutions Service Modeling and Publishing Guide .Initializing a cell To initialize a cell from the BMC Atrium CMDB production environment. see “pinit—Initializing a cell with service model data” on page 261.

Description='BMC DSM . END BMC_ComputerSystem. HomeCell=lopud. HomeCell=lopud. OwnerContact='713. OwnerName='DSM PSR/I Lab'. mc_udid=test1_obj1<-obj2.918. Creating a BAROC source with component and relationship objects The following BAROC file. the goal is to initialize the publish environment for Dept1 with the default management data instances and with a number of components and impact relationships. sm.918. Description=Application. StatusModel=STANDARD. mc_udid=test1. HostName=test1_S0101_N01. mc_udid=test1_S0101_N01.baroc. END Chapter 8 Managing BMC Impact Publishing Server 211 . OwnerContact='713. OwnerName='DSM PSR/I Lab'. HomeCell=lopud. mc_udid=test1_S0101_N01_A01. Name=test1_S0101.Example—creating SIM data in BMC Atrium CMDB from BAROC files Example—creating SIM data in BMC Atrium CMDB from BAROC files In this scenario. HomeCell=lopud. Description=Computer. provider_home_cell=lopud. END BMC_Application. OwnerContact='713. consumer_home_cell=lopud. Name=test1_S0101_N01. Name=test1_S0101_N01_A01.8800'. OwnerName='DSM PSR/I Lab'. END BMC_Impact.8800'. OwnerName='DSM PSR/I Lab'. consumer_id=test1. defines the components and impact relationships of “dept1”: EXAMPLE BMC_BusinessProcess. provider_id=test1_S0101.918.8800'.PSR and Interoperability Lab Test Business Process'. Name=test1.918. Type='WINDOWS_SYSTEM'. Type=app_type1.8800'. PropagationModel=DIRECT. mc_udid=test1_S0101. OwnerContact='713. END BMC_BusinessService.

the BMC Impact Publishing Server needs to publish them to avoid synchronization problems between cells and BMC Atrium CMDB data. 2 Copy into it the kb/data directory. The cell for Dept1 is running and is initialized immediately when you initialize the BMC Atrium CMDB. the cell has the components and the impact relationships. 3 Define the HomeCell parameter of the Dept1 environment as lopud. deleting the instances from the cells.Purging and deleting service model objects Sending service model data to a cell using a BAROC source file To initialize the publish environment for Dept1 with the default management data instances and a number of components and impact relationships.load" init -v The service model is created in the asset and impact datasets of the AtriumCMDB Publish environment Dept1. and edit the . Purge=F and Merge=T. When the initialization completes. To purge objects from the cells that have been hard deleted (purged) from the asset dataset. By default. Purging and deleting service model objects BMC recommends that service model objects be soft-deleted in BMC Atrium CMDB (MarkAsDeleted=Yes) until the BMC Impact Publishing Server is able to process their deletion. add the file sm_Dept1. the CLI command publish supports two parameters: Purge and Merge.load to add the sm_dept1. Ensure that you have retention rules on the Reconciliation's Purge activities for SIM classes. For manual publishing. Occasionally. then the automated publisher is triggered. execute the following command: publish -p “Purge=T” 212 BMC Impact Solutions Service Modeling and Publishing Guide . if objects are purged from the asset dataset by a reconciliation’s purge activity. 4 Execute the following command: penv -e dept1 -p "SourceBarocServiceModel=etc/kb/data_dept1/. do the following: 1 Create a directory MCELL_HOME/etc/ps_hostname/kb/data_Dept1. For automated publishing. when objects have been purged or hard deleted in BMC Atrium CMDB before being published.

s publishing operates in the background publish is pre-authenticated if you password protect the AtriumCMDB Publish environment publish requests are queued. so the instances that are promoted and reconciled. you disable automated publish and use the CLI command publish.Publishing in automated or manual mode Publishing in automated or manual mode When the source of the service model data is the BMC Atrium CMDB. For more information about publish. the BMC Impact Publishing Server service starts in automated mode. the throughput time of the publication increases all modified instances since the last successful publish are published. This is controlled in the pserver. By default. for example). edit the pserver. Switching between automated publish and manual publish By default. you can control when publishes occur by enabling or disabling automated publish. a new request starts when the one in progress completes if multiple promotion and reconciliation processes are running at the same time. Automated publish considerations When automated publish is enabled. The BMC Impact Publishing Server service (or process) starts in automated mode. and the instances that are published are not necessarily the same s s s s Chapter 8 Managing BMC Impact Publishing Server 213 .conf file and change the value of the parameter AutomatedStartMode to Manual.conf configuration file by the parameter AutomatedStartMode (which is set to Automated). To temporarily switch the mode in which BMC Impact Publishing Server is running. To publish service model objects manually. the BMC Impact Publishing Server automatically publishes service model objects to the cells. execute the command pscontrol automated or pscontrol manual. To permanently switch the mode (if you always want to control all publications. see “publish— Publishing a service model or viewing instances to be published” on page 283.

214 BMC Impact Solutions Service Modeling and Publishing Guide . Such a failure cannot be prevented because the BMC Atrium CMDB does not “know” the concept of transactions. automated publish is disabled on publish environments with overlay asset dataset and an overlay publish mode. notifications from a reconciliation job run are saved in BMC Impact Publishing Server’s persistent store. When automated publisher restarts. it will also find publishable data that became publishable after the in-progress publish was initiated. s s s you can also use the CLI command publish How automated publish works When a BMC Atrium CMDB Reconciliation Engine job terminates. the ARDBC plugin notifies the BMC Impact Publishing Server that the reconciliation job has terminated. By default. and publish are independent processes.Publishing in automated or manual mode s publication failures caused by reasons independent of model consistence (for example. so a promotion from BMC Impact Service Model Editor to a production cell is automatically published. When the automated publisher is temporarily off. By default. all the notifications that are present are included in one publish request. This — might cause inconsistent data (like an impact relationship pointing to a nonexistent component) and publication failure. but the subsequent publish fails. so a reconciliation to an asset dataset of a SME test environment to a test cell is not automatically published. BMC Impact Publishing Server looks up changes to SIM data in the asset dataset since the last successful publication and attempts to publish the changes to the specified cells on publish environments for which automated publication is enabled. automated publish is enabled on publish environments with regular asset dataset. This ensures that no notifications are lost. when a cell is not available) result in the automated publisher reattempting the publication promotion and reconciliation. if an in-progress publish is still retrieving publishable data from an asset dataset. The second publication displays the message Nothing to be published. It is possible that the promotion and reconciliation processes are successful. — causes the first publication to also publish the data of the second reconciliation.

Publishing from a Direct Publish source When you have a source of data other than BMC Atrium CMDB. Data that you send from a Direct Publish environment must be updated and deleted in the context of a Direct Publish environment.Publishing from a Direct Publish source Determining the current publish mode To determine the current publish mode in which the BMC Impact Publishing Server is running. You execute the CLI command pposter to publish the data from a Direct Publish environment. Create a Direct Publish environment for the SIM management data.Manual mode In an environment without the BMC Atrium CMDB. updated or deleted in the cells. you can send it to cells using Direct Publish publishing. The basic process of publishing from a Direct Publish source is Table 57 Basic process of publishing from a Direct Publish source For instructions. Chapter 8 Managing BMC Impact Publishing Server 215 . Create a Direct Publish environment for component instances and impact relationships. if you create a component by publishing from the Direct Publish environment MySource.Automated mode Started . You can publish from multiple publish environments.Starting Automated mode Started . For example. “Creating an environment for component instances and relationships” on page 219 “Creating an environment for component instances and relationships” on page 219 Basic process 1. see “Enabling Direct Publish publishing” on page 218. You provide a BAROC file that contains the data that is to be added. One of the following messages is returned: s s s Started . 3. Enable Direct Publishing. see “psstat—Displaying status of BMC Impact Publishing Server” on page 282. For more information about psstat. then the component can only be updated or deleted by publishing from the same Direct Publish environment. psstat returns the status of publishing server as Started. 2. execute the CLI command psstat.

keep track of the cells to which you published data using the Direct Publish environment. see “pposter—Sending service model objects to a cell” on page 268 “pposter—Sending service model objects to a cell” on page 268 Basic process 4. this parameter is not set. If a HomeCell is defined for the publish environment. 216 BMC Impact Solutions Service Modeling and Publishing Guide . Then. 5. the BMC Impact Publishing Server uses the following algorithm: 1. About home cell and cell alias Table 58 describes the parameters that apply to a Direct Publish environment. Create a source file that contains the service model data in BAROC format. Parameter name CellAliases You must define either the HomeCell or the CellAliases parameter for a Direct Publish environment. when you modify them. this parameter is not set. all SIM data is published to that cell and CellAliases are not used.About home cell and cell alias Table 57 Basic process of publishing from a Direct Publish source For instructions. that value is used (regardless of the values of the component’s HomeCell or HomeCellAlias slots) 2. However. Table 58 Valid parameters for a Direct Publish environment Function specifies one or more cell alias to cell name pairs By default. Determining the cell to which a component is published To determine the cell to which a component is published. Only cell aliases and cell names defined in the publish environment's CellAliases parameter are used. You can set a default cell by setting CellAlias to null. Send service model data in the BAROC source file to the cells. You can define values for the parameters HomeCell and CellAliases of Direct Publish environments when you define the environment or you can modify them later. the components that do not have a value set for the attribute HomeCellAlias are published to that default cell. By default. If HomeCell is set. HomeCell specifies to which cell to publish.

HomeCellAlias slot) 4. If the component’s attribute HomeCell is set. In a Direct Publish environment. An impact relationship must go to the cell of its consumer.HomeCellAlias slot) 4. that value is used (regardless of the values of the component's consumer_home_cell or Consumer. If HomeCell is defined for the publish environment. The value of the HomeCellAlias slot is used to look up the HomeCell in the publish environment's CellAliases.HomeCellAlias slots) 2. 3. Determining the cell to which an impact relationship is published To determine the cell to which a impact relationship is published.About home cell and cell alias 3. 4.HomeCellAlias slot is used to look up the provider_home_cell in the publish environment's CellAliases.HomeCellAlias slots) 2. Chapter 8 Managing BMC Impact Publishing Server 217 . that value is used (regardless of the values of the component's provider_home_cell or Provider. The value of the Provider. that value is used (regardless of the value of the Provider. The value of the Consumer. About the home cell of the provider 1. that value is used (regardless the value of the HomeCellAlias slot). If consumer_home_cell is set. 3. If provider_home_cell slot is set. Only cell aliases and cell names defined in the publish environment's CellAliases are used. If HomeCell is defined for the publish environment. status is not propagated when the value for provider_home_cell for a remote provider is incorrect. that value is used (regardless the value of the Consumer. the BMC Impact Publishing Server uses the following algorithm: 1.HomeCellAlias slot is used to look up the consumer_home_cell in the publish environment's CellAliases. Only cell aliases and cell names defined in the publish environment's CellAliases are used.

and Provider. located in MCELL_HOME/etc. Consumer. so cells and BMC Impact Publishing Server share the file.dir. HomeCellAlias. by the parameter DirectPublishOrigin = T. Consumer.HomeCellAlias are published to the cell. Provider.HomeCell. All slots that are defined in the source files for pposter.conf with the parameter IMFileDirectoryName.HomeCell. Enabling Direct Publish publishing By default.conf file. see “Configuration file and parameters for CLIs” on page 235. except possibly HomeCell. Direct Publish is controlled in the pserver. 218 BMC Impact Solutions Service Modeling and Publishing Guide . Direct Publish publishing is enabled. depending on the value of the parameter ContinueOnFailure in the pclient. For information about the pclient. then management data is send to HomeCell. 2 Management data is sent to all cells defined in the CellAliases of the publish environment. the cell information is looked up from a cell directory file. Determining the cells to which management data is published 1 If HomeCell is defined for the publish environment. It defaults to mcell.conf file. The attributes or slots in the source files must also exist in the cell or the publication fails. You set this file in pserver.conf file. the publication continues or terminates. (Default = T) For DirectPublish environments. About class and slot data If there are classes in the source files that do not exist in the cell.HomeCellAlias.About class and slot data Relationships that cross cells When a relationship crosses cells (the provider and consumer components belong to different cells). you must set the provider_classname slot for successful creation of relationship.

Create a Direct Publish environment and define CellAliases by executing a similar command (depending on the number of cells): penv open -e EnvId -p “OriginId=DirectPublish” -p “CellAliases=[cellAlias1. cellName# represents the name of the cell to which you are sending objects with the preceding cell alias. cellName represents the name of the cell to which you are sending objects. you need to define cell aliases with the parameter CellAliases. NOTE When you modify the value of the parameter CellAliases. cellName1. you must redefine all cell aliases. Create a Direct Publish environment and define HomeCell by executing the following command: penv open -e EnvId -p “OriginId=DirectPublish” -p “HomeCell=cellName” EnvId represents the name of the environment you are creating. cellAlias# represents the cell alias to which you are sending objects. Modifying home cell and cell aliases To modify existing values for the parameters HomeCell or CellAliases. use the CLI command penv with its action command set. To change the value of HomeCell to null (unset or remove the value). Sending SIM data to multiple cells When SIM data for the environment goes to more than one cell.Creating an environment for component instances and relationships Creating an environment for component instances and relationships Sending SIM data to one cell When all the SIM data for the environment goes to one cell. use the following command: penv set -e EnvId -p "HomeCell=" Chapter 8 Managing BMC Impact Publishing Server 219 . cellName2]” EnvId represents the name of the environment you are creating. you can define the cell once with the parameter HomeCell. cellAlias2.

execute CLI commands similar to the following: pposter -e EnvId sourceFileName.baroc Removing data from a cell To remove existing service model data for a specific environment from a cell. Examples—using cell aliases for Direct Publish publishing Example 1 You need a service model for the Sales department in the production cells austin and brussels. the second pposter command references an empty (containing no data) BAROC file. use the following command: penv set -e EnvId -p "CellAliases=" Initializing a cell from a Direct Publish environment Initializing a cell from a Direct Publish environment consists of deleting all existing SIM data of the publish environment from the cell and then recreating it from the original BAROC source file.baroc For more information about reinitializing a cell.baroc pposter -e EnvId -p “Init=T” sourceFileName.m Reinitializing a cell To initialize a cell from a Direct Publish environment and recreate the data from the BAROC source file.baroc pposter -e EnvId -p “Init=T” emptyFileName. You define a Direct Publish production environment by executing the following command: 220 BMC Impact Solutions Service Modeling and Publishing Guide . Execute CLI commands similar to the following: pposter -e EnvId sourceFileName.Initializing a cell from a Direct Publish environment To change the value of CellAliases to null (unset or remove the value). see “pinit—Initializing a cell with service model data” on page 261.

you add a new component and a new impact relationship and leave the remainder of the data in the source file unmodified. In the sales_test.Test “OriginId=DirectPublish” -p “CellAliases=[austin.baroc Example 2 The service model for the Sales department is needed for training. brussels. You send the objects in the source file to the cells austin and brussels by executing the following command: EXAMPLE pposter -e Sales sales. In the source file.Training -p “OriginId=DirectPublish” -p “CellAliases=[austin.HomeCellAlias=brussels.HomeCellAlias=austin and Provider.baroc file.baroc Now you want to experiment with the impact of a change to the service model in the test cells austin_test and brussels_test.baroc. austin_training. brussels_training]” Chapter 8 Managing BMC Impact Publishing Server 221 .Examples—using cell aliases for Direct Publish publishing EXAMPLE penv open -e Sales -p “OriginId=DirectPublish” -p “CellAliases=[austin. brussels]” You create a BAROC source file named sales.baroc. You send the objects in the source file sales_test. You define a Direct Publish environment by executing the following command: EXAMPLE penv open -e Sales. sales. brussels. these attributes are set: HomeCellAlias=austin.baroc.baroc to the cells austin_test and brussels_test by executing the following command: EXAMPLE pposter -e Sales sales_test. and name the copy sales_test. brussels. You define a test Direct Publish environment by executing the following command: EXAMPLE penv open -e Sales. Consumer. brussels_test]” You make a copy of the BAROC source file. austin. austin_test.

however it makes the password available for anyone who has the right to execute the CLI. set. a password that is in a CLI's configuration file applies to all executions that do not specify a password on the command line itself. You enter the password in plain text and it is encrypted the first time a CLI is executed. You can put a password in the pclient. Therefore. 222 BMC Impact Solutions Service Modeling and Publishing Guide . You can password protect both Atrium CMDB environments and Direct Publish environments. then you must enter the password for every action on the environment: publishing.baroc.Training environment that are in the source file sales.Training sales. if you have multiple secured environments. See “Determining the cell to which a component is published” on page 216. Securing publish environments You can control the execution of publishes for a specific publish environment by putting a password on the environment. initializing. the service model objects are sent to the cell austin_training because the Sales. you need to decide if you want to put the password of one of them in the configuration file. and penv action commands: init.) and passwords that end with (encrypted) are not supported. Also. brussels_training.Securing publish environments You need the same objects in the Sales.baroc.conf CLI’s configuration file.conf file. austin_training and brussels. regardless of the publish environment.Training environment was defined with cellalias-to-cellname pairs as austin. unless you enable password logging by setting the PasswordLogging parameter to T (true) in the pserver. Passwords that contain a semicolon (. so you send the objects in that source file to the cells austin_training and brussels_training by executing the following command: EXAMPLE pposter -e Sales. which has component instances defined with HomeCellAlias=austin.baroc Even though you did not modify the source file sales. close. This relieves you from having to enter the password on the command line when executing the CLI. Executing commands on password protected environments If a publish environment is password protected. Passwords are removed in generated request logs and from BMC Impact Publishing Server request events (class IPS_REQUEST).

You enter the password in plain text and it is encrypted the first time a CLI command that uses the configuration file is executed. in the format: Chapter 8 Managing BMC Impact Publishing Server 223 .Securing publish environments For example. Adding a password to an existing environment To add a password to an environment that was not password protected when it was created.conf or pinit. you use the CLI command penv and the action command set. you use the CLI command penv and the action command open. you want to create a service model for the Sales department using a BAROC source file for the service model data and password protect it. the_password (first occurrence) represents the password. Modifying the password on an environment To change a password on an environment. to confirm it. which has an environment ID = Accounting and is password protected. So you create a Direct Publish environment with the CLI command penv and the action command open using the following command: EXAMPLE penv open -e Sales -p “OriginId=DirectPublish” -p “NewPassword1=sam3ul” -p “NewPassword2=sam3ul” You can also enter a password in the pclient. so you execute the following command: EXAMPLE penv set -e Accounting -p “Password=ut0p1a” -p “HomeCell=cell2” Adding a password when you create an environment To add a password when you create a new publish environment. you use the CLI command penv and the action command set. the_password (second occurrence) represents the password again. in the format: penv set -e EnvId -p “NewPassword1=the_password” -p “NewPassword2=the_password” EnvId represents the environment ID.conf configuration files. in the format: penv open -e EnvId -p “OriginId=DirectPublish|AtriumCMDB” -p “NewPassword1=the_password” -p “NewPassword2=the_password” For example. you want to assign a value to the HomeCell parameter for the Accounting department.

Using CLI command pposter for a password protected Direct Publish environment If you password protect a Direct Publish environment. For changes to this file to take affect. you use the CLI command penv and the action command set. you must include the password in the command string when you execute the CLI command pposter. in the format: penv set -e EnvId -p “Password=old_password” .pserver. For example: EXAMPLE pposter -e Payroll -p “Password=86a032” sm_payroll. 224 BMC Impact Solutions Service Modeling and Publishing Guide . you must restart the BMC Impact Publishing Server service or process. you must include the password in the command string when you execute the CLI command publish.conf file and parameters This section contains information you need to configure the BMC Impact Publishing Server.conf file and parameters penv set -e EnvId -p “Password=old_password” .baroc pserver. For example: EXAMPLE publish -e Accounting -p “Password=l0b3l1a” Automated publishing for a secured Atrium CMDB Publish environment is preauthenticated.p “NewPassword1=” -p “NewPassword2=” Using CLI command publish for a password protected AtriumCMDB Publish environment If you password protect an Atrium CMDB Publish environment.conf file and all its parameters.p “NewPassword1=new_password” -p “NewPassword2=new_password” Removing the password on an environment To remove the password on an environment. Table 59 describes the default pserver.

the publish is cancelled. If you want to use the command "publish -e OVO" then you have to add the adapter cell to this parameter.pserver. AtriumCMDBPreviewTimeout sets the length of time that BMC Impact Publishing Server waits for an answer to cancel or commit the publish after publish preview When no answer is received after this interval.conf file and parameters Table 59 Filename File path Description pserver. you must specify an NFS path. or a commit from a client during publish preview When no heartbeat is received after this interval. Specifying a UNC path is not supported.conf MCELL_HOME/etc/ps_hostname or if that file does not exist MCELL_HOME/etc contains the configuration settings that control the behavior of the BMC Impact Publishing Server Description specifies the name of the log directory for the BMC Impact Publishing Server On UNIX platforms. This name is looked up in the directory set in IMFileDirectoryName. and you must use the command "pubilsh -e OVO -p "OriginId=CellPublish" -p "Cell=ovo_java"" CellPublishGateway enables (T) or disables (F) listening by the Publishing Server for incoming IPS_CP_TRIGGER events propagated by a staging cell that will trigger a publication for a CellPublish environment of the cell defines the name of gateway that listens for incoming IPS_CP_TRIGGER events to trigger a CellPublish publication. If empty. that is. then the command will fail with the message No publish environment OVO found. the publish is cancelled. Default value log Parameter name SystemLogDirName AtriumCMDBPublishOrigin AtriumCMDBHeartbeatInterval enables (T) or disables (F) publishing from BMC Atrium CMDB to a cell T (true) 180 (seconds) sets the length of time that BMC Impact Publishing Server waits for a heartbeat. set by install Chapter 8 Managing BMC Impact Publishing Server 225 . T (true) CellPublishGatewayName not defined.conf file pserver. 180 (seconds) CellPublishOrigin CellPublishIms enables (T) or disables (F) publishing from staging cells T (true) lists all the staging cells. a cancel. all the cells that define CellPublish publish environments.

CellPublish2Cmdb can find all offending data in one run. CellPublish2CmdbReconJobTime defines the length of time. DirectPublishOrigin DirectPublishHeatbeat Interval enables (T) or disables (F) direct publishing feed F (false) 180 (seconds) sets the length of time that BMC Impact Publishing Server waits for a heartbeat. the reconciliation job might complete successfully after the timeout.conf file lists the cells from which the Publishing Server accepts not defined incoming events.pserver. localhost:9379 JMSCommWarnReconnectCount the number of times to retry to establish JMS communication If the trial fails then an IPS_ERROR event with message "Unable to establish JMS communications. If the interval expires before the reconciliation job run completes. 30 (reconnect attempts) JMSCommWarnReconnectInterval the interval (in seconds) between two reconnection 10 (seconds) attempts 226 BMC Impact Solutions Service Modeling and Publishing Guide ." of severity WARNING is generated. If JMSCommWarnReconnectCount is -1 then retries continue indefinitely. this value must match the same value in the pclient. Even though no result is indicated. a new commit is retried without the offending data. in seconds.conf file and parameters Table 59 pserver.conf file. By retrying the commit without the offending date. in seconds that CellPublish2Cmdb retries in total to commit the data in the import dataset. JNPServers defines the host and port of JNP Servers When the Portal is set up in cluster mode. CellPublishCommitRetryTime Out 900 (seconds) defines the length of time. CellPublishGatewayIms CellPublish2CmdbContinueOn Warning enables (T) or disables (F) continuation when instances F (false) that cannot be imported must skipped The list of skipped instances and the reason they were skipped is output to the request log. When a commit fails. that Out CellPublish2Cmdb checks for the termination of the 120 (seconds) reconciliation job run. then the request log does not indicate the result. the publish is cancelled. or a close from a client When no heartbeat is received after this interval. a direct request. If no cell is listed then all incoming events are accepted.

encrypted at first launch not defined.pserver. set by install use 0 for dynamic port detection CMDBServer CMDBPort CMDBUser CMDBPassword defines the user ID that grants access to the BMC Atrium CMDB a valid BMC Atrium CMDB user password appears in plain text when entered. Use 0 for dynamic port detection.conf file and parameters Table 59 pserver. set by install ARSGroupMembers lists the host and TCP/IP port of every AR Server Group member If an AR Server Group is deployed then you must set this parameter. set by install not defined.conf file the number of times to retry to establish JMS communication If the trial fails then an IPS_ERROR event with message "Unable to establish JMS communications. regardless of whether you use a load balancer." of severity MAJOR is generated. -1 (connection attempts) JMSCommMajorReconnectCount JMSCommMajorReconnectInterval the interval (in seconds) between two reconnection attempts specifies the name of the computer on which BMC Atrium CMDB resides defines the port number for connecting to the BMC Atrium CMDB 300 (seconds) not defined. not defined RequestHistorySize CellConnectionTimeout sets the maximum number of request log files that are retained by the BMC Impact Publishing Server 100 sets the length of time the BMC Impact Publishing 60 (seconds) Server maintains a connection to a cell when there is no activity from the cell sets the size of the message buffer for communication with the cell sets the time to keep messages buffered while waiting for an answer 2000 300 (seconds) IMMessageBufferSize IMMessageBufferKeepSent Chapter 8 Managing BMC Impact Publishing Server 227 . set by install not defined. If JMSCommMajorReconnectCount is -1 then retries continue indefinitely.

it is looked up in the directory MCELL_HOME/etc/PSName. 0 or a negative value disables heartbeat. mcell.pserver. AutomatedCancelAckTimeout AutomatedCancelScsFlrTimeout When automated publishing is stopped. an ongoing 900 (seconds) publish is canceled. which returns a message indicating if the publish request was canceled or not.conf file and parameters Table 59 pserver. an ongoing publish is canceled. This parameter sets the length of time for an ack reply of the publishing request. This parameter sets the length of time for the final reply of the publish request. sets the length of time that BMC Impact Publishing Server waits for an answer to a heartbeat from the AR Notify plugin.conf file defines the name of the Impact Manager directory for direct publications. then the publish request is not canceled. If the publish is canceled or if the final reply is unknown. or if that file does not exist. then the publish is retriggered when automated publish is restarted. if possible. -1 (seconds) AutomatedHeartbeatTimeout 5 (seconds) 228 BMC Impact Solutions Service Modeling and Publishing Guide . If the requestID is unknown. if possible. AutomatedHeartbeatInterval sets the length of time between the BMC Impact Publishing Server and the AR Notify plugin for heartbeat.dir IMFileDirectoryName PaswordLogging SMMMessageBufferSize SMMMessageBufferKeepSent SMMMessageBufferKeepSent Estimate ARSNormalTimeOut ARSLongTimeOut ARSXLongTimeOut ARSXLongTimeOutEstimate enables (T) or disables (F) the display of passwords in generated request logs and IPS_REQUEST events sets the size of the message buffer for communication with Service Model Manager sets the time to keep messages buffered while waiting for an answer F (false) 500 300 (seconds) enables (T) or disables (F) the use of the estimate when T (true) the length of time exceeds the value that is calculated for the upload time of the service model sets the time to stop waiting on a BMC Remedy AR System operation that occurs quickly sets the time to stop waiting on a BMC Remedy AR System operation that occurs slowly sets the time to stop waiting on a BMC Remedy AR System operation that occurs slowly 120 (seconds) 300 (seconds) 1800 enables (T) or disables (F) the use of the estimate when T (true) the length of time exceeds the value that is calculated for committing bulk entry transactions 5 (seconds) When automated publishing is stopped. which returns the requestID. in the directory MCELL_HOME/etc This directory file is also used to locate the cell for BMC Impact Publishing Server event generation.

Configuring the Notify ARDBC plug-in Table 59 pserver. When the BMC Impact Publishing Server is running. the BMC Impact Publishing Server starts in automated mode. defines the cell to which BMC Impact Publishing Server events are sent not defined. so AutomatedPublishRetryCount is the effective maximum number of retries. AutomatedPublishRetryPeriod sets the length of time between two consecutive publish requests when publish fails If a previous publish request is not terminated when the interval times out. 300 seconds AutomatedStartMode the publishing mode when the BMC Impact Publishing automated Server starts or restarts. Configuring the Notify ARDBC plug-in The Notify ARDBC plug-in adds real-time notification functionality to BMC Remedy AR System applications and enables clients to receive notification about events in BMC Remedy AR Server.conf file the maximum number of times automated publishing is retried after failures n represents the number of repeated publication attempts: s s s AutomatedPublishRetryCount 12 n = 0 means the publication is attempted once and not retried n = 1 means the publication is attempted and then retried once n < 0 means the BMC Impact Publishing Server continues to retry until a publication is successful Publications that are skipped are not counted as retry attempts. Chapter 8 Managing BMC Impact Publishing Server 229 . By default. set by install to Impact Administration Cell all subclassess of IPS_EVENT set when? IPSEventsIM IPSEventClasses DefaultCell defines the event classes for which BMC Impact Publishing Server events are created sets the CellName for the default HomeCellAlias This parameter is used by the PROD publish environments of AtriumCMDB and CentralPublish origins. the next trial is skipped. you can change the publishing mode by using requests (using the CLI command pscontrol).

the plug-in allows the operating system to choose an available port and binds to that port. BMC-ARDBC-NOTIFY-Mem-Trace enables (T) or disables (F) memory tracing You should enable memory trace only when BMC Customer Support requests it. the NOTIFY:protocols property for the V1 protocol contains the key to use for encryption.cfg file parameter descriptions Description log file location Default value Remedy AR System/ Impact directory 1840. BMC-ARDBC-NOTIFY-Protocol-V1-Encrypt switches encryption for V1 protocol on or off T (True) If encryption is switched on (T). event caching is disabled 230 BMC Impact Solutions Service Modeling and Publishing Guide . the NOTIFY:protocols property for the V1 protocol is empty. The actual port is visible in the NOTIFY:servers form. F (False) BMC-ARDBC-NOTIFY-Event-Cache sets the number of events for the event cache 200 When the size is 0.Configuring the Notify ARDBC plug-in You can modify the Notify ARDBC parameters in the following files: UNIX: arInstallDirectory/conf/ar. restart BMC Remedy AR System so the changes take affect. set by install BMC-ARDBC-NOTIFY-Server-Port port number for the server If 0 is specified.cfg After you make changes to these parameters.conf Windows: arInstallDirectory\conf\ar. If encryption is switched off (F). Table 60 Parameter BMC-ARDBC-NOTIFY-Verify-Log ar.

Automated publishing will not function. you must set the address of the Remedy AR server group member to which you want the Publishing Server to connect using the CMDBServer parameter in the pserver. you must add the load balancer host name to the CMDBServer parameter in the pserver. To check whether the Remedy AR server group is correctly configured for the Publishing Server and the Notify plug-in: 1 From the computer running the Publishing Server. If you use a load balancer. 3 In the form NOTIFY:Servers. the Publishing Server (the AR API client or Remedy User) cannot access the ARDBC vendor form NOTIFY:Servers of the plugin running on the node that is not the alias. NOTE If a Server Name Alias is set equal to one of the group members. If you do not use a load balancer. you should find one entry when you attempt to retrieve the entries. Chapter 8 Managing BMC Impact Publishing Server 231 .conf file.conf file.conf file. 2 Open the form. logon as Remedy User to the individual AR Server Group Members. You must also add the individual group member nodes (<host>:<tcp/ip port>) to the ARSGroupMembers parameter in the pserver. NOTIFY:Servers.Configuring the Notify plug-in for AR server groups Configuring the Notify plug-in for AR server groups The Publishing Server supports the Notify plug-in for Remedy AR server groups.

Configuring the Notify plug-in for AR server groups 232 BMC Impact Solutions Service Modeling and Publishing Guide .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . initialize. . . 247 pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB . . . . . . 243 Using CLI commands . . . . . . . . . . . . . . . . . . . 268 pscontrol—Sending a command to BMC Impact Publishing Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Understanding common command options for CLIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and close publish environments request and review information about BMC Impact Publishing Server execution compare service model class definitions on cells with the class definitions in the BMC Atrium Configuration Management Database (BMC Atrium CMDB) This appendix provides reference information on the BMC Impact Publishing Server CLIs. . . . . . . . 235 Changing the time-out values for all the CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 plogdisplay—Converting the XML log for a request to text format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 plog—Obtaining the XML log for a request . . . 280 pshowlog—Obtaining the XML log in user-friendly format . . . . . . . 282 publish—Publishing a service model or viewing instances to be published . . . . . . . . . . . . .Chapter 9 9 BMC Impact Publishing Server CLIs Use the BMC Impact Publishing Server Command Line Interface (CLI) to s s s s s initiate a service model publish create service model data (with a BAROC source file) create. . . . . . . . . . . . . 281 psstat—Displaying status of BMC Impact Publishing Server . . . . . . . . . . . . . . 247 Summary of CLI commands for BMC Impact Publishing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 pinit—Initializing a cell with service model data . . . . . . . . . . 241 Configuring trace for CLIs . . . . . . . . . . . . . . . . . . . . . . 240 Setting the configuration for a specific CLI command . . . . 241 Configuring trace for CLIs . . It contains the following topics: Configuring BMC Impact Publishing Server CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Understanding return codes for CLIs . . . . 249 penv—Managing publish environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Configuration file and parameters for CLIs . . . . . . . . . . . . . . . . . 266 pposter—Sending service model objects to a cell . . . . . . . . . . . . . . . . 283 Chapter 9 BMC Impact Publishing Server CLIs 233 . . . 278 pserver—Starting the BMC Impact Publishing Server service . . . . . . . . . . . . . . . . . . . . . . . . . . . .

the -i option remains viable for compatibility. Publishing Server CLIs no longer require authentication. 234 BMC Impact Solutions Service Modeling and Publishing Guide .00. If you specify the -i option. NOTE As of version 7.conf file located in the MCELL_HOME/etc directory. you do need to provide authentication credentials.Configuring BMC Impact Publishing Server CLIs Configuring BMC Impact Publishing Server CLIs You configure the BMC Impact Publishing Server CLI by using a text editor to set the parameter values in the pclient.3. However. See “Changing the time-out values for all the CLI commands” on page 240. You can configure the CLI to change the length of time that CLI commands wait for an acknowledgement of a request (ConnectionInitTimeout) or for the completion of a request (RequestTimeout).

The p-CLIs attempt to connect to the first BMC Impact Administration Server. Note that this is not only applicable to nodes of a high availability BMC Impact Administration Server pair. located in the MCELL_HOME/etc/pclient. Chapter 9 BMC Impact Publishing Server CLIs 235 . For example. or if the Portal is not running. If that connection attempt fails. the values must match. measured in seconds. or the Portal's JMS service is not up and running Normally.secondaryIAS:3084 The p-CLIs first attempt to connect the BMC Impact Administration Server on the host primaryIAS.conf file. the BMC Impact Publishing Server immediately acknowledges any request that it receives. If that connection attempt fails.Configuration file and parameters for CLIs Configuration file and parameters for CLIs Table 61 on page 235 lists and describes the configuration parameters for BMC Impact Publishing Server CLIs.conf file but do not provide user credentials. you must enter both servers as a comma separated list. Default value <host of Portal>: 9379 IASServers specifies the BMC Impact Administration Server (usually by localhost: 3084 host name) that authenticates the CLI commands If you specify a remote BMC Impact Administration Server in the pclient. When the Portal is set up in cluster mode. the BMC Impact Publishing Server service is not running. Two BMC Impact Administration Servers can be setup as a high availability pair. Table 61 Parameter JNPServers pclient. You can specify more than one independent BMC Impact Administration Server. ConnectionInitTimeout 5 seconds sets the length of time. To do this. an attempt is made to connect to the BMC Impact Administration Server on the host secondaryIAS. for example: primaryIAS:3084. that a CLI command on making a request waits for the acknowledging reply from the BMC Impact Publishing Server. you must provide them as command line arguments when you run a CLI command. If this time-out expires.conf parameters (part 1 of 6) Description host and port of the naming service of BMC Impact Portal. an attempt is made to connect to the next server in the list and so on until a connection is successful. it often indicates the BMC Impact Publishing Server is not receiving the request.

conf parameters (part 2 of 6) Description sets the length of time. indicates whether the Publishing Server should look for additions. that a CLI command waits for the processing of an acknowledged request to complete Depending on the type of request. true (default). pposter removes all existing data in the F cell of the publish environment and recopies the data in the input BAROC file to the cell when set to F (false). if possible. the CLI command stops following the request processing and. This option is set to T when an automated publication is triggered from a reconciliation job with Purge activity sets the password of a secured publish environment for the none execution of the publish CLI command indicates whether pposter should stop when encountering invalid data in the source file If ContinueOnFailure is set to T. measured in seconds. T Password Parameters specific to the pposter CLI command ContinueOnFailure Init when set to T (true). If ContinueOnFailure is set to F. false. Default value 3600 seconds RequestTimeout Locale outputs messages in the language of the specified locale if message resource files for the language are defined. Country is a valid 2-letter ISO Country Code as defined by ISO-3166. and soft deletions that are to be published.Configuration file and parameters for CLIs Table 61 Parameter pclient. Language is a valid 2-letter ISO Language Code as defined by ISO-639. not even those items processed before the incorrect data in the source file. request processing may take a reasonable amount of time. modifications. The option is set to T when an automated publication is triggered from a reconciliation job with Merge activity inherits system’s locale Parameters specific to the publish CLI command Merge T Purge F indicates whether the Publishing Server should look for hard deletions that are to be published. pposter incrementally updates the cell of the publish environment with data in the input BAROC file Password sets the password of a secured publish environment for the none execution of the pposter CLI command Parameters specific to the penv CLI command 236 BMC Impact Solutions Service Modeling and Publishing Guide . pposter stops as soon as invalid data in the source file is encountered and no data is sent to the cell. skipping invalid data in the source file. pposter sends as much data as possible. The format is language[_country]. If this time-out period expires. cancels the request.

ASSET. in the BAROC list of string format: [cellAlias. which defaults to F. In this way. this releases the cells for use in another environment enables (T) or disables (F) the removal of the asset dataset along with all objects in the dataset F (false) CloseAsset CloseCells F (false) enables (T) or disables (F) the removal of all data instances T (true) (including management data) of the service model from the cells specifies a description for the environment to BMC Asset EnvDesc sets the environment name to BMC Asset EnvId BMC Asset EnvDesc BMC Asset EnvId EnvDesc EnvName Chapter 9 BMC Impact Publishing Server CLIs 237 .Configuration file and parameters for CLIs Table 61 Parameter pclient. EnvId Regular AssetDataSetId AssetDataSetType AssetUnderlyingDataSetId sets the underlying dataset ID Used when AssetDataSetType = Overlay BMC.cellAlias. in the BAROC list of string format: [cellName[.cellName[. cells aliases cannot be created or modified with the penv CLI command. For Atrium CMDB environments.cellName]] This parameter applies only on Direct Publish environments. automated publication is by default enabled on PROD environment.conf parameters (part 3 of 6) Description specifies the asset dataset name sets the asset dataset type options are Regular or Overlay Default value BMC.cellName]] This parameter applies only on Direct Publish environments. you can set this parameter as an alternative. and is disabled by default on test environments of BMC Impact Service Model Editor.ASSET AutomatedPublish enables (T) or disables (F) automated publishing on the publish environment The default value is T. T (true) CellAliases defines cell alias and cell name pairs that are unique in a given environment. except for an overlay publish environment (an overlay dataset which has a publish mode of overlay). not defined Cells If cell aliases are not used. not defined CloseAliases enables (T) or disables (F) the removal of aliases of an environment.

blank InitMgmtData InitServiceModel Level specifies whether management data are initialized.Configuration file and parameters for CLIs Table 61 Parameter Format pclient. please refer to “InitEffectively parameters” on page 206 which discusses the effect of the possible InitEffectivelyMgmtData settings on management data retention in or removal from the BMC Atrium CMDB. IN. based on the value assigned to their ServiceModelSet class attribute. CellAliases are not used. please refer to “InitEffectively parameters” on page 206 that discusses the effect of the possible InitEffectivelyServiceModel settings on SIM component instance retention in or removal from the BMC Atrium CMDB. it is not sent to the Publishing Server as a request Default value Display HomeCell sets the cell to which the entire service model is published If set. based on the value assigned to their ServiceModelSet attribute. are removed from the BMC Atrium CMDB asset dataset Before setting this parameter. sets a new password for a secured environment confirms a new password for a secured environment specifies the origin of the environment options are AtriumCMDB or DirectPublish not defined not defined AtriumCMDB NewPassword1 NewPassword2 OriginId Password sets a password for a secured environment not defined 238 BMC Impact Solutions Service Modeling and Publishing Guide . are removed from the BMC Atrium CMDB Before setting this parameter. T (true) or F (false) T specifies whether the service model is initialized.conf parameters (part 4 of 6) Description sets the format of information to Raw (a parsable data stream) or Display (readable by a user) specific to the CLI. not set InitEffectivelyMgmtData determines which asset management data instances. OUT InitEffectivelyServiceModel determines which service model component and impact relationship instances. Cell names and aliases are displayed only when -p “Level=1” is part of the command string. T (true) or T F (false) determines the amount of information display by the info 0 action command. By default. Asset instances with the ServiceModelSet attribute value of IN or OUT_OF_IN have their attribute value reset to OUT. all service model component or impact relationship instances are not removed from the BMC Atrium CMDB.

this parameter determines the mask used when retrieving publishable service model instances. if Overlay. Management data in those files are ignored.load file. all instances of the overlay dataset. SIM enables (T) or disables (F) the classes that may be published T (true) for the Direct Publish environments only if T. are considered if Current. PublishModeServiceModel determines the mask used when retrieving publishable components and impact relationships. as well as the underlying dataset. are considered if Current. Service model instances in those files are ignored.baroc files pointed to in the . all instances of the overlay dataset. This parameter cannot be set if SourceEnvServiceModel is set.loa d This is the default value for the PROD environment.loa d This is the default value for the PROD environment.load file.baroc files pointed to in the . MCELL_HOME /etc/<PSName >/kb/data/. and all subclasses cannot be published SourceBarocMgmtData causes the import of initial management data from instances in the .conf parameters (part 5 of 6) Description determines the mask used when retrieving publishable management data instances if AssetDataSetType = Overlay Default value Overlay PublishModeMgmtData if Overlay.Configuration file and parameters for CLIs Table 61 Parameter pclient. components and relationships of MC_SM_COMPONENT. This parameter cannot be set if SourceEnvMgmtData is set. if AssetDataSetType = Overlay Overlay used when the dataset type is overlay. Chapter 9 BMC Impact Publishing Server CLIs 239 . SourceBarocServiceModel causes the import of initial service model data from instances in the . only SIM classes may be published if F. as well as the underlying dataset. MCELL_HOME /etc/<PSName >/kb/data/. only instances of the overlay dataset are considered. only instances of the overlay dataset are considered. MC_SM_RELATIONSHIP.

for reinitialization of environments other than PROD SourceEnvServiceModel causes initial service model data to be imported from instances in the asset dataset in the source environment EnvId. Changing the time-out values for all the CLI commands You can change the length of time that CLI commands wait for an acknowledgement of a request (ConnectionInitTimeout) or for the completion of a request (RequestTimeout). PROD. If PublishModeServiceModel is Current.conf parameters (part 6 of 6) Description causes initial management data to be imported from instances of the source environment EnvId. To set the time-out values for all the CLI commands Use a text editor to edit the pclient. no instances are created in the overlay dataset. default value for all environments other than PROD. then: s s If PublishModeServiceModel is Overlay. Data are created in the asset dataset of the environment. SourceEnvServiceModel cannot be set if SourceBarocServiceModel is set.Changing the time-out values for all the CLI commands Table 61 Parameter pclient.conf file located in the MCELL_HOME/etc directory and change the values set of these parameters: s s ConnectionInitTimeout RequestTimeout 240 BMC Impact Solutions Service Modeling and Publishing Guide . If the asset dataset of source environment is an overlay dataset and EnvId refers to an underlying regular dataset. all instances will be created in the overlay dataset. Default value PROD environment SourceEnvMgmtData SourceEnvMgmtData cannot be set if SourceBarocMgmtData This is the is set.

trace file and removing the comment character (# ) from the lines that contain the value =DEBUG.conf file and name it CLIcommand. only fatal. error.conf. When the CLI command is run. 3 Edit the new configuration file with a text editor and set the appropriate parameter values. for example: pposter.conf. the values in the appropriate configuration file are used.trace. You can enable the inclusion of informational and debugging messages for specific packages and subpackages by editing the pclient.trace file. you can create a configuration file just for it. Chapter 9 BMC Impact Publishing Server CLIs 241 . Alternately. pposter. and warning messages appear in the trace file MCELL_HOME/tmp/pcli/pcli. Understanding common command options for CLIs Many BMC Impact Publishing Server CLI commands use the same option to perform the same function. 2 Save the file in the MCELL_HOME/etc directory. Configuring trace for CLIs You set and configure tracing of the BMC Impact Publishing Server CLIs in the MCELL_HOME\etc\pclient. This section describes the options that may be used by multiple commands. 4 Save the file. for example.conf where CLIcommand is the name of the CLI command for which you are creating a special configuration. To set the configuration for specific CLI command 1 Make a copy of the pclient.Setting the configuration for a specific CLI command Setting the configuration for a specific CLI command If you want to customize a configuration for a specific CLI command. you can use the -c option (see “Understanding common command options for CLIs” on page 241). By default.

Understanding common command options for CLIs Syntax for common options [-c ConfigFile] [-h|-?] [-i User/Password[@Host[/Port][.conf. in seconds. you can specify multiple hosts and ports This option is optional if you execute a CLI command on the BMC Impact Administration Server host computer.. If you provide only a file name.. including command syntax and options authenticates the specified user name and password with the BMC Impact Administration Server running on the specified host computer and port. If IASServer and IASPort are set in the configuration file pclient.Host[/Port] [. Table 62 BMC Impact Publishing Server CLI common command options (part 1 of 2) Description specifies another configuration file to use instead of the default MCELL_HOME\etc\pclient. if you do use this option for local authentication and the credentials that you provide are invalid.. You can also provide the absolute path for the log file. -t ConnectionInitTimeout specifies the length of time. the command will fail. default is 5 seconds 242 BMC Impact Solutions Service Modeling and Publishing Guide .]]] [-q] [-l HomeLocation] {-p "Var=Value"} [-r RequestLogFile] [-t ConnectionInitTimeout] [-u RequestTimeout] [-v] [-z] Common command options Table 62 describes the common options for the BMC Impact Publishing Server CLI commands. However.conf file displays help information. this option modifies and overrides a value defined in the configuration file invokes quiet execution (no banner appears) retrieves the XML-formatted log file and stores it as RequestLogFile By default.Host[/Port][. the file is created in the directory where you run the CLI. then you don't have to pass the host and port with the -i option... the location of the log file is relative to the directory where you run the CLI. -l HomeLocation -p "Var=Value" -q -r RequestLogFile Option Syntax -c ConfigFile -h -? -i User/Password[@Host [/Port][. for the command to wait for a connection before terminating.]]] specifies a home directory other than MCELL_HOME for the command sets an option (Var) to the specified value (Value)..

Understanding return codes for CLIs Table 62 BMC Impact Publishing Server CLI common command options (part 2 of 2) Description specifies the length of time. 2.sh) file correctly contains: -DHomeLocation=%MCELL_HOME% 3. Verify that the MCELL_HOME environment variable is set for the application. default is 3600 seconds activates verbose mode to display more information (such as detailed failure messages) displays version information and ends command Option Syntax -u RequestTimeout -v -z Understanding return codes for CLIs When a BMC Impact Publishing Server CLI command exits with a return value other than 0 (success). additional textual information on the error cause is displayed to standard output and to the generated publishing CLI trace file MCELL_HOME\tmp\pcli\pcli. for the command request to wait for an answer before terminating. Chapter 9 BMC Impact Publishing Server CLIs 243 .bat or . These exit codes. in seconds. their meanings. indicates that the home directory Do the following: (MCELL_HOME) of the application can not be found 1. and recommended remedial actions are described in Table 63. Specify the home directory (-l HomeLocation) path at the command line. Verify that the CLI script (. Table 63 Error Exit Code 1 2 3 BMC Impact Publishing Server CLI error exit codes (part 1 of 3) Description indicates a syntax error on one or more command line arguments or options indicates an invalid number option Recommended remedial action Verify the correct syntax for the command string.trace. Verify the correct syntax for the numerical options such as -t and -u.

do the following: 1. 12 indicates a communication failure when the CLI sent data to its communication provider.Understanding return codes for CLIs Table 63 Error Exit Code 10 BMC Impact Publishing Server CLI error exit codes (part 2 of 3) Description indicates a generic (unspecified) error Recommended remedial action (This is an internal error. Locate the pcli. do the its communication layer following: 1.conf file (in the MCELL_HOME/etc directory) is correct.) Do the following: 1.trace is located in MCELL_HOME/tmp/pcli. If the error still occurs. Try the command again. Verify that the URL of the provider specified in the pclient. 13 indicates that the CLI cannot decode an answer that it has received from its communication provider (This is an internal error. Locate the pcli. Restart the BMC Portal and BMC Impact Publishing Server. Enable tracing and execute the command again to have a trace. 2. indicates that the CLI cannot resolve a host Repair the computer’s network settings name 15 244 BMC Impact Solutions Service Modeling and Publishing Guide . If the error still occurs. for example a exist FileNotFound exception. Contact BMC Software Support and file a user case for this failure. pcli. 3. 14 indicates that the CLI cannot find a file that Verify that the file whose name appears as missing does it requires to run properly. Contact BMC Software Support and file a user case for this failure.) Do the following: 1. for example. 2. the jBoss server Retry the command. Enable tracing and execute the command again so there is an entry in the trace file.trace file to submit to BMC Software Support. 2.trace file (MCELL_HOME/tmp/pcli ) to submit to BMC Software Support. 2. 3. Try the command again. 3. 11 indicates that the CLI is unable to initialize Retry the command. Restart the BMC Portal and BMC Impact Publishing Server.

Understanding return codes for CLIs Table 63 Error Exit Code 16 BMC Impact Publishing Server CLI error exit codes (part 3 of 3) Description indicates the failure to authenticate with the BMC Impact Administration Server Recommended remedial action Do the following: s If you are running a CLI command. s 17 indicates an Impact interface initialization Do the following: failure.conf file. 18 19 20 indicates an I/O error when the publishing Verify that the write permission is set for the publishing log file is written request log file. IASPassword. If automatic authentication is set up in the pclient. Contact BMC Software Support and file a user case for this failure. and IASServers) are valid. verify the credentials that you specified. Locate the pcli. 2. 3. verify that the credentials (IASUsername. You specify the name of the RequestLogFile for a CLI command by using the -r common option Chapter 9 BMC Impact Publishing Server CLIs 245 . Enable tracing and execute the command again to generate a trace. indicates that the UTF-8 character set is not The host computer must support the UTF-8 character supported by the host set.trace file (MCELL_HOME/tmp/pcli) to submit to BMC Software Support.load exists on the host where the pcli is running/installed. for example the I18N configuration may be wrong Verify that the file MCELL_HOME/etc/locale/pclient. indicates that the CLI does not have a request identifier Do the following: 1.

indicates the Impact Administration Server Verify BMC Impact Administration Server settings and interface cannot initialize installation. their meanings.lock.Return codes for pserver Return codes for pserver The pserver command has return codes that differ from other CLI commands. 246 BMC Impact Solutions Service Modeling and Publishing Guide . indicates another Publishing Server is already running indicates the CMDB interface cannot initialize Verify with fuser (Unix) that a process is keeping a lock on ps. Specify the home directory (-l HomeLocation) path at the command line.lock file cannot be Ensure the pserver user has write access to created MCELL_HOME/log. 2 3 4 5 6 7 9 10 indicates the log directory cannot be created Ensure the pserver user has write access to MCELL_HOME/log. indicates a configuration file is missing indicates an I/O exception occurred on a configuration file indicates a syntax error Provide the configuration file. Check the syntax you used for the command and try the command again. Ensure the pserver user has write access to the configuration file. and recommended remedial actions are described in Table 64. indicates that the log/ps. remove ps. Table 64 Error Exit Code 1 pserver error exit codes (part 1 of 2) Description indicates that the HomeLocation system property is not set Recommended remedial action Do the following: 1. If not.sh) file correctly contains: -DHomeLocation=%MCELL_HOME% 3. Verify that the CLI script (. Verify that the MCELL_HOME environment variable is set for the application. These exit codes.lock. Verify ARServer and BMC Atrium CMDB settings and installation.bat or . 2.

Using CLI commands Table 64 Error Exit Code 11 pserver error exit codes (part 2 of 2) Description Recommended remedial action indicates the home directory does not exist Do the following: 1. Verify that the CLI script (. To use the BMC Impact Publishing Server CLI commands remotely. 14 Using CLI commands This section provides information on how you use BMC Impact Publishing Server CLI commands. 2.bat or . and examples.sh) file correctly contains: -DHomeLocation=%MCELL_HOME% 3. or from a script. either locally on the BMC Portal host computer or remotely on another computer. 12 13 indicates a security exception error on the home directory Ensure the pserver user has write access to the home directory. Specify the home directory (-l HomeLocation) path at the command line. Verify that the MCELL_HOME environment variable is set for the application.trace file indicates the publish environments cannot be initialized Verify that the SIM CMDB extension of the same version as the Publishing Server is installed. HomeLocation/tmp/ps. including functions. syntax. you must copy the CLI installation to the remote host and configure the CLI for remote access See “Configuring BMC Impact Publishing Server CLIs” on page 234. indicates an I/O exception occurred during Ensure the pserver user has write access to the creation of the MCELL_HOME/tmp. Summary of CLI commands for BMC Impact Publishing Server Table 65 lists all of the available BMC Impact Publishing Server CLI commands and provides a brief description of the purpose for each command. from a UNIX operating system prompt. Chapter 9 BMC Impact Publishing Server CLIs 247 . You can invoke BMC Impact Publishing Server CLI commands from a command prompt on Windows.

started. pclassinfo penv enables you to set up advanced environments and staging 252 scenarios beyond the abilities of the Send to Test commands available in BMC Impact Service Model Editor initializes or reinitializes cells with service model impact data obtains the XML log for a specific service model publishing request and routes it to standard output Use this command with the plogdisplay command. the process for copying pserver to another computer is different. stop) to the BMC Impact Publishing Server starts the BMC Impact Publishing Server service or daemon The major differences between pserver and the other BMC Impact Publishing Server CLI commands are: s s 266 268 pscontrol pserver 278 280 s s the exit codes are different pserver is the BMC Impact Publishing Server itself. relationships. while the others are CLI commands that communicate with the server the configuration files and tracing files are different although possible. manual.Summary of CLI commands for BMC Impact Publishing Server Table 65 Command BMC Impact Publishing Server CLI command descriptions Description Page compares the service model class definitions on a cell or 249 cells with the class definitions in the BMC Atrium CMDB and lists the differences You can also use this command to export service model class definitions from the BMC Atrium CMDB. such as component instances. or stopping) and mode (automated or manual) of the BMC Impact Publishing Server publishes service model or displays (-w) the service model objects to be published psstat 282 publish 283 248 BMC Impact Solutions Service Modeling and Publishing Guide . and management data to cells by using the BMC Impact Publishing Server sends a specific command (automated. 261 265 pinit plog plogdisplay pposter displays the XML log for a specific service model publishing in text format to standard output sends SIM elements. and performance considerations should be taken into account 281 pshowlog obtains the XML log for a specific service model publishing request plus the prior publishing request and routes it in readable format to standard output returns the status (starting.

.pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB Use the pclassinfo command to s compare the service model class definitions on a specific cell or cells with the service model class definitions in the BMC Atrium CMDB and list the differences between them.. s pclassinfo syntax pclassinfo <common options> [-n cellName1[. If the cell has a different name.]] Chapter 9 BMC Impact Publishing Server CLIs 249 . the default cell name (the unqualified version of the host computer name) is used. Table 66 Options <common options> -? -c -h -i -l -p -q -t -u -v -z -a pclassinfo options (part 1 of 2) Description see “Understanding common command options for CLIs” on page 241 specifies to retrieve the service model classes from ALL the cells and compare them with the BMC Atrium CMDB service model classes specifies the specific cell or cells from which to retrieve the service model classes and compare them with the BMC Atrium CMDB service model classes On Windows platforms. the command fails...cellName2[. There are no required options for pclassinfo. If a cell name is not specified. export the service model class definitions from the BMC Atrium CMDB.]] |-a | -x] [-o OutputFile] [-s Description] pclassinfo command options Table 66 lists the options for pclassinfo. you must enclose the cell list in quotation marks (").cellName2[. -n cellName1[.

type the following command: pclassinfo -x This command generates a listing of the service model class definitions defined in the BMC Atrium CMDB and outputs it to standard output. type the following command: pclassinfo -x -o fileName 250 BMC Impact Solutions Service Modeling and Publishing Guide . prints the differences between the specified service model class definitions to the specified output file. pclassinfo examples This section contains several examples of the pclassinfo command including: s exporting service model class definitions from the BMC Atrium CMDB to standard output exporting service model class definitions from the BMC Atrium CMDB to a file comparing cell service model class definitions with those in the BMC Atrium CMDB s s Exporting service model class definitions from the BMC Atrium CMDB To export the service model class definitions in the BMC Atrium CMDB to standard output. To export the service model class definitions in the BMC Atrium CMDB to a specific file. -o OutputFile -s description -x describe request exports service model class definitions from the BMC Atrium CMDB to standard output or if an output file (-o option) is specified to a file Service model class definitions are exported in BAROC language format.pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB Table 66 Options pclassinfo options (part 2 of 2) Description If the -a or -n option is specified. prints the service model class definitions from the BMC Atrium CMDB to the specified output file. If the -x option is specified.

-. All rights reserved.000 20-May-2008) Copyright 2005-2008 BMC Software.00 (Build 1544975. as an unpublished work.000 20-May-2008) Copyright 2005-2008 BMC Software.00 (Build 1544975.2. Inc. All rights reserved. as an unpublished work. If there are differences between the service model class definitions on the cell and those defined in the BMC Atrium CMDB. Class info is synchronized. You can load this file on a cell.BEGIN DIFFS -<PreviewItem><Im>arwad</Im><SlotAdd><Class>BMC_BaseElement</Class><S lot>VersionNumber</CmdbSlot></SlotAdd></PreviewItem> <PreviewItem><Im>arwad</Im><ClassAdd><CmdbClass>BMC_Region</CmdbClas s></ClassAdd></PreviewItem> -. which appear similar to the following: MCELL_HOME\bin>pclassinfo BMC Impact Service Model Class Retriever v7. type the following command: pclassinfo -n cellName Chapter 9 BMC Impact Publishing Server CLIs 251 . Comparing cell service model class definitions with those in the BMC Atrium CMDB To compare the service model class definitions in the cell whose name is the shortversion of its host computer name (the default cell name) with the definitions in the BMC Atrium CMDB. the command returns output similar to the following: MCELL_HOME\bin>pclassinfo BMC Impact Service Model Class Retriever v7. type the following command: pclassinfo If there are no differences between the service model class definitions on the cell and those defined in the BMC Atrium CMDB. the command returns the differences. Inc.END DIFFS -Class info is not synchronized To compare the service model class definitions in a specific cell with those defined in the BMC Atrium CMDB on Windows platforms.2.pclassinfo—Comparing service model classes on cells with class definitions in the BMC Atrium CMDB The service model class definitions are written to a BAROC file with the specified name.

This command returns the differences. For more information. see “Understanding publish environments” on page 192 and “Publishing from a Direct Publish source” on page 215. To compare the service model class definitions for all the cells registered with the BMC Impact Portal with those defined in the BMC Atrium CMDB. You can secure publish environments by applying a password. For more information about publish environments. if there are any. see “Publishing large service models” on page 293 252 BMC Impact Solutions Service Modeling and Publishing Guide . pclassinfo return codes For information about CLI return codes.penv—Managing publish environments NOTE On Windows platforms. NOTE When performing a penv init of a large service model the Stack Size and the Heap Size of the Publishing Server might need to be increased. See “Securing publish environments” on page 222. type the following command: pclassinfo -a This command returns the differences. penv—Managing publish environments Use the penv command to create and manage publishing environments when the source of the service model data is either the BMC Atrium CMDB (Atrium Publish) or the CLI pposter (Direct Publish). see “Understanding return codes for CLIs” on page 243. between the service model class definitions on the cell named with those defined in the BMC Atrium CMDB. you must enclose the cell list in quotation marks ("). if any. found between the classes defined in the BMC Atrium CMDB and the service model class definitions on all the cells found by the BMC Impact Publishing Server.

then Consumer. If HomeCellAlias is used then CellAliases must be set. If Cells contains more than one element. the destination cell must be found through the data instance: For components. HomeCell becomes deprecated because setting HomeCell is equivalent to setting Cells with one element. the attribute HomeCell is first searched.penv—Managing publish environments penv syntax penv <common options> [-f] (-e EnvId (close | init | open | set)|[-e EnvID] info) penv command options Table 67 lists the options for penv. Table 67 Option <common options> -c -h -? -i -l -q -p -t -u -v -z Cells = ["["] cell1 {. Defining a DirectPublish environment with HomeCell is supported for backward compatibility. consisting of all cell names found in CellAliases. cellN} ["]"] penv options (part 1 of 2) Description see “Understanding common command options for CLIs” on page 241 The pair of opening and closing brackets are allowed but not mandatory. The destination cell names are determined as follows: s If Cells contains a single element. then HomeCellAlias is searched. A DirectPublish environment can be created using either Cells or CellAliases. publish fails. otherwise publish fails. s s If no valid destination cell is found. Cells extend the existing concept of the HomeCell parameter. but it is deprecated.HomeCellAlias is searched. then this cell name is used to publish all data. Management data or non-SIM data (that is. instances other than components or relationships) are published to all cells. For relationships. Chapter 9 BMC Impact Publishing Server CLIs 253 . then for components and relationships. If a CellAliases is given. the attribute consumer_home_cell is searched. regardless of any cell information found in the data. a list of cells is built by the Publishing Server.

-e EnvID -f forces the command execution without prompting the user to confirm the initialization action. init. aliases of the environment are removed. asset dataset instances are removed and the asset dataset is removed. Specific to BMC Atrium CMDB environments If CloseAsset=T. depending on the type of environment. -s description describe request penv action commands: open. info penv provides additional functionality with these action commands: close. Some action commands work differently or have different requirements. default = F (false). and set. info. The impact dataset and all its instances are removed. set. close. open. default is T (true). default is T (true). you are prompted to confirm command execution. If CloseCells=T. Table 68 action command close Actions commands (part 1 of 2) General description removes data related to the specified environment. If the -f option is not specified. If CloseAliases=T. as described in Table 68. which releases the cells for usage in another environment. cells are reinitialized with empty ServiceModel. Atrium Publish or Direct Publish. Specific to Direct Publish environments 254 BMC Impact Solutions Service Modeling and Publishing Guide .penv—Managing publish environments Table 67 Option penv options (part 2 of 2) Description sets a unique identifier for the environment Default is PROD. init.

Chapter 9 BMC Impact Publishing Server CLIs 255 . Cells. there is no secondary datastore set sets or resets the parameters of the publish environment you can reset only parameters AutomatedPublish. CellAliases. and CellAliases. HomeCell. you cannot modify values for PublishModeServiceModel or PublishModeMgmtData parameters not applicable open data is stored only in the cell (and the source file). see “Configuration file and parameters for CLIs” on page 235. NewPassword1. Format. init initializes (or reinitializes) the asset and impact datasets of the specified environment creates the asset and impact datasets of also stores the settings for the specified environment and stores the environment in the environment settings in the cell BMC Atrium CMDB after the environment is opened. Level. use the -p “Level=1” option Display characteristics are — when HomeCell is not set. and NewPassword2 you can reset only parameters HomeCell. Password. For a complete list of parameters in the pclient. a empty string is returned () — cell alias values may include blank characters — cell name values do not include blank characters — values containing blank characters are quoted according to the rules for quoting BAROC strings you must include -p OriginId=Direct Publish as part of the command string if the EnvID is not included. Password. and NewPassword2 Atrium Publish environments—valid parameters for each action command Table 69 provides a brief description of the parameters in the pclient.conf configuration file for an Atrium Publish environment and specifies the parameters that are valid for each penv action command: close. use the -v option to display cell alias information. NewPassword1. and OriginId to display column headings.conf file and additional parameter information. open. info.penv—Managing publish environments Table 68 action command info Actions commands (part 2 of 2) General description displays information relevant to environments s s s Specific to BMC Atrium CMDB environments all parameters are valid except CellAliases Specific to Direct Publish environments relevant parameters are CellAliases. init. and set. HomeCell.

are removed from the BMC Atrium CMDB See “Configuration file and parameters for CLIs” on page 235. default is T. close info init open set yes yes yes Parameter name AssetDataSetId AssetDataSetType AssetUnderlyingDataSetId AutomatedPublish yes CellAliases yes yes CloseAliases enables (T) or disables (F) the removal of aliases of an environment. this releases the cells for use in another environment enables (T) or disables (F) the removal of the asset dataset along with all objects in the dataset yes CloseAsset yes CloseCells enables (T) or disables (F) the removal yes of all data instances (including management data) of the service model from the cells describes the environment specifies the name of the environment specifies to which cell to publish. In this case.ASSET. the entire service model is published to the specified cell. 256 BMC Impact Solutions Service Modeling and Publishing Guide . except for overlay publish environments defines cellalias-to-cellname pairs that are unique to a given environment You cannot define CellAliases with the CLI command penv.penv—Managing publish environments Table 69 Valid parameters for a BMC Atrium CMDB publish environment (part 1 of 2) Description defines the asset dataset ID. default is Overlay defines the underlying dataset for an overlay asset dataset.EnvId defines the asset dataset type as Regular or Overlay. based on their ServiceModelSet attribute. default is BMC. If HomeCell is set. default is BMC. CellAliases are not used defines the information displayed with info EnvDesc EnvName HomeCell yes yes yes yes Format InitEffectivelyMgmtData yes yes determines which asset management data instances.ASSET enables (T) or disables (F) automated publication for the publish environment.

causes initial service model data to be imported from instances in the asset dataset in the source environment EnvId. Data are created in the asset dataset of the environment.load file. Level NewPassword1 NewPassword2 OriginId Password PublishModeMgmtData determines the amount of information display by the info action command specifies a new password confirms a new password defines the source of the service model yes data specifies a password for authentication yes defines whether management data should be approached as overlay or as regular dataset defines whether components and impact relationships should be approached as overlay or as regular dataset causes the import of initial management data from instances in the . T (true) or F (false) See “Configuration file and yes parameters for CLIs” on page 235. causes initial management data to be imported from instances of the source environment EnvId.baroc files pointed to in the .penv—Managing publish environments Table 69 Valid parameters for a BMC Atrium CMDB publish environment (part 2 of 2) Description component and impact instances. yes yes yes yes yes yes yes yes yes yes yes PublishModeServiceModel yes SourceBarocMgmtData yes SourceBarocServiceModel yes SourceEnvMgmtData yes SourceEnvServiceModel yes Chapter 9 BMC Impact Publishing Server CLIs 257 . InitServiceModel specifies whether the service model is initialized. T (true) or F (false) See “Configuration file and yes parameters for CLIs” on page 235.load file. are removed from the BMC Atrium CMDB close info init yes open set Parameter name InitEffectivelyServiceModel determines which service model InitMgmtData specifies whether management data are initialized. based on their ServiceModelSet attribute. causes the import of initial service model data from instances in the .baroc files pointed to in the .

see “Examples of advanced environments” on page 200. MC_SM_RELATIONSHIP. CellAliases are not used. Table 70 Valid parameters for a Direct Publish environment Description defines cell alias and cell name pairs that are unique in an given environment defines cell names when cell aliases are not used defines the information displayed with info specifies to which cell to publish.penv—Managing publish environments Direct Publish environments—valid parameters for each action command Table 70 provides a brief description of the valid parameters in the pclient. For a complete list of parameters in the pclient. If HomeCell is set.conf file and additional parameter information.conf configuration file for a Direct Publish environment and specifies the parameters that are valid for each penv action command: close. determines the amount of information displayed by the info action command specifies a new password confirms a new password defines the source of the service model data specifies a password for authentication enables (T) or disables (F) the classes that may be published for the Direct Publish environments only if T. and all subclasses cannot be published yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes close info init open set yes yes yes Parameter name CellAliases Cells Format HomeCell Level NewPassword1 NewPassword2 OriginId Password SIM penv examples This section contains examples of penv info. and set. open. the whole service model is published to the specified cell. components and relationships of MC_SM_COMPONENT. In this case. 258 BMC Impact Solutions Service Modeling and Publishing Guide . init. see “Configuration file and parameters for CLIs” on page 235. only SIM classes may be published if F. info. For other examples of penv.

1 BMC.IMPACT.ASSET.TEST.IMPACT.Ghislain.1 BMC.ASSET BMC.TEST.penv—Managing publish environments Example 1—includes cell names and cell aliases.ASSET.1 Overlay Marcelle.Marcelle.PROD Overlay Regular BMC.1 BMC.0 (Build 666.ASSET. Request received and accepted by the Publishing Server requestId=Z00000emahxa59Xp9sZhyMZ6zowkZ AtriumCMDB Ghislain.343 . as an unpublished work. EXAMPLE $ penv -p "OriginId=AtriumCMDB" -p "Level=1" info BMC Impact Publishing Server Environment Manager v7.1 Overlay Current F cell1 cell2 cell3 test_ghislain test_ghislain test_ghislain BMC.TEST.343 .05/21/2007) Copyright 2005-2007 BMC Software. but column headings are missing because the -v option is not used. Inc.Marcelle.1 BMC.PROD Regular T '' 3 cell1 cell1 cell2 cell2 cell3 cell3 Chapter 9 BMC Impact Publishing Server CLIs 259 .1 Overlay Current Current F imtest 0 PROD BMC.1 BMC.TEST.TEST.TEST. All rights reserved.Marcelle.1 Overlay Current Current F '' 3 cell1 test_ghislain cell2 test_ghislain cell3 test_ghislain Marcelle. but no column headings In example 1.1 BMC. Request received and accepted by the Publishing Server requestId=Z00000emahxa59Xp9yZhyMZ6zowkZ AtriumCMDB Ghislain.TEST.05/21/2007) Copyright 2005-2007 BMC Software.IMPACT. as an unpublished work.IMPACT.TEST.Marcelle.IMPACT.TEST. Atrium Publish environments are displayed and cell names and cell aliases are displayed because the -p “Level=1” option is used.TEST.Ghislain.IMPACT.ASSET. Inc.TEST.1 BMC.1 Overlay Current F imtest PROD cell1 cell2 cell3 BMC.ASSET cell1 cell2 cell3 Example 2—raw format Example 2 displays the information in Raw format.Ghislain.TEST. rather than display format EXAMPLE $ penv -p "OriginId=AtriumCMDB" -p "Format=Raw" -p "Level=1" info BMC Impact Publishing Server Environment Manager v7.Ghislain. All rights reserved.0 (Build 666.

ASSET.1 BMC.1 Overlay Overlay Current F ImTest -----------------------------------------------------------------------------------EnvId AssetDataSetId ImpactDataSetId AssetDataSetType PublishModeMgmtData PublishModeServiceModel AutomatedPublish HomeCell PROD BMC.ASSET.1 Overlay Overlay Current F CellAlias CellName cell1 test_ghislain cell2 test_ghislain cell3 test_ghislain -----------------------------------------------------------------------------------------------------------------------------------------------------------------------EnvId AssetDataSetId ImpactDataSetId AssetDataSetType PublishModeMgmtData PublishModeServiceModel AutomatedPublish HomeCell Marcelle.05/21/2007) Copyright 2005-2007 BMC Software.1 BMC.IMPACT.IMPACT.Ghislain.1 BMC.1 BMC.Ghislain.TEST.ASSET BMC.343 .TEST.0 (Build 666.TEST.Marcelle. Request received and accepted by the Publishing Server requestId=Z00000emahxa59Xp9uZhyMZ6zowkZ OriginId: AtriumCMDB -----------------------------------------------------------------------------------EnvId AssetDataSetId ImpactDataSetId AssetDataSetType PublishModeMgmtData PublishModeServiceModel AutomatedPublish HomeCell Ghislain.IMPACT.TEST. cell aliases and column headings are included for an Atrium Publish environment. Inc. All rights reserved. as an unpublished work.PROD Regular T CellAlias CellName cell1 cell1 cell2 cell2 cell3 cell3 ------------------------------------------------------------------------------------- 260 BMC Impact Solutions Service Modeling and Publishing Guide . EXAMPLE $ penv -p "OriginId=AtriumCMDB" -p "Level=1" -v info BMC Impact Publishing Server Environment Manager v7.TEST.TEST.penv—Managing publish environments Example 3—includes cell aliases and column headings In Example 3.Marcelle.

EXAMPLE $ penv -p "OriginId=DirectPublish" -p "Level=1" -v info BMC Impact Publishing Server Environment Manager vDeveloper-ppa (Build 666. Normally. then you must publish the management data manually before the components and impact relationships by using the CLI command pposter. Request received and accepted by the Publishing Server requestId=Z00000f48fmlfkXp9tZdlMZ3dbyuZ OriginId: DirectPublish -----------------------EnvId HomeCell direct direct_cell -----------------------EnvId HomeCell direct_2 CellAlias CellName direct_al_1 d_cell_1 direct_al_2 d_cell_2 -----------------------EnvId HomeCell direct_3 direct_cell_3 ------------------------ pinit—Initializing a cell with service model data The pinit command copies the service model data of the publish environment to the specified cells. then the cells are automatically initialized with the data of the Atrium Publish environment to which they are assigned and default management data is also created on the cells. the BMC Impact Publishing Server initializes new cells automatically. Chapter 9 BMC Impact Publishing Server CLIs 261 .pinit—Initializing a cell with service model data Example 4—Direct Publish environment with cell aliases Example 6 is for a Direct Publish publish environment. as an unpublished work. Inc. If publish from BMC Atrium CMDB is enabled.343 xx/xx/2008) Copyright 2005-2008 BMC Software. You may need to use the pinit command to restore a cell’s service model when it is not in sync with the impact service model of BMC Atrium CMDB. Initializing a cell does not remove status values from component instances. Cell names and cell alias are displayed because of the -p “Level=1” option and column headings are displayed because the -v option is used. If publish from BMC Atrium CMDB is disabled. All rights reserved.

pinit—Initializing a cell with service model data For more information for a Direct Publish environment. see “Publishing large service models” on page 293. 262 BMC Impact Solutions Service Modeling and Publishing Guide . For more information. because a cell is not running).. you are prompted to confirm the initialization action.on page 241 t -v -z -a initializes HomeCell or the cells defined by CellAliases If one or more of the cells cannot be initialized (for example. -f forces the cell initialization without prompting you to confirm the initialization action If the -f option is not specified. There are no required options for pinit.cellName2[. none of them are initialized and the request fails. see “Initializing a cell from a Direct Publish environment” on page 220.]] |-a ] -e EnvId [-s Description] pinit command options Table 71 lists the command options for pinit.. pinit syntax pinit <common options> [-f] [-n cellName1[. NOTE When performing a pinit of a large service model the Stack Size and the Heap Size of the Publishing Server might need to be increased. Table 71 Option pinit options (part 1 of 2) Description see “Understanding common command options for CLIs” <common options> -c -h -? -i -q -l -p .

Atrium Publish and CellPublish). OriginId=AtriumCMDB or OriginId=CellPublish). if the same cell contains different environments (for example. If one or more of the cells cannot be initialized (for example. because a cell is not running).) pinit Chapter 9 BMC Impact Publishing Server CLIs 263 . type the following command. (The short host name is the unqualified version of the host computer name. If such a cell does not exist or does not belong to the considered environment. the command fails. It specifies either an Atrium CMDB environment or a Cell Publish environment. If a cell name is not specified.. then only part of the cell’s data is reinitialized. The default value is PROD.cellName2[ . you must enclose the cell list in quotation marks ("). So. On Windows platforms. pinit examples This section provides examples of using the pinit command to initialize or reinitialize a cell with service model data.. When you execute a pinit command for a specific environment. depending on the value of OriginId.pinit—Initializing a cell with service model data Table 71 Option pinit options (part 2 of 2) Description For a BMC Atrium CMDB publish environment: specifies the cells to initialize or reinitialize with the impact service model. the default cell name (the unqualified version of the host computer name) is used.]] -s description -e environmentID describes request sets environment identifier to environmentID. -n cellName1[. only the data for that environment is reinitialized. none of them are initialized and the request fails. Initializing a cell with the production service model data from the BMC Atrium CMDB To initialize or reinitialize the cell whose name is the short host name (default cell name) with the BMC Atrium CMDB production service model. For example.

Initializing a cell’s data for a Direct Publish environment To initialize the cell austin in the Direct Publish environment Sales. either in the pclient. 264 BMC Impact Solutions Service Modeling and Publishing Guide .Sales. for example. type the following command. pinit -a If one or more of the specified cells cannot be initialized. type the following command: pinit -n jana Initializing all BMC Impact Portal-registered cells with the BMC Atrium CMDB production service model To initialize all the cells registered with the BMC Impact Portal with the BMC Atrium CMDB production service model. pinit return codes For information about CLI return codes. pinit -n austin -e Sales This command removes all data of the service model in the Direct Publish environment Sales. this corresponds to data that has the slot publish_env_id set to DirectPublish. if a cell is not running. none of them are initialized and the request fails. If the BMC Impact Publishing Server has both Atrium CMDB and Direct Publish enabled.conf file or in the CLI penv command string as -p “OriginId=DirectPublish”. see “Understanding return codes for CLIs” on page 243.pinit—Initializing a cell with service model data Initializing a specific cell with the BMC Atrium CMDB production service model To initialize a specific cell named ”jana” with the BMC Atrium CMDB production service model. type the following command. then you must specify OriginId=DirectPublish. In the cell.

plog syntax plog <common options> RequestID [-r] [-s] [-w] plog command options The required command option for plog is the Request ID. Table 72 Option <common options> -c -h -? -i -q -l -p -t -v -z RequestID -r -w -s plog options Description see “Understanding common command options for CLIs” on page 241 the ID of a specific publish request request the replies part of the XML log request the instances to be published request the process report of the XML log plog examples This section provides examples of using the plog command to obtain and output the XML log for a specific service model publishing request.plog—Obtaining the XML log for a request plog—Obtaining the XML log for a request Use the plog command to obtain and optionally view the XML log for a publishing request. The plog command requests the XML log for a specific request from the BMC Impact Publishing Server and routes it in XML format to standard output. Use the plogdisplay command with the plog command to convert the XML log to text and to output the text to standard output. substituting the request ID in this example: plog -s Z00000e8mu7xw9Xpa1ZfsMZeg4v1Z Chapter 9 BMC Impact Publishing Server CLIs 265 . and send it to standard output for viewing. type a command similar to the following. Table 72 lists the options for plog. Viewing the XML log for a specific publishing request as stdout To obtain the XML log for a specific publishing request.

it can be either standard input (-@) or a specified file. you pipe the output of the plog command through the plogdisplay command to convert it to text format for output. 266 BMC Impact Solutions Service Modeling and Publishing Guide . Table 73 lists the options for plogdisplay. convert it to text format. substituting the request ID: plog -s Z00000e8mu7xw9Xpa1ZfsMZeg4v1Z | plogdisplay -@ Using this command. type a command similar to the following. plogdisplay—Converting the XML log for a request to text format Use the plogdisplay command to convert the XML log for a request to text and output it to standard output. plog return codes For information about CLI return codes. plogdisplay syntax plogdisplay <common options> (-@ | RequestLogFile) plogdisplay command options You must specify an input for the command. see “Understanding return codes for CLIs” on page 243. and output it to standard output for viewing.plogdisplay—Converting the XML log for a request to text format Viewing the XML log for a specific publishing request as a text in stdout To obtain the XML publishing log for a specific publishing request. See “plogdisplay— Converting the XML log for a request to text format” on page 266. Use this command with the plog command.

-t. If you do include the authentication option (-i). substituting the correct xml file name: publish -r myLog.plogdisplay—Converting the XML log for a request to text format Table 73 Option plogdisplay options Description <common options except: -r. -@ | RequestLogFile specifies the source of input to display Use one of these arguments: s s Use -@ to indicate standard input as the source to display. and -u. Converting an XML log file for a specific publishing request to text To convert the XML log file for a publishing request to text and output it to standard output. type a command similar to the following command. For a specific publishing request. plogdisplay examples This section provides examples of using the plogdisplay command to convert an XML log file for a publishing request to text and output it to standard output.xml plogdisplay myLog. the user is authenticated. -t. You do not need to authenticate a user with the BMC Portal when using this command. To view a specific publishing log in text format. type the name of the XML log file as the source to display.xml Viewing the XML log for a specific publishing request as a text in stdout You pipe the output of the plog command through the plogdisplay command to convert it to text format and output it to standard output. and u> see “Understanding common command options for CLIs” on page 241 This command does not interact with the BMC Impact Publishing Server so it does not accept these CLI common options: -r. type the following command: plog -r -s Z00000e8mu7xw9Xpa1ZfsMZeg4v1Z | plogdisplay -@ Chapter 9 BMC Impact Publishing Server CLIs 267 .

as shown in Table 74.conf and create a Direct Publish environment with a penv command. For information about these error codes. relationships. To use the pposter command. pposter—Sending service model objects to a cell You use the pposter command to send service model objects (components. to the generated publishing CLI trace file pcli.trace. you must set the parameter DirectPublishOrigin to T in pserver. at the command prompt. Table 74 Code 0 plogdisplay return codes Description success a number error other than 0 When a CLI command exits with a return value other than 0.pposter—Sending service model objects to a cell plogdisplay return codes The plogdisplay command returns a nonzero value if it encounters any errors during execution. see BMC Impact Solutions Infrastructure Administration Guide. For information on mposter. “penv— Managing publish environments” on page 252. additional textual information on the error cause is displayed to standard output and. see “Understanding return codes for CLIs” on page 243. and SIM management data) to a cell for Direct Publish environments only by using BMC Impact Publishing Server. type: penv -e EnvId -p “OriginId=DirectPublish” open -p “HomeCell=cellName” For more information about creating environments and the penv command. pposter syntax pposter <common options> -e EnvId sourceFile {sourceFile} 268 BMC Impact Solutions Service Modeling and Publishing Guide . The main difference between pposter and mposter is that pposter communicates with a Publishing Server and uses an environment identifier (EnvId) to refer to a specific service model and enables the deletion of service model objects. It returns a zero (0) value upon a successful execution. For example. possibly.

false (default) or omitted. then existing published data is replaced with the data of the Baroc file. then the new data will have mc_udid that differs from the existing data. true. execute pposter -p "Init=T" with an empty Baroc file or without Baroc file. If the data in the Baroc file has no mc_udid. pposter uses the following parameter in the MCELL_HOME/etc/pclient. true (default). pposter publishes components (instances of subclasses of MC_SM_COMPONENT) and impact relationships (instances of subclasses of MC_SM_RELATIONSHIP) to their HomeCell. All data is always published to all cells of the environment. If Init is set to F. existing published data of the DirectPublish publish environment is removed and new data as defined in the Baroc file is added. To remove all published data of a DirectPublish publish environment from a cell. then existing data is updated with the new data. Init=T/F sourceFile file that contains the data to send See “Source files for pposter” on page 270. In other words. You must specify a environment ID and a source file for pposter. pposter publishes data other than SIM data.conf file: ContinueOnFailure=T/F Chapter 9 BMC Impact Publishing Server CLIs 269 . pposter requires confirmation (-f option). If Init is set to T. It is not possible to publish components (instances of subclasses of MC_SM_COMPONENT) and impact relationships (instances of subclasses of MC_SM_RELATIONSHIP). Instances of all other classes are considered Service Impact Management Data and are published to all cells of the environment. When using Init=T.pposter—Sending service model objects to a cell pposter command options Table 71 lists the options for pposter. Table 75 Option <common options> -c -h -? -i -q -l -p -r -s -t -u -v -z -e EnvId SIM=T/F pposter options Description see “Understanding common command options for CLIs” on page 241 sets the environment identifier to EnvID to specify a service model If SIM is set to T. false. If SIM is set to F.

See “pposter example 3—using cell aliases” on page 275. If ContinueOnFailure is set to T. dnew + is assumed. update it The space between dnew and + is required. consumer_home_cell and provider_home_cell slots.HomeCellAlias for relationships. define the contents in BAROC format with the appropriate data additions. Command dnew + Definition create a new data instance. ignore the dnew . dnew create a new data instance The space between dnew and . do not change it. you must provide a value for the HomeCell slot for each component. A relationship is sent to the cell of its consumer component. 270 BMC Impact Solutions Service Modeling and Publishing Guide . false (default). pposter stops as soon as invalid data in the source file is encountered and no data is sent to the cell. This is the default. BMC Impact Publishing Server uses the alias table of the environment and replaces them with the values in the HomeCell. if none of the three commands are present at the beginning of a line in a source file. using the following commands. and a value for the provider_home_cell and the consumer_home_cell slots for each relationship. skipping invalid data in the source file. you must specify a value for the provider_classname slot. pposter sends as much data as possible. not even those items processed before the incorrect data in the source file. and Consumer.HomeCellAlias and Provider. If this instance exists.command. modifications. dmodify ddelete change the existing data instance delete the existing data instance For each data instance. provide a value for mc_udid. but the mc_udid is still needed to modify or delete the existing data in cell. You can also use cell aliases by specifying values for HomeCellAlias for components.pposter—Sending service model objects to a cell If ContinueOnFailure is set to F. or deletions. For environments that do not have a value for the HomeCell slot. if this instance exists. See “pposter example 2—two cells” on page 273. Source files for pposter You create a source file and. except if all existing data is replaced when publishing. For relationships in which the consumer and provider components belong to different cells. You can publish new data instances without specifying a value for mc_udid. true. Since these slots do not exist in the class definition of the cell.is required.

mc_udid = comp1. at the command prompt. or ddelete commands. possibly prepended with dnew (+ or -). Inc. dmodify. Name = comp1. followed by a Return. that depends on a database (comp1). consumer_id = comp1. must terminate with END. pposter example 1 This example shows how to create a simple service model. Name = comp1. type the following command: EXAMPLE pposter -v -e MY_ENV FileDnew. modify the service model. provider_id = comp0.343 . as an unpublished work. it is named FileDnew. and delete the service model. Name = comp0. For this example.xx/xx/2007) Copyright 2005-2007 BMC Software. END BMC_Application. END To send this new service model to the cell.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666. The service model consists of three objects: an application (comp0). Publish successfully applied. Chapter 9 BMC Impact Publishing Server CLIs 271 . create a source file. END BMC_Impact. PropagationModel = DIRECT. All rights reserved.baroc: EXAMPLE BMC_DataBase. mc_udid = comp0.pposter—Sending service model objects to a cell Data instances. mc_udid = rel. Creating a service model To create this service model. and the relationship between the two. The environment is MY_ENV and the HomeCell is MY_HOMECELL.

at the command prompt.baroc: EXAMPLE dmodify BMC_DataBase. type the following command: EXAMPLE pposter -v -e MY_ENV FileDdelete. Deleting a service model To delete the service model. it is named FileDdelete. it is named FileDModify.xx/xx/2007) Copyright 2005-2007 BMC Software.baroc: EXAMPLE ddelete BMC_DataBase. create a source file. For this example. as an unpublished work.xx/xx/2007) Copyright 2005-2007 BMC Software. as an unpublished work.pposter—Sending service model objects to a cell Modifying a service model To modify the service model by adding impact costs. mc_udid = comp1.343 . END To send this modification to the service model to the cell. 272 BMC Impact Solutions Service Modeling and Publishing Guide . type the following command: EXAMPLE pposter -v -e MY_ENV FileDmodify. Publish successfully applied. All rights reserved. For this example. mc_udid = rel. create a source file. Inc. Publish successfully applied. ImpactCostPerSec = 5. END ddelete BMC_Impact. ImpactCostPerSecOut = 2. END ddelete BMC_Application. mc_udid = comp0.343 .baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666. Inc. at the command prompt.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666. END To send this deletion of the service model to the cell. All rights reserved. mc_udid = comp0.

pposter—Sending service model objects to a cell

pposter example 2—two cells
This service model consists of three objects: an application (comp0) that belongs in cell_1, a database (comp1) that belongs in cell_2, and the relationship between the two.

Creating a service model for two cells
To create this service model, create a source file. For this example, it is named FileDnew.baroc:

EXAMPLE
BMC_DataBase; HomeCell = cell_1; mc_udid = comp0; Name = comp0; END BMC_Application; HomeCell = cell_2; mc_udid = comp1; Name = comp1; END BMC_Impact; provider_home_cell = cell_1; consumer_home_cell = cell_2; provider_classname = BMC_DataBase; mc_udid = rel; provider_id = comp0; consumer_id = comp1; PropagationModel = DIRECT; END

To send this new the service model to the cells, at the command prompt, type the following command:

EXAMPLE
pposter -v -e MY_ENV FileDnew.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2007 BMC Software, Inc. as an unpublished work. All rights reserved. Publish successfully applied.

Chapter 9

BMC Impact Publishing Server CLIs

273

pposter—Sending service model objects to a cell

Modifying a service model for two cells
To modify the service model by adding impact costs, create a source file. For this example, it is named FileDModify.baroc:

EXAMPLE
dmodify BMC_DataBase; HomeCell = cell_1; mc_udid = comp0; ImpactCostPerSec = 5; ImpactCostPerSecOut = 2; END

To send this modification to the service model to the cells, at the command prompt, type the following command:

EXAMPLE
pposter -v -e MY_ENV FileDmodify.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666.343 - xx/xx/2008) Copyright 2005-2008 BMC Software, Inc. as an unpublished work. All rights reserved. Publish successfully applied.

Deleting a service model
To delete the service model, create a source file. For this example, it is named FileDdelete.baroc:

EXAMPLE
ddelete BMC_DataBase; HomeCell = cell_1; mc_udid = rel; END ddelete BMC_Application; HomeCell = cell_2; mc_udid = comp0; END ddelete BMC_Impact; consumer_home_cell = cell_1; mc_udid = comp1; END

To send this deletion of the service model to the cell, at the command prompt, type the following command:

274

BMC Impact Solutions Service Modeling and Publishing Guide

pposter—Sending service model objects to a cell

EXAMPLE
pposter -v -e MY_ENV FileDdelete.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2007 BMC Software, Inc. as an unpublished work. All rights reserved. Publish successfully applied.

pposter example 3—using cell aliases
This service model consists of three objects: an application (comp0) that belongs in cell_1, a database (comp1) that belongs in cell_2, and the relationship between the two. For this example, cell aliases are as follows:
cell alias c_alias_1 c_alias_2 cell name cell_1 cell_2

Creating a service model with cell aliases
To create this service model, create a source file. For this example, it is named FileDnew.baroc:

EXAMPLE
BMC_DataBase; HomeCellAlias = c_alias_1; mc_udid = comp0; Name = comp0; END BMC_Application; HomeCellAlias = c_alias_2; mc_udid = comp1; Name = comp1; END BMC_Impact; Provider.HomeCellAlias = c_alias_1; Consumer.HomeCellAlias = c_alias_2; provider_classname = BMC_DataBase; mc_udid = rel; provider_id = comp0; consumer_id = comp1; PropagationModel = DIRECT; END

Chapter 9

BMC Impact Publishing Server CLIs

275

pposter—Sending service model objects to a cell

To send this new the service model to the cells, at the command prompt, type the following command:

EXAMPLE
pposter -v -e MY_ENV FileDnew.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2007 BMC Software, Inc. as an unpublished work. All rights reserved. Publish successfully applied.

Modifying a service model with cell aliases
To modify the service model by adding impact costs, create a source file. For this example, it is named FileDModify.baroc:

EXAMPLE
dmodify BMC_DataBase; HomeCellAlias = c_alias_1; mc_udid = comp0; ImpactCostPerSec = 5; ImpactCostPerSecOut = 2; END

To send this modification to the service model to the cell, at the command prompt, type the following command:

EXAMPLE
pposter -v -e MY_ENV FileDmodify.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2007 BMC Software, Inc. as an unpublished work. All rights reserved. Publish successfully applied.

276

BMC Impact Solutions Service Modeling and Publishing Guide

pposter—Sending service model objects to a cell

Deleting a service model with cell aliases
To delete the service model, create a source file. For this example, it is named FileDdelete.baroc:

EXAMPLE
ddelete BMC_DataBase; HomeCellAlias = c_alias_1; mc_udid = rel; END ddelete BMC_Application; HomeCellAlias = c_alias_2; mc_udid = comp0; END ddelete BMC_Impact; Consumer.HomeCellAlias = c_alias_2; mc_udid = comp1; END

To send this deletion of the service model to the cell, at the command prompt, type the following command:

EXAMPLE
pposter -v -e MY_ENV FileDdelete.baroc BMC Impact Publishing Server Data Poster vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2007 BMC Software, Inc. as an unpublished work. All rights reserved. Publish successfully applied.

Return codes for pposter
Table 76 describes the return codes specific to the pposter command. For return (or error exit) codes common to all BMC Impact Publishing Server CLI commands, see “Understanding return codes for CLIs” on page 243. Table 76
0 50

pposter return codes (part 1 of 2)
Description All data commands in the source files are successfully applied to all cells of the environment. Publish has successfully completed, but some errors were detected. This can occur only if ContinueOnFailure is set to T (true). For more information, see the publish log; the -v option provides more detail.

Return Code

51

BMC Impact Publishing Server refused to initiate the publish process. The actual cause of the error (for example, another publish is in progress) is displayed on the standard error device. An error is returned by BMC Impact Publishing Server when data are being sent to it. For more information, see the publish log; the -v option provides more detail.

52

Chapter 9

BMC Impact Publishing Server CLIs

277

pscontrol—Sending a command to BMC Impact Publishing Server

Table 76
53

pposter return codes (part 2 of 2)
Description An error is returned by BMC Impact Publishing Server when data are effectively applied to the cells. For more information, see the publish log; the -v option provides more detail.

Return Code

54 55

There is a syntax or invalid BAROC object in the source file. There is an I/O error with a source file, for example, no source file or the source file cannot be opened.

pscontrol—Sending a command to BMC Impact Publishing Server
Use the pscontrol command to send a command (automated, manual, stop) to the BMC Impact Publishing Server. By default, pscontrol only sends the command to the BMC Impact Publishing Server. To monitor that the mode effectively changed to Automated or Manual, you can use the -u option.

pscontrol syntax
pscontrol [-c ConfigFile] [-h|-?] [-i User/Password[@Host[/Port] [,Host[/Port] [,...]]] [-q] [-l HomeLocation] {-p "Var=Value"} [-t ConnectionInitTimeout] [-u RequestTimeout] [-v] [-z] [-f] (automated | manual | stop)

pscontrol command options
Table 77 lists the options for the pscontrol command. There are no required command options for the pscontrol command. Table 77
Options <common options> -c -h -i -q -l -p -t -u -v -z -f stop

pscontrol command options (part 1 of 2)
Description

see “Understanding common command options for CLIs” on page 241
The -u option default for pscontrol is 0 seconds. forces the command to run without prompting the user to verify the execution of the command

stops the BMC Impact Publishing Server

278

BMC Impact Solutions Service Modeling and Publishing Guide

pscontrol—Sending a command to BMC Impact Publishing Server

Table 77
Options

pscontrol command options (part 2 of 2)
Description turns automated publishing on turns automated publishing off

automated manual

pscontrol examples
This section contains examples of usage of the pscontrol command. Figure 29 contains an example of the pscontrol stop command, which stops the BMC Impact Publishing Server. Figure 29 pscontrol stop example

$ pscontrol stop BMC Impact Publishing Server Controller vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2006 BMC Software, Inc. as an unpublished work. All rights reserved. Please confirm control command (stop) (type y (yes) / n (no). Default is n): y Publishing Server is stopping

Figure 30 contains an example of the pscontrol automated command, which restarts automated publishing. Figure 30 pscontrol automated example

pscontrol -f automated BMC Impact Publishing Server Controller vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2006 BMC Software, Inc. as an unpublished work. All rights reserved. Automated publishing is starting

Figure 31 contains an example of the pscontrol automated command using the -u option. Figure 31 pscontrol automated -u example

pscontrol -f -u 300 automated BMC Impact Publishing Server Controller vDeveloper-ppa (Build 666.343 - xx/xx/2007) Copyright 2005-2006 BMC Software, Inc. as an unpublished work. All rights reserved. Automated publishing is starting Automated publishing is started

Chapter 9

BMC Impact Publishing Server CLIs

279

causes the BMC Impact Publishing Server to run in the foreground instead of as a daemon in the background (On Windows platforms. Please confirm control command (manual) (type y (yes) / n (no). Figure 32 pscontrol manual example pscontrol manual BMC Impact Publishing Server Controller vDeveloper-ppa (Build 666.343 . as an unpublished work.) -b psname identifies the name of the BMC Impact Publishing Server. There are no required command options for the pserver command. Default is n): y Automated publishing is stopping pserver—Starting the BMC Impact Publishing Server service Use the pserver command to start the Publishing Service service. defaults to ps_hostname 280 BMC Impact Solutions Service Modeling and Publishing Guide .pserver—Starting the BMC Impact Publishing Server service Figure 32 contains an example of the pscontrol manual command. Inc. pserver syntax pserver [-b psname] [-c ConfigFile] [-d] [-h|-?] [-q] [-l HomeLocation] {-p "Var=Value"} [-v] [-z] pserver command options Table 78 lists the options for the pserver command.xx/xx/2007) Copyright 2005-2007 BMC Software. All rights reserved. the BMC Impact Publishing Server always runs in the foreground. Table 78 Options <common options> -? -c -h -p -q -v -z -d pserver command options Description see “Understanding common command options for CLIs” on page 241 on UNIX platforms. which stops automated publishing.

readable format. pshowlog example This section provides examples of using the pshowlog command to obtain and output the XML log in readable format for a specific service model publishing request. pshowlog syntax pshowlog [ -i User/Password[@Host[/Port][. Table 79 lists the options for pshowlog. -i RequestID pshowlog options Description see “Understanding common command options for CLIs” on page 241 the ID of a specific publish request Any non-supported options added to the pshowlog command results in the usage being printed to stdout (standard out).. Type a command similar to the following. type a command similar to this example: Chapter 9 BMC Impact Publishing Server CLIs 281 . substituting the request ID in this example: pshowlog Z00000e8mu7xw9Xpa1ZfsMZeg4v1Z To pass the Impact Administration Server host name and port number.]]] requestId | -h pshowlog command options The required command option for pshowlog is the Request ID..Host[/Port][.. for any request to the BMC Impact Publishing Server.pshowlog—Obtaining the XML log in user-friendly format pshowlog—Obtaining the XML log in user-friendly format Use the pshowlog command to view the XML log. The pshowlog command requests the XML log for the specific request from the BMC Impact Publishing Server and routes it in readable format to standard output.. pshowlog displays the log in a non-XML. Table 79 Option -h. However. The pshowlog command provides a quick way to display all the information shown by the plog command with all command options specified. in a user-friendly format.

psstat—Displaying status of BMC Impact Publishing Server Use the psstat command to determine if the BMC Impact Publishing Server is running and in what mode.. psstat returns the following message: 282 BMC Impact Solutions Service Modeling and Publishing Guide . BMC Impact Publishing Server running with automated publish enabled When the BMC Impact Publishing Server is running and automated publish is enabled. Table 80 lists the options for the psstat command. psstat syntax psstat [-c ConfigFile] [-h|-?] [-i User/Password [@Host[/Port] [. see “Understanding return codes for CLIs” on page 243..]]] [-q] [-l HomeLocation] {-p "Var=Value"} [-t ConnectionInitTimeout] [-u RequestTimeout] [-v] [-z] psstat command options There are no required command options for the psstat command.psstat—Displaying status of BMC Impact Publishing Server pshowlog -i user/user@vm-w23-sms29/3084 Z00000fo8jh7evXp9yZ6jMZapgqvZ pshowlog return codes For information about CLI return codes. Table 80 Options <common options> psstat command options Description see “Understanding common command options for CLIs” on page 241 psstat examples This section provides examples of using the psstat command to view the status of the BMC Impact Publishing Server and whether it is in automated or manual mode.Host[/Port] [.. automated or manual.

publish—Publishing a service model or viewing instances to be published Use the publish command to s publish the service model without viewing what is being published (default) view the service model instances. relationship.]]] [-e EnvId] [-w [-o File] [-m]] [-s Description] Chapter 9 BMC Impact Publishing Server CLIs 283 . relationships.. psstat returns the message Request Timeout Expired.publish—Publishing a service model or viewing instances to be published psstat Started . including components. and management data instances that are marked for publishing publish the entire service model or selected service model class instances and view a listing of the component. BMC Impact Publishing Server without the BMC Atrium CMDB In an environement without the BMC Atrium CMDB.. psstat returns the status of publishing server as Started.UdId[. and management data instances being published s s publish syntax publish <common options> [-d ClassName.UdId[. psstat returns the following message: psstat Started .Automated mode BMC Impact Publishing Server running with automated publish disabled When the BMC Impact Publishing Server is up and automated publish is disabled..ClassName.Manual mode BMC Impact Publishing Server not running (or cannot be contacted) When the BMC Impact Publishing Server is down or cannot be reached.

The default value is PROD. including components. Other values will result in error messages if using a BMC Impact Publishing Server version prior to 5..U dId[.x. -o OutputFile -w -s description -e environmentID publish examples This section provides examples of using the publish command to view the service model class instances to be published (including components. including component. and management data instances.UdId[.publish—Publishing a service model or viewing instances to be published publish command options Table 81 lists the options for the publish command.. Table 81 Options <common options> [-d ClassName. relationships. to be published to the specified output file (relevant only with the -w option) view the service model class instances marked for publishing describe request publishes in environmentID. that you viewed (relevant only with the -w option) prints the service model class instances.ClassName. and management data publishes the service model class instances. There are no required command options for the publish command. type the following command: publish 284 BMC Impact Solutions Service Modeling and Publishing Guide . which can include component.. relationship. relationship. relationships.]]] -m publish command options Description see “Understanding common command options for CLIs” on page 241 publishes the specified service model object class instances. and management data) and to publish them. Publishing the service model without viewing it To publish a service model without viewing the objects queued for publish. and management data.

see “Understanding return codes for CLIs” on page 243. type the following command: publish -w -m Viewing hard-deleted service model instances and publishing deletions To view the service model objects that have been hard-deleted from the production asset dataset.Viewing the service model class instances to be published prior to publishing To view the service model class instances that are queued for publishing. Chapter 9 BMC Impact Publishing Server CLIs 285 . but that still exist in cells. type the following command: publish -p “Purge=T” -p “Merge=F” -w To view the service model objects that have been hard-deleted from the production asset dataset. type the following command: publish -w Viewing what is queued to publish and then publishing the objects To view and then publish the service model objects that are marked for publishing. and then to publish the deletions to the cells. but that still exist in cells. type the following command: publish -p “Purge=T” -p “Merge=F” -w -m publish return codes For information about CLI return codes.

286 BMC Impact Solutions Service Modeling and Publishing Guide .

. . . . . . . . . . . . . . . . . . No publication after successful promotion . . . Automated publication after reconciling reconciliation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing large service models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Impact Service Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using dynamic ports with the ARDBC Notify plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other BMC Impact Service Model Editor Troubleshooting Options . . . . . . . Avoiding duplicate CIs. . . . . . . . . . . . . . . . . . Appendix A Troubleshooting 287 . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Impact Publishing Server service or daemon fails to start . . . . . . . . . . . . . . . . . Publishing failures and reattempts . . . . . . . . . . . . Using the BMC Impact Service Model Editor log. . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying that BMC Impact Publishing Server is running . . . . . . . . . . . . Reconciliation jobs hang . . . . . . . . . . . . . . . . . . . . . . Another publish request is ongoing . . . . . . . . . . . . . . . . Diagnosing publication failures . BMC Impact Publishing Server . . . . . . . . . . . . . . . . . . . . . BMC Impact Publishing Server does not reply to requests. Stopping BMC Impact Publishing Server when JMS is not running . . . . . . . . . . . . . . . . . . .Appendix A 288 288 292 292 293 293 293 293 295 296 296 297 297 298 302 303 303 303 304 A Troubleshooting This section describes problem solving for the BMC Impact Service Model Editor. . . . . . . . . the BMC Impact Publishing Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and the BMC Impact Service Model Integration with HP OpenView Operations. . BMC Impact Service Model Integration with HP OVO . . . . . . . . . . . . . . . . . . . . . . . . . Using trace files . . . . . . . . . . . . . . . .

see “To set log file preferences” on page 155. ID: BMCSME000004. Level: INFO] Logging level changed to ALL. 2006 4:57:08 PM [Seq: 0. 288 BMC Impact Solutions Service Modeling and Publishing Guide . Version: 5. 2006 4:57:09 PM [Seq: 2. ID: BMCSME001010. The following illustration depicts representative log entries of the BMC Impact Service Model Editor GUI log.0. Level: INFO] Loaded 1 workspaces from server.0 Build: 1124943 Nov 27. 2006 5:01:03 PM [Seq: 4. Level: INFO] FindPanel Creation done Nov 27. ID: BMCSME000006. Nov 27. you can enable the log for the BMC Impact Service Model Editor server and the Java Web Start console. To record different levels of information for debugging purposes. Figure 33 BMC Impact Service Model Editor log By default.BMC Impact Service Model Editor BMC Impact Service Model Editor This section describes problem solving for the BMC Impact Service Model Editor product. ID: BMCSME000018. Outside BMC Impact Service Model Editor. Level: INFO] Service Model Editor console started. this log captures startup and shutdown information. choose Tools => View Log. Nov 27. Using the BMC Impact Service Model Editor log To open the BMC Impact Service Model Editor Log dialog box and view the log messages. 2006 4:57:42 PM [Seq: 3.

apache.logging.jboss.dir}/log/portal.xml configuration file of the JBoss application server.xml configuration file is located on the system where the BMC Portal is installed in the directory: BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf. you must modify the log4j.%c{1}> %m%n"/> </layout> </appender> <category name="com.appender.server.OnlyOnceErrorHandler"/> <param name="Threshold" value="DEBUG"/> <param name="File" value="${jboss.PatternLayout"> <param name="ConversionPattern" value="<%5.1p. and debugger information. open the BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf/log4j. You can modify the log4j.util.sms.home.Using the BMC Impact Service Model Editor log BMC Impact Service Model Editor Server The BMC Impact Service Model Editor Server records commands.bmc.xml file to send its output to s s s the BMC Portal log file a console window a console window and the JBoss log file To send BMC Impact Service Model Editor Server debug output to the BMC Portal log file 1 In an appropriate editor.%d{MM/dd/yy HH:mm:ss z}.sme"> <priority value="DEBUG"/> <appender-ref ref="SME_FILE"/> </category> Appendix A Troubleshooting 289 .log"/> <param name="Append" value="true"/> <param name="MaxFileSize" value="100MB"/> <param name="MaxBackupIndex" value="10"/> <layout class="org.logging.xml.RollingFileAppender"> <errorHandler class="org. To view the output of the BMC Impact Service Model Editor Server log. runtime exceptions.log4j. <appender name="CLUSTER" class="org.jboss. The log4j. 2 Add the following appender and category elements under the Setup the Root Category heading.

jboss.log4j.Category> Message\n --> <param name="ConversionPattern" value="<%5.log4j. and enter the following command: BMC_PORTAL_KIT_HOME/tools/jboss/bin/jboss.%c{1}> %m%n"/> </layout> </appender> <category name="com.apache.Date.ConsoleAppender"> <errorHandler class="org.bmc. 290 BMC Impact Solutions Service Modeling and Publishing Guide .PatternLayout"> <!-.Using the BMC Impact Service Model Editor log To send BMC Impact Service Model Editor Server debug output to a console window 1 In an appropriate editor.util. 2 Add the following appender and category elements under the Setup the Root Category heading.out"/> <param name="Threshold" value="DEBUG"/> <layout class="org. open the BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf/log4j.OnlyOnceErrorHandler"/> <param name="Target" value="System.sh 4 Restart the BMC Portal application server.xml. and enter the following command: BMC_PORTAL_KIT_HOME\appserver\websdk\bin\run. <appender name="SME_CONSOLE" class="org.apache. we shorten the context info from log4j and use the following format: <last letter of Priority.sms. open a terminal window.logging.bat s For Solaris.sme"> <priority value="DEBUG"/> <appender-ref ref="SME_CONSOLE"/> </category> 3 To view debug output in a console window.%d{MM/dd/yy HH:mm:ss z}.Since sdk logger prints its own context info. open a Command Prompt window. start the BMC Impact Portal from a shell window: s For Windows.1p.

Using the BMC Impact Service Model Editor log To send BMC Impact Service Model Editor Server debug output to a console window and the BMC Portal log file 1 In an appropriate editor. 3 On the Advanced tab. execute the following command: %JAVA_HOME%\jre\javaws\javaws. 4 To select an existing file. click Choose Log File Name. To enable Java Web Start logging 1 Open the Java Web Start Application Manager console in one of the following ways: s s Double-click the Java Web Start icon on your desktop. from the Command Prompt. Under Windows. 2 Add both sets of appender and category elements for sending output to the BMC Portal log and to a console window as described in the preceding two procedures. in the Output Options area.xml. Java Web Start logging The Java Web Start log helps you to identify BMC Impact Service Model Editor deployment problems.sme. Appendix A Troubleshooting 291 . select Log Output.exe 2 In the Java Web Start Application Manager console.sme"> <priority value="DEBUG"/> <appender-ref ref=”SME_CONSOLE”/> <appender-ref ref="SME_FILE"/> </category> NOTE The appender element FILE is defined under the Preserve Messages in a local file heading of the default log4j.bmc. <category name="com. 3 Add the following ref subelement pointing to the SME_FILE under the category element with the value com.bmc. choose Start => Programs => Java Web Start => Java Web Start or. open the BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf/log4j.xml file.sms.sms. or enter a file path in the Log File Name box. choose File => Preferences.

and publish are independent processes. BMC recommends that you monitor the success or failure of publications that are automatically started. restart the Remedy AR System server service. BMC Impact Publishing Server This section contains information on troubleshooting problems with the BMC Impact Publishing Server and publication failures. For information about publication logs. you may receive a blank error dialog box when performing commands in BMC Impact Service Model Editor. Other BMC Impact Service Model Editor Troubleshooting Options These workarounds apply to various troubleshooting scenarios that you might encounter. 292 BMC Impact Solutions Service Modeling and Publishing Guide . but the subsequent publication fails. Promotion. which provide helpful information when troubleshooting problems. you connect to the Remedy AR System server using the Remedy User Tool. reconciliation.Other BMC Impact Service Model Editor Troubleshooting Options 5 Click OK. not whether the publication is successful or has failed. If the BMC Atrium CMDB is not accessible. If necessary. Deleting all Views Remove all the View files from the following locations: s BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/data/ smsConsoleServer/sme/indexes BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/data/ smsConsoleServer/sme/Views s Connecting to the Remedy AR System server To verify that the BMC Atrium CMDB is accessible. BMC Impact Service Model Editor notifies you only of the success or failure of a promotion. It is possible that the promotion and reconciliation processes are successful. see “Working with publication logs” on page 108.

trace contains tracing information. several parameters may require adjustment: Appendix A Troubleshooting 293 . you can use ps. If the BMC Impact Portal JMS is not functioning properly.trace (or MCELL_HOME/etc/pserver.lock to verify whether a BMC Impact Publishing Server is running. Using trace files To help debug problems with publishing.trace) by commenting out the last two sections.trace file. you use the pserver. only trace information of level WARN or higher is logged. BMC Impact Publishing Server maintains the file MCELL_HOME/log/ps_hostName/ps. Stopping BMC Impact Publishing Server when JMS is not running If the BMC Impact Portal JMS is not up and running properly. 2 Execute the command fuser ps. 3 Kill the BMC Impact Publishing Server process by executing the command: fuser -k ps. 1 At the command prompt. navigate to the MCELL_HOME/log/ps_hostName directory. Note that this procedure is for UNIX platforms only. By default. The file MCELL_HOME/tmp/ps_hostName/pserver.lock. Ensure that you do not kill the BMC Impact Publishing Server process when it is processing a request. find and stop the BMC Impact Publishing Server process.lock The processID of the BMC Impact Publishing Server process is returned. Enable debug tracing in MCELL_HOME/etc/<PSName>/pserver.lock Publishing large service models When publishing large models.Verifying that BMC Impact Publishing Server is running Verifying that BMC Impact Publishing Server is running To ensure that only one BMC Impact Publishing Server is running.

conf file. If publication fails with Publish validation of IMs failed.conf file. The BMC Atrium CMDB continues to commit modifications in the impact dataset and after a while the service model will be available in the impact dataset. BMC Impact Publishing Server estimates the timeout needed. the operation has been accepted by the server and will usually complete successfully. use the following information to troubleshoot the problem according to the message you receive: IM <CellName> failed to upload service model from SMM The DestinationBufferKeepSent of smmgr is not high enough and expires before the cell has terminated uploading service model from smmgr. This parameter specifies the time out value for the communication between BMC Impact Publishing Server and the BMC Atrium CMDB. s In the MCELL_HOME/etc/smmgr.92 Timeout. In the MCELL_HOME/etc/pserver. If publication fails during the database update with the message Failure while applying publish on CMDB . By default. successful publication are necessary to avoid subsequent publication job failure with the message Unique data identifier not/already in use. The same failure may happen when initializing CMDB with large service models. set SMMMessageBufferKeepSentEstimate=F and increase SMMMessageBufferKeepSent. Reinitialization of a cell (pinit) and a new. Make sure the parameters are set correctly.Error . the configuration parameter ARSXLongTimeOut may not be set high enough. If the publication fails with Publish verification of IMs failed. BMC Impact Publishing Server estimates the timeout needed.conf file. IM <CellName> did not answer the request 294 BMC Impact Solutions Service Modeling and Publishing Guide . By default. the value for ARSXLongTimeOut is not set high enough and expires before the BMC Atrium CMDB has terminated committing modifications in the impact dataset. the SMMMessageBufferKeepSent parameter is the timeout for communication between BMC Impact Publishing Server and smmgr. the DestinationBufferKeepSent parameter is the timeout for communication between smmgr and the cell. If the timeout is not adequate.Publishing large service models s In the pserver. set ARSXLongTimeOutEstimate=F and increase ARSXLongTimeOut.

bat file change the default -Xms256M -Xmx800M values to -Xms512M Xmx1600M.additional.Publishing failures and reattempts The SMMMessageBufferKeepSent of publishing server is not high enough and expires before the smmgr has applied the verification or upload.conf file defines the interval between two publish requests). you should double both the Stack Size and the Heap Size. The configuration parameter AutomatedPublishRetryCount gives the maximum number of retries: s s s 0 means no retrial. when a cell is not available).bat manually. To double the Heap Size. For service models with approximately 10.5=-Xmx1600M Making these changes will allow publishing of 10k models successfully if you run pserver.4=-Xss1M wrapper. Additionally. if necessary. To double the Stack Size.java.additional.conf file.2=-Xms512M wrapper.000 relationships. add the following parameters before restarting the Publishing Server: wrapper. In both cases. a new interval is started. the automated publisher retries the publish (the configuration parameter AutomatedPublishRetryPeriod in the pserver.java. in the pserver. until a publish is successful.bat file (Windows) or the pserver file (UNIX) change the default -Xoss400k and Xss512k values to -Xoss800k and -Xss1M.java.3=-Xoss800k wrapper. in the pserver_service. Nevertheless. s When performing a penv init or a pinit of a large service model the Stack Size and the Heap Size of the Publishing Server might need to be increased.java. a number less than zero (-1) means the automated publisher will republish indefinitely. Publishing failures and reattempts When an automated publish request fails because of reasons independent of model consistency (for example.additional. 1 means a publish request and one retry attempt. the cell continues to upload and eventually the service model is available in the cell. thus only a single publish request is performed. reinitialize the cell and publish again to avoid subsequent publish jobs failing with the message Unique data identifier not/already in use.additional. Appendix A Troubleshooting 295 . If a request is still not terminated when the interval runs out. in the pserver.000 CIs and 10.

ERROR-8755 The specified plug-in does not exists. This is controlled in the MCELL_HOME/log/<PSName>/ps. automated publisher is up and running. but data does not appear in the BMC Impact Portal or BMC Impact Explorer. publication might still fail.ARDBC. Promotion and publication are asynchronous processes. No publication after successful promotion Even if promotion is successful. which is updated with a timestamp every minute by the BMC Impact Publishing Server as it runs. Unable to start automated publishing If you receive the following error event after switching to automated mode: Unable to start automated publishing. follow the guidelines in this section to troubleshoot the problem.NOTIFY). If the Promotion Results dialog box in BMC Impact Service Model Editor indicates that the promotion was successful.lock is removed. 296 BMC Impact Solutions Service Modeling and Publishing Guide . Verify automated publishing mode Verify that the BMC Impact Publishing Server is running in automated mode with the CLI command psstat.lock file. Another BMC Impact Publishing Server is already running remove the ps. This error occurs when the Notify ARDBC plugin is not loaded when BMC Impact Publishing Server starts in automated mode. then ps.BMC Impact Publishing Server service or daemon fails to start BMC Impact Publishing Server service or daemon fails to start Only one BMC Impact Publishing Server may be running at any given time. If the BMC Impact Publishing Server service or daemon fails to start and displays the error message Unable to launch BMC Impact Publishing Server. (BMC. If the Impact Publish Server is stopped gracefully.lock file in the MCELL_HOME/log/ps_hostname/ directory and restart the BMC Impact Publishing Server service (or daemon).Automated mode. If the psstat command returns Started . Verify that the plugin is properly installed and loaded.

2 Open the form NOTIFY:protocols and retrieve entries. follow these steps: 1 Log on to Remedy User. Ensure that the NOTIFY plug-in configuration and the BMC Remedy AR System plug-in environment variables are correct so that the NOTIFY plug-in is loaded. To verify that the NotifyARDBC plugin is running. occasionally the communication is not restored and the BMC Impact Publishing Server doesn't stop. You should get one entry with version 1. This might have occurred because the configuration parameter AutomatedStartMode in pserver. To switch to automated mode. You should get one entry. If the BMC Impact Publishing Server is running in manual mode. However. If the port is not accessible for the BMC Impact Publishing Server to open a TCP/IP connection. execute the CLI command pscontrol automated. To resolve this situation. Normally. the BMC Impact Publishing Server restores when the JMS service drops. Appendix A Troubleshooting 297 .trace file contains repeated warnings from org. 3 Open the form NOTIFY:servers and retrieve entries. and the pserver.SpyJMSException. it may be in manual mode.conf is set to Manual. The port should be open for the BMC Impact Publishing Server to open a TCP/IP connection. Reconciliation jobs hang When reconciliation jobs hang and remain in a started status (causing BMC Impact Service Model Editor promotions to hang).mq. BMC Impact Publishing Server does not reply to requests The client and server use the JMS service of BMC Impact Portal for communication. or because the mode was set with the CLI command pscontrol. the NotifyARDBC plug-in is not installed or is not running.jboss. the BMC Impact Publishing Server stops with a critical error. you can request a publication using the CLI command publish. verify the installation of the Notify ARDBC plugin. If the JMS service remains down.Reconciliation jobs hang If the psstat command indicates that the BMC Impact Publishing Server is not running in automated mode.

launch Tools => Export Cell Meta Data to generate an up-to-date mc_sm_baroc. examine the details of the request log in BMC Impact Service Model Editor using the menu command Publish History (Tools => Publish History). a class may be modified in the BMC Atrium CMDB after the service model is published to the cell. 298 BMC Impact Solutions Service Modeling and Publishing Guide . Replace the existing mc_sm_baroc. Table 82 describes BMC Impact Publishing Server request failure messages. Restart the BMC Impact Publishing Server. cell in the MCELL_HOME/etc/cellName/kb/class es directory. and restart the cell. Recompile the cell’s Knowledge Base. Restart the BMC Portal.baroc. and what to do to correct the problem.Diagnosing publication failures 1. the class definitions in the BMC Atrium CMDB can become out of sync with the class definitions of published service model of the cells. Publish the purge by using the CLI command publish -p "Purge=T" See “Purging and deleting service model objects” on page 212 for more information. s s Make sure all CIs have unique aliases. Table 82 BMC Impact Publishing Server request failure messages (part 1 of 5) Cause For various reasons.object file of the target Failure message Classinfo is not synchronized. Execute pclassinfo -x -o mc_sm_object. what causes the problem. Verify that BMC Impact Portal is running properly (or restart the BMC Impact Portal). For example. Action In BMC Impact Service Model Editor. Diagnosing publication failures When a publication attempt or other request fails.object file. Component alias "{0}" for component "{1}" is already used by component "{2}" Two CIs have the same alias. 2.

Verify that the ServiceModelSet of impact relationship is correct. Delete Direct Publish management data using the pposter CLI command and the ddelete action command.conf file. Also verify that the cell’s location and encryption key are registered with BMC Impact Portal. This message may occur if s Failure message Connection to IM cellName is not open OR Connection to IM cellName dropped Action Verify that the target cell instance is running. When you have previously published from a Direct Publish environment and now want to publish from BMC Atrium CMDB. The cell does fork a Service Model Manager (SMM) process. the Direct Publish management data conflicts with management data being published from BMC Atrium CMDB. the parameter ServiceModelManagerStartTimeOut = 60 defines the timeout. Increase the value of ServiceModelManagerStartTimeOut. Consumer/Provider component with mc_udid {0} is not defined an impact relationship is pointing to a non-existent CI the impact relationship has ServiceModelSet IN.Diagnosing publication failures Table 82 BMC Impact Publishing Server request failure messages (part 2 of 5) Cause The BMC Impact Publishing Server is not able to connect to the BMC Impact Manager or the connection was dropped.conf file cell. IM {0} failed to upload service model from SMM This failure message displays after Reinitialize the cell and publish a failure in the second phase of again (to avoid subsequent two-phase commit. but the consumer or provider component instance has ServiceModelSet OUT_OF_IN or OUT s IM {0} failed to launch SMM (Service Model Manager) In a cell's trace file you find the message Service Model Manager process ({0}) not active within expected delay. Using automated publish for two promotions will prevent this failure. Restart it if necessary. publishes failing with the message Unique data identifier not/already in use") IM is not publish enabled. or in MCELL_HOME/etc/<CellName>/ mcell. Please verify.conf file is set to No. In the mcell. Such problems may occur when two promotions follow very quickly and the first promotion adds a relationship and the second promotion moves a CI out of model. init verify failure Appendix A Troubleshooting 299 . Reset the ServiceModelPublish The ServiceModelPublish parameter in the parameter to Yes and restart the MCELL_HOME/etc/mcell.

Diagnosing publication failures Table 82 BMC Impact Publishing Server request failure messages (part 3 of 5) Cause Action In the BMC Atrium CMDB. cell X runs on port X. Use the instance's publish environment to publish modifications or deletions. This failure typically occurs when you remove a group in AR Server for which there still are components that refer to it. so the provider_home_cell is remote (other cell as relationship) s The issue originates from the fact that although the CI is sent to cell Y. a CI's Modify the CIs to point only to existing user groups. in reality. Failure message No user group defined with id {0} Operation on instance of different environment Provider_home_cell ({0}) is remote but component {1} is local The data instance is already published to the cell from another publish environment. port X is mistakenly entered for both cells. typo when registering cells. securities point to BMC Remedy AR System user group ids. thus the cell X impact relationship is sent to the cell with name Y. a provider component with cell name Y is sent to cell on port X. However. This error can occur as a result of a Correctly register the ports of the cells. it is sent to cell X because that cell is listening on the (erroneous) port (X) of cell Y. a CI's securities points to BMC Impact Administration User Roles. BMC Impact Publishing Server maps the BMC Remedy AR System user group ids to user role names. thus s the cell on port X is component local (same cell as relationship) provider_home_cell has value Y. In the BMC IM. While cell X is running. by using the user group info found in the AR form groups and the AR external authentication group mappings. 300 BMC Impact Solutions Service Modeling and Publishing Guide . For example. and cell Y runs on port Y.

Diagnosing publication failures

Table 82

BMC Impact Publishing Server request failure messages (part 4 of 5)
Cause Publication failure Action Use the -v option (publish -v) to return both generic and detailed (verbose) failure messages.

Failure message Publish returns generic failure message, such as Publish
validation of Impact Manager failed The cell alias is not mapped to a cell name in the current environment The component has a class id BMC_TRANSACTION that does not correspond with a SIM class.

The attribute HomeCellAlias has a Define the cell aliases correctly. value that is not defined in the publish environment's CellAliases. A CI of the class with the given id has ServiceModelSet IN or OUT_OF_IN, although the class is not flagged as a SIM class. Only instances of SIM classes should have ServiceModelSet IN or OUT_OF_IN. To make the class a SIM class, follow these steps: 1. Use Remedy User's Class Manager Console and assign the attribute Custom Properties to 100050. 2. Export the modified SIM class information with the CLI command pclassinfo -x. 3. Update the Knowledge Base of the cells and recompile. For more information, see “Adding new classes to the BMC Atrium CMDB” on page 157.

The minimum supported protocol version is 7. Unique data identifier already in use.

The version of the target cell Uninstall the earlier version and instance is earlier than the required install the appropriate version. version. A service component instance with The service model in the cell is the same mc_udid is already most likely not in sync with the published in the cell. master copy kept in the BMC Atrium CMDB impact dataset. Reinitialize the cell. If reinitializing the cell fails because of invalid data, then the master copy is invalid. Reinitialize the BMC Atrium CMDB.

Appendix A

Troubleshooting

301

Another publish request is ongoing

Table 82

BMC Impact Publishing Server request failure messages (part 5 of 5)
Cause This failure may occur when the deletion or modification of a CI with a udid that does not exist is requested. For Atrium CMDB Publish, this typically happens when the service model in a cell is not in sync with service model in (the impact dataset of) the BMC Atrium CMDB, typically when a previous publish failed because of failure while applying publish on cell or BMC Atrium CMDB, or when cell has been restarted with the -id option. Action Reinitialize the SIM data from the publish environment by executing the CLI command pinit -n cellName -e EnvId If this solution fails, the data in the BMC Atrium CMDB may be invalid. Reinitialize the BMC Atrium CMDB.

Failure message
Unique data identifier not in use

Unknown home cell "{0}" for shadow component

The entry in the mcell.dir file of the Correct mcell.dir. consumer's cell is not defining the provider's cell. For instance, you will receive failure messages when the number of CI's exceeds the limited number available with a trial license. These failures may occur in the second phase of the two-phase commit. To troubleshoot these failure messages, consult the BMC Remedy AR System and BMC Atrium CMDB documentation. If the failure occurred in the second phase of the two-phase commit, to avoid subsequent publish failures with the message Unique data identifier not in use or already in use, reinitialize the cell and publish again.

You may receive detailed failure messages from the BMC Atrium CMDB.

Another publish request is ongoing
When the BMC Impact Publishing Server does not accept or begin processing a publish request, the following messages may display:
s s s

Another publish request is ongoing The environment is not registered Error with ids/udids for partial publish, i.e. publish of selected instances

302

BMC Impact Solutions Service Modeling and Publishing Guide

Using dynamic ports with the ARDBC Notify plug-in

Message: Another publish request is ongoing
The BMC Impact Publishing Server executes only one publication at a time, per cell. If you request a new publication (by using the CLI command publish or pposter) while another publication is in progress, the message Another publish request is ongoing displays. If you receive this message unexpectedly, verify that the previous publication is still running. If a publication hangs (because of an uncached exception, which can be found in tmp/ps.err), then all following publications will result in failure messages and you must contact BMC Customer Support.

Using dynamic ports with the ARDBC Notify plug-in
The Notify plug-in uses the static port 1840 by default . However, if the Notify plugin is configured to use a dynamic port, automated publishing might not work. If the Notify plug-in listens on a port that is registered and used by another service, for example, port 1828 used by the cell, automated publication does not function. If this occurs, psstat returns the message: Started - Starting Automated mode To prevent this issue, restart the Remedy AR Server so that Notify plug- in chooses another port to which to listen.

BMC Impact Service Model Integration with HP OVO
This section discusses solutions to common issues that you might encounter when attempting to create a service model from imported HP OVO data.

Avoiding duplicate CIs
Duplicate CIs can occur when the name of a CI is different based on the discovery type or location of the CI relative to a domain name server. Situations that cause this issue can include, for example, servers that have mulitple IP addresses or DNS names, cluster nodes with several IP addresses, or a router discovered by management tools employing different IP addresses to perform their respective CI discoveries.

Appendix A

Troubleshooting

303

Automated publication after reconciling reconciliation failure

To avoid this situation, BMC Software recommends identifying what attributes will avoid duplicate CIs and then modify the identification rule to recognize those attributes.

Automated publication after reconciling reconciliation failure
If a reconciliation job (triggered by the Publishing Server after importing HP OVO data into into the Atrium CMDB) fails, diagnose the cause of the job failure and take corrective action if necessary. You can then trigger the reconciliation job to restart again by selecting this option from the the Reconciliation History Console. If reconciliation succeeds, this triggers an automated publication that will publish the HP OVO service model to the SIM cell or cells.

Limiting HP OVO fetcher trace file growth
When you turn on debug tracing for the HP OVO fetcher, the trace file continuously increases in size when trace is active. As a result, the fetcher trace file can grow large enough to cause disk space issues. To circumvent this issue, turn off trace after debugging is complete.

304

BMC Impact Solutions Service Modeling and Publishing Guide

Appendix

B
306 306 306 307 307 313 317 319 321 322 322 323 323 324 324 325 325 326 326 327 327 327 327 328 328 330 330 331

B

Default service model data classes
This appendix describes the service model class hierarchy in the BMC Atrium CMDB Common Data Model. This appendix covers the following topics: Service model data structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model data class overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model data class files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model component data classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_BaseElement data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_Impact data class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_STATUS_COMPUTATION data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_STATUS_PROPAGATION data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_PROPAGATION_MAP data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIM data class descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_SEVERITY_TO_STATUS data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_SIM_MATCH_TABLE data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_SIM_ALIAS data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_SLOT_FORMULAS data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_TIME_SCHEDULE data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_TIME_FRAME_TO_SCHEDULE data class . . . . . . . . . . . . . . . . . . . . . . . . . BMC_SELF_PRIORITY_MAPPING data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_SERVICE_SCHEDULE_CONFIG data class . . . . . . . . . . . . . . . . . . . . . . . . BMC_STATUS_TO_SEVERITY data class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIM_TIME_FRAME class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIM_CellAlias class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SIM_CellInformation class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC_PROMOTION_LOG class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service model event classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CORE_EVENT base class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Root event class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . History event class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Impact event class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix B

Default service model data classes

305

Service model data structures

Service model data structures
The service model uses various data structures as data classes. In this documentation, the term class designates the structure definition. The term table is the set of data instances defined for a data class. The following discussions are not intended to represent an exhaustive hierarchy of all classes associated with the dynamic data model.

Service model data class overview
There are several types of BAROC data classes that are important in the service model:
s

Component data classes—the service model data classes that define the component types typically used by business organizations. These classes are loaded into the Knowledge Base by default. Relationship data class (BMC_Impact)—the data class that defines the different types of relationships that can exist between service components. The only class that exists for impact relationships is BMC_Impact. Service model management classes—the data classes that define the status computation and propagation, as well as the classes that support the service model event-to-component mapping mechanism. These classes are loaded into the Knowledge Base by default. Event classes—the classes that define the product event types and their behaviors.

s

s

s

Service model data class files
Table 83 on page 307 lists the files in which the various data class definitions are located. Default class definitions are in the MCELL_HOME\BMC Software\server\etc\cellName\kb\classes directory. In addition, each cell has a working Knowledge Base with its class definitions in the MCELL_HOME\etc\cellName\classes directory.

306

BMC Impact Solutions Service Modeling and Publishing Guide

Service model component data classes

Table 83

Service management data class files
File name mc_sm_object.baroc Contents these component types and their subclasses:
s

Data classes Component

BMC_BaseElement s BMC_Collection s BMC_LogicalEntity s BMC_System s BMC_SystemComponent s BMC_SystemService

Root

mc_sm_root.baroc

event and data classes and the enumerations that are the foundation of the solution mapping data classes that provide the event-to-component mapping mechanism

Mapping

mc_sm_event_mapping.baroc

Service model component data classes
A service model component type is the data class that defines a logical or physical IT resource that participates in the delivery of business services. Service model component instances can represent a hardware component, an application, a service, or a business entity. A component instance can be any aspect of the business for which service management is desired. Service model component instances are organized in a hierarchy of data classes in which each class represents a component type. The farther down the hierarchy a particular class occurs, the more specific its type.

BMC_BaseElement data class
The parent class of the data class hierarchy is the BMC_BaseElement class. The classes that immediately extend from BMC_BaseElement are:
s s s s s

BMC_Collection BMC_LogicalEntity BMC_System BMC_SystemComponent BMC_SystemService

Appendix B

Default service model data classes

307

OwnerName : STRING. WriteSecurity : LIST_OF STRING. default = 'n/a'. VersionNumber : STRING. default = '0'. MC_SM_COMPONENT class is located in the mc_sm_root. ReadSecurity : LIST_OF STRING. Notes : STRING.baroc file. Item : STRING. InstanceId : STRING. OwnerContact : STRING. END BMC_BaseElement inherits slots from MC_SM_COMPONENT class. which is located in the mc_sm_object. Category : STRING.BMC_BaseElement data class BMC_BaseElement data class definition Figure 34 shows the BAROC definition of the BMC_BaseElement class. ImpactCostUnit : STRING. ManufacturerName : STRING. Model : STRING.baroc file. which is defined in Figure 35 on page 309. DatasetId : STRING. Figure 34 BMC_BaseElement definitions MC_PUBLISH_DATA_CLASS : BMC_BaseElement ISA MC_SM_COMPONENT DEFINES { Type : STRING. Name : STRING. 308 BMC Impact Solutions Service Modeling and Publishing Guide . AccountID : STRING. }. ShortDescription : STRING. Description : STRING.

read_only=yes. default = NONE. manual_status_comment: STRING. default=NO_SLAS. schedule_status: MC_SM_SCHEDULE_STATUS. parse=no. read_only=yes. parse=no. read_only=yes.baroc file. default = NO. parse = no. END Appendix B Default service model data classes 309 . status: MC_SM_COMPONENT_STATUS. read_only=yes. read_only=yes. StatusModel: STRING. parse=no. read_only=yes. parse=no.BMC_BaseElement data class Figure 35 MC_SM_COMPONENT definition MC_PUBLISH_DATA_CLASS: MC_SM_COMPONENT ISA MC_SM_DATA DEFINES { ComponentAliases: LIST_OF STRING. shadow_cells: LIST_OF STRING. read_only=yes.0 possible_causes: LIST_OF STRING. default=PRIORITY_5. parse=no. maintenance_mode: MC_YESNO. manual_status_providers_count: INTEGER. business_data : STRING. read_only=yes. read_only=yes. sla_roleup_status: MC_SM_SLM_SLA_STATUS. read_only=yes. PriorityWatchdog:MC_YESNO. consumer_num: INTEGER. }. computed_priority: MC_PRIORITY. root_causes: LIST_OF STRING. parse=no. read_only=yes. parse=no. default = NONE. default = LOCAL. read_only=yes. read_only=yes. parse=no. default = NONE. parse=no. default=PRIORITY_5. END MC_SM_COMPONENT inherits slots from MC_SM_DATA (which contains no slot definitions. self_priority: MC_PRIORITY. ImpactCostPerSecOut : REAL. direct_events_count: INTEGER. representation = date. consolidate_function: MC_SM_CO_FUNCTION. sub_status: MC_SM_COMPONENT_STATUS. parse=NO. # additional slot in 7. ImpactCostPerSec : REAL. Priority:MC_PRIORITY. parse =no. self_status: MC_SM_COMPONENT_STATUS. parse=no. read_only=yes. read_only=yes. read_only = YES. parse=no. default = OK. manual_status: MC_SM_COMPONENT_STATUS. impact_status: MC_SM_COMPONENT_STATUS. default = NONE. parse=no. parse=no. parse=no. last_status_modification: INTEGER. read_only=yes. HomeCell: STRING. default=NO. read_only=yes. read_only=yes. parse=no. ScheduleId: STRING. PriorityOut:MC_PRIORITY. manual_status_requestor: STRING. parse=NO. cost:REAL. read_only=YES. manual_status_providers: LIST_OF STRING. comment: STRING. change_number : INTEGER. default = OK. default=IN. read_only=yes. parse=no. default=PRIORITY_5. impact_priority: MC_PRIORITY. parse=no. Figure 36 MC_SM_DATA definition MC_DATA_CLASS : MC_SM_DATA ISA CORE_DATA. parse=no. default=PRIORITY_5. MC_SM_DATA is located in the mc_sm_root. parse=NO. component_scope: MC_SM_COMPONENT_SCOPE. raw_impact_priority: REAL. as shown in Figure 36). parse=no. read_only=yes. default = 'STANDARD'. parse=no. parse=no. computed_status: MC_SM_COMPONENT_STATUS. read_only=yes. read_only=yes.

shadow. Figure 37 CORE_DATA definition MC_DATA_CLASS : CORE_DATA DEFINES { data_handle : INTEGER. etc. read_only = yes. mc_udid : STRING. Table 84 Slots AccountId Slots that define component instances (part 1 of 4) Description identification of the Account the object belongs to (Accounts are created in the Portal) Data type or enumeration STRING Source class BMC_BaseElement Category provides a user-defined categorization of a STRING component instance BMC_BaseElement change_number increments every time an event is sent for the component. CORE_DATA is located in the mc_root_internal. END Component instance slot descriptions in alphabetical order Table 84 alphabetically lists the slots that define component instances with their descriptions and data type. read_only = yes. parse = no. The Source class column indicates the name of the class where the slot is defined. read_only = yes. mc_creation_time : INTEGER. }. Used to determine the order of events for events which happen in the same second. representation = date. read_only = yes.baroc file. mc_modification_requestor : STRING. parse = no.) STRING MC_SM_COMPONENT computed_priority the priority of a component that is the highest between self priority and impacts priority. enumeration: MC_PRIORITY MC_SM_COMPONENT computed_status status of the component instance computed enumeration: from self and substatuses MC_SM_COMPONENT_STATUS MC_SM_COMPONENT 310 BMC Impact Solutions Service Modeling and Publishing Guide . parse = no. mc_modification_time : INTEGER. representation = date. INTEGER MC_SM_COMPONENT ComponentAliases list of aliases used to associate events to the STRING component instance MC_SM_COMPONENT consumer_num number of component instances acting as consumers of the component instance INTEGER MC_SM_COMPONENT comment a comment that is set for the component via STRING BMC Impact Manager MC_SM_COMPONENT component_scope scope of the component (local. Set in the computed_priority field. which is shown in Figure 37. read_only = yes.BMC_BaseElement data class MC_SM_DATA inherits slots from CORE_DATA.

INTEGER STRING CORE_DATA BMC_BaseElement Description a description of the component instance that is meaningful to the enterprise STRING BMC_BaseElement direct_events_count count of events coming from instrumentation INTEGER MC_SM_COMPONENT HomeCell name of the parent cell for the component instance STRING MC_SM_COMPONENT ImpactCostPerSec cost of one second of unavailability of the component STRING BMC_BaseElement ImpactCostPerSec cost for a component when it is During Schedule REAL MC_SM_COMPONENT ImpactCostPerSecOut cost for the component when it is in an Exceptions Within During Schedule period REAL MC_SM_COMPONENT ImpactCostUnit unit of the cost expressed in ImpactCostPerSec STRING BMC_BaseElement impact_priority priority determined from a component’s impacts enumeration: MC_PRIORITY MC_SM_COMPONENT impact_status status computed by impact_function enumeration: MC_SM_COMPONENT_STATUS MC_SM_COMPONENT InstanceId instance identification of a component within the BMC STRING BMC_BaseElement Atrium CMDB BMC_BaseElement Item Provides a user-defined categorization of a STRING component instance last_status_modification last time the status or sub_status was changed (used by GUI) INTEGER MC_SM_COMPONENT maintenance_mode operational switch used to drop events when UM enumeration: MC_YESNO enumeration: MC_SM_COMPONENT_STATUS MC_SM_COMPONENT manual_status manual status flag of the component (NONE if not set) MC_SM_COMPONENT manual_status_comment comment entered by user when component STRING instance is set to manual status MC_SM_COMPONENT Appendix B Default service model data classes 311 .BMC_BaseElement data class Table 84 Slots Slots that define component instances (part 2 of 4) Description function used to determine impact_status from the provider’s propagated status Data type or enumeration enumeration: MC_SM_CO_FUNCTION REAL Source class MC_SM_COMPONENT consolidate_function cost the current cost for the component depending on the current value of the schedule (either During Schedule or Exceptions Within During Schedule) MC_SM_COMPONENT data_handle DatasetId identifier in local cell identification of the dataset within which the instance exists. This attribute relates to the CoreDatasetId attribute of a BMC_Dataset instance.

mc_udids of component instances with manual status set (may contain duplicate entries Data type or enumeration LIST_OF_STRING Source class MC_SM_COMPONENT manual_status_providers manual_status_providers_co number of direct and indirect providers unt with manual status set (may contain duplicate entries) manual_status_requestor login ID of user who sets the component instance to manual status ManufacturerName name of the company that manufactured the component instance mc_creation_time mc_modification_time INTEGER MC_SM_COMPONENT STRING MC_SM_COMPONENT STRING BMC_BaseElement date and time when the object was created INTEGER date and time when the object was last changed INTEGER CORE_DATA CORE_DATA mc_modification_requestor mc_udid Model modification requestor universal data identifier STRING STRING CORE_DATA CORE_DATA BMC_BaseElement model assigned to the component instance STRING by the manufacturing company Name user-defined name that is meaningful to the STRING enterprise BMC_BaseElement Notes OwnerContact general notes on the object INTEGER BMC_BaseElement BMC_BaseElement A string that provides information on how STRING the primary system owner can be reached (e.BMC_BaseElement data class Table 84 Slots Slots that define component instances (part 3 of 4) Description list of direct and indirect providers. phone number. e-mail address OwnerName name of the person in the enterprise who is STRING responsible for the component instance BMC_BaseElement possible_causes list of possible causes for the component’s current status (different from root causes) LIST_OF_STRING MC_SM_COMPONENT Priority priority enumeration: MC_PRIORITY MC_SM_COMPONENT PriorityWatchdog indicates whether the component is a priority propagator enumeration: MC_YESNO MC_SM_COMPONENT raw_impact_priority the computed priority for an object (value between 0 and 1) REAL MC_SM_COMPONENT ReadSecurity list of permission groups that defines who has read access to a component instance LIST_OF_STRING BMC_BaseElement root_causes list of root causes for the component’s current status LIST_OF_STRING MC_SM_COMPONENT ShortDescription short textual description (one-line string) of STRING the object BMC_BaseElement schedule_status indicates whether the component is currently During Schedule or Exception Within During Schedule enumeration_ MC_SM_SCHEDULE_STATUS MC_SM_COMPONENT 312 BMC Impact Solutions Service Modeling and Publishing Guide .g.

baroc file. such as MC_SM_COMPONENT_STATUS. This class inherits slots from the root class CORE_DATA and the superclass MC_SM_RELATIONSHIP.baroc file and their descriptions are provided in Table 7 on page 24. BMC_Impact data class The BMC_Impact class is the parent class of the hierarchy of data classes that define the different types of service model relationships. are listed in the mc_sm_root. Appendix B Default service model data classes 313 . if any MC_SM_SLM_SLA_STATUS LIST_OF_STRING MC_SM_COMPONENT shadow_cells list of cells that contain shadow of the component instance MC_SM_COMPONENT status main status of the component (equals computed_status unless manual status is set) enumeration: MC_SM_COMPONENT_STATUS MC_SM_COMPONENT StatusModel sub_status name of the status computation model derived status of the component instance STRING enumeration: MC_SM_COMPONENT_STATUS MC_SM_COMPONENT MC_SM_COMPONENT Type user-defined categorization of a component STRING instance BMC_BaseElement VersionNumber version number of the component instance. BMC_Impact class definition Figure 38 shows the BAROC definition of the BMC_Impact superclass. which is located in the mc_sm_object.BMC_Impact data class Table 84 Slots self_priority Slots that define component instances (part 4 of 4) Description base priority and the component’s current status Data type or enumeration Source class MC_SM_COMPONENT the priority of the component based on the enumeration: MC_PRIORITY self_status the status of the object based on events directly attached to it (this does not take into account status from providers) enumeration: MC_SM_COMPONENT_STATUS MC_SM_COMPONENT sla_roleup_status the aggregation of the compliance status of enumeration: the associated SLAs. LIST_OF_STRING assigned by the manufacturer BMC_BaseElement WriteSecurity list of permission groups that define who has write access to a component instance LIST_OF_STRING BMC_BaseElement BMC_BaseElement enumerations Enumeration types.

BMC_Impact data class

Figure 38

BMC_Impact definition

MC_PUBLISH_DATA_CLASS : BMC_Impact ISA MC_SM_RELATIONSHIP DEFINES { WriteSecurity : LIST_OF STRING; ShortDescription : STRING, default = 'na'; AccountID : STRING; ReadSecurity : LIST_OF STRING; }; END

BMC_Impact inherits slots from MC_SM_RELATIONSHIP, which is shown in Figure 39. MC_SM_RELATIONSHIP is located in the mc_sm_root.baroc file. Figure 39 MC_SM_RELATIONSHIP definition

MC_PUBLISH_DATA_CLASS: MC_SM_RELATIONSHIP ISA MC_SM_DATA DEFINES { PropagationModel: STRING; provider_home_cell: STRING; provider_classname: STRING; State: MC_SM_RELATIONSHIP_STATE, default = ACTIVE; StatusWeight : INTEGER, default=100; consumer_id: STRING, key = yes; last_status_modification: INTEGER, parse=no, read_only=yes, representation = date; propagated_status: MC_SM_COMPONENT_STATUS, parse=no, read_only=yes, default = UNKNOWN; propagated_sub_status: MC_SM_COMPONENT_STATUS, parse=no, read_only=yes, default = UNKNOWN; provider_id: STRING, key = yes; true_impact: MC_YESNO, parse=no, read_only=yes, default = NO; change_number : INTEGER; }; END

MC_SM_RELATIONSHIP inherits slots from MC_SM_DATA (which contains no slots, as shown in Figure 40). MC_SM_DATA is located in the mc_sm_root.baroc file. Figure 40 MC_SM_DATA definition

MC_DATA_CLASS : MC_SM_DATA ISA CORE_DATA; DEFINES { publish_env_id : STRING, parse = no, read_only = yes;

};
END

MC_SM_DATA inherits slots from CORE_DATA, which is shown in Figure 41. CORE_DATA is located in the mc_root.internal.baroc file.

314

BMC Impact Solutions Service Modeling and Publishing Guide

BMC_Impact data class

Figure 41

CORE_DATA definition

MC_DATA_CLASS : CORE_DATA DEFINES{ data_handle : INTEGER, parse = no, read_only = yes; mc_udid : STRING, read_only = yes; mc_creation_time : INTEGER, parse = no, read_only = yes, representation = date ; mc_modification_time : INTEGER, parse = no, read_only = yes, representation = date; mc_modification_requestor : STRING, read_only = yes; }; END

Relationship slot descriptions in alphabetical order
Table 85 alphabetically lists the slots that define component instance relationships, with their descriptions and data type. The Source class column indicates the name of the class where the slot is defined. Table 85
Slot consumer_id change_number data_handle

BMC_Impact slot definitions in alphabetical order
Description mc_udid of the consumer component instance change number identifier in local cell Data type or enumeration STRING INTEGER INTEGER INTEGER Source class MC_SM_ RELATIONSHIP MC_SM_ RELATIONSHIP CORE_DATA MC_SM_ RELATIONSHIP CORE_DATA CORE_DATA CORE_DATA MC_SM_ RELATIONSHIP MC_SM_ RELATIONSHIP MC_SM_ RELATIONSHIP

last_status_modification date/time when the value of true_impact function was last changed (used by GUI) mc_creation_time mc_modification_time mc_udid propagated_status date and time when the object was created date and time when the object was last changed internal key used to reference the relationship; it is an inherited slot status that is currently propagated through the relationship maximum of provider substatus and status values name of the status propagation model used for determining the propagated status from of the provider’s main status name of the class of the provider component instance

INTEGER INTEGER STRING enumeration: MC_SM_COMPONENT_ STATUS enumeration: MC_SM_COMPONENT_ STATUS STRING

propagated_sub_status

PropagationModel

provider_classname

STRING

MC_SM_ RELATIONSHIP

Appendix B

Default service model data classes

315

BMC_DOWNTIME_STATUS_CONFIG data class

Table 85
Slot

BMC_Impact slot definitions in alphabetical order
Description the cell that receives events for the provider component instance Data type or enumeration STRING Source class MC_SM_ RELATIONSHIP MC_SM_ RELATIONSHIP MC_SM_ RELATIONSHIP MC_SM_ RELATIONSHIP

provider_home_cell provider_id

mc_udid of the provider STRING component instance, the impacting component instance state of the relationship, Active or Inactive enumeration: MC_SM_RELATIONSHIP _STATE

State

StatusWeight

number that determines the degree INTEGER of importance to give to each provider relationship that impacts a consumer component instance flag indicating whether this relationship affects the impact_status of the consumer enumeration: MC_SM_YESNO

true_impact

MC_SM_ RELATIONSHIP

BMC_Impact enumerations
The following enumerations are listed in the mc_sm_root.baroc file:
s s s s s s s s s s s s s

MC_SM_RELATIONSHIP_STATE MC_SM_IMPACT_FUNCTION MC_SM_SELF_FUNCTION MC_SM_CO_FUNCTION MC_SM_SLA_RESET_MODE MC_SM_COMPONENT_SCOPE MC_SM_COMPONENT_STATUS MC_SM_SHADOW_REQUEST_OP MC_SM_SLM_SLA_STATUS MC_SM_CAUSE_TYPE PRIORITY_FORMULA MC_SM_SCHEDULE_STATUS BMC_SIM_DOWNTIME_STATUS_CONFIG

BMC_DOWNTIME_STATUS_CONFIG data class
The BMC_DOWNTIME_STATUS_CONFIG data class is used to define which status enumeration values qualify as downtime for both impact reports and priority computation.

316

BMC Impact Solutions Service Modeling and Publishing Guide

BMC_STATUS_COMPUTATION data class

BMC_DOWNTIME_STATUS_CONFIG data class definition
Figure 42 shows the BAROC definition of the BMC_DOWNTIME_STATUS_ CONFIG data class, which is located in the mc_sm_root.baroc file. Figure 42 BMC_DOWNTIME_STATUS_CONFIG definition

MC_PUBLISH_DATA_CLASS : BMC_DOWNTIME_STATUS_CONFIG ISA BMC_SIM_DATA DEFINES { status : MC_SM_COMPONENT_STATUS, default = UNAVAILABLE; }; END

BMC_DOWNTIME_STATUS_CONFIG inherits slots from BMC_SIM_DATA, which is shown in Figure 45. BMC_SIM_DATA is located in the mc_sm_root.baroc file. Figure 43 BMC_SIM_DATA definition

MC_DATA_CLASS: BMC_SIM_DATA ISA MC_SM_DATA DEFINES { ReadSecurity : LIST_OF_STRING; WriteSecurity : LIST_OF_STRING; }; END

BMC_DOWNTIME_STATUS_CONFIG slots
BMC_DOWNTIME_STATUS_CONFIG has the following slot. Table 86
Slot

BMC_DOWNTIME_STATUS_CONFIG slot
Data type or enumeration enumeration: MC_SM_COMPONENT_STATUS Source class BMC_SIM_DOWNTIME_ST ATUS_CONFIG

Description

status the lowest component status that qualifies as down time

BMC_STATUS_COMPUTATION data class
The BMC_STATUS_COMPUTATION data class is used to define status computation models for the component instances. A status computation model is a model that determines the current status of a service model component when direct impact events occur or the status of a provider component instance changes.

Appendix B

Default service model data classes

317

BMC_STATUS_COMPUTATION data class

BMC_STATUS_COMPUTATION data class definition
Figure 44 shows the BAROC definition of the BMC_STATUS_COMPUTATION data class, which is located in the mc_sm_root.baroc file. Figure 44 BMC_STATUS_COMPUTATION definition

MC_PUBLISH_DATA_CLASS: BMC_STATUS_COMPUTATION ISA BMC_SIM_DATA DEFINES { model_name: STRING, key = yes; impact_function: MC_SM_IMPACT_FUNCTION, default = HIGHEST_VAL; ext_impact_function: LIST_OF STRING; self_function: MC_SM_SELF_FUNCTION, default = HIGHEST_VAL; consolidate_function: MC_SM_CO_FUNCTION, default = HIGHEST_VAL; quorum: INTEGER, default = 51; no_alert_status: MC_SM_COMPONENT_STATUS, default = OK; }; END

BMC_STATUS_COMPUTATION inherits slots from BMC_SIM_DATA, which is shown in Figure 45. BMC_SIM_DATA is located in the mc_sm_root.baroc file Figure 45 BMC_SIM_DATA definition

MC_DATA_CLASS: BMC_SIM_DATA ISA MC_SM_DATA DEFINES { ReadSecurity : LIST_OF_STRING; WriteSecurity : LIST_OF_STRING; }; END

BMC_STATUS_COMPUTATION slots in alphabetical order
Table 87 alphabetically lists the BMC_STATUS_COMPUTATION slots with their descriptions and types.

318

BMC Impact Solutions Service Modeling and Publishing Guide

BMC_STATUS_PROPAGATION data class

Table 87
Slot

BMC_STATUS_COMPUTATION slots in alphabetical order
Description Data type or enumeration Source class
enumeration: MC_SM_CO_FUNCTION BMC_STATUS_COMPUTATION

consolidate_function name of the algorithm used to compute the component computed status; it consolidates the impact_status and the self_status ext_impact_function the name of the external algorithm to be used by the impact_function when the impact_function slot contains the placeholder EXTERNAL This slot is reserved for future extension.

LIST_OF_STRING

BMC_STATUS_COMPUTATION

impact_function

name of the algorithm used to enumeration: compute the impact status from MC_SM_IMPACT_FUNCTI provider components; it ONS merges the propagated status values of the different provider components name of the status computation STRING model (key of the table) default main status when the consolidate function’s status is NONE

BMC_STATUS_COMPUTATION

model_name noalert_status

BMC_STATUS_COMPUTATION

enumeration: BMC_STATUS_COMPUTATION BMC_BaseElement_STATUS BMC_STATUS_COMPUTATION

quorum

quorum percentage applied by INTEGER the impact function when set to use the QUORUM algorithm list of permission groups that defines who has read access to a component instance LIST_OF_STRING

ReadSecurity

BMC_SIM_DATA

self_function

name of the algorithm used to enumeration: compute the self status; it maps MC_SM_SELF_FUNCTION and merges the severity values directly from the events list of permission groups that LIST_OF_STRING defines who has write access to a component instance

BMC_STATUS_COMPUTATION

WriteSecurity

BMC_SIM_DATA

BMC_STATUS_PROPAGATION data class
The BMC_STATUS_PROPAGATION class defines the different pairs of component types whose instances can be related to one another through relationships, along with the propagation map to be used by those relationships.

Appendix B

Default service model data classes

319

BMC_STATUS_PROPAGATION data class

BMC_STATUS_PROPAGATION class definition
Figure 46 shows the BAROC definition of the BMC_STATUS_PROPAGATION data class, which is located in the mc_sm_root.baroc file. Figure 46 BMC_STATUS_PROPAGATION definition

MC_PUBLISH_DATA_CLASS: BMC_STATUS_PROPAGATION ISA BMC_SIM_DATA DEFINES { name: STRING, key = yes; provider_type: STRING, key = yes; consumer_type: STRING, key = yes; description: STRING; }; END

BMC_STATUS_PROPAGATION inherits slots from BMC_SIM_DATA, which is shown in Figure 47. BMC_SIM_DATA is located in the mc_sm_root.baroc file. Figure 47 BMC_SIM_DATA definition

MC_DATA_CLASS: BMC_SIM_DATA ISA MC_SM_DATA DEFINES { ReadSecurity : LIST_OF_STRING; WriteSecurity : LIST_OF_STRING; }; END

BMC_STATUS_PROPAGATION slots in alphabetical order
Table 88 alphabetically lists the class slots with their descriptions. Table 88
Slot

Status propagation slots in alphabetical order
Description Data type STRING STRING Source class BMC_STATUS_PROPGATION BMC_STATUS_PROPGATION BMC_STATUS_PROPGATION

consumer_typ valid component types for the e consumer component instance description name description applicable to the relationships using this model

name of the status propagation STRING model; it must match the name of a propagation map list of permission groups that defines who has read access to a component instance

ReadSecurity

LIST_OF_STRING BMC_SIM_DATA

320

BMC Impact Solutions Service Modeling and Publishing Guide

}.baroc file Figure 49 BMC_SIM_DATA definition MC_DATA_CLASS: BMC_SIM_DATA ISA MC_SM_DATA DEFINES { ReadSecurity : LIST_OF_STRING. relationship_state: MC_SM_RELATIONSHIP_STATE. The BAROC definition of the class follows. and source class. propagated_status: MC_SM_COMPONENT_STATUS. }. Figure 48 BMC_PROPAGATION_MAP definition MC_PUBLISH_DATA_CLASS: BMC_PROPAGATION_MAP ISA BMC_SIM_DATA DEFINES { name: STRING. shown in Figure 49. which is located in the mc_sm_root. enumeration or data type. BMC_PROPAGATION_MAP data class definition Figure 48 shows the BAROC definition of the BMC_PROPAGATION_MAP data class. key = yes. provider_status: MC_SM_COMPONENT_STATUS. Appendix B Default service model data classes 321 . END BMC_PROPAGATION_MAP inherits slots from BMC_SIM_DATA. key = yes. WriteSecurity : LIST_OF_STRING. BMC_SIM_DATA is located in the mc_sm_root. key = yes.baroc file.BMC_PROPAGATION_MAP data class Table 88 Slot Status propagation slots in alphabetical order Description Data type STRING Source class BMC_STATUS_PROPGATION provider_type valid component types for the provider component instance WriteSecurity list of permission groups that defines who has write access to a component instance LIST_OF_STRING BMC_SIM_DATA BMC_PROPAGATION_MAP data class The BMC_PROPAGATION_MAP class is used to define status mapping instances for the relationships. END BMC_PROPAGATION_MAP slots in alphabetical order Table 89 alphabetically lists the BMC_PROPAGATION_MAP slots with their descriptions.

SIM data class descriptions Table 89 Slot name BMC_PROPAGATION_MAP slot definitions Description Data type or enumeration Source class BMC_PROPAGATION_MAP name of the parent STRING status propagation model enumeration: MC_SM_COMPONENT_STATUS propagated_status status to be propagated to the consumer component provider_status status of the provider component list of permission groups that defines who has read access to a component instance applicable relationship state list of permission groups that defines who has write access to a component instance BMC_PROPAGATION_MAP enumeration: MC_SM_COMPONENT_STATUS LIST_OF_STRING BMC_PROPAGATION_MAP ReadSecurity BMC_SIM_DATA relationship_state WriteSecurity enumeration: BMC_PROPAGATION_MAP MC_SM_RELATIONSHIP_STATE LIST_OF_STRING BMC_SIM_DATA SIM data class descriptions The following data classes are used in creating service models: s s s s s BMC_SEVERITY_TO_STATUS BMC_SIM_MATCH_TABLE BMC_SIM_ALIAS BMC_SLOT_FORMULAS COMPONENT_CREATION BMC_SEVERITY_TO_STATUS data class The BMC_SEVERITY_TO_STATUS class is used to map the severity value of an impact event to a status value that will participate in the computation of the self status for the associated component instance. 322 BMC Impact Solutions Service Modeling and Publishing Guide .

which is located in the mc_sm_root. key=yes. }. Figure 51 shows the BAROC definition of the BMC_SIM_MATCH_TABLE class. }. END You should not edit a SEVERITY_TO_STATUS table unless the severity and/or the status enumerations are customized.BMC_SIM_MATCH_TABLE data class BMC_SEVERITY_TO_STATUS data class definition Figure 50 shows the BAROC definition of the BMC_SEVERITY_TO_STATUS class. key=yes. BMC_SIM_MATCH_TABLE is located in the mc_sm_event_mapping. Figure 51 BMC_SIM_MATCH_TABLE definition MC_PUBLISH_DATA_CLASS : BMC_SIM_MATCH_TABLE ISA BMC_SIM_DATA DEFINES { name : STRING . BMC_SIM_MATCH_TABLE data class The BMC_SIM_MATCH_TABLE is used to associate events with component instances. Figure 50 SEVERITY_TO_STATUS definition MC_PUBLISH_DATA_CLASS: BMC_SEVERITY_TO_STATUS ISA BMC_SIM_DATA DEFINES { severity: SEVERITY. BMC_SIM_ALIAS is located in the mc_sm_root. key = yes. key = yes. status: MC_SM_COMPONENT_STATUS. tag : STRING . default=alias. read_only=yes. output_expressions : LIST_OF STRING .baroc file. input_match : LIST_OF STRING .baroc file. ref_instances_classes : LIST_OF STRING . Appendix B Default service model data classes 323 . END BMC_SIM_ALIAS data class The BMC_SIM_ALIAS is used to associate events with component instances. Figure 52 shows the BAROC definition of the BMC_SIM_ALIAS class.baroc file.

END BMC_TIME_SCHEDULE data class The BMC_TIME_SCHEDULE data class defines a service schedule. }. ComponentID: STRING. END BMC_SLOT_FORMULAS data class The SLOT_FORMULAS class is used to map event slots to other slots when processing a new raw event.baroc file. ComponentID: STRING. }. Figure 54 shows the BAROC definition of the BMC_TIME_SCHEDULE class. which is located in the mc_sm_event_mapping. key=yes.BMC_SLOT_FORMULAS data class Figure 52 BMC_SIM_ALIAS definition MC_PUBLISH_DATA_CLASS: BMC_SIM_ALIAS ISA BMC_SIM_DATA DEFINES { ComponentAlias: STRING. 324 BMC Impact Solutions Service Modeling and Publishing Guide . which is located in the mc_sm_root.baroc file. Figure 53 BMC_SLOT_FORMULAS definition MC_PUBLISH_DATA_CLASS: BMC_SIM_ALIAS ISA BMC_SIM_DATA DEFINES { ComponentAlias: STRING. BMC_SLOT_FORMULAS data class definition Figure 53 shows the BAROC definition of the SLOT_FORMULAS class. key=yes.

Figure 56 shows the BAROC definition of the BMC_SELF_PRIORITY_MAPPING class.baroc file. Schedule : STRING. status: MC_SM_SCHEDULE_STATUS. key=yes. key=yes. which is located in the mc_sm_root. }.parse=NO. Description : STRING.BMC_TIME_FRAME_TO_SCHEDULE data class Figure 54 BMC_TIME_SCHEDULE definition MC_PUBLISH_DATA_CLASS : BMC_TIME_SCHEDULE ISA BMC_SIM_DATA DEFINES { Name : STRING. Figure 55 BMC_TIME_FRAME_TO_SCHEDULE definition MC_PUBLISH_DATA_CLASS : BMC_TIME_FRAME_TO_SCHEDULE ISA BMC_SIM_DATA DEFINES { Timeframe : STRING. Appendix B Default service model data classes 325 . Included : MC_YESNO. Figure 55 shows the BAROC definition of the BMC_TIME_FRAME_TO_SCHEDULE class. which is located in the mc_sm_root.baroc file. read_only=YES. As part of the mapping it indicates whether the timeframe contains During Schedule or Exceptions Within During Schedule time. }. END BMC_SELF_PRIORITY_MAPPING data class The BMC_SELF_PRIORITY_MAPPING data class contains the resulting self priorities for each combination of base priority mapped against component status. END BMC_TIME_FRAME_TO_SCHEDULE data class The BMC_TIME_FRAME_TO_SCHEDULE data class maps timeframes to schedules. default=YES.

which is located in the mc_sm_root. default = WEIGHTED.baroc file. END BMC_SERVICE_SCHEDULE_CONFIG data class The BMC_SERVICE_SCHEDULE_CONFIG data class contains the settings for the priority formula. status :MC_SM_COMPONENT_STATUS. }. which is located in the mc_sm_root. Figure 57 shows the BAROC definition of the BMC_SERVICE_SCHEDULE_CONFIG class. DefaultSchedule : STRING. severity: SEVERITY. }. Figure 58 BMC_STATUS_TO_SEVERITY definition MC_PUBLISH_DATA_CLASS: BMC_STATUS_TO_SEVERITY ISA BMC_SIM_DATA DEFINES { status: MC_SM_COMPONENT_STATUS. key=yes. Figure 58 shows the BAROC definition of the BMC_STATUS_TO_SEVERITY class. }. key = yes. self_priority : MC_PRIORITY.BMC_SERVICE_SCHEDULE_CONFIG data class Figure 56 BMC_SELF_PRIORITY_MAPPING definition MC_PUBLISH_DATA_CLASS : BMC_SELF_PRIORITY_MAPPING ISA BMC_SIM_DATA DEFINES { priority : MC_PRIORITY. END 326 BMC Impact Solutions Service Modeling and Publishing Guide . Figure 57 BMC_SERVICE_SCHEDULE_CONFIG definition MC_PUBLISH_DATA_CLASS : BMC_SERVICE_SCHEDULE_CONFIG ISA BMC_SIM_DATA DEFINES { PriorityFormula : PRIORITY_FORMULA. key = yes. the default schedule. key=yes. END BMC_STATUS_TO_SEVERITY data class The BMC_STATUS_TO_SEVERITY class is used to map the status value of an impact event to a severity value that will participate in the computation of the self status for the associated component instance. and the list of classes which are priority propagators by default.baroc file.

SIM_TIME_FRAME class

SIM_TIME_FRAME class
The SIM_TIME_FRAME class defines a time period that can be used as part of a schedule. Figure 59 shows the BAROC definition of the BMC_STATUS_TO_SEVERITY class, which is located in the mc_sm_root.baroc file. Figure 59 SIM_TIME_FRAME definition

SIM_TIME_FRAME; mc_udid='SMS_DEFAULT_TIMEFRAME'; description='sms.defaulttimeframe.description'; name='sms.defaulttimeframe.name'; dtstart='20060101T000000'; duration='P1D'; interruptions=[]; tzid=''; rdate=[]; rrule=['FREQ=DAILY;INTERVAL=1;WKST=SU']; exdate=[]; exrule=[]; END

SIM_CellAlias class
The SIM_CellAlias class is assigned to cells and used for publishing. The class maps a cell alias to a real cell name. Cell aliases can be remapped to different cells for different test environments. The definition of the SIM_CellAlias class is located in the cellalias.def file.

SIM_CellInformation class
The SIM_CellInformation class stores cell connection information (similar to mcell.dir). Additionally, it contains a field which specifies whether the cell is a production cell or a test cell.

BMC_PROMOTION_LOG class
BMC_PROMOTION_LOG is a log object created for each user promotion. The object tracks data such as promoted objects, users who initiated the promotion, promotion start and end times, and the status of the promotion (in progress, success, or failed).
Appendix B Default service model data classes 327

Service model event classes

Service model event classes
The service model implements event structures. These event structures are in the form of BAROC event classes. The file containing the root class definitions, mc_sm_root.baroc, is in the MCELL_HOME\server\etc\cellName\kb\ directory.

CORE_EVENT base class
CORE_EVENT is the base class for all BMC Impact Manager event classes. This base class is defined in mc_root_internal.baroc file, and extended in the mc_root_redef.baroc file. It is not specific to the service model, but it includes slots specifically for service impact management functionality.

CORE_EVENT partial data class definition (SIM only)
Figure 60 on page 329 shows the SIM-related definition of the class. For a complete description of all event class slots, see BMC Impact Solutions Knowledge Base Development Reference Guide.

328

BMC Impact Solutions Service Modeling and Publishing Guide

CORE_EVENT base class

Figure 60

Partial CORE_EVENT definition

MC_EV_CLASS : CORE_EVENT DEFINES { event_handle : INTEGER, parse = no, read_only = yes; mc_ueid : STRING, read_only = yes; mc_client_address : STRING, parse = no; adapter_host : STRING; mc_location : STRING; mc_service : STRING; mc_host_class : STRING; mc_host : STRING; mc_host_address : STRING; mc_object_class : STRING; mc_object : STRING; mc_tool_class : STRING; mc_tool : STRING; mc_tool_rule : STRING; mc_tool_key : STRING; mc_tool_sev : STRING; mc_origin_class : STRING; mc_origin : STRING; mc_origin_key : STRING; mc_origin_sev : STRING; mc_parameter : STRING; mc_parameter_value : STRING; mc_event_category : MC_EVENT_CATEGORY; mc_incident_time : INTEGER, representation = date; mc_arrival_time : INTEGER, representation = date; mc_local_reception_time : INTEGER, representation = date; date_reception : INTEGER, representation = date; date : STRING; status : STATUS, default = OPEN; severity : SEVERITY, default = WARNING; mc_original_severity : SEVERITY, parse = no; mc_priority : MC_PRIORITY, default = PRIORITY_5; mc_original_priority : MC_PRIORITY, parse = no; mc_owner : STRING; msg : STRING; duration : INTEGER, parse = no; mc_timeout : INTEGER; repeat_count : INTEGER; mc_action_count : INTEGER, parse = no; administrator : STRING; mc_acl : LIST_OF STRING, parse = no; mc_date_modification : INTEGER, representation = date; mc_notes : LIST_OF STRING, hidden = yes; mc_operations : LIST_OF STRING, hidden = yes; mc_notification_history : LIST_OF STRING, hidden = yes; mc_bad_slot_names : LIST_OF STRING; mc_bad_slot_values : LIST_OF STRING; mc_history : LIST_OF STRING, hidden = yes; mc_modhist : LIST_OF STRING, hidden = yes; mc_propagations : LIST_OF STRING, parse = no, hidden = yes; mc_collectors : LIST_OF STRING, parse = no, hidden = yes; mc_abstraction : LIST_OF INTEGER, parse = no, hidden = yes; mc_abstracted : LIST_OF INTEGER, parse = no, hidden = yes; mc_associations : LIST_OF STRING, parse = no, hidden = yes; mc_cause : INTEGER, parse = no, hidden = yes; mc_effects : LIST_OF INTEGER, parse = no, hidden = yes; mc_event_relations : LIST_OF STRING, parse = no, hidden = yes; mc_relation_source : STRING; mc_smc_id : STRING; mc_smc_alias : STRING; mc_smc_impact : INTEGER, default = 0; mc_smc_type : STRING; mc_smc_causes : LIST_OF STRING, parse = no; mc_smc_effects : LIST_OF STRING, parse = no; }; END

Appendix B

Default service model data classes

329

Root event class

CORE_EVENT slots
The CORE_EVENT slots are listed in BMC Impact Solutions Knowledge Base Development Reference Guide.

Root event class
The MC_SMC_ROOT event class is used to isolate the service management events from the other branches of the event hierarchy and, more specifically, to distinguish among the events associated with a component, those which come from the outside, and those which have been generated internally. Figure 61 shows the BAROC definition of the MC_SMC_ROOT class, which is located in the mc_sm_root.baroc file. Figure 61 MC_SMC_ROOT definition

MC_EV_CLASS : MC_SMC_ROOT ISA EVENT; END

The service model root event class branches into two subclasses: a history event class and an impact event class.

History event class
The history event class, SMC_STATE_CHANGE, is an internal event class used to trace the status changes of components. Figure 62 shows the BAROC definition of the SMC_STATE_CHANGE class, which is located in the state.change.baroc file. Figure 62 SMC_STATE_CHANGE definition

MC_EV_CLASS: SMC_STATE_CHANGE ISA EVENT DEFINES { mc_smc_id: STRING, dup_detect=yes ; smc_status: SIM_NOTIFICATION_STATUS; smc_previous_status: SIM_NOTIFICATION_STATUS; msg: default='A Service Management Component status has changed'; mc_smc_impact: default=2; }; END

330

BMC Impact Solutions Service Modeling and Publishing Guide

Impact event class

Events of class SMC_STATE_CHANGE are automatically generated and associated with their component by the cell. As history events, they are not used in the status computation process.

Impact event class
The MC_SMC_EVENT internal event class should be used as the abstract class when abstracting raw events into service model events. The BAROC definition of the class follows. Figure 63 shows the BAROC definition of the MC_SMC_EVENT class, which is located in the mc_sm_root.baroc file. Figure 63 MC_SMC_EVENT definition

MC_EV_CLASS: MC_SMC_EVENT ISA MC_SMC_ROOT DEFINES { mc_smc_impact : default = 1; component_sub_type: STRING; component_name: STRING; }; END

Events of class MC_SMC_EVENT, or any custom subclass of that class, are not used in the status computation process.

Appendix B

Default service model data classes

331

Impact event class

332

BMC Impact Solutions Service Modeling and Publishing Guide

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index
A
access rights to service model objects 100 Access Server component type 27 active relationship defined 78 setting as 82 Activity component type 26 Activity Decision component type 26 Activity End component type 26 Activity Interaction component type 26 Activity Manual component type 26 Activity options 82 Activity Start component type 26 Add to Saved Finds button 72 Advanced Find tab 74 algorithm, quorum 129 alias entering in component instance 64 alias formulas conditional operators 88 creating 86 functions in 89 analyzing relevance of events 11 Application component type 27 Application Infrastructure component type 27 Application Service component type 31 Application System component type 27 applications, using with extended data models 157 AR System server using with extended data models 157 ARDBC plug-in 214 Atrium Publish environments parameters for 255 attributes generating fields for AR System 157 automated publishing 53, 296 AutomatedPublish configuration parameter 230 AutomatedPublishRetryPeriod configuration parameter 229, 230 described 46 exporting SIM class definitions from 250 BMC Impact Portal monitoring service events 111 BMC Impact Publishing Server generating events for 181 BMC Impact Publishing Server CLI command summary 247–248 common options for commands 241–243 configuring 234–?? configuring error tracing 241 error exit codes 245 error tracing, configuring 241 pclassinfo command 249–?? pcli.trace file 241, 244 pinit command 261–?? plog command 265–??, 281–?? plogdisplay command 266–?? pscontrol stop command 278 pserver command 280 publish command 283–?? BMC Impact Publishing Server service stopping with pcontrol stop CLI command 278 BMC Impact Solutions using new classes 158 BMC Software, contacting ii BMC.ASSET data set 103 BMC.IMPACT.PROD data set 54, 103 BMC_Activity component class 26 BMC_Application component class 27 BMC_ApplicationInfrastructure component class 27 BMC_ApplicationService component class 31 BMC_ApplicationSystem component class 27 BMC_BaseElement BAROC definition 307 enumerations 313 slot definitions 310, 315 BMC_BusinessProcess component class 26 BMC_BusinessService component class 26 BMC_CDROMDrive component class 31 BMC_Cluster component class 27 BMC_ComputerSystem component class 27, 28, 29, 30, 31 BMC_ConnectivityCollection component class 27 BMC_DataBase component class 26 BMC_DataBaseStorage component class 32 BMC_DiskDrive component class 31

B
blackout status described 24 BMC Atrium Configuration Management Database

Index

333

action commands 254 pinit 261 plog 265. 281 plogdisplay 266 pposter 268 pscontrol stop 278 pserver 280 publish 283 common 245 Common Data Model (CDM) SIM-qualified classes of 46 Communication Server component type 28 comparing published to new 106 component classes BMC_Activity 26 BMC_Application 27 BMC_ApplicationInfrastructure 27 BMC_ApplicationService 31 BMC_ApplicationSystem 27 BMC_BMCComputerSystem 27. 30. action command for penv 254 Cluster component type 27 color setting active border 152 setting selected background 152 command options pclassinfo 249 pinit 253. 31 BMC_BusinessProcess 26 BMC_BusinessService 26 BMC_CDROMDrive 31 BMC_Cluster 27 BMC_ComputerSystem 27. 28. 29. 281 plogdisplay 267 pscontrol stop 278 pserver 280 publish 282.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z BMC_DiskPartition component class 32 BMC_FileSystem component class 32 BMC_FloppyDrive component class 31 BMC_HardwareSystemComponent component class 31 BMC_Impact data class 313 enumerations 316 BMC_IPConnectivitySubnet component class 27 BMC_IPXConnectivityNetwork component class 27 BMC_LAN component class 27 BMC_LNsCollection component class 27 BMC_LNsCollection component type 27 BMC_LocalFileSystem component class 32 BMC_LogicalSystemComponent component class 32 BMC_Mainframe component class 29 BMC_Media component class 31 BMC_Monitor component class 29 BMC_OperatingSystem component class 32 BMC_Organization component class 27 BMC_PROPOGATION_MAP defined 321 slots 321 BMC_RemoteFileSystem component class 32 BMC_SIM_ALIAS data class 323 BMC_Software component class 32 BMC_SoftwareServer component class 28. 30. 31 BMC_ConnectivityCollection 27 BMC_DataBase 26 BMC_DataBaseStorage 32 BMC_DiskDrive 31 BMC_DiskPartition 32 BMC_FileSystem 32 C CD ROM Drive component type 31 cell add or change name 68 assigning related component instances to 83 determining topology 14 field 63 initializing with pinit command 263–264 initializing with service model data 261 list of cell names 63 reinitializing 209 SIM. 28. 262. 29. comparing SIM class definitions 252 unassigned 63 cell alias about 193 334 BMC Impact Solutions Service Modeling and Publishing Guide . 30. 29. 269 plog 265. 31 BMC_STATUS_COMPUTATION data class 317 BMC_STATUS_PROPOGATION data class 319 BMC_SystemResource component class 32 BMC_SystemSoftware component class 32 BMC_TapeDrive component class 31 BMC_UPS component class 31 BMC_UserCommunity component class 27 BMC_VirtualSystem component class 31 BMC_VirtualSystemEnabler component class 32 BMC_VMWare component class 32 BMC_WAN component class 27 Business Process component type 26 Business Service component type 26 chart illustrating 196 Class Manager Console 158 classes IPS_CONFIG 186 IPS_ERROR 191 IPS_EVENT 184 CLI for BMC Impact Publishing Server 233–236 close. 284 commands mposter 37 msend 37 pclassinfo 249 penv 252 penv.

31 BMC_Sofware 32 BMC_SystemResource 32 BMC_SystemSoftware 32 BMC_TapeDrive 31 BMC_UPS 31 BMC_UserCommunity 27 BMC_VirtualSystem 31 BMC_VirtualSystemEnabler 32 BMC_VMWare 32 BMC_WAN 27 component instances access to 100 assigning related to cells 83 associating with events 86 copying 69 creating 61 creating multiple copies 62 deleting 70 determining dependencies 10 editing 66 exporting 123 finding existing 71 hide 69 relationship state 35 setting icon colors and labels 152 viewing properties 65 component status computation model 25 computing 126 description of 24 component types 23 Access Server 27 Activity 26 Activity Decision 26 Activity End 26 Activity Interaction 26 Activity Manual 26 Activity Start 26 Application 27 Application Infrastructure 27 Application Service 31 Application System 27 BMC_LNsCollection 27 Business Process 26 Business Service 26 CD ROM Drive 31 Cluster 27 Communication Server 28 Computer System 28 Configuration Management Agent 28 Connectivity Collection 27 Database 26 Database Server 28 Database Storage 32 Disk Drive 31 Disk Partition 32 DNS Server 28 File Server 28 File System 32 Firewall 28 Floppy Drive 31 FTP Server 28 Gateway 28 Hardware System Component 31 Hub 28 Input/Output Device 28 IP Connectivity Network 27 IP Connectivity Subnet 27 JBOD 28 LAN Network 27 Layer 3 Switch 28 LDAP Server 29 Load Balancer 29 Local File System 32 Logical System Component 32 Mail Server 29 Mainframe 29 Media 31 Message Server 29 Mobile User Device 29 Monitor 29 Operating System 32 Organization 27 Print Server 29 RAID Storage Device 29 Remote File System 32 Resource Server 29 Router 29 SAN Bridge 29 SAN Director 30 SAN Hub 30 SAN Router 30 SAN Switch 30 Security Server 30 Server 30 Software 32 Software Server 30 Storage 30 Switch 30 Index 335 .A B C D E F G H I J K L M N O P Q R S T U V W X Y Z BMC_FloppyDrive 31 BMC_HardwareSystemComponent 31 BMC_IPConnectivitySubnet 27 BMC_IPXConnectivityNetwork 27 BMC_LAN 27 BMC_LNsCollection 27 BMC_LocalFileSystem 32 BMC_LogicalSystemComponent 32 BMC_Mainframe 29 BMC_Media 31 BMC_Monitor 29 BMC_OperatingSystem 32 BMC_Organization 27 BMC_RemoteFileSystem 32 BMC_SoftwareServer 28. 29. 30.

BMC Impact Publishing Server CLI 241 Connectivity Collection component type 27 Console Navigation Tree add a component to 113 adding a folder 111 copying a folder 112 dockable window 111 moving a folder 112 permissions for folders 112 refreshing 114 removing a folder 113 renaming a folder 111 copy component instances 69 set options for 154 creating alias formulas 86 component instances 60 multiple copies of component instances 62 relationships 79 custom icons. associating with service model component classes 159 customer support iii D data classes BMC_BaseElement. 230 configuring BMC Impact Publishing Server CLI 234–?? error tracing.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z System Resource 32 System Software 32 Tape Drive 31 Tape Library 30 Telnet Server 30 Transaction Server 30 UDDI Server 30 Uninterruptible Power Supply (UPS) 31 User Community 27 Virtual System 31 Virtual System Enabler 32 VMware 32 WAN Network 27 Web Cache 31 Web Server 31 Computer System component type 28 computing status. 230 InitEffectivelyMgmtData 229.ASSET 104 BMC.IMPACT. setting 153 decreasing relationship policy 82 deleting component instance 70 event alias associations 90 relationships 85 Views 116 Direct Feed for service model data 21 Direct Publish environments parameters for 258 direct relationship policy 82 discovery tools 60 Disk Drive component type 31 Disk Partition component type 32 DNS Server component type 28 dockable windows Console Navigation Tree 111 Find 72 Pan and Zoom 119 repositioning 122 Template 62 undocking 122 documenting extensions 163 drawing relationships 79 dynamic prioritization final priority 147 impacts priority 146 overview 43 priority propagators 146 self priority 137 336 BMC Impact Solutions Service Modeling and Publishing Guide . overview of 306 SEVERITY_TO_STATUS 322 status related 306 Database component type 26 Database Server component type 28 Database Storage component type 32 datasets BMC.PROD 104 defined 46 for Atrium Publish environments 197 date and time formats. of a component 126 Conditional Find tab 75 conditional operators in alias formulas 88 configuration activities for administrators associating custom icons with service model component classes 159 Configuration Management Agent component type 28 configuration parameters AutomatedPublish (publishing server) 230 AutomatedPublishRetryPeriod 229. BAROC definition 307 BMC_Impact 313 BMC_PROPOGATION_MAP 321 BMC_SIM_ALIAS 323 BMC_STATUS_COMPUTATION 129. 317 BMC_STATUS_PROPOGATION 319 extending 23 file location 306 mapping 322 relationship 306 service model relationships 313 service model.

Advanced 74 Find.trace 241. described 24 import service model data 123 important component 146 in model. 230 initializing cells with pinit command 263–264 Input/Output Device component type 28 IP Connectivity Subnet component type 27 IPS_CONFIG class 186 F file location of data classes 306 File Server component type 28 File System component type 32 files pcli.trace (configure) 241 Find command configuring results pane 73 filtering the results 73 Index 337 . 325. Conditional 75 finding component instances 71 relationships 72 Firewall component type 28 Floppy Drive component type 31 FTP Server component type 28 functions in alias formulas 89 in status computation 126 G Gateway component type 28 General tab 62 generating publishing events 181 Go to Component button 74 grab hand in View 119 H Hardware System Component component type 31 hiding component instance 69 dockable windows or View window 61 history event class 330 home cell about 193 home cell alias about 193 Hub component type 28 I icons custom. 325. 244 pclient.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z E editing component instances 66 event alias associations 90 in model/not in model setting 67 multiple component instances 68 multiple objects 67 relationships 84 embedded Help options 154 error exit codes for BMC Impact Publishing Server CLI 245 error messages modifying 110. 331 events associating to component instances 86 generating publishing 181 missing. 281 plogdisplay 267 publish 284 expansion handles in relationships 120 exploring paths in relationships 120 exporting component instances 123 SIM class definitions from BMC Atrium CMDB 250 extending Common Data Model BMC applications and 157 BMC Impact Solutions and 158 documenting 163 relationships 81 Find. 326. 326. defined 78 increasing relationship policy 82 info. described 12 monitoring 110 examples pclassinfo 250–252 penv 258 pinit 263–264 plog 265.trace 241 pserver. action command for penv 255 InitEffectivelyMgmtData configuration parameter 229. 331 IMPACTED component status. action command for penv 255 init.conf 234 pserver. 178 event alias associations creating 86 deleting 90 editing 90 testing 102 event classes 328 history 330 impact 324. defined 54 inactive relationship. associating with user-defined classes in SME 159 identifying critical events 11 impact event class 324.

trace 241 pcli. publishing viewing with plog command 265 logging on BMC Impact Service Model Editor 59 Logical System Component component type 32 P Pan and Zoom dockable window 119 parameters for Arium Publish environments 255 for Direct Publish environments 258 Paste Multiple Components dialog box 69 pclassinfo command 249–?? examples 250–252 options 249–250 pcli.trace file 241. 244 pclient.baroc 307 mc_sm_object. showing 122 not in model defined 54 setting in component instance 63 338 BMC Impact Solutions Service Modeling and Publishing Guide . 325. for relationships 153 lines styles. Views 116 Operating System component type 32 Options command 152 Organization component type 27 Output Preview option 69 J JBOD (Just a Bunch Of Disks) component type 28 L LAN Network component type 27 Layer 3 Switch component type 28 LDAP Server component type 29 line weight. 281 syntax 265.baroc 314 mc_root_redef.conf file configuring Impact Publishing Server CLI 234 location 234 penv command 252 pinit command 261–?? examples 263–264 options. for relationships 153 Load Balancer component type 29 Local File System component type 32 log files setting preferences for 155 log. 326. described 33 M Mail Server component type 29 Mainframe component type 29 Match Attributes box for event alias association 87 mc_root_internal. described 24 missing events 12 Mobile User Device component type 29 Monitor component type 29 mposter command 37 msend command 37 N non-impact relationships.baroc 307 mc_sm_root. 281 plogdisplay command 266–?? examples 267 options 267 return codes 268 syntax 266 pposter CLI command 268 Print Server component type 29 priority propagators 146 product support iii promotion all instances 105 deleting instances 71 guidelines 104 overview 52 requirements before 104 status message 106 step-by-step instructions 105 submitting 104 verifying status 107 promotion of service model 103 provider relationship. described 24 Open Saved Finds button 72 open. 281–?? examples 265. action command for penv 255 opening. BAROC definition 308 mc_sm_event_ mapping.baroc 307 MC_SMC_EVENT data class BAROC definition 324. required 262 syntax 262 plog command 265–??. 331 Media component type 31 Message Server component type 29 MINOR IMPACT component status.baroc 328 MC_SM_COMPONENT data class.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z IPS_ERROR class 191 IPS_EVENT class 184 IPX Connectivity Network component type 27 O OK component status.

177 publishing automated 53. access to 100 promotion 103 publishing large 293 service model components computing status of 126 status colors. action command for penv 255 setting options 152 regional preferences 153 SEVERITY_TO_STATUS data class 322 showing topology views 122 SMC_STATE_CHANGE data class BAROC definition 330 Software component type 32 Software Server component type 30 source file Q query builder in Find 76 quick expansion arrows 61 R RAID Storage Device component type 29 refresh View 121 regional preferences. calculation of relationship values 204 set.conf file configuration parameters 205 pserver. default 24 status computation 25 status values 24 service model relationships data classes 313 defined 34 ServiceModelSet class attribute.trace file 241 publish command 283–?? command options 282. overview of 306 Direct Feed 21 internals of 305 objects. 284 examples 282. 296 changing recommended actions 110. 177 publishing large service models 293 publishing log viewing with plog command 265 renaming Views 116 repositioning objects in a View 118 Reset button in Find 74 Resource Server component type 29 return codes plogdisplay 268 Router component type 29 S SAN Bridge component type 29 SAN Director component type 30 SAN Hub component type 30 SAN Router component type 30 SAN Switch component type 30 save a search statement 72 component instances 64 Views 115 Security Server component type 30 selecting multiple objects 67 relationships 80 Server component type 30 service components types 26 service model class hierarchy 305 composition 17 data classes. 178 viewing history 108. 284 syntax 283 Publish History command 108. options defined 82 relationships active 78 creating 79 define line styles for 153 deleting 85 drawing 79 example View 83 expansion handles 120 exploring paths 120 finding 72 inactive 78 legend of types of 122 selecting 80 showing non-impact 122 state 35 state values 35 status propagation models 36 testing 102 updating 84 Remote File System component type 32 Index 339 .A B C D E F G H I J K L M N O P Q R S T U V W X Y Z pscontrol stop command 278 options 278 syntax 278 pserver command 280 options 280 syntax 280 pserver. setting 153 reinitializing a cell 209 relationship legend 122 relationship policy.

customer iii Switch component type 30 syntax pclassinfo 249.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z for pposter CLI command 270 state_change.baroc file 330 status list of default values for components 24 Status and Alias tab 63 status computation functions 129 model 25 model anatomy 129 of components 25 status propagation models for relationships 36 in BMC Impact Service Model Editor 133 STATUS_COMPUTATION data class. 318 stopping BMC Impact Publishing Server service 278 Storage component type 30 support. 318 slots 317. 253 pinit 262 plog 265. BAROC definition 317. 281 plogdisplay 266 pscontrol stop 278 pserver 280 publish 283 System Resource component type 32 System Software component type 32 User Community component type 27 user groups default rights 100 V verifying promotion status 107 Views adjusting focus in 118 and user accounts 115 deleting 116 grab and move objects in 119 opening 116 refreshing 121 rename 116 reposition objects in 118 saving 115 setting appearance options 154 visual cues in 117 zoom 118 Virtual System component type 31 Virtual System Enabler component type 32 visual cues in a View 117 VMware component type 32 W WAN Network component type 27 WARNING status. described 24 Web Cache component type 31 Web Server component type 31 weighted cluster status model 25 wildcards using with Find command 72 T Tape Drive component type 31 Tape Library component type 30 technical support iii Telnet Server component type 30 topology views configuring 156 showing 122 trace configuration file BMC Impact Publishing Server CLI 241 Transaction Server component type 30 Z zoom in View 118 U UDDI Server component type 30 UNAVAILABLE component status. described 24 undocking dockable windows 122 Uninterruptible Power Supply (UPS) component type 31 UNKNOWN status described 24 user accounts views 115 340 BMC Impact Solutions Service Modeling and Publishing Guide .

Notes .

*52779* *52779* *52779* *52779* *97725* .

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.