Section | Field | Description |
Mashup step name | Provide a name for the mashup step that is unique within the mashup. | |
API Endpoint | The API endpoint that you want to invoke in the mashup step. The API must be published on the current API Gateway instance. | |
API Gateway API | The endpoint of the API that you want to use. You can type a few letters and select from the autocomplete list. | |
Resource | The resource in the API that you want to use. You can type a few letters and select a resource from the autocomplete list. | |
Method | The specific method of the resource that you want to invoke. | |
Execute outbound authentication policy | Select if you want the outbound security policies of the participating API to be enforced in the context of an API mashup. | |
Headers | ||
Use incoming Headers | Select to use the headers in the incoming request. | |
Custom Headers | Custom headers that you can add in addition or instead of the incoming headers. Each custom header must have the following fields: Header Name Header Value | |
Query Parameters | Provide the following values: Query Parameter Name Query Parameter Value | |
Path Parameters | Provide the following values: Path Parameter Name Path Parameter Value | |
Payload | Type the Payload. | |
XSLT Document | Click Add xslt document and select the XSLT file for transforming the payload. Provide the following values: XSLT File Feature Name Feature value For information about transforming the payload using XSLT, see
Request Transformation. | |
XSLT Transformation alias | Click Add xslt transformation alias and select an existing XSLT transformation alias. | |
Advanced Transformation | ||
webMethods IS service | Click Add webMethods IS service and provide the following values: webMethods IS Service Run As User Select Comply to IS Spec For information about these fields and using the webMethods IS Service, see
Invoke webMethods IS. | |
webMethods IS Service Alias | For information about the webMethods IS Service Alias, see
Invoke webMethods IS. | |
Transformation Metadata | ||
Namespace | Provide the following values: Namespace Prefix Namespace URI For information about transformation metadata, see
Request Transformation. | |
Custom Pipeline Variables | You can use custom pipeline variables to hold values that need to be used in another step of the API mashup. Provide the following values: Name Value For more information, see
Structure of an API Mashup. |
Section | Field | Description |
Headers | ||
Use incoming Headers | Select to use the headers in the incoming request. | |
Custom Headers | Custom headers that you can add in addition or instead of the incoming headers. Each custom header must have the following fields: Header Name Header Value | |
Query Parameters | Provide the following values: Query Parameter Name Query Parameter Value | |
Path Parameters | Provide the following values: Path Parameter Name Path Parameter Value | |
Payload | Type the Payload. | |
XSLT Document | Click Add xslt document and select the XSLT file for transforming the payload. Provide the following values: XSLT File Feature Name Feature value | |
XSLT Transformation alias | Click Add xslt transformation alias and select an existing XSLT transformation alias. | |
Advanced Transformation | ||
webMethods IS Service | Click Add webMethods IS service and provide the following values: webMethods IS Service Select a Run As User Select Comply to IS Spec For information about these fields and using the webMethods IS Service, see
Invoke webMethods IS. | |
webMethods IS Service Alias | Select an existing webMethods IS service alias. | |
Transformation Metadata | ||
Namespace | Provide the following values: Namespace Prefix Namespace URI | |
Custom Pipeline Variables | You can use custom pipeline variables to hold values that need to be used in another step of the API mashup. Provide the following values: Name Value For more information, see
Structure of an API Mashup. | |
Mashup Response Transformation | Select Aggregate response Payload |