Work through the following sections to prepare your project and Web service for deployment, and to deploy and verify.
You need to build the project to generate all required deployment files.
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 ESSOAP instance where the MakeCheckAppt service will run.
After the list on the
Server Explorer refreshes, the ESSOAP entry appears with a green icon
, indicating that it is started.
To successfully deploy a SOAP 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
The Output window shows the progression of the deployment process. If deployment was successful, you should see a message: Installation of package "MakeCheckAppt.car" finished with 6 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 SOAP Web service is deployed, you can look at its details in ESCWA.
At the bottom of the right pane, you should see both operations marked as Available. This means that the service is ready to be accessed by a client.