Deploying EJBs Overview

An EJB running a COBOL service runs in two places: the COBOL service runs under an enterprise server, and the EJB and client run under a third party J2EE application server, such as WebSphere or WebLogic.

You deploy the COBOL service from the .car file or, if you are a developer, by using the Deploy tool in the Interface Mapping Toolkit.

You deploy the EJB and client by deploying the following to a J2EE application server:

• The enterprise archive file myservice.ear. This file is created automatically when you generate a Java client. The file contains the:
  • EJB archive file myservice.jar. This file is created when you generate a client and also when you use the Deploy tool to deploy the service interface.
  • Client archive file myservice.war. This file is created when you generate a client.

  If you haven't generated an .ear file, but have only the .jar file, you might be able to deploy the .jar file instead. Your J2EE application might require you to package the .jar file into an .ear before deploying it, or you might find it simpler to do that.

• One of the supplied resource adapters, mfcobol*.rar. A resource adapter enables the EJB to communicate through its J2EE application server with an enterprise server. Resource adapters are also known as J2EE connectors and they are packaged in resource archive (.rar) files.

Many J2EE application servers are supported, such as BEA WebLogic and IBM WebSphere. Each application server has different deployment requirements and different utilities to help.