Creating a RosettaNet Control

This topic describes how to create a new RosettaNet control. You add one RosettaNet control per public initiator business process. To learn more about public vs. private processes see, "Types of Business Processes" in "Trading Partner Business Process Concepts" in Introducing Trading Partner Integration at http://download.oracle.com/docs/cd/E13214_01/wli/docs81/tpintro/index.html. To learn about RosettaNet controls, see RosettaNet Control.

To create a new RosettaNet control

If you are not in Design View, click the Design View tab.
On the Controls section of the Data Palette, click Add.

Note: If the Controls tab is not visible in WebLogic Workshop, choose View —> Windows —> Data Palette from the menu bar. Instances of controls already available in your project are displayed in the Controls tab.

In the pop-up menu, click Integration Controls to display a drop-down list of controls that represent the resources with which your business process can interact.
Click RosettaNet to display the Insert Control - Insert RosettaNet dialog box.
In the Step 1 pane, in the Variable name for this control field, type the variable name used to access the new RosettaNet control instance from your business process. The name you enter must be a valid Java identifier.
In the Step 2 pane, select one of the following options:

Use a RosettaNet control already defined by a JCX file

Enter the name of the JCX file, or click the Browse button to find and select it.

Create a new RosettaNet control to use

Enter the name of the new JCX file to create.

If you are creating a new control, in the Step 3 pane, specify the following information:

Note: Where applicable, the values entered here must match their corresponding settings in the TPM repository.

Field

Description

from

Sender's DUNS number. Must be defined in the TPM repository.

to

Recipient's DUNS number. Must be defined in the TPM repository.

rnif-version

Version of the RNIF (RosettaNet Implementation Framework). One of the following values:

1.1

2.0

pip

RosettaNet PIP code, such as 3B2. Must be a valid PIP code as defined in http://www.rosettanet.org.

pip-version

RosettaNet PIP version. Must be a valid version number associated with the PIP.

from-role

RosettaNet role name for the sender as defined in the PIP specification, such as Buyer, Initiator, Shipper, and so on. A PIP request might be rejected if an incorrect value is specified.

to-role

RosettaNet role name for the recipient as defined in the PIP specification, such as Seller, Participant, Receiver, and so on. A PIP request might be rejected if an incorrect value is specified.

method-arg-type

Required. Type of attachment. Includes the standard RNIF XML parts. One of the following values:

XmlObject—Default. Represents data in untyped XML format. The XML data is not specified at design time.

RawData—Represents any non-XML structured or unstructured data and for which no MFL file (and therefore no known schema) exists. Not recommended, as the payload includes standard RNIF XML parts.

MessageAttachment[]—Array containing one or more parts of a business message. Message parts can be untyped XML data (XmlObject data type) or non-XML data (RawData data type). Used when sending different kinds of payloads (XML and non-XML) in the same message. The actual number of message parts might not be known until processed. To learn about working with MessageAttachment objects, see Using Message Attachments.

To learn more about data types, see Working with Data Types.

Click the Create button.
If you are prompted, select a subfolder in which to save the JCX file.

A RosettaNet control instance is displayed in the Controls tab.

Field	Description
from	Sender's DUNS number. Must be defined in the TPM repository.
to	Recipient's DUNS number. Must be defined in the TPM repository.
rnif-version	Version of the RNIF (RosettaNet Implementation Framework). One of the following values: 1.1 2.0
pip	RosettaNet PIP code, such as 3B2. Must be a valid PIP code as defined in http://www.rosettanet.org.
pip-version	RosettaNet PIP version. Must be a valid version number associated with the PIP.
from-role	RosettaNet role name for the sender as defined in the PIP specification, such as Buyer, Initiator, Shipper, and so on. A PIP request might be rejected if an incorrect value is specified.
to-role	RosettaNet role name for the recipient as defined in the PIP specification, such as Seller, Participant, Receiver, and so on. A PIP request might be rejected if an incorrect value is specified.
method-arg-type	Required. Type of attachment. Includes the standard RNIF XML parts. One of the following values: XmlObject—Default. Represents data in untyped XML format. The XML data is not specified at design time. RawData—Represents any non-XML structured or unstructured data and for which no MFL file (and therefore no known schema) exists. Not recommended, as the payload includes standard RNIF XML parts. MessageAttachment[]—Array containing one or more parts of a business message. Message parts can be untyped XML data (XmlObject data type) or non-XML data (RawData data type). Used when sending different kinds of payloads (XML and non-XML) in the same message. The actual number of message parts might not be known until processed. To learn about working with MessageAttachment objects, see Using Message Attachments. To learn more about data types, see Working with Data Types.