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

Product configuration files after upgrade


After you finish upgrading BMC Cloud Lifecycle Management, you must review every file mentioned in the following table where the values are not retained post-upgrade and check for the parameters whose values have got changed. Compare the latest version of the file with the backed-up version. 

This topic contains the following information:

Before you begin

Review Product-configuration-files-before-upgrade.

Product configuration files after upgrade

Product files

Values retained after upgrade?

Platform Manager

 

cloudservices.json

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

❌️

providers.json

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

❌️

wrapper.conf

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

❌️

config.ini

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

❌️

csm-bootstrap.properties

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

❌️ Check for safety if any parameter is customized in this file.

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.

✅️

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.

✅️

secure

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

 

BBSA Agent on vCenter host

AssetImplConfig.xml

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

✅️

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.

✅️

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.

✅️

bladelogic.keystore

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

✅️

Custom NSH scripts

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

✅️

Sensors

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

✅️

Enterprise-AR and Cloud-AR

 

ar.conf

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

❌️ 

armonitor.conf

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

❌️ Check for safety if any parameter is 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

❌️ Check for safety.

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.

❌️ Check for safety.

Mid Tier

 

config.properties

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

✅️

server.xml

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

❌️ 

tomcat6w/startup.sh

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

✅️

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

❌️ 

Access Manager and Repository bao.sh

Linux: <AMREPO_Install>/bin

❌️ 

Access Manager and Repository repository.xml

Linux:
<AMREPO_Install>/repository/config
<AMREPO_Install>/tomcat/webapps/baorepo/WEB-INF/classes/META-INF

Windows:
<AMREPO_Install>\repository\config
<AMREPO_Install>\tomcat\webapps\baorepo\WEB-INF\classes\META-INF

❌️ 

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

❌️

Configuration Distribution Peer bao.sh

Linux: <AMREPO_Install>/bin

❌️

Configuration Distribution Peer log4j.xml

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

❌️

BMC Network Automation

 

BcanInstalledConfiguration.xml

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

✅️

database.properties

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

❌️

logging.properties

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

❌️ 

server.xml

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

❌️ 

BMC Capacity Optimization

 

freetds.conf

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

✅️

server.xml

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

✅️

User configurations

User configurations in the BCO database

✅️

BMC Database Automation

 

Manager Configuration (Manager Host)

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

✅️ 

Middle Tier Configuration (Manager Host)

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

✅️ 

GUI Configuration (Manager Host)

Linux: <BDA_Install_Dir>/dmanager/etc/d2500_config

✅️ 

GUI PHP Configuration (Manager Host)

Linux: <BDA_Install_Dir>/etc/php.ini

❌️ 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

❌️ Partial – Some values reset on upgrade 

MultiManager Configuration (Manager Host)

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

✅️ 

Agent Configuration (Agent Host)

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

Windows: <BDA_Install_Dir>\dagent.conf

✅️

Recommended settings

After you compare the latest version of the file with the backed-up version, manually update these parameters to their recommended values.

Platform Manager

Apply the following settings to the Platform Manager configuration files:

Configuration file

Recommended value

cloudservices.json

Maximum Connections = 50

 

Maximum number of connections = 50

 

Number of task manager threads = 100

 

Maximum number of task manager threads = 300

providers.json

"name" : " BBSA_MAX_WEBSERVICES_SESSIONS " }, "attributeValue" : "1",

 

name : "BBSA_VG_JOB_STATUS_POLLS " }, "attributeValue" : "240",

 

name:BBSA_VG_JOB_STATUS_POLL_INTERVAL_SECONDS"}, "attributeValue" : "15",

 

“name" : BBSA_USP_JOB_STATUS_POLLS " }, "attributeValue" : "240"

 

“name" : BBSA_USP_JOB_STATUS_POLL_INTERVAL_SECONDS " }, "attributeValue" : "15"

 

name : "BBSA_SCRIPT_JOB_STATUS_POLLS" }, "attributeValue" : "240"

 

name:"BBSA_SCRIPT_JOB_STATUS_POLL_INTERVAL_SECONDS"}, "attributeValue" : "15"

 

name:BBSA_SOFTWARE_JOB_STATUS_POLLS" },"attributeValue": "240"

 

name:BBSA_SOFTWARE_JOB_STATUS_POLL_INTERVAL_SECONDS"}, "attributeValue" : "15"

 

name : "BBSA_VG_AGENT_STATUS_POLLS" }, "attributeValue" : "240"

 

name:"BBSA_VG_AGENT_STATUS_POLL_INTERVAL_SECONDS" }, "attributeValue" : "15"

wrapper.conf

Not applicable

BMC Server Automation

Apply the following settings to the BMC Server Automation configuration files:

Configuration file

Recommended value

App Server

2 GB Heap Size

Do not use the Application Server as the Job Server.

Job Server

MaxJobs = 75 (per Job Server)

 

MaxWorkItems = 120 (per Job Server)

 

Affinity Rules:
"_VG_Job_"
 "_USP_Job_"
 "_create_user_job_"

C:\WINDOWS\rsc\secure

rscd:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls:timeout=120
default:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls:timeout=120

BBSA Agent on vCenter host

<AgentHomeDirectory>\8.1\RSCD\daal\Implementation\BMC_VMware_VirtualInfrastructureManager_win64\win64\AssetImplConfig.xml,
'assetImpl_coServerMaxThreadCount' = 100.

In addtion, review the following BMC Server Automation settings.

File name

Parameter

Recommended value

Additional information

config_deployment

Max Heapsize

2048

Values are retained if modified and upgraded.

Job_Deployment

Max Heapsize
maxThreads
maxWorkItemThreads

2048
75
120

Values are retained if modified and upgraded.

Manually created Job Deployment

Max Heapsize
maxThreads
maxWorkItemThreads

2048
75
120

Values are retained if modified and upgraded.

secure

timeout

120

Values are retained if modified and upgraded.

Enterprise-AR and Cloud-AR

Apply the following settings to the Enterprise-AR and Cloud-AR configuration files:

Configuration file

Setting

Value

Additional information

ar.conf (Linux)
armonitor.conf (Windows)

AR Server tag 

Recommended value 

Configuration parameter and value

 

Delay-Recache-Time

300 seconds (5 minutes)

Delay-Recache-Time: 300

 

Max-Entries-Per-Query

2000

Max-Entries-Per-Query: 2000

 

Next-Id-Block-Size

100

Next-ID-Block-Size: 100

 

Server-Side-Table-Chunk-Size

1000

Server-Side-Table-Chunk- Size: 1000

 

Allow-Unequal-Queries

Disallow

Allow-Unequal-Queries: F

 

Cache-Mode

Development mode OFF

Cache-Mode: 0

 

Debug-mode

No debug mode

Debug-mode: 0

 

Submitter-Mode

Locked

Submitter-Mode: 1

 

Minimum-API-Version

Set a value appropriate for your production environment.

Defaults to 0 (not recommended).

General rule is 2 versions backward-compatible.

For more information, see the AR System 8.1 documentation on ar.cfg and ar.conf settings.

 

Private-RPC-Socket (Fast: 390620)
Private-RPC-Socket (List: 390635)

<Value = 3 x # of CPUs>
<Value = 5 x # of CPUs>

Total number of threads should not exceed 8 times the number of CPU cores.

 

CMBD-Cache-Refresh-Interval

600 seconds (10 minutes)

CMDB-Cache-Refresh-

Enterprise-AR Plugin Server: <AR System Home Directory>\pluginsvr\pluginsvr_config.xml

numCoreThreads:

Default 5: New 30

 

Cloud-AR Plugin Server : <Cloud Portal Home Directory>\plugin\pluginsvr_config.xml

numSelectorThreads

Default 2: New 5

 

 

workQueueTaskThreshold

Default 5: New 5

 

CAI Plugin Registry

Manual steps to be set in the database.

 

For more information, see the AR System 8.1 documentation on CAI-plug-in-configuration,

Mid Tier

Apply the following settings to the Mid-Tier configuration files:

Tomcat configuration parameters

Parameter

Recommended value

 

Keep-alive parameters

 

 

Keep-alive count

Infinite (minimum 5000)

 

Max connection timeout

90000 ms (minimum 60000 ms)

 

JVM parameters

 

 

JVM heap

=-Xms1024m –Xmx1024m

 

MaxPermSize

-XX:MaxPermSize=256m

 

Tomcat connector parameters

 

 

maxThreads

500

 

acceptCount

100

 

64-bit JVM

 

 

JVM hybrid mode and GC

-XX:+UseCompressedOops
 -XX:+UseParallelGC

<Tomcat_directory>/conf/ server.xml

Enable Cache Persistence

 

 

Prefetch or preload service

 

 

Recommended pre-load procedure

 

 

arsystem.formhtmljs_expiry_interval
arsystem.resource_expiry_interval

 

 

Definition Change Check Interval

 

 

arsystem.log_level

 

BMC Atrium Orchestrator

Apply the following settings to the BMC Atrium Orchestrator configuration files:

Configuration file

Operating system

Recommended value

Additional information

BMC Atrium Orchestrator Access Manager and Repository.lax/BMC Atrium Orchestrator CDP.lax/server.sh

Windows:
lax.nl.java.option.additional

-Xms1024m
-Xmx1280m
-XX:NewSize=256m
-XX:MaxNewSize=256m

Values are not retained. You must manually restore the modified values from the .bak files

 

Linux:
JAVA_OPTS

-Xms1024m
-Xmx1280m
-XX:NewSize=256m
-XX:MaxNewSize=256m

Values are not retained. You must manually restore the modified values from the .bak files

BMC Network Automation

Apply the following settings to the BMC Network Automation configuration files:

File name

Parameter

Recommended value

Additional information

BcanInstalledConfiguration.xml

DATABASE_URL

jdbc:oracle:thin:<hostname>:<port>:<SID>

Values are retained if modified.

database.properties

javax.jdo.option.ConnectionUR

jdbc:oracle:thin:<hostname>:<port>:<SID>

Values are retained if modified/

logging.properties

com.bmc.bcan.engine.database.persistence.level
java.util.logging.FileHandler.count

INFO
5

Values are not retained if modified. You must manually take the back-up before upgrade and restore them later.

server.xml

maxThreads
ConnectionTimeout

150
20000

Values are not retained if modified. You must manually take the back-up before upgrade and restore them later.

 

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

BMC Cloud Lifecycle Management 3.1