• Spaces
  • Collections
  • Help
    • ×
     
     
    •  
    BMC TrueSight Infrastructure Management 10.0

    Page tree

    Unsupported content

     

    This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

    During the installation process, you have the option to configure the BMC TrueSight Infrastructure Management Server integration with BMC Atrium CMDB. If you did not configure the BMC Atrium CMDB integration during installation, you can configure it now.

    Warning

    Before you configure integration with BMC Atrium CMDB, ensure that BMC CMDB Extensionsare installed on the computer where the BMC Atrium CMDB is installed. For information about installing the CMDB extensions, see Preparing for BMC Atrium CMDB integration.

    Notes

    • To ensure that all folders are deleted during the uninstallation of BMC Atrium CMDB, run the integrate_atrium_cmdb command inside the pw directory.
    • The UDDI parameters in the integrate_atrium_cmdb command are optional because UDDI is not mandatory for Infrastructure Management to integrate with BMC Atrium CMDB. If UDDI is not configured then there will be no cross launch from operator console into the federated links configured in BMC Atrium CMDB.
    • If UDDI is configured for HTTPS, set bmc.uddi.registryserver.secure.enabled=true  in the pw\custom\conf\pronet.conf file and restart TrueSight Infrastructure Management server before running the integrate_atrium_cmdb  script.

    Use the following script:

    integrate_atrium_cmdb [-uddi_server_host_name <uddiServerHostName>] [-uddi_server_port_no <uddiServerPortNumber>] [-uddi_user_name <uddiUserUame>] [-uddi_password  <uddiPassword>] -cmdb_server_host_name <cmdbServerHostName> -cmdb_server_port_no <cmdbServerPortNumber> -cmdb_user_name <cmdbUserName> [-cmdb_password  <cmdbPassword>] -cmdb_version <cmdbVersion> [-bppm_webserver_protocol <webServerProtocol>] [-bppm_webserver_port_no <proactiveNetWebServerPortNumber>] [-enterprise (T|F)]

    where,

    • cmdbServerHostName is the host name where BMC Atrium CMDB is running. For integration with an AR Server Group, cmdbServerHostName is the AR Server load balancer host name or the AR Server integration server host name
    • cmdbServerPortNumber is the BMC Remedy Action Request System TCP port number, used to log into the system server
    • cmdbUserName is the user name to access the BMC Remedy Action Request System server

    Use the following optional arguments if you need Infrastructure Management to cross-launch into other Atrium applications:

    • (Optional) uddiServerHostName is the host name of the UDDI web service where BMC Atrium CMDB is running
    • (Optional) uddiServerPortNumber is the port number used by the UDDI web service on the specified host
    • (Optional) uddiUserUame is the user name for the UDDI web service
    • (Optional) uddiPassword is the password for the UDDI web service user
    • (Optional) cmdbPassword is the password for the BMC Remedy Action Request System server user

    Note

    All user names and passwords are case sensitive.

    Use the following optional arguments if you need to enable the cross-launch into Infrastructure Management:

    • webServerProtocol is the ProactiveNet web server protocol, either http (default) or https.
    • proactiveNetWebServerPortNumber is the ProactiveNet web server port number. The default value is 80.
    • -enterprise (T|F) indicates whether or not your enterprise environment has multiple BMC TrueSight Infrastructure Management Servers that will be communicating with the same CMDB.

    For example:

    integrate_atrium_cmdb -uddi_server_host_name Vm-w23-rds1184 -uddi_server_port_no 8080 -uddi_user_name admin -uddi_password admin -cmdb_server_host_name Vm-w23-rds1183 -cmdb_server_port_no 5555 -cmdb_user_name Admin -cmdb_password Admin -cmdb_version 7.6.04 -bppm_webserver_protocol https -bppm_webserver_port_no 8888 -enterprise T

    If you integrate with BMC Atrium CMDB in an AR Server Group, you must manually configure the pserver.conf file. Edit the ARSGroupMembers in the pserver.conf file and set to all AR Servers of the group that have reconciliation function enabled. See also Configuring the Publishing Server to integrate with an AR Server group.

    If you run integrate_atrium_cmdb without providing UDDI settings and later require cross launch, then at that time you can configure the UDDI settings via the pw cmdb settings command.

    At the time of installation, if you have selected not to integrate BMC Atrium CMDB, then you need to configure IBRSD. Edit the ARSServerName parameter in the IBRSD.conf and IBRSD.dir files, located in the /pw/integrations/ibrsd/conf directory.

    Note

    If you are running Infrastructure Management in high-availability mode, to integrate with BMC Atrium CMDB, you must run the integrate_atrium_cmdb command on both the primary and secondary nodes.

    To integrate Infrastructure Management with BMC Atrium Service Context, see Enabling cross-launch to BMC Atrium Service Context.

    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.