You need to build the ProgramRESTAPI project to generate all required deployment files.
You need to associate the ESRSTAPI enterprise server instance with your ProgramRESTAPI project:
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:
Before deploying your service interface, you must start the ESRSTAPI instance where the CarTracker service will run.
After the list on the Server Explorer refreshes, the ESRSTAPI entry appears with a green icon , indicating that it is started.
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.
Now that your RESTful Web service is deployed, you can look at its details in ESCWA.
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.