To successfully deploy a REST service interface to an enterprise server region, you need to first set some options in Enterprise Developer.
To ensure that the deployment process runs smoothly, you must set some options that tell Enterprise Developer where to find certain files.
File | Location |
---|---|
|
|
schedule.dll | Your project's ProgramREST\bin\x86\Debug folder |
These files are copied to the enterprise server when you deploy. The .dll is the executable file you need to debug the service. The .dat files are data files accessed by the service.
You need to associate the ESDEMO enterprise server region with your ProgramREST project:
Before deploying your service interface, you must start the ESDEMO region where the ProgramREST service will run.
The Enterprise Server Console Daemon is then invoked, starting the ESDEMO enterprise server region.
You need to generate a .dll executable file from your project to deploy with your service interface. This is necessary so that you can debug the service after generating a client.
The Output window shows the progression of the deployment process. If deployment is successful, you should see a message indicating that deployment was completed. If the deployment process produced some warnings, this does not affect the validity of the deployment process.
If deployment were to fail, 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 ESDEMO enterprise server, you can look at the details of the deployed service via the Enterprise Server Administration page.
The Enterprise Server Administration Home page starts in Enterprise Developer.
In the row showing information for the ESDEMO enterprise server, you should see that the Objects column shows the number of services that this enterprise server region runs. In this case, the number of running services should be at least 7. These are the five that come standard with the ESDEMO enterprise server, plus the one service you added containing two operations. You might see more if you have deployed other services to the ESDEMO enterprise server.
In the row showing your new service, ProgramREST, 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.