Create and Configure ESSOAP

Walks you through the process of creating and configuring an enterprise server instance, ESSOAP, to use in this tutorial.
Restriction: This topic applies to Windows environments (local development) only.

To successfully deploy and run (debug) a Web Services service interface, you must have an enterprise server instance started in Enterprise Server. For these tutorials, you create and configure the ESSOAP enterprise server instance.

Create ESSOAP

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

  1. If the Server Explorer is not loaded, click Window > Show View > Other > Micro Focus > Server Explorer; then click OK.
  2. On the Server Explorer, right-click Local [localhost:86]; then select New > Enterprise Server.
  3. In the Name field, type ESSOAP.
  4. Click the Browse button associated with the Template field.

    The default location for Enterprise Server templates is %ProgramFiles(x86)%\Micro Focus\Enterprise Developer\etc\ServerTemplates.

  5. If the Template field does not show the path and ESTemplate.xml file, browse to the default location for Enterprise Server templates and double-click ESTemplate.xml to select it.
  6. Click Finish.

Start Enterprise Server Administration

  1. From the Server Explorer, right-click Local [localhost:86]; then click Open Administration Page.

    The Enterprise Server Administration Home page starts in an Enterprise Developer window.

Configure a Listener Port

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

  1. On the Enterprise Server Administration Home page, in the Communications Processes column for the ESSOAP server, click the Details button.

    This takes you to the Communications Processes page for Enterprise Server listeners.

  2. Click the Edit button that corresponds to Web Services and J2EE Listener.
  3. Change the contents of the Endpoint Address field to *:9003.
  4. Click Apply.

    This returns you to the Communications Processes page.

  5. Click Home to return to the Home page.
    Important: If you do not have Administrator privileges to the Enterprise Developer installation directory, continue with the configuration. Otherwise, configuration for the ESSOAP enterprise server instance is complete at this point.

Configure a Deployment Directory

Note: The default deployment directory used by Enterprise Server is a subfolder to your Enterprise Developer installation directory. If you have Administrator privileges to the Enterprise Developer installation directory structure, or if you started Enterprise Developer 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 the deploy folder
Without Administrator privileges, you cannot deploy to Enterprise Server from the default Enterprise Developer deployment directory. To ensure successful deployment, create a deploy folder in your ProgramSOAP project.
  1. In the Team Developer Tree View, right-click the project; then select New > Folder > Folder from the context menu.
  2. In the Folder name field, type deploy; click Finish.
Import the .mfdeploy File
The new deploy folder must contain the .mfdeploy configuration file. You import the file from the Team Developer Tree View.
  1. From the Team Developer Tree View, right-click the deploy folder; then select Import from the context menu.
  2. Expand General; then click double-click FileSystem.
  3. Click the Browse button that corresponds to the From directory field, and navigate to
    InstallDir\deploy

    where InstallDir is your Enterprise Developer installation directory. By default, this is %ProgramFiles(x86)%\Micro Focus\Enterprise Developer.

  4. Click OK.
  5. Check .mfdeploy in the right pane.
  6. Click Finish to import the file into the project.
Define the Deployment Directory
Now you need to configure the ESSOAP enterprise server instance by defining the new deploy project folder as the deployment directory.
  1. On the Enterprise Server Administration Home page in the Communications Processes column for your enterprise server instance, click the Details button that corresponds to Listeners.
  2. Click the Listeners tab.
  3. In the row for the Web listener name, click Edit.
  4. Scroll down to the Configuration Information field; then within the field, scroll down until you find the relevant code, then change:
    uploads=<ES>/deploy

    to:

    uploads=ProjectDir/deploy
    where ProjectDir is the full path to your project directory, using forward slashes to separate subdirectories. For example:
    uploads=c:/Users/Bob/workspace/project-name/deploy
  5. Click OK.
  6. Click Home to return to the Home page.