| Oracle® Application Server Integration B2B User's Guide 10g Release 2 (10.1.2) Part Number B19370-03 |
|
|
View PDF |
| Oracle® Application Server Integration B2B User's Guide 10g Release 2 (10.1.2) Part Number B19370-03 |
|
|
View PDF |
acknowledgment mode
The mode in which trading partners receive messages (asynchronous or synchronous).
active configuration
A configuration state during which the trading partner agreement included in the configuration is available for execution of business in the OracleAS Integration B2B runtime repository. Incoming messages are accepted based on your design in the trading partner agreement and processed accordingly.
admin user
The default username for accessing and using the OracleAS Integration B2B user interface. This username is created automatically during installation.
Administration tab
A main tab of the OracleAS Integration B2B user interface that enables you to manage and administer OracleAS Integration B2B, including exporting and importing the design-time repository; importing configurations; importing RosettaNet collaborations, EDI transaction sets, and UCCnet standards; importing and purging the design-time repository and instance data in the runtime repository; and managing contact types and trading partner identification types.
Administrator role
The role that enables a user to access and use the entire OracleAS Integration B2B user interface. Only a user in the host trading partner organization can be assigned this role.
Applicability Statement 2
An EDI specification between businesses using the Internet's Web page protocol (HTTP). This specification was created by EDI over the Internet (EDIINT), a working group of the Internet Engineering Task Force (IETF) that develops secure and reliable business communication standards.
B2B core
The process, document, and exchange protocols and protocol revisions supported by OracleAS Integration B2B.
B2B integration
B2B integration enables trading partners to exchange business data across networks such as the Internet and incorporates the trading partners' host applications and business processes.
business action
Identifies the roles played in a configuration using an EDI or Custom Document business protocol. Business actions describe the business documents and their movement between trading partners. In the OracleAS Integration B2B user interface, trading partners define their operational capabilities by the business actions they support.
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.
Business Message Status Reports
Monitor trading partner business message instances for EDI or Custom Document business protocols.
business protocol
Identifies the implementation guidelines to use for the reliable transport of business document messages between trading partners. The business protocol consists of three protocols: process (of which support for business actions and collaborations are a part), document, and exchange.
business transaction
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 trading partners playing opposite roles in a transaction. The roles are always an initiating role and a responding role.
business-to-business
A type of integration technology that enables companies to integrate trading partners with other trading partners.
callouts
Used to transform documents from one form to another. You can use callouts to invoke an XSLT style sheet and any Java program in general. For example, an incoming remote trading partner's EDI document is sent to the host trading partner's host Oracle E-Business Suite application, which uses XML. Callouts enable you to transform the EDI document into an XML format understood by the Oracle E-Business Suite application. The outgoing document can then be transformed back into its original format. Callouts are associated with internal delivery channels.
collaboration
Collaborations consist of a set of RosettaNet PIPs that define the capabilities of a trading partner in a business transaction (such as buyer and seller). Collaborations describe the business documents and their movement between trading partners. In the OracleAS Integration B2B user interface, trading partners define their operational capabilities by the collaborations they support.
Collaboration Status Reports
Monitor trading partner business message instances for the RosettaNet over RNIF business protocol.
communication capabilities
Define the following details for the business protocol of a host or remote trading partner:
Delivery channel details, such as use of nonrepudiation, encryption, and transport security
Document exchange details, such as use of digital envelopes, encryption credentials, digital signatures, and signing credentials
Transport details, such as transport mode, protocol, server name, and endpoint address details
concurrent conversations
Defines the maximum number of concurrent collaboration instances that can be in progress at any time.
configuration
A collection of partner data of trading partners that is consistent, complete, and deployable. Creating a configuration enforces the validation rules so that only valid, complete, and consistent data is available in the runtime repository.
configuration states
The state that a configuration is in at any given time (for example, active, validated, quiesced, retired, and discarded).
contact information
The method by which to contact a user or organization when you want to perform a specific action (such as reviewing a trading partner or trading partner agreement).
contact types
The method for contacting persons and organizations (such as a phone number or e-mail address) when a specific activity within OracleAS Integration B2B is required (such as reviewing a trading partner agreement).
Create Business Action wizard
Enables you to create support for business actions for any EDI or Custom Document business protocol.
Create Collaboration wizard
Enables you to create support for PIP collaborations for the RosettaNet over RNIF business protocol.
Create Trading Partner wizard
Enables you to create a remote trading partner, assign support for a business protocol to a remote trading partner, assign operational capabilities (collaborations or business actions) to a remote trading partner, and assign communication capabilities (delivery channels, document exchanges, transports, and endpoint details) to a host trading partner and remote trading partner.
The host trading partner is automatically assigned support for all business protocols and operational capabilities; only the communication capabilities for the host trading partner must be created.
Data Universal Numbering System
A unique, sequentially-generated, nine-digit number that you can assign as the trading partner identification type. You obtain this number from Dun and Bradstreet.
delivery channel
Describes whether trading partner security characteristics such as nonrepudiation of origin and receipt, acknowledgment mode, time to acknowledge, retry count, transport security, encryption, and file compression are required. The delivery channel also includes the associated transport (with its transport protocol, mode, server, and endpoint address) and document exchange (with its exchange protocol parameters, exchange protocol override elements, and, if defined, its support for digital envelope, encryption credentials, digital signature, signing credentials, and validation).
deployment
The process of activating a configuration from the design-time repository to the runtime repository.
Deployment tab
A main tab of the OracleAS Integration B2B user interface that enables you to manage (create, validate, deploy, quiesce, discard, or export) a configuration.
design-time repository
The repository in which partner data (trading partners and trading partner agreements) is stored before being included in a deployed configuration in the runtime repository. The OracleAS Integration B2B design-time repository is part of the Oracle Application Server Metadata Repository.
digital signature
Created when a public key algorithm signs the sender's message with the sender's private key. The digital signature ensures that the document is authentic, has not been forged by another trading partner, has not been altered, and cannot be repudiated by the sender.
discarded configuration
A configuration state during which a configuration has been discarded and cannot be deployed. These types of configurations were created and validated, but never deployed.
document definition
The fourth level in the document protocol hierarchy. In this hierarchy, a document protocol can consist of multiple document protocol revisions. A document protocol revision can consist of multiple document types. A document type can consist of multiple document definitions. A document definition can consist of an XSD or DTD file and associated information. An example of a document definition is an XSD file for EDI X12 4010 8050 or a DTD file for RosettaNet V02.00 RequestPurchaseOrder.
document exchange
Describes the supported exchange protocol (such as RosettaNet 02.00) and, if being used, credential encryption and signing credentials, digital envelopes and digital signatures, and validation support. The document exchange uses these capabilities to exchange messages with a trading partner.
document protocol
Defines the document type of the message payload. The first level in the document protocol hierarchy. In this hierarchy, a document protocol can consist of multiple document protocol revisions. A document protocol revision can consist of multiple document types. A document type can consist of multiple document definitions. An example of a document protocol is RosettaNet, EDI X12, EDI EDIFACT, or Custom Document (such as UCCnet).
document protocol revision
The second level in the document protocol hierarchy. In this hierarchy, a document protocol can consist of multiple document protocol revisions. A document protocol revision can consist of multiple document types. A document type can consist of multiple document definitions. An example of a document protocol revision is RosettaNet V02.00 or EDI X12 4010.
document type
The third level in the document protocol hierarchy. In this hierarchy, a document protocol can consist of multiple document protocol revisions. A document protocol revision can consist of multiple document types. A document type can consist of multiple document definitions. An example of a document type is a RosettaNet RequestPurchaseOrder or EDI X12 4010 850.
e-business
The conduct of business over the Internet, such as buying and selling products, servicing customers, and collaborating with other companies, known as trading partners.
ebXML Messaging Service
Electronic business extensible markup language is a specification for XML standards that is used to exchange XML-based messages. The ebMS exchange protocol in OracleAS Integration B2B is used in the Custom Document over ebMS business protocol.
EDI EDIFACT
EDI for Administration, Commerce, and Transport (EDIFACT) is the international standard for EDI. Developed by the United Nations, these standards work for international conventions for electronic data interchange.
EDI X12
A numbered set of commercial EDI transactions defined by the American National Standards Institute's Accredited Standards Committee X12. These uniform rules for the interchange of business documents are defined for cross industry EDI use and are based upon the variable-length X12 standard.
endpoint
The physical endpoint address of a trading partner. An endpoint includes a protocol endpoint, which is a combination of a specific endpoint address (such as http://server.partner.com:5555/submit/rnmsg) and transport protocol (such as HTTP 1.1). The trading partner uses this address to send or receive data. Endpoints are global to all trading partners.
exchange protocol
Defines the message exchange mechanism—how to exchange the documents defined by the document protocol. It defines the headers, the acknowledgments, and the packaging that puts the headers and payload together. It also defines the transport protocol and packaging protocol for the exchange.
export
The OracleAS Integration B2B user interface provides design-time repository export functionality that enables you to perform the following tasks:
Export the entire contents of the design-time repository to an XML file
Export a configuration created under the Deployment tab to and from the design-time repository
Export the partner data associated with trading partners and trading partner agreements to XML files that can then be submitted to individuals for optional review and eventual approval
Health Level 7
This specification for the health care domain—pharmacy, medical devices, imaging, insurance claim processing, and so on—provides standards to exchange and manage health care-related information. OracleAS Integration B2B provides the HL7 over Generic Exchange and the HL7 over MLLP Exchange business protocols.
host application
The application installed within the host trading partner's environment. An internal delivery channel is the communication interface between the host trading partner's host application and their installation of OracleAS Integration B2B.
host trading partner
The organization in which OracleAS Integration B2B is installed. The host trading partner conducts business with the remote trading partner (the organization outside your enterprise).
ias_admin user
The default user account for accessing and using the Oracle Enterprise Manager 10g Application Server Control Console. This user is created automatically during installation.
import
The OracleAS Integration B2B user interface provides design-time repository import functionality that enables you to perform the following tasks:
Import the entire contents of the previously exported design-time repository from an XML file
Import a previously exported configuration created under the Deployment tab
Import support for RosettaNet collaborations (partner interface processes (PIPs)), EDI X12 and EDIFACT transaction sets, and UCCnet standards into the design-time repository to assign to trading partners
Import reports
Import the design-time repository and instance data of the runtime repository
instance data
Partner data included in a deployed configuration. During configuration creation, partner data of the integration is validated end-to-end a final time to ensure that only a complete and consistent configuration is deployed to the run-time repository. After a configuration is deployed, the runtime repository stores the configuration of run-time data required to execute an integration. Run-time data is created during run time when messages are exchanged between trading partners. These messages are logged in an instance table in the runtime repository.
internal delivery channels
An internal delivery channel is the communication interface between the host trading partner's host application and their installation of OracleAS Integration B2B. Internal delivery channels operate only within the host trading partner's enterprise.
internal endpoints
Predefined endpoints that are associated with a specific internal delivery channel to enable communication between the host trading partner's host application and their installation of OracleAS Integration B2B. Internal endpoints operate only within the host trading partner's enterprise.
lifecycle management
Enables you to manage the various states in the design and deployment of partner data (such as draft, approved, and deployed).
lifecycle states
The states that partner data is in at any given point in time. The set of lifecycle states is based on state changes that must be captured from a business (that is, integration) standpoint.
message payload
The data contents of a message (for example, a payload of a purchase order can identify the quantity ordered, the total cost, the product being ordered, and so on).
middle tier
The host on which you installed the J2EE and Web Cache and OracleAS Integration B2B installation types.
multipurpose internet mail extensions
An extension of the original Internet e-mail protocol that lets users use the protocol to exchange different kinds of datafiles on the Internet: audio, video, images, application programs, and other kinds, as well as the ASCII handled in the original protocol, the simple mail transfer protocol (SMTP).
nonrepudiation
A standard that provides absolute evidence that a specific action occurred. OracleAS Integration B2B supports two types:
Nonrepudiation of origin requires a message sender to digitally sign a message. This protects against any attempt by a sender to deny sending a message.
Nonrepudiation of receipt requires a message recipient to send back a digitally signed acknowledgment. This protects against any attempt by a message recipient to deny receiving a message.
operational capability
Defines the support for business actions or collaborations for the business protocol of a host or remote trading partner.
OracleAS Integration B2B - Document Editor
An integrated guideline creation and implementation application for creating business-to-business (B2B) electronic commerce. You can use the OracleAS Integration B2B - Document Editor library of templates to create EDI X12 and EDI EDIFACT .ecs files, RosettaNet XSD, HL7, and DTD files that you then import into the OracleAS Integration B2B user interface tool with the Create Business Action wizard and Create Collaboration wizard. This enables you to create configurations with OracleAS Integration B2B trading partners that use EDI X12, EDI EDIFACT, HL7, and RosettaNet.
Oracle Application Server Containers for J2EE
A complete set of J2EE containers written entirely in Java that execute on the Java Virtual Machine (JVM) of the standard Java Development Kit (JDK).
Oracle Application Server Metadata Repository
An Oracle database that contains schemas and business logic used by application server components (including OracleAS Integration B2B). The OracleAS Integration B2B schema is part of the OracleAS Metadata Repository. The OracleAS Integration B2B design-time repository and runtime repository are both part of the OracleAS Metadata Repository.
Oracle Application Server Integration B2B (OracleAS Integration B2B)
Enables you to successfully design, deploy, monitor, and maintain configurations between trading partners.
Oracle E-Business Suite
Provides a complete set of applications capable of automating daily business process functions. These applications assist in running supply chain operations; managing employees; and marketing, selling, and providing customer services.
Oracle Process Manager and Notification Server
Enables you to monitor Oracle Application Server Metadata Repository processes based on settings in the opmn.xml file.
Oracle Wallet Manager
A Java-based application that security administrators use to manage public-key security credentials on clients and servers.
packaging
Encapsulates all components of a message into a packaging format (for example, OracleAS Integration B2B supports the multipurpose internet mail extensions (MIME) format).
packaging protocol
Defines a packaging mechanism. Message security such as signing and encryption are often based on a specific packaging mechanism.
partner data
Design-time data before it is included in a deployed configuration (for example, trading partner and trading partner agreement data). Partner data is the data that you create under the Partners tab in the OracleAS Integration B2B user interface. Partner data is stored in the design-time repository part of the Oracle Application Server Metadata Repository.
Partners tab
A main tab of the OracleAS Integration B2B user interface that enables you to create a remote trading partner, assign support for a business protocol to a remote trading partner, create the operational capabilities (support for collaborations or business actions) for the business protocol of the remote trading partner, and create the communication (delivery channel, security, transport, transport server, and endpoint details) capabilities for the business protocols of the remote and host trading partners.
The host trading partner is automatically assigned support for all business protocols and operational capabilities; only the communication capabilities for the host trading partner must be created.
person
A user that can be assigned as an OracleAS Integration B2B user interface user or as an optional reviewer of trading partner and trading partner agreement details.
process protocol
Defines how documents are exchanged. Process protocols define the support for collaborations (for the RosettaNet over RNIF business protocol) and business actions (for any EDI or Custom Document business protocols) that are associated with specific document types.
protocol endpoint
Consists of a transport protocol (such as HTTP 1.1) and trading partner endpoint address (such as URI www.myapp124abc.com).
purging
Deletes data from the design-time repository with the exception of data that was part of installation. In addition, instance data in the runtime repository can also be purged.
quiesce
The process of gracefully shutting down a deployed configuration. A configuration can be automatically or manually quiesced.
quiesced configuration
A configuration state during which the configuration is in the process of being quiesced (retired). Once quiesced, the configuration can be retired or redeployed.
remote trading partner
The organization outside your enterprise with whom to conduct business. The host trading partner must define the capabilities for both the host and remote trading partners with the OracleAS Integration B2B user interface.
remote trading partner certificates
A method by which to secure the given exchange of data. A certificate securely binds an identity such as a trading partner to a public key. A certificate is created when a trading partner's public key is signed by a trusted identity known as a certificate authority (CA). This certificate ensures that the trading partner's data is correct and that the public key actually belongs to that trading partner. You select the location of a certificate. This is typically the location for the Oracle Wallet Resource Locator.
Reports role
Provides a host trading partner user with access to only the functionality of the Reports tab of the OracleAS Integration B2B user interface. A user with this role cannot see or access the other parts of the user interface.
Reports tab
A main tab of the OracleAS Integration B2B user interface that enables you to create reports that describe OracleAS Integration B2B run-time behavior.
retired configuration
A configuration state during which a deployed configuration has been quiesced and retired. This configuration cannot be redeployed. This occurs when you deploy another configuration. This action causes any currently running configurations to be quiesced and retired. You can also manually quiesce a deployed configuration.
RosettaNet
A nonprofit organization of leading technology companies that has 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. Guidelines are provided for transport, routing, packaging, security, signals, and trading partner agreements.
RosettaNet Business Dictionary
A RosettaNet dictionary that designates the properties used in basic business transactions between trading partners. The business dictionary defines the business properties and fundamental business data entities in PIP messages.
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 information 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. There are two dictionary types: business dictionary and technical dictionary. OracleAS Integration B2B supports only the business dictionary.
RosettaNet Implementation Framework
Defines the implementation guidelines for the reliable exchange of business data messages (in XML business documents) between trading partners over the Internet.
RosettaNet Partner Interface Process
XML-based dialogs that define the specific sequence of steps required to execute a business process (and thus, exchange data) between trading partners. PIPs are XML-based dialogs that define the structure, allowable data elements, values, and value types for each business document message exchanged. Trading partners agree on the set of PIPs to support to conduct business.
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 information such as element datatypes, element lengths, element value lists, and element cardinality.
runtime repository
Stores the run-time data required to deploy and execute a configuration. Run-time data is created during run time when messages are processed. The OracleAS Integration B2B runtime repository is part of the Oracle Application Server Metadata Repository.
Save Definition button
Saves the contents of generated reports to XML files. You can reimport the report contents as needed into the OracleAS Integration B2B user interface.
secure multipurpose internet mail extensions
A secure method of sending e-mail. MIME indicates how to organize an electronic message. S/MIME describes how encryption data and a digital certificate can be included as part of the message body.
signing credential
Enables you to assign the certificate to use to sign the given document exchange.
trading partner
Engages in business transactions with another trading partner. You assign a trading partner to a trading partner agreement.
trading partner agreement
An electronic agreement that defines the way in which a host and remote trading partner agree to interact when performing an agreed-on collaboration or business action.
trading partner identification type
A type for which you assign a value that uniquely identifies a trading partner, such as a data universal numbering system (DUNS) number. You can define other types of trading partner identification types.
trading partner management
The design stage during which you define the basic B2B transaction. This includes setting up trading partners, assigning support for business protocols, creating business protocol operational and communication capabilities, and creating trading partner agreements.
transaction set
A collection of formatted data that contains the information required by a receiver to perform a standard business transaction. In an EDI standard, a transaction set has three sections (header, detail, and summary) and consists of a predefined group of segments in each section. An EDI transaction set maps to a document type of a business action in the OracleAS Integration B2B user interface.
transport
Defines the properties specific to a given usage of a protocol endpoint. The transport is responsible for message delivery using the selected transport protocol (such as HTTP 1.1), mode (synchronous or asynchronous), server, and protocol endpoint address (trading partner address, such as a URI).
UCCnet
An industry standard utility for item registration and data synchronization between suppliers and retailers. UCCnet was created to synchronize item data between suppliers and retailers. It is not-for-profit and a subsidiary of the Uniform Code Council.
use case groups
The privileges of the Administrator role assigned to a user of the OracleAS Integration B2B user interface.
user interface
The OracleAS Integration B2B tool that enables you to design, deploy, monitor, and manage configurations.
user role
The group of related use case groups (privileges) that permit a user to perform tasks with the OracleAS Integration B2B user interface.
validated configuration
A configuration state during which the partner data has been successfully validated to ensure that it is correct and complete and a configuration has been created. The configuration is ready for deployment. Only valid configurations can exist; invalid configurations cannot be created.
value-added networks
A private network provider (sometimes called a turnkey communications line) hired by a company to facilitate electronic data interchange (EDI) or provide other network services.
wallet password
Opens a user's wallet. A wallet is a container in which certificates and trusted certificates are stored and managed. These data structures securely store a user private key, a user certificate, and a set of trusted certificates.
wire messages
The native format of data sent from trading partners. OracleAS Integration B2B does not know this data format. The direction of wire messages coming from trading partners is called inbound. The direction of wire messages sent to trading partners is called outbound. Wire messages can contain a number of sections, such as payloads, attachments, or trailers.
