Work through the following sections to prepare your project and Web service for deployment, and to deploy and verify.
To successfully deploy a REST Web service to an enterprise server instance, you need to first set some options that tell Enterprise Developer the name of your enterprise server instance, and where to find certain files.
Files | Location | Description |
---|---|---|
appoint.dat consultants.dat customers.dat |
Your project's ProgramREST folder |
Data files accessed by the service |
schedule.dll |
Your project's New_Configuration.bin folder |
The executable file you need to debug the service |
These files are copied to the enterprise server when you deploy.
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:
Before deploying your service interface, you must start the ESREST instance that runs the MakeCheckAppt Web service.
The Enterprise Server Daemon is then invoked via the Console, starting the ESREST enterprise server instance.
The Console view 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 Console view 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 service interface has been deployed as a service running on the ESREST enterprise server, you can look at the details of the deployed service via the Enterprise Server Administration page.
In the row showing information for the ESREST enterprise server instance, you should see that the Objects column shows the number of services that this enterprise server instance runs.
In the row showing your new service, MakeCheckAppt, you'll notice that the Current Status column shows both operations as Available. This means that the service is ready to be accessed by a client.