Oracle® Application Server ProcessConnect User's Guide 10g (9.0.4) Part Number B12121-01 |
|
This chapter describes the RosettaNet business-to-business (B2B) protocol standard and its implementation of trading partner agreements, and how Oracle Application Server ProcessConnect provides support for both.
This chapter contains these topics:
See Also:
B2B integrations enable trading partners to communicate with other trading partners outside an enterprise and over a network. B2B integrations use B2B protocol standards. B2B protocol standards provide guidelines for trading partners to follow when conducting business between enterprises. One B2B protocol standard is RosettaNet. Figure 24-1 shows RosettaNet's role in a B2B integration.
This chapter provides key details about the RosettaNet B2B protocol.
See Also:
|
RosettaNet is a group of leading technology companies that have created and implemented a common set of nonproprietary, XML-based, e-business standards. These standards define how trading partners conduct business through the exchange of business documents over the Internet.
The following sections describe key details about RosettaNet, as shown in Figure 24-2:
See Also:
"Oracle Application Server ProcessConnect Support for RosettaNet" for details on how Oracle Application Server ProcessConnect supports these key RosettaNet details |
The RosettaNet Implementation Framework (RNIF) defines implementation guidelines for creating software applications that provide for the reliable transport of partner interface processes (PIPs) in XML-format business documents between trading partners. Guidelines are provided for transport, routing, packaging, security, signals, and trading partner agreements.
These sections describe features of the following RNIF versions:
"Oracle Application Server ProcessConnect Support for the RosettaNet Implementation Framework" for additional details on how Oracle Application Server ProcessConnect supports RNIF implementation guidelines
See Also:
Table 24-1 describes several RNIF version 1.1 implementation guidelines.
Table 24-2 describes several RNIF version 2.0 implementation guidelines.
This section contains the following PIP topics:
The exchange of business data between trading partners is the fundamental purpose of PIPs. PIPs are specialized, XML-based dialogs that define the structure, sequence of steps, role (buyer and seller) activities, data elements, values, and value types for each business document message exchanged between trading partners. Conformance to these specifications enables trading partners to achieve the business objective.
PIPs require the following:
Trading partners agree on the set of PIPs to support to conduct business. Each partner must fulfill their specific requirements of the PIP. If one trading partner does not fulfill all requirements, then the business transaction is voided for all participating PIP trading partners.
PIPs consist of the following major views:
Describes the flow between roles as they perform business activities
Describes the design of and interactions between network components as they execute a PIP. Network components are also known as services, and include buyers and sellers.
Describes the message structures of actions performed by roles (for example, the XML DTDs and message guidelines) and communication requirements for network components (for example, for the use of Secure Socket Layer (SSL) and digital signatures)
PIPs are classified into clusters, segments, and individual PIPs. The following PIP clusters are provided:
Each cluster is subdivided into segments. Each segment includes individual PIPs. Individual PIPs contain one or more activities, which specify actions to be performed.
For example, Table 24-3 identifies PIP3A4 features.
Element | Description |
---|---|
3 |
Order management cluster, which lets trading partners: |
3A |
Quote and order entry segment |
3A4 |
Specific PIP type. This PIP supports the: |
Figure 24-3 shows the message flow when a buyer and seller use PIP3A4 V02.00. This PIP enables a buyer to request a purchase order and a seller to acknowledge if the order request is accepted, rejected, or pending. An acknowledgment can also include details about delivery expectations. A purchase order acceptance is typically sent after checks for price and availability occur.
See Also:
|
The RosettaNet dictionaries define and describe a common set of properties for use in PIP messages. These properties define a common vocabulary for conducting business. This ensures that the data exchanged between trading partners is consistent, overlapping efforts of trading partners are eliminated, and confusion caused by the uniquely defined terminology of each trading partner is reduced. Two dictionary types are provided:
Designates the properties used in basic business transactions between trading partners. The Business Dictionary defines the business properties, business data entities, and fundamental business data entities in PIP messages.
Provides properties for defining products and services. The Technical Dictionary eliminates the need for trading partners to use separate dictionaries when implementing PIPs.
For example, if two trading partners are engaged in a business transaction involving the sale of personal computers, the Technical Dictionary describes the computer features in a text document, such as:
See Also:
http://www.rosettanet.org
RosettaNet validation compares the elements in RosettaNet XML-format business documents to the requirements specified in the RosettaNet Message Guideline specification to determine their validity. This specification defines requirements for details such as element datatypes, element lengths, element value lists, and element cardinality. PIPs that require RosettaNet dictionary validation are also validated when a dictionary is present.
The minimum validation-level requirements on the sections of a RosettaNet XML-format business document are as follows. These requirements cover the preamble, delivery header, service header, and service content sections of a document. Documents not following one or more of these requirements are identified as invalid.
See Also:
http://www.rosettanet.org
Oracle Application Server ProcessConnect provides RosettaNet B2B protocol standard support with the B2B adapter. Figure 24-4 shows the role of the B2B adapter in a B2B integration.
The B2B adapter is a plug-in component to the Oracle Application Server ProcessConnect adapter framework. The adapter framework enables communication between the Oracle Application Server ProcessConnect runtime system (the component that executes integrations) and various adapters. These adapters enable Oracle Application Server ProcessConnect to communicate with applications and trading partners, enabling integration types such as B2B to be executed. The B2B adapter supports the features of the RosettaNet B2B protocol standard.
See Also:
The following documentation for additional details about adapters and the adapter framework:
|
Oracle Application Server ProcessConnect supports the following RNIF versions:
"Adding a Business Protocol" for instructions on adding RNIF 1.1 or RNIF 2.0 support
See Also:
Table 24-4 describes several RNIF version 1.1 features supported by the B2B adapter during Oracle Application Server ProcessConnect runtime.
Table 24-5 describes several RNIF version 2.0 features supported by the B2B adapter during Oracle Application Server ProcessConnect runtime.
The B2B adapter supports the RosettaNet PIPs shown in Table 24-6.
See Also:
|
Oracle Application Server ProcessConnect supports the RosettaNet Business Dictionary described in "RosettaNet Dictionaries". The RosettaNet Technical Dictionary is not currently supported. Only PIP2A9 (not supported by Oracle Application Server ProcessConnect) currently uses the RosettaNet Technical Dictionary.
Oracle Application Server ProcessConnect supports RosettaNet validation, as described in "RosettaNet Validation". This support is preseeded in Oracle Application Server ProcessConnect and cannot be changed. RosettaNet Business Dictionary validation of RosettaNet documents is also supported. RosettaNet Technical Dictionary validation of RosettaNet documents is not currently supported.
A trading partner agreement is an electronic agreement that defines the way in which two trading partners agree to interact when performing an agreed-on business collaboration. An example of a business collaboration is RosettaNet PIP3A4 (purchase order request), where one trading partner acts as the role of buyer to request a purchase order and another trading partner acts as the role of seller to send a purchase order acceptance. (See "PIP Message Flow Example" for details.) Trading partner agreements essentially define the terms and agreements that enable business documents to be exchanged between trading partners.
The trading partner agreement is independent of the internal processes executed at each trading partner's individual site. The trading partner agreement does not expose the internal processes of a trading partner to other trading partners.
The contents of a trading partner agreement include the following elements. Each element includes data essential to a trading partner agreement. After these elements of data are fully defined, you assign them to a trading partner agreement.
Figure 24-5 provides a specific example of trading partner agreement elements and the types of data that can be defined in these elements.
A trading partner is an organization or enterprise that engages in business transactions with another trading partner. The trading partner agreement captures the agreed-on capabilities of both trading partners to conduct a business transaction. Trading partners include the following elements of data for identification and communication capabilities:
The party ID defines the agreed-on identification to be used to conduct the business collaboration. RosettaNet sends the party ID data as part of the business protocol header. One example is the data universal numbering system (DUNS) number. Trading partners must obtain a DUNS number themselves. Other examples can include an e-mail address or any other standard that a company decides to use.
The delivery channel describes the communication capabilities. To conduct a business collaboration, messages must be exchanged in a sequence. Messages must follow an agreed-on, predefined exchange mechanism and must be sent over an agreed-on transport. Message exchange details are defined by the document exchange. The delivery channel also provides security details to ensure a secure message exchange. These capabilities are described in the following sections:
The document exchange provides data about the supported exchange protocol. The document exchange layer receives a business document, encrypts it (if specified), adds a digital signature for nonrepudiation (if specified), and sends it to the transport for transmission to the other trading partner. The document exchange elements essentially describe a trading partner's message receiving characteristics. Examples of document exchange types include the following:
"RosettaNet Implementation Framework" for a description of RNIF capabilities
See Also:
The transport is responsible for message delivery using the selected transport protocol. The transport defines the trading partner's capabilities with regards to the following:
Collaborations describe how message processing occurs, including the message exchange order, the documents exchanged, role exchange order, and the actions. Collaborations consist of business activities. Business activities are conducted between the roles authorized to participate in a collaboration. A business activity can be either a business transaction or a business collaboration. Collaborations include the following elements of data that you assign to a trading partner agreement:
A business transaction is a unit of business conducted by two or more trading partners that generates a definite state of success or failure. A business transaction is conducted between two parties playing opposite roles in a transaction. The roles are always an initiating role (the from role) and a responding role (the to role). Trading partners participate in the business collaboration through roles. The business transactions are sequenced to occur in a predefined order.
A business transaction consists of a set of business data and business signal exchanges between trading partners that occur in an agreed-on format, sequence, and time period. If any of the agreements are violated, the transaction is terminated and all business data and business signal exchanges are discarded.
For example, a trading partner acting as the role of buyer submits a purchase order request message to a trading partner acting as the role of seller. The trading partner acting as the role of seller receives the message and delivers a purchase order response message acknowledging the receipt.
A business collaboration consists of a set of roles (buyer and seller) collaborating through a set of agreed-on business transactions by exchanging business documents. Trading partners participate in a business collaboration through roles. This business collaboration must achieve a specified outcome.
PIPs are mapped to business collaborations. Examples of business collaborations include the following:
See Also:
Roles represent the actors (such as a buyer and seller) authorized to participate in a collaboration (for example, PIP3A4). A collaboration includes the following:
The business actions define the documentation types to be exchanged. For example, the following business actions occur when a request purchase order business transaction is initiated by a buyer role and responded to by a seller role:
Oracle Application Server ProcessConnect provides support for the elements comprising a trading partner agreement. This section first describes Oracle Application Server ProcessConnect support for trading partner agreement elements and then provides an overview of how the Oracle Application Server ProcessConnect user interface tool supports these elements.
This section contains these topics:
The B2B adapter supports the following elements:
The B2B adapter uses the party ID to identify the trading partner agreement. The Oracle Application Server ProcessConnect user interface tool identifies the party ID through the concept of the trading partner identification type. Examples of trading partner identification type include a DUNS number, an e-mail address, or any identifier that you chose to use.
See Also:
The following sections for instructions on performing these tasks:
|
The B2B adapter supports the following elements of data:
The following sections for instructions on performing these tasks:
See Also:
The B2B adapter supports the document exchange features shown in Table 24-7. These features are included with RNIF 1.1 and RNIF 2.0 unless otherwise stated.
The transport is responsible for message delivery using the selected transport protocol. The B2B adapter uses the HTTP and secure HTTP transport communication protocols.
For outgoing messages sent from the B2B adapter to a trading partner, the B2B adapter calls the transport with the message to send and provides the necessary transport protocol-specific bindings. For incoming messages received from a trading partner, the transport receives the messages and calls the B2B adapter with the received message and transport binding data for processing. The transport binding data specifies the protocol-specific status data and a list of protocol headers with their values.
Oracle Application Server ProcessConnect provides support for collaborations. Collaborations consist of business activities. Business activities are conducted between the roles authorized to participate in a collaboration. The B2B adapter supports the following elements.
A business transaction consists of a request message (for example, a request purchase order) and an optional response message (for example, respond to a purchase order request). The B2B adapter provides support for one business transaction. The B2B adapter supports request and response messages. The B2B adapter enforces the time limit to perform the business transaction.
The B2B adapter provides the following additional collaboration support:
Roles represent the actors (such as a buyer and seller) authorized to participate in a collaboration (for example, PIP3A4). The B2B adapter provides support for roles.
See Also:
"Creating a Supported Actor" for instructions on assigning a role to a trading partner (such as the role of a seller using PIP3A4 with RNIF 2.0) |
The B2B adapter provides support for actions through the concept of business actions. The business action defines the documentation types to be exchanged.
RosettaNet and Oracle Application Server ProcessConnect differ slightly in the use of terminology. Table 24-8 identifies these differences.
This chapter describes Oracle Application Server ProcessConnect support for the following RosettaNet features:
Oracle Application Server ProcessConnect support for trading partner agreements is also described.
|
![]() Copyright © 2003 Oracle Corporation. All Rights Reserved. |
|