Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

HTTP Transport

HTTP Transport

HTTP Transport
Select this policy assertion as described in Adding Policy Assertions.
You can add this policy to a Partner Role. It is not applicable for a My Role. Depending on the REST service requests from the process, you may wish to set one or more of the HTTP transport sender timeout values.
Note
: This policy currently works only in conjunction with REST-enabled processes.
Client Connection Timeout
The timeout until a connection is established. A value of zero means the timeout is not used. Zero is the default.
Connection Pool Manager Timeout
Set the connection acquisition timeout value. The default is not defined.
Socket Timeout
The default socket timeout (SO_TIMEOUT) in milliseconds that is the timeout for waiting for data. A timeout value of zero is interpreted as an infinite timeout. This value is used when no socket timeout is set in the HTTP method parameters.
TCP no delay
Enable, if used.
The TCP no delay parameter controls TCP (Transmission Control Protocol) packet batching. The default value is 1, which means that TCP packets are not batched.
Determines whether Nagle's algorithm is to be used. (The Nagle's algorithm tries to conserve bandwidth by minimizing the number of segments that are sent.) To decrease network latency and increase performance, Process Server disables Nagle's algorithm (by enabling TCP_NODELAY). Data is sent earlier, at the cost of an increase in bandwidth consumption and number of packets.
Redirect with GET
Instruct the browser to load a different page using an HTTP GET request.
XML MIME Types
To interpret data correctly, add additional MIME types, such as
image/svg+xml
.

0 COMMENTS

We’d like to hear from you!