Management of Gateway Endpoints


The window in which the endpoints of the gateway are managed is opened when the gateway name on the gateway box on the Gateway Format screen is clicked.

  • The tick next to the gate endpoints indicates that the endpoint is active, the cross symbol indicates that the endpoint is inactive, by clicking on these buttons, the gateway endpoint is active / passive.

Figure: Gateway Service Information

Protocol Transformation

The protocol transform is performed if the REST gate has been created from the SOAP API.

Figure: Protocol Transformation Definition

  • Click the Protocol Transformation button for the relevant gateway.

  • The values of the fields in the Protocol Conversion window are entered. Descriptions of these fields are given below.

    • API Method: API method information to be called.
    • HTTP Method: HTTP method information of API method.
    • Resource Path: Endpoint’s value.
    • Header: Header creation and edition processes are executed here.
    • Message Handling: Select the corresponding option to convert incoming messages to the REST source.
      • Apply Transformation to option is activated when JSONML Transformation option selected.
        • Apply Transformation to input field specifies which part of the XML message is to be applied.
        • Clicking on the Show Sample Message button will display a sample message conversion format.
      • If the Create Message option is selected, values are entered in the active fields.
        • The variables in the source path can be defined in the body variables of the messages sent to the REST source in the ‘Body Variable’ field or ‘Path Variables’ to be used in the template section.
        • The message will be sent to the SOAP API in the Template field. The template should be updated according to the variables. Apinizer converts REST messages according to this template..
  • Click Save button to save the operation.

The Gateway Server must re-deploy after the Gateway Endpoints edited.