Configuring a CI Type as a service on the TrueSight console


You can select different CI Types to be configured as Services on the TrueSight console. This feature enables you to monitor different CI Types as Services on the Services page.

When you select a specific CI Type as a service, the relevant CIs of that CI Type are listed as Services on the Services page. Once these CIs are listed as Services, you can perform any of the following operations :

Note

In TrueSight Operations Management versions earlier than 11.0, only the Business Service CI Type is configured as a service by default. You cannot configure other CI Types as services.

You can configure either predefined CI Types or user-defined CI Types as Services. Predefined CI Types are already defined CI Types available in TrueSight Infrastructure Management, for example Application, DataBase, Business Process, Organization etc. The user-defined CI Types can be created in the BMC Atrium CMDB. The following sections explain the prerequisites and the procedure to configure CI Types as services.

Before you begin

  • To configure a CI Type as a Service, ensure that you have Solution Administrator level access.

  • To configure a predefined CI Type as a Service, ensure that the TrueSight Infrastructure Management is registered as a component with TrueSight Presentation Server.
  • To configure a user-defined CI Type as a Service, ensure that the BMC Atrium CMDB is integrated with the TrueSight Infrastructure Management, and this TrueSight Infrastructure Management is registered as a component with TrueSight Presentation Server.

To configure a CI Type as a service

The following video (6:06) illustrates how to configure CI Types as services to monitor them on TrueSight console.

Click here to see the video that explains how to configure CI Types as services

icon_play.png https://youtu.be/laG_43J9nxY.

Perform the following sequence of steps to configure a CI Type as a service:

  1. In the TrueSight console, select Monitoring > Services
  2. On the Services page, click the action menu callout_1.png and select Configure CI Types as shown in the following figure:
    config_citypes.png


  3. Select CI Types to configure as Services dialog box is displayed with a list of CI Types.
    citypes_dialogbox.png

    Note

    • Select CI Types to configure as Services dialog box displays 17 predefined CI Types. If you want to configure additional CI Types (predefined and user-defined) as Services, run the tssh command. For step by step instructions, see To configure additional CI Types as a services.
    • CI Type list gets updated at a time interval of 20 minutes. If you find any discrepancy in the CI Type list and want to see the updated list immediately, restart the TrueSight Presentation Server.
  4. Select a check box for choosing a specific CI Type. To search a specific CI Type, type the CI Type name in the search box and press Enter.

    Note

    Business Service is a mandatory CI Type that is configured by default. You can select a maximum of 20 CI Types.


    Recommendation
    Configure top level CI Types such as Application, Application System, Cluster, Organization etc. as services for better monitoring of services in your environment.

  5. Click Save to apply the configuration. 

After the configurations are applied successfully, these CIs can be monitored as Services on the Services page.

Note

Once the solution administrator selects different CI Types to configure them as services, the changes are applied to all the users. These changes persist between user sessions.

 

To configure additional CI Types as a services

You can configure a maximum of 17 predefined CI Types as services from the Services page of the TrueSight console. The following table represents the complete list of predefined CI Types available in TrueSight Infrastructure Management. To configure any additional CI Types (predefined and user-defined) those are not listed when you click Configure CI Types option on the Services page, run the tssh command as explained in the following section.

CI Type Name

Icon

CI Type Name

Icon

CI Type Name

Icon

CI Type Name

Icon

Activity

CI_Activity.png

Connectivity Segment

CI_ConnectivitySegment.png

Logical Entity

CI_LogicalEntity.png

Storage Extent

CI_SoftwareExtend.png

Application

CI_Application.png

Database

CI_Database.png

Logical System

Component

CI_LogicalSysComp.png

Storage Subsystem

CI_SubSystem.png

Application Infrastructure

 CI_AppInfra.png

Database Storage

CI_DatabaseStorage.png

Mainframe

CI_Mainframe.png

Storage Volume

CI_StorageVolume.png

 Application Service

 CI_AppService.png

Disk Drive

CI_DiskDrive.png

Media

CI_Media.png

System

CI_System.png

Application System

CI_AppSystem.png

Disk Partition

CI_DiskPartition.png

MF Coupling

Facility

CI_MfCouplingFacility.png

System Component

CI_SystemComponent.png

Base Element

CI_BaseEle.png

File System

CI_FileSystem.png

Offering

CI_Offering.png

System Resource

CI_SystemResource.png

Business Process

CI_BusinessProc.png

Floppy Drive

CI_FloppyDrive.png

Operating System

CI_OperatingSystem.png

System Service

CI_SystemService.png

Business Service

CI_BusinessService.png

Hardware Package

CI_HardwarePkg.png

Organization

CI_Organization.png

System Software

CI_SystemSoftware.png

CD ROM DRIVE

CI_CDROM.png

Hardware System Component

CI_hardwareSysComp.png

Physical Location

CI_PhysicalLoc.png

Tape Drive

CI_TapeDrive.png

Chassis

CI_Chassis.png

IP Connectivity Subnet

CI_IpConnSubnet.png

Remote File System

CI_RemoteFileSys.png

Transaction

CI_Transaction.png

Cluster

CI_Cluster.png

IPX Connectivity Network

CI_IpxConnNetwork.png

Resource Pool

CI_ResourcePool.png

UPS

CI_Ups.png

Collection

CI_Collection.png

LAN

CI_LAN.png

Service Offering

CI_ServiceOffering.png

User Community

CI_UserCommunity.png

Concrete Collection

CI_ConcreteCollection.png

LNs Collection

CI_lnsCollection.png

Service Offering

Instance

CI_ServiceOffering_Instance.png

Virtual System Enabler

CI_VirtualSystemEnabler.png

Connectivity Collection

CI_ConnCollection.png

Local File System

CI_LocalFileSystem.png

Software

CI_Software.png

WAN

CI_WAN.png

 

 

Logical Disk

CI_LogicalDisk.png

Software Server

CI_SoftwareServer.png

User-defined CI Type

CI_SystemComponent.png

  1. Navigate to the <Presentation Server Installation Directory>\truesightpserver\bin directory location.
  2. Run the following command at the command prompt to configure additional CI Types as services:

    #Syntax
    tssh properties set include.citypes.as.service <CI Types list seperated by comma>
    #Example
    tssh properties set include.citypes.as.service bmc_lan,bmc_wan,bmc_collection

    In the preceding command, bmc_lan, bmc_wan, bmc_collection are the names of the CI Types that will be included in the CI Type list.

     

     

  3. Run the following command to reload the properties set in the preceding command:

    tssh properties reload
  4. In the TrueSight console, select Monitoring > Services
  5. On the Services page, click the action menu callout_1.png and select Configure CI Types as shown in the following figure:
    config_citypes.png

  6. Select CI Types to configure as Services dialog box is displayed with a list of CI Types. This list now displays additional CI Types those were included through tssh command as highlighted in the following figure:
    additional_CITypes.png

     

  7. Select check boxes representing LAN,WAN, and Collection CI Types. 
  8. Click Save to apply the configuration. 

After the configurations are applied successfully, these CIs can be monitored as Services on the Services page.

Note

  • Once the solution administrator selects different CI Types to configure them as services, the changes are applied to all the users. These changes persist between user sessions.
  • Run the tssh properties command again, to delete any additional CI Types added through the tssh command. For example if you have added the CI Types bmc_lan, bmc_wan, bmc_collection by running the command tssh properties set include.citypes.as.service bmc_lan,bmc_wan,bmc_collection. Now if you want to delete bmc_wan from the CI Types list, then run the following command excluding the CI Type that needs to be deleted tssh properties set include.citypes.as.service bmc_lan,bmc_collection

 


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*