Describes the additional requirements associated with deployment of a Java-type service interface.
Restriction: This topic applies only when the Enterprise Server feature is enabled.
When you deploy a Java service interface from
Visual COBOL, the deployment process creates a deployment package (.car) file. This file is installed on
The EJB and JSP client are generated simultaneously from
Visual COBOL, and are packaged into a Java
.ear file. Because the EJB and JSP client run under a third-party Java application server, you must deploy the generated Java
.ear file to the application server.
Visual COBOL generates a .car file when you deploy the svi to your ESI. When you are ready to put the service interface into a production
environment, you must also deploy the EJB and optionally, a JSP client, to the Java application server of your choice.
Once a Java service interface is ready for use in a production environment, you should deploy it to an enterprise server using
.car file generated during the last deployment. You can either use the
mfdepinst command to deploy the
.car file, or you can deploy it manually.
Depending on the Java application server you are using, additional deployment tasks are likely required. We recommend that
you become familiar with these by reviewing the topics contained in the
Deploying EJBs and Resource Adapters documentation.
Be mindful of the following as well:
- If the service has been mapped as an EJB interface, you might need to perform one or both of the following tasks in addition
to deploying the
- Deploy the EJB to a Java application server
- Deploy a resource adapter
- Some Java application servers require that you set some deployment options that tell
Visual COBOL what application server to use and where to find certain files. For more information, see your application server documentation,
To set deployment properties and
To modify the CLASSPATH property for a Java-based service interface topics.
- For some Java application servers, you might be required to select which application files to deploy, and select one or more
deployment locations. See
To add or remove application files to deploy for more information.
- If you generate a client for your Java service, the
.car file is deleted from the deployment folder. When setting up your service in a production environment, be sure to deploy this
file before generating a client.
Note: To learn about alternative deployment methods, see
Service Interface Deployment Methods.