Request Transformation

Click Add Condition and provide the following information and click the Add button.

• Variable. Specifies the variable type with a syntax.
• Operator. Specifies the operator to use to relate variable and the value provided. You can select one of the following:
  • Equals
  • Equals ignore case
  • Not equals
  • Not equals ignore case
  • Contains
  • Not Contains
  • Exists
  • Not Exists
  • Range
  • Greater Than
  • Less Than
• Value. Specifies a plain value or value with a syntax.

For details about the variables available in webMethods API Gateway, see Variable Framework .

and

Header Transformation for SOAP API

You can add or modify header, query or path transformation parameters by providing the following information:

• Variable. Specifies the variable type with a syntax.
• Value. Specifies a plain value or value with a syntax.

You can add multiple variables and corresponding values by clicking the Add button.

You can remove any header, query, or path transformation parameters by typing the plain value or value with a syntax.

For details about the variables available in webMethods API Gateway, see Variable Framework .

Select any of the following HTTP Methods.

• GET
• POST
• PUT
• DELETE
• HEAD
• CUSTOM

Provide the following information:

• Payload Type. Specifies the content-type of payload, to which you want to transform. The Payload field renders the respective payload editor based on the selected content-type.
• Payload. Specifies the payload transformation that needs to be applied for the incoming requests

  As this property supports variable framework, you can make use of the available variables to transform the request messages.

  For example, consider the native API accepting two integer values value1 and value2, and you want to pass these two values from webMethods API Gateway to the native API, you can configure the payload field as follows.

  {"value1" : 12,"value2" : 34}

  You can also configure the payload field using one or more variables by using variable framework. Let us see another syntax. For example, for the same native API seen in the previous example, if your client sends both the values through headers val1 and val2, and you want to add it to payload for the native API to recognize the input, you can do so by configuring the payload field as follows.

  {"value1" :${request.headers.val1},"value2" :${request.headers.val2}}. For details about the variables available in webMethods API Gateway, see Variable Framework.
  Note: If your payload content-type is different from the incoming payload's content-type, you need to transform the content-type of the header by using Header Transformation.
• Click + Add xslt document to add an xslt document and provide the following information:
  • XSLT file. Specifies the XSLT file used to transform the request messages as required.

    Click Browse to browse and select a file.

  • Feature Name. Specifies the name of the XSLT feature.
  • Feature value. Specifies the value of the XSLT feature.

    You can add more XSLT features and xslt documents by clicking the Add button.

    Note: webMethods API Gateway supports XSLT 1.0 and XSLT 2.0.
• Click + Add xslt transformation alias and provide the following information:
  • XSLT Transformation alias. Specifies the XSLT transformation alias

    When the incoming request is in JSON, you can use a XSLT file similar to the below sample:

    
    <?xml version="1.0" ?>
    <xsl:stylesheet version="1.1"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="xml"/>
     <xsl:template match="/" >
     <xsl:element name="fakeroot">
     <xsl:element name="fakenode">
     <!-- Apply your transformation rules based on the request from the Client-->
     </xsl:element>
     </xsl:element>
     </xsl:template>
    </xsl:stylesheet>
    

    When the incoming request is in XML, you can use a XSLT file similar to the below sample:

    
    <?xml version="1.0" ?>
    <xsl:stylesheet version="1.1"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
    <xsl:output method="xml"/>
    <xsl:template match="/"> 
    <xsl:element name="soapenv:Envelope">
    <xsl:element name="soapenv:Body">
    <!-- Apply your transformation rules based on the request from the Client-->
    </xsl:element>
     </xsl:element>
    </xsl:template>
    </xsl:stylesheet>
    

For example, the namespaces configured in this section can be used when you provide the syntax for XPath ${request.payload.path}.

For example: ${request.payload.xpath[//ns:emp/ns:empName]}

Provide the following information:

• Namespace Prefix. The namespace prefix of the payload expression to be validated.

  For example, specify the namespace prefix as SOAP_ENV.

• Namespace URI. The namespace URI of the payload expression to be validated.

  For example, specify the namespace URI as http://schemas.xmlsoap.org/soap/envelope/. This declaration defines SOAP_ENV as an alias for the namespace: http://schemas.xmlsoap.org/soap/envelope/.

  Note: You can add multiple namespace prefix and URI by clicking the Add button.