To successfully deploy a REST service interface to an enterprise server instance, you need to first set some options in Enterprise Developer.
You need to build the project to generate all required deployment files.
To ensure that the deployment process runs smoothly, you must set some options that tell Enterprise Developer where to find certain files.
Files | Location | Description |
---|---|---|
|
Your project's ProgramREST folder |
Data files accessed by the service. |
schedule.dll | Your project's ProgramREST\bin\x86\Debug folder | The executable file you need to debug the service. |
These files are copied to the enterprise server when you deploy.
You need to associate the ESREST enterprise server instance with your ProgramREST 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 as follows:
Before deploying your service interface, you must start the ESREST instance where the MakeCheckAppt service will run.
The Enterprise Server Console Daemon is then invoked, starting the ESREST enterprise server instance.
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 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.