Configuring a J2EE servlet container

This procedure describes how to configure Control-M for Java to work in a J2EE servlet container server, which enables Control-M for Java applications to run in the J2EE servlet container environment.

Before you begin

Ensure the following:

• Control-M for Java must be installed on the computer where the J2EE Server is installed.
• In UNIX, the Control-M/Agent user must be the same user as the J2EE Server user.

  Control-M/Agent and the J2EE Server shares files located under the Control-M for Java installation path.

To configure the J2EE servlet container:

1. Navigate to the following directory:

   <CONTROL-M Agent location>/cm/JAVA/exe

2. Copy the CTMJAVA.jar file to the J2EE Servlet Container server class path.

   EXAMPLE: In a Tomcat servlet container, copy the file to the following:

   <Tomcat location>/shared/lib

3. Set up the J2EE servlet container by configuring a servlet, which enables the servlet container to start Control -M for Java as a servlet. You can use the following example below (taken from Tomcat, web.xml) to configure a servlet.

   <servlet>

   <servlet-name>CTM_JAVA_CONTAINER_1</servlet-name>

   <servlet-class>com.bmc.ctm.bpi.cm.ejb.servlet.CMExtension</servlet-c

   lass>

   <init-param>

   <param-name>ACCOUNT</param-name>

   <param-value>CTM_JAVA_CONTAINER_1_CONNECTION PROFILE</param-value>

   </init-param>

   <init-param>

   <param-name>CM_ROOT</param-name>

   <param-value>c:\Program Files\BMC Software\CONTROL-M

   Agent\Default\CM\JAVA\</param-value>

   </init-param>

   <load-on-startup>1</load-on-startup>

   </servlet>

   NOTE: Each servlet container account must have its own servlet definition, with a unique servlet name.

   For information the servlet parameters, see Servlet parameters.