Oracle Applications InterConnect Installation Guide Release 4.0.0 for Windows NT and UNIX Part Number A87478-01 |
|
This chapter describes the following steps to install Oracle Applications InterConnect:
To install Oracle Applications Interconnect (OAI) and its dependent components, install the products in the following order:
Perform one of the following steps to install OID:
or
For information about installing OID 2.0.6, see the Oracle8i Release 2 (8.1.6) Installation Guide for you UNIX platform. For information about installing OID 2.1.1, see the Oracle8i Release 3 (8.1.7) Installation Guide for you UNIX platform.
Installing OID installs the database for you. Even though the installation allows you to use an already installed database instance, do not install OID on top of a pre-installed database.
oidadmin
tool (located in $ORACLE_HOME/bin
).
The login window appears.
Field | Value |
---|---|
|
|
|
welcome |
|
Computer name where OID is installed |
|
Port that OID uses. Use the default. Do not change the value. |
SSL Enabled |
Do not select |
login
.
The Login window appears.
Access Control Manager
.
Select Default ACP
.
The Details window appears.
Structural Access Item
list.
Select edit
.
A dialog window appears.
Access Rights
tab.
Select Grant permission
for all items.
Select OK
.
Apply
.
oidadmin
tool.
All OAI components (Repository, Adapters, iStudio, and Management Infrastructure) and OMB communicate to each other using CORBA. OID provides the location service for the components to find each other. The components use OID for storing and accessing CORBA object references.
Both the repository and OMB store their CORBA object references (IOR) in OID in a predefined place (configured through OAI and OMB installations). The adapters look up OID in the same predefined place to access both OMB and repository connection information. The iStudio product looks up OID to access repository connection information.
Perform one of the following sections to install OMB:
or
Perform the following steps to install OMB 2.0.0.1:
Perform the following steps to install OMB 2.0.1.0:
Available Products
window of the Oracle Universal Installer program.
Oracle 8i Management and Integration 8.1.7
.
Custom
installation type.
Do not select Oracle Integration Server
even though it lists OMB
as one of its components.
A product hierarchy (starting with Oracle 8i Management and Integration
) appears.
Oracle integration Server 8.1.7
.
Deselect Oracle Workflow
and Oracle Partitioning
before you deselect Oracle8i Server
. Otherwise, you will not be able to deselect Oracle8i Server
.
Oracle Integration Server 8.1.7
subtree.
Oracle Message Broker 2.0.1.0.1a
.
The Advanced Security
feature is selected automatically when OMB is selected.
If you are installing OMB specifically for OAI, perform the following steps:
Directory Suffix
, Country Code
, Organization
, and Organizational Unit Name
. You will need them later in the OAI installation.
Next
.
Ldap Port
and Ldap
Server
. You will need them later in the OAI installation.
Next
.
Next
.
The Summary window appears.
Next
.
Perform the following post-installation steps:
For more information about the TNS listener, see the OMB Installation Guide.
Do not perform any other optional steps--MQSeries, TIBCO, Async Component Invocation, or AQLite.
ombenv
script.
This file is supplied by OMB. For information about ombenv
, see the OMB Installation Guide.
For information about ombadmin
, see the OMB Administration Guide.
The login window appears.
Do not modify any fields in the login window.
connect
.
The main window appears.
tools
menu.
Select OMB Instance Configuration Wizard
.
The Welcome window appears.
Next
.
The Create a new or select an existing OMB instance window appears.
create a new OMB instance
.
Next
.
The Create a new OMB instance window appears.
Field | Value |
---|---|
|
Enter a lowercase, four- to eight-letter OMB instance name. Do not use spaces between letters. |
OMB Instance Name
. You will need it later in the OAI installation.
Next
.
The Create Message Broker window appears.
Field | Value |
---|---|
|
|
Next
.
The Select Servers and Drivers to Add window appears.
AQ Server, AQ Driver, Connection Factory for AQ
.
Next
.
The Create an Oracle AQ Server window appears.
The Create an Oracle AQ Driver 1 of 2 window appears.
Next
.
Do not modify the entries.
The Create an Oracle AQ Driver 2 of 2 window appears.
Field | Value |
---|---|
|
|
Do not modify any other entries.
Next
.
The Create an Oracle ASQ Connection Factory window appears.
aqCF
.
finish
.
Perform one of the following steps to start OMB.
MsgBroker -start -omb cn=msg_broker,cn=omb_instance_name
,cn=omb -heap 100
-noauth &
MsgBroker -start -omb "cn=msg_broker,cn=omb_instance_name
,cn=omb" -heap 100
-noauth
OMB is the store and forward unit for messages. It acts as the messaging hub in the OAI hub 'n' spoke architecture. OAI adapters use the Java Message Service (JMS), provided by OMB, for sending and receiving messages. For more information, see the OMB User Guide.
Perform the following steps to install OAI components:
setup.exe
on Windows NT
or
Run Installer
on UNIX.
The Welcome window appears.
Next
.
The File Locations window appears.
Next
.
This section describes the following:
The repository architecture consists of the following components:
The OAI components communicate to the Java layer and not directly to the database.
The database instance used for the repository is typically the same one used by OMB and OID. You do not need a separate physical database or another instance for the repository. The repository post-installation steps create the user and all its schema is contained within the user in the database.
The repository is used to store integration information as metadata.The iStudio product connects to the repository at design time and pushes the modeled mapping information into the repository. At runtime, the adapters access the repository and use the metadata as runtime instructions for performing transformations and other functions.
The following sections describe:
The installer does not allow you to install more than one repository per Oracle Home (it will deinstall the first repository and then install the second one.) However, you can have multiple Oracle Homes on a computer and have one repository per Oracle Home. (You can create an Oracle Home by installing the Oracle 8i client in different locations.) When you install the repository the second time, choose a different Oracle Home than the one where you first installed the repository.
To use the same database for multiple repositories, make sure you use different user names when the installation asks for the repository user name.
To tell if the repository is installed or started properly, start the repository and view the reposlog.txt
file in your repository directory. If you do not see any Exceptions in this file, the repository has been started properly.
Inspect the Exceptions you see in the repository log file. The most common cause of startup problems with the repository is that it is unable to talk to OID. When the OAI repository is started, it writes its location identifying information in OID so that iStudio (and the other OAI components) can find it. The following are common reasons that the repository is unable to connect to OID:
Make sure OID is started and that there are no errors starting OID. See the OID documentation for problems starting OID. If you want to use the OAI design time without OID, you can ignore the OID/LDAP Exceptions you see in the repository log file. If you see no other Exceptions, the repository has been started properly. Restart the repository after fixing problems with OID.
This indicates a wrong OID host, port, or organization information. The OID host should be the computer where OID is installed. If you are using the default port, the port should be 389. The organizational information should be the same information that you used when you installed OMB. If you are unsure what the organizational information is, use oidadmin
to view what is under Entry Management. To fix organizational information, reinstall the repository so that it points to the correct OID.
The OMB post-installation steps manually create base entries in OID. Run the OMB InitDir
post-installation command by entering:
InitDir -ccountry
-oorganization
-ouorganizational unit
For information about the InitDir
command, see the OMB Installation Guide.
Use the oidadmin
tool provided by OID command. The following message appears under Entry Management (bottom up):
ou=organizational_unit
,o=organization
,c=country
After starting the repository successfully, the following message appears:
cn=IORS,cn=Repository,cn=OAI,cn=Products,cn=OracleContext,ou=organizational
unit
,o=organization
,c=country
A message similar to the following appears in the repository log file:
javax.naming.NoPermissionException: [LDAP: Insufficient Access Rights]
This indicates that you have not run the OAI post-installation steps for OID (see "Performing an OID Post-Installation",). Run these steps and then restart the repository.
A SQL Exception indicates that the repository is unable to communicate to its database schema properly. Perform the following steps:
sqlplus system/manager@database_TNS_service_name
After you start the database and listener properly, the repository automatically reconnects to the database so you do not need to restart the repository.
.ini
repository in your repository directory) then try connecting to your database with this connection information using SQL*Plus. For example, enter:
sqlplususername
/password
@database_TNS_service_name
If the database user was not created properly, an error message similar to the following appears:
ORA-01017: invalid username/password; logon denied
The repository automatically reconnects to the database so you do not need to restart the repository.
Perform the following steps to install the repository:
OAI Repository 4.0.0
.
Next
.
The Welcome to the Repository Installation window appears.
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The repository component uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository's CORBA identification information (IOR) from OID. With this information, iStudio and the adapters can connect to the repository.
Next
.
The Repository Configuration window appears.
Field | Value |
---|---|
|
The repository name, which is not more than 10 characters, does not have white space, and is not the same as any other repository name on the computer. The install program creates a directory of the repository information on the file system of the computer. The repository is the Java API layer, not the database. See "Using iStudio", for more information. |
|
The name of the computer on which you are running the installer. |
Metadata Owner |
A two- to four-letter acronym of the company name on which the metadata is installed. This entry is used for strict metadata versioning. Metadata built by one owner cannot be modified by another. For more information about metadata versioning, see the user guide. |
Name
and Host Name
. You will need them for installing adapters.
The Repository Database Configuration window appears.
The Database User Configuration window appears.
Next
.
The Summary window appears.
Next
.
On Windows NT, the repository is installed at $ORACLE_HOME\oai\4.0\repository\
your_repository_name
.
On UNIX, the repository is installed at $ORACLE_HOME/oai/4.0/repository/
your_repository_name
.
After the installation is complete, the installer gives you a set of post-installation steps. These steps are also copied to post_installation.txt
in the repository's directory. Execute the following steps to create the repository's schema:
repo1.sql
and repo2.sql
scripts.
manager
. You changed this after installing the database.)
@repo1.sql
on the SQL*Plus command line to run the repo1.sql
script.
@repo2.sql
on the SQL*Plus command line to run the repo2.sql
script.
This section describes the following:
Perform the following steps to install iStudio:
Next
.
The Welcome to the iStudio Installation window appears.
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The iStudio component uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository's CORBA identification information (IOR) from OID. With this information, iStudio can connect to the repository.
Next
.
The Summary window appears.
Next
.
The iStudio component is installed at $ORACLE_HOME\oai\4.0\istudio
.
This section describes the following:
If you are not able to connect to the repository when you open or create a project, perform the following steps:
host
, port
, country
, organization
, organizational unit
) when you installed iStudio as you did when you installed the repository. If you did not, reinstall either the repository or iStudio to make them match.
RepoName
and RepoHostName
parameters in the repository.ini
file in your repository's directory.)
If you need to bring up iStudio (and do not need to use the OAI runtime), after iStudio fails to find the repository entry in OID (or fails to connect to OID), it asks if you want to read the repository's IOR (its location identifying information) from a file. Open the IOR file (FTP the file from the repository computer if iStudio and the repository are on different computers). The iStudio product connects to the repository bypassing OID. However, if you do not install OID or fix the problems with OID, the adapters will not be able to connect to the repository and the OAI runtime will not work.
All integration logic is captured in metadata modeled through iStudio. Perform the following steps to create or install integration metadata:
or
Use iStudio to create metadata from scratch.
Oracle has pre-packaged metadata packs for certain applications. These metadata packs come with their own installation instructions. For example, if you are integrating Oracle Internet Procurement with SAP, see the Implementation Guide for Oracle Internet Procurement InterConnect for SAP R/3.
If there is no pre-packaged metadata for your application, create the metadata using iStudio. (For information about using iStudio to create metadata, see the iStudio User Guide.)
Applications
. You will need the names when you install the adapters.
The single consumer queue
field lists queues. The multi consumer queue
field lists topics.
Perform the following steps to create JMS queues and topics under OMB:
ombenv
script.
This file is supplied by OMB. For information about ombenv
, see the OMB Installation Guide.
ombadmin
tool.
For more information, see the OMB Administration Guide.
Tool
menu.
The single consumer queue
field lists queues. The multi consumer queue
field lists topics.
Perform the following steps to create the queue wizard:
Next
.
The Use an Existing OMB Instance window appears.
ombadmin
tool.
Next
.
The Use an Existing Server window appears.
aq_server
.
Next
.
The Create an Oracle AQ Queue window appears.
Field | Value |
---|---|
|
The queue name that matches the single consumer queue name specified in the iStudio Message Capability Matrix. (See Step 3 of "Creating or Installing Integration Metadata".) |
|
Leave blank |
|
Select |
AQ Schema |
Enter |
Next
.
The Successful Queue Creation window appears.
finish
if you are done with all queues
or
Select Next
to create another queue.
Perform the following steps to create the queue wizard:
Next
.
The Use an Existing OMB Instance window appears.
ombadmin
tool.
Next
.
The Use an Existing Server window appears.
aq_server
.
Next
.
The Create an Oracle AQ Queue Topic 1 of 2 window appears.
Field | Value |
---|---|
|
The topic name that matches the single consumer queue name specified in the iStudio Message Capability Matrix. (See Step 3 of "Creating or Installing Integration Metadata".) |
|
Leave blank |
|
Select |
AQ Schema |
Enter |
Next
.
The Create an Oracle AQ Topic 2 of 2 window appears.
not assigned
.
Next
.
The Successful Topic Creation window appears.
finish
if you are done with all topics
or
Select Next
to create another topic.
This section describes the following:
The following adapters are packaged with OAI:
Adapters are components that are attached to applications to OAI enable them. The adapters differ from each other because of how they communicate with an application. For example, the SAP Adapter utilizes the SAP Remote Function Call (RFC) proprietary protocol to talk to SAP, but The XML AQ Adapter picks (and puts) XML messages in AQs.
Adapters do not have integration logic. The adapter has a generic transformation engine that processes metadata from the repository as runtime instructions to do transformations. The application defines for a adapter what its capabilities are. For example, it can define what messages it can publish, what messages it can subscribe to, and what are the transformations to perform. The application parameter allows the adapter to become smart in the context of the application to which it is connected. It allows the adapter to retrieve from the repository only that metadata that is relevant to the application. The application parameter must match the corresponding application that will be defined in iStudio under the Applications
folder.
If you are using pre-packaged metadata, after importing the pre-packaged metadata into the repository, start up iStudio to find the corresponding application (under the Applications
folder in iStudio) to use as the application for the adapter you are installing (unless the pack you are using provides directions for what the application should be.)
This section describes the following:
Perform the following steps to install the CRM 11i Adapter:
OAI CRM 11i Adapter 4.0.0
.
Next
.
The Welcome to the CRM 11i Adapter Installation window appears.
Next
.
The Adapter Information window appears.
Field | Value |
---|---|
|
The application you defined in iStudio. (See "Editing the adapter.ini Parameter"). |
|
Leave blank |
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The adapter uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository and OMB CORBA identification information (IOR) from OID. With this information, the adapter can connect to the repository and to OMB.
The Adapter Repository Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
Next
.
The Adapter OMB Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down previously. (See Step 10 of "Performing Post-Installation Steps for OMB on OAI".) |
|
Select 2.0.0.1 if you are using OMB 2.0.0.1 (with Oracle 8.1.6). Select 2.0.1.0 if you are using OMB 2.0.1.0 (with Oracle 8.1.7). |
Next
.
The AQ Database Configuration window appears.
The information on the AQ Database Configuration window is the AQ database on the application side from which the adapter will put or get XML messages. This is not the information for the hub database.
The AQ Database User Configuration window appears.
The Summary window appears.
Next
.
On Windows NT, the CRM 11i Adapter is installed on $ORACLE_HOME\oai\4.0\adapters\
Application
Partition
..
On UNIX, the CRM 11i Adapter is installed on $ORACLE_HOME/oai/4.0/adapters/
Application
Partition
..
This section describes the following:
The installer does not allow you to install more than one CRM 11i Adapter per Oracle Home. (It will deinstall the first CRM 11i Adapter and then install the second one.) However, you can have multiple Oracle Homes on a computer and have one CRM 11i Adapter per Oracle Home. (You can create an Oracle Home by installing the Oracle8i client in different locations.) When you install the CRM 11i Adapter the second time, choose a different Oracle Home than the one where you first installed the CRM 11i Adapter.
You can edit the following parameters in adapter.ini
in your CRM 11i Adapter's directory.
The AQ_HOST
, AQ_USERNAME
, AQ_PASSWORD
, AQ_INSTANCE
, AQ_PORT
, and AQ_CONSUMER_NAME
are not part of the installation.
Restart the adapter after editing the parameters.
This section describes the following:
You can install the database adapter on Oracle 7.3.x, Oracle 8.0.x, or Oracle8i databases. All other OAI components require Oracle8i.
Perform the following steps to install the database adapter:
OAI Database Adapter 4.0.0
.
Next
.
The Welcome to the Database Adapter Installation window appears.
Next
.
The Adapter Information window appears.
Field | Value |
---|---|
Application |
The application you defined in iStudio. (See "Editing the adapter.ini Parameter"). |
Partition |
Leave blank |
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The adapter uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository and OMB CORBA identification information (IOR) from OID. With this information, the adapter can connect to the repository and to OMB.
The Adapter Repository Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
Next
.
The Adapter OMB Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down previously. (See Step 10 of "Performing Post-Installation Steps for OMB on OAI".) |
|
Select 2.0.0.1 if you are using OMB 2.0.0.1 (with Oracle 8.1.6). Select 2.0.1.0 if you are using OMB 2.0.1.0 (with Oracle 8.1.7). |
Next
.
The Database Configuration window appears.
Field | Value |
---|---|
|
The computer name on which the database is installed. |
|
The default TNS listener port. |
|
The SID for the application database. |
The Host Name
, Listener Port Number
, and SID
you enter are for the application database that the adapter will connect to, not the hub database.
Next
.
The Database User Configuration window appears.
The Host Name
and Password
are used to determine where the stored procedures generated through iStudio will be installed for application inbound messages. At runtime, the database adapter will use this information to call the user-specified stored procedures. The user can be a existing user. You can, but are not required to, create a separate OAI user.
Next
.
The Summary window appears.
Next
.
On Windows NT, the database adapter is installed at $ORACLE_HOME\oai\4.0\adapters\
Application
Partition
.
On UNIX, the database adapter is installed at $ORACLE_HOME/oai/4.0/adapters/
Application
Partition
.
After the installation is complete, the installer gives you a set of post-installation steps. These steps are also copied to post_installation.txt
in the database adapter's directory. Execute the following steps to create the database adapter's bridge tables:
agent1.sql
and agent2.sql
scripts.
sys
(not system
) user and change_on_install
password (this is the default password unless after installing the database, this was changed).
@agent1.sql
on the SQL*Plus command line to run the agent1.sql
script.
oai
user name and the oai
password to connect to the database.
@agent2.sql
on the SQL*Plus command line to run the agent2.sql
script.
This section describes the following:
The installer does not allow you to install more than one Database Adapter per Oracle Home. (It deinstalls the first Database Adapter and then installs the second one.) However, you can have multiple Oracle Homes on a computer and have one Database Adapter per Oracle Home. (You can create an Oracle Home by installing the Oracle8i client in different locations.) When you install the Database Adapter the second time, choose a different Oracle Home than the one where you first installed the Database Adapter.
You can edit the following parameters in adapter.ini
in your Database Adapter's directory.
Field | Value |
---|---|
|
the host name |
|
the SID |
|
the TNL listener port |
|
the user name |
|
the password |
The HTTP Adapter is an XML AQ Adapter with additions for communicating with remote Web applications.
This section describes the following:
Perform the following steps to install the HTTP Adapter:
OAI HTTP Adapter 4.0.0
.
Next
.
The Welcome to the HTTP Adapter Installation window appears.
Next
.
The Adapter Information window appears.
Field | Value |
---|---|
|
The application you defined in iStudio. (See "Editing the adapter.ini Parameter"). |
|
Leave blank |
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The adapter uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository and OMB CORBA identification information (IOR) from OID. With this information, the adapter can connect to the repository and to OMB.
The Adapter Repository Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
Next
.
The Adapter OMB Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down previously. (See Step 10 of "Performing Post-Installation Steps for OMB on OAI".) |
|
Select 2.0.0.1 if you are using OMB 2.0.0.1 (with Oracle 8.1.6). Select 2.0.1.0 if you are using OMB 2.0.1.0 (with Oracle 8.1.7). |
Next
.
The AQ Database Configuration window appears.
The information on the AQ Database Configuration window is the AQ database on the application side from which the adapter will put or get XML messages. This is not the information for the hub database.
The AQ Database User Configuration window appears.
The Summary window appears.
Next
.
On Windows NT, the HTTP Adapter is installed at $ORACLE_HOME\oai\4.0\adapters\
Application Partition
.
On UNIX, the HTTP Adapter is installed at $ORACLE_HOME/oai/4.0/adapters/
Application Partition
.
The installer gives you a set of post-installation steps in the README.txt
file in your HTTP Adapter's directory. After you installation is complete, execute these steps to enable your Web/Application Server for use with the HTTP Adapter.
This section describes the following:
The installer does not allow you to install more than one HTTP Adapter per Oracle Home. (It will deinstall the first HTTP Adapter and then install the second one.) However, you can have multiple Oracle Homes on a computer and have one HTTP Adapter per Oracle Home. (You can create an Oracle Home by installing the Oracle8i client in different locations.) When you install the HTTP Adapter the second time, choose a different Oracle Home than the one where you first installed the HTTP Adapter.
You can edit the following parameters in adapter.ini
in your HTTP Adapter's directory.
The AQ_HOST
, AQ_USERNAME
, AQ_PASSWORD
, AQ_INSTANCE
, AQ_PORT
, and AQ_CONSUMER_NAME
are not part of the installation.
Restart the adapter after editing the parameters.
This section describes the following:
Perform the following steps to install the SAP Adapter:
OAI SAP Adapter 4.0.0
.
Next
.
The Welcome to the SAP Adapter Installation window appears.
Next
.
The Adapter Information window appears.
Field | Value |
---|---|
Application |
The application you defined in iStudio. (See "Editing the adapter.ini Parameter"). |
Partition |
Leave blank |
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The adapter uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository and OMB CORBA identification information (IOR) from OID. With this information, the adapter can connect to the repository and to OMB.
The Adapter Repository Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
Next
.
The Adapter OMB Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down previously. (See Step 10 of "Performing Post-Installation Steps for OMB on OAI".) |
|
Select 2.0.0.1 if you are using OMB 2.0.0.1 (with Oracle 8.1.6). Select 2.0.1.0 if you are using OMB 2.0.1.0 (with Oracle 8.1.7). |
Next
.
The SAP Configuration window appears.
Next
.
The SAP User Configuration window appears.
Next
.
The Integration Methods window appears.
all
. For iProcurement to SAP, select the following:
BAPIs
IDocs outbound from SAP
IDocs inbound into SAP
Following is a description of these integration methods:
Next
.
Depending upon what you select, the windows listed in Steps 19 to 23 appear.
If the SAP Adapter will be sending or receiving IDocs, the RFC Destination Configuration window appears.
See "Creating a Valid RFC Destination" for details on how to configure a valid RFC destination in SAP.
Next
.
If the SAP Adapter will be sending IDocs into SAP, the Sender Partner Configuration window appears.
Next
.
If the SAP Adapter will be sending IDocs into SAP, the Recipient Partner Configuration window appears.
Next
.
The Summary window appears.
Next
.
On Windows NT, the SAP Adapter is installed on $ORACLE_HOME\oai\4.0\adapters\
Application
Partition
.
On UNIX, the SAP adapter is installed on $ORACLE_HOME/oai/4.0/adapters/
Application
Partition
.
Perform the following steps to complete installing the SAP Adapter:
librfc32.dll
file to the $ORACLE_HOME\ojrfc\4.0\bin
directory.
The librfc32.dll
file is distributed with the SAP system to which the adapter will connect. OAI does not provide the librfc32.dll
file.
any_name
.segment_release_version
. SAP_version
.
Normally, the segment release version and the SAP version are the same. For example, for SAP version 4.0B, the file would have a name like ALL.40B.40B
. If you are using SAP 4.5B, but you want to use the 4.0B version of the IDocs, export the IDocs (setting the segment release version to 40B) to files and give the files a name similar to idoc_name.
40B.45B
. You can also you can export all the IDocs to one file and give it a name similar to ALL.40B.45B
.
If you purchased OAI as part of a pack, check to see if the pack comes with the IDoc files and for more details on how to use the files.
adapter.ini
file located in your SAP Adapter's directory. Provide the names of the IDoc files. If there are more than one, separate them with commas. For example, enter:
IDocRepositoryFiles=MATMAS03.40B.45B,DEBMAS03.40B.45B.
If you do not perform this step correctly, you may encounter the following error when you run the SAP Adapter:
** Error: The IDoc repository could not be initialized from the repository file (file_name
) because of an error: io error: syntax file file_namee cannot be opened (file_name
). Please make sure you have the correct IDoc repository file, save log files and contact the integration team.
This section describes the following:
The installer does not allow you to install more than one SAP Adapter per Oracle Home. (It will deinstall the first SAP Adapter and then install the second one.) However, you can have multiple Oracle Homes on a computer and have one SAP Adapter per Oracle Home. (You can create an Oracle Home by installing the Oracle8i client in different locations.) When you install the SAP Adapter the second time, choose a different Oracle Home than the one where you first installed the SAP Adapter.
Log on to SAP as the same user that you specified during the SAP Adapter install using the SAP front end. Call SAP transaction SM59 or go to Tools>Administration>Administration>Network>RFC destinations
.
Press F8
or select Create
. Enter a name for your RFC destination, specify T
for connection, enter a description, check the Current User
option, and select save
or press Control+s
.
On the next window, select Registration as the Activation. Then enter a program ID. SAP recommends entering an ID like:
host_name
. program_or_organization_identifier.
Remember what you enter for program ID because this is what you will specify for RFV destination during the SAP Adapter install (or what you will specify for IDocDestination in the adapter.ini
file.)
You can edit the following parameters in adapter.ini
in your SAP Adapter's directory.
This section describes the following:
Perform the following steps to install the XML AQ Adapter:
OAI XML AQ Adapter 4.0.0
.
Next
.
The Welcome to the XML AQ Adapter Installation window appears.
Next
.
The Adapter Information window appears.
Field | Value |
---|---|
|
The application you defined in iStudio. (See "Editing the adapter.ini Parameter"). |
|
Leave blank |
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The adapter uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the repository and OMB CORBA identification information (IOR) from OID. With this information, the adapter can connect to the repository and to OMB.
The Adapter Repository Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
Next
.
The Adapter OMB Configuration window appears.
Field | Value |
---|---|
|
The value you wrote down previously. (See Step 10 of "Performing Post-Installation Steps for OMB on OAI".) |
|
Select 2.0.0.1 if you are using OMB 2.0.0.1 (with Oracle 8.1.6). Select 2.0.1.0 if you are using OMB 2.0.1.0 (with Oracle 8.1.7). |
Next
.
The AQ Database Configuration window appears.
The information on the AQ Database Configuration window is the AQ database on the application side from which the adapter will put or get XML messages. This is not the information for the hub database.
The AQ Database User Configuration window appears.
The Summary window appears.
Next
.
On Windows NT, the XML AQ Adapter is installed at $ORACLE_HOME\oai\4.0\adapters\
Application Partition
.
On UNIX, the XML AQ Adapter is installed at $ORACLE_HOME/oai/4.0/adapters/
Application Partition
.
This section describes the following:
The installer does not allow you to install more than one XML AQ Adapter per Oracle Home. (It will deinstall the first XML AQ Adapter and then install the second one.) However, you can have multiple Oracle Homes on a computer and have one XML AQ Adapter per Oracle Home. (You can create an Oracle Home by installing the Oracle8i client in different locations.) When you install the XML AQ Adapter the second time, choose a different Oracle Home than the one where you first installed the XML AQ Adapter.
You can edit the following parameters in adapter.ini
in your XML AQ Adapter's directory.
The AQ_HOST
, AQ_USERNAME
, AQ_PASSWORD
, AQ_INSTANCE
, AQ_PORT
, and AQ_CONSUMER_NAME
are not part of the installation.
Restart the adapter after editing the parameters.
This section describes the following:
After the initial configuration, you can enter the following values to edit adapter.ini
parameters located in your adapter's directory:
After the initial configuration, you can enter the following values to edit agent.ini
parameters located in your adapter's directory:
The other parameters in agent.ini are not part of the installation and are described in the agent.ini
documentation.
After the initial configuration, you can enter the following values to edit repository.ini
parameters located in your adapter's directory:
Field | Value |
---|---|
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
|
The value you wrote down when you installed the repository. (See Step 8 of "Installing the Repository".) |
To tell if an adapter is installed or started properly, start the adapter and view the adapter's log files. The adapter log files are located in the adapter's directory. Look at the following log files:
AgentLog.txtApplication
Partition
Log.txt service.log
If you do not see any Exceptions in these files, the adapter started properly.
Inspect the Exceptions you see in the adapter log file. The most common cause of startup problems are the following:
Make sure OID is started and that you ran the OMB post-installation steps properly. Also, see the repository documentation.
Make sure the repository is started properly. (See the repository documentation.) The adapter will connect to the repository after it is started properly. You do not need to restart the adapter.
Make sure the OMB is started properly. (See the OMB documentation.)
The OAI Management Infrastructure is an extension of the Oracle Management Server component of the Oracle Enterprise Manager. You must install the OAI Management Infrastructure in an Oracle Home that contains Oracle Management Server version 2.1 or later. After you install the Management Infrastructure, use the Enterprise Manager Console to manage OAI components. Use the console to start, stop, monitor, and troubleshoot the OAI at runtime.
Perform the following steps to install the Management Infrastructure.
OAI Management Infrastructure 4.0.0
.
Next
.
The Welcome to the Management Infrastructure Installation window appears.
Next
.
The LDAP Server Location window appears.
Field | Value |
---|---|
|
The computer on which OID is installed. If you follow the recommended topology, the host name is the hub computer. |
|
The value you wrote down when you installed OMB. (See Step 6 of "Installing OMB for OAI". The default value is 389. |
The LDAP Server Suffix Information window appears.
Field | Value |
---|---|
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
|
The value you wrote down when you installed OMB. (See Step 2 of "Installing OMB for OAI". |
The Management Infrastructure uses Country
, Organization
, and Organizational Unit
to locate the OID instance in the hub to find the OAI CORBA identification information (IOR) from OID. With this information, the Management Infrastructure can connect to the OAI components and manage them.
The Summary window appears.
Next
.
Perform the following Management Infrastructure post-installation steps:
To create new adapters and iStudio browsers instead of using the ones that come bundled with OAI, install SDK and follow the documentation provided with it. Perform the following steps:
OAI SDK 4.0.0
.
Next
.
The Summary window appears.
Next
.
On Windows NT, the SDK is installed at $ORACLE_HOME\oai\4.0\sdk
.
On UNIX, the SDK is installed at $ORACLE_HOME/oai/4.0/sdk.
NT$ORACLE_HOME\oai\4.0\sdk\istudio\doc\Browser Doc.html
.
$ORACLE_HOME\oai\4.0\sdk\adapter\doc\index.html
.
$ORACLE_HOME/oai/4.0/sdk/adapter/doc/index.html
.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|