Preface

This guide is the primary source of introduction, installation, configuration, and usage information for Oracle Application Server ProcessConnect.

This preface contains these topics:

Audience

Oracle Application Server ProcessConnect User's Guide is intended for customers who want to design, deploy, monitor, and manage integrations within an enterprise and integrations between enterprises.

Organization

This document contains:

Part I, "Oracle Application Server ProcessConnect Introduction and Concepts"

Chapter 1, "A Road Map to Using this Guide"

This chapter provides a road map to using this guide for each type of Oracle Application Server ProcessConnect user.

Chapter 2, "Introduction to Oracle Application Server ProcessConnect"

This chapter defines e-business and integration challenges, and describes how Oracle Application Server ProcessConnect answers integration challenges.

Chapter 3, "Oracle Application Server ProcessConnect Concepts"

This chapter provides a conceptual overview of Oracle Application Server ProcessConnect.

Chapter 4, "Oracle Application Server ProcessConnect Architecture"

This chapter provides a high-level overview of the capabilities provided by the Oracle Application Server ProcessConnect architecture.

Part II, "Introduction to the User Interface Tool"

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

This chapter describes how to get started with the Oracle Application Server ProcessConnect user interface tool. This chapter also briefly describes the tasks you can perform and the features available from each user interface tool tab.

Chapter 6, "Methodologies for Using Oracle Application Server ProcessConnect"

This chapter describes several methodologies for using the Oracle Application Server ProcessConnect user interface tool to design and deploy integrations.

Chapter 7, "Tutorial of an Integration within an Enterprise"

This chapter provides a simple tutorial on how to use the Oracle Application Server ProcessConnect user interface tool to design and deploy an integration within an enterprise.

Part III, "Modeler Management Tasks"

Chapter 8, "Oracle Application Server ProcessConnect Technology Adapters"

This chapter provides details about the technology adapters included with Oracle Application Server ProcessConnect.

Chapter 9, "Creating Metadata with the Modeling Wizards"

This chapter describes how to create integration modeling metadata with the assistance of the Oracle Application Server ProcessConnect modeling wizards.

Chapter 10, "Managing Datatypes"

This chapter describes the datatype management tasks required to design an integration.

Chapter 11, "Managing Adapter Interactions and Event Types"

This chapter describes the adapter interaction and event type management tasks required to design an integration.

Chapter 12, "Managing Business Processes and Roles"

This chapter describes the business process and role management tasks required to design an integration.

Chapter 13, "Managing Transformations"

This chapter describes transformation concepts and management tasks for designing an integration.

Chapter 14, "Advanced Transformations Design"

This chapter describes how to design advanced transformations. Common transformation errors and transformation limitations are also described.

Part IV, "Administrator Management Tasks"

Chapter 15, "Managing Applications and Application Agreements"

This chapter describes the application and application agreement tasks required to design an integration within an enterprise.

Chapter 16, "Creating and Deploying a Configuration"

This chapter describes how to create and deploy a configuration of an end-to-end integration that consists of the modeling metadata and profile data you created.

Chapter 17, "Administering Integrations with the User Interface Tool"

This chapter describes how to administer Oracle Application Server ProcessConnect with the Oracle Application Server ProcessConnect user interface tool.

Chapter 18, "System Management with Oracle Enterprise Manager"

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

Chapter 19, "Performance Tuning"

This chapter describes how you can manage the performance of components of the Oracle Application Server ProcessConnect runtime engine.

Chapter 20, "Oracle Application Server ProcessConnect Security"

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

Chapter 21, "Oracle Application Server ProcessConnect Error Handling"

This chapter describes how to detect and handle system and domain errors in Oracle Application Server ProcessConnect runtime components.

Chapter 22, "Oracle Application Server ProcessConnect Troubleshooting"

This chapter describes Oracle Application Server ProcessConnect troubleshooting methodologies.

Part V, "Analyst Management Tasks"

Chapter 23, "Creating Reports"

This chapter describes how to create Oracle Application Server ProcessConnect reports.

Part VI, "RosettaNet Solutions"

Chapter 24, "RosettaNet B2B Protocol Standard"

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.

Chapter 25, "Managing Host and Remote Trading Partner Capabilities"

This chapter describes the host and remote trading partner identification, organization, cooperation, delivery, security, and endpoint capability tasks required to design an integration between enterprises. The host trading partner uses the Oracle Application Server ProcessConnect user interface tool to define the capabilities for all trading partners (both host and remote). The host trading partner consults with the remote trading partner to obtain the necessary details.

Chapter 26, "Managing Trading Partners and Trading Partners Agreements"

This chapter describes the trading partner and trading partner agreement tasks required to design an integration between enterprises.

Part VII, "Reference"

Appendix A, "Native Formats and Translators"

This appendix describes the native formats and translators supported with Oracle Application Server ProcessConnect.

Appendix B, "Transformation Rules"

This appendix describes the datatype transformation map rules, event header rules, and domain value map rules included with Oracle Application Server ProcessConnect.

Appendix C, "Error Codes"

This appendix describes Oracle Application Server ProcessConnect error messages.

Appendix D, "Jacada Integrator Adapter for Legacy Systems"

With Jacada Integrator®, Oracle Application Server ProcessConnect customers can integrate legacy applications when prebuilt APIs or legacy application source code is not available.

Glossary

Conventions

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

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.	Oracle9i 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 open 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 `U``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.
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 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 Microsoft Windows Operating Systems

The following table describes conventions for Microsoft 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>`
	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 Oracle``HOME_NAME``TNSListener`

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 Corporation 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.