Midtier Reinstall and Hotfix


A recent service call with Remedy for a hotifx resulted in a complete overhaul of how miditer is installed.

Midtier Reinstall

Remove all instances of the current install:

cd /usr/local/tomcat7/webapps

rm -fr arsys*


Download and extract the latest midtier.

Find and extract the .war file:

cd linux/installers/miditer/war
unzip midtier_linux.war

Remove the .war file and copy this directory into /opt:

rm -fr *war
cd ../
cp war /opt/midtier

We now need to reconfigure tomcat to let it know where we moved miditer by creating an app definition (context) xml file:

vi /usr/local/tomcat7/conf/Catalina/localhost/arsys.xml
    Context configuration file for the Tomcat Manager Web App
    $Id: manager.xml 303123 2004-08-26 17:03:35Z remm $
<!-- http://tomcat.apache.org/tomcat-5.5-doc/config/context.html -->
<Context docBase="/opt/midtier"
         <!-- this will disable session persistance across shotdown/startup -->
         <Manager pathname=""/>

Startup tomcat to verify that midtier works.

Clear the cache files:

cd /usr/local/tomcat7/work/Catalina/localhost/
rm -fr arsys

hotfix install

Extract the hotfix.

Replace the following files:

cp MidTier.jar Config.jar /opt/midtier/WEB-INF/lib/
cp -r resources /opt/midtier/
cp Flashboard.jar /opt/midtier/LocalPlugins/Flashboard/

Restart tomcat.

Reconfigure Midtier cache

Login to the midtier admin using the default password ‘arsystem’.

Under ‘cache settings’ replace ‘prefetch cofiguration’ with the following:

<?xml version="1.0" encoding="UTF-8"?><midtier-prefetch-config xmlns="http://www.bmc.com/remedy/midtier/midtier">