Deploy the REST Web service

Build the ProgramCORS Project

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

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

Set Deployment Properties

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

1. From the Solution Explorer, right-click the AccessBooks.svi service interface file; then click Properties.
2. Click the Application files to deploy field, and then click its corresponding browse button to add the following files:

   File	Project Folder
   bookfile.dat	ProgramCORS
   bookfile.idx	ProgramCORS
   book.dll	ProgramCORS > bin > x86 > Debug

   These files are copied to the enterprise server instance when you deploy. The .dat and .idx files are the data and index parts of the indexed file accessed by the service. The .dll is the executable file you need to debug the service.
3. Click OK to accept the default values for all other fields and close the dialog box.

Associate the ESCORS Enterprise Server Instance

You need to associate the ESCORS enterprise server instance with your ProgramCORS project:

1. From Server Explorer, expand localhost under Micro Focus Servers to see a list of available enterprise server instances.
2. Right-click ESCORS; then click Associate with Project > ProgramCORS.

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 ESCORS Enterprise Server Instance

Before deploying your service interface, you must start the ESCORS instance where the AccessBooks service will run.

1. From the Server Explorer, right-click ESCORS; 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 Server is secured is checked, uncheck it; then click OK. Unchecking Server is secured prevents this dialog box from showing when you subsequently start the region. If Server is secured is not checked, simply click OK to clear the dialog box.

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

Deploy the AccessBooks Web Service

• From the Solution Explorer, right-click the AccessBooks Web service; then click Deploy.

The Output window shows the progression of the deployment process. If deployment was successful, you should see a message: Deployment completed with warnings. If you scroll up to see the log output, notice that the deployment process changed the direction of the slashes in some directory specifications. This is normal behavior for successful deployment.

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 ESCORS enterprise server, you can look at the details of the deployed service via the Enterprise Server Administration page.

1. If you have closed the Enterprise Server Administration window in Enterprise Developer, start it again.

   In the row showing information for the ESCORS enterprise server instance, you should see that the Objects column shows the number of services that this enterprise server instance runs.

2. Click the Details button for the ESCORS Services.

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