Configuring the BMC Remedy Mid Tier

After you finish upgrading the cloud stack, perform the following steps to configure the BMC Remedy Mid Tier (mid tier):

1. Stop the following services in the following order:
   1. AR System server - Cloud Portal and Database (Enterprise-AR)
   2. (if applicable) AR System server on Cloud-AR
   3. CSM service on Platform Manager
   4. Tomcat service on the Mid Tier
2. Navigate to the midtier subdirectory and delete the following:
   1. <AR Install Directory>/midtier/dvModule/*
   2. <AR Install Directory>/midtier/WEB-INF/atriumDeploymentPackages
   3. <AR Install Directory>/midtier/WEB-INF/AtriumWidget*
   4. <AR Install Directory>/midtier/WEB-INF/lib/atrium-dvm-*
   5. <AR Install Directory>/midtier/WEB-INF/lib/atrium-submodule-*
   6. <AR Install Directory>/midtier/PluginsCache
3. Restart the following services in the following order:
   1. AR System server - Cloud Portal and Database (Enterprise-AR)
   2. CSM service on Platform Manager
   3. (if applicable) AR System server on Cloud-AR
   4. Tomcat service on the Mid Tier
4. Log on to the mid tier Configuration Tool, using the following link:
   http://midTierHost:portNumber/arsys/shared/config/config.jsp
   http://SanJoseMidTier:8080/arsys/shared/config/config.jsp 
5. In the left navigation pane, click Cache Settings.

6. Click Flush Cache.

   Note

   If you are using the aliasing method in /etc/hosts in the upgrade, then you do not need to perform step 6 and 7. Simply remove the load balancer alias from /etc/hosts.

7. In the left navigation pane, click General Settings.
8. Configure the Enterprise AR System server load balancer IP or host name.
9. Inform your user community to flush the cache on their browsers.
   Otherwise, they run the risk of seeing a confused mix of old and new functionality in their browsers.

Where to go next

Configuring-the-BMC-Atrium-Core-Web-Registry