You need to build the project to generate all required deployment files.
To successfully deploy a REST Web service to an enterprise server instance, you need to first set some options that tell Enterprise Developer where to find certain files.
These are the data files accessed by the service.
This is the executable file you need to debug the service
You need to associate the ESCORS enterprise server instance with your ProgramCORS 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 ESCORS instance where the AccessBooks service will run.
After the list on the
Server Explorer refreshes, the ESCORS 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 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.
Now that your REST Web service is deployed, you can look at its details in ESCWA.
See the row showing under your new service, AccessBooks - you should see that the Last Status column shows all four operations as Available. This means that the service is ready to be accessed by a client.