Preparing for upgrade

In-Place

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products. 
3. After upgrade, perform data migration:
   1. Prepare for data migration.
   2. Prepare for 2.1.x migration.
   3. Migrate your data.
4. Perform post-upgrade configuration.

Staging

1. Complete all the prerequisites for the upgrade.
2. Upgrade Zone 1 products.
3. Create Zone 2 staging servers.
4. Upgrade Zone 2 products. 
5. Prepare for DDM.
6. Run Live DDM.
7. Run Final DDM.
8. After DDM, perform data migration:
   1. Prepare for data migration.
   2. Prepare for 2.1.x migration.
   3. Migrate your data.
9. Perform post-upgrade configuration.

For a helpful overall view of the Staging upgrade process, see 2-1-x-Staging-upgrade-process-flow-chart.

Staged-Lite

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products. 
3. After upgrade, perform data migration:
   1. Prepare for data migration.
   2. Prepare for 2.1.x migration.
   3. Migrate your data.
4. Perform delta data migration.
5. After DDM, perform Step 3 a second time.
6. Perform post-upgrade configuration.

Use Staged-Lite upgrade strategy only for HA environments.

In-Place

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products in the solution. 
3. After upgrade, perform data migration :
   1. Prepare for data migration.
   2. Migrate your data.
4. Perform post-upgrade configuration.

Staging

1. Complete all the prerequisites for the upgrade.
2. Upgrade Zone 1 products.
3. Create Zone 2 staging servers.
4. Upgrade Zone 2 products. 
5. Prepare for DDM.
6. Run Live DDM.
7. Run Final DDM.
8. After DDM, perform data migration:
   1. Prepare for data migration.
   2. Prepare for 2.1.x migration.
   3. Migrate your data.
9. Perform post-upgrade configuration.

For a helpful overall view of the Staging upgrade process, see 3-x-Staging-upgrade-process-flow-chart.

Staged-Lite

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products in the solution. 
3. After upgrade, perform data migration:
   1. Prepare for data migration.
   2. Migrate your data.
4. Perform delta data migration.
5. After DDM, perform Step 3 a second time.
6. Perform post-upgrade configuration.

Use Staged-Lite upgrade strategy only for HA environments.

In-Place

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products in the solution. 
3. After upgrade, perform data migration.
4. Perform post-upgrade configuration.

Staging

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products in the solution. 
3. After upgrade, perform data migration:
4. Perform delta data migration.
5. After DDM, perform Step 3 a second time.

1. Perform post-upgrade configuration.

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products in the solution. 
3. Prepare for DDM.
4. Run Live DDM.
5. Run Final DDM.
6. After DDM, perform data migration:
7. Perform post-upgrade configuration.

• When upgrading to 4.x, you do not need to perform the Before you begin data migration  steps. These migration prerequisite steps are now performed automatically by the installer.
• For a helpful overall view of the Staging upgrade process, see 4.0 Staging upgrade process flow chart.

Staged-Lite

1. Complete all the prerequisites for the upgrade.
2. Upgrade all products in the solution. 
3. After upgrade, perform data migration:
4. Perform delta data migration.
5. After DDM, perform Step 3 a second time.

1. Perform post-upgrade configuration.

• When upgrading to 4.x, you do not need to perform the Before you begin data migration  steps. These migration prerequisite steps are now performed automatically by the installer.
• Use Staged-Lite upgrade strategy only for HA environments.

In-Line

Perform upgrade in production environment.

• No products are taken offline during the upgrade
• Delta data migration is not required

10-11 days

Staging

Clone production servers into staged environment.

• Environment remains available throughout the upgrade
• Delta data migration is required.

18-30 days

Staged-Lite (HA environments only)

Clone production servers into staged environment, but dismantle secondary servers to minimize their number.

• Environment remains available throughout the upgrade
• Delta data migration is required.

18-30 days

Plan the upgrade accordingly

Review the product configuration files before you start. During the upgrade, some but not all production configuration files are preserved. 

Create overlays

After you upgrade the AR System Server on both Enterprise-AR and Cloud-AR, use the Best Practice Conversion Utility (BPCU) to identify any existing customizations that are in base mode. You use BPCU to create overlays and preserve your customizations. You then can continue the upgrade. Otherwise, you will have to re-create the customizations after the upgrade.

For detailed information, see Creating-overlays-with-BPCU-for-existing-customizations-and-future-upgrades.

Upgrade strategies

You might have customized one or several components in the solution to suit your business needs (for example, the Network Automation API). You must decide whether to replace your customizations or port them.

To configure the mid tier for upgrade

Configure the mid tier, so that you can use it to access Enterprise-AR and Cloud-AR:

1. Open the BMC Remedy Configuration Tool using the following URL: 
   http://<hostname>:<port>/arsys/shared/config/config.jsp
   For example:
   http://MidTier:8080/arsys/shared/config/config.jsp 
2. On the AR Server Settings panel, click Add Server and specify the Enterprise-AR – Primary host name.
3. On the General Settings panel, set the following fields to the Enterprise-AR – Primary host name:
   • Preference Server(s)
   • Data Visualization Module Server(s)
   • Homepage Server
   • Authentication Server
4. Repeat steps 2 and 3 to add Cloud-AR to the mid tier configuration.

To prepare Enterprise-AR for upgrade

Before you upgrade the Enterprise-AR host, you must complete the following prerequisites:

1. Install Oracle JRE 1.7.
2. If you are upgrading Linux, reset the symlink for /usr/java/latest to Oracle JRE 1.7 installation path.

3. Ensure that the Enterprise-AR host has a minimum of 16 GB RAM and 4 CPUs available.

   Note: Ensure that you have the same amount of RAM and same number of CPUs on Cloud-AR host also.

4. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.confon Linux):

   Private-RPC-Socket:  390601   1   1
   Private-RPC-Socket:  390603   5  10
   Private-RPC-Socket:  390620  12  12
   Private-RPC-Socket:  390621  12  16
   Private-RPC-Socket:  390622   4   6
   Private-RPC-Socket:  390626  12  12
   Private-RPC-Socket:  390635  20  20
   Private-RPC-Socket:  390680   2  25
   Private-RPC-Socket:  390681   4   4
   Allow-Unqual-Queries: T
   

   If the queue parameters are not present on the Enterprise-AR primary and secondary hosts, add these parameters in the ar configuration file and restart the AR System server services.

5. If you are upgrading from 3.0 to 4.x, use BMC Remedy Developer Studio to perform the hotfix located at <Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix before you upgrade BMC Atrium Core.
   The following instructions are adapted from the Readme.txt.  

   1. If you are in a Linux environment, install BMC Remedy Developer Studio on a Windows host.
   2. Make a copy the CMU%ServiceInstances1.def file.
      • On Windows, copy the file to the Enterprise-AR host.
      • On Linux, copy the file to the Windows host.
   3. Launch BMC Remedy Developer Studio and log on to the AR System Server.
   4. Set Developer Studio to Base Development mode.
   5. Select File > Import, select the import source as Object Definitions, and then click Next.
   6. Browse to the CMU%ServiceInstances1.def file and then click Next.
   7. Select Replace Objects on the destination server and start the import
6. (For Staged upgrades only) If you are upgrading Linux from 2.1 to 4.x, create a symlink /etc/arsystem/<stage-ear-2140>/armonitor.conf that points to /etc/arsystem/<ear>/armonitor.conf to fix an upgrade issue.
7. In BMCServiceRequestManagementInstalledConfiguration.xml, set the MULTIPLE_INSTANCE_CAPABLE parameter from true to false to prevent an error message occurring during the upgrade of the Enterprise-AR SRM module (which indicates that there are multiple instances of SRM installed).
8. Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing-your-database-for-an-upgrade.

9. Open the CMF:PluginConfiguration form for Enterprise-AR, review the following attributes, and update them if necessary.
   For example: 

   http://CLM-MT:8080/arsys/plugins/CloudCallBackPlugin/params?server=
   <EnterprisePrimaryHostname>&username=csmcallback&pwd=csmcallback

   • Callback URI: set to the host name on which you installed the Enterprise-AR – Primary
   • FIELD_AO_HOST: set to host name on which you installed BMC Atrium Orchestrator – Primary

10. Review the BMC.CLOUD:BMC_Callout join form on Cloud-AR host. 

    [http://clm-mt:8080/arsys/plugins/CloudCallBackPlugin/params?server=]
    <ITSMPrimartHost>&username=csmcallback&pwd=csmcallback&operation=
    CHECK_CHANGE_REQUIRED

    1. Search for the CSM Change integration HTTP Callout entry.
    2. Click View relationship and open the URL entry.
    3. From the Custom tab, review the Attribute Value with the host name on which you installed the Enterprise-AR – Primary, and update it if necessary.
11. Take a snapshot of your Enterprise-AR VM and database. 
12. Back up any customizations that you have made to your AR System components before you upgrade or you will lose the customizations.

To prepare Cloud-AR for upgrade

Before you upgrade the Cloud-AR host, you must complete the following prerequisites:

1. Install Oracle JRE 1.7.
2. If you are upgrading Linux, reset the symlink for /usr/java/latest to Oracle JRE 1.7 installation path.
3. (For Staged upgrades only) If you are upgrading Linux from 2.1 to 4.x, create a symlink 
   /etc/arsystem/<stage-cloud-ar-2140>/armonitor.conf that points to 
   /etc/arsystem/<cloud-ar>/armonitor.conf to fix an upgrade issue.
4. Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing-your-database-for-an-upgrade.
5. Take a snapshot of your Cloud-AR VM and database.
6. Back up any customizations that you have made to your AR System components before you upgrade or you will lose the customizations.

To prepare BMC Server Automation for upgrade

1. Update the /etc/hosts file with new hostnames of the cloned Zone 2 CLM component VMs.
2. License the rscd agents of all the cloned Zone 2 CLM component VMs.
3. Shut down the AppServer process.
4. Take a snapshot of your Zone 1 BMC Server Automation VM.

To prepare PXE for upgrade

1. Back up the tftp directory on the PXE VM.
2. Shut down the pxe and tftp processes.

To prepare BMC Network Automation 8.1 for the upgrade to 8.5

If you are upgrading from 2.1.x to 4.x and you have existing multizone containers or container blueprints in BMC Network Automation 8.1, expand the following section for instructions.

To prepare for BMC AR System Server and IT Management Suite upgrade

To ensure an efficient BMC AR System Server and IT Management Suite upgrade, see the following steps described in the BMC Remedy AR System online technical documentation:

• BMC AR System upgrade - Preparing-your-components-and-applications-for-an-upgrade
• BMC Atrium Core upgrade - Preparing to upgrade BMC Atrium Core
• BMC ITSM upgrade - Preparing to upgrade BMC Remedy ITSM
• BMC SRM upgrade - Preparing to upgrade BMC Service Request Management

To prepare for a BMC AR System Server – Cloud Database upgrade

To ensure an efficient cloud database upgrade, see the following steps described in the BMC Remedy AR System online technical documentation:

• BMC AR System upgrade - Preparing-your-components-and-applications-for-an-upgrade
• BMC Atrium Core upgrade - Preparing to upgrade BMC Atrium Core

To prepare for Cloud Portal AR Extensions upgrade

Before you upgrade the Cloud Extensions, verify that DSO is working between Enterprise-AR and Cloud-AR. For example:

1. Log on to the Enterprise-AR System host using mid tier.
2. Open the User form, search for entries in the form, and update a field on any record (for example, Email Address) for any user.
3. Save the record.
4. Log on to the Cloud-AR host and open the User form.
5. Verify whether the user information that you modified in the previous step is now visible on the Cloud-AR host.

To prepare for Staged upgrades

In your staging environment, make sure that the /etc/hosts file of each computer has a load-balancer entry that points to individual computers only. The entry should not point to the load balancer itself. Make similar changes on all staged environments.

 The following example is the previous entry in /etc/hosts:

The following example lists the correct entry you must make in /etc/hosts, where clm-itsm is the name of the load balancer:

Make sure that the cloning environment is isolated; it should not communicate with production data.

To prepare for Staged-Lite upgrades

In a Staged-Lite upgrade, all primary servers are removed from the environment. Make sure that all primary servers services are disabled or suspended on the load balancer. The request should not go to primary servers.

Update the /etc/hosts file of each primary server that you removed so that primary servers and the related load-balancer entry should point to the same IP address.

The following example is the previous entry in /etc/hosts:

The following example now lists the correct entry you must make in /etc/hosts, where clm-itsm is the name of the load balancer:

To prepare Enterprise-AR for upgrade

Before you upgrade the Enterprise-AR host, you must complete the following prerequisites:

1. Ensure that the Enterprise-AR host has a minimum of 16 GB RAM and 4 CPUs available.

    

   Note: Ensure that you have the same amount of RAM and same number of CPUs on Cloud-AR host also.

2. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.confon Linux):

   Private-RPC-Socket:  390601   1   1
   Private-RPC-Socket:  390603   5  10
   Private-RPC-Socket:  390620  12  12
   Private-RPC-Socket:  390621  12  16
   Private-RPC-Socket:  390622   4   6
   Private-RPC-Socket:  390626  12  12
   Private-RPC-Socket:  390635  20  20
   Private-RPC-Socket:  390680   2  25
   Private-RPC-Socket:  390681   4   4
   Allow-Unqual-Queries: T
   
3. If the queue parameters are not present on the Enterprise-AR primary and secondary hosts, add these parameters in ar configuration file and restart the AR System server services.
4. Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing your database for an upgrade.
5. Use BMC Remedy Developer Studio to perform the hotfix located at<Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix.
   For detailed information on how to apply the hotfix on Windows and Linux, see Readme.txt.  

To prepare DSO for upgrade in a server group

If you have installed a server group environment for the following products, ensure that you update the Distributed Server Option (DSO) for them to point to the Primary servers:

• The Enterprise-AR server(all nodes in server group)--Update the DSO target with Cloud-AR – Primary host information
• Cloud-AR servers (all nodes in server group)-- Update the DSO target with the Enterprise-AR – Primary host information

1. Using the mid tier, log on to any of the AR System server in the server group.
2. Open the Distributed Logical Mapping form (by selecting AR System Administration Console > System > Distributed Server Option >Distributed Logical Mappings) and change the Name attribute value to the host name on which you installed the Enterprise-AR – Primary or Cloud-AR – Primary depending on the following points:
   • For Enterprise-AR, specify Cloud-AR – Primary host name.
   • For Cloud-AR, specify the Enterprise-AR – Primary host name.
3. Using the mid tier, log on to the Primary and Secondary servers of Enterprise-AR and Cloud-AR products.
4. Go to AR System Administration Console > System > General > Server Information > Connection Settings > DSO Server tab.
5. Change the Server Nameto the local host name on which you installed the Enterprise-AR server – Primary depending on the following points:
   • For Enterprise-AR, specify Cloud-AR – Primary host name.
   • For Cloud-AR, specify the Enterprise-AR – Primary host name.
6. Restart the AR System Server service on the Enterprise-AR and Cloud-AR hosts.

To prepare BMC Network Automation version 8.1 for the upgrade to 8.5

Note: These instructions apply to upgrades from 2.1.x to 4.x if you have existing multi-zone containers or container blueprints in BMC Network Automation 8.1.

1. Create a .properties file to use with the upgrade, for example, upgrade_8_2.properties.

2. Add the multizone containers or container blueprints content from your environment. 

    

   Click here to see an example.

   # Place this in the BNA Data folder (i.e. c:\BCA-Networks-Data)
   ############################################################
   # CONTAINER BLUEPRINT INFO
   ############################################################
   #
   # ******************************
   # Multi Zone Container Blueprint
   # ******************************
   #
   # Names of the VFW blueprints either in Firewall Host Blueprints or in
   # Pair blueprints in Multi Zone Container Blueprint.
   #
   # 1. The vfw blueprint name in the key is represented in the form 
   #    <firewallHostBlueprint>.<vfwBlueprintGuestNodeName>
   #    or as <firewallHostPairBlueprint>.<vfwBlueprintGuestNodeName>
   # 2. The bridged interface names are represented in the form 
   # <zoneBlueprintName>.<vfwGuestNodeName>.<interfaceBlueprintName>
   # 3. For the serviced segment names, either the NIC segment blueprint 
   #    names (port type blueprints in 8.1.x) and/or the address pool name
   #    of the vip segment blueprints (associated with the load balancer 
   #    pool type blueprint in that zone blueprint) can be provided.
   #
   #    Firewall Host WEB.VFW1
   #             |
   #    Firewall Host Application.VFW2
   #             |
   #    Firewall Host Data.VFW3
   #
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[outside].servicedSegmentNames=Default External Network
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ 
   Web.VFW1].interfaceBlueprints[outside].bridgedInterfaceNames=
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ 
   Web.VFW1].interfaceBlueprints[inside].servicedSegmentNames=Web Pool, Web Network
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[inside].bridgedInterfaceNames=Application.VFW2.outside
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[outside].servicedSegmentNames=
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[outside].bridgedInterfaceNames=Web.VFW1.inside
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[inside].servicedSegmentNames=Application Pool, 
   Application Network
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[inside].bridgedInterfaceNames=Data.VFW3.outside
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ 
   Data.VFW3].interfaceBlueprints[outside].servicedSegmentNames=
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[outside].bridgedInterfaceNames=Application.VFW2.inside
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[inside].servicedSegmentNames=Data Network
   containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ 
   Data.VFW3].interfaceBlueprints[inside].bridgedInterfaceNames=
3. Save the file in the BNA Data folder (for example, C:\BCA-Networks-Data)
4. Continue with the upgrade.

To prepare the Cloud Platform Manager for upgrade

Before you upgrade the Cloud Platform Manager host, you must open the Cloudservice.JSON file and set the attributevalue parameter of Cloud-AR load balancer setting name to the host name on which you installed Cloud-AR – Primary.

Zone 1 (Backward compatible products):

• BMC Server Automation
• BMC Capacity Optimization (not included in BMC Cloud Lifecycle Management)

Zone 1 (Backward compatible products):

• BMC Server Automation
• BMC Network Automation
• BMC Capacity Optimization (not included in BMC Cloud Lifecycle Management)

Because the products in Zone 1 are backward compatible, you can perform the upgrade in separate periods of maintenance time, or you can upgrade them all in the same maintenance period. An upgraded Zone 1 product will continue to work with other non-upgraded products in this zone, even if not all products are upgraded in the same maintenance period.

BMC recommends that you upgrade Zone 1 products in the production environment (in-place).

Zone 2 (Non-backward compatible products):

• BMC Remedy AR System & BMC Remedy IT Service Management Suite (Enterprise-AR)
• BMC Remedy AR System—Cloud Database (Cloud-AR)
• Cloud Platform Manager
• BMC Atrium Orchestrator—Platform
• BMC Atrium Orchestrator—Content
• BMC Network Automation

Zone 2 (Non-backward compatible products):

• BMC Remedy AR System & BMC Remedy IT Service Management Suite (Enterprise-AR)
• BMC Remedy AR System—Cloud Database (Cloud-AR)
• Cloud Platform Manager
• BMC Atrium Orchestrator—Platform
• BMC Atrium Orchestrator—Content

Upgrade products in Zone 2 only after you have completed the upgrade for Zone 1 products.

Because the products in Zone 2 are not backward compatible, you must upgrade these products in one maintenance period. If you upgrade one product in this zone and try to continue using the 2.1.x environment, the BMC Cloud Lifecycle Management solution will not work.

Because the time required to upgrade Zone 2 products is greater than the time to upgrade Zone 1 products, BMC recommends that you upgrade these products in a staging environment. Creating a staging environment and upgrading the products in that environment ensures that you are able to keep a 2.1.x environment running while you complete the upgrade process.

1

BMC Server Automation – File Server

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.

2

BMC Server Automation – Application Server & Console

1. When prompted by the installer, stop the PXE server, BMC Server Automation – Multiple Application Server (MAS), and BMC Server Automation – Advanced Repeater services, if available. 
2. Upgrade BMC Server Automation Application Server
3. Manually perform BMC Server Automation database migration.
4. Manually start the appserver.
5. Upgrade BMC Server Automation Console.
6. Complete the BMC Server Automation post-upgrade configuration in the installer.
7. Manually upgrade the Virtual Center (VC) agent.
8. Manually upgrade the BMC RSCD Agent on the source VM Template. 
   After upgrading the RSCD Agent, ensure that the Exports file mappings are appropriately configured.

3

BMC Server Automation – Multiple Application Server (MAS)

1. Upgrade BMC Server Automation – Application Server.
2. Perform post-upgrade configuration tasks after the upgrade.

4

(Optional) PXE server

• Upgrade the PXE server only after you have upgraded all application servers.
• On Windows, make a backup copy of the TFTP folder, which is located in the <PXE Server Installation directory>. During the upgrade, the PXE server uninstalls the existing TFTP folder before installing the latest version.

5

(Optional) BMC Server Automation – Advanced Repeater 

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.

6

BMC Atrium Orchestrator – Configuration Distribution Peer

Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer:

1. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.
2. Upgrade the following components in this order using the installer planner:
   1. Access Manager and Repository
   2. Configuration Distribution Peer
   3. Atrium Orchestrator Content
   4. BMC Server Automation Console
   5. BMC Atrium Orchestrator Post Installation Configuration
3. Manually activate the BMC Atrium Orchestrator adapters.

7

Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA) 

1. Upgrade the BMC Server Automation Console.
2. Upgrade the Configuration Distribution Peer.

8

BMC AR System & BMC Remedy IT Service Management Suite – Primary (Enterprise-AR)

1. Install BMC AR System & BMC Remedy IT Service Management Suite – Primary and BMC Remedy AR System Cloud Database – Primary in the same session.
2. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the installer planner:
   1. AR System server
   2. If you are upgrading from 3.0 to 4.x, use BMC Remedy Developer Studio to install the hotfix located at clm40build/Applications/AtriumCore/Common/hotfix.
      Follow the Windows and Linux instructions in clm40build/Applications/AtriumCore/Common/hotfix/Readme.txt before you upgrade BMC Atrium Core.
   3. BMC Atrium Core
   4. Atrium Integrator
   5. If you launched the installer planner with the setup.cmd/sh -J skip_itsm=false condition to upgrade BMC Remedy IT Service Management, you now see its node. Otherwise, the BMC Remedy IT Service Management node is not displayed by default.
   6. BMC Remedy Service Request Management
   7. AR Post Install Configuration
3. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.

9

BMC Remedy AR System Cloud Database – Primary (Cloud-AR)

1. Upgrade the following BMC Remedy AR System Cloud Database – Primary components in this order using the installer planner:
   1. AR System server
   2. Atrium Core
2. Upgrade Enterprise-AR DSO mapping using the installer.
3. Perform the post-upgrade configuration steps for the AR System server using the installer.
4. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
5. Perform Cloud-AR DSO mapping using the installer.

10

BMC AR System & BMC Remedy IT Service Management Suite – Secondary 

1. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the installer planner:
   1. AR System server
   2. Atrium Core
   3. Atrium Integrator
   4. BMC Remedy ITSM, if it exists in the 2.1 or 2.1 SPx implementation
      Upgrading BMC Remedy ITSM is optional. If you must upgrade, use the following command to launch the installer:
      setup.cmd/sh -J skip_itsm=false  
   5. BMC Remedy Service Request Management
2. Perform the post-upgrade configuration steps for the AR System server using the installer.
3. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
4. Use BMC Remedy Developer Studio to perform the hotfix located at <Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix.
   For detailed information about how to apply the hotfix on Windows and Linux, see <Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix/Readme.txt.

11

BMC Remedy AR System Cloud Database – Secondary 

1. Upgrade the following BMC Remedy AR System Cloud Database – Secondary components in this order using the installer planner:
   1. AR System server
   2. Atrium Core
2. Upgrade Enterprise-AR DSO mapping using the installer.
3. Perform the post-upgrade configuration steps for the AR System server using the installer.
4. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
5. Perform Cloud-AR DSO mapping using the installer.

12

BMC Remedy Mid Tier 

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner..

13

BMC Atrium Core – Web Registry Components

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner..

14

BMC Network Automation

Note: Upgrading the BMC Network Automation server in an HA environment is not supported by the installer planner. Therefore, you must perform the upgrade using the BMC Network Automation product installer.

1. Upgrade the BMC Network Automation – Primary server where the cluster and application service is active.
2. Failover the cluster.
3. In the silent.ini file, set the SKIP_DB_UPGRADEoption to true. You use this option to skip the database update step on the secondary servers. For more information, see running the installer in silent mode.
4. Perform the upgrade using the BMC Network Automation product installer; see preserving the application server database.

15

(Optional) BMC Network Automation – Device Agent 

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.

16

Cloud Database Extensions

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 

17

Cloud Platform Manager

If you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server. 

18

Cloud Portal AR Extensions – Primary

Upgrade the following Cloud Portal AR Extensions components in this order using the installer planner: 

1. Cloud Portal AR Extensions – Primary.
2. Using the Cloud Upgrade Migration option in the installer, migrate the BMC Cloud Lifecycle Management data. 
   Note: Make sure that you have your Cloud administrator credentials ready before you begin the Cloud upgrade migration using the installer.

19

Cloud Portal AR Extensions – Secondary

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 

1

BMC Server Automation – File Server

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.

2

BMC Server Automation – Application Server & Console

1. When prompted by the installer, stop the PXE server, BMC Server Automation – Multiple Application Server (MAS), and BMC Server Automation – Advanced Repeater services, if available. 
2. Upgrade BMC Server Automation Application Server
3. Manually perform BMC Server Automation database migration.
4. Manually start the appserver.
5. Upgrade BMC Server Automation Console.
6. Complete the BMC Server Automation post-upgrade configuration in the installer.
7. Manually upgrade the Virtual Center (VC) agent.
8. Manually upgrade the BMC RSCD Agent on the source VM Template. 
   After upgrading the RSCD Agent, ensure that the Exports file mappings are appropriately configured.

3

BMC Server Automation – Multiple Application Server (MAS)

1. Upgrade BMC Server Automation – Application Server.
2. Perform post-upgrade configuration tasks after the upgrade.

4

(Optional) PXE server

• Upgrade the PXE server only after you have upgraded all application servers.
• On Windows, make a backup copy of the TFTP folder, which is located in the <PXE Server Installation directory>. During the upgrade, the PXE server uninstalls the existing TFTP folder before installing the latest version.

5

(Optional) BMC Server Automation – Advanced Repeater 

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.

6

BMC Atrium Orchestrator – Configuration Distribution Peer

Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer:

1. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.
2. Upgrade the following components in this order using the installer planner:
   1. Access Manager and Repository
   2. Configuration Distribution Peer
   3. Atrium Orchestrator Content
   4. BMC Server Automation Console
   5. BMC Atrium Orchestrator Post Installation Configuration
3. Manually activate the BMC Atrium Orchestrator adapters.

7

Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA) 

1. Upgrade the BMC Server Automation Console.
2. Upgrade the Configuration Distribution Peer.

8

BMC Network Automation

Note: Upgrading the BMC Network Automation server in an HA environment is not supported by the installer planner. Therefore, you must perform the upgrade using the BMC Network Automation product installer.

1. Upgrade the BMC Network Automation – Primary server where the cluster and application service is active.
2. Failover the cluster.
3. In the silent.ini file, set the SKIP_DB_UPGRADE option to true. You use this option to skip the database update step on the secondary servers. For more information, see running the installer in silent mode.
4. Perform the upgrade using the BMC Network Automation product installer, see preserving the application server database.

9

(Optional) BMC Network Automation – Device Agent 

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.

10

Cloud Database Extensions

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 

11

Cloud Platform Manager

If you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server. 

12

Cloud Portal AR Extensions – Primary

Upgrade the following Cloud Portal AR Extensions components in this order using the installer planner: 

1. Cloud Portal AR Extensions – Primary.
2. Using the Cloud Upgrade Migration option in the installer, migrate the BMC Cloud Lifecycle Management data. 
   Note: Make sure that you have your Cloud administrator credentials ready before you begin the Cloud upgrade migration using the installer.

13

Cloud Portal AR Extensions – Secondary

No manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 

cloudservices.json

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

❌️

providers.json

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

❌️

wrapper.conf

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

❌️

config.ini

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

❌️

csm-bootstrap.properties

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

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

❌️

email-templates

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

❌️

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

✅️

ar.cfg

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

❌️ 

armonitor.cfg

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

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

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

❌️ For safety, verify any parameters that were customized in this file.

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>\conf\server.xml

❌️ 

tomcat6w/startup.sh

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

✅️

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/bao.sh

❌️ 

Access Manager and Repository repository.xml

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

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

❌️ 

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/bao.sh

❌️ 

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

❌️ 

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

❌️ 

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

✅️

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

✅️