×
 
 
  •  
$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 4.6 ... Upgrading Verifying upgraded products

CLM product configuration files after upgrade

After you finish upgrading BMC Cloud Lifecycle Management, perform the following tasks:

  1. Review every file mentioned in the following table where the values are not retained post-upgrade.
  2. Check for the parameters whose values are changed. 
  3. Compare the latest version of the file with the backed-up version. 

This topic contains the following information:

Product configuration files after upgrade

Product filesValues retained if you upgrade?
Platform Manager 

cloudservices.json

Linux : <PM_Install_Directory>/Platform_Manager/configuration/cloudservices.json
Windows : <PM_Install_Directory>\Platform_Manager\configuration\cloudservices.json

(error)

providers.json

Linux: <PM_Install_Directory>/Platform_Manager/configuration/providers.json
Windows: <PM_Install_Directory>\Platform_Manager\configuration\providers.json

(error)

wrapper.conf

Linux: <PM_Install_Directory>/Platform_Manager/wrapper.conf
Windows: <PM_Install_Directory>\Platform_Manager\wrapper.conf

(error)

config.ini

Linux: <PM_Install_Directory>/Platform_Manager/configuration/config.ini
Windows: <PM_Install_Directory>\Platform_Manager\configuration\config.ini

(error)

csm-bootstrap.properties

Linux: <PM_Install_Directory>/Platform_Manager/csm-bootstrap.properties
Windows: <PM_Install_Directory>\Platform_Manager\csm-bootstrap.properties

(error) For safety, verify any parameters that were customized in this file.

actionCatalogs

Linux: <PM_Install_Directory>/Platform_Manager/configuration/actionCatalogs
Windows: <PM_Install_Directory>\Platform_Manager\configuration\actionCatalogs

(error)

email-templates

Linux: <PM_Install_Directory>/Platform_Manager/configuration/email-templates
Windows: <PM_Install_Directory>\Platform_Manager\configuration\email-templates

(error)
BMC Server Automation 

Config Server

Use the BMC Server Automation Console to enter Application Server settings as required. Your changes are stored in the database.

  1. Open the BMC Server Automation Console.
  2. Go to Configuration > Infrastructure Management.
  3. Expand Application Servers.
  4. Right-click the config_deployment object (for example, config_deployment_clm-hou-008414).
  5. Select Edit.
  6. Set MaxHeapSize to 2048.
  7. Click OK.

(tick)

Job Server

Use the BMC Server Automation Console to enter Job Server settings as required. Your changes are stored in the database. 

  1. Open the BMC Server Automation Console.
  2. Go to Configuration > Infrastructure Management.
  3. Expand Application Servers.
  4. Right-click the job_deployment object (for example, job_deployment_1_clm-hou-008414).
  5. Select Edit.
  6. Set the following values:
    • MaxHeapsize = 2048
    • MaxJobs = 75
    • MaxWorkItemThreads = 120
  7. Click OK.
(tick)

secure

Linux: /etc/rsc/secure or /opt/bmc/rscd/NSH/conf/secure
Windows: C:\Windows\rsc\secure

(tick)

BBSA Agent on vCenter host

AssetImplConfig.xml

Windows: <AgentHome>\daal\Implementation\BMC_VMware_VirtualInfrastructureManager_win64\ win64\AssetImplConfig.xml

(tick)

deployments

Linux: <bl_install_dir>/NSH/br/deployments
Windows: <bl_install_dir>\NSH\br\deployments 

This directory contains all the various configuration settings for the Application Server.

(tick)

AppServerProfiles.xml

Linux: <bl_install_dir>/NSH/br/AppServerProfiles.xml
Windows: <bl_install_dir>\NSH\br\AppServerProfiles.xml

Exists if you are running multiple instances of the Application Server.

(tick)

bladelogic.keystore

Linux: <bl_install_dir>/NSH/br/deployments/bladelogic.keystore
Windows: <bl_install_dir>\NSH\br\deployments\bladelogic.keystore

(tick)

Custom NSH scripts

Linux: <bl_install_dir>/NSH/scripts
Windows:  <bl_install_dir>\NSH\scripts

(tick)

sensors

Linux : <bl_install_dir>/NSH/share/sensors
Windows: <bl_install_dir>\NSH\share\sensors

(tick)
Enterprise-AR and Cloud-AR 

ar.cfg

Linux:  <ARS_Home>/conf/ar.cfg
Windows: <ARS_Home>\Conf\ar.conf

(error) 

armonitor.cfg

Linux:  /etc/arsystem/<hostname>/armonitor.cfg
Windows: <ARS_Home>\Conf\armonitor.conf

(error) For safety, verify any parameters that were customized in this file.

pluginsvr_config.xml

E-AR Linux:
<ARS_Home>/pluginsvr/pluginsvr_config.xml
<Cloud_Portal_Home>/Cloud_Portal/plugin/pluginsvr_config.xml

E-AR Windows:
<ARS_Home>\pluginsvr\pluginsvr_config.xml
<Cloud_Portal_Home>\Cloud_Portal\plugin\pluginsvr_config.xml

C-AR Linux:
<ARS_Home>/pluginsvr/pluginsvr_config.xml

C-AR Windows:
<ARS_Home>\pluginsvr\pluginsvr_config.xml

(error) For safety, verify any parameters that were customized in this file.

CAI Plugin Registry

  1. Log on to the Mid Tier.
  2. Open the CAI Plugin Registry form.
  3. Review the settings.
    Required settings are stored in the database.
(error) For safety, verify any parameters that were customized in this file.
Mid Tier 

config.properties

Linux: <MidTier_Install>/WEB-INF/classes/config.properties
Windows: <MidTier_Install>\midtier\WEB-INF\classes\config.properties

(tick)

server.xml

Linux: < Tomcat_Install>/conf/server.xml
Windows: <Tomcat_Install>\conf\server.xml

(error) 

tomcat6w/startup.sh

Linux: <Tomcat_Install>/bin/startup.sh
Windows: <Tomcat_Install>\bin\tomcat6w.exe

(tick)
BMC Atrium Orchestrator 

Access Manager and Repository .lax/server.sh

Linux: <AMREPO_Install>/bin/server.sh
Windows: <AMREPO_Install>\bin\BMC Atrium Orchestrator Access Manager and Repository.lax

(error) 

Access Manager and Repository bao.sh

Linux: <AMREPO_Install>/bin/bao.sh

(error) 

Access Manager and Repository repository.xml

Linux:
<AMREPO_Install>/repository/config/repository.xml

Windows:
<AMREPO_Install>\repository\config\repository.xml

(error) 

Configuration Distribution Peer
BMC Atrium Orchestator CDP.lax/server.sh

Linux: <CDP_Install>/bin/server.sh
Windows: <CDP_Install>\bin\BMC Atrium Orchestrator CDP.lax

(error) 

Configuration Distribution Peer bao.sh

Linux: <AMREPO_Install>/bin/bao.sh

(error) 

Configuration Distribution Peer log4j.xml

Linux: <CDP_Install>/tomcat/webapps/baocdp/WEB-INF/classes/log4j.xml
Windows: <CDP_Install>\tomcat\webapps\baocdp\WEB-INF\classes\META-INF\classes\log4j.xml

(error) 
BMC Network Automation 

BcanInstalledConfiguration.xml

Linux: <BCA_NETWORKS_INSTALL_DIR>/BcanInstalledConfiguration.xml
Windows: <BCA_NETWORKS_INSTALL_DIR>\BcanInstalledConfiguration.xml

(tick)

database.properties

Linux: <BCA_NETWORKS_DATA_INSTALL_DIR>/database.properties
Windows: <BCA_NETWORKS_DATA_INSTALL_DIR>\database.properties

(error)

logging.properties

Linux: <BCA_NETWORKS_DATA_INSTALL_DIR>/logging.properties
Windows: <BCA_NETWORKS_DATA_INSTALL_DIR>\logging.properties 

(error) 

server.xml

Linux: <BCA_NETWORKS_INSTALL_DIR>/tomcat/conf/server.xml
Windows: <BCA_NETWORKS_INSTALL_DIR>\tomcat\conf\server.xml

(error) 
BMC Capacity Optimization 

freetds.conf

Linux: /opt/cpit/etl/freetds/etc/freetds.conf

(tick)

server.xml

Linux : %BCO_HOME%/web/tomcat/conf/server.xml

(tick)

User configurations

User configurations in the BCO database

(tick)
BMC Database Automation 

Manager Configuration (Manager Host)

Linux: <BDA_Install_Dir>/dmanager/etc/dmanager.conf

(tick) 

Middle Tier Configuration (Manager Host)

Linux: <BDA_Install_Dir>/dmanager/etc/mtd.conf

(tick) 

GUI Configuration (Manager Host)

Linux: <BDA_Install_Dir>/dmanager/etc/d2500_config

(tick) 

GUI PHP Configuration (Manager Host)

Linux: <BDA_Install_Dir>/etc/php.ini

(error) Partial – Some values reset on upgrade 

GUI Web Server Configuration (Manager Host)

Linux:

/etc/httpd/etc/conf/httpd.conf

/etc/httpd/etc/conf.d/gridapp.conf

(error) Partial – Some values reset on upgrade 

MultiManager Configuration (Manager Host)

Linux: <BDA_Install_Dir>/dmanager/etc/mesh.conf

(tick) 

Agent Configuration (Agent Host)

Linux/Unix: <BDA_Install_Dir>/dagent/etc/dagent.conf

Windows: <BDA_Install_Dir>\dagent.conf

(tick)

Where to go next

To achieve optimal performance with BMC Cloud Lifecycle Management, review the parameters listed in Performance tuning parameters.

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.

Last modified by Lisa Greene on Mar 27, 2017

Comments

Log in or register to comment.

CLM upgrade log files
Configuring upgrades
© Copyright 2013 - 2017 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.