Deploy a Service Interface

Build the ProgramSOAP Project

You need to build the project to generate all required deployment files.

• On the Solution Explorer, right-click the ProgramSOAP project; then click Build.

Set Deployment Properties

To ensure that the deployment process runs smoothly, you must set some options that tell Visual COBOL where to find certain files.

1. From the Solution Explorer, right-click the ProgramSOAP service interface; then click Properties.
2. Ensure that the Interface type property is set to SOAP Web Service (default).
3. Click the Application files to deploy field, and then click its corresponding browse button to add the following files:

   Files	Location	Description
   appoint.dat consultants.dat customers.dat	Your project's ProgramSOAP folder	Data files accessed by the service.
   schedule.dll	Your project's ProgramSOAP\bin\x86\Debug folder	The executable file you need to debug the service.

   These files are copied to the enterprise server instance when you deploy. The .dat files hold the data accessed by the service. The .dll is the executable file you need to debug the service.
4. Accept the default values for all other fields.

Stop Enterprise Server Instances

To ensure that your enterprise server instance does not encounter any port conflicts with other enterprise server instances that use the same listener port, stop all started enterprise server instances as follows:

1. From the Server Explorer, expand localhost under Micro Focus Servers to see a list of enterprise server instances.
2. Right-click each started enterprise server instance, and stop it by selecting Stop from the context menu. Started enterprise server instances show with a green icon .

Start the ESSOAP Enterprise Server Instance

Before deploying your service interface, you must start the ESSOAP instance where the ProgramSOAP service will run.

1. From the Server Explorer, expand localhost under Micro Focus Servers to see a list of available enterprise server instances.
2. Right-click ESSOAP; then select Start from the context menu.
   Note: If this is the first time you have started the server you see a sign-on dialog box. If Store Credentials is checked, uncheck it; then click OK. Unchecking Store Credentials prevents this dialog box from showing when you subsequently start the region.

The Enterprise Server Console Daemon is then invoked, starting the enterprise server instance.

Deploy the ProgramSOAP service interface

• From the Solution Explorer, right-click the ProgramSOAP service interface; then click Deploy.

The Output window shows the progression of the deployment process. If deployment was successful, you should see a message indicating success.

If deployment ever fails, you should find a message in the Output window indicating why it failed. Also, the failure message contains the path to the deployment log file. You can type the address into a browser and view the log file from there.

View deployment results

Now that your service interface has been deployed as a service running on the ESSOAP enterprise server, you can look at the details of the deployed service Enterprise Server Administration page.

1. From Server Explorer, right-click Micro Focus Servers; then click Administration.

   The Enterprise Server Administration Home page appears in a window of the Visual Studio IDE.

   In the row showing information for the ESSOAP enterprise server, you should see that the Objects column shows the number of services that this enterprise server runs. In this case, the number of running services should be at least 8. These are the four that come standard with the enterprise server, plus the one service you added containing four operations.

2. Click the Details button for the ESSOAP Services.

   In the row showing your new service, ProgramSOAP, you'll notice that the Current Status column shows all four operations as Available. This means that the service is ready to be accessed by a client.