HTTP Client Begin Session Service

Implementing the HTTP Client Begin Session Service

Configuring the HTTP Client Begin Session Service

You can set the following values in the trading partner profile and specify it in the ProfileId field, or you can set these values in an instance of the service to only apply for that instance. If specified in the HTTP Client Begin Session service, the following values override those in the HTTP trading partner profile:

• CACertificateId
• CipherStrength
• ConnectionRetries
• RemoteHost
• RemotePasswd
• RemotePort
• RemoteUserId
• SSL
• SystemCertificateId
• RetryDelay

To configure the HTTP Client Begin Session service, you must specify settings for the following fields in the GPM:

Output from Service to Business Process

The following table contains the parameters passed from the HTTP Client Begin Session service to the business process:

Output from Business Process to Service

The following table contains the parameters passed from the business process to the HTTP Client Begin Session service:

Business Process Example

The following example business process illustrates by using the HTTP Client Begin Session service:

<process name="HTTPExample">
  <sequence> 
<operation name="Obscure Password">
      <!-- insert obscured password into process data -->
      <participant name="HTTPClientObscureParameter"/>
      <output message="outmsg">
        <assign to="." from="*"></assign>
      </output>
      <input message="inmsg">
        <assign to="HTTPClientObscureResults" from="*"></assign>
      </input>
    </operation> 
<operation name="HTTP Client Begin Session Service">
      <participant name="HTTPClientBeginSession"/>
      <output message="HTTPClientBeginSessionServiceTypeInputMessage">
        <assign to="HTTPClientAdapter">HTTPClientAdapter</assign>
        <assign to="RemoteHost">hostb</assign>
        <assign to="RemotePort">26633</assign>
	<assign to="RemoteUserId">admin</assign>
	<!-- copy obscured password from process data to service -->
	<assign to="RemotePasswd" from="admin/text()"></assign>
	<assign to="SSL">Must</assign>
        <assign to="CipherStrength">Strong</assign>
        <assign to="CACertificateId">B2BHttp-Id</assign>
        <assign to="SystemCertificateId">httptestclientcert1-Id</assign> -->
        <assign to="." from="*"></assign>
      </output>
      <input message="inmsg">
        <assign to="HTTPClientBeginSessionServiceResults" from="*"></assign>
      </input>
    </operation>

The following example shows how to use of the revealObscured function when the user ID contains domain or special characters. First, create a name in the Obscure Service without any special characters and assign the appropriate password to it. In the following example, the name created in the Obscure Service is "htan" while the userid is sgp-htan\htan.

The parameter to the revealObscured() function is the node containing the obscured password. The function uses the node name as the key and the node value as the obscured password when unobscuring.

<operation name="Obscure HTTP client password">
      <participant name="HTTPClientObscureParameter"/>
      <output message="outmsg">
	<assign to="." from="*"/>
      </output>
      <input message="inmsg">
	<assign to="ObscureResult" from="*"/>
      </input> 
</operation> 
<operation name=" HTTP Client Begin Session Service ">
     <participant name="HTTPClientBeginSession"/>
     <output message="BeginSessionRequest">
           ............
       <assign to="RemoteUserId">sgp-htan\htan</assign>
       <assign to="UsingRevealedPasswd">true</assign>   
       <assign to="RemotePasswd" from="revealObscured(ObscureResult/htan)"/> 
       ..........
      </output>
      <input message="inmsg">
         <assign to=" HTTPClientBeginSessionServiceResults " from="*"/>
      </input> 
</operation>