Walks you through the steps required to associate an
enterprise server instance with your project, build the project, set deployment properties, deploy the service interface, and verify the deployment results.
Restriction: This topic applies to Windows environments (local development) only.
To successfully deploy a SOAP service interface to an
enterprise server instance, you need to first set some options in
Enterprise Developer.
Set Deployment Properties
To ensure that the deployment process runs smoothly, you must set some options that tell
Enterprise Developer
the name of your
enterprise server instance, and where to find certain files.
- From the
Team Developer Tree View, expand
ProgramSOAP > Web Services
- Right-click the
ProgramSOAP Web service; then select
Web Service
Properties from the context menu.
- On the
Deployment Server tab, click the
Change button that corresponds to the
Enterprise Server name field.
- In the
Server column, click
ESSOAP; then click
OK.
- On the
Application Files tab, click
Legacy application needs deploying; then click
Add Files to add the following files:
Files
|
Location
|
Description
|
- appoint.dat
- consultants.dat
- customers.dat
|
Your project's
ProgramSOAP 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 instance when you deploy. The
.dat files hold the data accessed by the service. The
.dll is the executable file you need to debug the 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 as follows:
- If the Server Explorer in
Enterprise Developer is not active, click
Window > Show View > Other > Micro Focus > Server Explorer; then click
OK.
- From the Server Explorer, expand
Local [localhost:86]
to see a list of
enterprise server instances.
- Right-click each started
enterprise server instance, and stop it by selecting
Stop from the context menu. 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 ProgramSOAP service will run.
- If the Server Explorer in
Enterprise Developer is not active, click
Window > Show View > Other > Micro Focus > Server Explorer; then click
OK.
- From the Server Explorer, expand
Local [localhost:86]
to see a list of available
enterprise server instances.
- 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
Store Credentials is checked, uncheck it; then click
OK. Unchecking
Store Credentials prevents this dialog box from showing when you subsequently start the region.
The
Enterprise Server Daemon is then invoked via the Console, starting the
enterprise server instance.
Deploy the ProgramSOAP
Web Service
- In Eclipse, click the
Console tab.
- On the icon bar, click the down arrow associated with
Display Selected Console
.
- Click
3 Service Interfaces Console.
- From the
Team Developer Tree View, right-click the
ProgramSOAP Web Service; then click
Deploy.
The
Console view shows the progression of the deployment process. If deployment was successful, you should see a message indicating success.
Note: If the console switches to the
Micro Focus Build view after deployment, switch the view back to
Service Interfaces Console to review the deployment log.
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 service interface has been deployed as a service running on the ESSOAP enterprise server, you can look at the details of the deployed service Enterprise Server Administration page.
- From Server Explorer, right-click
Local [localhost:86]; then click
Open Administration Page.
The Enterprise Server Administration Home page appears in
a window of the Eclipse IDE.
In the row showing information for the ESSOAP enterprise server, you should see that the
Objects column shows the number of services that this enterprise server runs. In this case, the number of running services should be at least 8. These are the four that come standard with the enterprise server, plus the one service you added containing four operations.
- Click the
Details button for the ESSOAP Services.
In the row showing your new service,
ProgramSOAP, you'll notice that the
Current Status column shows all four operations as
Available. This means that the service is ready to be accessed by a client.