Remedy MidTier - Deploying in a JBoss 7.x Webserver

Version 6
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System Mid Tier



    PROBLEM:

     

    Detailed instructions on how to deploy Midtier in a JBoss 7.1 webserver.

     


    SOLUTION:

     

     

      
      Deploying Mid-Tier on JBoss 7.1.x
      
      NOTE: The deployment steps were performed on a Linux OS using the 7.1.1 JBoss Community edition, however the concepts should apply for other operating systems. The steps were also done using JBoss in standalone mode as opposed to domain mode. 
      
        
      
      Deployment steps:
      
      1)      Configure JBoss for manual deployment: 
      
      -Locate the standalone.xml file in    <jboss root>/standalone/configuration and open it for editing.  
      
      -Locate this    subsystem element and add the highlighted attributes:   
    <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">             <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-zipped="false" auto-deploy-exploded="false"/>    </subsystem>
      
      
      2)      Prepare the arsys.war file for deployment: 
      
      -Create a new directory called arsys.war at <jboss root>/standalone/deployments. 
      
      -Copy the arsys.war    file to the arsys.war    directory
      
      -Extract the contents of the arsys.war file inside the arsys.war directory. For example use the jar command if Java is on the system path, ‘ jar –xvf arsys.war’. 
      
      -Rename the arsys.war file to arsys.war.back. 
      
      -Create a new file called    jboss-web.xml inside of    <jboss root>/standalone/deployments/arsys.war/WEB-INF with the following content to define the URL context path for mid-tier: 
      
          
    <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <context-root>arsys</context-root> </jboss-web>
       
       -Create a new file called     jboss-deployment-structure.xml inside of      <jboss root>/standalone/deployments/arsys.war/WEB-INF with the following content.   
         
    <jboss-deployment-structure> <deployment> <!-- Exclusions allow you to prevent the server from automatically adding some dependencies --> <exclusions> <module name="org.codehaus.jackson.jackson-core-asl" /> <module name="org.codehaus.jackson.jackson-mapper-asl" /> </exclusions> </deployment> </jboss-deployment-structure>
        
      
       
      
      
      4)      Replace the existing directories and files in the .war file with the updated directories and files included in the hotfix bundle and noted in the installation readme document in the hotfix bundle. 
      
      5)      Open up permissions on the new arsys.war directory created and all subfolders and files contained in it. From testing at BMC we had to set full rwx permissions to avoid any “permission denied” I/O errors during deployment. 
      
      6)      Deploy the mid-tier web application: 
      
       -Change directories to    <jboss root>/standalone/deployments
      
       -Create a new file called    arsys.war.dodeploy, e.g. ‘touch arsys.war.dodeploy’. 
      
       -The deployment scanner will detect the file and begin deploying the application.  
      
       -If deployment is successful you will see a new file created called    arsys.war.deployed
      
      -If deployment fails you’ll see a new file created called    arsys.war.failed. Examine the server.log   file in    <jboss root>/standalone/log to determine why deployment was not successful. Once the     problem is corrected create the    arsys.war.dodeploy file to attempt deployment again. 
      
      -If you need to redeploy a successfully deployed mid-tier, for example you added or edited existing files or directories under mid-tier, simply remove the    arsys.war.deployed file and JBoss will automatically redeploy for you.  
    -If nothing happened it means your service is down, start jboss standalone service (standalone.sh for linux or standalone.bat for windows) and then the deployment scanner will run. 
      
      7)      If deployment was successful you should be able to access the Mid-Tier Configuration tool and configure mid-tier for use using the default HTTP port 8080, for example    http://yourhostname:8080/arsys/shared/config/config.jsp
      

    Note. If you are deploying 18.x systems with Atrium Core, please follow extra steps in this knowledge article https://communities.bmc.com/docs/DOC-109027

    If IIS/Jakarta ISAPI Redirector loadbalancing is used in front of multiple JBOSS servers, you may need to change the JSESSIONID that is created by JBOSS so that it does not conflict with the JSESSIONID generated by the midtier.   Evidence of a conflict would be the reset of the JSESSIONID to a value that IIS does not recognize which causes it to redirect the session to another midtier and reset the JSESSIONID again.   This causes the new midtier to not recognize the JSESSIONID and pushes the customer back to the login.jsp.
    Update the Jakarta ISAPI redirector workers.properties.minimal file to include the directive session_cookie. In our example this is: worker.ARSystem_Cluster.session_cookie=XX_ARSystem_App

      
       
    • Update JBOSS EAP7 standalone-full.xml to contain session-cookie name sub-element of servlet-container element. In our example this is:
      

                <servlet-container name="default">
                    <jsp-config/>
                    <session-cookie name="XX_ARSystem_App"/>
                    <websockets/>
                </servlet-container>
     

     


    Article Number:

    000352529


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles