Set Up the ESSOAP Enterprise Server Instance

Start the Server Explorer

Create ESSOAP

In this section, you create the ESSOAP enterprise server instance from the Server Explorer in Visual COBOL.

1. On the Server Explorer, expand Local [localhost:10086]; then right-click Default [127:0.0.1:86] and select New > Enterprise Server .
2. In the Name field, type ESSOAP.
3. 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 (Windows) or .

4. Click ESTemplate.xml to select it, and the Open.
   Note: If the Template field does not show the path and ESTemplate.xml file, browse to the Enterprise Server template location cited above to find and select the file.
5. Click Finish.

Start Enterprise Server Common Web Administration (ESCWA)

1. From the Eclipse Server Explorer, expand Local [localhost:10086].
2. Right-click Default [127.0.0.1:86] and then click Open Administration Page.

   The Region and Server List page in ESCWA is displayed in your default browser.

Configure listener ports in ESCWA

When you create a service interface in Visual COBOL, 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.

In addition, you need to enable the Web listener to start automatically with the enterprise server instance.

1. In ESCWA, click NATIVE.
2. In the navigation pane, expand Directory Servers > Default, and select your enterprise server instance.
3. On the GENERAL drop-down list, select Listeners.
4. Expand Communications Process 1, and click Web Services and J2EE.
5. In the Port field, type 9003.
6. Scroll down to the Status section, and set the status to Stopped.
7. Click APPLY.
8. Under Communications Process 1, click Web.
9. Change the Requested Status field to Stopped.
10. Click APPLY.

Create and configure a deployment directory

Create the deploy directory

Without Administrator privileges, you cannot deploy to Enterprise Server from the default Visual COBOL deployment folder. To ensure successful deployment, create a deploy subdirectory in your project.

1. In the COBOL Explorer, right-click the project, and then select New > Folder from the context menu.
   Note: If Folder is not an option on the context menu, click Other, and create a new deploy folder from there.
2. In the Folder name field, type deploy, and then click Finish.
   Note: To ensure that you can see the deploy folder in COBOL Explorer:

   1. Click View Menu > Filters and Customization .

      This opens the Filters and Customization dialog box.

   2. Uncheck .* resources and Empty folders outside categories.
   3. Click OK.

Import the .mfdeploy file

The new deploy folder must contain the .mfdeploy configuration file. You import the file from the COBOL Explorer.

1. From the COBOL Explorer, right-click the new deploy folder; then select Import > Import from the context menu.
2. Expand General; then click double-click File System.
3. Click the Browse button that corresponds to the From directory field, and browse to the %ProgramFiles(x86)%\Micro Focus\Visual COBOL \deploy (Windows) or /opt/microfocus/VisualCOBOL/deploy (UNIX) folder.
   Note: On UNIX platforms: If the .mfdeploy file is not listed on the Import from directory dialog box, right-click in the dialog box, and check Show Hidden Files to view .mfdeploy on the list .
4. Click Open.
5. Check .mfdeploy in the right pane.
6. Click Finish to import the file into the project.

Define the deployment directory in ESCWA

Now you need to configure your enterprise server instance by defining the new deploy project folder as the deployment folder.

1. In ESCWA click NATIVE.
2. In the ESCWA navigation pane, expand Directory Servers > Default, and then select your enterprise server instance.
3. On the GENERAL drop-down list, select Listeners.
4. Expand Communications Process 1, and click Web.
5. In the LISTENER PROPERTIES pane, scroll down to the Custom Configuration field; then within the field, scroll down until you find the relevant code, then change:

   uploads=<ES>/deploy

   to:

   uploads=project-folder/deploy

   where project-folder is the full path to your project folder, using forward slashes to separate subfolders. For example:

   Windows: uploads=c:/Users/Bob/workspace/project-name/deploy

   UNIX: uploads=/home/hub/workspace/project-name/deploy

   where project-name is the name of the project.

6. Click APPLY.