HTTP(S) Submit output connector

These connectors enable the StreamServer to function as an HTTP client submitting output to an HTTP server.

Comments

Use the HTTPS Submit connector if you want the StreamServer to function as an SSL client that communicates over an encrypted HTTPS channel.

The connector settings are described below.

Use security configuration

Select whether to use a security configuration or a CA certificate for the HTTPS Submit connector. If the HTTPS server requires client authentication, you must use a security configuration. If the HTTPS server does not require client authentication, you can use a CA certificate instead.

CA certificate

The CA root certificate that confirms the identity of the SSL server. See the Encryption and authentication documentation for more information about security configurations. The certificate must be included in a resource set connected to the Platform.

PEM encoded x 509 certificates are supported.

Security configuration

The Security configuration to use with the HTTPS Submit connector. See the Encryption and authentication documentation for more information. The security configuration must be included in a resource set connected to the Platform.

Method

The method to use when submitting output to the HTTP server.

•	POST – Send output to the HTTP server for further processing.

•	PUT – Send output to the HTTP server. For example, if output is a web page, select PUT to put it on a web server. Requires scripting and specific access rights to the server.

URL

The URL to the HTTP server.

Content-type

The content-type of the output to send to the HTTP server.

Example 20

Content-type

text/html; charset="ascii"

 

Time-out

The maximum time (milliseconds) the StreamServer waits before cancelling a transfer.

Version

The HTTP version to use.

SSL version

The SSL version to use with the HTTPS Submit connector. The server and the clients must use the same SSL version.

Authentication

The type of authentication scheme (RFC 2617) to use for password authentication.

•	None - Do not use authentication.

•	Basic - Send authentication parameters as clear text. This is the only scheme supported in HTTP/1.0.

•	Digest - Send authentication parameters as a checksum over the network. Requires HTTP/1.1.

Realm

The name of the realm to access. Used only if authentication is required.

User name

A user name to access the realm. Used only if authentication is required.

Password

A password to access the realm. Used only if authentication is required.

Cache file

The cache file that stores communication checksums between StreamServer start/stop.

Runtime specific connector settings

Custom header

A custom header to add to the output. Use the following syntax:

Name:Value

You can separate Name:Value pairs with <0d><0a>.

Response place connector

The name of the connector that receives the response from the HTTP server. Used only if a response is required. This connector is either an HTTP Response output connector, or any type of queue enabled input connector.

Example 21

Using an HTTP Response connector as Response place connector

1	A client sends input to the StreamServer via an HTTP input connector.

2	The StreamServer processes the data.

3	The processed data is sent via an HTTP Submit connector to an HTTP server.

4	The HTTP Response connector collects the response from the HTTP server.

5	The HTTP connector retrieves the response from the HTTP Response connector, and sends it to the client.

 

Example 22

Using an input connector as Response place connector

1	A client sends input to the StreamServer via an HTTP input connector.

2	The StreamServer processes the data.

3	The processed data is sent via an HTTP Submit connector to an HTTP server.

4	The input connector collects the response from the HTTP server.

5	The response data is queued as a separate job.

 

Response custom header

A custom header to add to the response from the HTTP server. Use the following syntax:

Name:Value

On failure file

The path to a file to be used if output cannot be delivered to the HTTP server.

On failure place connector

The connector that retrieves the On failure file specified above. This connector is either an HTTP Response output connector, or any type of queue enabled input connector. For example, if the StreamServer receives input from a client, and sends output to an HTTP server, an error message (the on failure file) can be sent back to the client via an HTTP Response connector.

Example 23

Using an HTTP Response connector as On failure place connector

1	A client sends input to the StreamServer via an HTTP input connector.

2	The StreamServer processes the data.

3	The StreamServer tries, but fails, to send the processed data via an HTTP Submit connector to an HTTP server.

4	The HTTP Response connector collects the On failure file.

5	The HTTP connector retrieves the On failure file from the HTTP Response connector, and sends it to the client.

 

Example 24

Using an input connector as On failure place connector

1	A client sends input to the StreamServer via an HTTP input connector.

2	The StreamServer processes the data.

3	The StreamServer tries, but fails, to send the processed data via an HTTP Submit connector to an HTTP server.

4	The input connector collects the On failure file.

5	The On failure file is queued as a separate job.

 

On failure content-type

The content type of the On failure file.

Example 25

On failure content type

text/html; charset="ascii"

 

On failure custom header

A custom header to add to the response with the On failure file. Use the following syntax:

Name:Value