PIP Editor

The PIP Editor is displayed when you double-click the PIP entry on the RNIF Mailbox PIP tab or right-click an entry and select Edit.

For pre-defined or newly-defined PIPs, any field can be updated. PIP specifications can be obtained from RosettaNet at http://www.rosettanet.org/Standards/RosettaNetStandards/PIPDirectory/tabid/476/Default.aspx . The values for the fields in these tabs can be obtained from these specifications. 

The PIP Editor page contains five tabs: General, Content, Request, Request Ack, Response and Response Ack.

General tab

Use the General tab to specify general naming information for the PIP. 

PIP Code
The code that uniquely defines the PIP.
PIP Version
The version of the PIP specification. Incoming and outgoing messages are mapped to the PIP code and version to determine the rules for processing the message.
PIP Description
A user-friendly description of the PIP. This description is displayed in the PIP drop-down on the PIPs form.
My Role
The initiator role. This value is found in the specification for the PIP.
My Service
The initiator role's service. This value is found in the specification for the PIP.
Partner Role
The message receiver's role. This value is found in the specification for the PIP.
Partner Service
The receiver role's service. This value is found in the specification for the PIP.
Time to Perform
The total time to perform a two-action PIP. This field is not used for single-action PIPs. The expected value is found in the specification for the PIP. This field should be of the format HH:MM:SS.

Content tab

Use the Content tab to specify information related to sending and receiving of general message parts.

Retries
Specify the number of times to attempt resending the request or response when sending a request or response (as applicable to two-action PIPs) results in an error or fails to receive an expected acknowledgment.
Encryption
Specify whether no encryption is used (None), whether the service content and service content header are encrypted (Payload container), or just the service content (Payload only) is encrypted.
For selections other than None, the encryption algorithm to be used is selected in the Encryption Method field. If an encryption option is selected for any of the PIPs, encryption certificates will need to be specified in the mailbox Certificates tab. See RNIF Mailbox: Certificates Tab.
Signing
Select this check box to digitally sign messages. If Authorization Required is selected on any of the other tabs, you must select this option and sign the message. If you enable signing, the Signing Algorithm to be used can be selected and you must also specify signing certificates in the mailbox Certificates tab. See RNIF Mailbox: Certificates Tab.
Synchronous Acks
Select this check box to receive synchronous rather than asynchronous acknowledgments to requests and responses.

Request tab

Use the Request tab to define the rules for an incoming or outgoing message request.

Activity Id
The business activity name for the request. This value is found in the specification for the PIP.
Service Action Identity
The action name for the request. This value is found in the specification for the PIP.
Content Validation
Specify whether outgoing content (in the case of an outgoing message) or incoming content (in the case of an incoming message) is validated. Options are None, DTD, and Schema. If DTD or Schema is selected, it is expected that the DTD or schema reference are specified in the message content. Click Import to import a PIP DTD or schema file into the VersaLex application.
Authorization Required
Select this check box to compare the signing certificate for the incoming message against the signing certificate specified in the mailbox. 
Non-repudiation Required
Select this check box to save the the original request message in the host General tab's Sentbox folder for outgoing and Receivedbox folder for incoming. See RNIF Host.
Has Response
Select this check box if the PIP is a two-action PIP and will send a response. Clear the check box for single-action PIPs.

Request Ack tab

Use the Request Ack tab to define the rules for a request acknowledgment.

Time to Acknowledge
The amount of time to wait for a request acknowledgment.  If the time expires without an acknowledgment or exception, the original request is resent according to the retries rules.
Authorization Required
Select this check box to compare the signing certificate for the incoming message against the signing certificate specified in the mailbox. 

Response tab

The Response tab defines the rules for a response message.

Activity Id
The business activity name for the request. This value is found in the specification for the PIP.
Service Action Identity
The action name for the request. This value is found in the specification for the PIP.
Content Validation
Specify whether outgoing content (in the case of an outgoing message) or incoming content (in the case of an incoming message) is validated. Options are None, DTD, and Schema. If DTD or Schema is selected, it is expected that the DTD or schema reference are specified in the message content. Click Import to import a PIP DTD or schema file into the VersaLex application.
Authorization Required
Select this check box to compare the signing certificate for the incoming message against the signing certificate specified in the mailbox. 
Non-repudiation Required
Select this check box to save the original response message in the host General tab's Sentbox folder for outgoing and Receivedbox folder for incoming. See RNIF Host.

Response Ack

Use the Response Ack tab to define the rules for response acknowledgment.

Time to Acknowledge
The amount of time to wait for a response acknowledgment.  If the time expires without an acknowledgment or exception, the original response is resent according to the retries rules.
Include in Time to Perform
Select the check box if the time for the response acknowledgment is included in the Time to Perform specified on the General tab.
Authorization Required
Select this check box to compare the signing certificate for the incoming message against the signing certificate specified in the mailbox.