Deploy the MakeCheckAppt Web Service

Stop enterprise server instances

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:

1. On the Server Explorer, expand Local [localhost:10086] > Default[127.0.0.1:86] to see a list of enterprise server instances.
2. Right-click each started enterprise server instance, and stop it by selecting Stop from the context menu.
   Note: Started enterprise server instances show with a green icon .

Start the ESSOAP enterprise server instance

Before deploying your service interface, you must start the ESSOAP instance where the MakeCheckAppt service will run.

• From the Server Explorer, right-click ESSOAP; then select Start from the context menu.
  Note: If this is the first time you have started the server, you see a sign-on dialog box. If Server is secured is checked, uncheck it; then click OK. Unchecking Server is secured prevents this dialog box from showing when you subsequently start the region. If Server is secured is not checked, simply click OK to clear the dialog box. Also, if prompted to disable password recovery, click No.

After the list on the Server Explorer refreshes, the ESSOAP entry appears with a green icon , indicating that it is started.

Set Deployment Properties

To successfully deploy a SOAP 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.

1. From the Application Explorer view, expand ProgramSOAP > Web Services
2. Right-click the MakeCheckAppt Web service; then select Web Service Properties from the context menu.
3. On the Deployment Server tab, click the Change button that corresponds to the Enterprise Server name field.
4. In the Server column, click ESSOAP; then click OK.
5. On the Application Files tab, click Legacy application needs deploying; then click Add Files.
6. Browse to your project's ProgramSOAP folder, and select the following files:
   • appoint.dat
   • consultants.dat
   • customers.dat

   These are the data files accessed by the service.

7. Click Open.
8. Click Add Files again, and browse to the ProgramSOAP\New_Configuration.bin folder.
9. Select schedule.dll , and then click Open.

   This is the executable file you need to debug the service

10. Click OK.

Deploy the MakeCheckAppt Web service

1. From the Application Explorer view, right-click the MakeCheckAppt Web service, and then click Deploy.
2. In Eclipse, click the Console tab.
3. On the icon bar, click the down arrow associated with Display Selected Console .
4. Click Service Interfaces Console to monitor deployment progress.

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.

View deployment results

Now that your SOAP Web service is deployed, you can look at its details in ESCWA.

1. In ESCWA, click Native.
2. In the navigation pane, expand Directory Servers > Default, and double-click your enterprise server instance.
3. On the General drop-down list, select Services.

   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.

4. Close ESCWA.