Services Used By Web Services

The following table contains the names and descriptions of the services and adapters that are used to enable Web services for Sterling B2B Integrator. These services are internal and should not be changed or copied.

Service	Description
SOA Http Server Adapter	Configuration of the HTTP Server adapter specifically for Web services. As delivered, it is set up to use the default perimeter server (node1 & local) and HTTP.
SOA SSL Http Server Adapter	Configuration of the HTTP Server adapter specifically for Web services HTTPS transport. As delivered, it is set up to use the default perimeter server (node1 & local) and HTTP. Note: If you want to use an HTTPS certificate other than the default self-signed certificate, configure that change on the SSL configuration page of the adapter instance.
Dynamic Service Invoker Service	Invokes a service designated by the service parameter `SVC_NAME`. The primary business usage of this service is for Web service invocation. Business process writers can also use this to execute services dynamically in a business process by simply adding the Dynamic Service Invoker (DSI) service as an operation or participant and setting the `SVC_NAME` parameter.
Service Information Service	Provides information about a referenced service.
SOA Fault Service	Puts Sterling B2B Integrator-specific error information into standard Web services (SOAP) faults. The SOAP protocol requires specific fault handling mechanisms that allow Sterling B2B Integrator-specific details to be added to the fault message. This service allows detailed error information for Sterling B2B Integrator to be added to the appropriate SOAP fault message.
SOA Inbound	Processes inbound Web service request documents, separates the MIME parts, and validates signatures. Called by the system for a Web services consumer process for this application. Note: Configure and use the SOAInbound and SOAOutbound services if you want, as a consumer, to sign attachments or use signature processing based on XML signature. These features are not available with SOAInboundSecurityService and SOAOutboundSecurityService.
SOA Inbound Msg Processing Service	Processes incoming SOAP message. If the incoming SOAP message has MIME attachments, it extracts the attachment parts from the message and uploads the attachments in the process data. It also extracts the SOAP Envelope from the message and uploads it in the process data as a primary document.
SOAInboundSecurityService	Processes WS-Security headers (including timestamps, username token, signature verification, and decryption) in an incoming SOAP message. The input to this service is a SOAP document carrying WS-Security Header and the output is a valid/decrypted SOAP document. This service is compliant with WS-Security specification 1.0. Note: The ability to sign attachments or use signature processing is not available with SOAInboundSecurityService and SOAOutboundSecurityService. To obtain these features as a consumer, use the SOAInbound and SOAOutbound services.
SOA Outbound	Processes the output of the SOA Response Builder service and packages it in MIME format. This service sends an outbound (response) message from a Web service. Note: Configure and use the SOAInbound and SOAOutbound services if you want, as a consumer, to sign attachments or use signature processing based on XML signature. These features are not available with SOAInboundSecurityService and SOAOutboundSecurityService.
SOA Outbound Msg Processing Service	Constructs the final SOAP Response (MIME or without MIME) using the output of the end-point invocation. This service is the complement to the SOA Inbound Msg Processing Service.
SOAOutboundSecurityService	Creates a WS-Security Header that can carry security timestamps, username token, signature and encryption. The input to this service is a SOAP document without any WS-Security header and the output is a signed, encrypted SOAP document carrying a WS-Security header. This service with compliant with WS-Security specification 1.0. Note: The ability to sign attachments or use signature processing is not available with SOAInboundSecurityService and SOAOutboundSecurityService. To obtain these features as a consumer, use the SOAInbound and SOAOutbound services.
SOA Request Handler Service	Processes the output of the SOA Inbound service and prepares the workflow context for invocation. It checks that the request is valid according to the WSDL and that the user is authorized to execute the requested Web service.
SOA Response Builder Service	Processes the output of the invoked Web service and prepares the documents for the SOA Outbound service.
SOA WS Config Info Service	Based on the WSDL service name provided, this service provides information about the referenced service configuration.
HTTP Respond Service	This service is used as part of a business process to return a response to an HTTP request. Used in conjunction with an HTTP Server adapter.
RM Decision Service	Processes inbound Web Services request documents to determine whether the request carries a WS-RM header and is a WS-Reliable Message or not. Called by the system for Web service consumer processes.
RM Service Handler	Validates an incoming RM SOAP request message against WS-Reliability 1.1 specification, converts the incoming SOAP message in an internal Message object and then persists this internal Message object into the Workflow Context.
RM Service Manager	Processes, manages, and generates appropriate responses to a WS-Reliable message.