Notify and Request-Response Activity Properties

Depending on the type of PIP activity you select, you see either the Notify Activity tab or the Request-Response Activity tab when you configure the activity in the Notify Activity window or New Request-Response Activity window.

You can override certain PIP activity settings when configuring protocol bindings for a business agreement. For more information, see the Operation Settings tab .

The following tables contain the settings for Notify and Request-Response activities:

General Tab
Field Description

Name

The displayed name of the activity.

Description

A short description of the activity.

Default RNIF Version

The default RNIF version to use when the private process does not specify a valid RNIF version.

From Role Classification Code

The From role for this activity as specified in RNIF.

Example: Forecast Owner.

To Role Classification Code

The To role for this activity as specified in RNIF.

Example: Forecast Recipient.

From Business Service Code

The From business service code for this activity as specified in RNIF.

Example: Forecast Owner Service.

To Business Service Code

The To business service code for this activity as specified in RNIF.

Example: Forecast Recipient Service

Private Process Tab
Field Description
Private Process Settings :

Send Parsed XML to Private Process

Send the XML document to the private process.

Send Actual Payload to Private Process Instead of File Reference

Always send the actual payload data to the private process instead of a file reference. If this checkbox is selected, then large payload handling is disabled.

Private Process Wait Time (seconds)

The time in seconds that the BusinessConnect Container Edition server waits for the private process to respond to a request before the server sends an error to the trading partner.
RNIF 2_0 Tab
Field Description
RNIF 2.0 Settings :

Payload Compression

Select this checkbox to enable payload compression for any outgoing documents. (For inbound PIPs, TIBCO BusinessConnect Container Edition - RosettaNet Protocol accepts both compressed and uncompressed documents.)

Payload Encryption

Select any one of the choices:
  • None
  • Payload Only
  • Payload Container