Deploying the Default Service

The default service, MFCLISRV, is provided in a COBOL archive file, csbind.car. You can install the service to your enterprise server using the imtkmake or mfdepinst utilities.

For example, to deploy the MFCLISRV service under the ESDEMO server using the default configuration:

At the command prompt, change to the deployment directory for ESDEMO; this is Base\Deploy under your Net Express installation, $COBDIR/deploy in Server Express.

Create a subdirectory named "csbind" and change to it.

Copy csbind.car to the csbind directory.

Run "mfdepinst csbind.car".

When mfdepinst completes, look at the file deploylog.txt in the current directory to see if deployment completed successfully.

The deployment process extracts the files needed to run servers under Server Enterprise Edition. These are:

mfes-csbsrvr.int, the program that runs the servers

mfcsbind.idt, the Interface Definition Table file for the service

It then creates two new objects in the Micro Focus Directory Server repository, under the enterprise server where the service is being installed. These are:

A package named "CSBIND", which specifies mfes-csbsrvr.int as the package module and mfcsbind.idt as the interface definition. This package can be used for all CSBIND services for this Enterprise Server.

A service named "MFCLISRV" is created. MFCLISRV uses the CSBIND package and is associated with the default listener for services deployed to this server ("Web Services and J2EE" in the default configuration).

You can use the MFCLISRV as the service for all of your Client/Server Binding applications or you can use Enterprise Server Administration to create additional services that use the CSBIND package (see the section Adding Extra Services). The client part of the application supplies the name of the server program when making the connection, so more than one application can use the same service.