Deploying Java Service Interfaces

Describes the additional requirements associated with deployment of a Java-type service interface.
Restriction: This topic applies to Windows environments (local development) only.

When you deploy a Java service interface from Enterprise Developer, the deployment process creates a deployment package (.car) file. This file is installed on Enterprise Server.

The EJB and JSP client are generated simultaneously from Enterprise Developer, 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.

ED 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 the .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:

Note: To learn about alternative deployment methods, see Service Interface Deployment Methods.