The mfdepinst command handles the server-side part of the process of deploying a service to an enterprise server. The tool installs the files contained in a .car to an enterprise server instance by extracting the deployment package files (.int, .idt, etc.) from the .car file, updating the Directory Service directory for the new services and packages, and if the enterprise server is running, informs it of the new services so they are available for use.
mfdepinst [install-options] myservice.car
Run mfdepinst from a Visual COBOL command prompt from the same directory that contains the .car file.
You can specify mfdepinst installation options in one of the following ways:
If using .mfdeploy, before running mfdepinst, copy the .mfdeploy file in the $COBDIR/deploy to the parent directory of the directory that contains the .car file.
Comments:
The mfdepinst command extracts files from the .car file and installs them on the enterprise server specified as specified using install-options at the command line or in an .mfdeploy file in the parent directory (../.mfdeploy).
The .mfdeploy file specifies the location, name, and listener for the enterprise server to which the service interface is deployed. So, for example, if the .car file is in $COBDIR/myservice/myservice.deploy , the .mfdeploy file must be in $COBDIR/myservice.
Edit .mfdeploy as necessary to specify values other than the default values.
mfdepinst records its progress in the file deploylog.txt in the current directory, overwriting any existing deploylog.txt. After mfdepinst completes, you can examine this file to find out if deployment succeeded.
Beginning with Visual COBOL 5.0, the .mfdeploy file supports an extended syntax and additional settings. See the associated related reference topic for more information.