Configure the ESDEMO Enterprise Server Instance

Walks you through the process of configuring the provided ESDEMO enterprise server instance by adding a deployment directory and configuring ESDEMO to use it.

To successfully deploy and run or debug a Java service interface, you must have an enterprise server instance started in Enterprise Server. For these tutorials, we provide the ESDEMO enterprise server instance.

Start the Server Explorer

The Server Explorer view is visible by default when using the COBOL perspective, and appears as a tab on the same level as the COBOL Explorer view. However, if it is not visible:

In Eclipse, click Window > Show View > Other > Micro Focus > Server Explorer, and then click Open.

Start Enterprise Server Common Web Administration (ESCWA)

From the Eclipse Server Explorer, expand Local [localhost:10086].
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 the Web listener in ESCWA

You need to enable the Web listener in ESDEMO to start automatically when you start the enterprise server instance.

In ESCWA, click NATIVE.
In the navigation pane, expand Directory Servers > Default, and then select the ESDEMO enterprise server instance.
On the GENERAL drop-down list, select Listeners.
Expand Communications Process 1, and click Web.
Change the Requested Status field to Stopped.
Click APPLY.

Important: The default deployment directory used by Enterprise Server is a subdirectory, deploy, within your Visual COBOL installation directory structure. If you have Administrator privileges to this subdirectory, or if you started Eclipse 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 directory.

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.

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.
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.

From the COBOL Explorer, right-click the new deploy 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 browse to the /opt/microfocus/VisualCOBOL/deploy folder.
Note: 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 .
Click Open.
Check .mfdeploy in the right pane.
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.

In ESCWA click NATIVE.
In the ESCWA navigation pane, expand Directory Servers > Default, and then select your enterprise server instance.
On the GENERAL drop-down list, select Listeners.
Expand Communications Process 1, and click Web.
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:
```
uploads=/home/hub/workspace/project-name/deploy
```
where project-name is the name of the project.
Click APPLY.