Deploy the CarTracker Web Service

Guides you through the steps required to deploy the CarTracker Web service to the ESRSTAPI enterprise server, and verify the deployment results.

Build the ProgramRESTAPI project

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

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

Associate the ESRSTAPI enterprise server instance

You need to associate the ESRSTAPI enterprise server instance with your ProgramRESTAPI project:

  1. From the Server Explorer, expand localhost under Micro Focus Servers to see a list of available enterprise server instances.
    Note: If the list does not include the ESRSTAPI server, right-click Micro Focus Servers and select Refresh from the context menu.
  2. Right-click ESRSTAPI; then click Associate with Project > ProgramRESTAPI.

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, if any, as follows:

  1. On 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.
    Note: Started enterprise server instances show with a green icon Started enterprise server instance.

Start the ESRSTAPI enterprise server instance

Before deploying your service interface, you must start the ESRSTAPI instance where the CarTracker service will run.

  • From the Server Explorer, right-click ESRSTAPI; then select Start from the context menu.

    After the server starts, the Server Explorer refreshes, and the ESRSTAPI entry appears with a green icon Started enterprise server instance, indicating that it is started.

Deploy the CarTracker Web service

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

The Output window shows the progression of the deployment process. If deployment was successful, you should see a message: Deployment completed successfully

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 RESTful Web service is deployed, you can look at its details in ESCWA.

  1. In ESCWA click Native.
  2. In the ESCWA navigation pane, expand Directory Servers > Default, and then select ESRSTAPI.
    Note: If you have followed this tutorial up to this point without using ESCWA for another purpose, it should already be in the configuration described in steps 1 and 2.
  3. On the General drop-down list, select Services.

    In the rows under your new service, CarTracker, you should see that the Last Status column shows all three operations as Available. This means that the service is ready to be accessed by a client.

    In addition, the name of the service and the Package columns for all operations display /temppath/CarTracker/1.0. This is the base URI used to identify the Web service in Enterprise Server. In a JSON request, the base URI, combined with the path specification for a particular operation, identifies which operation to launch. See Operation Paths for more information.