Service Interface Deployment Methods

Restriction: This topic applies to Windows environments (local development) only.
Restriction: This topic applies only when the Enterprise Server feature is enabled.

The following scenarios cover four possible deployment methods:

Deploy from your Eclipse project
This is the easiest and most straightforward way to deploy. Visual COBOL provides a service interface Deploy option that automatically generates a deployment package (.car file) and installs it on the enterprise server instance associated with your project. See To generate and deploy a service interface from a project for instructions.
Deploy using the imtkmake command
The imtkmake command enables you to generate a deployment package (.car file) and deploy it to Enterprise Server from the command line. See To deploy a service interface using imtkmake and imtkmake command for details.
Deploy using the mfdepinst command
Use the mfdepinst command to install an existing deployment package to Enterprise Server without generating a new deployment package. This enables you to deploy the same .car to multiple enterprise server instances. See To install a deployment package using mfdepinst and mfdepinst command for details.
Deploy manually
While we recommend that you use one of the first two deployment scenarios, it is possible to perform all the deployment steps manually without a deployment package. You can create all the necessary pieces, copy them manually to the Enterprise Server system, and add package and service objects to the configuration from the Micro Focus Directory Server interface. For more information, see Work with Packages and Work with Services.
Note: EJB service interfaces require, in addition to deploying the service interface to Enterprise Server, that you also deploy the EJB and JSP client to a Java application server. See Deploying Java Service Interfaces and JSP Client for more information.