Preface

This guide is the primary source of introduction and usage information for Oracle Application Server Integration B2B.

This Preface contains these topics:

Intended Audience
Documentation Accessibility
Structure
Related Documents
Conventions

Intended Audience

Oracle Application Server Integration B2B User's Guide is intended for customers who want to perform the following tasks for integrations between enterprises.

Design
Deploy
Monitor
Manage

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure

This document contains:

Part I, "Introduction and Concepts"

This part provides OracleAS Integration B2B introduction and conceptual details.

Chapter 1, "Introduction to Oracle Application Server Integration B2B"

This chapter provides a conceptual overview of OracleAS Integration B2B.

Chapter 2, "Supported Protocols"

This chapter provides an overview of supported protocols.

Chapter 3, "Communicating with Host Trading Partner Applications"

This chapter describes how OracleAS Integration B2B communicates with the host application of the host trading partner.

Part II, "Introduction to the User Interface Tool"

This part introduces and provides a tutorial on how to use the OracleAS Integration B2B user interface tool.

Chapter 4, "Getting Started with the User Interface Tool"

This chapter describes how to get started with the OracleAS Integration B2B user interface tool. This chapter briefly describes the tasks to perform and the features available from each user interface tool tab.

Chapter 5, "OracleAS Integration B2B Tutorials"

This chapter provides a simple tutorial on how to use the OracleAS Integration B2B user interface tool to design and deploy an integration within an enterprise.

Part III, "Design-Time and Deployment Tasks"

This part describes how to design and deploy a configuration consisting of a trading partner agreement between trading partners with the OracleAS Integration B2B user interface tool.

Chapter 6, "Managing Business Protocols"

This chapter describes the tasks required to manage business protocols that you assign to remote trading partners. The host trading partner is automatically assigned all business protocols in OracleAS Integration B2B.

Chapter 7, "Creating Trading Partners"

This chapter describes how to use the Create Trading Partner wizard to create a remote trading partner, assign it a business protocol with operational and communication capabilities, and assign communication capabilities to the business protocol of the host trading partner. The host trading partner is automatically assigned all business protocols and operational capabilities.

Chapter 8, "Managing Trading Partners"

This chapter describes the tasks required to manage trading partners created with the Create Trading Partner wizard and their business protocol operational and communication capabilities.

Chapter 9, "Managing Callouts"

This chapter describes how to use callouts to transform documents from one form to another.

Chapter 10, "Creating and Managing Trading Partner Agreements"

This chapter describes the tasks required to create and manage a trading partner agreement between a host and remote trading partner. Both trading partners include a business protocol with operational and communication capabilities.

Chapter 11, "Creating and Deploying a Configuration"

This chapter describes how to create and deploy a configuration consisting of a trading partner agreement between two trading partners.

Part IV, "Administration, Monitoring, and Security Tasks"

This part describes how to administer OracleAS Integration B2B design-time and runtime data and create reports that monitor the status of a deployed configuration.

Chapter 12, "Administering Oracle Application Server Integration B2B"

This chapter describes how to administer OracleAS Integration B2B design-time and runtime data with the OracleAS Integration B2B user interface tool.

Chapter 13, "System Management with Oracle Enterprise Manager 10g"

This chapter provides an overview of Oracle Application Server Integration B2B monitoring and administration tasks that you can perform from Oracle Enterprise Manager 10g.

Chapter 14, "Creating Reports"

This chapter describes how to create OracleAS Integration B2B reports that monitor the status of a deployed configuration.

Chapter 15, "Oracle Application Server Integration B2B Security"

This chapter describes the architecture and configuration of security for Oracle Application Server Integration B2B.

Appendix A, "Troubleshooting and Workarounds"

This appendix describes Oracle Application Server Integration B2B troubleshooting methods.

Glossary

This glossary provides definitions of terms

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text
Conventions in Code Examples
Conventions for Windows Operating Systems

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
`UPPERCASE monospace (fixed-width) font`	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a `NUMBER` column. You can back up the database by using the `BACKUP` command. Query the `TABLE_NAME` column in the `USER_TABLES` data dictionary view. Use the `DBMS_STATS`.`GENERATE_STATS` procedure.
`lowercase monospace (fixed-width) font`	Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter `sqlplus` to start SQL*Plus. The password is specified in the `orapwd` file. Back up the datafiles and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_id` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user. The `JRepUtil` class implements these methods.
`lowercase italic monospace (fixed-width) font`	Lowercase italic monospace font represents placeholders or variables.	You can specify the `parallel_clause`. Run `old_release.SQL` where `old_release` refers to the release you installed before upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	DECIMAL (digits [ , precision ])
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	{ENABLE \| DISABLE}
\|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.	{ENABLE \| DISABLE} [COMPRESS \| NOCOMPRESS]
...	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees;
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.	SQL> SELECT NAME FROM V$DATAFILE; NAME ------------------------------------ /fsl/dbs/tbs_01.dbf /fs1/dbs/tbs_02.dbf . . . /fsl/dbs/tbs_09.dbf 9 rows selected.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.	`acctbal NUMBER(11,2);` `acct CONSTANT NUMBER(4) := 3;`
Italics	Italicized text indicates placeholders or variables for which you must supply particular values.	CONNECT SYSTEM/system_password DB_NAME = database_name
UPPERCASE	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees;
lowercase	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9;

Conventions for Windows Operating Systems

The following table describes conventions for Windows operating systems and provides examples of their use.

Convention	Meaning	Example
Choose Start >	How to start a program.	To start the Database Configuration Assistant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant.
File and directory names	File and directory names are not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (\|), and dash (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the file name begins with \\, then Windows assumes it uses the Universal Naming Convention.	c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32
`C:\>`	Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this manual.	C:\oracle\oradata>
Special characters	The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documentation for more information on escape and special characters.	C:\>exp scott/tiger TABLES=emp QUERY=\"WHERE job='SALESMAN' and sal<1600\" C:\>imp SYSTEM/password FROMUSER=scott TABLES=(emp, dept)
HOME_NAME	Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore.	C:\> net start OracleHOME_NAMETNSListener
`ORACLE_HOME` and `ORACLE_BASE`	In releases before Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a top level `ORACLE_HOME` directory. This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level `ORACLE_HOME` directory. There is a top level directory called `ORACLE_BASE` that by default is `C:\oracle`. If you install the latest Oracle release on a computer with no other Oracle software installed, then the default setting for the first Oracle home directory is `C:\oracle\orann`, where `nn` is the latest release number. The Oracle home directory is located directly under `ORACLE_BASE`. All directory path examples in this guide follow OFA conventions. Refer to Oracle Database Platform Guide for Windows for additional information about OFA compliances and for information about installing Oracle products in non-OFA compliant directories.	Go to the `ORACLE_BASE\ORACLE_HOME\rdbms\admin` directory.

Preface

Intended Audience

Documentation Accessibility

Structure

Related Documents

Conventions