×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

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.
BMC Cloud Lifecycle Management 3.1 ... Installing Installing products for HA

Installing products on the secondary node for HA

This topic was edited by a BMC Contributor and has not been approved.  More information.

The following sections discuss installing the supporting products in the secondary node, in a high availability (HA) environment.

Installing the Secondary Enterprise AR

  1. Click the secondary enterprise AR System server node on IP to start installation.
  2. Provide same database information that was specified during primary enterprise AR System server installation.
  3. Continue with Post Install configuration and DSO.

Installing the Secondary Cloud AR

  1. Click the secondary cloud AR System server node on IP to start installation.
  2. Specify same database information that was provided during primary cloud AR System server installation.
  3. Specify same port information that was specified during primary Cloud AR installation.
  4. Continue with Post Install configuration and DSO.

Installing the Secondary Cloud Portal AR Extension

  1. Continue with Cloud Portal AR Extension
  2. Specify correct secondary enterprise AR System server information

  1. Follow all instruction to install Secondary Cloud Portal AR Extension.

Installing the Secondary Atrium Web Registry

  1. Copy the Atrium Web Registry installer from the install host machine to secondary Atrium Web Registry VM.
  2. Delete Atrium Web Registry related Name and Version entries from the Share:Application_Properties form on enterprise AR System server. Back up the enterprise AR System server database before performing this step.
  3. Start Installation and provide similar information that you provided during primary Atrium Web Registry information.

Installing the Secondary Platform Manager on a Cluster

  1. Failover the cluster to secondary node.

  2. For Windows create BMC CSM and Quick start services manually using the following command:

    sc create BMCCSM binPath= "\"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\wrapper.exe\" -s \"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\wrapper.conf\"" DisplayName= "BMC CSM"
sc create BMCQuickStart binPath= "\"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\quickstart.exe\" -s \"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\quickstart.conf\"" DisplayName= "BMCQuickStart"

  3. For Linux create softlink for BMC CSM and Quick start service in /etc/init.d.

    ln -s /gfs/bmc/BMCCloudLifeCycleManagement/Platform_Manager/sh.script.in /etc/init.d/bmccsm
ln -s /gfs/bmc/BMCCloudLifeCycleManagement/Platform_Manager/QuickStart/sh.script.in /etc/init.d/BMCQuickStart

Was this page helpful? Yes No Submitting... Thank you
Last modified by Fran Coughlin on Apr 26, 2013
bmc_contributor contributor_unapproved

Comments

Log in or register to comment.

Installing the primary Cloud Portal AR Extension for HA
Configuring after installation
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© 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.