Siebel Store-and-Forward Messaging Guide for Handheld > Installation and Configuration of Siebel Store-and-Forward Messaging > 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 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 Siebel SupportWeb.

     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 Siebel SupportWeb.
   • 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 comes as a Zip file delivered as part of the Siebel Server installation package in <Siebel_Server>\classes\SiebelSMQServlet.war.

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 server or engine. Alternatively, it might mean running a configuration utility built into the server or engine. 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. Open the web.xml file in a text editor and change the DataDir parameter to specify the directory where you want the queues to be stored.
5. 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.