Deploying Applications

 

This chapter describes how to deploy your own applications using the BEA eLink Java Adapter for Mainframe WLS Edition (JAM) software. Deployment is the process of taking previously developed servlets and/or EJB's and installing them into a specific operational environment. In this case, the operational environment is your WebLogic system.

This topic consists of the following sub-topics:

• Deploying Servlets

• Deploying Enterprise Java Beans

 

---

Deploying Servlets

Please refer to the BEA WebLogic Server documentation for detailed instructions on deploying servlets.

The following steps provide an example of deploying a servlet by modifying the weblogics.properties file.

Perform the following steps to deploy a servlet:

1. Place a class file for the servlet and all other classes that it depends on into the servlet classpath. Be sure and include the class files for the DataView's that are used by the servlet.

2. Add a registration line to your weblogics.properties file. This line will specify both the URL that will be used to access the servlet and the full package and name of the servlet class. For example, assuming your server is named www.webstore.com, the properties line weblogic.httpd.register.widgets=webstore.WidgetServlet will cause the class webstore.WidgetServlet to serve requests to the URL http://www.webstore.com/widgets.

   weblogic.httpd.register.urlname=mypackage.MyServlet

   This registration line causes the WebLogic Server to use the servlet class "mypackage.MyServlet" to serve all HTTP requests for a page at the URL name (on your host).

3. Add any corresponding remote service entries into the jcrmgw.cfg file. For example, if your servlet invokes a service named widgetQuote, then you would need something like the following in your configuration:

   *JC_REMOTE_SERVICES
   widgetQuote RDOM="myMainframe"
   RNAME="WIDQUOTE"

4. Restart the WebLogic Server.

There are other servlet deployment options, including hot-deploying a servlet into a running WebLogic server. Please refer to the WebLogic Server documentation for more details.

 

---

Deploying Enterprise Java Beans

Please refer to the BEA WebLogic Server documentation for detailed instructions on deploying EJBs.

Perform the following steps to deploy an EJB:

1. Place the class file for the EJB and all other classes that it depends on into your development classpath. Be sure to include the class files for the DataView's that are used by the EJB.

2. Convert the text deployment descriptor into serialized form with the following command.

   java weblogic.ejb.utils.DDCreator MyEjbDD.txt

   This command creates the serialized deployment descriptor in the current directory.

3. Build the Home Interface implementation, remote Interface implementation and container classes by using the following command.

   java weblogic.ejbc -d dest MyEjbDD.ser

   Replace `dest' with the directory where you want the generated class files to be placed.

4. Place the class files for the generated files and the EJB (including classes it depends on) into your WebLogic classpath. Be sure and include the class files for the DataView's that are used by the EJB.

5. Edit your Weblogic properties file to add the new EJB to the weblogic.ejb.deploy property. This property should contain a comma separated list of full-paths to ejb ".ser" or ".jar" files. For example:

   weblogic.ejb.deploy=c:/mybeans/MyEjbDD.ser,c:/otherbeans/
   WebstoreEJB.jar

6. Add any corresponding local or remote service entries into the jcrmgw.cfg file. For example, if your EJB invokes a service named "widgetQuote", then you would need something like the following in your configuration:

   *JC_REMOTE_SERVICES
   widgetQuote			  RDOM="myMainframe"
                 RNAME="WIDQUOTE"

7. Restart WLS.

EJB's may also be placed into jar files before being deployed, and may be hot-deployed into a running WebLogic Server. Please refer to the Weblogic Server documentation for more details.