Oracle Applications Interconnect Installation Guide
Release 3.1.3
Part Number A86040-01

Library
Product

Oracle ® Applications InterConnect

Release 3.1.3 Installation Guide

Part No. A86040-01

This guide explains the installation of Oracle Applications InterConnect Release 3.1.3. Please check that your system meets all the hardware and software prerequisites before starting the installation of these products.

Introduction

This guide explains the installation of Oracle Applications InterConnect Release 3.1.3.

How This Guide is Organized

There are a total of eight broad steps to install OAI and all its dependent components. The guide lists these steps one by one in the order you should follow them. Each step has a number of substeps. The guide is organized such that you can begin from page 1 and go to the end of the guide without having to jump around sections and have a fully installed working OAI system.

Notation

Throughout this documentation, <variable_name> refers to variables suppliedby the user. For example, <ORACLE_HOME> refers to the top-level directory used during Oracle software installation. $VARIABLE_NAME refers to system environment variables. The notation $ORACLE_HOME is reserved for the Oracle home directory on Unix platforms.

OAI and Dependent Component List

OAI is a hub'n'spoke end to end integration solution. The following is a list of components that need to be installed.

Note:

All of the following components can be found on the Oracle 8i Release 3 (8.1.7) CD. There is one Oracle 8i Release 3 (8.1.7) CD per platform. Currently OAI is supported on NT and Solaris. Use the NT or Solaris CD to install these components. Most of the installation steps are not platform specific. The ones that are, are clearly marked.

OAI Components

Dependent Products

Oracle Applications InterConnect Overview

Oracle Applications InterConnect is comprised of three major components:

iStudio

iStudio is a wizard-based tool used to specify and configure the integration. It enables you to model hierarchical data that represent business objects you are integrating between applications. It is used to specify data transformations, and supports publish/subscribe, request/reply, and point-point messaging paradigms.

Repository

The Repository stores iStudio-generated metadata, that encapsulates all the integration information.

Adapters

Adapters are software modules that plug into applications to make them Applications InterConnect enabled. Each adapter is a runtime component that manages all information flow between a particular application and OAI. Adapters may be specialized for use with applications.

Applications InterConnect includes four specialized adapters:

Two XML adapters are available--one for use with Oracle 8.1.5, and one for use with Oracle 8.1.6/8.1.7. For more detailed information please refer to the users guide.

Recommended Topology

There is absolutely no restriction on where each of the components listed above reside--it could range from all components on one machine to each component on its own dedicated machine. We, however, recommend the following topology:

Hardware Requirements

A CD-ROM drive to install Applications InterConnect, or the ability to access a CD-ROM drive over the network.

Note:

Do not run an install on a Solaris machine using Exceed on a remote machine. This can cause problems during install.

The Hub Machine (for OMB, OID, Repository, and database)

NT platform

Solaris platform

The Spoke Machine (for adapters)

Note:

The SAP adapter can only run on an NT machine

NT platform

Solaris platform

The iStudio/Management Console Machine

NT platform only

Software Requirements

JRE Requirements for Solaris

OAI works on JRE 1.1.8.

Note:

You do not need to install JRE or JDK 1.1.8 prior to OAI install. The OAI install bundles JRE 1.1.8 with it and will install it for you. The following is information on the Solaris patch required for proper functioning of Java programs.

(Reproduced from the README for JDK 1.1.8_10 for Solaris/SPARC)

Requirements

Solaris 2.5.1, Solaris 2.6 or Solaris 7 with at least the required patches from the table below installed. The patches in the table can be downloaded from http://www.sun.com/solaris/java or obtained from your service provider. The two digit number following the dash in each patch id is the revision of that patch. The table lists minimum revisions that this release was tested with; later revisions are acceptable.

Solaris 

required/Version Patch Id recommended 

Description 

2.5.1 

(5.5.1) 

103566-43 required X11/OpenWindows patch 

2.5.1 

(5.5.1) 

 103640-28 required Kernel patch 

2.5.1 

(5.5.1) 

103627-10 recommended Linker patch 

2.6 

(5.6) 

106040-11 required X Input & Output Method patch 

2.6 

(5.6) 

105181-15 recommended Kernel Update (socket close/hang) 

2.6 

(5.6) 

105284-25 recommended Motif Runtime Library patch 

2.6 

(5.6) 

105490-07 recommended Dynamic linker patch.5 

2.6 

(5.6) 

106409-01 recommended Chinese TrueType fonts patch (1) 

2.6 

(5.6) 

105633-30 recommended OpenWindows 3.6: Xsun Patch (1) 

2.6 

(5.6) 

105568-13 recommended Libthread Patch 

2.6 

(5.6) 

105210-19 recommended LibC Patch 

2.6 

(5.6) 

105669-07 recommended CDE 1.2: libDTSvc Patch (dtmail) 

7 

(5.7) 

107636-01 required X Input & Output Method patch 

7 

(5.7) 

106980-05 recommended Libthread Patch 

7 

(5.7) 

107607-01 recommended motif fontlist fontset libxm 

7 

(5.7) 

107078-10 recommended OpenWindows 3.6.1 Xsun Patch (1) 

Note:

(1) - recommended for locales which use traditional Chinese characters. In addition to the patches listed here, you may also want to install the latest patch cluster for your version of Solaris, which includes additional recommended and security patches. Solaris patch clusters are available for download on the Web; follow the appropriate links starting at http://sunsolve.sun.com.

Patch installation

Use the command 'showrev -p' to list the patches installed on your system. If the required/recommended patches are not already installed, follow the steps below:

  1. Extract the patch tar file that matches your version of Solaris (only onewill apply to a given system):

    Solaris 2.5.1: $ tar xvf 1.1.8_10_patches_sparc_5.5.1.tar

    Solaris 2.6: $ tar xvf 1.1.8_10_patches_sparc_5.6.tar

    Solaris 7: $ tar xvf 1.1.8_10_patches_sparc_5.7.tar

This will create a number of patch archives with names like <patch-id>.tar.Z.

  1. Uncompress and extract each of the patch archives that you wish to install:

    $ zcat <patch-id>.tar.Z | tar -xvf -A directory with a name like <patch-id> will be created for each patch. General instructions for patch installation are included in the Install.info file in the top-level directory of each patch. In addition, special installation instructions or post-installation requirements (such as a system reboot) appear in the README file included with each patch, along with a list ofbug ids fixed and files changed by that patch.

  2. Login to the system console as root.

  3. Place the system in single-user mode (this step is not required, but is recommended for patch installation):

    # shutdown

  4. Install the patches.

    Most patches can be installed using the commands below; however the Install.info and README files for each patch should be consulted. In the commands below, replace <your_patch_directory> with the path to the directory where the patches were extracted.

    Solaris 2.5.1 (repeat these steps for each patch):

    # cd <your_patch_directory>/<patch-id>

    # ./installpatch .

    Solaris 2.6 and Solaris 7:

    # patchadd -M <your_patch_directory> <patch-id> <patch-id> ...

  5. (6) Shutdown and reboot:

    # shutdown -i6

Installation

Overview

To successfully install Oracle Applications Interconnect and its dependent components, it is important to install the products in the order listed here:

Note:

Do not multi-select items when installing. Install components in the order listed below ONE by ONE.

  1. Oracle Internet Directory 2.1.1

    This should also install database 8.1.7 automatically.

  2. OMB 2.0.1.0

  3. Repository

  4. iStudio

  5. Adapters

  6. OAI Monitoring Console

Install Oracle Internet Directory 2.1.1

Refer to Oracle 8i Release 3 (8.1.7) Installation Guide on information on installing this component. OID can be found in the Management and Integration section of Oracle 8i Release 3 (8.1.7).

Note:

OID installation will install the database for you. Even though the install allows you to use an already installed database instance, DO NOT install OID on top of a pre-installed database.

Post OID Installation (OAI Specific Tasks)

Bring up the oidadmin tool (located in $ORACLE_HOME/bin)On the login screen, enter: After logging in: On the details page: On the dialog: Repeat the above steps for Content Access Item list When done, click Apply

How OAI Utilizes OID

All OAI components (repository, adapters, iStudio, console) and OMB communicate to each other using CORBA. To find each other, they need a location service. OID provides that location service. These components use OID for storing and accessing CORBA object references.

In particular, both the repository and OMB store their CORBA object references in OID in a predefined place (configured through OAI and OMB installs). The adapters look up OID in the same predefined place to access both OMB and repository connection information. And, iStudio looks up OID to access repository connection information.

Install Oracle Message Broker (OMB) 2.0.1.0

Before you start installing OMB, make sure that the following components are in their desired state:
    1. Database is started.

    2. TNS listener is stopped.

    3. OID Monitor process is stopped.

    4. OID LDAP process is stopped.

Locate OMB in the install program

In the Oracle Universal Installer program, in the "Available Products" screen, select Oracle 8i Management and Integration 8.1.7.

Now you will see four choices for Installation Types. Select Custom.

Note:

Do not select Oracle Integration Server even though it lists OMB as one of its components. The OMB version that works with OAI can be found under the Custom selection.

You will now see a product hierarchy starting with Oracle 8i Management and Integration as the first element. Deselect all elements immediately under this node except for Oracle integration Server 8.1.7.

Note:

You should deselect Oracle Workflow and Oracle Partitioning before you deselect Oracle 8i Server. Otherwise, you will not be able to deselect Oracle 8i Server.

Note:

Advanced Security feature is selected automatically when OMB is selected. This is ok.Now, refer to the Oracle Message Broker 2.0.1.0 Installation Guide for instructions.

OAI-Specific Tasks During OMB Installation

If you are installing OMB specifically for OAI, specify the values listed below for these specific steps during installation.

On the Suffix screen: Note:

Be sure to write down the values you supply in this step on paper. You will need to supply them later during OAI installation.On the LDAP Information screen:

Note:

This is not the DHCP name. The default is the host name determined by the installer. If it is a DHCP name, you MUST change it to the computer name.

Note:

Be sure to write down the values you supply in this step on paper. You will need to supply them later during OAI installation.

On the Authentication Methods screen: On the Summary screen:

OAI-Specific Tasks During Post-Installation

Note:

Please make sure that OID and the TNS listener are started. Refer to the OMB Installation Guide (Post Installation Tasks chapter) for more detail.

If you installed OMB specifically for OAI, specify the values listed below for these specific steps during post-installation.During the "Directory Configuration" post installation step:

For the "update the directory schema using the LDAPSchema command" step use the following command line options:

For the "modify the directory for OMB suffix with the InitDir command" step use the following command line options: Perform the Oracle Advanced Queueing Configuration step.

For the "Configure database parameters" step provide the following values:

Do not perform any other optional steps--MQSeries, TIBCO, Async Component Invocation, or AQLite.

After the post installation step are done, you need to initialize OMB so that topics and queues can be installed later.

Start ombadmin tool. On the login screen:

Do not modify any of the fields on the login screen.

On the main screen: In the wizard...

On the welcome screen:

On the Create a new or select an existing OMB instance screen: On the Create a new OMB instance screen:

You will need to provide this information duing OAI installation.

On the Create Message Broker screen: On the Select Servers and Drivers to Add screen: On the Create an Oracle AQ Server screen: On the Create an Oracle AQ Driver 1 of 2 screen: On the Create an Oracle AQ Driver 2 of 2 screen: On the Create an Oracle AQ Connection Factory screen:

Starting the Broker

On Solaris:

On NT:

How OAI Utilizes OMB

OMB is the store and forward unit for messages and acts as the messaging hub in the OAI hub'n'spoke architecture. OAI adapters use Java Message Service (JMS), provided by Oracle Message Broker, for sending and receiving messages. Please refer to OMB's user guide for more details.

At this point all dependent products have been installed. Now we need to install OAI components.

Where do you find the OAI components

OAI can be installed from the Oracle 8i Release 3 (8.1.7) NT or Solaris CD. Here are the general steps to navigate the CD to reach OAI components:

On the Welcome screen:

On the File Locations screen:

On the Available Products screen:

On the Installation Types screen:

On the Available Product Components screen:

Note:

If you don't click them in the order listed, you may not be able to deselect the Oracle 8i Server.

Now you're ready to install OAI components.

Install OAI Repository

Please follow the steps outlined in "Where do you find the OAI components" before performing the following steps

Note:

Before installing the repository, please make sure that the hub database (installed through OID) is up and running. For details on how this database is used by the repository, please see "Repository Architecture Details", .On the Available Product Components screen:

On the Application Interconnect Repository screen:

Before proceeding to the next step, please review "Repository Architecture Details", if you are unfamiliar with what the repository is. This is relevant to the install.

On the Repository Configuration screen, provide the following information: Note:

This is not the DHCP name. The default is the host name determined by the installer. If it is a DHCP name, you should change it to the computer name. Be sure to write the repository name and host name on a piece of paper. You will need to supply this information during adapter installation.

On the Database Configuration screen:

Note:

This is the database which the repository Java program connects to. Please read "Repository Architecture Details", for more information.

On the Oracle Internet Directory Configuration screen:

Note:

You will need the piece of paper where you noted down OID specific information during OMB install (Refer to Step 2.4 and 2.5).

Note:

All this information is utilized by the repository to locate the OID instance in the hub so that it can put it's CORBA identification information (IOR) in OID to be used by iStudio and adapters to connect to it.

On the Summary screen:

Where is the Repository installed

\[ORACLE_HOME]\OAIRepository31\[your repository name]

Repository Architecture Details

The repository consists of two components:

  1. A Java API layer sitting OUTSIDE the database as a standalone Java Application.

  2. A database with repository schema that the Java API layer communicates to using JDBC to store and retrieve metadata.

Note:

In the install program and this installation document, all references to "repository" should be considered references to the Java API layer (item 1 above). All references to "repository database" should be considered references to item 2 above.

Note:

All OAI components talk to the Java layer and not directly to the database.

Note:

The database instance used for the repository is typically the same one used by OMB and OID. You don't need a separate physical database or even another instance for the repository. The repository install creates a user and all its schema is contained within that user in the database.

The repository is used to store integration information as metadata. iStudio connects to the repository at design time and pushes the mapping information modeled into the repository. At runtime, the adapters access the repository and use the metadata as runtime instructions for doing transformations and other functionality.

Install iStudio

Please follow the steps outlined in "Where do you find the OAI components" before performing the following steps.

On the Available Product Components screen: On the iStudio Installation screen:

On the Oracle Internet Directory Configuration screen:

Note:

During this step, refer to the information you wrote down regarding OID specific information during OMB install (Refer to Step 2.4 and 2.5).

Note:

This information is used by iStudio to locate the OID instance in the hub so it can pull the repository's CORBA identification information (IOR) from OID. With that information, iStudio can connect to the repository.

On the Summary screen:

Where is iStudio installed

\[ORACLE_HOME]\OAIIstudio31

Create or Install Integration Metadata

All integration logic is captured in metadata modeled through iStudio. You have two choices:

  1. Use pre-packaged metadata. Oracle has pre-packaged metadata packs for certain integration scenarios. The specific metadata pack to be installed depends upon the applications in your integration scenario. These metadata packs come with their own installation instructions. For example, if you're integrating Oracle Internet Procurement with SAP, read the Implementation Guide for Oracle Internet Procurement InterConnect for SAP R/3. These instructions will tell you how to populate the repository with metadata.

  2. Create the metadata from scratch in iStudio. If there is no pre-packaged metadata for your integration scenario, you must create the metadata using iStudio. Please refer to the iStudio chapter in the user guide for more details on how to do this.

Regardless of whether you used method 1 or 2 to model your integration, you need to start up iStudio for the following tasks:

Note:

For instructions on starting iStudio, please refer to "How To Start and Stop OAI Components", near the end of this guide. Note down what the application names are on paper.

Provide information on what queues and topics messages will go into or come out of the hub. Note:

In iStudio, multi consumer queue corresponds to topic; single consumer queue corresponds to queue.

You will need to note down all queues and topics that need to be configured under AQ for the next step.

Create JMS Queues and Topics under OMB

Start ombadmin tool.

From the Tool menu:

Note:

In iStudio, multi consumer queue corresponds to topic; single consumer queue corresponds to queue.

For each topic or queue, you must go through the wizard and create it.

Queue Wizard

On the Welcome screen: On the Use an Existing OMB Instance screen: On the Use an Existing Server screen: On the Create an Oracle AQ Queue screen: On the Successful Queue Creation screen:

Topic Wizard

On the Welcome screen: On the Use an Existing OMB Instance screen: On the Use an Existing Server screen: On the Create an Oracle AQ Topic 1 of 2 screen: On the Create an Oracle AQ Topic 2 of 2 screen: On the Successful Topic Creation screen:

Install Adapters

There are several adapters that come packaged with OAI. They are as follows:

  1. CRM 11i Adapter--This is an XML AQ adapter specifically designed for Oracle CRM 11i apps (Oracle 8.1.6 or higher).

  2. DB Adapter--This is an Oracle database adapter that can be used for a non-AQ based integration.

  3. SAP Adapter--This is used to connect to SAP via RFC. You can make BAPI invocations into SAP and send both inbound and outbound IDOCs.

  4. XML AQ Adapter for Oracle 8.1.5--This adapter will pick up messages in XML from an AQ or put messages in XML in an AQ. This adapter is specifically for Oracle 8.1.5.

  5. XML AQ Adapter for Oracle 8.1.6 and higher--Like the 8.1.5 XML AQ adapter but works with 8.1.6 and higher versions of the database. This is used by Oracle iProcurement to integrate to 3rd party applications. It is generic enough to be utilized by any application that wants to send or receive messages in AQ in XML format. (There is no iProcurement specific features in this adapter.)

Please follow the steps outlined in "Where do you find the OAI components" before proceeding to install a specific adapter.

Install CRM 11i Adapter

On the Available Product Components screen: On the Welcome to the Adapter Installation screen: On the Application Identification screen: On the OMB Configuration screen:

On the Repository Configuration screen:

Note:

You will need the piece of paper on which you noted this information down during repository install (Step 3.3).

On the Oracle Internet Directory Configuration screen:

Note:

You will need the piece of paper where you noted down OID specific information during OMB install (Step 2.4 and 2.5).

Note:

All this information is utilized by the adapter to locate the OID instance in the hub so that it can pull the repository's and OMB's CORBA identification information (IOR) from OID. With that information, the adapter can connect to the repository and OMB.

On the AQ Database Configuration screen:

Note:

This is the database on the application side from which the adapter will either put or get messages from AQs. This is NOT the information for the hub database.

On the Summary screen:

Where is the CRM Adapter installed

\[ORACLE_HOME]\OAICRMAdapter31\[AppType][Partition]

Install DB Adapter

Note:

You can install the DB Adapter on Oracle 7.3.x or 8.0.x or 8i databases. All other components of Applications InterConnect require Oracle 8i.On the Available Product Components screen:

On the Welcome to the Adapter Installation screen: On the Application Identification screen: On the OMB Configuration screen:

On the Repository Configuration screen:

Note:

You will need the piece of paper on which you noted this information down during repository install (refer to Step 3.3).

On the Oracle Internet Directory Configuration screen:

Note:

You will need the piece of paper where you noted down OID specific information during OMB installation (Step 2.4 and 2.5.)

Note:

All this information is utilized by the adapter to locate the OID instance in the hub so that it can pull the repository's and OMB's CORBA identification information (IOR) from OID. With that information, the adapter can connect to the repository and OMB.

On the Application Database Connection Configuration screen:

Note:

This information is regarding the application database that this adapter will connect to, NOT the hub database.

On the Application Database User Configuration screen:

Note:

This information is utilized to figure out where will the stored procedures generated through iStudio be installed for application inbound messages. At runtime, the db adapter will utilize this information to call user specified stored procedures. This can be a existing user.

You may, but are not required to create a separate OAI user.

On the After Installation screen: On the Summary screen:

Where is the DB Adapter installed

\[ORACLE_HOME]\OAIDBAdapter31\[AppType][partition]

Post Installation Steps for DB Adapter

Go to the directory that the db adapter is installed in. Using sqlplus, connect to the application database that this adapter will connect to. Run SQL script agent1.sql (by typing "@agent1.sql" on the sqlplus command line).Connect to the database with username--"oai" and password--"oai".Run SQL script agent2.sql (by typing "@agent2.sql" on the sqlplus command line).Exit sqlplus.

Install SAP Adapter

On the Available Product Components screen: On the Welcome to the Adapter Installation screen: On the Application Identification screen: On the OMB Configuration screen:

On the Repository Configuration screen:

Note:

You will need the piece of paper on which you noted this information down during repository install (Refer to Step 3.3).

On the Oracle Internet Directory Configuration screen:

Note:

You will need the piece of paper where you noted down OID specific information during OMB install (Refer to Step 2.4 and 2.5).

Note:

All this information is utilized by the adapter to locate the OID instance in the hub so that it can pull the repository's and OMB's CORBA identification information (IOR) in OID. With that information, the adapter can connect to the repository and OMB.

On the SAP Configuration screen: On the SAP Credentials screen: On the Message Types screen: Note:

Depending upon what you select, you might or might not see some of the screens listed below.

On the IDOC Destination Configuration screen:

Type the IDOC Destination. This question will be asked only if the SAP Adapter will be sending or receiving IDocs.The IDoc Destination is the program id of a valid RFC destination in SAP which SAP will use to send IDocs to the SAP Adapter or receive IDocs from the SAP Adapter. See the seciton titled "Common Questions about the SAP Adapter" for details on how to configure a valid RFC destination in SAP.

On the Sender Partner Configuration screen:

This screen will show up only if the SAP Adapter will be sending IDocs into SAP.

Configure this information about the partner which is sending the IDocs into SAP.

On the Recipient Partner Configuration screen:

This screen will show up only if the SAP Adapter will be sending IDocs into SAP.

Configure this information about the partner in SAP which is receiving the IDocs.

On the Summary screen:

Where is the SAP adapter installed

\[ORACLE_HOME]\OAISAPAdapter31\[AppType][Partition]

Post Installation Steps

After installing the SAP adapter, make sure the file librfc32.dll is in the system path variable. librfc32.dll is distributed with the SAP system this adapter will connect to. We recommend you install the dll in the\[ORACLE_HOME]\OracleSAPBridge31\bin directory.

Note:

OAI does NOT provide this dll.You must export one file from SAP which contains information about the IDoc structure of all the IDocs which the SAP Adapter will be using. This file should have the same information which you used to import the IDoc in iStudio. The file must be named ALL.<segment release version>. <SAP version>

Copy the file into your SAP Adapter's directory.Edit the IDocRepositoryFile entry in the sap.ini file. If you've purchased OAI as part of a Pack, check to see if the Pack comes with an IDoc file and for more details on how to use the file.

Common Questions about the SAP Adapter

How do I create a valid RFC Destination in SAP?:

Log on to SAP as the same user that you specified during the SAP Adapter install using the SAP Frontend. Call SAP transaction SM59 or go to Tools->Administration->Administration->Network->RFC destinations.

Hit F8 or the Create button. Type in any name for your RFCdestination, specify T for connection, enter some description, check the "Current User" option and push the save button or type Ctrl-s.

On the next screen choose Registration as the Activation type and type in something for program id. SAP recommends entering something like [hostname].[some program or organization identifier]. Remember what you type in for program id because this is what should specify for IDoc Destination during the SAP Adapter install (or what you should specify for IDocDestination in the sap.ini file.)

Is it possible to edit the SAP configuration settings after the initial configuration?:

Yes, simply edit $ORACLE_HOME/OAISapAdapter31/[AppType][Partition]/sap.ini.

Listed below are the parameters and their corresponding question in the install:

These parameters are not part of the installation:

Install XML AQ Adapter for 8.1.5

The steps are exactly the same as the ones for CRM 11i Adapter installation.

Install XML AQ Adapter for 8.1.6/8.1.7

The steps are exactly the same as the ones for CRM 11i Adapter installation.

Adapter Details

Adapters are components that are attached to applications to OAI enable them. The adapter has the following defining characteristics:

Note:

If you're using pre-packaged metadata, after importing it into the repository (see below), you will need to start up iStudio to find the corresponding application name (under Apps folder in iStudio) to utilize as the Application Type for the adapter you are installing.

Install Management Console

Please follow the steps outlined in "Where do you find the OAI components" before proceeding.

On the Available Product Components screen: On the Welcome screen:

On the Oracle Internet Directory Configuration screen:

Note:

You will need the piece of paper where you noted down OID specific information during OMB install (Refer to Step 2.4 and 2.5).

On the Error DB Configuration screen:

Note:

All runtime errors get logged to this database. You need to supply this information so that through the Management Console, you can browse the error database. The error database IS THE SAME as the repository database.

Note:

Refer to Steps 3.3 and 3.4.

On the Summary screen:

Where is the Management Console installed

\[ORACLE_HOME]\OAIManagementConsole31

Management Console Overview

Oracle Applications InterConnect console is a centralized tool to administer the Applications InterConnect runtime components, specifically the repository and each adapter. Using the Management Console, the administrator can start, stop, monitor and troubleshoot the Applications InterConnect runtime.

Optional Install Adapter SDK

If you want to create new adapters instead of using pre-existing ones that come bundled with OAI, you must install the adapter SDK and read the documentation contained therein. To install the SDK, do the following steps:

Please follow the steps outlined in "Where do you find the OAI components" before proceeding.

On the Available Product Components screen: On the Summary screen:

Where is the Adapter SDK installed

\[ORACLE_HOME]\OAIAdapterSDK31

How To Start and Stop OAI Components

Starting the Repository on NT

  1. Start the hub database and OID.

  2. Click Start in the Windows NT panel.

  3. Select Settings.

  4. Click Control Panel.

  5. Select the Services icon.

  6. Select the service OracleOAIRepository_[reponame].

  7. Click Start.

Stopping the Repository on NT

  1. Click Start in the Windows NT panel.

  2. Select Settings.

  3. Click Control Panel.

  4. Select the Services icon.

  5. Select the service OracleOAIRepository_[reponame].

  6. Click Stop.

Starting the Repository on Solaris

  1. Start the hub database and OID.

  2. Go to $ORACLE_HOME/OAIRepository31/<RepoName>.

  3. Run repoStart.

Stopping the Repository on Solaris

  1. Go to $ORACLE_HOME/OAIRepository31/<RepoName>

  2. Run repoStop.

Starting iStudio on NT

  1. Start the hub database and OID.

  2. Start the Repository.

  3. Click Start in the Windows NT panel.

  4. Select Programs.

  5. Select Oracle Applications InterConnect.

  6. Click iStudio.

Stopping iStudio on NT

  1. Exit the iStudio program.

Starting the Adapters on NT

  1. Start the hub database and OID.

  2. Start OMB.

  3. Start the Repository.

  4. Click Start in the Windows NT panel.

  5. Select Settings.

  6. Click Control Panel.

  7. Select the Services icon.

  8. Select the service OracleOAIAdapter_[AppType][Partition].

  9. Click Start.

Stopping the Adapters on NT

  1. Click Start in the Windows NT panel.

  2. Select Settings.

  3. Click Control Panel.

  4. Select the Services icon.

  5. Select the service OracleOAIAdapter_[AppType][Partition].

  6. Click Stop.

Starting the Adapters on Solaris

  1. Start the hub database and OID.

  2. Start OMB.

  3. Start the Repository.

  4. Go to $ORACLE_HOME/OAIDBAdapter31/<adapterName>

  5. Run run adapter.

Stopping the Adapters on Solaris

  1. Hit Ctrl-C.

Note:

This medthod of stopping the adapter will be improved in the next version.

Starting the Management Console on NT

  1. Click Start in the Windows NT panel.

  2. Select Programs.

  3. Select Oracle Applications InterConnect.

  4. Click Management Console.

Stopping the Management Console on NT

  1. Exit the Management Console program.

Oracle
Copyright © 1996-2000 Oracle Corporation.
All Rights Reserved.

Library
Product