This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring and installing BMC Remedy Mid Tier on IBM WebSphere

To install the mid tier with an IBM WebSphere web server, complete the following steps:

  1. Install IBM WebSphere.
  2. Deploy the mid tier with the .war file.
  3. Configure system requirements.
  4. Configure the WebSphere Application Server to support the WBMP MIME type.

To install IBM WebSphere

  1. Create an Administrator User with the following advanced rights:
    • Act as part of the operating system
    • Log on as services
  2. Install IBM WebSphere.
    See your IBM WebSphere Application Server product documentation for specific installation instructions.

To deploy the mid tier with the .war file

  1. Locate the midtier.war, midtierCombined.war, or midtier_<platform>.war file.
    The .war file is located with the BMC Remedy AR System installation files. If you have BusinessObjects or Crystal software installed, use the midtierCombined.war file.
  2. Start the IBM WebSphere server.
    In the output command window, check for the Open for e-business message, which confirms that the server has started.
  3. Open the WebSphere Application Server console.
    The default URL is http://<hostName>:9060/admin.
  4. Log on as the administrator that you created in To install IBM WebSphere.
  5. If the BMC Remedy Mid Tier is installed, stop it and uninstall it by using the WebSphere Application Server console.
  6. Choose Applications > Install New Application.
  7. In the Preparing for the application installation section, browse to the midtier_<platform>.war file.
  8. Designate a name for BMC Remedy Mid Tier on WebSphere in the Context Root Path subsection.
    The recommended path is /arsys.
  9. Click Next.
  10. In the Select Installation Options section, enter ARSYSTEM in the Application Name field, and click Next.
  11. In the Map Modules to Application Servers section, select the BMC Remedy AR System check box, and click Next.
  12. In the Map Virtual Hosts for Web Modules section, select the BMC Remedy AR System check box, and click Next.
  13. In the Summary section, click Finish.
  14. In the Application appName Installed Successfully section, click Save directly to the master configuration.
  15. In the WebSphere Application Server console, select ARSYSTEM and click Startto start the server.

    Note

    If you are deploying mid tier with the .war file for the mid tier home page, user form, group form, and any form created with trim fields to open:
    Stop the WebSphere server and then delete or rename the aspectjrt.jar file from the WebSphere6.1 InstallDir/lib directory (for example: /opt/IBM/WebSphere61/lib). Then, start the WebSphere server.
    This will make sure that WebSphere uses the aspectjrt.jar file provided by the mid tier.

To configure system requirements

  1. Make the following modifications:
    • On Windows, add the BMC Remedy Mid Tier lib directory to the system PATH environment variable as in the following example:
      C:\Program Files\WebSphere\AppServer\installedApps\<computerName>\<midTierName>.ear\midtier\<platform>.war\WEB-INF\lib.
    • On UNIX, modify the startServer.sh file and add <midTierInstallDir>/WEB-INF/lib as follows, depending on your operating system:

      Platform

      Path

      AIX

      LIBPATH=/usr/WebSphere/AppServer/installedApps/<computerName>/arsys.ear/midtier_<platform>.war/WEB-INF/lib;export LIBPATH

      HP_UX

      SHLIB_PATH =/usr/WebSphere/AppServer/installedApps/<computerName>/arsys.ear/midtier_<platform>.war/WEB-INF/lib;export SHLIB_PATH

      Solaris and Linux

      LD_LIBRARY_PATH=/usr/WebSphere/AppServer/installedApps/<computerName>/arsys.ear/midtier_<platform>.war/WEB-INF/lib;export LD_LIBRARY_PATH

  2. Modify the config.properties file in the <WebSphereInstallDir>/installedApps/<computerName>/<midTierName>.ear/midtier<platform>.war/WEB-INF/classes directory.
    Modify all directory references to point to your newly installed BMC Remedy AR System directories. For example, modify the following directory references as shown:
    • Windows:

      arsystem.log_filepath=<WebSphereInstallDir>\installedApps\arsys.ear\midtier_<platform>.war\work\logs
      
      arsystem.crt_working_dir=<WebSphereInstallDir>\installedApps\arsys.ear\midtier_<platform>.war\reports
    • UNIX:

      arsystem.log_filepath=<WebSphereInstallDir>/installedApps/arsys.ear/midtier_<platform>.war/work/logs
      
      arsystem.crt_working_dir=<WebSphereInstallDir>/installedApps/arsys.ear/midtier_<platform>.war/reports
  3. In the Websphere Admin Console, choose WebSphere Application Servers > serverName > Session management > Enable Cookies.
    Make sure that the path is set to the context root of the mid tier.

    Note

    BMC recommends that you use the WebSphere Application Servers > serverName > Session management > Enable Cookies > Cookie Path setting to mark the sessionID cookie as HTTPOnly. If incorrect settings are used, duplicate sessionID cookies are generated and the mid tier login functionality does not work correctly.

  4. To ensure that users can log in successfully, create a new NoAdditionalSessionInfoproperty:
    1. Choose WebSphere Application Servers > serverName > Web Container > Custom Properties.
    2. Create a new NoAdditionalSessionInfo property, and set it to True.
  5. Restart the IBM WebSphere server.

    Note

    When you start the mid tier for the first time, WebSphere might send socket I/O errors. To fix this, set the ServerIOTimeout to 300. For more information, see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21318463.

To configure the WebSphere Application Server to support the WBMP MIME type

If you are using WebSphere Application Server, perform the following steps to configure WebSphere Application Server to support the WBMP MIME type:

  1. Log in to the WebSphere Application Server Administrative Console.
  2. Expand the Environments icon (forward arrow) to Virtual Hosts.
  3. Select default_host.
  4. Select MIME Types under Additional Properties.
  5. Click New.
  6. Enter text/css in the MIME Type field.
  7. Enter css in the Extension field.
  8. Click OK to save the new MIME type.
  9. Click New.
  10. Enter image/png in the MIME Type field.
  11. Enter png in the Extension field.
  12. Click OK to save the new MIME type.
  13. Save the configuration changes.
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Jose pedro Teixeira

    Hi, When configuring system requirements on Step 3, by "Make sure that the path is set to the context root of the mid tier" what option should we use for "Cookie path":

    - Use the context root

    or

    - Set cookie path (/arsys)

    BTW regarding the other cookie setting any other recommendation?

    Thanks.

    Regards,
    Jose Pedro

    Dec 04, 2013 05:30
    1. Hemant Baliwala

      Hi Jose Pedro, 

      You need to select Use the context root.

      For other options there are no specific recommendations. 

      Thanks, 

      Hemant

      Dec 04, 2013 05:56
  2. Hemant Baliwala

    Thanks Vaibhav. 

    Looks like IBM has removed that page. I have updated the page with another relevant link. 

    Regards, 

    Hemant

    Jun 04, 2014 02:01