Release 4.1 for Windows NT/2000 and UNIX
Part Number A90327-01
 Library |
 Contents |
 Index |
| Oracle Applications InterConnect Installation Guide Release 4.1 for Windows NT/2000 and UNIX Part Number A90327-01 |
|
This chapter describes using the Oracle Applications InterConnect components:
This section describes the following:
In the following sections, the "repository directory" refers to:
On Windows NT:
$ORACLE_HOME\oai\4.1\repository\your_repository_name.
On UNIX:
$ORACLE_HOME/oai/4.1/repository/your_repository_name.
In the following sections, the "hub directory" refers to:
Perform the following steps to start the Repository on a Windows NT system:
Perform the following steps to start the Repository on a UNIX system:
To tell if the repository is started properly, view the reposlog.txt file in your repository directory after starting the repository. If you do not see any Exceptions in this file, the repository has been started properly. If you do see Exceptions, refer to the Repository Installation.
Perform the following steps to stop the repository on a Windows NT system:
Perform the following steps to stop the Repository on a UNIX system:
All repository configuration may be modified manually except for the repository name.
To change the repository name, you must do a reinstall (Repository Installation.) Before reinstalling, either deinstall Oracle Applications InterConnect from this Oracle Home, or delete the hub.ini file in the hub directory.
To change the repository's hub database configuration, edit the hub.ini file located in the hub directory. Note: this change will effect all Oracle Applications InterConnect components installed in this Oracle Home.
To change any other configuration information, edit the repository.ini file in the repository's directory. Configurable parameters are documented in this file.
If you see Exceptions in the reposlog.txt file after starting your repository, then this means that there has been an error.
Inspect the Exceptions that you see in the repository log file. The most common cause of start-up problems with the repository is that it is unable to talk to the Oracle Applications InterConnect hub database. You will notice a SQLException in the repository log file. The following are common reasons that the repository is unable to connect to the hub database:
This section describes the following:
Perform the following steps to start iStudio on a Windows NT system:
Perform the following step to stop iStudio on a Windows NT system:
If you are unable to connect to the repository when creating or opening a project, please make sure the repository is started properly (see "Making Sure the Repository is Started Properly" ).
This section describes the following:
In the following sections, the "adapter directory" refers to:
On Windows NT:
$ORACLE_HOME\oai\4.1\adapters\your_adapter_name.
On UNIX:
$ORACLE_HOME/oai/4.1/adapters/your_adapter_name.
In the following sections, the "hub directory" refers to:
If you will be using the SAP Adapter to send or receive IDocs to or from SAP, then you must follow these steps:
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 RFC destination during the SAP Adapter install (or what you will specify forsap_bridge_idoc_destination in the adapter.ini file.)
Export one or more files from SAP that contain information about the IDoc structures for the IDocs which the SAP Adapter will be using. These files must have the same information that you used to import the IDocs in iStudio. The file must be named 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 export all the IDocs to one file and give it a name similar to ALL.40B.45B.
If you purchased Oracle Applications InterConnect 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.
sap_bridge_idoc_reposition_files=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 cannot be opened (file-name). Please make sure you have the correct IDoc repository file, save log files and contact the integration team.
Perform the following steps to start an Adapter on a Windows NT system:
Perform the following steps to start an Adapter on a UNIX system:
To tell if an adapter is started properly, view the adapter's oailog.txt file. In the adapter's directory, there should be a directory called logs. In there, a new directory is generated every time an adapter is started. Go into the most recently created directory and view the oailog.txt file. If you do not see any Exceptions in this file, the adapter has been started properly. If you do see Exceptions, refer to the "Troubleshooting Adapters" .
Perform the following steps to stop Adapters on a Windows NT system:
Perform the following steps to stop Adapters on a UNIX system:
All adapter configuration may be modified manually except for the adapter's application parameter.
If you see Exceptions in the oailog.txt file after starting an adapter, then this means that there has been an error.
Inspect the Exceptions that you see in the adapter log file. The most common causes of start-up problems with the adapter is that it is unable to talk to the Oracle Applications InterConnect hub database or repository. The following are common reasons that the adapter is unable to connect to the hub database:
The following are common reasons that the adapter is unable to connect to the repository:
This section describes the following:
In the following sections, the "Workflow Communication Infrastructure directory" refers to:
In the following sections, the "hub directory" refers to:
Perform the following steps to start the Workflow Communication Infrastructure on a Windows NT system:
Perform the following steps to start the Workflow Communication Infrastructure on a UNIX system:
To tell if the Workflow Communication Infrastructure is started properly, view its oailog.txt file. In the Workflow Communication Infrastructure directory, there should be a directory called logs. In there, a new directory is generated every time the Workflow Communication Infrastructure is started. Go into the most recently created directory and view the oailog.txt file. If you do not see any Exceptions in this file, then it has been started properly. If you do see Exceptions, refer to the "Troubleshooting Workflow Communication Infrastructure" .
Perform the following steps to stop the Workflow Communication Infrastructure on a Windows NT system:
Perform the following steps to stop the Workflow Communication Infrastructure on a UNIX system:
Note: this change will effect all Oracle Applications InterConnect components installed in this Oracle Home.
If you see Exceptions in the oailog.txt file after starting an the Workflow Communication Infrastructure, then this means that there has been an error.
Inspect the Exceptions that you see in the log file. The most common cause of start-up problems with the Workflow Communication Infrastructure is that it is unable to talk to the Oracle Applications InterConnect hub database or repository. The following are common reasons that the Workflow Communication Infrastructure is unable to connect to the hub database:
The following are common reasons that the Workflow Communication Infrastructure is unable to connect to the repository:
This section describes the following:
In the following sections, the "hub directory" refers to:
The Management Infrastructure (Server) is an extension to Oracle Management Server. After starting the hub database and TNS listener, simply start the Oracle Management Server guide in order to use the Management Infrastructure (Server). Also, make sure the Oracle 8.1.7 Intelligent Agent in the same Oracle Home as the Oracle Management Server has been started.
The Management Infrastructure (Client) is an extension to the Enterprise Manager Console. Simply start the Enterprise Manager Console (refer to the Enterprise Manager user guide) in order to use the Management Infrastructure (Client).
View the log files to make sure the Management Infrastructure is started properly.
Review all logs:
The Management Infrastructure (Server) is an extension to Oracle Management Server. Simply stop the Oracle Management Server in order to stop the Management Infrastructure (Server).
The Management Infrastructure (Client) is an extension to the Enterprise Manager Console. Simply exit the Enterprise Manager Console (refer to the Enterprise Manager user guide) in order to stop using the Management Infrastructure (Client).
To change the Management Infrastructure's hub database configuration, edit the hub.ini file located in the hub directory. Here you can change the hub database connection information. Note: this change will effect all Oracle Applications InterConnect components installed in this Oracle Home.
If you are unable to use the Enterprise Manager Console to manage the Oracle Applications InterConnect components, check the following:
Make sure you have run the Management Infrastructure (Server) and Management Infrastructure (Client) installs and Post-Installation steps successfully. The Management Infrastructure (Server) must be installed in the same Oracle Home as the Oracle Management Server that you are connecting to. The Management Infrastructure (Client) must be installed in the same Oracle Home as the Oracle Enterprise Manager Console that you are using.
Make sure the Management Infrastructure (Server) is started properly (see "Making sure the Management Infrastructure is Started Properly" ).
Check all log files (see "Making sure the Management Infrastructure is Started Properly" ).
Navigate your browser to the SDK documentation for details on using the SDK.
The iStudio SDK documentation (for creating custom Browsers) for Windows NT is located at:
$ORACLE_HOME\oai\4.1\sdk\istudio\doc\BrowserDoc.html
The Adapter SDK documentation (for creating custom Adapters) for Windows NT is located at:
$ORACLE_HOME\oai\4.1\sdk\adapter\doc\index.html
for UNIX it is located at:
$ORACLE_HOME/oai/4.1/sdk/adapter/doc/index.html
All configuration information is stored in .ini files. It is recommended that you rely on your Operating System's security to protect these configuration files so that only privileged users can view or modify the appropriate configuration information.
If you would like to provide additional security, you can encrypt any parameter in the .ini files. To do so:
On Windows NT:
- run $ORACLE_HOME\oai\4.1\bin\encrypt
On UNIX:
- run $ORACLE_HOME/oai/4.1/bin/encrypt
This program will ask you for the value that you want to encrypt. You can then copy the encrypted value into the .ini file and prepend the parameter name with encrypted_. For example, if you want to encrypt the "password=manager" parameter in a .ini file, run the encrypt program and type in "manager". Then in the .ini file, change the line to:
"encrypted_password=[whatever the encrypt program returns]".
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|