Using the HTTP Target Connector

The HTTP target connector enables you to exchange messages with non-PeopleSoft systems using the HTTP protocol. The HTTP target connector uses SSL for all basic security services, including client-side authentication.

The HTTP target connector also supports the Simple Object Access Protocol (SOAP) XML format.

The connector ID for the HTTP target connector is HTTPTARGET.

IBInfo Data Contained in HTTP Headers

A message has two parts—the transaction data and the IBInfo header that is the routing envelope used by PeopleSoft Integration Broker. In the event that a receiving system wants to make use of the IBInfo data, IBInfo header information is included when publishing messages to non-PeopleSoft systems when using the HTTP target connector or the JMS target connector.

When using the HTTP target connector to send messages to non-PeopleSoft systems, the following IBInfo data is contained in the HTTP headers. The content of the message (message body) is not impacted.

  • ExternalOperationName

  • OperationType

  • OrigTimeStamp

  • NonRepudiation

  • To

  • From

Gateway-Level Connector Properties

The HTTP target connector provides the option of routing through proxy servers. To enable this capability, you must set the domain name of the proxy server and the port number of the proxy server in the integrationGateway.properties file:

See Running Integration Gateways Behind Proxy Servers.

Node-Level Connector Properties

The HTTP target connector features properties that correspond to standard HTTP 1.1 header fields, as well as several custom properties that are documented in the following table. The World Wide Web Consortium (W3C) web site provides complete documentation for the standard header fields.

See World Wide Web Consortium

Property ID Property Name Description

HTTPPROPERTY

Disable_URLEncodingBody

Disable the gateway from encoding the body of data.

HTTPPROPERTY

Method

Specify the HTTP method used to send messages. The valid values are:

  • POST (the default).

  • GET.

HTTPPROPERTY

RemoveSOAP-Response

(Optional.) Remove the SOAP wrapping from response messages returned from a third party. The valid values are:

  • Y. (Default.) The SOAP formatting is removed from response messages.

  • N. The SOAP formatting is not removed from response messages.

HTTPPROPERTY

SOAPUpContent

(Optional.) Automatically wrap outbound transactions in SOAP 1.1 format. The valid values are:

  • Y. (Default.) Outbound messages are wrapped in SOAP 1.1 format.

  • N. Outbound message are not SOAP-wrapped.

To wrap outbound transactions in SOAP 1.2 format, use the SOAP 1.2 parameter described elsewhere in this table.

HTTPPROPERTY

SOAP 12

(Optional.) Use this property in conjunction with the SOAPUpContent parameter described elsewhere in this table.

When using the SOAPUpContent parameter to wrap outbound transactions in SOAP format, by default the system wraps the content in SOAP 1.1 format. To wrap the content in SOAP 1.2 format, use the SOAP 1.2 parameter in addition to the SOAPUpContent parameter. The valid values are:

  • Y. Outbound messages are wrapped in SOAP 1.2 format.

  • N. Outbound messages are wrapped in SOAP 1.1 format.

HTTPPROPERTY

Use-DomainName

(Optional.) Use domain name instead of IP address for all HTTP requests to the endpoint URL.

HTTPPROPERTY

Use-WSA10-Namespace

(Optional.) Override the WS-Addressing namespace URI used in outbound messages that have been SOAP wrapped via the connector property SOAPUpContent. The valid values are:

  • Y. (Default.) The namespace URI http://www.w3.org/2005/08/addressing is used.

  • N. The system default WS-Addressing namespace URI is used.

PRIMARYURL

URL

Specify the URL to which messages are sent using this connector.

BACKUPURL

URL

(Optional.) Specify the URL to which messages can be sent if the primary URL is inaccessible.

HEADER

SendUncompressed

Specify whether to send messages decompressed. Options are:

  • Y: Send messages decompressed and decoded. (Default.)

  • N: Send messages compressed and base64 encoded.

HEADER

Proxy-Authorization

Specify the user ID and password for proxy authentication.

See Running Integration Gateways Behind Proxy Servers.

HEADER

SOAPAction

(Optional.) Enable third-party systems (for example, Universal Description, Discovery, and Integration (UDDI) sites) to receive SOAP transactions over HTTP.

The default value is ”“ (a null string).

HEADER

TimeOut

Specify the time in milliseconds for the connector to wait for the message to transmit. If the timeout period expires without a successful transmission, the transaction fails.

The default value is 50000 (50 seconds).

Using the Content-Type Property

One of the optional gateway-level properties you can set for the HTTP target connector is Content-Type.

When the HTTP target connector property Content-Type is application/x-www-form-urlencoded, the connector converts the content string to MIME format.

Encoding Strings

When encoding a string, the following rules apply:

  • The alphanumeric characters "a" through "z", "A" through "Z" and "0" through "9" remain the same.

  • The special characters ".", "-", "*", and "_" remain the same.

  • The space character " " is converted into a plus sign "+".

  • All other characters are unsafe and are first converted into one or more bytes. Then each byte is represented by the three-character string "%xy," where xy is the two-digit hexadecimal representation of the byte.

Using the HTTP Target Connector to Send Message Segments

The HTTP target connect is segment-aware and you may use it to send message segments to integration partners.

See Integration Broker: Working With Message Segments.