Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > Consuming External Web Services Using Siebel Web Services >

SHA2 Support for Outbound Web Service

NOTE:  Non-Windows platforms use Mainwin library that does not support SHA2. In order to provide SHA2 support on non-Windows platforms, Siebel uses the OUTBOUNDSHA2 named subsystem that routes the outbound calls using a javacontainer. As Windows platforms support SHA2, they do not require OUTBOUNDSHA2.

Siebel supports SHA2 for outbound calls through the framework described here. This support for SHA2 is through the introduction of a Config Agent between the Siebel Server and the external Web Server. The Config Agent accepts local requests from mainwin within the Siebel server and transfers the same to the external Web Server in SHA2 as seen in Figure 28. To configure certificates for the Config Agent, see the chapter on communications and data encryption in the Siebel Security Guide.

Figure 28. Siebel outbound web service configuration for SHA2

The transfer is made possible by a servlet named outboundeai that resides on the Config Agent. This servlet copies the outbound request body and Siebel server header information and transfers it to the external Web Server. The servlet also collects the response from the Web Server and transfers it back to the Siebel server as seen in Figure 29.

Figure 29. Detailed Siebel outbound web service configuration for SHA2

Configuring Siebel Server and Config Agent for SHA2 Outbound

The SHA2 support for HTTP outbound is achieved via configuring a named subsystem of type JavaContainerSubSys. The name of this named subsystem is then set to the value of the EAIOutboundSubSys component parameter as described in the following procedure.

To configure the named subsystem for SHA2 support in outbound

1. Go to the Siebel Server Manager and search on OUTBOUNDSHA2 as follows:

   list param for named subsystem OUTBOUNDSHA2

   where:

   OUTBOUNDSHA2 is the name of the new named subsytem

2. Set the name of this named subsystem as value of the EAIOutboundSubSys component parameter:

   change param EAIOutboundSubSys=OUTBOUNDSHA2 for comp SCCObjMgr_enu

   where:

   SCCObjMgr_enu is the Siebel Object Manager component

3. When the user makes an outbound call, the EAI Outbound Dispatcher checks for the value of the component parameter.
   1. If the value is present, the dispatcher will make a http call to the servlet hosted in the Config Agent specified in CONTAINERURL and the Config Agent will make the https call to the external Web Server.
   2. If the value is not present for the component parameter or the named subsystem parameter, the dispatcher makes a direct https call to the external Web Server.
4. Restart component.

   stop comp sccobjmgr_enu

   start comp sccobjmgr_enu

Parameters for the named subsystem

The named subsystem has three parameters as seen in Table 10.

NOTE:  Only CONTAINERURL should be used for this configuration.