Skip Headers

Oracle® Application Server Integration InterConnect Installation Guide 10g Release 2 (10.1.2) B14070-02 |
| Contents | Index

Previous | Next |

# 1 Overview

This chapter describes how to install Oracle Application Server Integration InterConnect (OracleAS Integration InterConnect). It contains the following topics:

- OracleAS Integration InterConnect Overview

- OracleAS Integration InterConnect Installation Types

- Dependent Products

- Deployment Topology

- OracleAS Integration InterConnect System Requirements

## OracleAS Integration InterConnect Overview

This section explains terminology used in this guide:

Design Time The phase of integration development where you model the integration scenario. The modelled information is stored as metadata. The following components are required for modeling your integration:

- iStudio

- Repository

- Hub Database

- Oracle Workflow Builder (required only if your scenario has business process modeling)

Run Time At run time, the metadata gathered at design time is used to carry out integration. The following components are required for run time:

- Adapters

- Repository

- Hub Database

- Oracle Workflow (required only if your scenario has business process modeling)

- Oracle Workflow Communication (required only if your scenario has business process modeling)

- Oracle InterConnect Manager

Hub and Spoke The physical architectural approach for integration used by OracleAS Integration InterConnect is called the hub and spoke arrangement. In this approach, all applications (spokes) are connected through a central server (hub), as illustrated in Figure 1-1.

Figure 1-1 Hub and Spoke Architecture

Description of "Figure 1-1 Hub and Spoke Architecture"

The OracleAS Integration InterConnect has the following components:

- iStudio

- Repository

- Hub Database

- Adapters

- Oracle Workflow Builder

- Oracle Workflow Communication

- Oracle Workflow

- Oracle InterConnect Manager

- OracleAS Integration InterConnect Development Kit

iStudio The tool used at design time to define the integration. iStudio is a design-time integration specification tool used to help business analysts specify the integration logic at a functional level, instead of a technical coding level. iStudio exposes the integration methodology using simple wizards and reduces or eliminates the need for writing code to specify the integration logic. This reduces the total time required to complete an integration.

Repository This is a middle tier repository server, java process, that communicates with the repository schema in the hub database to store and retrieve metadata. At design time, this server is used to store metadata in the hub database. At run time, adapters can access the metadata through the repository.

Hub Database The hub database has three uses:

- Store Metadata: The repository schema contains all the metadata modeled at design time through iStudio.

- Store and Forward Messages: At run time, all messages enter and leave the OracleAS Integration InterConnect hub AQ queues.

- Store Tracking and Error Information: At run time, all message tracking and error information is stored in the repository schema.

Adapters Adapters are the run time engines that carry out the integration based on the metadata modeled during design time.

Oracle Workflow Builder This component is used to model a business process at design time.

Oracle Workflow Communication This component is used to communicate between OracleAS Integration InterConnect hub and Oracle Workflow at run time.

Oracle Workflow The collection of Workflow design time (Oracle Workflow Builder) and run time components.

Oracle InterConnect Manager Oracle InterConnect Manager (IC Manager), this command-line tool is used for monitoring OracleAS Integration InterConnect at run time.

OracleAS Integration InterConnect Development Kit This contains iStudio and adapter SDKs that enable you to extend OracleAS Integration InterConnect.

See Also: Oracle Application Server Integration InterConnect User's Guide

## OracleAS Integration InterConnect Installation Types

OracleAS Integration InterConnect installation types are presented in Table 1-1. You can choose the installation types on the Select Installation Type screen during installation.

Table 1-1 OracleAS Integration InterConnect Installation Types

Installation Type | Description
--- | ---
Hub | Installs the OracleAS Integration InterConnect Repository, Oracle Workflow Communication, and Oracle Workflow Server.
Adapter | Installs OracleAS Integration InterConnect Adapters.
Development Kit | Installs iStudio (Windows only), OracleAS Integration InterConnect Development Kit, and Oracle Workflow Builder (Windows only).

## Dependent Products

You can use an Oracle Database 10g as the hub database to run OracleAS Integration InterConnect. Alternatively, you can also use a OracleAS Infrastructure database or a Oracle Standalone 9.2.0.x database.

Note: The 10g DB import and export scripts are not compatible with the 9.2 DB, so if you wish to import or export the `ichub` schema from a 9.2 database, port the scripts to the 9.2 Oracle home. Copy the SQL scripts from the `$INTERCONNECT_HOME/repository/sql` directory to the destination directory. Please ensure the Oracle home values of the `oaiimport` and `oaiexport` scripts are changed to the new values.

## Deployment Topology

The commonly used deployment topologies are as follows:

- All OracleAS Integration InterConnect run time components on one computer and iStudio on a separate development computer, as illustrated in Figure 1-2.

Figure 1-2 OracleAS Integration InterConnect Components on One Computer

Description of "Figure 1-2 OracleAS Integration InterConnect Components on One Computer"

- All hub components on one computer, all spoke components on separate computers, and iStudio on a separate development computer, as illustrated in Figure 1-3. In this case, there is a dedicated computer for the hub components. Adapters either have dedicated separate computers or are co-located with the applications they are connected to.

Figure 1-3 OracleAS Integration InterConnect Run-Time Components on Different Computers

Description of "Figure 1-3 OracleAS Integration InterConnect Run-Time Components on Different Computers"

The OracleAS Integration InterConnect hub can exist on the same, or a different computer as the hub database.

## OracleAS Integration InterConnect System Requirements

The following sections describe the OracleAS Integration InterConnect system requirements:

- Hardware Requirements

- Software Requirements

### Hardware Requirements

This section contains hardware requirements for the following:

- Hub

- Adapters

- Development Kit

#### Hub

For hub, the computer should meet the minimum requirements listed in Table 1-2.

Table 1-2 Hardware Requirements for Hub Computer

Hardware | UNIX | Windows
--- | --- | ---
CD-ROM Device | A CD-ROM drive to install, or the ability to access a CD-ROM device over the network. | A CD-ROM drive to install, or the ability to access a CD-ROM device over the network.
Disk Space | 1 GB | 1 GB
Memory | 512 MB | 512 MB

Note: Do not use Hummingbird Exceed to perform the installation remotely on a UNIX computer, as that can cause problems during installation.

#### Adapters

For adapters, the computer should meet the minimum requirements listed in Table 1-3.

Table 1-3 Hardware Requirements for Adapters

Hardware | UNIX | Windows
--- | --- | ---
Disk Space | 400 MB | 400 MB
Memory | 512 MB | 512 MB

#### Development Kit

For Development Kit, the computer should meet the minimum requirements listed in Table 1-4.

Table 1-4 Hardware Requirements for Development Kit

Hardware | UNIX (Solaris Only) | Windows
--- | --- | ---
Disk Space | 512 MB | 500 MB
Memory | 256 MB | 512 MB

See Also: Oracle Workflow Administrator's Guide

### Software Requirements

This section contains the software requirements for the following:

- Operating System Requirements

- JRE Requirements

- Operating System Patches

Operating System Requirements

Table 1-5 lists the operating system requirements for the computer on which hub and spoke will be installed.

Table 1-5 Operating System Requirements

Operating System | Version
--- | ---
HP Tru64 | HP Tru64 UNIX (Alpha) 5.1b
HP-UX | HP-UX (PA-RISC) 11.11, 11.23
IBM AIX | AIX (POWER) version 5.2
Linux (x86) | Red Hat Enterprise Linux 2.1, 3.0 SuSE SLES8, SLES9
Sun SPARC Solaris | Sun SPARC Solaris 2.8 and 2.9
Microsoft Windows | Windows XP Professional, Windows 2000 (SP3 or higher)

JRE Requirements

OracleAS Integration InterConnect runs on Java Runtime Environment (JRE) 1.4. JRE is bundled with OracleAS Integration InterConnect on Sun SPARC Solaris, Linux, and Windows. When you install OracleAS Integration InterConnect on these platforms, JRE is automatically installed for you.

Operating System Patches

The operating system patches can be found at OracleMetaLink:

`http://metalink.oracle.com`