After you create a RosettaNet participant business process, you must customize it for the associated RosettaNet conversation. Common customization tasks include:
Depending on your implementation requirements, you might make additional customizations to the participant business process as needed.
The RosettaNet participant business process file specifies the following default annotations:
@jpd:rosettanet protocol-name="rosettanet" protocol-version="2.0"
pip-name="processName" pip-version="1.0" pip-role="Seller"
These properties are set in the Property Editor that is visible when you have the Start node of your business process selected. Review and edit (if needed) the following properties:
Change to 1.1 if you are using RNIF (RosettaNet Implementation Framework) version 1.1 instead. |
||
Change to the RosettaNet PIP code, such as 3B2. Must be a valid PIP code as defined in http://www.rosettanet.org. |
||
Change to your RosettaNet PIP version (example: v01.01 for PIP3B2). Must be a valid version number associated with the PIP. |
||
Change to the RosettaNet name of the participant's role as defined in the PIP specification (example: Receiver for PIP3B2). |
Note: If the Property Editor is not visible in Design View, choose View —> Property Editor from the WebLogic Workshop menu.
To learn more about these annotations, see @jpd:rosettanet Annotation. To learn about configuring business process properties, see Business Process Language.
By default, the RosettaNet participant business process includes a Client Request node, named Receive Message, to handle an incoming RosettaNet request message from an initiator. For the response and callback.sendReply methods, you might need to specify the attachment and its Java data type. The data type must match the contents of the incoming message and can be one of the following values:
Default. Represents data in untyped XML format. The XML data is not specified at design time. |
|
Represents any non-XML structured or unstructured data for which no MFL file (and therefore no known schema) exists. |
|
Array containing one or more parts of a RosettaNet 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. |
Note: Attachments can also be typed XML or typed MFL data as long as you specify the corresponding XML Bean or MFL class name in the parameter.
To learn more about data types, see Working with Data Types.
Public and private business processes often use different document formats. Public business processes use the associated PIP schema. Private processes use whatever format is required by the internal process (XML or binary), such as a proprietary ERP format. If a private business process does not use the PIP format, then the public business process needs to transform data between the PIP format to the format used in the private business process.
To configure data transformation, you need to:
After you create a RosettaNet public participant business process, you need to link it to the private participant process that handles the initiator's request privately. WebLogic Workshop provides many ways for communicating with other business processes, including:
In this participant business process, if a time-out occurs while awaiting a reply from the initiator to the response document, the participant needs to send a Notification of Failure (PIP0A1) to the initiator. To learn more about PIP0A1, see the following URL:
To notify the initiator of the failure, you need to create a separate initiator business process that implements PIP0A1, and then start the initiator business process:
To learn about initiator business processes, see Introducing Trading Partner Integration at the following URL:
http://edocs.bea.com/wli/docs81/tpintro/index.html
About the RosettaNet Participant Business Process File
Creating a RosettaNet Participant Business Process
![]() |
|