Hybrid Integration 10.1 | Integrating On-Premises Applications | Integration Server Built-In Services | SOAP Folder | pub.soap.handler:getServicePipeline
 
pub.soap.handler:getServicePipeline
WmPublic. Gets the service pipeline from a given message context.
Input Parameters
messageContext
Object Message context from which to get the service pipeline.
A message context contains properties for the SOAP message and provides access to the SOAP message. Integration Server creates the message context and passes it to the header handler. All handlers invoked by a given instance of a SOAP request or SOAP response use the same message context, which enables you to use the message context to pass information among handlers.
Output Parameters
servicePipeline
Document Document (IData) containing the service pipeline.
The contents of servicePipeline depend on whether the pub.soap.handler:getServicePipeline service executes as part of a consumer handler chain or a provider handler chain and which type of handler service (request, response, or fault) executes the service.
For this consumer handler service...
servicePipeline contains...
Request handler service
Contents of the web service connector pipeline after any pipeline mapping or manipulation occurs during execution of the web service connector but just before Integration Server sends the SOAP request.
Response handler service
The pipeline that becomes the web service connector output pipeline. At this point, the pipeline does not contain data from SOAP response. Integration Server adds the data form the SOAP response after handler processing completes.
Fault handler service
The contents of the web service connector output pipeline. At this point, the pipeline does not contain data from the SOAP fault. Integration Server adds the data form the SOAP fault after handler processing completes.
For this provider handler service...
servicePipeline contains...
Request handler service
The pipeline passed as input to the endpoint service. At this point, the pipeline does not yet contain data from the SOAP request. Integration Server places data from the SOAP request in the pipeline after handler processing completes
Response handler service
The output pipeline of the endpoint service that corresponds to the invoked web service operation.
servicePipeline also contains data from the SOAP request if the endpoint service did not drop the data from the pipeline during service execution.
Fault handler service
The output pipeline of the endpoint service that corresponds to the invoked web service operation.
servicePipeline also contains data from the SOAP request if the endpoint service did not drop the data from the pipeline during service execution.
Usage Notes
Use this service to give handler services access to the contents of the pipeline. The handler service can then pass pipeline contents to another service. For example, during execution of a handler service for a provider web service descriptor, you can use the pub.soap.handler:getServicePipeline service to:
*Pass pipeline data from the request handler service to the endpoint service.
*Pass pipeline data from the endpoint service to the response handler service or fault handler service.
During execution of a handler service for a consumer web service descriptor, you can use the pub.soap.handler:getServicePipeline service to:
*Pass pipeline data from the web service connector input to the request handler service.
*Pass pipeline data from the response handler service or fault handler service to the web service connector output
Use the pub.soap.handler:getServicePipeline service to access the pipeline instead of using thepub.soap.handler:getProperty service to access the servicePipeline property.
Copyright © 2015- 2017 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.