Configuring your BEA WebLogic web server

BMC Software recommends that you do not use the .war file to deploy the mid tier on WebLogic. Instead, use the mid tier installer and follow the configuration steps outlined in this section:

To install the mid tier with a BEA WebLogic web server

1. Install the BEA WebLogic web server. (See the BEA WebLogic product documentation.)
2. Configure a new domain. (See To configure a new domain.)
3. Install the mid tier. (See Installing BMC Remedy Mid Tier.) Choose Other for your web server and Other for your JSP engine.
4. Install an enterprise application. (See To install an enterprise application.)
5. Change the context name to the standard name. (See To change the context name to the standard name.)
6. Enable your mid tier to run Web reports. (See To enable your mid tier to run Web reports.)

7. Include arsys in the cookie path. (See To include arsys in the cookie path.)

To configure a new domain

1. Start the WebLogic Configuration Wizard.
   • On Windows, choose All Programs > BEA Products > Tools > Configuration Wizard.
   • On UNIX, make sure that you have UI access enabled. (Set your display, or run from the console.) Then, after a clean installation of WebLogic Server 9.1, go to the WebLogic ../common/bin directory, and run the config.sh script. The Welcome screen appears.
2. Select Create New WebLogic Domain, and click Next. The Select Domain Source screen appears.
3. Select Generate a domain configured automatically. The WebLogic Server (recommended) option is selected by default.
4. Click Next. The Configure Admin Username and Password screen appears.
5. In the Username field, enter weblogic.
6. In the Password fields, enter weblogic, and click Next. The Configure Start Mode and JDK screen appears.
7. Select Development Mode, and select BEA Supplied JDK (or an alternate), and click Next. The Customize Environment and Services Settings screen appears.
8. Select No, and click Next. The Create Domain screen appears.
9. Enter a Domain Name (such as testing ), enter the Domain Location, and click Create. The Creating Domain screen appears.
10. After the script finishes the configuration, click Done.
11. Start WebLogic Server.

To install an enterprise application

1. Install BMC Remedy Mid Tier. (See Installing BMC Remedy Mid Tier.)
2. Log in to the WebLogic Administration Console through a URL similar to: http://<hostName>:7001/console Use the login information that you specified in step 5 and step 6 in To configure a new domain.
3. Under the Change Center, complete the following steps:
   1. Click Lock and Edit.
   2. Click the Deployments folder.
   3. Click Install.
   4. Click Location (host name), and go to the directory in which the mid tier is installed.
   5. Click Next.
   6. Select Install this deployment as an application, and click Next.
   7. In the Name for deployment field, enter arsys, and click Next.
   8. Click Finish, and click Save.
4. Under the Change Center, click Activate Change.
5. Click Start.
6. On Windows platforms, verify that the mid tier installer added the \WEB-INF\lib mid tier installation directory path in the PATH variable.
7. On UNIX systems, update the mid tier installation path in the BEA WebLogic start script as follows:
   1. Stop the WebLogic server.

   2. Update the BEA WebLogic start script with the appropriate path:

      Platform	Path
      Linux	LD_LIBRARY_PATH=/usr/ar/mid tier/WEB-INF/lib:$LD_LIBRARYPATH;export LD_LIBRARY_PATH

   3. Restart the WebLogic server.

To change the context name to the standard name

1. Create a weblogic.xmlfile the following directory:
   • Windows — <MidTierInstallDirectory>\WEB-INF\
   • Unix — <MidTierInstallDirectory>/WEB-INF/

2. Change the context name to the standard name of arsys by adding the following lines to the file:

   <?xml version="1.0" encoding="ISO-8859-1" ?>
   <!DOCTYPE weblogic-web-app>
   <weblogic-web-app>
   <context-root>arsys</context-root>
   </weblogic-web-app>

To enable your mid tier to run Web reports

1. Shut down the Weblogic Server.
2. Open weblogic.xml with a text editor.

3. Add the following lines before the <context-root> line:

   "xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"    
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"   
   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee   
   http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd    
   http://xmlns.oracle.com/weblogic/weblogic-web-app   
   http://xmlns.oracle.com/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"> 

4. Add the following lines after the <context-root> line:

   <container-descriptor>
   <prefer-web-inf-classes>true</prefer-web-inf-classes>
   </container-descriptor>

   For example:

   <weblogic-web-app>
   "xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"    
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"   
   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee   
   http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd    
   http://xmlns.oracle.com/weblogic/weblogic-web-app   
   http://xmlns.oracle.com/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"> 
   <container-descriptor>
   <prefer-web-inf-classes>true</prefer-web-inf-classes>
   </container-descriptor>
   <context-root>arsys</context-root> 
   </weblogic-web-app>

5. Save weblogic.xml.
6. Restart the Weblogic server.

To include arsys in the cookie path

1. Shut down the Weblogic Server.
2. Open weblogic.xml with a text editor.

3. Add the following lines to the file:

   <session-descriptor>
   <cookie-path>/arsys</cookie-path>
   </session-descriptor>

4. Save weblogic.xml.
5. Restart the Weblogic server.