Create and Configure the CICSCA Enterprise Server Region

Provides instructions for creating and configuring the CICSCA enterprise server region on which to run the COMMWS Web service created later in this tutorial.

Create the CICSCA enterprise server region

  1. In Visual Studio, open the Server Explorer.
    Note: If it is hidden, select View > Server Explorer from the Visual Studio main menu.
    Attention: You might encounter an Enterprise Server Sign On dialog box as you perform the steps required to create, configure, start, or stop an enterprise server instance from the Server Explorer. If you do, ensure that the Server requires credentials, Use specific server credentials, or Server is secured box is unchecked, and then click OK. Also, if prompted to disable password recovery, click No.
  2. Expand Micro Focus Servers.
  3. Right-click localhost, and then select New Enterprise Server from the context menu.
  4. In the Name field, type CICSCA.
  5. Click the browse button Browse button associated with the Template field.

    By default, this opens to the location of the Enterprise Server template files, which is %ProgramFiles(x86)%\Micro Focus\Enterprise Developer\etc\ServerTemplates.

  6. Double-click CICSTemplate.xml.
  7. On the Associate with projects list, check CICSCommareaWS.
  8. Click OK.

    The Output window displays a notification that the server has been created.

  9. In the Server Explorer, expand localhost to be sure that the CICSCA region has been added.

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.

Configure listener ports in ESCWA

When you create a service interface in Enterprise Developer, 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 Requested Status to Stopped.
  7. Set the Conversation Type to Web.
  8. Click Apply.
  9. Under Communications Process 1, click Web.
  10. Change the Requested Status field to Stopped.
  11. Click Apply.
Important: The default deployment directory used by Enterprise Server is a subdirectory, deploy, within your Enterprise Developer 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 Enterprise Developer 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, and 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. 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\Enterprise Developer\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 ensure that your enterprise server instance is selected in the navigation pane, and the Communications Processes page is open in the right pane.
  2. Under Communications Process 1, select Web.
  3. In the Listener Properties pane, scroll down to the Custom Configuration field.
  4. Within the Custom Configuration field, scroll down until you find the relevant code, then change:
    uploads=<ES>/deploy

    to:

    uploads=c:/tutorials/IMTK/project-name/deploy

    where project-name is the name of the project.

  5. Click Apply.