Deployment Services

Restriction: This topic applies only when the Enterprise Server feature is enabled.

All deployment services must have their Service Class attribute set to 'MF deployment'. They must be associated with a listener that uses the conversation type 'Web'.

The configuration information for a deployment service looks like this:

[MF client]
 scheme=http
 URL=virtual-directory-name-1/mfdeploy.exe/virtual-directory-name-2
 accept=application/x-zip-compressed

where virtual-directory-name-1 specifies the directory that holds the deploy program, mfdeploy.exe, and virtual-directory-name-2 specifies a directory to contain deployed services.

The values for the scheme and accept parameters must not be changed, but when you are creating a new deployment service you can omit them, as these are the defaults.

The settings for the Deployer service of ESDEMO are:

[MF client]
 scheme=http
 URL=/cgi/mfdeploy.exe/uploads
 accept=application/x-zip-compressed

The configuration of a deployment service must match the configuration of the listener for the service. The URL parameter must specify the same virtual directory name for the location of the mfdeploy.exe program that the listener uses. You can change the virtual path to receive deployed services to any virtual directory name configured for the listener.

For example, if the listener's configuration was:

[virtual paths]
 <default>=/dev/null
 studioenterpriseedition=<ES>/bin
 project1=c:/development/project1
 project2=c:/development/project2

then you might create a deployment service named "project1" with this configuration:

[MF client]
 scheme=http
 URL=/studioenterpriseedition/mfdeploy.exe/project1
 accept=application/x-zip-compressed

and services deployed using the "project1" service would be stored under c:\development\project1. You could create a similar service for project2.

For example, if the listener's configuration was:

[virtual paths]
 <default>=/dev/null
 studioenterpriseedition=<ES>/bin
 project1=home/development/project1
 project2=home/development/project2

then you might create a deployment service named "project1" with this configuration:

[MF client]
 scheme=http
 URL=/studioenterpriseedition/mfdeploy.exe/project1
 accept=application/x-zip-compressed

and services deployed using the "project1" service would be stored under /home/development/project1. You could create a similar service for project2.

Note that the deployment directory must have a .mfdeploy file. Copy the .mfdeploy file from %ProgramFiles(x86)%\Micro Focus\Visual COBOL\deploy (Windows) or $COBDIR/deploy (UNIX) and modify it as necessary.

For example, if COBOL Server is installed in %ProgramFiles(x86)%\Micro Focus\Visual COBOL, then "<ES>/deploy" becomes %ProgramFiles(x86)%\Micro Focus\Visual COBOL\deploy (Windows).