BMC Impact Solutions Infrastructure Management Guide

Transcription

1 BMC Impact Solutions Infrastructure Management Guide Supporting BMC Impact Manager version 7.3 BMC Impact Administration Server 7.3 BMC Impact Explorer version 7.3 BMC Impact Portal version 7.3 February

2 Contacting BMC Software You can access the BMC Software website at 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 USA Outside United States and Canada Telephone or Telephone (01) Fax (01) Fax Copyright 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. AIX is a registered trademark of International Business Machines Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC. Linux is the registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation. Sun, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and several other countries. UNIX is the registered trademark of The Open Group in the US and other countries. 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 , DFARS , DFARS , DFARS , and DFARS , as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX , USA. Any contract notices should be sent to this address.

3 Customer support You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or . 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 From this website, you can 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 alerts when new product notices are released find worldwide BMC support center locations and contact information, including addresses, fax numbers, and telephone numbers Support by telephone or In the United States and Canada, if you need technical support and do not have access to the web, call or send an 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: product information product name product version (release number) license number and password (trial or permanent) 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 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 3

4 4 BMC Impact Solutions Infrastructure Management Guide

5 Contents Chapter 1 Managing BMC Impact Manager cells 23 General configuration overview Production cells and test cells Cell configuration tasks Configuring mcell.conf parameters Creating cell-specific configuration files Configuring event slot propagation About mcell.dir, the cell directory file Configuring passive connections Configuring slots for time stamping Configuring encryption Reloading cell configuration Managing high availability cell servers Automatic failover process Automatic switchback process Manually failing over to the secondary server Manually switching back to the secondary server Explicitly connecting a CLI to a selected high availability cell server Monitoring event performance Monitoring client to cell interactions Configuring cell tracing Configuring mcell.trace Configuring a destination for cell trace output Sending trace output to another cell Event processing errors Automatic notification of trace configuration changes Interpreting cell execution failure codes Using the BMC IX Administration view to manage cells Connecting or disconnecting a cell Viewing cell information Registering for SIM notification events Trouble-shooting BMC Impact Manager Problem: The cell will not start Problem: The primary and secondary servers for my high availability cell are in active mode simultaneously or are unsynchronized Chapter 2 Managing a Knowledge Base 65 Knowledge Base structure Contents 5

6 About the unified Event Management and Service Impact Management Knowledge Base Knowledge Base directory structure Knowledge Base index files Managing a Knowledge Base Integrating a unified KB with pre-7.2 cell definitions Creating a new production or test Knowledge Base mcrtcell Importing Knowledge Base information into a cell mkb Compiling a Knowledge Base mccomp Loading a Knowledge Base into a running cell mcontrol Implementing changes to a Knowledge Base Versioning a Knowledge Base Retrieving KB version information in rules Retrieving KB version information by using a command mgetinfo Chapter 3 Managing the BMC Impact Administration server 77 Configuration files Command line interface Impact Administration cell How to configure BMC Impact Administration server files Guidelines for manual edits Users, groups, roles, and permissions Defining permissions Full Access role permissions Adding customized role/permission mappings Defining group roles File-based authentication: updating user information Adding role names to the cell s KB definition files Receiving synchronized data from the BMC Portal Synchronizing cell information with BMC Atrium CMDB Updating cell information Editing logging properties for IAS Defining client logging for the iadmin script Customizing colors for severities, statuses, and priorities IAS Status Monitoring Customizing the IAS thread pool handling IAS Clients Defining standalone, primary, and secondary BMC Impact Administration servers Defining a failover configuration for the Impact Administration cell Transaction and trace logs Example trace output Advanced tasks Configuring BMC Impact Administration server to support remote actions Configuring Lightweight Directory Access Protocol for BMC Impact Administration server Troubleshooting Problem: Cell_info.list synchronization error during manual configuration of an IAS failover BMC Impact Solutions Infrastructure Administration Guide

7 Chapter 4 Managing the BMC Impact Portal 121 Accessing the BMC Impact Portal Starting and stopping the BMC Portal Starting and stopping the BMC Portal on Windows Starting and stopping the BMC Portal on UNIX Configuration tasks for BMC Impact Portal Registering production and test cells in the BMC Impact Portal Customizing BMC Impact Portal configuration Configuring Dashboard Table View columns Configuring Events Table columns Configuring Status Table columns Configuring object link synchronization Configuring reports Configuring the number of events displayed Changing the maximum number of recent items displayed Configuring the general properties displayed Setting up Image Views Modifying connection settings Configuration file and parameter definitions for BMC Impact Portal smsiwc/application.properties file and parameters smsconsoleserver/application.properties file and parameters internal.properties file and parameters Chapter 5 Working with Infrastructure Management 139 Default Infrastructure Management service model Roles and permissions Walkthrough Displaying the out-of-the-box real-time service model Sampling context-sensitive information Managing files on remote systems Packaging support files Launching remote actions Common Infrastructure Management tasks Navigating the interface Displaying and understanding the Details and Administer tab data Editing infrastructure relationships Creating logical components Deleting components Usage reporting Executing remote actions Reloading cell configuration Forcing event propagation Collecting metrics Executing other actions Configuring the audit log Creating the support package Background to Infrastructure Management How a product component registers and communicates with the IAC Contents 7

8 Registering a cell with the Admin cell Recreating an Admin cell Unregistering with the IAC Remote actions Chapter 6 Managing the BMC Impact Explorer (BMC IX) console 177 Defining property files Selecting a single BMC IX instance for cross- and web-launching Defining console-wide policy files Configuring display and connection settings Defining global event severity and priority color values Event group configuration files XML files that define user interface elements Chapter 7 Defining presentation names 187 Presentation names overview Presentation name resource file locations Default presentation name definitions Creating a new presentation name resource file Presentation name resource files search order Defining presentation names Creating or modifying presentation name keys Digitally signing a.jar file with a digital test certificate Enabling or disabling presentation names in BMC Impact Explorer tool tips Chapter 8 Configuring StateBuilder and gateways 197 Understanding the StateBuilder and gateways StateBuilder configuration file statbld return codes Gateway configuration Exporting events Modifying a statbld.conf file to export events Modifying a gateway.export file to export events Configuring tracing for StateBuilder Trouble-shooting the StateBuilder process Appendix A BMC SIM and EM CLI Reference 209 BMC Impact Manager CLI commands BMC Impact Manager CLI common command options Configuring CLI authentication through BMC Impact Administration Server. 212 BMC Impact Manager CLI common return codes mccomp Compiling rules in the Knowledge Base mcell Starting a cell mcfgtrace Configuring tracing mclassinfo Requesting class information mcollinfo Getting information about a specific collector BMC Impact Solutions Infrastructure Administration Guide

9 mcontrol Performing cell control operations mcrtcell Creating a new cell mcstat Returning cell status mdelcell Deleting a cell mgetinfo Retrieving information about a cell mgetrec Obtaining a global record value mkb Updating the Knowledge Base mkill Stopping a cell mlogchk Performing consistency checks mposter and msend Managing data and events mquery Retrieving objects from a cell mrecover Recovering from a catastrophic data loss mrextract Extracting cell state files to create new state files mrmerge Merging event objects msetmsg Modifying an event msetrec Setting the value of a global record BMC Impact Manager CLI configuration Configuring tracing for BMC Impact Manager CLI commands BMC Impact Manager CLI trace configuration Appendix B mcell.conf file parameters 273 Action result event parameters Cell configuration parameters Cell failover configuration parameters Client communication parameters Encryption parameters Event repository cleanup parameters Event cleanup process Heartbeat parameters Internal cell monitor parameters KB parameters Propagation parameters Deprecated MessageBuffer propagation parameters Reporting client connection parameters Service model parameters State Builder parameters Trace parameters Index 297 Contents 9

10 10 BMC Impact Solutions Infrastructure Administration Guide

11 Figures ConnectionPortRange syntax Distributed event management using event propagation Format of an entry in the mcell.dir file Example of the mcell.dir file and its entries Passive connection format Data object specification mcell.modify file Masking syntax Format of configuration line in mcell.trace file Knowledge Base directory structure Output from mgetinfo kbsources argument Relation among users, groups, roles, and permissions Excerpt from ldap_configuration.xml file Default Infrastructure Management service model Infrastructure Management navigation pane Default service model BMC Impact Solutions (with active services) Edit Relationships dialog with Edit This Relationship subdialog Actions right-click menu High availability (HA) view: two cell servers Actions right-click menu for OVO adapter cells default.econ.config file contents Operator.econ.config file contents Default policy file Listing of the contents of a keystore file Parameters used to print event in BAROC format Example of printed events Command to configure the export file gateway.export file format gateway.explore file output for new events gateway.explore file output for modified events mccomp syntax mccomp example Example output for mccomp mcell syntax Starting a cell Starting a cell as a service on windows Starting the BMC Impact Manager service on Microsoft Windows mcfgtrace syntax mcfgtrace example mclassinfo syntax Figures 11

12 Raw output format for mclassinfo Class tree for mclassinfo Example of mclassinfo command for a list of classes Example output of mclassinfo command for a list of classes Example of mclassinfo command for list of classes Example of mclassinfo command output for list of classes Example of mclassinfo command for adding slot names Example of mclassinfo command output for adding slot names Example of mclassinfo command for adding slot flags Example of mclassinfo command output for adding slot flags mcollinfo syntax Raw output format for mcollinfo mcollinfo example mcollinfo command for verbose mode mcollinfo command for number of events for severity/status mcontrol syntax Retrying Pending propagations with mcontrol command Example of mcontrol command output for retrying pending propagations Terminating a cell using the mcontrol command Example of mcontrol command output for terminating a cell Reconfiguring a cell Example of mcontrol command output for reconfiguring a cell mcrtcell syntax Example of mcrtcell command Example of output of mcrtcell Example of mcrtcell command Example output of mcrtcell Example mcrtcell for recreating an Admin cell mcstat syntax mcstat example Message for cell not running Message for cell running mdelcell syntax Deleting a cell using mdelcell Output for mdelcell if cell is not running Output for mdelcell if cell is running mgetinfo syntax Example of mgetinfo param mgetinfo param command output Example of mgetinfo services mgetinfo services command output Example of mgetinfo services Output of mgetinfo connect mgetrec syntax Example of mgetrec Output of mgetrec mkb syntax mkb command on UNIX mkb output on UNIX BMC Impact Solutions Infrastructure Management Guide

13 mkb command on Microsoft Windows mkb command output on Microsoft Windows mkill syntax Example of mkill Output of mkill mlogchk syntax Example of mlogchk Output of mlogchk mlogchk message mposter syntax msend syntax Example of mposter Definition changes using mposter Enabling persistent buffering using mposter Error message if buffers files are not writable mquery syntax Example of raw output specification Verbose mode options End of form Special BAROC format Example of mquery Select events with severity status Example of mquery Select events from collector Deleting events using mquery mrecover syntax Fixing a broken cell using mrecover mrextract syntax Example of mrextract mrmerge syntax Example of mrmerge msetmsg syntax msetrec syntax Example of msetrec command to send tracing output to text file Example of Heartbeat Figures 13

14 14 BMC Impact Solutions Infrastructure Management Guide

15 Tables BMC Impact Solutions configuration process Cell configuration tasks Substitution parameters for %X in path value parameters Default mcell.propagate options IP Address parameters Files for cell reconfiguration MC_CELL_METRIC slots Default values for client parameters MC_CELL_CLIENT slots MC_CELL_MODIFIED_EVENT slots Trace configuration file parameters MC_CELL_PROCESS_ERROR slots BMC Impact Manager exit codes SIM_NOTIFICATION_REGISTRY dialog box fields Knowledge Base subdirectories Knowledge Base file extensions and directories Configurable IAS files iadmin options BMC Impact Explorer user group mapping to functionality Groups and roles Cell entry format in cell_info.list Server logging properties IAS status monitoring properties IAS thread pool properties IAS synchronization properties mcell.dir entries for a failover pair of Impact Administration cells IAS log files LDAP configuration parameters Event operations Event Table column default values Status table column default values Report parameters (application.properties file) Report parameters (internal.properties) file application.properties file in smsiwc directory application.properties file in smsconsoleserver directory aggregator.properties file internal.properties file Supported application groups Icon listing for infrastructure management model Slot values: Details: General subtab Tables 15

16 Edit Relationship dialog: field descriptions Edit This Relationship subdialog Audit log parameters Audit log IAS properties Slots for specifying support files run_state values for components Component state and menu options for a normal or primary cell in a high availability configuration Component state and menu options for a secondary cell in a high availability configuration Components and actions default.console_policy.prop parameters Property descriptions from ix.properties file Event severity levels and colors Event priority levels and colors Event group configuration files xml files that define user interface elements in BMC IX Presentation names for BMC Impact Solution interfaces Presentation name key formats StateBuilder file name conventions statbld.conf Parameters statbld return codes Gateway configuration parameter predefined variables Gateway Configuration Parameter Text Values gateway.export file parameters BMC Impact Manager CLI command descriptions Common options for CLI commands Common return codes for CLI commands mccomp options mcell options mcell return codes mcfgtrace option mcfgtrace parameters mclassinfo options Type of slot value for mclassinfo Reported facets Class flags Information amount limitation options for mclassinfo mclassinfo return codes mcollinfo options Information amount limitation options for mcollinfo mcollinfo return codes mcontrol option mcontrol controls Files for UNIX mcrtcell options mcrtcell return codes mcstat option mdelcell options BMC Impact Solutions Infrastructure Management Guide

17 mdelcell return codes mgetinfo option mgetinfo information options Information from connect request mgetinfo return codes mgetrec option mkb options mkb new file options mkill option mlogchk return codes mposter and msend options mposter and msend return codes mquery options mquery query options mquery return codes mrecover option mrecover return codes mrextract options mrextract return codes mrmerge options mrmerge return codes msetmsg options msetmsg return codes msetrec options msetrec return codes BMC Impact Manager CLI configuration parameters Action result event parameters Cell configuration parameters Cell failover configuration parameters Client communication parameters Date and time format parameters for Solaris Encryption parameters Event Repository cleanup parameters Heartbeat parameters Heartbeat slots Internal cell monitors parameters KB parameters Propagation parameters Deprecated MessageBuffer propagation parameters Reporting client connection parameters Service model parameters State Builder parameters Cell tracing parameters Tables 17

18 18 BMC Impact Solutions Infrastructure Management Guide

19 Chapter 1 Managing BMC Impact Manager 1 cells This chapter describes how to manage and configure BMC Impact Manager cells. General configuration overview Cell configuration tasks Configuring mcell.conf parameters Configuring event slot propagation Configuring passive connections Configuring slots for time stamping Configuring encryption Reloading cell configuration Managing high availability cell servers Manually failing over to the secondary server Manually switching back to the secondary server Automatic failover process Automatic switchback process Explicitly connecting a CLI to a selected high availability cell server Monitoring event performance Monitoring client to cell interactions Configuring cell tracing Configuring mcell.trace Configuring a destination for cell trace output Sending trace output to another cell Event processing errors Automatic notification of trace configuration changes Interpreting cell execution failure codes Using the BMC IX Administration view to manage cells Connecting or disconnecting a cell Viewing cell information Registering for SIM notification events Trouble-shooting BMC Impact Manager Problem: The cell will not start Problem: The primary and secondary servers for my high availability cell are in active mode simultaneously or are unsynchronized Chapter 1 Managing BMC Impact Manager cells 23

20 General configuration overview General configuration overview To configure the BMC Impact Solutions environment, you configure the following components after installation: BMC Impact Manager cell BMC Impact Explorer BMC Impact Portal Table 1 outlines the tasks that configure these components. Table 1 BMC Impact Solutions configuration process Task Description Component For more information, see 1 (optional) Configure the BMC Impact Portal. BMC Impact Portal Chapter 4, Managing the BMC Impact Portal BMC Portal Getting Started 2 Configure BMC Impact Manager cells. BMC Impact Manager Chapter 1, Managing BMC Impact Manager cells 3 Define user groups for access to the console functions and objects. 4 Distribute the BMC Portal URL address so users can install consoles. BMC Impact Explorer can be deployed as a Java Web Start application from BMC Impact Portal or installed standalone. BMC Impact Administration Server BMC Impact Portal BMC Impact Explorer BMC Impact Service Model Editor Chapter 3, Managing the BMC Impact Administration server BMC Portal Getting Started BMC Impact Solutions Installation Guide 5 (optional) Customize BMC Impact Portal. BMC Impact Portal Chapter 4, Managing the BMC Impact Portal 6 (optional) Customize BMC Impact Explorer. BMC Impact Explorer Chapter 6, Managing the BMC Impact Explorer (BMC IX) console 7 (optional) Configure the StateBuilder, which manages the persistent storage of events. 8 (optional) Customize the labels used in the console interfaces. BMC Impact Manager BMC Impact Portal BMC Impact Manager BMC Impact Service Model Editor Chapter 8, Configuring StateBuilder and gateways Chapter 7, Defining presentation names After you configure BMC Impact Manager, BMC Impact Portal, and BMC Impact Explorer, you are ready to implement event management and service impact management. For information, consult the following resources: 24 BMC Impact Solutions Infrastructure Management Guide

21 Production cells and test cells Event management For information about setting up adapters to collect events, see the BMC Impact Event Adapters User Guide. For information about setting up dynamic data, policies, event groups, and image views, see the BMC Impact Solutions Event Management Guide. For information about defining event data, writing event management rules, defining collectors, or creating actions, see the BMC Impact Solutions Event Management Guide. Service impact management For information about monitoring service impact management, see BMC Impact Solutions Service Impact Management Guide. For information about defining service models, see the BMC Impact Solutions Service Modeling and Publishing Guide. Production cells and test cells A production cell is an EM or SIM cell that service operators and service managers use to monitor the events and services associated with your IT resources in real time. A test EM or SIM cell provides senior service managers and service administrators with a test environment in the following ways: SIM cell Enables publishing of service models from a development sandbox to a test environment before promoting them to a production environment. Each BMC Impact Service Model Editor user has one dedicated test environment, which consists of a pair of test CMDB data sets and an alias to a test cell. Promoted service model components include those in a user s sandbox and in production. For details about test environments and promotion, see the BMC Impact Solutions Service Modeling and Publishing Guide. EM cell For event management, a test cell provides KB developers with a test environment for defining event classes, event management rules, policies, actions, and collectors and testing their behavior with test event data. BMC Impact Portal does not collect events from test cells for reporting. Chapter 1 Managing BMC Impact Manager cells 25

22 Production cells and test cells Production and test cell naming and creation The only way to distinguish a test cell from a production cell is by the cell name. Adopt a naming convention for test and production cells that clearly identifies its purpose. You name a cell when it is created. One cell is created with each BMC Impact Manager instance that you install. You use the mcrtcell command to create additional production or test cells. The mcrtcell command can only be run on the local computer where the cell is being created. For more information about syntax and options available with mcrtcell, see mcrtcell Creating a new cell on page 231. Production and test cell configuration You register test and production cells in BMC Impact Portal. For instructions, see Registering production and test cells in the BMC Impact Portal on page 124. In BMC Impact Service Model Editor, each user associates a test cell to a test environment. For further information, see BMC Impact Solutions Service Modeling and Publishing Guide. In BMC Impact Explorer, assign the production and test cells to a group. The default groups are MyTest and MyProduction. Viewing test cell data You view test data in BMC Impact Explorer. To view test event data, collectors, and actions, select a test cell in the Events view. To view and create test event management policies, select a test cell in the Administration view. To view test service model components, use the Find tool in the Services view and select a test cell. 26 BMC Impact Solutions Infrastructure Management Guide

23 Cell configuration tasks Cell configuration tasks The more you customize your cell to fit your needs, the more efficiently the cell works. All configuration tasks are optional. Table 2 describes the cell configuration tasks. Table 2Cell configuration tasks Task Description For more information, see 1 Create additional cells. When you install BMC Impact Manager on a system, one cell is installed. You can create additional cells by running the mcrtcell command. 2 If you created multiple cells for an environment, you can create separate configuration files for each cell. 3 If you created multiple cells for an environment, configure the cells so that they can communicate with other cells in the network. 4 If you created multiple cells for an environment, configure a high availability cell or cells. 5 Events can be processed locally or selectively propagated to other cells. To configure the event slots that must be propagated when they are changed configure the propagation configuration file. 6 If inbound connections to the cell are disallowed in a protected environment, the connection has to be established within the protected zone to allow a connection between an external client and a cell in the protected zone. 7 To add a time stamp to a slot so that the date and time is recorded when the slot is changed, configure the mcell.modify file. 8 If desired, you can encrypt communication among the various BMC Impact Solutions components. mcrtcell Creating a new cell on page 231 Creating cell-specific configuration files on page 30 BMC Impact Solutions Getting Started Guide BMC Impact Solutions Getting Started Guide Managing high availability cell servers on page 44 Configuring event slot propagation on page 31 Configuring passive connections on page 36 Configuring slots for time stamping on page 37 Configuring encryption on page 38 9 Set the default client parameters executing CLI commands. BMC Impact Manager CLI configuration on page 269 Chapter 1 Managing BMC Impact Manager cells 27

24 Configuring mcell.conf parameters Configuring mcell.conf parameters The mcell.conf configuration file installed with the cell allows it to run without any additional configuration. You can change the configuration parameters in the mcell.conf file to customize the cell for your particular IT infrastructure and environment. You can override some parameters using command line arguments when you start the cell. For more information, see mcell Starting a cell on page 216. To configure the mcell.conf file using a text editor 1 Open the mcell.conf file in a text editor. The default location is MCELL_HOME\etc. 2 Create line entries using the format Parameter=Value based on the syntax rules described in Rules for cell configuration parameter syntax. 3 Save the changes. 4 Either reload the cell configuration or restart the cell for the changes to go into effect. For more information, see Reloading cell configuration on page 43. Rules for cell configuration parameter syntax One parameter per line, in the form: Parameter=Value where the Value extends to the end of the line Typically, the value for a parameter is a Boolean value, a string, or a path. The supported Boolean values are Yes/No and On/Off. The Boolean values are not case sensitive, so, for example, On, ON, on, and even on are equally valid. Do not enclose the value in quotation marks unless you want the quotation marks to be part of the value. Times are stated in seconds unless otherwise specified. By default, all parameter settings are disabled, that is, commented out with a # sign at the beginning of the line of code. Enable a parameter setting by removing the # sign that precedes it. For more information on cell configuration parameters, see Appendix B, mcell.conf file parameters. 28 BMC Impact Solutions Infrastructure Management Guide

25 Configuring mcell.conf parameters Specification of path values Parameters that have path values contain the string filename or dirname, for example TraceConfigFileName or SystemLogDirName. Path values can be stated as: absolute path starts with slash (/) or backslash (\), or on Windows, with a drive designator (for example, D:) runtime relative path starts with./ or../. The path is relative from the cell s working directory. The working directory is the root directory (/) when it runs as a daemon or a service. When running in foreground, it is the directory where mcell is started. configuration relative path all other path values are relative from the cell s configuration directory, or, for program paths, from the kb\bin directory. Path values can contain the substitution parameters $VAR or %X. Any $VAR parameter is substituted by the value of the environment variable VAR. Table 3 lists the possible %X substitution parameters. Table 3 Substitution parameters for %X in path value parameters Parameter Description %H cell home directory %C cell configuration directory %B Knowledge Base binary directory, kb\bin %L log file directory %T temporary file directory %P program name %N cell name Modifying SystemLogDirName, SystemTmpDirName, and KBDirName With the cell configuration parameters SystemLogDirName and SystemTmpDirName, users can specify alternative path locations for the system defined log and tmp directories. Their default values are %H/log and %H/tmp. To enable file name specifications that refer to these alternative locations, use the substitution parameters %L for the log and %T for the tmp directory. They are substituted by the specified path to the log and tmp directory, respectively. Chapter 1 Managing BMC Impact Manager cells 29

26 Creating cell-specific configuration files If you change the default value for the SystemLogDirName parameter or the KBDirName parameter in the mcell.conf file, you must also change the value in the statbld.conf file. If you fail to do this, the cell loses persistency and the mcdb file is not created, because the StateBuilder is configured from statbld.conf file and has no input from the mcell.conf file. As a result, StateBuilder does not know where to find the log files or the KB directory it requires. ConnectionPortRange syntax Figure 1 shows the syntax of ConnectionPortRange. Figure 1 ConnectionPortRange syntax PortRange = PortSequence{, PortSequence} PortSequence = Port[-Port] A range is a number of sequences, each of which is a consecutive range of ports. The cell attempts to access all ports in the specified order. The default is to use any of the ephemeral ports. For example, specifies a range of ports 1828 through , 1829, 1840 specifies the sequence of ports 1828, 1829, and 1840 Creating cell-specific configuration files By default, one set of configuration files is installed during installation of the BMC Impact Manager. These files are located in the MCELL_HOME\etc directory and multiple cells on a host can use them. You can also create unique configuration files for individual instances (cells) as needed. To create cell-specific configuration files 1 Copy the configuration file that you want to be unique to the MCELL_HOME\etc\cellName directory. cellname represents the name of the cell. 2 Using a text editor, edit the configuration file and customize it for that cell and save it. You can copy and edit any configuration file located in the MCELL_HOME\etc directory. 3 Either reload the cell configuration or stop and start the cell so that the changes take affect. 30 BMC Impact Solutions Infrastructure Management Guide

27 Configuring event slot propagation When a cell starts, it searches for configuration files in the MCELL_HOME\etc\cellName directory. If no configuration file is found, the cell uses the configuration file in the MCELL_HOME\etc directory. For example, if you copy the mcell.conf file into the MCELL_HOME\etc\cellName directory and modify it, the cell reads that mcell.conf file and all other files in the MCELL_HOME\etc directory. All cells use the following cell-specific directories: $MCELL_HOME/etc/CellName contains cell-specific configurations (including the Knowledge Base) $MCELL_HOME/log/CellName contains the cell transaction logs and persistent state of the cell $MCELL_HOME/tmp/CellName contains the cell s temporary files High availability cells use the cell-specific directories, but the names of the log and tmp directories are suffixed with # followed by the server number, 1 for the primary server and 2 for the secondary server. The names become: $MCELL_HOME/log/CellName#1 $MCELL_HOME/log/CellName#2 $MCELL_HOME/tmp/CellName#1 $MCELL_HOME/tmp/CellName#2 Configuring event slot propagation Events can be processed locally or selectively propagated to other cells. To configure the event slots that must be propagated when they are changed, and in which direction (forward/backward), you configure the propagation configuration file mcell.propagate. The mcell.propagate file lists all of the slots whose modifications will be propagated. In addition, using the BMC Impact Solutions gateways, events can be propagated to a third-party program in a specific format that is described in a gateway configuration file, gateway.gwtype. The default location for these files is MCELL_HOME\etc. When an event has been propagated to a destination and that event is later modified, the modifications are then propagated to the same destination. The event can be propagated through a Propagate rule. If the destination is a gateway, gateway configuration rules also apply. Chapter 1 Managing BMC Impact Manager cells 31

28 Configuring event slot propagation For the mcell.propagate file to be effective, one or more Propagate rules must be running. For information about Propagate rules, see the BMC Impact Solutions Knowledge Base Development Reference Guide. The format is Slotname = Value, where: Slotname = slot name or CLASS for class-specific slots Value = sequence of { b = backward f = forward } You can specify a slot in the base CORE_EVENT class. However, if you want to specify a slot outside those in the base CORE_EVENT class you must use the CLASS specifier, which means that all class-specific slots are propagated in the direction given. Table 4 on page 32 lists the parameters in the mcell.propagate file and the defaults. Table 4 Default mcell.propagate options Default Parameter Action Performed Values administrator propagates administrator value changes up (forward) within the cell hierarchy f CLASS mc_modhist mc_notes propagates changes to the class-specific slots up (forward) within the cell hierarchy propagates changes to the mc_modhist up (forward) within the cell hierarchy This is a system defined slot that requires such propagation. propagates changes to notes attached to an event up (forward) within the cell hierarchy repeat_count propagates changes to repeat_count up (forward) within the cell hierarchy f severity propagates severity value changes up (forward) within the cell hierarchy f status propagates status value changes in both directions, backward and forward, in the cell hierarchy f f f bf If you have multiple instances of BMC Impact Manager installed, you might want to use event propagation to distribute the event processing load among the cells or to back up events on another cell for failover. Figure 2 on page 33 illustrates a cell network that is collecting and processing numerous events in a distributed environment. 32 BMC Impact Solutions Infrastructure Management Guide

29 Configuring event slot propagation Figure 2Distributed event management using event propagation Some events are propagated for management by other cells in the cell network. cell cell cell cell cell cell cell event sources event sources event sources event sources In this illustration, the lower-level cells process the source events and then propagate (or forward) the events on to higher-level cells according to a Propagate rule or an Event Propagation policy. As events pass through a series of cells, the cells discard unneeded events, identify and leave behind unimportant events, and resolve some of the problems reported by other events. To enable event propagation, perform the following tasks: enable cell-to-cell communication in mcell.dir configure propagation parameters in mcell.conf specify the slots whose modification has to propagate in mcell.propagate either write a Propagate rule or define an Event Propagation policy How unpropagated events are buffered When the cell is started, the buffers are set to a minimum workable size. The default minimum size is 5000 events for each destination buffer and 5000 requests for the propagation buffer. Chapter 1 Managing BMC Impact Manager cells 33

30 About mcell.dir, the cell directory file If the cell cannot propagate events, the cell stores the events to be propagated in the destination buffers and the requests for propagation of those events in the propagation buffer. When the buffers become full, the cell automatically expands the buffer size by a specified percentage (10 percent, by default), unless the buffer has exceeded a maximum size. By default, the maximum buffer size is unlimited, although the practical limit of the buffer size is the amount of available memory. Once the maximum defined buffer size is reached, additional requests will fail. When automatic expansion occurs, an MC_CELL_RESOURCE_EXPANSION event is generated. An expanded buffer will contain free space after propagation has resumed. To free memory resources, the buffer will be reduced when it contains more than the specified amount of free space. Reduction will leave enough free space to avoid the need for an immediate expansion. The buffer will never be reduced below the specified minimum size. When the buffer is reduced, an MC_CELL_RESOURCE_ REDUCTION event is generated. Parameters controlling the buffer size are located in the mcell.conf file. For information on configuring these parameters, see Propagation parameters on page 288. About mcell.dir, the cell directory file The mcell.dir file is created during product installation. It acts as the cell directory file, contains the list of cells, the BMC Impact Portal, Impact Administration Servers, and gateways known on a specific computer. Upon startup, the cell reads the mcell.dir file and associates itself with the appropriate name, encryption key (if encryption is enabled), address information, and port number. In addition, it reads this information for the other cells to which it connects and for the BMC Impact Portal. The mcell.dir file for a cell has an entry for each cell and the BMC Impact Portal to which the cell connect. Figure 3 shows the format of an entry. Figure 3 on page 34 shows an example mcell.dir entry. Figure 3 Format of an entry in the mcell.dir file # ## One line per component : # <Type> <Name> <EncryptionKey> <IpAddress/Port> # <Type> = cell gateway.type # # cell ComponentName EncryptionKey Host/1828 # gateway.portal bip.fullyqualifiedhostname EncryptionKey Host/3783 # admin ImpactAdministrationServerName UserID/Password Host/ BMC Impact Solutions Infrastructure Management Guide

31 About mcell.dir, the cell directory file Each parameter in the file is defined as follows: Attribute Type Name EncryptionKey Description type of component. It can be cell BMC Impact Manager cell name gateway.type Gateway of type type gateway.jserver - predefined jserver gateway type gateway.portal - BMC Impact Portal admin - named Impact Administration Server (IAS) Name is an abstract name for the component. Component names are not case-sensitive and may be any alphanumeric string, including underscores (_). A Portal name is, by convention, the fully qualified host name of the Portal host, prefixed with bip. String to be used as part of the key for the encryption of the communication between a cell and the component. Default value is 0 (zero). Note: If the string has an odd number of characters, the last character is ignored. IPAddress/Port For an IAS component, the string must have the form UserID/Password, or be 0. If the value is non-zero, the indicated UserId and Password are used as IAS login credentials. Host name or IP address and port number on which the component is listening. Default port number for a cell is 1828 and for a Portal is Figure 4 Example of the mcell.dir file Figure 4 shows an example of the mcell.dir file with typical component entries. Example of the mcell.dir file and its entries # ## One line per component : # <Type> <Name> <EncryptionKey> <IpAddress/Port> # <Type> = cell gateway.type # cell bos-71 mc bos-71/1828 cell local mc /1828 gateway.portal bip.bos-71.amc.com mc bos-71/3783 admin ias1 Mac/FreeAI1 bos-71/3084 cell sim1 mc pprod001:1828 bprod001:1828 Conventions for mcell.dir file entries The following conventions apply when creating entries for the mcell.dir file: Cells may be grouped into separate cell files readable only by certain users or groups (domains). Chapter 1 Managing BMC Impact Manager cells 35

32 Configuring passive connections A cell must be configured to communicate with, at a minimum, the cells to which it propagates events. A cell does not need to be configured to communicate with the cell from which it receives events, even for backward propagation. The mcell.dir file may define any number of entries, but each entry must be on a separate line. You can place mcell.dir files on remote mountable partitions or distribute them using rdist, tftp, or any other distribution mechanism. Configuring passive connections If inbound connections to the cell are disallowed in a protected environment, the connection has to be established within the protected zone to allow a connection between an external client and a cell in the protected zone. To connect to the cell, the client issues a passive connection; that is, it waits until the cell establishes the connection to the client. NOTE A passive connection is only possible with the server type clients, such as the cell and gateway clients. Configuring the client for passive connections On the client side, the mcell.dir file has to indicate that the destination cell is located in an isolated protected zone. To configure the client for passive connections 1 Open the mcell.dir file in a text editor. The default location is MCELL_HOME\etc. 2 For the destination cell, replace Host:Port with 0 as shown in Figure 5. Figure 5 Passive connection format cell cellname EncryptionKey 0 3 Save the changes. 4 Either reload the cell configuration or stop and start the cell. 36 BMC Impact Solutions Infrastructure Management Guide

33 Configuring slots for time stamping When a cell or gateway client needs to connect to an isolated destination cell, it cannot establish a connection because it does not have the IP address and port number of the cell. Instead, the cell or gateway client registers the destination and waits for a connection from it. Configuring a cell for passive connections On the cell side, an indication is needed that a client could be waiting on a connection. To configure a cell for passive connections To configure a cell for passive connection, you must create a data object and specify how to control it, as shown in Figure 6. Figure 6 Data object specification MC_CELL_PASSIVE_CLIENT ISA MC_CELL_HEARTBEAT ; END The cell slot, as defined in the MC_CELL_HEARTBEAT superclass, gives the name of the passive client. The enable slot in the superclass specifies whether or not monitoring and reconnection is enabled. The cell attempts to connect to passive client targets as configured with the standard connection parameters. As soon as a connection is established, the connection is reversed. At that moment, the client takes up the connection and behaves as an ordinary client. Monitoring passive targets The cell may not be aware that a connection has been terminated when a connection from a passive client to a cell is terminated. The passive client cannot try to reestablish the connection, nor can it signal the cell to reestablish the connection. To avoid such situations, the cell monitors the passive client, based on the standard heartbeat monitor mechanism. Then, when a disconnect is detected, the cell attempts to connect to the passive client target. Configuring slots for time stamping Each event has an mc_modification_date slot that contains the time stamp of the last modification of the event. Only select slot modifications set this time stamp. To add a time stamp to a slot so that the date and time is recorded when the slot is changed, you must configure the mcell.modify file. The mcell.modify file contains the names of the slots that affect the mc_modification_date slot. When one of the slots listed in the mcell.modify file is modified, the mc_modification_date slot is set with the time stamp of this change. Chapter 1 Managing BMC Impact Manager cells 37

34 Configuring encryption To configure slots for time stamping 1 Open the mcell.modify file in a text editor. The default location is MCELL_HOME\etc. 2 Create a line entry containing the name of the slot whose modification is to be time stamped. Figure 7 shows an example of the mcell.modify file. Figure 7 mcell.modify file # Configuration of slots affecting mc_modification_date when modified # Format : # SlotName # Special name : CLASS : specifies all class-specific slots status severity mc_priority repeat_count CLASS When CLASS is used as a slot name, all class-specific slots or slots not defined in the base class CORE_EVENT update the mc_modification_date slot with a time stamp. 3 Save the changes. 4 Either reload the cell configuration or stop and start the cell. Configuring encryption You can encrypt communication among the various BMC Impact Solutions components. To enable encryption, make the appropriate settings in the following locations: the cell s configuration file mcell.conf the CLI configuration file mclient.conf the BMC Impact Administration server used by BMC Impact Explorer the cell directory file, which is MCELL_HOME\etc\mcell.dir by default 38 BMC Impact Solutions Infrastructure Management Guide

35 Configuring encryption mcell.conf file settings that control encryption The primary settings controlling encryption are in the cell configuration file mcell.conf. The following settings control encryption: Encryption ForceEncryption EncryptionKey If Encryption is set to Yes, encrypted communication to and from the cell is enabled, but not required. For example, if a BMC Impact Explorer does not have encryption enabled, then the communication with that particular BMC Impact Explorer console is not encrypted. ForceEncryption requires encryption for all communications. If the BMC Impact Explorer attempts an unencrypted connection to the cell, the connection is rejected. The encryption process uses the EncryptionKey value as part of the encoding key. If there is no encryption, the EncryptionKey value has no effect. mclient.conf file settings that control encryption All CLIs can use an mclient.conf file to determine encryption functionality. The parameters are Encryption EncryptionKey For more information about the CLI configuration parameters, see BMC Impact Manager CLI configuration on page 269. mcell.dir file settings that control encryption The mcell.dir file contains a field for an EncryptionKey. At installation, the default EncryptionKey value is set to mc. BMC Software recommends that you modify the value for security. The string specified as the encryption key is transformed to a binary value as follows: Characters of the encryption key are grouped in pairs. If the string has an odd number of characters, the last character is ignored. Each pair is converted to an 8-bit value. The first character of the pair determines the four most significant bits, the second character determines the four least significant bits. Chapter 1 Managing BMC Impact Manager cells 39

36 Configuring encryption A character in the hexadecimal range (0-9, A-F, a-f) is converted to the corresponding hexadecimal value (for example, 8 gives the value 8, B gives the value 11). Any other character is converted to its ASCII code modulo 16. Encryption behavior between cells and components This section describes the encryption behavior of cells and components during communication. The following actions occur when a BMC Impact Solutions component initiates communication with a cell: 1. The component scans the cell configuration file, mcell.dir, for that cell s connection information. 2. BMC Impact Explorer retrieves the cell s connection information from the BMC Impact Administration server. 3. The component opens a connection to the cell. If the cell has Encryption=yes, the component can use encrypted or non-encrypted communication. The component must use encrypted communication if the cell has ForceEncryption=yes and Encryption=yes. If the communication is encrypted, both the cell and the component must use the same EncryptionKey values to establish communication. Information retrieval A component must have the address and port of a cell to establish communications with it. To establish encrypted communications, the component must also have the encryption key of the cell. BMC Impact Explorer and the CLI commands determine the information in different ways: BMC Impact Explorer acquires the information from the BMC Impact Administration server (cell_info.list). BMC Impact CLI commands obtain the information by determining the server location using one of the following methods: directly from the CLI command from CLI configuration parameters in mclient.conf from mcell.dir if you use the -n cellname option 40 BMC Impact Solutions Infrastructure Management Guide

37 Configuring encryption Default values The default value for cellname is the name of the host (hostname). The default value for the port is When the mcell.dir file is present, the default value is EncryptionKey=mc at installation. BMC Software recommends that you modify this value for security. If the mcell.dir file is absent on the host and you do not specify an encryption key, the CLI command uses 0 (zero) as the default value for EncryptionKey. This value enables encrypted communications. NOTE You can disable encryption by setting the configuration parameter to Encryption=No. You might want to use this setting to disable encryption while tracing. Mandatory key specification conditions You must specify the encryption key if the following conditions apply: you execute the CLI command on a host without an mcell.dir file the cell has an encryption key other than 0 (zero) These conditions apply with the default installation. However, if the mcell.dir file is present on the host, and the file specifies the encryption key, you are only required to specify the cellname. Limiting cell access A client is allowed to connect to the cell if its IP address matches the general AllowConnectionFrom as well as the client type-specific Allow*From. Figure 8 shows an example of masking syntax. Figure 8 Masking syntax AddrMaskList = AddrMask {':' AddrMask} AddrMask = Addr ['/' Mask] Addr = Nr '.' [Nr '.' [Nr '.' [Nr]]] Mask = Addr Nr Nr = Chapter 1 Managing BMC Impact Manager cells 41

38 Configuring encryption The following conventions apply: An abbreviated Addr or Mask is expanded with zeros. A numeric Mask (number without trailing dot) gives the number of 1 bit. An omitted Mask defaults to all bits set to 1. A connection is allowed if the source address ANDed with the Mask matches Addr ANDed with the Mask. When the Mask is all zeros, any address matches regardless of the value of Addr. For all Mask bits whose value is one (1), the equivalent bits in Addr must match the equivalent bits in the source address. Table 5 lists the IP address parameters. Table 5 IP Address parameters Parameter AllowConnectionFrom=0./0 Description all systems allowed (same as /0) AllowConnectionFrom=0./32 no system allowed ( is not a valid IP address) AllowConnectionFrom= / any system from the xx.xx network can connect AllowConnectionFrom= /1 allows any host with an IP address lower than , because it indicates there is only 1 bit in the mask Only the highest-order bit is considered and must be the same as 127, which is a 0 bit. AllowConnectionFrom= / : / systems on the xx and xx networks may connect The default is 0./0, indicating that the server should accept connections from any source. Usually this is useful only for testing or debugging, or for use with a system that is isolated from the network. To specify one single address, specify the address without a mask, or use a 32-bit mask. The following examples are equivalent ways of specifying a single address: / / BMC Impact Solutions Infrastructure Management Guide

39 Reloading cell configuration When you specify more than one address per mask pair, a system that matches at least one of the pairs can accept a connection. Connection attempt using invalid encryption key An attempt to connect to a cell using an invalid encryption key or from an disallowed address generates an internal event MC_CELL_UNALLOWED_CONNECT. This event contains a slot, reason, that includes the reason for the refused connection. Reloading cell configuration The cell does not automatically reconfigure itself, but you can customize and reload the configuration after you have made configuration changes without restarting the cell. To reload cell configuration To trigger the reconfiguration, perform one of the following actions: Send a hang-up signal on UNIX. Run the mcontrol command on UNIX or Windows. For information about the mcontrol command, see mcontrol Performing cell control operations on page 228. Table 6 lists the specific instances in which the reconfigure feature can be used and the effect that results from its use. Table 6 Files for cell reconfiguration (part 1 of 2) Type Name/Directory Result of reconfiguration cell directory mcell.dir a This internal directory is replaced with new contents from the mcell.dir file. Associated data objects are replaced as well. Connected clients and destinations remain connected, even if the corresponding directory entries are modified. cell tracing mcell.trace a Tracing is adapted and has the same effect as through the mcfgtrace CLI. cell mcell.conf The cell restarts automatically. configuration mcell.propagate mcell.modify KB collector kb\collectors The cell restarts automatically. Chapter 1 Managing BMC Impact Manager cells 43

40 Managing high availability cell servers Table 6 Files for cell reconfiguration (part 2of 2) Type Name/Directory Result of reconfiguration KB program kb\classes The cell restarts automatically. \kb\rules \kb\lib \kb\bin KB data kb\data The cell restarts automatically. \kb\records a For mcell.dir and mcell.trace, a hang-up signal on a UNIX platform performs maximum reconfiguration without a cell restart. For information about restarting a cell, see Interpreting cell execution failure codes on page 56. Managing high availability cell servers If you have installed and configured primary and secondary cell servers as described in the BMC Impact Solutions Installation Guide and the BMC Impact Solutions Getting Started Guide, you may need some of the following advanced procedures to manage your high availability environment. WARNING The primary and secondary servers of a high availability pair must run on two different logical OS images of the same type. Primary and secondary servers of a high availability pair running on the same system or running on different operating systems is not supported. The highest possible availability for a cell occurs when two server machines are close to each other with a highly reliable network connection. When the two server machines are on remote sites, the high availability cell functions more like a Disaster Recovery system. Only one of the two servers should be active at any time. WARNING It is highly recommended that you disable automatic failover and enable manual failover when the connection between the primary and secondary server is unreliable. Otherwise, there is a risk that both primary and secondary servers would be active at the same time when they cannot communicate with each other, due to network problems. Although it is technically possible to activate both servers, this is not supported. If both servers are activated, incompatible server states can occur. If the server states are incompatible, manual intervention is required to re-synchronize the primary and secondary servers. If this situation occurs, see Problem: The primary and secondary servers for my high availability cell are in active mode simultaneously or are unsynchronized. on page BMC Impact Solutions Infrastructure Management Guide

41 Automatic failover process WARNING It is highly recommended that you disable automatic failover and enable manual failover when the connection between the primary and secondary server is unreliable. Otherwise, there is a risk that both primary and secondary servers would be active at the same time when they cannot communicate with each other. This situation is not supported. If this situation occurs, see Problem: The primary and secondary servers for my high availability cell are in active mode simultaneously or are unsynchronized. on page 63. Automatic failover process If a high availability cell is configured with CellDuplicateAutoFailOver=Yes, it will automatically perform a failover when needed. Failover occurs when the secondary server loses its connection with the primary. If it cannot connect to the primary server within the time period specified in the CellDuplicateFailOverTimeOut parameter, the secondary server assumes that the primary server is no longer available and becomes active. The CellDuplicateFailOverStartTimeOut parameter specifies the period after startup after which the secondary server will become active when it has no connection with the primary server. This parameter should be set high enough to allow primary and secondary servers to be started at more or less the same time. Although you can start the secondary server before the primary server, if the secondary server is started first, it cannot connect to the primary server. Therefore, the value of the CellDuplicateFailOverStartTimeOut parameter should be set so that there is enough time for the primary server to start. Automatic switchback process If a high availability cell is configured with CellDuplicateAutoSwitchBack=Yes, it automatically performs a switchback when the primary server starts. When the primary server is started, it connects to the secondary server and determines its activity level. If the secondary is active, the switchback procedure is started. The secondary server switches to standby mode and transmits its state to the primary server. Once the primary server has determined that the secondary server is in standby mode, the primary server restarts itself and reloads the state that it received from the secondary server. Chapter 1 Managing BMC Impact Manager cells 45

42 Manually failing over to the secondary server Manually failing over to the secondary server If there is a problem with the primary server, a failover to the secondary server is required. By default, failover is automatic; however, if the cell is configured with CellDuplicateAutoFailOver=No, this failover must be performed manually. To manually fail over from a primary server to a secondary server 1 Terminate the primary server (if it is still running) by entering: mkill -n CellName#1 WARNING You must explicitly include the #1 suffix after the cell name or the mkill command will terminate the secondary cell if the command cannot connect to the primary cell. 2 Start the secondary cell server by entering: mcontrol -n CellName#2 start Manually switching back to the secondary server After a primary cell server has been repaired, a switchback operation is required to re-activate it. By default, switchback is automatic; however, if the cell is configured with CellDuplicateAutoSwitchBack=No, switchback must be performed manually. To manually switch back from a secondary server to a primary server 1 Clear the primary server log directory by entering the appropriate command for your operating system: For UNIX, enter: rm -f $MCELL_HOME/log/CellName#1/* For Windows, enter: del /f /s /q %MCELL_HOME%\log\CellName\* 2 Switch the secondary server to standby mode by entering: mcontrol -n CellName#2 standby 3 Transfer the state file from the secondary to the primary server: On UNIX, copy host2:$mcell_home/log/cellname#2/mcdb to host1:$mcell_home/log/cellname#1/mcdb On Windows, copy host2:%mcell_home%\log\cellname#2\mcdb to host1:%mcell_home%\log\cellname#1\mcdb 4 Start the primary cell server. 46 BMC Impact Solutions Infrastructure Management Guide

43 Explicitly connecting a CLI to a selected high availability cell server Explicitly connecting a CLI to a selected high availability cell server A CLI will automatically connect to the primary cell server. If the primary cell server is not active, the CLI connects to the secondary server. It is possible to connect a CLI explicitly to either the primary or the secondary server, using the common CLI -n option. One method is to indicate the host and port of the desired server explicitly. For example: mgetinfo -n host2/port2 -v activity This example retrieves the activity level of the secondary cell server. Another method is to enter the cell name, followed by # and the server number (1 for primary and 2 for secondary). For example: mgetinfo -n CellName#2 -v activity Monitoring event performance Event processing metrics are internal counts maintained on cell performance categories in connection with event processing. These metrics count the following items: number of events received, including erroneous ones number of events containing errors number of events dropped by rules (Filter, Regulate) number of events removed from the event repository during cleanup number of events propagated, including sendto number of events added to the event repository, that is, entering the permanent context Calculation is performed on a 60-second basis, so every minute the counters are restarted. Counts from the last five minutes are retained. Running counters are reset only on demand. Chapter 1 Managing BMC Impact Manager cells 47

44 Monitoring event performance The resulting metrics are: short term total count of the last complete one-minute interval medium term sum of the five last, completed one-minute intervals long term running total Metrics are stored in MC_CELL_METRIC data objects, one object instance for each metric. Each metric mentions the subject. For each of the short-, medium-, and longterm results, it contains the length of the interval, in seconds, and the total count. An average per second is also provided, rounded to an integer. Other averages per second, minute, or hour can be calculated by the application from this information, if needed. A configuration parameter, CellMetricsEnabled, determines whether metrics are collected or not. The mcontrol CLI is used to switch metric collection on and off, and to reset the counters. Short- and medium-term metrics are reset whenever metrics are disabled. Metrics can be retrieved through rules by data object access, or through a command. The BMC Impact Explorer console and the mgetinfo CLI can use that command. The received event counter does not include incoming messages that cannot be parsed as events. It does include events of nonexistent classes or events with erroneous slots. These are added to the erroneous event counter. Internally generated events are counted as received events. Dropped events include those that are dropped when an event with the same universal ID exists. Table 7 lists the metrics data objects MC_CELL_METRIC slots. Table 7 MC_CELL_METRIC slots Slot description long_average long_interval long_total medium_average medium_interval medium_total short_average short_interval short_total subject Description metric description long-term average, per second long-term interval lengths, in seconds long-term total count medium-term average, per second medium-term interval lengths, in seconds medium-term total count short-term average, per second short-term interval lengths, in seconds short-term total count metric subject name Subject names available are: 48 BMC Impact Solutions Infrastructure Management Guide

45 Monitoring client to cell interactions ReceivedEvents ErrorEvents DroppedEvents StoredEvents RemovedEvents PropagatedEvents CLI commands for collecting metrics are: mcontrol metrics on off reset mgetinfo [-v] metrics Monitoring client to cell interactions Whenever a client connects, disconnects, or modifies an event, the cell generates an internal event to represent this operation. Such events are only generated for certain clients configured by means of the ReportConnectClients and ReportModifyClients settings. The parameter value is interpreted from left to right. Settings that conflict with previous settings override the previous ones. Table 8 lists the defaults for these two parameters. Table 8 Default values for client parameters Parameter ReportConnectClients ReportModifyClients Value browser, Console, mcontrol, mkill, mposter, msetmsg, msetrec mposter, msetmsg, msetrec Every parameter corresponds to a reporting clients set. Such a set has a positive and a negative list. Clients that belong to the positive list will have their operation reported while operations performed by clients on the negative list will not be reported. Clients that are not named in the parameter are considered to be on the default list. The default list initially is the negative list. The default list can be modified through a special setting of the parameter. A value for a reporting configuration parameter consists of a comma separated sequence of client names. Every client name can be prefixed with a minus sign (-) or a plus sign (+). The client name prefixed with the minus sign (-) is added to the negative list. When not prefixed, or prefixed with a plus sign (+), it is added to the positive list. Chapter 1 Managing BMC Impact Manager cells 49

46 Configuring cell tracing The special value ALL in place of a client name refers to the default. Including ALL or +ALL modifies the default list so it becomes the positive list. With -ALL, the default list is the negative list. Both parameters could include -ALL, as this is the default setting for clients that are not explicitly mentioned. The superclass for client operation related events is MC_CELL_CLIENT. Table 9 lists the slots. Table 9 MC_CELL_CLIENT slots Slot client_location client_name client_type Data the location of the client as IPAddress:Port the client's name, as announced by the client, or noname type of client, such as adapter, CLI, console, cell There are three subclasses of this class: MC_CELL_ALLOWED_CONNECT to represent successful client connection MC_CELL_UNALLOWED_CONNECT to represent a refused connection An attempt to connect using an invalid encryption key generates an internal event, MC_CELL_UNALLOWED_CONNECT, that contains the slot reason, which details why the connection is refused. MC_CELL_DISCONNECT to represent a disconnect. Another class, MC_CELL_MODIFIED_EVENT, represents the operation of modification of an event. Table 10 lists the slots. Table 10 MC_CELL_MODIFIED_EVENT slots Slot event requestor Data universal event ID of the event being modified identification of the user that performed the modification Configuring cell tracing To set up cell tracing, configure the trace configuration file, mcell.trace tracing parameters in the mcell.conf configuration file You can also configure cell tracing using the mcfgtrace command. For further information, see mcfgtrace Configuring tracing on page BMC Impact Solutions Infrastructure Management Guide

47 Configuring mcell.trace Configuring mcell.trace The trace configuration file, mcell.trace, configures the tracing of the cell s operation. Tracing messages are divided in several levels. Every module of the cell can be configured differently. An output destination can be determined per message level and per module. Messages also can be disabled at the same granularity. The default location is MCELL_HOME\etc. The configuration commands in mcell.trace are incremental. Every new command adds to the configuration, possibly overriding previous commands either completely or partly. Figure 9 shows the format of a configuration line in the mcell.trace file.. Figure 9 Format of configuration line in mcell.trace file <Module> <Level> <Destination> SWITCH <Switch> <Destination> Table 11 lists the parameters that must be defined in a configuration line. Table 11 Trace configuration file parameters (part 1 of 2) Parameter Destination Level a Description destination file name or predefined value for the selected trace messages or switch predefined values: no disables these tracing messages console sends to the console device stderr sends to standard error stream message severity value level predefined values: FATAL ERROR WARNING INFORM VERBOSE Chapter 1 Managing BMC Impact Manager cells 51

48 Configuring a destination for cell trace output Table 11 Trace configuration file parameters (part 2of 2) Parameter Module a a SWITCH Switch Description name of module, each of which corresponds to a particular category of information, such as filtering or configuration; values are as follows: ACTION HEARTBEAT RESULT COLLECT INTEVT ROLES COLLMAP MC2TEC RULES CONFIG MCBAROC SERVICE CONTROL MESSAGES SRVMGT DATAPROC METRIC STATBLD DBDATAID PROPAGATE SVCMGT DBEVTID QUERY SVRCOMM DBEVTTM RECOVERY SVRDIR EVTLOG RECTRL SYNCH EVTPROC REGEX SYSPROC EXPORT REGULATE TRACE FILTER keyword that enables access to a sublevel or category of messages for a module switch name You can also specify ALL or * (wildcard) for these parameters. Configuring a destination for cell trace output You can use the tracing parameters to configure the cell to output information to a specified destination. The destination for cell trace output is determined by the value of the DESTINATION parameter in the mcell.trace file. Possible destinations for cell trace output are: the console the standard error stream an external file or files no trace output In addition to sending trace output to one of these destinations, you also can send trace output to another cell. For information, see Sending trace output to another cell on page 53. Sending trace output to a console To send trace output to a console, open the mcell.trace file and set the DESTINATION parameter to the value console. 52 BMC Impact Solutions Infrastructure Management Guide

49 Sending trace output to another cell Sending trace output to the standard error stream To send trace output to the standard error stream of the command window where the cell is running, open the mcell.trace file and set the DESTINATION parameter to the value stderr. If the cell runs as a service or daemon, all trace output that is configured to go to stderr will be redirected to the file specified in the TraceDefaultFileName parameter in the mcell.conf file. If you specify for the trace output to go to stderr, the trace file is truncated every time the cell restarts, and a new trace file is written. Sending trace output to an external file To send trace output to an external file or files, open the mcell.trace file and set the DESTINATION parameter to the path and file name of the destination file. The cell keeps the trace file open on both UNIX and Windows systems. On UNIX, any attempt to remove the file will succeed. However, all trace output goes to an invisible file that becomes visible when the cell is restarted. A trace destination file can be located anywhere, but the BMC Impact Solutions process must have write access to that location. WARNING The MCELL_HOME\tmp\cellName directory is for temporary files only. A trace file placed in that directory will be deleted by the cell when it restarts. To maintain your trace file across cell sessions, place it in a different directory. Disabling trace output To disable trace output, open the mcell.trace file and set the DESTINATION parameter to the value no. Sending trace output to another cell Sending trace output to a cell allows you to capture the traces of one or more cells in a centralized location. To send the trace of one cell to another cell, the trace of the originating cell should be produced as events. Those events can be sent to the destination cell using a propagate rule. Chapter 1 Managing BMC Impact Manager cells 53

50 Sending trace output to another cell To enable sending cell trace information to another cell, you must configure which module/level combinations of trace messages will be produced as events add a propagate rule to the Knowledge Base to specify which trace log events have to be propagated to which destination(s) Once configured, the cell trace module will generate an internal event for each trace log message. Definition of the class of trace log events Each trace message is represented through a single MC_CELL_LOG_MSG event, as shown: ENUMERATION MC_LOG_LEVEL 10 VERBOSE 20 INFORM 30 WARNING 40 ERROR 50 FATAL END MC_EV_CLASS: MC_CELL_LOG_MSG ISA MC_CELL_CONTROL DEFINES { log_time: INTEGER; -- Timestamp log_program: STRING; -- Name of the program generating the message log_module: STRING; -- Name of the module producing the message log_level: MC_LOG_LEVEL; -- Message level log_src_file: STRING; -- Source file name log_src_line: INTEGER; -- Source file line number log_msg_id: STRING; -- Unique message identifier (form BMC-IMCxxxxxxC) log_args: LIST_OF STRING; -- Message argument list log_text: STRING; -- Message text in origin's locale }; END The log_time date and time slot is an integer in timestamp format. The textual representation of the log message log_text uses the originating cell's local message catalog. 54 BMC Impact Solutions Infrastructure Management Guide

51 Event processing errors Configuring trace messages to be produced as log events By default, a cell will not produce log events for its trace. This has to be enabled explicitly using the TraceEvents configuration parameter in the mcell.conf file. The value of this parameter is a comma-separated sequence of module:level combinations. Each one is optionally prefixed with a + or a - sign to indicate addition or removal, respectively, from the list. The special value ALL for module and for level indicate all modules and all levels. For example TraceEvents=ALL:ALL,-ALL:VERBOSE This setting specifies that events must be generated for messages from all modules, of all but the VERBOSE level. WARNING Event tracing should be configured with care, as it may produce an excessive number of events. In particular, VERBOSE level messages should not be configured as events. For more information about the trace configuration parameters in mcell.conf, see Trace parameters on page 293. Adding a propagate rule to the Knowledge Base to specify which trace log events have to be propagated to which destination(s) The propagate rule syntax is described in the BMC Impact Solutions Knowledge Base Development Reference Guide. The following is an example of a propagate rule for trace log events: propagate PropTraceEvents: MC_CELL_LOG_MSG to CentralAdminCell END Event processing errors When an error occurs during the processing of an event, the cell s trace displays an error message. It also generates an internal event of class MC_CELL_PROCESS_ERROR, with the slots listed in Table 12. Chapter 1 Managing BMC Impact Manager cells 55

52 Automatic notification of trace configuration changes Table 12MC_CELL_PROCESS_ERROR slots Slot error_code error_goal error_message error_source event Data the error number the part of the processing command that has the error an error description message the position in the rule source where the error occurred the mc_ueid of the event that was being processed Automatic notification of trace configuration changes The cell automatically generates the following MC_CELL_LOG_CHANGED event when trace configuration is modified for a cell: MC_EV_CLASS: MC_CELL_LOG_CHANGED ISA MC_CELL_CONTROL DEFINES { log_module: STRING; -- Name of the module log_level: MC_LOG_LEVEL; -- Message level log_destination: STRING; -- Destination file name }; END If the modification applies to all modules, then log_module=all. If the modification applies to all message levels, then log_level=all. The log_destination slot contains the full path to the destination file, in normalized (UNIX) form. Other possible values are: no indicates disabling stderr indicates redirection to the standard error stream console indicates redirection to the console terminal Interpreting cell execution failure codes When the cell runs as a daemon or a service, it has no standard output or error stream. Tracing that is configured to go to stderr will be redirected to a file in this case. The path for that file can be configured in mcell.conf. The default is MCELL_HOME\tmp\cellName\trace. 56 BMC Impact Solutions Infrastructure Management Guide

53 Interpreting cell execution failure codes If the cell service setup fails, an error file, mcell.err, is generated. Additional service setup failures can be appended to the original file, resulting in a file content of multiple lines. Normally, each line corresponds to one failed service setup. This error file contains exit codes specific to BMC Impact Manager. Table 13 lists the exit codes for BMC Impact Manager. Table 13 BMC Impact Manager exit codes Code Description 1 invalid command line options used 2 bad home directory specification through option -l 3 no home directory could be determined 4 specified home directory is invalid 5 internal initialization failure 16 tracing configuration failed 17 system process handling module initialization failure 19 logging facility initialization failure 27 service control module initialization failure 29 Knowledge Base load failed 37 message handling module initialization failure 39 internal object initialization failure 47 event processing module initialization failure 49 saved state reload failed 57 query handling module initialization failure 59 service activation failed 67 internal object module initialization failure 69 metrics initialization failed 77 data processing module initialization failure 79 metrics activation failed 97 service setup failed Chapter 1 Managing BMC Impact Manager cells 57

54 Using the BMC IX Administration view to manage cells Using the BMC IX Administration view to manage cells You can also manage cells by using a pop-up menu in the navigation pane of the Administration view of BMC Impact Explorer to perform the following tasks: connect and disconnect a cell view cell information register for state change events For more information on using BMC Impact Explorer, see Chapter 6, Managing the BMC Impact Explorer (BMC IX) console and the BMC Impact Solutions Event Management Guide. Connecting or disconnecting a cell Use the Disconnect and Connect menu commands to connect or disconnect a cell from BMC Impact Explorer. To connect or disconnect a cell 1 Right-click the cell icon or name. 2 Select Connect or Disconnect from the pop-up menu. This menu item toggles between Connect and Disconnect, depending on the state of the cell when you right-click it. The result of your action in the Administration view is reflected in the Events and Services views. Viewing cell information Use the View Manager Info menu command to view information about and the metrics associated with the cell selected. To view cell information 1 Right-click a cell. 2 Choose View Manager Info. 58 BMC Impact Solutions Infrastructure Management Guide

55 Registering for SIM notification events The Impact Manager Info dialog box appears with cell property information presented on the Info tab. 3 To refresh the information in the Workload tab of this dialog box, click Refresh in the top right corner of the tab. Registering for SIM notification events BMC Impact Manager can generate events that notify you of changes to components in the SIM service model. These events are called SIM notification events. The four types of SIM notification events are SIM_COMPONENT_CHANGE SIM_COMPONENT_DELETE SIM_COMPONENT_OVERWRITE SIM_RELATIONSHIP_CHANGE SIM_RELATIONSHIP_DELETE NOTE In the mc_sm_notify.baroc file under mcell_home/etc/cellname/kb/classes, you can view the definitions of the SIM_NOTIFICATION_EVENT base class and the event classes SIM_COMPONENT_CHANGE, SIM_COMPONENT_DELETE, SIM_COMPONENT_OVERWRITE, SIM_RELATIONSHIP_CHANGE, and SIM_RELATIONSHIP_DELETE. The SIM_COMPONENT_DELETE and SIM_RELATIONSHIP_DELETE events are generated when you remove a configuration item or an impact relationship from the published service model. The SIM_COMPONENT_CHANGE and SIM_RELATIONSHIP_CHANGE events are generated when a configuration item or an impact relationship is altered by the cell because of a change in status or priority. BMC Impact Manager generates these notification events upon request by a client. For example, the BMC Impact Portal can register to receive notification events just as a gateway client can. Another BMC Impact Manager or even the BMC Impact Manager containing the SIM model can register to receive the notification events. Chapter 1 Managing BMC Impact Manager cells 59

56 Registering for SIM notification events The following slots are reported: Slots for configuration item: status manual_status computed_status self_status impact_status manual_status_comment manual_status_requestor consolidate_function root_causes schedule_status cost self_priority impact_priority computed_priority maintenance_mode Slot for relationships: true_impact To register for notification events, you create a SIM_NOTIFICATION_REGISTRY instance in the cell, telling it which notification events to look for and which clients to forward the events to. You perform this procedure through the BMC IX interface or through the mposter CLI. NOTE Refer to the BMC Impact Solutions: Knowledge Base Development Reference for mposter examples that show how to register for notification events. To register for notification events in the BMC IX 1 In the Adminstration tab, expand the cell for which you want to create a SIM_NOTIFICATION_REGISTRY data instance. 2 Expand the DATA folder. 3 Expand the MC_CELL_DATA folder. 60 BMC Impact Solutions Infrastructure Management Guide

57 Registering for SIM notification events 4 Right-click SIM_NOTIFICATION_REGISTRY. 5 Select New. 6 Fill in the editable fields in the SIM_NOTIFICATION_REGISTRY dialog box. Table 14 SIM_NOTIFICATION_REGISTRY dialog box fields (part 1 of 2) Field mc_udid client_data clients requested_notifications notification_mode Description populated automatically allows you to define a rule set for the SIM notification events that your client has registered for. For example, the rule could look for the text john in the client_data to determine if it is a state change requested by john. The content of this slot is copied to the client_data slot of the corresponding SIM notification event. Each SIM_NOTIFICATION_REGISTRY data instance must have a different value for this slot. This slot is available only in BMC Impact Manager versions 7.0.x and later. comma-separated list of clients where the notification must be sent. The clients in the list must be defined in mcell.dir. By default, the cell name is listed as the client in mcell.dir, so you do not need to change mcell.dir if you are sending events internally. comma-separated list of SIM notification events for which notification is requested SIM_COMPONENT_CHANGE SIM_COMPONENT_DELETE SIM_COMPONENT_OVERWRITE SIM_RELATIONSHIP_CHANGE SIM_RELATIONSHIP_DELETE specifies how slot values that have not changed are reported in the SIM notification event DELTA the slots whose values do not change are reported with their default values, not their current values. The default value is an empty string for symbolic values and -1 for numer ic values. See the.baroc class definition of the SIM notification event for the default slot values. FULL the current values of all slots are reported, including those that have not changed Chapter 1 Managing BMC Impact Manager cells 61

58 Registering for SIM notification events Table 14 SIM_NOTIFICATION_REGISTRY dialog box fields (part 2of 2) Field Description notifications_at_registration instructs the cell whether or not to send the current component states at the moment of registration YES instructs the cell to send the current component state at the moment of registration asset_filter NO instructs the cell not to send the current component state at the moment of registration filter contains one class name. When you specify a class name, only state change notifications for configuration items of this class or a sub-class are generated. 7 Click OK. In the Administration tab, the new SIM_NOTIFICATION_REGISTRY instance is displayed under SIM_NOTIFICATION_REGISTRY. To delete a SIM_NOTIFICATION_REGISTRY data instance 1 Right-click the SIM_NOTIFICATION_REGISTRY data instance. 2 Select Delete. To modify a SIM_NOTIFICATION_REGISTRY data instance 1 Right-click the SIM_NOTIFICATION_REGISTRY data instance. 2 Select Edit. 3 Make the necessary changes to the fields in the SIM_NOTIFICATION_REGISTRY dialog box. 4 Click OK to accept the changes. 62 BMC Impact Solutions Infrastructure Management Guide

59 Trouble-shooting BMC Impact Manager Trouble-shooting BMC Impact Manager NOTE If you are experiencing problems with BMC Impact Manager, you can turn on cell tracing to help diagnose the problem. For instructions, see Configuring cell tracing on page 50. Problem: The cell will not start If there is nothing in the log trace files to help you diagnose the problem, try running the cell in the foreground. This will frequently provide the information needed to correct the problem or enough information for BMC Support to diagnose the problem. To run the cell in the foreground, enter: mcell n {cell_name} d Possible solution: Delete the mcdb.0 and mcdb.lock files It is possible that a statbld failure has occurred. To correct this problem, follow these steps: 1 Look for the following files in the MCELL_HOME\log\cellName directory: mcdb.0 mcdb.lock 2 If either or both of these files are present, delete them. 3 Restart the cell. Problem: The primary and secondary servers for my high availability cell are in active mode simultaneously or are unsynchronized. This problem can occur when the primary and secondary servers are running on a network that does not have a reliable connection, if you have started a high availability cell using any of the mcell -i initialization options (for example, -ia, -id or other variants), or if the primary server was started first and terminates before the secondary server is started. Chapter 1 Managing BMC Impact Manager cells 63

60 Problem: The primary and secondary servers for my high availability cell are in active mode simultaneously or are Possible solution: Synchronize the mcdb and xact files of the primary and secondary servers Follow these steps to correct the incompatible states between the primary and secondary servers: 1 If the problem was caused by an unreliable network, resolve the network issue. 2 Shut down both cell servers 3 Copy the mcdb and xact files of the preferred server to the other server. (The preferred server can be either primary or secondary.) 4 Start the secondary cell server. 5 Start the primary cell server. 64 BMC Impact Solutions Infrastructure Management Guide

61 Chapter 2 Managing a Knowledge Base 2 This chapter describes how the Knowledge Base is organized and used in BMC Impact Manager. This chapter presents the following topics: Knowledge Base structure About the unified Event Management and Service Impact Management Knowledge Base Knowledge Base directory structure Knowledge Base index files Managing a Knowledge Base Integrating a unified KB with pre-7.2 cell definitions Creating a new production or test Knowledge Base mcrtcell Importing Knowledge Base information into a cell mkb Compiling a Knowledge Base mccomp Loading a Knowledge Base into a running cell mcontrol Implementing changes to a Knowledge Base Versioning a Knowledge Base Chapter 2 Managing a Knowledge Base 65

62 Knowledge Base structure Knowledge Base structure The following sections explain the structure of the Knowledge Base (KB) and its directories. About the unified Event Management and Service Impact Management Knowledge Base For an overview of the unified template structure of the KB, see the BMC Impact Solutions Concepts Guide. NOTE The SIM code of the unified KB is active only if the cell is configured as a SIM cell and the ServiceModelEnabled parameter of the MCELL_HOME/etc/mcell.conf file is set to Yes. For additional information about the mcell.conf parameters, see Appendix B, mcell.conf file parameters. The Event Management-only KB, stored under MCELL_HOME/etc/default/EM/kb, remains for backward compatibility with versions of the mcrtcell CLI older than version It contains the KB elements used by Event Management to process events. When you create or install a new cell using the mcrtcell command, you always create or install a unified SIM KB in the newly-created cell s KB directory path: MCELL_HOME/etc/CellName/kb. Modifications to the KB in the CellName/kb directory apply to the CellName cell only. If you modify the template KB in either MCELL_HOME\etc\default\SIM or MCELL_HOME\etc\default\EM any cell that you install or create will include those modifications. Knowledge Base directory structure The Knowledge Base uses a defined directory structure to organize its files and executables. The Knowledge Base directories are in the following locations: The Knowledge Base used by the cell during runtime is located in %MCELL_HOME%\etc\CellName\kb on Windows platforms and in $MCELL_HOME/etc/CellName/kb on UNIX platforms. 66 BMC Impact Solutions Infrastructure Management Guide

63 Knowledge Base directory structure The template Knowledge Base resides in the MCELL_HOME\etc\default\SIM or MCELL_HOME\etc\default\EM directory. The Knowledge Base available (EM only or both EM and SIM) will depend on the type specified when the cell was created. Cells are created during installation of a BMC Impact Manager instance or by using the mcrtcell command. For information about this command, see mcrtcell Creating a new cell on page 231. NOTE The environment variables created during installation that define paths to BMC Impact Manager configuration files and executables are listed in the BMC Impact Solutions Installation Guide. Figure 10 lists the directory structure for a Knowledge Base. Figure 10 kb \bin \A \h1 \l2 \p4 \s5 \w4 \classes \collectors \data \lib \records \rules Knowledge Base directory structure In the Knowledge Base, each subdirectory is labeled to indicate the type of files or programs it stores, as listed in Table 15 on page 68. Chapter 2 Managing a Knowledge Base 67

64 Knowledge Base directory structure Table 15 Knowledge Base subdirectories (part 1 of 2) Knowledge Base subdirectory Description bin stores the external scripts that can execute during rule processing and actions that can be run from BMC Impact Explorer The bin directory organizes the scripts and programs in subdirectories specific to the appropriate operating system, as follows: A independent, all UNIX, or non-windows h1 HP-UX l2 Linux p4 AIX s5 Solaris w4 Windows classes The.load file in the bin directory specifies the order in which external scripts or programs are presented to clients. Actions are defined in.mrl files. There is one default file,.load, in the bin directory. Actions and their syntax are described in the BMC Impact Solutions Event Management Guide. stores event class, data class, and interface definitions Classes are stored in.baroc files. The.load file in the classes directory specifies the order in which classes are loaded. Parent classes must be loaded prior to child classes. collectors data lib Event and data classes are described in the BMC Impact Solutions Knowledge Base Development Reference Guide. stores collector rule definitions Collector definitions are used to organize the event lists that are viewed in the BMC Impact Explorer console. Collector rules are defined in.mrl files. Collectors and their syntax are described in BMC Impact Solutions Event Management Guide. instances of dynamic data stored in files that are loaded when the cell is initialized Dynamic data instances are stored in.baroc files. The.load file indicates the order in which the files are loaded into the cell. After the values are loaded into the cell any changes are maintained in the mcell.db. Dynamic data objects and their syntax are described in the BMC Impact Solutions Knowledge Base Development Reference Guide and in the BMC Impact Solutions Event Management Guide. stores primitives and functions used in the Knowledge Base For example, the SIM Knowledge Base contains the following files that cannot be modified: sim.wic contains the compiled implementation of primitives and functions that are loaded by the cell at startup sim_decl.wic contains the compiled definitions for primitives and functions; it is loaded by the compiler to compile rules that reference SIM primitives For more information about functions and primitives, see the BMC Impact Solutions Knowledge Base Development Reference Guide. 68 BMC Impact Solutions Infrastructure Management Guide

65 Knowledge Base directory structure Table 15 Knowledge Base subdirectories (part 2of 2) Knowledge Base subdirectory Description records stores global record definitions, which store dynamic information across all rule phases rules A global record stores persistent dynamic information in a.baroc file. Many rule processing phases use global records for retrieving dynamic information. The.load file indicates the order in which the files are loaded into the cell. The default copy of record definitions is stored in baroc files in the records directory. After the values are loaded they are maintained in the mcell.db. Dynamic data objects and their syntax are described in the BMC Impact Solutions Knowledge Base Development Reference Guide and in the BMC Impact Solutions Event Management Guide. stores the rule definitions for the Knowledge Base The source for rule definitions are the files with an.mrl extension. The compiled versions of rules are contained in files with the.wic or.pkg extension. The.load file indicates the order in which the rules are loaded into the cell. Rules and their syntax are described in the BMC Impact Solutions Knowledge Base Development Reference Guide and in the BMC Impact Solutions Event Management Guide. Table 16 lists the file extensions and directory location for the each of the components contained in a KB. Table 16 Knowledge Base file extensions and directories Component File extension Directory event classes.baroc kb\classes data classes.baroc kb\classes data instances.baroc kb\data global records.baroc kb\records rules.mrl kb\rules collectors.mrl kb\collector action executables.mrl kb\bin service model class definitions.baroc kb\classes interface classes.baroc kb\classes scripts and programs not applicable kb\bin\platform Chapter 2 Managing a Knowledge Base 69

66 Knowledge Base index files Knowledge Base index files The following files are included with the installation and are necessary for the Knowledge Base to run properly: manifest.kb serves as an index file for the listed directories that compose the Knowledge Base during compilation. This file is located in %MCELL_HOME%\etc\CellName\kb on Windows platforms and in $MCELL_HOME/etc/CellName/kb on UNIX platforms..load serves as an index file for the individual files contained in the corresponding subdirectory of the Knowledge Base directory structure. Load files are included in each subdirectory to determine load order for that particular directory. Files types within the.load file do not have extensions..loadwic Before the compilation of the Knowledge Base, rules and collectors are created in.mrl files and are included in the.load files. After compilation, rule and collector files are stored in.wic files and a.loadwic file is created for the KB to use. The.wic files are machine-readable only. Managing a Knowledge Base To manage a Knowledge Base, you must perform several tasks by using the BMC Impact Manager command-line interface (CLI). This section briefly describes these tasks; for more information about syntax and options available for the CLI commands, see Appendix A, BMC SIM and EM CLI Reference. NOTE To protect the format of the default Knowledge Base, back it up prior to making any modifications. An adequate backup includes all directories and files in the kb directory or the directory where the changes occur. You can also use source-control programs such as CVS or Subversion to keep track of changes to the KB. Source control allows you to revert to older versions of the KB and to examine changes. Integrating a unified KB with pre-7.2 cell definitions In version , the unified Knowledge Base was introduced. You can integrate your cell definitions from cells older than version with the unified KB of the current version of the cell. 70 BMC Impact Solutions Infrastructure Management Guide

67 Creating a new production or test Knowledge Base mcrtcell 1 Create a new cell using the mcrtcell CLI with either the -ae or -as option. 2 Copy the modifications or extensions you ve made in old cell s KB to the new cell s KB. To do so, you can manually edit the files or use your specific utilities. 3 Recompile the KB, and restart the cell. Creating a new production or test Knowledge Base mcrtcell Use the mcrtcell command to create a new production or test cell and Knowledge Base. The mcrtcell command can be run only on the local computer where the cell is being created. For more information about syntax and options available with mcrtcell, see Appendix A, BMC SIM and EM CLI Reference. Importing Knowledge Base information into a cell mkb You can use the mkb command to import an existing Knowledge Base. You can also use this command to import files containing definitions for event classes, interfaces, global records, data classes, collectors, or rules from an existing Knowledge Base. For more information about syntax and options available with mkb, see Appendix A, BMC SIM and EM CLI Reference. NOTE To use the mkb command to manipulate an existing KB, you must use the -f parameter to define the path to the manifest.kb file and specify the action that the mkb command should execute. Compiling a Knowledge Base mccomp Each time you change, add, or delete actions, classes, collectors, or rules, you must compile the KB. The cell recognizes changes to the KB only when the cell is restarted. Use the mccomp command to compile the Knowledge Base. The mccomp command parses event, data class and global records, and compiles the rules. For more information about syntax and options available with mccomp, see Appendix A, BMC SIM and EM CLI Reference. Chapter 2 Managing a Knowledge Base 71

68 Loading a Knowledge Base into a running cell mcontrol Effects of compiling a Knowledge Base with tracing enabled If you enable tracing by using the -t option when compiling a KB and if TraceRuleToXact=Yes in mcell.conf, an event can be tracked in the transaction log, an.xact file, as it progresses through the rule execution. Entries in the log file related to rule tracing are include a TRCX header. However, deploying a KB compiled with the -t option can degrade performance by as much as 50 percent. BMC recommends that you do not use the -t option to compile the production KB. NOTE The TraceRuleLevel parameter in the mcell.conf file must be set to 2 for rules tracing to occur. Loading a Knowledge Base into a running cell mcontrol You must load a KB on a running cell each time that you edit collectors. Use the mcontrol reload kb command to reload the Knowledge Base while the cell is still running. For more information about the mcontrol command, see Appendix A, BMC SIM and EM CLI Reference.. Implementing changes to a Knowledge Base You must stop and start the cell to implement any changes to a cell s KB. For instructions on stopping and starting a cell, see the BMC Impact Solutions Getting Started Guide. Versioning a Knowledge Base KB versioning enables you to determine which KB and which version of the KB is loaded in a cell. You can implement version information for KB source files For each KB source file that you specify, information about the source file is provided and the version of the compiler that was used to compile it. Logical KB modules Version information is provided for each logical module that you identify in the KB. 72 BMC Impact Solutions Infrastructure Management Guide

69 Versioning a Knowledge Base A logical KB module is a collection of class definitions and rules that perform a specific task within the KB. For instance, all class definitions and rules that are related to Help Desk events could be called the HelpDesk KB module. A single KB can contain multiple such logical modules. The class definitions and rules that are not associated to a specific KB module are considered to be part of the global, unnamed KB module. If desired, you can make rules behave differently depending on the version of specific KB modules. This can be useful in patches, for example. Enabling KB versioning To enable versioning, you must create logical modules in the KB. To identify the files for a particular module, add annotation to the KB source files, using the following [ ModuleName, ] VersionID ) Variable ModuleName VersionID Description specifies the name of the module to which the current file belongs To indicate version information for the global module, either use the empty string as ModuleName or omit ModuleName. specifies the version (v.r.mm) For example, WARNING annotations for the same module will result in a compilation error. This also applies to a global version; only one annotation without a module name is allowed in a KB. The mccomp command compiles annotations into the KB object files and includes the following information about each source file in the KB: release number of the compiler used to compile the file build number of the compiler used to compile the file build date of the compiler used to compile the file source file name source file size in bytes source file checksum Chapter 2 Managing a Knowledge Base 73

70 Retrieving KB version information in rules KB versioning HelpDesk, '1.2.01' ) This example specifies that the KB contains a logical module called HelpDesk, and that its version is Retrieving KB version information in rules You can retrieve KB module version information in a rule by using the kbversion primitive. For information about the kbversion primitive, see the BMC Impact Solutions Knowledge Base Development Reference Guide. Retrieving KB version information by using a command mgetinfo You use the mgetinfo command with the kbmodules and kbsources arguments to retrieve version information from the cell's loaded KB. mgetinfo -n cellname [-v] kbmodules kbsources Argument kbmodules kbsources Returned results list of KB modules with version information list of KB source files with compiler version information The information is displayed in raw format. You can use the -v switch to obtain the information in a more readable format. Figure 11 on page 75 shows a portion of the information returned from the kbsources argument. 74 BMC Impact Solutions Infrastructure Management Guide

71 Retrieving KB version information by using a command mgetinfo Figure 11 Output from mgetinfo kbsources argument BMC Impact InfoRetrieval (Build Jan-2009) Copyright BMC Software, Inc. as an unpublished work. All rights reserved Jan-2009 collectors/self_collector.mrl Jan-2009 collectors/mc_bystatus_collectors.mrl Jan-2009 collectors/mc_bylocation_collectors.mrl Jan-2009 collectors/mc_evr_collectors.mrl Jan-2009 collectors/bii4p_collectors.mrl Jan-2009 collectors/mc_sm_collectors.mrl Jan-2009 collectors/catchall_collector.mrl Jan-2009 rules/mc_startup.mrl Jan-2009 rules/im_internal.mrl Jan-2009 rules/mc_intevt.mrl Jan-2009 rules/mc_mccs.mrl Jan-2009 rules/ips.mrl Jan-2009 rules/mc_sm_start.mrl Jan-2009 rules/mc_sm_associate.mrl Jan-2009 rules/mc_sm_maintenance.mrl Jan-2009 rules/mc_sm_elect.mrl Jan-2009 rules/mc_sm_attach.mrl Jan-2009 rules/mc_sm_shadow.mrl Jan-2009 rules/mc_sm_slm.mrl Jan-2009 rules/bii4p.mrl Jan Jan-2009 bin/mc_actions.mrl Jan-2009 bin/im_operations.mrl Jan-2009 bin/sim_operations.mrl Chapter 2 Managing a Knowledge Base 75

72 Retrieving KB version information by using a command mgetinfo 76 BMC Impact Solutions Infrastructure Management Guide

73 Chapter 3 Managing the BMC Impact 3 Administration server This chapter presents the following topics: Configuration files Command line interface Impact Administration cell How to configure BMC Impact Administration server files Guidelines for manual edits Users, groups, roles, and permissions Defining permissions Full Access role permissions Adding customized role/permission mappings File-based authentication: updating user information Adding role names to the cell s KB definition files Receiving synchronized data from the BMC Portal Synchronizing cell information with BMC Atrium CMDB Updating cell information Editing logging properties for IAS Defining client logging for the iadmin script Customizing colors for severities, statuses, and priorities IAS Status Monitoring Customizing the IAS thread pool handling IAS Clients Defining standalone, primary, and secondary BMC Impact Administration servers Defining a failover configuration for the Impact Administration cell Transaction and trace logs Advanced tasks Configuring BMC Impact Administration server to support remote actions Configuring Lightweight Directory Access Protocol for BMC Impact Administration server Troubleshooting Problem: Cell_info.list synchronization error during manual configuration of an IAS failover Chapter 3 Managing the BMC Impact Administration server 77

74 Configuration files Configuration files End users can configure the following IAS file listed in Table 17. These files are located under the IMPACT_SOLUTIONS_HOME/server/conf directory. Table 17 IAS file ias.properties Configurable IAS files user_definitions.xml ldap_configuration.xml role_permissions.xml group_roles.xml cell_info.list cmdb.properties server_logging.properties client_logging.properties color.properties credential_repository.xml ldap_configuration_query.xml default_role_permissions.xml Description contains required and optional configuration parameters for the IAS. This file is loaded whenever IAS starts or restarts. defines user information for file-based authentication defines LDAP server information for LDAP authentication enables you to add customized role/permission mappings contains the group/role mappings contains identifying information about each cell that is connected to the IAS specifies information for the IAS and BMC Atrium CMDB connection defines the logging properties for the server defines the logging properties for the client when you use the iadmin command defines different color properties for severity, status, and priority stores the authentication credentials used for remote execution actions defines LDAP server information used by IAS query option tlq defines the view and edit permissions for each tab view and menu option in BMC IX NOTE The full path to the server directory under IMPACT_SOLUTIONS_HOME is /opt/bmc/impact/server on UNIX and drive letter:\program Files\BMC Software\Impact\server on MS Windows. Command line interface The IAS uses an iadmin command to launch the file management options. The iadmin script or command is located under the IMPACT_SOLUTIONS_HOME/server/bin directory. 78 BMC Impact Solutions Infrastructure Management Guide

75 Command line interface You can use the iadmin command to manage the following configuration files: user_definitions.xml group_roles.xml cell_info.list role_permissions.xml credential_repository.xml Remember that you do not have to restart IAS to initialize your changes if you use the iadmin command. You can execute the iadmin command against an IAS on the local system. You cannot execute the iadmin command against an IAS on a remote system. The iadmin options are summarized below in Table 18 on page 79. You can display these options from the command line by entering iadmin -h. Table 18 iadmin options (part 1 of 2) Option -ac -mc -dc -lc -aru -mru -dru -lru -ar -dr -lr -mr -ag -dg -lg -mg -acr -mcr -dcr -lcr -cp Description add a cell to the cell_info.list file and register the cell with the BMC Impact Administration Server modify a cell delete a cell list connected cells add a new user modify the user group or groups to which an existing user belongs delete an existing user list all the users add a new mapping between a role and permissions delete an existing role/permissions mapping list all the roles modify the mapping between a role and a list of permissions add a new mapping between a group and a list of roles delete a group/role mapping for a specified group list all the groups modify the mapping between a group and a list of roles add a credential record to the credential_repository.xml modify a credential record delete a credential record list all credential records change the current password of an existing user. Requires that you enter the current password Chapter 3 Managing the BMC Impact Administration server 79

76 Impact Administration cell Table 18 iadmin options (part 2of 2) Option -rp -reinit [fullsync actions] -sync -tlq Description reset the password of an existing user. In this option, you enter the new password only. You do not enter the current password in a high availability setup, -reinit restarts the primary or secondary server with the latest configuration data. Use the [fullsync] option on the secondary server to copy the primary server s configuration to it and restart it with the new configuration. The [actions] option can reload the newly created remote actions defined in the.xml files in an high availability setup, synchronizes the secondary server before the expected synchronization interval returns the time required to execute an LDAP query. In addition, you choose to return a list of LDAP groups or to authenticate the LDAP user The CLI considers the LDAP configuration specified in the ldap_configuration_query.xml file in IAS. There is no need to restart the IAS after making changes to the ldap_configuration_query.xml file NOTE Refer to the BMC Impact Solutions Event Management Guide for a description of the -acr, -mcr, - dcr, -lcr, and [actions] options in its discussion of remote execution. When using iadmin to manage files, remember to: enclose values within quotation marks if they contain spaces omit spaces in lists enclose password values within double quotation marks For example, if the password string is $able_baker, then enclose it within double quotation marks in the iadmin command string, as in the following excerpt: password= $able_baker On Windows, execute the iadmin command from any path On Unix, set $MCELL_HOME environment using the command./etc/mcell/setup_env.sh, then run the iadmin command from any path Impact Administration cell The default mcell.dir file of the IAC is as follows: cell Admin mc hostname:1827 cell IAC mc hostname: BMC Impact Solutions Infrastructure Management Guide

77 How to configure BMC Impact Administration server files Admin is the default name of the Impact Administration cell. The default name is provided at installation. It is the same name as the IAS instance name. Its default port number is You can change the default name of the IAC and the IAS instance name simultaneously during installation as an installation option. After installation, you can change the name of the IAC independent of the IAS instance name. You can change the default port number as long as the port number that you assign does not conflict with any other. IAC is the alias name that other cells use to propagate events to the Impact Administration cell. Each SIM or BEM cell that registers with an Impact Administration cell and a Master IAS should have an IAC entry in its mcell.dir file along with its own cell name, as in the following example: cell cellname mc hostname:1828 cell IAC mc hostname:1827 How to configure BMC Impact Administration server files This section describes the following configuration tasks: Defining group roles and permissions Adding Impact Manager cells to the cell_info list Defining standalone, primary, and secondary BMC Impact Administration servers Defining HA configuration for Impact Administration cells Synchronizing cell information with BMC Atrium CMDB Receiving synchronized data from the BMC Portal Defining server-side logging levels Defining client-side logging levels Customizing the GUI color scheme for status, priority, and severity levels Setting LDAP authentication Configuring IAS to support remote actions Checking the time required to execute an LDAP query Depending on the goal of the task, you may need to edit multiple files. Chapter 3 Managing the BMC Impact Administration server 81

78 Guidelines for manual edits Guidelines for manual edits Use the iadmin script or command whenever possible. If you have to manually edit a file, follow these general steps: 1 Open the file in a text editor. 2 Make the changes in the proper format. 3 Save the file without changing its extension or file path. 4 Restart IAS. NOTE When manually editing files to enable a high availability configuration, you must follow the special guidelines outlined in the topic Defining a failover configuration for the Impact Administration cell on page 105. Users, groups, roles, and permissions IAS supports a hierarchical classification scheme that defines the relation among permissions that are assigned to groups, which, in turn, are assigned roles. All of these elements are contained in user definitions. Figure 12 outlines this relationship: Figure 12Relation among users, groups, roles, and permissions You can create new users, groups, and roles. You cannot, however, create new permissions. You can only select from a predefined list of existing permissions. 82 BMC Impact Solutions Infrastructure Management Guide

79 Defining permissions Defining permissions The default_role_permissions.xml file defines the view and edit permissions for each tab view and menu option in BMC IX. For each role, it lists the permissions in a comma-separated string as shown in the following extract for the Full Access role:... <properties> <entry key="full Access">administration_tab_view_and_access, events_tab_view_and_access,services_tab_view_and_access, services_tab_access_component_event_list, events_tab_edit_drill_down,events_tab_edit_user_event_filter, events_tab_edit_user_slot_order,... </entry>... </properties> WARNING Do not modify the default_role_permissions.xml file. Use the role_permissions.xml file instead. Any permission that you add or modify must be taken from the predefined default_role_permissions.xml file. Table 19 on page 83 matches the default mapping of roles/permissions to BMC IX functionality. Table 19 BMC Impact Explorer user group mapping to functionality (part 1 of 4) Permission (P) or Right (R) Choices Full Access Service Administrator Function BMC Impact Explorer R Dashboards-Create, Edit X X X update, and delete all profiles R Dashboards-Create Edit X X X X X and delete own profiles only R Dashboards (SIEM) View X X X X X X Service Manager, Senior Service Manager Service Operator, Senior Service Operator Read Only Admins Operators Supervisors Chapter 3 Managing the BMC Impact Administration server 83

80 Defining permissions Table 19 BMC Impact Explorer user group mapping to functionality (part 2of 4) Permission (P) or Right (R) Function Choices Full Access Service Administrator R Dashboards (CIEM) View X X X X X X X X X X R Events tab View X X X X X X X X X X R Configuration Edit Edit X X X X X X X X X Relationship View R Configuration Edit Edit X X X X X X X X X Personal Filters R Configuration Edit Edit X X X X X X X X X Personal Attribute (Slot) Orders R Configuration Edit Edit X X X X X X X Personal MetaCollectors R Configuration Edit Edit X X X X X X Global Event Filters R Configuration Edit Edit X X X X X X Global Attribute (Slot) Orders R Configuration Edit Edit X X X X X X X X X X Impact Manager Group on Impact Manager Configuration window R Events tab-show Edit X X X Impact Administration cell R Events tab Jump Edit X X X X X from an Event to Its Services Impacted View R Events tab Reopen Events Edit X X X X Service Manager, Senior Service Manager Service Operator, Senior Service Operator Read Only Admins Operators Supervisors 84 BMC Impact Solutions Infrastructure Management Guide

81 Defining permissions Table 19 BMC Impact Explorer user group mapping to functionality (part 3 of 4) Permission (P) or Right (R) Function Choices Full Access Service Administrator R Events tab Event Edit X X X X Operation Supervisor Privileges (for example, close events owned by someone else) R Events tab Assign Edit X X X X Events R Events tab Add Edit X X X X X Image View R Events tab Delete Edit X X X X X Image View R Services tab View X X X X X X R Services tab Search Edit X X X X X for Service Components R Services tab-create Edit X X X X and delete components R Services tab Event View X X X X X X List View of a Service Component R Services tab Edit My Edit X X X X X Services Navigation Tree R Services tab-create, Edit X X X X X Edit, Delete Relationship between components R Services tab Set or Remove Manual Status (of a component) Action Edit X X X X X Service Manager, Senior Service Manager Service Operator, Senior Service Operator Read Only Admins Operators Supervisors Chapter 3 Managing the BMC Impact Administration server 85

82 Full Access role permissions Table 19 BMC Impact Explorer user group mapping to functionality (part 4 of 4) Permission (P) or Right (R) Choices Full Access Service Administrator Function R Services tab Set or Edit X X X X X Clear Maintenance Mode (of a Component) Action R Administration tab View X X X X X R Timeframes Edit X X X X X R Administration tab: Edit X X X all actions R Infrastructure Edit X X X Management subtab R Infrastructure Edit X X X Management subtab: all actions R Alias Formula Editor Edit X X X R Remote Actions: Edit X X X Create remote actions R Send Events to Cell Edit X X X R Delete Events to Cell Edit X X X Service Manager, Senior Service Manager Service Operator, Senior Service Operator Read Only Admins Operators Supervisors Full Access role permissions Members of the Full Access user group can view, edit, and create all components and relationships, including the objects and relationships that were created by other users. Service Administrators, Service Managers - Senior, and Service Managers user groups can edit components and their associated relationships only if they already have write permission on the objects. If the user group member who creates a component does not specify otherwise, then the Read Users and Write Users slots of the component are populated by the user group of the BMC IX login account. To illustrate, if a user account belonging to the Service Administrators group creates a component, then by default its Read Users and Write Users slots are populated by the user group Service Administrators. 86 BMC Impact Solutions Infrastructure Management Guide

83 Adding customized role/permission mappings Adding customized role/permission mappings Use the role_permissions.xml file to add customized role/permission mappings. The com.bmc.sms.ixs.role.permission.mapping property of the ias.properties file specifies this default file for containing customized role/permission mappings, as shown in the following excerpt: com.bmc.sms.ixs.role.permission.mapping=role_permissions.xml If you create a separate.xml file to contain your customized role/permission mappings, you must specify its name in the com.bmc.sms.ixs.role.permission.mapping property of the ias.properties file. Then you must restart IAS to initialize the change. The user-defined.xml file does not override the default file. Its individual entries override matching ones in the default file. Any entries in the default file that are not overridden by matching ones in the user-defined file remain valid. When you use the iadmin script to add, modify, or delete a role/permission mapping, the change is saved to the role/permissions file specified by the com.bmc.sms.ixs.role.permission.mapping property. To add a new role/mapping permission From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -ar option, as in the following example: iadmin -ar role= Test :permissions= services_tab_delete_component To modify an existing role/mapping permission You can modify the permissions associated with a role in a user-defined roles/permissions file. The modified entry is saved to the user-defined roles/permissions file, which overrides any corresponding role entry in the default file. From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -mr option, as in the following example: iadmin -mr role=test:permissions= services_tab_view_and_access Chapter 3 Managing the BMC Impact Administration server 87

84 Defining group roles To delete an existing role/mapping permission You can delete an existing role in a user-defined roles/permissions file. NOTE If the role to be deleted only exists in the default file, then an entry is added to the userdefined file. The entry contains the role name only, without any permissions associated with it. Because the user-defined entry overrides the default one, the role is effectively deleted. From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -dr option, as in the following example: iadmin -dr role=test The entry role=test is written to the user-defined file and effectively overrides any identical role in the default file. To list roles defined in roles/permissions mapping files You can list all roles defined in both the default and in the user-defined roles/permissions mapping files. From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -lr option, as in the following example: iadmin -lr Defining group roles The ias.properties file specifies the default group roles, which are identified in the group_roles.xml file: com.bmc.sms.ixs.group.role.mapping=group_roles.xml Default groups and user roles IAS provides the following default groups and user roles, both of which are listed in Table 20. You can view these roles in the group_roles.xml file. Refer to Table 19 on page 83 for a complete listing of access permissions for group and role combination. 88 BMC Impact Solutions Infrastructure Management Guide

85 Defining group roles Table 20 Groups and roles Group Full Access Read Only Service Administrators Service Managers Service Managers - Senior Service Operators Service Operators - Senior Admins Operators Supervisors Role Full Access. Has write access to all features Read Only. Has read-only access Service Administrators. Has write access to all features Service Managers Service Managers - Senior Service Operators Senior Service Operator Full Access, Service Administrators Service Operators, Senior Service Operators Service Manager, Senior Service Managers NOTE If you are using Lightweight Directory Access Protocol (LDAP) authentication, you must map your LDAP user groups to the IAS roles defined in the group_roles.xml file. See Configuring Lightweight Directory Access Protocol for BMC Impact Administration server on page 109 for more information. You can update user groups and roles and create new ones by editing the group_roles.xml file, shown below: <!DOCTYPE properties SYSTEM " <!--Each entry's key is the Group name and the value is the list of Roles assigned to that group--> <properties> <entry key="full Access">Full Access</entry> <entry key="read Only">Read Only</entry> <entry key="service Administrators">Service Administrators</entry> <entry key="service Managers">Service Managers</entry> <entry key="service Managers - Senior">Service Managers - Senior</entry> <entry key="service Operators">Service Operators</entry> <entry key="service Operators - Senior">Service Operators - Senior</entry> <entry key="admins">full Access,Service Administrators</entry> <entry key="operators">service Operators,Service Operators - Senior</entry> <entry key="supervisors">service Managers - Senior,Service Operators - Senior</entry> </properties> Chapter 3 Managing the BMC Impact Administration server 89

86 Defining group roles To add a new group with mapping roles NOTE If you re adding a new role to the group, you must first create the role and add permissions to it using the iadmin -ar option before you create the group. See To add a new role/mapping permission on page 87. From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -ag option, as in the following example: iadmin -ag group= NewGroup :roles= Role To modify an existing group and/or mapping roles From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -mg option, as in the following example: iadmin -mg group= Service Administrators :roles= Service Administrators, Service Operators Any roles that you add to a group must have already been defined in the group_roles.xml file. To delete an existing group From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -dg option, as in the following example: iadmin -dg group= Service Operators You do not specify a role. To list groups in the group_roles.xml file From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -lg option, as in the following example: iadmin -lg 90 BMC Impact Solutions Infrastructure Management Guide

87 File-based authentication: updating user information To update user groups and roles (file editor) 1 Open the group_roles.xml file in an editor. 2 Update or delete the existing entries, or add a new entry where key is the name of the group the values inside the <entry></entry> element are the roles 3 Save and close the group_roles.xml file. 4 Restart the IAS to initialize the changes. File-based authentication: updating user information You choose file-based authentication in test environments or in small production environments. Using file-based authentication, you can manage users of the BMC EM and SIM products independent of your corporate environment. To enable file-based authentication 1 In the ias.properties file, ensure that the com.bmc.sms.ixs.enable.file.login parameter is set equal to true. 2 In the user_definitions.xml file, define the user s attributes. These include user id, password, group names and their descriptions, and so forth. You can use the iadmin command to update user information in the user_definitions.xml if you have enabled file-based authentication. You can add, modify, or delete users, and you can modify the password of an existing user. The user_definitions.xml file defines a user ID, password, and group of a specified user, as in the default example below: <?xml version="1.0" encoding="utf-8"?> <userlist xmlns="urn:bmc:schemas:impact" xmlns:xsi=" xsi:schemalocation="urn:bmc:schemas:impact user_definitions.xsd "> <user userid="user"> <password encrypted="false">user</password> <grouplist>full Access</groupList> <description>this is optional</description> </user> </userlist> Chapter 3 Managing the BMC Impact Administration server 91

88 File-based authentication: updating user information To add a user entry When adding a user entry, enter a plain-text password with the <password encrypted> element set equal to false. When the file is initialized, the password becomes encrypted and the <password encrypted> element is changed to true. From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -aru option, as in the following example: iadmin -aru loginid=qa:password= qa :usergroups= Full Access :description= Full Access User Group NOTE On UNIX platforms, execute the iadmin command that contains a password value without the bash shell. To modify a user group of an existing user From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -mru option, as in the following example: iadmin -mru loginid=qa:usergroups= Read Only To delete an existing user From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -dru option, as in the following example: iadmin -dru loginid=qa To update the current password of an existing user From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -cp option, as in the following example: iadmin -cp loginid=qa:oldpassword= qa :newpassword= bsm To reset the current password of an existing user When you reset a password, you do not specify the current password, only the new password. 92 BMC Impact Solutions Infrastructure Management Guide

89 Adding role names to the cell s KB definition files From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -rp option, as in the following example: iadmin -rp loginid=joeuser:newpassword= bsm To list all users in the user_definitions file From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -lru option, as in the following example: iadmin -lru To change the current admin password In the ias.properties file, type the new password in plain text format, as shown in the following example. # admin password used internally for different components (such as BIP) talking to IAS com.bmc.sms.ixs.admin.password=e1kyemjvrpcniw52m4m2tscjd3yziba1jymod jojtruniw52m4m2tscjdnyziba1jymodjojtruniw52m4m2tq== (encrypted) OR com.bmc.sms.ixs.admin.password=nwadmpwd23 Adding role names to the cell s KB definition files After adding a new role name, you must add this role name to the cell s KB definition files for the role to be effective. See To add the role name to the cell s KB definition files on page 113 for more information. Receiving synchronized data from the BMC Portal BMC Portal has a task named Synchronize Users with IAS. This a manual synchronization feature that pushes data one way from the BMC Portal to IAS. The synchronization is available in Standard and BMC Atrium installations. Chapter 3 Managing the BMC Impact Administration server 93

90 Receiving synchronized data from the BMC Portal The BMC Portal connects with IAS through IAS s administrative account. The default password is IAS$Admin$. (There is no user name associated with administrative access.) During synchronization, only BMC Portal user groups that have defined permissions in BMC IX are exported. You can check for the permissions in the User Groups task off of the Configure tab in the BMC Portal. Look for permissions that begin Impact Explorer. BMC Portal groups are mapped to IAS roles with the same name. When a BMC Portal group is exported to IAS, a new role is created in IAS with the same name. To illustrate, if the BMC Portal group abc is exported to IAS, a role/permission mapping is created in IAS for abc and all the permissions that abc maps to in the BMC Portal. Then IAS creates a group/role mapping abc/abc. User passwords are not exported, but are set to the default value user. Any cells that are added to the BMC Portal are registered with IAS. For the Atrium installation scenario, BMC Atrium CMDB parameters are not synchronized with either the BMC Portal or IAS. They need to be added manually. In LDAP authentication, the IAS and BMC Portal connect separately to an LDAP server. The mappings of BMC Portal groups to LDAP group mappings are sent to IAS as group to role mappings. The BMC Portal uses the fully qualified distinguished name for an LDAP group (for example, ldapg1.bmc.com) while the IAS uses the common name (ldapg1). For example, if the BMC Portal group abc maps to several LDAP groups for example, ldapg1.bmc.com and ldapg2.bmc.com then IAS creates the following group/role mappings: abc/abc, ldapg1/abc, and ldapg2/abc. To set up LDAP authentication in IAS, see Configuring Lightweight Directory Access Protocol for BMC Impact Administration server on page BMC Impact Solutions Infrastructure Management Guide

91 Synchronizing cell information with BMC Atrium CMDB Synchronizing cell information with BMC Atrium CMDB You can synchronize your cell information with the BMC Atrium CMDB by modifying the cmdb.properties, an excerpt of which is shown below:... # "true" if this IAS will synchronize with the CMDB server. com.bmc.sms.ixs.cmdb.enable.sync=false # host name for AR server com.bmc.sms.ixs.cmdb.host.name=localhost # port number for AR server com.bmc.sms.ixs.cmdb.port.number=0 # user id for AR server com.bmc.sms.ixs.cmdb.user.id=demo # password for AR server com.bmc.sms.ixs.cmdb.password= To synchronize with the BMC Atrium CMDB 1 Change the com.bmc.sms.ixs.cmdb.enable.sync property to true. 2 Enter the fully qualified domain name or the IP address of the host system where the AR Server resides. 3 Enter the port number of the AR Server. If the AR Server is using portmapper, then enter 0. 4 Enter the AR Server user Id that you use for accessing the BMC Atrium CMDB. 5 Enter the password in plain text. When IAS restarts, it encrypts the password and displays the encryption in the file. 6 Restart the IAS. Chapter 3 Managing the BMC Impact Administration server 95

92 Updating cell information Updating cell information You can add cells to the IAS, modify cells, delete cells from the IAS, and list the cells that are currently registered with the IAS. This cell information is stored in the cell_info.list, an example of which is shown below: cell test mc test.company.com:1828 Production * cell.admin IAC mc localhost:1828 Production * cell.sim qa mc qa.company.com:1828 qa.company.com:1888 Test "Full Access, Read Only" Each cell entry contains the following information: Table 21 Cell entry format in cell_info.list Entry Description cell required. Each entry must begin with cell. The cell type is appended after cell, with a period separating cell and the type. The available cell types are SIM, BEM, and Admin. IAS retrieves the type from the cell and appends to the entry. name matches the name in the mcell.dir file of the cell server. key The default value is mc. primaryhost system where the cell resides. It can be an unqualified or fully qualified host name, or an IP address. primaryport primary port number of the cell between failoverhost optional. If this is an HA pair, then enter the system name where the secondary cell resides. failoverport optional. If this is an HA pair, then enter the failover port number between that the secondary cell uses. environment Production or Test. usergroups user group or groups who can access this cell. If all groups can access the cell, enter an asterisk. Otherwise enter the user group name, separating multiple groups with commas. If the group name contains a space, use double quotation marks to enclose the entire name. To add/register a cell From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -ac option, as in the following example: iadmin -ac name=testcell:key=mc:primaryhost=moondog:primaryport=1828: failoverhost=suncat:failoverport=1828:environment=production:usergroups=* 96 BMC Impact Solutions Infrastructure Management Guide

93 Updating cell information The cell information is added to the cell_info.list. It is also added to the BMC Atrium CMDB if the cell is synchronized with BMC Atrium CMDB as defined in the cmdb.properties. To ensure that the cell is registered with the IAS, be sure that its mcell.dir file contains the IAC entry, as in the following example: cell IAC mc mycomputer.adprod.bmc.com:1827 The IAC entry enables event propagation between the cell and the Admin cell that is part of the IAS. To modify a cell From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -mc option. After you specify the cell name, you only to need to include the options that you are changing, as in the following example: iadmin -mc name=testcell:failoverhost=null:environment=test In this example, the secondary cell is removed and thus failoverhost is defined by null. The environment is changed from Production to Test. If you were to change the primaryhost or primaryport value, then IAS connects to the cell to retrieve its type. All updates are saved into the cell_info.list and to the BMC Atrium CMDB, if the cell is synchronized with the BMC Atrium CMDB. To delete a cell From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -dc option to delete a cell from the cell_info.list, as in the following example: iadmin -dc name=testcell If the cell is synchronized with the BMC Atrium CMDB, it is removed from the CMDB. To list cells From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -lc option, as in the following example: iadmin -lc Chapter 3 Managing the BMC Impact Administration server 97

94 Editing logging properties for IAS Editing logging properties for IAS IAS generates a default log file, ias<numeral>.log, under the IMPACT_SOLUTIONS_HOME/server/tmp/ias directory. This log file captures diagnostic trace messages generated by the server s activity. You can manually edit the logging level file name and path maximum size of each file number of log files in a cycle This information defined in the server_logging.properties file describes the properties that you would typically modify: Table 22 Server logging properties Property.level java.util.logging.filehandler.pattern java.util.logging.filehandler.limit java.util.logging.filehandler.count Description message levels that the log captures. The default is INFO. The log ignores all levels lower than the specified one. The values range from SEVERE to FINEST. specifies the file name, file path, and the generated numeral that distinguishes the log file cycle. The default pattern /tmp/ias/ias%g.log. the maximum size of each log file in bytes. The default is 5 million bytes (about 5 MB). maximum number of log files in each cycle. The default is 10. After the maximum number of files is reached, a new cycle starts and the new log files override the existing ones in sequence. After you make changes, save the server_logging.properties file, and restart IAS. Defining client logging for the iadmin script You can define the log message level that is directed to the command console when you execute the iadmin script. The default level is SEVERE, meaning that notices of only the most crucial changes are transmitted to the command console. All other notices are omitted. The client log information is defined in the client_logging.properties file. You can manually edit the log level by changing the value of the java.util.logging.consolehandler.level property. All levels below the one you specified are omitted from the client log. After you make changes, save the client_logging.properties file. 98 BMC Impact Solutions Infrastructure Management Guide

95 Customizing colors for severities, statuses, and priorities Customizing colors for severities, statuses, and priorities You can modify the default colors that BMC IX uses in row backgrounds in tables to indicate event severities, service component statuses, and priority computation by changing the hexadecimal numbers that represent the amount of red, green, and blue (RGB) in the color. The default colors are defined in the color.properties file. NOTE These changes to the color properties do not affect the icon colors. You should be consistent when changing the color values of the same parameter. For example, if you change the color for DOWN to indicate event severity, you should make the same change to the DOWN parameter for service component status. Otherwise, if you specify different colors, one color change overrides the other. After you make changes, save the color.properties file, and restart IAS. IAS Status Monitoring IAS Status Monitoring is used for auditing the IAS application at a predefined interval (known as IAS Application Audit Interval). During this audit, the following statistical information is generated: List of clients connected to IAS and the corresponding threads IDs of threads in IAS serving it Threads count (user, daemon) in the IAS application at that instant Peak thread count of the IAS application Memory consumption of the IAS application Other services information (like memory consumed and thread count) running on the machine hosting the IAS application Operating System information This information helps in gathering factual information about the customer environment for IAS and fine tuning IAS. You can define the configuration settings for status monitoring in the ias.properties file. Chapter 3 Managing the BMC Impact Administration server 99

96 Customizing the IAS thread pool handling IAS Clients Table 23 IAS status monitoring properties Property com.bmc.sms.ixs.appauditlogenable com.bmc.sms.ixs.appauditlogfilename com.bmc.sms.ixs.appauditloglimit com.bmc.sms.ixs.appauditlogfilecount com.bmc.sms.ixs.applicationauditinterval Description Used to enable or disable the status monitoring audit log. The supported values are true or false. The default is true. Specifies the log file name and its format. "%g" the generation number to distinguish rotated logs. Specifies an approximate maximum amount to write (in bytes) to any one file. Specifies how many output files to cycle through, that is, the number of files to use. Specifies the audit frequency time interval in minutes. Code examples follow that show sample IAS Status Monitoring configuration parameters. # IAS Status Monitoring Enable com.bmc.sms.ixs.appauditlogenable=true # Status Monitoring Audit File Name com.bmc.sms.ixs.appauditlogfilename=log/ias/ias_app_audit_file#%g.log # Status Monitoring Audit Log Limit com.bmc.sms.ixs.appauditloglimit=50000 # Status Monitoring Audit Log File Count com.bmc.sms.ixs.appauditlogfilecount=10 # Status Monitoring Audit Log Interval com.bmc.sms.ixs.applicationauditinterval=60 Customizing the IAS thread pool handling IAS Clients You can define the configuration parameters for the IASClientThreadManager thread pool in the ias.properties file. Table 24 IAS thread pool properties (part 1 of 2) Property com.bmc.sms.ixs.iasclient.threadmanager.cor e_pool_size com.bmc.sms.ixs.iasclient.threadmanager.ma x_pool_size Description Specifies the Core ThreadPool Size. It indicates the number of threads to keep in the pool even if they are idle (Minimum Thread Pool size). Specifies the Maximum ThreadPool Size. It indicates the maximum number of threads to allow in the thread pool. 100 BMC Impact Solutions Infrastructure Management Guide

97 Defining standalone, primary, and secondary BMC Impact Administration servers Table 24 IAS thread pool properties (part 2 of 2) Property com.bmc.sms.ixs.iasclient.threadmanager.ke ep_alive_time com.bmc.sms.ixs.iasclient.threadmanager.ke ep_alive_time_unit Description Specifies the maximum time that excess idle threads will wait for new tasks before terminating. Excess idle threads occur when the number of idle threads in the thread pool is more than the core pool size. Specifies the time unit for the keepalivetime argument. The possible values are DAYS, HOURS, MINUTES, or SECONDS. NOTE The property com.bmc.sms.ixs.thread.pool.size is not applicable in and 7.2.x, if the patch for thread pool changes is applied. Do not modify the properties com.bmc.sms.ixs.iasclient.threadmanager.keep_alive_time and com.bmc.sms.ixs.iasclient.threadmanager.keep_alive_time_unit as these are sensitive. Code examples follow that show sample IAS ThreadPool configuration parameters. # Core ThreadPool Size com.bmc.sms.ixs.iasclient.threadmanager.core_pool_size=10 # Max ThreadPool Size com.bmc.sms.ixs.iasclient.threadmanager.max_pool_size=50 # Keep Alive Time com.bmc.sms.ixs.iasclient.threadmanager.keep_alive_time=1000 # Keep Alive Time Unit com.bmc.sms.ixs.iasclient.threadmanager.keep_alive_time_unit=seconds Defining standalone, primary, and secondary BMC Impact Administration servers NOTE At installation, you can choose to install and implement a failover configuration for the IAS. If you select to define an failover setup for the Master IAS, the accompanying IAC is also defined as failover automatically. By default the IAS is configured to work in standalone mode. However, after installation, you can choose to implement a failover configuration, in which you define a pair of primary and secondary servers to handle failover situations after which you need to restart both the servers. Chapter 3 Managing the BMC Impact Administration server 101

98 Defining standalone, primary, and secondary BMC Impact Administration servers You must first install another BMC IAS on a second system. Rerun the installation, and make the appropriate Standard or Master IAS selection for the second system. The primary and secondary Impact Administration servers must have the same name. To configure IAS failover manually 1. Edit the ias.properties files as mentioned below: A On the primary IAS, go to the IMPACT_SOLUTIONS_HOME/server/conf/ias.properties file and set the parameters as mentioned below: com.bmc.sms.ixs.server.mode=primary com.bmc.sms.ixs.backup.server=hostname_of_secondary_ias_server:ias_port_number (for example: pun-sms-sun31:3084) Note: you can also use the IP address instead of the host name. com.bmc.sms.ixs.backup.server="ip address of secondary":3084 B On the secondary IAS, go to the IMPACT_SOLUTIONS_HOME/server/conf/ias.properties file and set the parameters as mentioned below: com.bmc.sms.ixs.server.mode=backup com.bmc.sms.ixs.primary.server=hostname:ias_port_number (for example: pun-sms-sun25:3084) Note: you can also use the IP address instead of the host name. com.bmc.sms.ixs.backup.server="ip address of primary": Restart the primary and secondary IASs. NOTE If you define a standalone Master IAS as an HA pair, you must also define its accompanying administration cell as an HA pair. 102 BMC Impact Solutions Infrastructure Management Guide

99 Defining standalone, primary, and secondary BMC Impact Administration servers When you define primary and secondary servers, you also define the synchronization properties for both. The synchronization process updates IAS records and files, such as the following files: user_definitions.xml group_roles.xml role_permissions.xml cmdb.properties cell_info.list During synchronization of failover pairs, data is carried from the primary to the secondary IAS and from the secondary to the primary. Each server of a failover pair has its own ias.properties and logging configuration files. These files are not synchronized. NOTE To enable synchronization between servers, they must be installed on the same type of platform: either all on MS Windows or all on the same UNIX operating system (for example, Solaris to Solaris, Linux to Linux). When you execute the iadmin command on a primary or secondary IAS, the change is reflected on the corresponding secondary or primary IAS after the synchronization process is complete. To synchronize the servers immediately, use the iadmin -reinit fullsync -sync command. See iadmin reinit/sync options on page 104 for more information. IAS synchronization properties You can define your IAS synchronization properties by modifying the following properties in its corresponding ias.properties file. Table 25 IAS synchronization properties (part 1 of 2) Property com.bmc.sms.ixs.transaction.history com.bmc.sms.configservice.keepbackupfile com.bmc.sms.ixs.sync.interval Description for failover definitions. The number of days that entries in the transaction log are kept before they are removed by synchronization. The default is 5 days. for standalone and failover definitions. Indicates whether the IAS maintains a backup copy (.bak extension) when it writes a file. The default is false. for failover definitions. Interval in minutes between synchronization requests from a secondary server to a primary server. The default is 15 minutes. Chapter 3 Managing the BMC Impact Administration server 103

100 Defining standalone, primary, and secondary BMC Impact Administration servers Table 25 IAS synchronization properties (part 2 of 2) Property com.bmc.sms.ixs.primary.server com.bmc.sms.ixs.backup.server com.bmc.sms.ixs.server.mode Description for failover definitions. The IP address of the primary server along with its default port number in the following format: ipaddressofprimaryserver:portnumber. You define the primary server in the ias.properties file of the paired secondary server. for failover definitions. The IP address of the secondary server along with its default port number in the following format: ipaddressofsecondaryserver:portnumber. You define the secondary server in the ias.properties file of the primary IAS server. the server role. Options are standalone (default), primary, and backup. If you specify primary or backup, then of course you must complete the primary and backup server entries in the respective ias.properties files of the two servers. iadmin reinit/sync options You can use the following iadmin reinit/sync options to restart a server, copy the primary server s configuration to its secondary server, or start a synchronization between the two servers immediately. From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, you can execute the iadmin -reinit command on the primary or secondary server to restart the server with the latest configuration data You usually execute the iadmin -reinit command on the primary server after you have manually edited any of its files. execute the iadmin -reinit fullsync command on the secondary server only to copy the primary server s configuration to it and to restart it with the new configuration You should execute the iadmin -reinit fullsync command on the secondary server the first time you start it after installation. execute the iadmin -sync command on the secondary server to start the synchronization process immediately instead of waiting until the next synchronization interval 104 BMC Impact Solutions Infrastructure Management Guide

101 Defining a failover configuration for the Impact Administration cell Use the iadmin -reinit and iadmin -reinit fullsync commands to restart the respective server anytime you have manually edited one or more of the primary server s configuration files. Your typical use case would look as follows: 1. Manually edit the configuration files on the primary server. 2. Execute the iadmin -reinit command on the primary server. 3. Execute the iadmin -reinit fullsync command on the secondary server. BMC recommends that you use the iadmin CLI to edit files whenever possible, thereby eliminating the need to restart the server. Defining a failover configuration for the Impact Administration cell As a general practice, you configure the IAC as an failover pair whenever you configure the Master IAS as a failover pair. Use this table as a guideline for changing the respective mcell.dir files of the primary IAC on one host system and the secondary IAC on the second host system: Table 26 mcell.dir entries for a failover pair of Impact Administration cells Primary IAC on Host 1 Secondary IAC on Host 2 cell Admin mc host1:1827 host2:1827 cell Admin mc host1:1827 host2:1827 cell IAC mc host1:1827 host2:1827 cell IAC mc host1:1827 host2:1827 Remember that the primary IAC resides on the same host as the primary Master IAS and the secondary IAC resides on the same host as the secondary Master IAS. After you define the entries in the mcell.dir files, you must modify the respective mcell.conf files as you would any normal cell that you are configuring for failover. Chapter 3 Managing the BMC Impact Administration server 105

102 Transaction and trace logs Transaction and trace logs The IAS automatically generates the log files listed in Table 27. Table 27 IAS log files File name transaction.log record_transaction.log ias0.log Description stored under IMPACT_SOLUTIONS_HOME/server/log/ias. Records transactions for file synchronization stored under IMPACT_SOLUTIONS_HOME/server/log/ias. Records transactions for record synchronization stored under IMPACT_SOLUTIONS_HOME/server/tmp/ias. This is the diagnostic trace log. They are numbered incrementally. A new log file is created whenever IAS restarts or when the current log file reaches its specified maximum size. When the maximum log file count is reached, then the process repeats itself because only one cycle of logs is maintained. The new log file is always named ias0.log. The logger renames the existing log files in ascending chronological order. So the earliest log file is ias1. log and the oldest log file in the cycle has the greatest number. You can edit the properties of the diagnostic trace log ias0.log in the server_logging.properties file. Example trace output An example trace excerpt, showing INFO level messages, is shown below: I :20:18:253 UTC INFO [WrapperStartStopAppMain] com.bmc.sms.ixscomm.jmx.ixscomm.startservice() -> Credential Repository loaded successfully :20:18:253 UTC INFO [Thread-1] com.bmc.sms.ixscomm.server.ixsserver.run -> start to accept requests Advanced tasks This section describes two tasks that require background knowledge of third-party products and utilities. The task Configuring BMC Impact Administration server to support remote actions on page 107 requires knowledge of secure protocols, and the task Configuring Lightweight Directory Access Protocol for BMC Impact Administration server on page 109 requires knowledge of Lightweight Directory Access Protocol (LDAP). 106 BMC Impact Solutions Infrastructure Management Guide

103 Configuring BMC Impact Administration server to support remote actions Configuring BMC Impact Administration server to support remote actions If the BMC Impact Administration server and the target application share an MS Windows platform, then remote actions are enabled by default. The IAS uses New Technology LAN Manager (NTLM), v. 2, to secure communications between MS Windows systems. If the BMC Impact Administration server and the target application share a UNIX Solaris or Linux platform, then remote actions are enabled by default also but through the Secure Shell (SSH), v. 2, protocol. SSH, v. 2, should be installed with the Solaris or Linux operation system. You may have to configure it for use if it is not already enabled. If either the BMC Impact Administration server or the target application is installed on an HP-UX or an AIX system, then you must download the SSH package from a third-party vendor to the HP-UX or AIX system. Then you must configure it to enable remote actions. If the BMC Impact Administration server resides on a UNIX or Linux system and the the target application sits on an MS Windows system, then you must download the SSH package to the MS Windows systems. Then configure it to enable remote actions. BMC recommends that you use SSH to secure communications. Default protocols IAS uses the default communication protocols that are specified in the IMPACT_SOLUTIONS_HOME/server/conf/resources/centraladmin-strings.properties file. For MS Windows, the IAS uses the PsExec protocol: windows.execute.command=com.bmc.sms.marimba_cas_tools.psexectask windows.putfile=com.bmc.sms.marimba_cas_tools.psexectask windows.getfile=com.bmc.sms.marimba_cas_tools.psexectask For the UNIX-based operating systems, the following defaults are used: unix.execute.command=com.bmc.sms.marimba_cas_tools.sshtask unix.putfile=com.bmc.sms.marimba_cas_tools.scptask unix.getfile=com.bmc.sms.marimba_cas_tools.scptask Chapter 3 Managing the BMC Impact Administration server 107

104 Configuring BMC Impact Administration server to support remote actions You can specify multiple protocol values for each of these properties, as shown: windows.execute.command=com.bmc.sms.marimba_cas_tools.psexectask,com.bmc.sms. marimba_cas_tools.sshtask,com.bmc.sms.marimba_cas_tools.telnettask windows.putfile=com.bmc.sms.marimba_cas_tools.psexectask,com.bmc.sms. marimba_cas_tools.scptask,com.bmc.sms.marimba_cas_tools.ftptask windows.getfile=com.bmc.sms.marimba_cas_tools.psexectask,com.bmc.sms. marimba_cas_tools.scptask,com.bmc.sms.marimba_cas_tools.ftptask In this instance, the IAS tries to execute the remote action using each of the specified protocols in sequence until the command succeeds. For example, for the windows.execute.command, the IAS first tries PsExec. If it fails, then it tries SSH. If it fails, then it uses Telnet. It repeats the pattern for each command. NOTE Make sure that you re familiar with security protocols before modifying these settings. If the BMC Impact Explorer console, cell, or the task definition in the UserDefinedActions.xml file does not specify an operating system, then IAS uses the SSH protocol for all OS commands, as shown below: all.execute.command=com.bmc.sms.marimba_cas_tools.sshtask all.putfile=com.bmc.sms.marimba_cas_tools.scptask all.getfile=com.bmc.sms.marimba_cas_tools.scptask See the BMC Impact Solutions Event Management Guide for more information on task definitions. You can also specify multiple protocol values for these commands, as shown in the preceding example. To initialize any changes, restart the BMC Impact Administration server. Enabling Telnet By default, the Telnet protocol is turned off. Telnet is not a secure protocol. User name and password credentials that you enter are sent in plain text to the remote system. Also, the Telnet session times out during the creation of support packages. However, you can enable Telnet and ftp. You will need to start the Telnet service on the Windows system. You also need to modify the centraladmin-strings.properties file located under the IMPACT_SOLUTIONS_HOME/server/conf/resources path. 108 BMC Impact Solutions Infrastructure Management Guide

105 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server The relevant section of the centraladmin-strings.properties file is depicted below: unix.execute.command=com.bmc.sms.marimba_cas_tools.sshtask unix.putfile=com.bmc.sms.marimba_cas_tools.scptask unix.getfile=com.bmc.sms.marimba_cas_tools.scptask To enable Telnet and ftp, modify the properties as follows: unix.execute.command=com.bmc.sms.marimba_cas_tools.sshtask,com.bmc.sms.marimba_cas_tools. TelnetTask unix.putfile=com.bmc.sms.marimba_cas_tools.scptask,com.bmc.sms.marimba_cas_tools.ftptask unix.getfile=com.bmc.sms.marimba_cas_tools.scptask,com.bmc.sms.marimba_cas_tools.ftptask Restart the BMC Impact Administration server to initialize your changes. Configuring Lightweight Directory Access Protocol for BMC Impact Administration server Use Lightweight Directory Access Protocol (LDAP) authentication in a production environment. In this way, you can link your BMC Impact Administration server (IAS) authentication with your corporate infrastructure for user authentication and authorization management. Using LDAP authentication allows you to use the same user definitions across multiple BMC product lines. After you define your LDAP user and user groups, you can map your LDAP user groups to the IAS user groups. Any users you add to an LDAP user group share the permissions of the IAS user group to which you have mapped. The IAS supports Active Directory LDAP nested groups. You can use a single sign-on to access multiple products. You do not have to create a separate user definition and sign-on information for each product. To enable LDAP authentication for the IAS on a Windows system, your login account must have administrator privileges on the target system. On a UNIX system, you must be logged in as root or under a user account with write and execute permission on the IMPACT_SOLUTIONS_HOME/server directory. Set up your LDAP server according to your LDAP server procedures. Next, enable the LDAP login entry in the ias.properties file. Then you can enter your LDAP configuration information for each LDAP server that you are enabling. Chapter 3 Managing the BMC Impact Administration server 109

106 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server NOTE If you are using a solution that requires the BMC Portal and/or BMC Atrium CMDB, you may need to set up LDAP authentication on the BMC Portal server and on the AR System server. Refer to the BMC Portal Getting Started guide for information on setting up LDAP authentication on the BMC Portal server. Refer to the BMC Remedy Action Request System 7.1 Integration with Plug-ins and Third-Party Products for information on setting up LDAP authentication on the AR System server. To enable the LDAP login entry in the ias.properties file 1 In an editor, open the IMPACT_SOLUTIONS_HOME/server/conf/ias.properties file, where IMPACT_SOLUTIONS_HOME/server is the installation directory of your server. Locate the com.bmc.sms.ixs.enable.ldap.login parameter, and set it equal to true : # # Enable/disable LDAP login module. # When it is enabled, "ldap_definition.xml" file has to be filled. # com.bmc.sms.ixs.enable.ldap.login=true 2 Optional. To enable file-based user groups, defined in the user_definitions.xml file, to map to roles in addition to LDAP user groups, modify the com.bmc.sms.ixs.allow.local.groups.for.ldap parameter, setting it equal to true, as in the following example: com.bmc.sms.ixs.allow.local.groups.for.ldap=true The user groups defined in the user_definitions.xml file are mapped to roles for the initial log-in and for user authorization. NOTE If you leave the default value false, then only roles that are mapped to the user s LDAP groups are used for user authorization. 3 Save and close the ias.properties file. 4 Restart IAS. 5 In an editor, open the IMPACT_SOLUTIONS_HOME/server/conf/jaas.conf file. Do not modify this file. Verify that it contains an entry such as the following: com.bmc.sms.ixscomm.authentication.ldap.ldaploginmodule Sufficient; 6 Close the file. 110 BMC Impact Solutions Infrastructure Management Guide

107 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server Figure 13 To add LDAP configuration information You are now ready to add your LDAP configuration information to the IMPACT_SOLUTIONS_HOME/server/conf/ldap_configuration.xml file. Figure 13 on page 111 depicts a sample ldap_configuration.xml file with a single LDAP server configuration: Excerpt from ldap_configuration.xml file <?xml version="1.0" encoding="utf-8"?><ldaplist xmlns="urn:bmc:schemas:impact" xmlns:xsi=" xsi:schemalocation="urn:bmc:schemas:impact ldap_definitions.xsd"> <ldap alias="test"> <host>majestix.bmc.com</host> <port>389</port> <version>3</version> <basedn>dc=pinfrastruct,dc=rd,dc=bmc,dc=com</basedn> <connectionusername>glin@pinfrastruct.rd.bmc.com</connectionusername> <useridattribute>samaccountname</useridattribute> <usessl>false</usessl> <memberofattribute>memberof</memberofattribute> <usersearchfilter>(objectclass=organizationalperson)</usersearchfilter> <groupsearchfilter/> <connectionpassword encrypted="true">fisscap4zholouenwple== </connectionpassword> </ldap>... </ldaplist> 1 Make only one <ldap></ldap> entry for each LDAP configuration. Multiple LDAP configurations can exist for one LDAP server with different basedn parameter values. 2 Follow these guidelines for your <ldap></ldap> entries: A Specify a unique alias for each LDAP configuration. B Ensure that the LDAP group is defined in the group_roles.xml file on the IAS. 3 Using Table 28 on page 111 as a guide, complete the LDAP configuration parameters. Table 28 LDAP configuration parameters (part 1 of 2) LDAP parameter Description host the fully qualified host name where LDAP is installed. You should be able to verify the connection between the LDAP server and the IAS using the ping command. port port number by which to connect to the LDAP server. Normally the nonsecure port number is 389. The secure (SSL) port number is 636. version LDAP version number. The most recent version is version 3. Chapter 3 Managing the BMC Impact Administration server 111

108 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server Table 28 LDAP configuration parameters (part 2 of 2) LDAP parameter basedn connectionusername useridattribute usessl memberofattribute usersearchfilter groupsearchfilter connectionpassword Description directory of the LDAP structure from which the search routine starts in LDAP. This is the base Fully Qualified Distinguished Name (FQDN) from which all user and group queries occur. The Distinguished Name represents an object and the path to the object in the directory hierarchical namespace. Objects are ordered from most to least specific. login Id that the programs use to connect to the LDAP server. attribute in the user entry that contains the login Id. indicates whether LDAP authentication is using OpenSSL. attribute in the user entry that specifies whether the user belongs to certain user groups. search filter that the LDAP server uses to look up a user entry. If left blank, this parameter defaults to the following filter: ( (objectclass=person)(objectclass=user) (objectclass=inetorgperson)(objectclass= organizationalperson)) search filter that the LDAP server uses to look up a user group entry. If left blank, this parameter defaults to the following filter: ( (objectclass=group)(objectclass= groupofuniquenames)(objectclass=groupofnames)(objectclass=grou pofurls)) authentication password (encrypted) that is used to connect to the LDAP server. Note: Set the encrypted attribute equal to false and then enter the password in plain text. When IAS restarts, it encrypts the password and changes the encrypted attribute value from false to true. 4 After completing your changes, restart the IAS. On Microsoft Windows, restart the IAS service through the Services window. On UNIX, execute the ias_service script from the appropriate path. (The default path is /opt/bmc/impact/server/bin.) You must be logged on as a root user to start and stop the script. The IAS connects to the LDAP servers one at a time in succession. When it finds a user s matching login credentials, the IAS returns the match. It does not attempt to connect to other LDAP servers that might be defined in the ldap_configuration.xml file. Next, after you add your LDAP server or servers, you can add a user group and assign it a user role. 112 BMC Impact Solutions Infrastructure Management Guide

109 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server To add a new user group with mapping roles NOTE If you re adding a new role to the group, you must first create the role and add permissions to it using the iadmin -ar option before you create the group. See To add a new role/mapping permission on page 87. From the/bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -ag option, as in the following example: iadmin -ag group= NewGroup :roles= Role The new entry would look similar to the following in the group_roles.xml file: <entry key="nameofusergroup">ias_defaultrolename</entry> To add the role name to the cell s KB definition files You add the role name to the Access Control List (ACL) of the collector definition and operation definition files in the connected cell or cells. NOTE If the ACL is empty, then every group has access. 1 Add the user group name to each of the following collector definition files that you want the user group to access. Where indicated, associate the read, write, and execute permissions (r, w, x) with the group name entry: biip4p_collectors.mrl catchall_collector.mrl mc_bylocation_collectors.mrl mc_bystatus_collectors.mrl mc_evr_collectors.mrl mc_sm_collectors.mrl mcxpcoll.mrl self_collector.mrl You may need to change the file permissions on these files before editing them. Chapter 3 Managing the BMC Impact Administration server 113

110 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server The following code examples show sample modifications to each file: biip4p_collectors.mrl collector PATROL : { r['service Administrators','Service Operators - Senior','Service Operators','Service Managers - Senior','Service Managers', nameofusergroup ] w['service Administrators','Service Operators - Senior','Service Operators','Service Managers - Senior','Service Managers', nameofusergroup ] x['service Administrators','Service Operators - Senior','Service Operators','Service Managers - Senior','Service Managers', nameofusergroup ] } END catchall_collector.mrl collector 'All Events' : { r['service Administrators', nameofusergroup ] w['service Administrators', nameofusergroup ] x['service Administrators', nameofusergroup ] } mc_bylocation_collectors.mrl collector 'By Location': { r['service Administrators', nameofusergroup ] w['service Administrators', nameofusergroup ] x['service Administrators', nameofusergroup ] } END... collector 'By Location'.*: { r['service Administrators','Service Operators - Senior','Service Operators','Service Managers - Senior','Service Managers', nameofusergroup ] w['service Administrators','Service Operators - Senior','Service Operators','Service Managers - Senior','Service Managers', nameofusergroup ] x['service Administrators','Service Operators - Senior','Service Operators','Service Managers - Senior','Service Managers', nameofusergroup ] }: 114 BMC Impact Solutions Infrastructure Management Guide

111 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server mc_bystatus_collectors.mrl collector 'By Status': { r['service Administrators','Service Operators - Senior', nameofusergroup ] w['service Administrators','Service Operators - Senior', nameofusergroup ] x['service Administrators','Service Operators - Senior', nameofusergroup ] } END mc_evr_collectors.mrl collector MC_Related_Events: { r['service Administrators', nameofusergroup ] w['service Administrators', nameofusergroup ] x['service Administrators', nameofusergroup ] } END collector MC_Related_Events.*: { r['service Administrators', nameofusergroup ] w['service Administrators', nameofusergroup ] x['service Administrators', nameofusergroup ] }: EVENT where [mc_relation_source:!= ''] create $THIS.CLASS END You can add a user group to this.mrl file, but be sure not to edit any other parameter or value. Chapter 3 Managing the BMC Impact Administration server 115

112 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server mc_sm_collectors.mrl collector MC_SMC_Events: { r['full Access', 'Service Administrators' nameofusergroup ] w['full Access', 'Service Administrators' nameofusergroup ] x['full Access', 'Service Administrators' nameofusergroup ] } END collector MC_SMC_Events.*: EVENT where [$THIS.mc_smc_id!= ""] create cond($this.mc_smc_type == '', "Unknown", $THIS.mc_smc_type) END collector MC_SMC_Events.*.Impacts: EVENT where [$THIS.mc_smc_impact == 1] END collector MC_SMC_Events.*.History: SMC_STATE_CHANGE END You can add a user group to this.mrl file, but be sure not to edit any other parameter or value. mcxpcoll.mrl collector 'By Location'.*.*.*.*.*: PATROL_EV where [p_application: not_equals ''] create $THIS.p_application END { r[ nameofusergroup ] w[ nameofusergroup ] x[ nameofusergroup ] } self_collector.mrl collector self : { r['full Access', 'Read Only', nameofusergroup ] w['full Access', nameofusergroup ] x['full Access', nameofusergroup ] } END 116 BMC Impact Solutions Infrastructure Management Guide

113 Configuring Lightweight Directory Access Protocol for BMC Impact Administration server 2 Next, assign the group name to the appropriate event management operations in the im_operations.mrl file. Each event operation can be performed by a predefined set of groups, as shown in Table 29. Table 29 Event operations Event operation Group names Acknowledge Service Administrators, Service Operators - Senior, Service Operators Take Ownership Service Administrators, Service Operators - Senior, Service Operators Decline Ownership Service Administrators, Service Operators - Senior, Service Operators Close Service Administrators, Service Operators - Senior, Service Operators Assign to Operation Service Administrators, Service Operators - Senior Set Priority Service Administrators, Service Operators - Senior Reopen Service Administrators, Service Operators - Senior An example of a group name assignment to a specific event management action is shown below: action im_operations.acknowledge: { ['Service Administrators','Service Operators - Senior','Service Operators', nameofusergroup ] } 3 Make the appropriate group name assignments to the mc_actions.mrl file and the sim_operations.mrl file, following the syntax examples in the files. 4 Recompile the cell s KB using the mccomp command, as in the following example: mccomp -n cellname manifestkbfilepath You must include the path to the manifest.kb file. 5 Restart the cell using the mcell command. To retrieve LDAP groups or to authenticate an LDAP user From the /bin subdirectory of your IMPACT_SOLUTIONS_HOME/server directory, execute the iadmin command using the -tlq option, as in the following example that retrieves a list of LDAP groups: iadmin -tlq group Chapter 3 Managing the BMC Impact Administration server 117

114 Troubleshooting NOTE When you execute the iadmin command using the -tlq option, you must have the correct LDAP server information in the ldap_configuration_query.xml file. To authenticate a specific LDAP user, enter the user name and password, as in the following example: iadmin -tlq username=<string>:password=<string> The -tlq option also checks the time required to execute an LDAP query. To facilitate the iadmin -tlq option, you can modify the following properties in the IMPACT_SOLUTIONS_HOME/server/conf/ias.properties file. LDAP property com.bmc.sms.ixs.search.time.limit com.bmc.sms.ixs.search.ldap.group Description the maximum time for an LDAP query to retrieve data from the LDAP server. The default is 5000 milliseconds. groups to be searched in the LDAP server when, for example, you are assigning events to groups. Only groups that are also defined in the group_roles.xml file are searched in LDAP. Troubleshooting Problem: Cell_info.list synchronization error during manual configuration of an IAS failover When manually configuring an IAS high availability pair, you will find that the cell_info.list does not synchronize properly between the primary and secondary Impact Administration servers. You can work around this issue by manually copying the cell entries of the Impact Administration server that you will convert to the secondary server saving them to an editor adding them to the newly created primary server using the iadmin command starting both the primary and secondary servers and executing the iadmin -reinit fullsync command on the secondary server 118 BMC Impact Solutions Infrastructure Management Guide

115 Problem: Cell_info.list synchronization error during manual configuration of an IAS failover Before you begin Configure the corresponding Impact Administration (Admin) cell in high availability mode. To manually synchronize the cell_info.list 1 Execute the iadmin -lc command against the Impact Administration server system that you will later configure as the secondary server. An example command with sample output is shown below: bash-3.00# iadmin -lc BMC Impact Administration Server [Build Dec-2008] Copyright BMC Software, Inc. as an unpublished work. All rights reserved. List BMC Impact Managers: pun-sms-sun31 mc pun-sms-sun31.bmc.com:1828 Production * 2 Copy the cell entry to a text editor, such as Notepad. In this example, the copy would look as follows: pun-sms-sun31 mc pun-sms-sun31.bmc.com:1828 Production * 3 Manually add the host cell entry from the secondary server to the primary server s cell_info.list file using the iadmin -ac command, as in the following example: iadmin -ac name= pun-sms-sun31:key=mc:primaryhost=pun-sms-sun31:port=1828: environment=production:usergroups=* 4 Configure IAS failover (primary and secondary servers). See To configure IAS failover manually on page 102 for the steps. 5 Restart the primary and secondary servers. 6 Execute the iadmin -reinit fullsync command on the secondary server to copy the primary server s configuration to it and to restart it with the new configuration 7 Wait for the synchronization process to complete. The default synchronization interval time is 15 minutes. This value is defined in the com.bmc.sms.ixs.sync.interval property of the IMPACT_SOLUTIONS_HOME/server/conf/ias.properties file. Chapter 3 Managing the BMC Impact Administration server 119

116 Problem: Cell_info.list synchronization error during manual configuration of an IAS failover 120 BMC Impact Solutions Infrastructure Management Guide

117 Chapter 4 Managing the BMC Impact Portal 4 This chapter describes how to configure the BMC Impact Portal and contains the following topics: Accessing the BMC Impact Portal Starting and stopping the BMC Portal Starting and stopping the BMC Portal on Windows Starting and stopping the BMC Portal on UNIX Configuration tasks for BMC Impact Portal Registering production and test cells in the BMC Impact Portal Customizing BMC Impact Portal configuration Configuring Dashboard Table View columns Configuring Events Table columns Configuring Status Table columns Configuring object link synchronization Configuring reports Configuring the number of events displayed Changing the maximum number of recent items displayed Configuring the general properties displayed Setting up Image Views Modifying connection settings Configuration file and parameter definitions for BMC Impact Portal smsiwc/application.properties file and parameters smsconsoleserver/application.properties file and parameters internal.properties file and parameters Chapter 4 Managing the BMC Impact Portal 121

118 Accessing the BMC Impact Portal Accessing the BMC Impact Portal Communication between the Web browser and the BMC Portal is encrypted and requires the use of the communication protocol. To access the BMC Portal 1 In the browser s address box, type the BMC Portal URL address using the following syntax: computername represents the host name of the BMC Portal server portnumber represents the port number assigned to the BMC Portal; the default port number is 443 NOTE The Transport Layer Security (TLS) protocol is used to secure communication between the BMC Portal Application Server and the Web browser. 2 In the security alert window, click Yes to accept the security certificate. 3 In the logon screen, type your logon user name and password, and then click Log On. If you receive the message user name and password invalid after entering a valid user name and password, the BMC Portal server might not be running. Start the BMC Portal and log on to it again. WARNING If you leave your BMC Portal session by selecting a different URL and then return to the session before the expiration of the timeout period, the BMC Portal fails to prompt you for your user name and password. To ensure the integrity of the session, log out of the session every time you leave your BMC Portal session. Starting and stopping the BMC Portal The installation process does not automatically start the BMC Portal service. The following topics describe how to start and stop the BMC Portal service on both Windows and UNIX. 122 BMC Impact Solutions Infrastructure Management Guide

119 Starting and stopping the BMC Portal on Windows Starting and stopping the BMC Portal on Windows You can start and stop the BMC Portal by using either of the following methods: using the Services window using the net start and net stop commands To start or stop the BMC Portal from the Services window 1 Open the Services window. 2 From the scroll list, select BMC Portal. 3 To start the service, click Start Service. 4 To stop the service, click Stop Service. To start or stop the BMC Portal from the command line From a command prompt, use the following methods to start and stop the BMC Portal: To start the BMC Portal, enter the following command: net start BMC Portal To stop the BMC Portal, enter the following command: net stop BMC Portal Starting and stopping the BMC Portal on UNIX The BMC Portal starts and stops as a daemon on UNIX platforms. To start or stop the BMC Portal daemon on UNIX To start or stop the BMC Portal on UNIX, use the BMCPortalAppserver script in the /etc/init.d directory and enter one of the following commands:./bmcportalappserver stop./bmcportalappserver start Chapter 4 Managing the BMC Impact Portal 123

120 Configuration tasks for BMC Impact Portal Configuration tasks for BMC Impact Portal This section contains some of the tasks you perform to configure the BMC Impact Portal. Registering production and test cells in the BMC Impact Portal Production and test cells must be registered in BMC Impact Portal so BMC Impact Explorer users can access the data defined to cells. Administrators can register a cell by using the BMC Impact Portal Viewable Impact Managers tab. For information on registering a cell in BMC Impact Portal, see the online Help or the BMC Portal Getting Started. Customizing BMC Impact Portal configuration You customize a BMC Impact Portal by editing the configuration parameters found in the internal.properties file located in the jboss/server/all/conf/properties/ smsconsoleserver directory. These configuration parameters can affect several services. If you make changes to the internal.properties file, you will need to stop and start the BMC Impact Portal. For more information about the internal.properties file and its configuration, see internal.properties file and parameters on page 136. Configuring Dashboard Table View columns You can change the columns displayed in the dashboard table views by editing the..\smsiwc\application.properties file. To configure Dashboard Table View columns 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 Edit the file to add or remove columns using the following format: table_name=comma separated attribute (slot) names 124 BMC Impact Solutions Infrastructure Management Guide

121 Configuring Events Table columns 3 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. Configuring Events Table columns You can edit the columns that appear in the table in the Events tab by editing the..\smsiwc\application.properties file. All columns in the events table are configurable. To configure Events Table columns 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 Edit the appropriate events table column as shown in Table 30 on page 125. Table 30 Event Table column default values Column heading Description status event status of the selected component mc_priority value of the possible priorities of the event (values 5, 4, 3, 2, or 1) severity value of the possible severities of the event (unknown, ok, info, warning, minor, major, or critical) date_reception date and time the event was received owner_name name of the owner of the component msg relevant information related to the event 3 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. For more information on this file, see smsiwc/application.properties file and parameters on page 133. Chapter 4 Managing the BMC Impact Portal 125

122 Configuring Status Table columns Configuring Status Table columns Table 31 You can edit some of the columns in the tables in the Status tab by editing the..\smsiwc\application.properties file. However, not all columns are configurable. The first three columns (status, type, and name) cannot be changed. A smaller version of each primary status table is displayed in the dashboard view, if the Status window is selected for one or more of the dashboard panes. By default, no columns beside the status, type, and name are configured for these smaller tables, but columns can be added in the application.properties file. To configure Status Table columns 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 Edit the appropriate status table column as shown in Table 31. Status table column default values Table Configuration file listing Default columns Providers com.bmc.sms.iwc.status.table.providers last_status_modification description owner_name owner_contact Providers com.bmc.sms.iwc.status.table.providers. small none (dashboard view) Consumers com.bmc.sms.iwc.status.table.consumers last_status_modification description owner_name owner_contact Consumers com.bmc.sms.iwc.status.table.consumers. small none (dashboard view) Causes com.bmc.sms.iwc.status.table.causes last_status_modification description owner_name owner_contact 3 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. For more information, see smsiwc/application.properties file and parameters on page BMC Impact Solutions Infrastructure Management Guide

123 Configuring object link synchronization Configuring object link synchronization You can change the objectlinksync values by editing the..\smsiwc\application.properties file. To configure object link synchronization 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 To change the object link type, modify the com.bmc.sms.iwc.objectlinksync.types entry. 3 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. For more information, see smsiwc/application.properties file and parameters on page 133. Configuring reports You can configure the following items for reports by editing the..\smsconsoleserver\application.properties file: scheduling value of report goal lines length of time report data is retained length of time event data is retained To configure reports 1 Open the application.properties or internal.properties files in a text editor. These file are located at installationdirectory\tools\jboss\server\all\conf\properties\smsconsoleserver\. 2 Edit the appropriate status table column as shown in Table 32 on page 128 and Table 33 on page 129. Chapter 4 Managing the BMC Impact Portal 127

124 Configuring reports Table 32Report parameters (application.properties file) Parameter type Parameter Description Report Goals com.bmc.sms.reportsummarizer.goal.default Availability report goal line, expressed as a.sms_cs_rt_avail percentage. Default value is 90.0%. Retention Age com.bmc.sms.reportsummarizer.goal.default.sms_cs_rt_mttr com.bmc.sms.reportsummarizer.goal.default.sms_cs_rt_mtbf com.bmc.sms.reportsummarizer.goal.default.sms_cs_rt_mtbsi com.bmc.sms.consoleserver.retention.policy. age.sms_cs_status_event com.bmc.sms.consoleserver.retention.policy. age.sms_cs_rt_avail com.bmc.sms.consoleserver.retention.policy. age.sms_cs_rt_mttr com.bmc.sms.consoleserver.retention.policy. age.sms_cs_rt_mtbf com.bmc.sms.consoleserver.retention.policy. age.sms_cs_rt_mtbsi com.bmc.sms.consoleserver.retention.policy. age.eg_event Mean Time to Repair goal line, expressed in milliseconds. Default value is (5 minutes). Mean Time Between Service Failures goal line, expressed in milliseconds. Default value is (2 days). Mean Time Between Service Incidents goal line, expressed in milliseconds. Default value is (2 days). The number of days Status tab data will be retained. Default value is 395. The number of days Availability data will be retained. Default value is 395. The number of days Mean Time to Repair data will be retained. Default value is 395. The number of days Mean Time Between Failure data will be retained. Default value is 395. The number of days Mean Time Between Service Incidents data will be retained. Default value is 395. The number of days event data will be retained in the BMC Datastore. Default value is BMC Impact Solutions Infrastructure Management Guide

125 Configuring the number of events displayed Table 33 Report parameters (internal.properties) file Parameter type Parameter Description Report Schedule com.bmc.sms.reportsummarizer.scheduler. The frequency, in hours, that the report frequencyhours information is summarized. Default value is 1. com.bmc.sms.reportsummarizer.scheduler. delayseconds com.bmc.sms.reportsummarizer.scheduler.is StartingNextHour com.bmc.sms.reportsummarizer.scheduler. startinghour The number of seconds that will be added to the starting hour for every scheduled summarization time. Default value is 30. Determines whether or not the setting of startinghour will be ignored. If set to true, startinghour will be ignored. Default value is true. Determines the desired starting hour. No summarization is made until this value is reached. If the startinghour has passed on that day, the summarization will start at that hour the next day. Default value is 0. 3 Save the application.properties and internal.properties files. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. For more information, see smsiwc/application.properties file and parameters on page 133. Configuring the number of events displayed You can set the maximum and minimum number of events displayed in the Events tab by editing the..\smsiwc\application.properties file. To configure the number of events displayed 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 To change the minimum number of events shown on the Events table, edit the value for com.bmc.sms.iwc.event.table.minimumevents. The default value is 5. 3 To change the maximum number of events shown on the Events table, edit the value for com.bmc.sms.iwc.event.table.maximumevents. The default value is 50. Chapter 4 Managing the BMC Impact Portal 129

126 Changing the maximum number of recent items displayed 4 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 5 Restart the BMC Portal service. For more information, see smsiwc/application.properties file and parameters on page 133 and internal.properties file and parameters on page 136. Changing the maximum number of recent items displayed You can change the maximum number of objects displayed in the Recent Items group in the navigation tree by editing the..\smsiwc\application.properties file. To change the maximum number of recent items displayed 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 To change the maximum number of recent items displayed in the navigation tree, edit the value for com.bmc.sms.iwc.ui.recentitems.maxsize. 3 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. For more information on this file, see smsiwc/application.properties file and parameters on page 133 Configuring the general properties displayed You can change the general properties in the Configuration tab by editing the..\smsiwc\application.properties file. 130 BMC Impact Solutions Infrastructure Management Guide

127 Setting up Image Views To configure the general properties displayed 1 Open the application.properties file in a text editor. This file is located at installationdirectory\tools\jboss\server\all\conf\properties\smsiwc\. 2 Add or remove property types associated with com.bmc.sms.iwc.component.properties.generalproperties.properties. 3 Save the application.properties file. WARNING To preserve the.properties suffix, save as type All Files. Do not save the application.properties file as a.txt file. The configuration changes may not be recognized. 4 Restart the BMC Portal service. For more information on this file, see smsiwc/application.properties file and parameters on page 133 Setting up Image Views Image Views provide an alternative method for displaying components contained in a service model. Using a background image, you can organize the service model components to represent an area of your environment. For example, you can create an Image View that illustrates the geographic locations of a service model on a map. The background images used for Image Views are located in the following directory: BMC_PORTAL_KIT_HOME\appserver\websdk\tools\jboss\server\all\data\ smsconsoleserver\image\background To add a background image, place a copy of the graphic file in this directory. You can use the following types of graphic files for background images: GIF JPEG PNG Use the Configure tab in the BMC Impact Portal to create, edit, and delete Image Views. For more information on setting up Image Views, see the BMC Impact Portal online Help. Chapter 4 Managing the BMC Impact Portal 131

128 Modifying connection settings Modifying connection settings You can modify the settings that BMC Impact Portal server uses when connecting to BMC Impact Manager instances. To modify BMC Impact Portal connection settings 1 In a text editor, open the %BMC_PORTAL_KIT_HOME%\appserver\websdk\tools\jboss\server\all\conf\ properties\smsconsoleserver\application.properties file. 2 Search for the Cell connection configuration stanza, and review the connection properties. The following figure depicts the default values for the connection properties. CellName.timeout = 30 CellName.reconnect_attempts = 5 CellName.reconnect_frequency = 30 CellName.polling_frequence = 3600 CellName.encryption = on 3 Modify the connection properties. 4 Save the application.properties file. 5 Restart the BMC Portal service (or daemon) to initialize the file. The BMC Impact Portal settings are reset. Configuration file and parameter definitions for BMC Impact Portal Normally, you make changes to BMC Impact Portal component configurations through the user interface. However, you can manually edit three sets of configuration files that contain configuration information for the BMC Impact Portal module. These files pertain to these components: BMC Impact Portal BMC Impact Service Model Editor BMC Impact Publishing Server 132 BMC Impact Solutions Infrastructure Management Guide

129 smsiwc/application.properties file and parameters smsiwc/application.properties file and parameters Table 34 describes the application.properties file in the smsiwc directory and its parameters. Table 34 application.properties file in smsiwc directory (part 1 of 2) Filename application.properties in the..smsiwc folder File path BMC_PORTAL_KIT_HOME/appserver/webskd/tools/jboss/server/all/conf/properties/smsIwc contains the general BMC Impact Portal configurations for component properties and user Description interface presentation Parameter name Description Default value com.bmc.sms.iwc.ui. recentitems.maxsize sets the maximum number of objects that can display in the Recent Items group folder in the navigation tree of the BMC Impact Portal 5 com.bmc.sms.iwc.status. table com.bmc.sms.iwc.component. properties.generalproperties. properties com.bmc.sms.iwc.event.table com.bmc.sms.iwc.domain. notification.impact.type Refer to Changing the maximum number of recent items displayed on page 130 for more information. sets the columns that will display in the status and dashboard table views Refer to Configuring Dashboard Table View columns on page 124 for more information. determines which general properties are displayed in the Configure tab for selected components Refer to Configuring the general properties displayed on page 130 for more information. determines which columns in the events table are visible in the BMC Impact Portal module Refer to Configuring Events Table columns on page 125 for more information. sets the impact definitions included in a component notification See the application. properties file. See the application. properties file for more information. See the application. properties file. BMC_BaseElement com.bmc.sms.iwc.domain. recentitem.recentitemsfoldericon You can designate multiple types of impact definitions, separating each by a comma. If no impact type is set explicitly, the default is BMC_BaseElement. specifies the default icon for the Recent Items folder ServiceComponent.gif Chapter 4 Managing the BMC Impact Portal 133

130 smsconsoleserver/application.properties file and parameters Table 34 application.properties file in smsiwc directory (part 2of 2) com.bmc.sms.iwc.status. table.providers com.bmc.sms.iwc.status. table.consumers com.bmc.sms.iwc.status. table.causes com.bmc.sms.iwc.status. table.existinggroup com.bmc.sms.iwc.status. table.causal.components com.bmc.sms.iwc.status. table.components.small com.bmc.sms.iwc.event. table.minimumevents com.bmc.sms.iwc.event. table.maximumevents determines which columns that you can add to the tables and dashboards under the Status tab in the BMC Impact Portal module Refer to Configuring Status Table columns on page 126 for more information. sets the maximum and minimum number of events retrieved per component instance; this information is displayed on the Events tab See the application. properties file. minimum: 5 maximum: 50 smsconsoleserver/application.properties file and parameters Table 35 describes the application.properties file in the smsconsoleserver directory and its parameters. Table 35 application.properties file in smsconsoleserver directory (part 1 of 3) Filename application.properties in the..smsconsoleserver folder BMC_PORTAL_KIT_HOME/appserver/webskd/tools/jboss/server/all/conf/properties/sms File path ConsoleServer Description contains the configurations for report scheduling, report goals, and report data retention Parameter name Description Default value com.bmc.sms.configservice. datalocation defines where the user configuration data is stored no value; the location BOSS_HOME/s erver/all/data/s msconsoleserv er is used com.bmc.sms.configservice. keepbackupfile com.bmc.sms.reportsummarizer.goa l.default. SMS_CS_RT_AVAIL com.bmc.sms.reportsummarizer.goa l.default. SMS_CS_RT_MTTR if configuration data is changed, defines whether a backup file is saved sets the value of the goal line for the Availability report as a percentage sets the value of the goal line for the Mean Time to Repair (MTTR) report false; no backup file is saved % milliseconds (5 minutes) 134 BMC Impact Solutions Infrastructure Management Guide

131 smsconsoleserver/application.properties file and parameters Table 35 application.properties file in smsconsoleserver directory (part 2of 3) com.bmc.sms.reportsummarizer.goa l.default. SMS_CS_RT_MTBF com.bmc.sms.reportsummarizer.goa l.default. SMS_CS_RT_MTBSI= cellname.timeout cellname.reconnect_attempts cellname.reconnect_frequency cellname.polling_frequency <cellname>.encryption com.bmc.sms.icon.webdir com.bmc.sms.event. maxdelayedhours com.bmc.sms.consoleserver. retention.policy.age. SMS_CS_STATUS_EVENT com.bmc.sms.consoleserver. retention.policy.age. SMS_CS_RT_AVAIL sets the value of the goal line for the Mean Time Before Failure (MTBF) report sets the value of the goal line for the Mean Time Before Service Impact (MTBSI) report. Goal line value is expressed in milliseconds sets the timeout value for data queries by the BMC Impact Portal to the specified cell. The timeout value is measured in seconds sets the number of times for the BMC Impact Portal to try to reconnect to the specified cell when it is unavailable cell (such as the cell or host is down) sets the polling cycle, measured in seconds, for the BMC Impact Portal reconnection attempt to the specified cell sets the polling cycle, measured in seconds, for the BMC Impact Portal data query attempt to the specified cell sets whether is encryption is enabled (off or on) for the connection with the specified cell defines the path in which the icon images for service model components are maintained defines the maximum number of hours an event can be delayed and will still be processed sets the length of time, in days, that report data is retained for each report and that event data is retained in the BMC Datastore milliseconds (2 days) milliseconds (2 days) 30 seconds 60 tries 30 seconds 1800 seconds on /smsconsoleser ver/images/obje cts/ 24 hours 395 days com.bmc.sms.consoleserver. retention.policy.age. SMS_CS_RT_MTTR com.bmc.sms.consoleserver. retention.policy.age. SMS_CS_RT_MTBF com.bmc.sms.consoleserver. retention.policy.age. SMS_CS_RT_MTBSI com.bmc.sms.consoleserver. retention.policy.age. EG_EVENT com.bmc.sms.service.os. unrestricted sets whether the Object Store communication service should run in unrestricted mode when connecting to the Remedy server true Chapter 4 Managing the BMC Impact Portal 135

132 internal.properties file and parameters Table 35 application.properties file in smsconsoleserver directory (part 3 of 3) com.bmc.sms.service.os. restrict.read.access com.bmc.sms.service.os. filtersim com.bmc.sms.remedy. serverhostname com.bmc.sms.remedy. serverportnumber sets whether the Object Store communication service filters are read-only objects sets whether the Object Store communication service filters classes and attributes that are marked SIM=false identifies the host computer on which the BMC Remedy Action Request System host resides lists the port number on which BMC Remedy Action Request System runs true true Action Remedy server host name default Table 36 describes the aggregator.properties file and its parameters. Table 36 aggregator.properties file Filename aggregator.properties BMC_PORTAL_KIT_HOME/appserver/webskd/tools/jboss/server/all/conf/properties/sms File path ConsoleServer contains the configurations for BMC Impact Portal communications with cells, including port Description number used for cell communications, encryption key, and encryption enablement Parameter name Description Default value com.bmc.sms. eventaggregator. jserverportnumber com.bmc.sms.eventaggregator. jserverencryptionkey com.bmc.sms.eventaggregator. jserverencryptionenabled sets the port number through which the BMC Impact Portal communicates with the BMC IM cell sets the encryption key used to communicate with the BMC IM cell communication encryption indicator (true or false) 3783 mc true internal.properties file and parameters Table 37 describes the internal.properties file and its parameters. Table 37 Filename File path internal.properties file internal.properties BMC_PORTAL_KIT_HOME/appserver/webskd/tools/jboss/server/all/conf/properties /smsconsoleserver contains the configurations for BMC Impact Portal communications with the BMC Impact Administration Server, including the port number used for BMC Impact Administration Server communications and parameters for building an IP address in a multi-homed Description environment Parameter name Description Default value 136 BMC Impact Solutions Infrastructure Management Guide

133 internal.properties file and parameters Table 37 internal.properties file com.bmc.sms.ixs.port.number com.bmc.sms.ixs.enable.bind.ip com.bmc.sms.ixs.bind.ip.address sets the port number through which the BMC Impact Portal communicates with the Administration Server sets whether the BMC Impact Portal can bind an IP address on a multi-homed (multi NIC card) system specifies the IP address on a multi-homed system to which the BMC Impact Portal is bound 3084 false Chapter 4 Managing the BMC Impact Portal 137

134 internal.properties file and parameters 138 BMC Impact Solutions Infrastructure Management Guide

135 Chapter 5 Working with Infrastructure 5 Management This chapter presents the following topics: Default Infrastructure Management service model Roles and permissions Walkthrough Displaying the out-of-the-box real-time service model Sampling context-sensitive information Managing files on remote systems Packaging support files Launching remote actions Common Infrastructure Management tasks Navigating the interface Displaying and understanding the Details and Administer tab data Editing infrastructure relationships Creating logical components Deleting components Usage reporting Executing remote actions Reloading cell configuration Forcing event propagation Collecting metrics Executing other actions Configuring the audit log Creating the support package Background to Infrastructure Management How a product component registers and communicates with the IAC Registering a cell with the Admin cell Recreating an Admin cell Unregistering with the IAC Remote actions Chapter 5 Working with Infrastructure Management 139

136 Default Infrastructure Management service model Default Infrastructure Management service model The default Infrastructure Management model consists of logical groupings of BMC infrastructure applications and components. Upon installation certain components send registration events and become automatically registered with the Infrastructure Management model. Figure 14 Default Infrastructure Management service model In the color scheme, green indicates that the object has registered with the Impact Administration cell. Grey indicates that the object is a logical grouping, components whose status is unknown to the Impact Administration cell. Only registered components are viewable in the Find window and services graph. The bold lines that connect the components represent the active impact relationships. The bold lines that connect the components represent the active impact relationships. The arrows indicate the direction (provider to consumer) of the event feed. A dotted line indicates that the relationship is inactive. The following versions of BMC components register with this service model. They can be added as components instances to the respective logical group. Table 38 Supported application groups (part 1 of 2) Group Id Name 100 EM_CELL 101 EM_SERVER_1 102 EM_SERVER_2 103 SIM_CELL 140 BMC Impact Solutions Infrastructure Management Guide

137 Default Infrastructure Management service model Table 38 Supported application groups (part 2of 2) Group Id Name 104 SIM_SERVER_1 105 SIM_SERVER_2 106 IAC (Impact Administration Cell) 110 BMC Impact Portal Application Server 111 IAS (Impact Administration Server) 112 PS (BMC Impact Publishing Server) 120 Adapter 121 LOG_FILE_ADAPTER 122 SNMP_ADAPTER 123 WINDOWS_EVENT_ADAPTER 124 SYSLOG_ADAPTER 125 TCP_ADAPTER 126 TELNET_ADAPTER 127 UDP_ADAPTER 130 IIP7 131 IIP3 132 IIOVO 133 IINNM 134 IITIVOLI 140 DBGW 141 IIARS 142 IBRSD 150 BPM 151 ARS 152 ARS_SD 153 CMDB 154 BiiZ 155 BIM 156 SLM 157 TM_ART 158 TM_RCA 159 TM_REM 160 EM_Server_Standby 161 SIM_Server_Standby 162 ADAP_SERVER_1 163 ADAP_SERVER_2 164 ADAP_CELL Chapter 5 Working with Infrastructure Management 141

138 Roles and permissions Roles and permissions The following group roles have full write permission to the components and features of the Infrastructure Management subtab: Service Administrators Full Access Only members of either group can view the Infrastructure Management subtab. Refer to Defining permissions on page 83 for information on assigning roles. Walkthrough This section provides a walkthrough of Infrastructure Management, highlighting its main features. You can use this walkthrough to learn about and become familiar with Infrastructure Management. Displaying the out-of-the-box real-time service model Infrastructure Management automatically deploys a BMC infrastructure service model, called BMC Impact Solutions. It consists of logical groupings of BMC services and applications, together with registered components that send all relevant information and latest statuses. The out-of-the-box service model reflects the realtime states of the registered components. To display the service model 1 In BMC Impact Explorer, click the Administration tab. 2 In the icon bar at the top of the navigation area on the left, click the Infrastructure Management icon (the wrench or spanner icon). 3 Under Find Infrastructure Components in the bottom pane of the navigation area, choose Find to list the services and applications. The logical groupings of components and applications are displayed, along with registered components. 142 BMC Impact Solutions Infrastructure Management Guide

139 Displaying the out-of-the-box real-time service model Alternatively, you can open the BEM Infrastructure Management group to display the navigation tree, as shown in Figure 15 on page 143. Figure 15 Infrastructure Management navigation pane 4 Locate the BMC Impact Solutions object in the Find list, and then, using the mouse, click and drag it into the graph viewing area in the top right pane to reveal the service model. You can also choose to select BMC Impact Solutions in the navigation tree under BEM Infrastructure Management to display it in the graph viewing area. You may need to click the Orientation icon at the top of the graph viewing area to reposition it vertically. The default service model should look similar to the example in Figure 16 on page 144. Chapter 5 Working with Infrastructure Management 143

140 Sampling context-sensitive information Figure 16 Default service model BMC Impact Solutions (with active services) The services and applications are color-coded to reflect their real-time status. You can check the multi-colored Status legend to see the status associated with each color. The grey-colored icons represent logical groupings, components whose status is unknown to the Impact Administration cell. Sampling context-sensitive information The Infrastructure Management interface offers a range of context-sensitive information that you can access from right-click pop-up menus and multi-layered notebook tabs. For example, you can expand the model and select a component under the SIM Cells heading. Click the leaf component under SIM Cells to select it. Click the Details tab. Click the subtabs such as General, Status, Priority and Cost, Advanced, Related Components, SLM, and Schedule. These tabs provide component specific information. Click the Administer tab. Click the subtabs such as Configuration, Logs, and Support Package. You can access the Workload and Components tabs if you have selected either a SIM or an EM cell server. Click Edit Component in the Details=>General tab and change a property of the component. 144 BMC Impact Solutions Infrastructure Management Guide

141 Managing files on remote systems Managing files on remote systems From the Infrastructure Management interface, you can edit and save the configuration and log files of other SIEM applications and services, both of which are running on remote systems. To edit and save configuration files 1 Click the leaf component under a service or an application, such as SIM Cells, to select it. 2 From the Notebook tabs, choose Administer=>Configuration. The drop list reveals the configuration files of the selected component. 3 To modify a file, select it from the list, and click Edit. The Credentials dialog box displays. The Additional command credentials check box applies mainly to UNIX systems, where you may need to log into the system under one user account, but then switch to another user account (for example, root) to execute the action. 4 In the dialog box, enter the credentials of the remote system, and click OK. The configuration file is displayed in the editor. Chapter 5 Working with Infrastructure Management 145

142 Packaging support files 5 Edit the file. 6 When you re done, you can click either of the following: File=>Save a Copy to save a copy of the file to your local system File=>Update Original to update the file on the remote system To edit and save log files 1 Click the leaf component under a service or an application, such as SIM Cells, to select it. 2 From the notebook tabs, choose Administer=>Logs. The drop list reveals the log files of the selected component. 3 To modify a file, select it from the list, and click View. 4 In the dialog box, enter the credentials of the remote system, and click OK. The log file is displayed in the editor. 5 Edit the file. 6 When you re done, click File=>Save a Copy to save a copy of the file to your local system. You cannot update a log file on a remote system. You can save it only to the local system. Packaging support files You can package selected debug files to help troubleshoot customer cases. Infrastructure Management automatically packages the selected files into a zipped file. 146 BMC Impact Solutions Infrastructure Management Guide

143 Packaging support files To package support files 1 Click on the leaf component under SIM Cells, for example, to select it. 2 From the Notebook tabs, choose Administer=>Support Package. 3 In the Destination field, enter the file path where the package should be saved on the local system. You can use the Browse button to navigate to the directory. The file name of the support package is created automatically. 4 Optional. Enter a tracking number in the Issue Number field. 5 Optional. Enter a description of the issue in the Description field. 6 Click Create Package. 7 Enter the credentials of the remote system from which you are retrieving the files. Chapter 5 Working with Infrastructure Management 147

144 Launching remote actions A pop-up progress indicator shows the status of the retrieval. If it completes successfully, go to the specified directory and review the contents of the zipped package. The file contents vary based on the type of component. Here are typical files for a SIM server component. 8 Repeat steps 1 through 7 for an Impact Administration Server component, verifying that the file contents of its zipped package are different from those of the SIM Cell. Launching remote actions From the Infrastructure Management interface, you can execute actions through the right-click pop-up menus on components and applications that are running on remote systems. To launch remote actions For this exercise, you must have a registered cell component installed on a remote system. 1 Right-click the leaf component under SIM Cells or EM Cells to select a cell residing on a remote system. 2 Choose Actions to display a list of all possible actions for that component. 3 Choose Stop Cell Server Process, click Stop, and enter the logon credentials for the remote system. If the selected component resides on an MS Windows system, your login credentials should have administrative rights to the system. The Additional Command Credentials are needed check box is disabled. 148 BMC Impact Solutions Infrastructure Management Guide

145 Common Infrastructure Management tasks When the component on the remote system has stopped, its status changes to Unavailable. 4 Return to the Infrastructure Management interface, right-click the SIM Cells component to display the pop-up menu, and choose Actions=>Start Cell Server Process. 5 Verify that the cell has started for example, you can execute an mcstat command to check the cell s status. Then you can verify that the status of the selected component is changed to OK. 6 Repeat steps 1 through 5 for a BMC Impact Administration Server (IAS) component. The actions permitted on this component are different from those of the EM or SIM Cell component. They are limited to Stop Process and Start Process. You can also launch remote actions for selected components by clicking one of the Action toolbar icons of the Infrastructure Management view. Depending on the type and state of the selected component, you can choose from among the following actions: Start Cell Server Process (Start) Stop Cell Server Process (Stop) Restart Cell Server Process (Restart) Pause Events Admittance (Pause) Resume Events Admittance (Resume) Set to Active Set to Standby Different actions are enabled based on the status and type of component. For example, if a component in an unknown state is already started and you choose Actions=>Start, you receive a status message notifying you that the component is started already. Refer to Remote actions on page 174 for more information. Common Infrastructure Management tasks This section describes the most common Infrastructure Management tasks. For the most part, you manipulate objects in the Infrastructure Management interface just as you would in the other BMC Impact Explorer Services tab views. Chapter 5 Working with Infrastructure Management 149

146 Navigating the interface Navigating the interface In the Administration tab view, select the Infrastructure Management subtab, represented by the wrench icon at the far right in the icon row atop the navigation pane: In the Of type drop-down list, click All if it s not already displayed. Click Find to open the list of logical groupings and registered components in your infrastructure. Logical groupings and registered components are depicted by different icons: Table 39 Icon listing for infrastructure management model (part 1 of 2) Icon Definition logical services grouping IAS (Impact Administration Server) SIM cell SIM cell server 1 SIM cell server 2 (high availability implementation) SIM cell server standby (high availability implementation) EM Cell EM cell server 1 EM cell server 2 (high availability implementation) BEM cell server standby (high availability implementation) OVO Fetcher BMC Portal Server 150 BMC Impact Solutions Infrastructure Management Guide

147 Navigating the interface Table 39 Icon listing for infrastructure management model (part 2of 2) Icon Definition BMC Publishing Server Integration for BMC Remedy Service Desk Select the BMC Impact Solutions grouping, which contains the default infrastructure model, and drag-and-drop it on the graph viewing area. You may need to select the Orientation icon to display it along a vertical axis. Multiple graphs You can display multiple graph views. For example, you can select registered components from the Results list in the navigation pane, and drag-and-drop them on the graph viewing area, creating new graph views. You can switch from one view to the other by selecting the tabs at the top of the graph viewing area. Navigation tree To help organize your model, you can display and manipulate the grouping and component hierarchy in the navigation tree view under the Infrastructure Management heading. You can select objects in the navigation tree and display them in the graph viewing area. You can drag objects from the graph viewing area and drop into the navigation tree, creating a navigation link between the two. TIP You can press the CTRL or SHIFT key and then click an object in the navigation tree to display the object in the graph viewing area without closing any displayed objects. Chapter 5 Working with Infrastructure Management 151

148 Displaying and understanding the Details and Administer tab data You can create customized subgroups under the Infrastructure Management heading. After selecting the heading, right-click to open the Add a sub group menu item. After you define your group, you can drag and drop component objects into it. Displaying and understanding the Details and Administer tab data The Details subtabs display information that identifies the characteristics of the selected component and returns its status. They let you perform common BMC IX actions, such as changing provider-consumer relationships between components. The Administer subtabs display specific infrastructure information and let you perform unique infrastructure actions, such as editing configuration and log files and collecting debug files for troubleshooting. To view data about an object in the interface, first select it. Then you can scan the corresponding subtabs under Details and Administer. To view information on one of the Administer tabs, the selected object must be a registered infrastructure component, not a greyed-out logical services group icon. Details tab data General In the General subtab, you can view the name, class, and subtype of the selected object. Depending on the subtype, you can also view other slot values, as described in Table BMC Impact Solutions Infrastructure Management Guide

149 Displaying and understanding the Details and Administer tab data Table 40 Slot Editable Here Slot values: Details: General subtab Description contains a Boolean Yes/No indicator that says whether the selected component object can be edited in BMC IX. Master Repository Run State Role Cell Type Cell Server 1 Cell Server 1 Port Cell Server 2 Cell Server 2 Port Infrastructure Management only contains objects that are not published. Therefore, Editable Here is always set to Yes in Infrastructure Management. specifies the data source of the component object. For example, component objects that originate from a direct feed source, such as BMC IX, mposter, or an MRL, are designated in this format: CellcellName. The default name for Infrastructure Management is Cell_Admin. the current state of the object, which helps to determine its status, its icon shape, the icon s color, as well as which actions can be performed against the object. This slot value is updated whenever the component changes its state, from start to stop, from start to paused, from stop to start, and so forth. indicates whether a component, such as a cell server or IAS, is standalone or, in an HA pair, either primary or secondary. identifies a selected cell component as Service Impact Management, Event Management, Impact Administration, or Integration. for a selected cell component, the IP address of the standalone cell server or of the primary cell server in an HA pair. for a selected cell component, the port number of the standalone cell server or of the primary cell server in an HA pair. for a selected cell component, the IP address of the secondary cell server in an HA pair. for a selected cell component, the port number of the secondary cell server in an HA pair. From the General subtab, you can click Edit Component to open the Edit Service Component dialog in which you can modify the component s properties. Status In the Status subtab, you can view the applicable status levels of the component: Service Level Agreement, manual status, maintenance mode, and computation statuses. Priority and Cost Under the Priority and Cost subtab, you can view the schedule status, impact priority, and impact cost. Chapter 5 Working with Infrastructure Management 153

150 Displaying and understanding the Details and Administer tab data Advanced In the Advanced subtab, you can view information on identification, creation and modification time, and read/write permissions for groups for the selected object. Related Components In the Related Components subtab, you can retrieve status causes, possible problems, providers, and consumers of the selected component type. You can modify the relationship by selecting Edit Relationship..., which opens the Edit Relationships dialog where you can add, modify, or remove relationships. Using the right-click menu options, you can highlight a retrieved component in the list, and add a link to the navigation tree by choosing the Add Navigation Link option. You can view the events associated with the component. This subtab also lets you view other components that have relationships with the selected component. SLM In the SLM subtab, you can list and view the details of Service Level Management agreements assigned to the component. This subtab view is not available for the Admin cell (IAC). Schedule In the Schedule subtab, you can view the times when the component is in service together with its priority costs when it is in service and when it is out of service. This subtab view is not available for the Admin cell (IAC). Administer tab data Configuration The Configuration subtab lists the editable configuration files of the selected component. You can retrieve these files, even those associated with components on remote systems. Click Edit. Then enter the logon credentials for the system where the component resides. (On UNIX, your login account must have permission to access the target system. On MS Windows, you must have administrative privileges on the system.) The file opens in a default text editor. 154 BMC Impact Solutions Infrastructure Management Guide

151 Displaying and understanding the Details and Administer tab data You can edit any supported configuration file of an infrastructure component. The type of file varies with the component, but the files include: mcell.dir.conf files filter files selector files mapping files trace.conf files cell_info.list You should know the parameters of the file before trying to edit it. Refer to the component s respective documentation. You can save the edited configuration file to a local or remote system. If saving to a local system, you can specify a different file path. If saving to a remote system, you update the configuration file in its current directory path. You cannot save it to a different file path. Logs Similar to configuration files, you can open and annotate log files of components on local systems in the Log subtab. You cannot save an edited or update a viewed log file to a remote system, however. You must save it to the local system. Support Package In the Support Package subtab, you can prepare a zipped package of predefined support files for troubleshooting purposes. See Creating the support package on page 169 for more information. Workload The Workload subtab dynamically tracks the event activity of the cell server component. It presents counts, averages, and percentages of different event actions, such as sent, received, dropped, and removed. You can refresh the table by clicking the Refresh button. This subtab view is available for SIM cell servers, but not for BEM cell servers. Components The Components subtab dynamically tracks the component instances that send events to the selected object. You refresh the table by clicking the Refresh button. This subtab view is available for SIM and BEM cell servers. Chapter 5 Working with Infrastructure Management 155

152 Editing infrastructure relationships Editing infrastructure relationships To open the Edit Relationships dialog box, select an infrastructure object in the graph area. Then do one of the following: Select the Related Components subtab from the Details notebook tab. Click the Edit Relationship... button. Click Edit => Edit Relationship. Click the Edit Relationship toolbar icon. The Edit Relationships dialog box is opened. Figure 17 on page 156 shows an open Edit Relationships dialog box with a selected SIM cell opened for editing in the Edit This Relationship subdialog. Figure 17 Edit Relationships dialog with Edit This Relationship subdialog The Edit Relationships dialog box contains the following fields: Table 41 Edit Relationship dialog: field descriptions (part 1 of 2) Field Component Name Related Component Type Relationships Description name of the selected infrastructure component identifies the infrastructure component subtype that has a consumer or provider relationship to the selected component and for which you want to search lists the consumer, provider, or both consumer and provider relationships of the selected component subtype and component 156 BMC Impact Solutions Infrastructure Management Guide

153 Creating logical components Table 41 Edit Relationship dialog: field descriptions (part 2of 2) Field Component Direction State Type Propagation Model Editable Description identifies the infrastructure object related to the selected component indicates the event flow of the object relationship. A consumer direction indicates that the component object receives events and data from the selected component. A provider direction indicates that the component object sends events and data to the selected component identifies current state of the relationship: active or inactive specifies the class that contains the relationship type identifies the status propagation model used for determining the propagated status from the provider s main status indicates whether you can edit the object in BMC IX You can search on component types by selecting an Impact Administration subtype from the drop-down list. When you click Search, it retrieves the relationships associated with the selected subtype. Select an item in the Edit Relationships dialog, and right-click to open the pop-up menu. You can perform actions common to all object relationships: View Service Impact Graph, View Events, Edit Component, Add Navigation Link, and Add Relationship. You can edit any of the component s relationships by selecting it and then choosing the Edit Relationship button at the bottom of the dialog. The Edit This Relationship subdialog contains the following fields: Table 42Edit This Relationship subdialog Field Consumer/Provider indicator Type of Relationship Relationship Status Status Weight Description Description indicates the directional flow of the relationship between the selected component and the component subtype. You can modify the relationship Direct, Increasing, Decreasing, Just_Info, or Just_Warning Active or Inactive weight (numeric value) of a relationship used while calculating the status using weighted cluster mode Summary description of the relationship Creating logical components You can add logical components to the Infrastructure Management service model. Logical components in this context refer to components that do not have a predefined registration event associated with them, as do the BMC infrastructure components listed in Table 38 on page 140. Chapter 5 Working with Infrastructure Management 157

154 Deleting components Although logical components are not registered with the IAC and therefore do not provide real-time status information, they can help to complement the BMC infrastructure model. For example, you can add logical integrations and server processes to the model to represent an idealized infrastructure environment. NOTE The names of logically created components do not display in Korean in the graph viewing area while its component object does. Deleting components You can delete both logical service groupings/objects and live, registered objects from the Infrastructure Management service model. To organize your service model around its real-time components, you can delete logical groupings that do not have registered components associated with them. Generally, you should delete the leaf objects, not objects that lie between other objects. If you delete objects that lie between other objects, some objects that should be deleted because of relationship associations with the other objects will nonetheless remain. BMC recommends that you do not delete components that have been registered automatically with the Infrastructure Management service model. However, if you delete a live, registered object, it is removed from the Infrastructure Management service model, and an event of the class Service Model Component Delete is sent to the IAC. TIP You can recover a deleted registered object by modifying the DATA/ADMIN_DATA/ ADMIN_REGISTRATIONS table of the IAC in the Administration tab view. You change the enable parameter for the specific component from NO to YES in the Edit tab. Then you restart the component to reregister it. 158 BMC Impact Solutions Infrastructure Management Guide