Walks you through the process of creating and configuring an
enterprise server instance, ESSOAP, to use in this tutorial.
Restriction: This topic applies only when the Enterprise Server feature is enabled.
Restriction: This topic applies to Windows environments (local development) only.
To successfully deploy and run (debug) a Web Services service interface, you must have an
enterprise server instance started in
Enterprise Server. For these tutorials, you create and configure the ESSOAP
enterprise server instance.
Create ESSOAP
In this section, you create the ESSOAP
enterprise server instance from the Server Explorer in
Visual COBOL.
- If the Server Explorer is not loaded, click
; then click
OK.
- On the Server Explorer,
right-click
Local [localhost:86]; then select
New > Enterprise Server.
- In the
Name field, type
ESSOAP.
- Click the
Browse button associated with the
Template field.
The default location for
Enterprise Server templates is
%ProgramFiles(x86)%\Micro Focus\Visual COBOL\etc\ServerTemplates.
- Double-click
ESTemplate.xml to select it.
Note: If the
Template field does not show the path and
ESTemplate.xml file, browse to the
Enterprise Server template location to find and select the file.
- Click
Finish.
Start
Enterprise Server Administration
- From the Server Explorer, right-click
Local [localhost:86]; then click
Open Administration Page.
The
Enterprise Server Administration Home page starts in a
Visual COBOL integrated browser.
Configure a Listener Port
When you create a service interface, it is configured by default to use port number 9003 to send messages to
Enterprise Server, which listens for incoming messages on its Web Services and J2EE listener. You need to set the endpoint address for the
Web Services and J2EE listener to match the port number for the service interface.
- On the
Enterprise Server Administration Home page, in the
Communications Processes column for the
ESSOAP server, click the
Details button.
This takes you to the Communications Processes page for
Enterprise Server listeners.
- Click the
Edit button that corresponds to
Web Services and J2EE Listener.
- Change the contents of the
Endpoint Address field to
*:9003.
- Click
OK.
This returns you to the Communications Processes page.
- Click
Home to return to the Home page.
Important: If you do not have Administrator privileges to the
Visual COBOL installation directory, continue with the configuration. Otherwise, configuration for the ESSOAP
enterprise server instance is complete at this point.
Create and Configure a Deployment Folder
Note: The default deployment folder used by
Enterprise Server is a subfolder to your
Visual COBOL installation folder. If you have Administrator privileges to the
Visual COBOL installation structure, or if you started
Visual COBOL using
Run as Administrator, you are not required to complete this section of the tutorial. Otherwise, you must complete this section to create and configure an alternative deployment folder.
- Create the
deploy folder
- Without Administrator privileges, you cannot deploy to
Enterprise Server from the default
Visual COBOL deployment folder. To ensure successful deployment, create a
deploy folder in your
ProgramSOAP project.
- In the
COBOL Explorer, right-click the project; then select
from the context menu.
- In the
Folder name field, type
deploy; click
Finish.
Note: To ensure that you can see the
deploy folder in COBOL Explorer:
- Click
.
This opens the
Available Customizations dialog box.
- Uncheck
Empty folders outside categories.
- Click
OK.
- Import the .mfdeploy File
-
The new
deploy folder must contain the
.mfdeploy configuration file. You import the file from the
COBOL Explorer.
- From the
COBOL Explorer, right-click the project folder; then select
Import > Import from the context menu.
- Expand
General; then click double-click
File System.
- Click the
Browse button that corresponds to the
From directory field, and navigate to
InstallFolder\deploy
where
InstallFolder is your
Visual COBOL installation folder. By default, this is
%ProgramFiles(x86)%\Micro Focus\Visual COBOL.
- Click
Select Folder.
- Check
.mfdeploy in the right pane.
- In the
Into folder field, append
\deploy to the existing value so that it points to the
deploy subdirectory.
- Click
Finish to import the file into the project.
- Define the Deployment Folder
- Now you need to configure the ESSOAP
enterprise server instance by defining the new
deploy project folder as the deployment folder.
- On the
Enterprise Server Administration Home page in the
Communications Processes column for your
enterprise server instance, click the
Details button that corresponds to
Listeners.
- In the row for the
Web listener name, click
Edit.
- Scroll down to the
Configuration Information field; then within the field, scroll down until you find the relevant code, then change:
uploads=<ES>/deploy
to:
uploads=ProjectFolder/deploy
where
ProjectFolder is the full path to your project folder, using forward slashes to separate subfolders. For example:
uploads=c:/Users/Bob/workspace/project-name/deploy
- Click
OK.
- Click
Home to return to the Home page.