ProxyGen creates an OpenEdge service instance for you. The following procedure describes how to define an instance of the OpenEdge service type outside of ProxyGen.
1. If necessary, start the SonicMQ Domain Manager container and then start the Sonic Management Console.
2. Select the Configure tab, then open the Services folder.
3. Click the appropriate OpenEdge Service type: OpenEdge Native Services for a Native Invocation service, or OpenEdge Web Services for a Web Service Invocation.
4. In the right pane, click New. The custom form for specifying service attributes goes into editable mode
The first six fields, in Service Maintenance, specify the properties common to all Sonic ESB services. Only the Service Name is required.
5. Enter a unique name in the Service Name field.
6. Optionally, you can specify an entry endpoint, an exit endpoint, a fault endpoint, and a rejected message endpoint for the service. Service endpoints function as logical connections between services and are used as routing mechanisms. An endpoint can be a SonicMQ queue or topic, a service, or a process. See Sonic ESB Developer's Guide for more information about endpoints.
You can specify an existing endpoint or create a new one for use as any of the four endpoint values. Click the ellipsis (...) button to the right of an endpoint field (for example, Entry Endpoint) to display the Select Entry Endpoint window, as shown:
Do one of the following:
Select an existing endpoint from the list.
Click New. Select Endpoint, Service, or Process; then select the desired option from the submenu to display the Configure Endpoint window. Enter the appropriate values and click OK to return to the Select Endpoint window.
At the Select Entry Endpoint window, click OK.
7. Repeat Step 6 to specify the remaining endpoints.
8. Optionally specify a WSDL file to be associated with the OpenEdge service. This is typically the WSDL file generated by means of the OpenEdge resource editor. For more information on generating a WSDL file, see Generating a WSDL file from the OpenEdge Resource Editor.
To specify a WSDL file, it must already be stored in the sonicfs directory. Click the ellipsis (...) button. The Choose WSDL File Resource window appears:
Browse to select the WSDL file. Choose Open. The WSDL is now associated with your service.
9. The remaining fields, in Init Parameters, are specific to the type of OpenEdge service you are creating:
a. For an OpenEdge Native service, the following parameters are mandatory:
AppServer Operating Mode — Specifies the state of the AppServer
AppServer URL — Specifies the URL of the AppServer called to execute the ABL code for the service
Optionally, you can modify the runtime properties, as shown:
b. For an OpenEdgeWeb Service, only the OpenEdge Service Definition File field requires that you supply a value. You must specify a valid WSM or WSD file. Click the ellipsis (...) button to the right of this field, and browse to the file.
The value in the SOAP Fault Processing field determines the action taken when the AppServer returns a SOAP fault message. SOAP faults result from conditions such as the server not running or a message being improperly formatted. They also result form using a RETURN ERROR string in your service. You can ensure that you do not get a SOAP fault from an application error by defining another way to return errors from the service (for example, by using an output parameter).
Choose one of the following three values from the drop-down menu that appears when you click the down arrow at the right of the field:
None — No fault processing occurs. As is always the case with any response from the AppServer, the SOAP fault message is simply sent to the service's exit endpoint, if any, or to the next step specified in the process itinerary.
Message — The message that was being processed when the SOAP fault was generated is sent to the service's fault endpoint or to the fault endpoint specified in the process definition. The message can be processed after the fault is corrected.
Fault — The SOAP fault message is sent to the service's fault endpoint or to the fault endpoint specified in the process definition (perhaps triggering an alert to a person who can take the appropriate corrective action). The message that was being processed when the SOAP fault was generated is lost.
If the SOAP Fault Processing field is set to Message or Fault, the service definition or the process definition must specify a fault endpoint. Otherwise, a SOAP fault causes an exception.
Enter values in the remaining fields only if you want to override the default values in the WSM or WSD file specified in the OpenEdge Service Definition File field. If values are entered for them, these properties override the defaults as follows:
AppServer Protocol — Overrides the appServiceProtocol default property
AppServer Host — Overrides the appServiceHost default property
AppServer Port — Overrides the appServicePort default property
OpenEdge AppService Name — Overrides the appServiceName default property
Disable SSL Hostname Verification — Overrides the noHostVerify default property
Disable SSL Session reuse — Overrides the noSessionReuse default property
Select an existing endpoint from the list.
