Set Up the ESACCTSV Enterprise Server Region

Provides step-by-step instructions to complete the creation and configuration of the ESACCTSV enterprise server region on which to run the ACCT Web-enabled application.

Create the ESACCTSV enterprise server region

  1. In Visual Studio, activate the Server Explorer.
  2. Expand Micro Focus Servers.
  3. Right-click localhost; then select New Enterprise Server.
  4. In the Name field, type ESACCTSV. This is the name for the new enterprise server region.
  5. Click the browse button that corresponds to the Template field.
  6. Double-click CICSTemplate.xml. This populates the Template field.
    Note: If CICSTemplate.xml is not on the list, browse to the Common7\IDE\Extensions\Micro Focus\Enterprise Developer\1.0\Etc\ServerTemplates subdirectory of your Visual Studio installation to locate the file.
  7. On the list next to Associate with projects, check ACCTWEB.
  8. Click OK.

    After refreshing, the Server Explorer shows the ESACCTSV enterprise server region listed under localhost.

Configure the ESACCTSV enterprise server region

Start Enterprise Server Common Web Administration (ESCWA)
  • From the Server Explorer, right-click Micro Focus Servers; then select Administration. This starts the ESCWA UI in a browser outside of the IDE.
  • Click NATIVE. In the navigation pane, expand Directory Server > Default to see the ESACCTSV enterprise server region in the list of servers.
Define environment variables
  1. Hover the row for the ESACCTSV entry in the list of servers, and click its Edit (EDIT) button.

    This action opens the GENERAL PROPERTIES page of the server's properties.

  2. Click GENERAL in the taskbar at the top of the properties pane to open the GENERAL PROPERTIES page.
  3. Type the following into the Configuration Information field:

    This indicates that the information that follows defines environment variables that are specific to the region. Next, you define an environment variable to represent your project directory.

  4. On the next line down, type:

    To use a defined environment variable in the value definition of another environment variable or as the value in other Enterprise Server Administration fields, you precede the name of the variable with a dollar sign ($). You can use the IDE_PROJECT_LOC environment variable to help define the next variable.

  5. On the next line down, type:

    This variable is used in the template definition for the DOCUMENT created in this tutorial: ACCTMP1, defined in the DFHWEB resource group.

    Note: When you create your enterprise server region using the CICS template as you have done in this tutorial, Enterprise Server generates and stores several environment variables based on the information in the associated project. For example, in this region, the IDE_LOADLIB environment variable has been generated and is set to the directory you defined as the output directory in the ACCTWEB Enterprise Developer project. Therefore, IDE_LOADLIB is equal to the loadlib subdirectory of your project directory, or c:\tutorials\CICS\ACCTWEB\loadlib. The definitions for generated environment variables do not show in the Configuration Information field, however.
  6. Click APPLY.
Set the location of your resource definition file
Earlier in this tutorial, you imported the resource definition file, dfhdrdat, as you imported the demonstration application. Now you need to tell the ESACCTSV region where to find that file.
  1. Click CICS in the taskbar at the top of the properties pane to access the CICS CONFIGURATION settings.
  2. In the Resource Definition File Path field, type:
  3. Click APPLY.
Set the TN3270 listener port
In this tutorial, you use the Rumba+ Desktop TN3270 emulator to access the CICS application. To enable communication with your enterprise server region, you need to set a port number where Enterprise Server listens for TN3270 messages.
  1. Click the downwards arrow next to GENERAL in the taskbar at the top of the properties pane, and click Listeners in the drop-down list.
  2. Click the TN3270 listener on the Communication Processes page.
  3. In the properties for the listener field, specify 5239 in the Port field.
  4. Click APPLY.
  5. Return to the list of Directory Servers.