Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Installation and Configuration of Siebel Store-and-Forward Messaging > Process of Deploying IBM MQe Queue Managers >

Installing the MQe Servlet


You deploy MQe as a Java 2 Enterprise Edition (J2EE)-compliant Web application, or servlet. You install this Web application into a J2EE-compliant Web server or Web server plug-in (container or servlet container).

To perform this procedure, it is recommended that you first be familiar with installing Java servlets on the Web server.

To install the MQe Servlet

  1. Make sure your system meets the following requirements:
    • The MQe Queue Manager servlet deployment requires a J2EE-compliant Web server or servlet engine that is capable of running Java servlets. For information about the required J2EE servlet specification version, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

      NOTE:  The Microsoft IIS Web server does not support servlets. However, third-party plug-ins are available that allow you to run servlets on IIS. Other Web servers such as Tomcat include servlet support by default.

    • Each computer running an MQe Queue Manager must have a Java Runtime Environment (JRE) installed. For information about the required Java Runtime Environment (JRE) version, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.
    • The servlet uses your Web server's existing port (generally port 80, the default for HTTP). Your firewall must permit inbound connections on this port for mobile clients or regular Internet users.
  2. Locate the MQe servlet on your installation media.

    The servlet is delivered as part of the Siebel Server installation package, in the <Siebel_Server>\classes\SiebelSMQServlet.war file. You can open .war files with winzip or any extraction tool that can decompress zip files.

  3. Follow the procedure specific to your Web server or servlet engine for installing the MQe servlet.

    This might mean copying the servlet directory tree into a directory that is specified by the Web server or servlet engine. Alternatively, it might mean running a configuration utility built into the server or engine. For a Tomcat server, you run the Tomcat Manager utility and deploy Context Path /smq using the complete path to your SiebelSMQServlet.war file as the WAR or Directory URL. For details of this procedure, see the documentation for your Web server or servlet engine.

    The MQe queue manager is deployed in a directory that conforms to the J2EE Web application specification. This structure consists of specially-named subdirectories containing the necessary Java class files and configuration information. The layout is as follows:

    <root>\
    WEB-INF\
    web.xml
    lib\
    MQeBase.jar
    MQeSecurity.jar
    SiebelSMQ.jar

    The files in this directory structure are described in the following table.

    File
    Comments

    web.xml

    Deployment descriptor file that configures the servlet according to the J2EE servlet specification

    MQeBase.jar

    Redistributable binary file from MQe

    MQeSecurity.jar

    Redistributable binary file from MQe

    SiebelSMQ.jar

    Siebel servlet implementation

  4. If the Web server you are preparing is a UNIX machine, perform the following steps; otherwise, skip to Step 5:
    1. Make a backup copy of the .cshrc file for the administrator account that will run MQE.
    2. Open the .cshrc file and locate the following line, where $HOME/${build} is the directory in which you installed your Siebel Server software:

    if (-f $HOME/${build}/ses/siebsrvr/siebenv.csh) source $HOME/${build}/ses/siebsrvr/siebenv.csh

    1. Add the following environmental variables immediately following the line described in Step b:
      • JAVA_HOME
      • PATH

        Typical commands for setting these variables would be similar to the following:

    setenv JAVA_HOME /user/jdk1.5.0_10

    setenv PATH {$PATH}:/usr/jdk1.5.0_10:/usr/jdk1.5.0_10/bin:/usr/jdk1.5.0_10/jre:/usr/jdk1.5.0_10/jre/bin

    1. Make sure that the lines that define the following environmental variables include the location of the libjvm.so file and the parent folder:
      • LD_LIBRARY_PATH (for Enterprise Linux (EL), Linux, and Solaris)
      • SHLIB_PATH (for HP)

        Typical commands for setting these variables would be similar to the following:

    setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:/usr/openwin/lib:/usr/dt/lib:/usr/
    jdk1.5.0_10/jre/lib/i386/server:/usr/jdk1.5.0_10/jre/lib/i386

    1. To initialize the modified variables, exit from the session and open a new session.
  5. Make a backup copy of the Web server's web.xml file, then open the web.xml file in a text editor and complete the following steps to change the DataDir parameter to specify the directory where you want the queues to be stored:
    1. Locate the following portion of the file:

    <web-app>
    ...
        <servlet>
    ...
            <servlet-name>ServerQM</servlet-name>
            <init-param>
                <param-name>DataDir</param-name>
    ...
                <param-value>CHANGE_ME</param-value>
            </init-param>
        </servlet>

    1. Replace CHANGE_ME with the path to the directory where you want Store-and-Forward Messaging queues to be located.

      NOTE:  Queues will be located in the MQe\servlet-name subdirectory of the directory that you specify. For example, if you specify a DataDir value of C:\Siebel and leave the default servlet name of ServerQM unchanged, then queues will be located in C:\Siebel\MQe\ServerQM.

    2. Save and close the web.xml file.
  6. Restart the servlet.

    At runtime, after the first time the servlet runs, the system populates the directory specified by the web.xml file's DataDir parameter with the queues.

After installation, the servlet starts automatically the first time a client or a Siebel Server accesses it. The servlet shuts down when the Web server shuts down.

Siebel Store-and-Forward Messaging Guide for Mobile Web Client Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.