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 on Enterprise-AR
   2. 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:
   • <AR Install Directory>/midtier/dvModule/*
   • <AR Install Directory>/midtier/WEB-INF/atriumDeploymentPackages
   • <AR Install Directory>/midtier/WEB-INF/AtriumWidget*
   • <AR Install Directory>/midtier/WEB-INF/lib/atrium-dvm-*
   • <AR Install Directory>/midtier/WEB-INF/lib/atrium-submodule-*
   • <AR Install Directory>/midtier/PluginsCache
3. 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 
4. In the left navigation pane, click Cache Settings.

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

6. Go to Configuration > AR Settings > General Settings.
7. Configure the Enterprise AR System server load balancer IP or host name.
8. Restart the following services in the following order:
   1. AR System server on Enterprise-AR
   2. CSM service on Platform Manager
   3. AR System server on Cloud-AR
   4. Tomcat service on the Mid Tier
9. Flush the browser cache.