Set Up the ESRSTAPI Enterprise Server Instance

Walks you through the process of creating and configuring an enterprise server instance, ESRSTAPI, to use in this tutorial.
Restriction: This topic applies only when the Enterprise Server feature is enabled.

To successfully deploy and run, an IMTK Web service, you must have an enterprise server instance configured and started in Enterprise Server. For this tutorial, you create the ESRSTAPI enterprise server instance, configure its listeners, and optionally configure a deployment folder for it to use.

Start the Server Explorer

The Server Explorer expandable ribbon is visible in Visual Studio on the top left side of the IDE by default when using Visual COBOL. However, if it is not visible:

  • In Visual Studio, click View > Server Explorer.

Start Enterprise Server Common Web Administration (ESCWA)

  • On the Server Explorer, right-click Micro Focus Servers, and then click Administration.

    ESCWA starts in your default browser.


In this section, you create the ESRSTAPI enterprise server instance from the ESCWA Administration page.

  1. In ESCWA, click NATIVE.
  2. In the navigation pane, expand Directory Servers, and then click Default.
  3. In the right pane, click New.
  4. In the Name field, type ESRSTAPI.
  5. Uncheck MSS Enabled.
  6. Click Save.

Configure ESRSTAPI

By default, your new enterprise server instance is already configured for REST Web services; however, you must make some adjustments, which include enabling dynamic debugging, setting an endpoint address for the Web Services and J2EE listener, and if you do not have Administrator privileges to the Visual COBOL installation folder, defining a deployment folder.

Enable Dynamic Debugging
  1. On REGION AND SERVER LIST page, hover over the ESRSTAPI entry, and then click the Edit Edit icon icon that appears to the right of the Security column.
  2. Under STARTUP OPTIONS, check Allow Dynamic Debugging.
  3. Click APPLY.
Configure Listeners
  1. In the navigation pane, be sure that ESRSTAPI is selected.
  2. On the GENERAL drop-down list, select Listeners.
  3. Expand Communications Process 1, and click Web Services and J2EE.
  4. In the Port field, type 9003.
  5. Click APPLY.
  6. Click the Web communication process.
  7. Change the value of the Requested Status field to Stopped.
  8. 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 Visual Studio using Run as Administrator, you are not required to complete the following tasks. Otherwise, you must complete them 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.
  1. In the Solution Explorer, right-click the project, and then select Add > New Folder from the context menu.
  2. Type deploy; then press Enter.
Import the .mfdeploy file
The new deploy folder must contain the .mfdeploy configuration file. You import the file from the Solution Explorer.
  1. From the Solution Explorer, right-click the deploy folder; then select Add > Existing Item.
  2. Browse to the %ProgramFiles(x86)%\Micro Focus\Visual COBOL\deploy folder.
  3. Set the filter drop-down list to All Files (*.*).
  4. Double-click the .mfdeploy file.
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:



    where project-name is the name of the project.

  6. Click APPLY.