Oracle® Application Server Integration B2B Installation Guide
10g Release 2 (10.1.2) for Solaris Operating System (SPARC), Linux x86, hp HP-UX PA-RISC (64-bit), and Microsoft Windows Part No. B13850-01 |
|
![]() Previous |
![]() Next |
This chapter describes how to install Oracle Application Server Integration B2B components.
This chapter contains these topics:
Installing Multiple OracleAS Integration B2B Versions on a Single Host
Silent and Noninteractive Installation
Note: In addition to installing from CD-ROM, you can also install Oracle Application Server Integration B2B from DVD. Oracle Application Server Integration B2B installation files are located in theb2b directory of the DVD. See the Oracle Application Server Installation Guide for your operating system for additional information on DVD installations.
|
Note: Unless otherwise noted, the directory paths shown in this chapter follow UNIX conventions (for example, forward slashes (/ ) are used). If using Integration B2B on a Windows operating system, modify your directory paths as required.
|
You must complete the following preinstallation tasks before installing OracleAS Integration B2B.
Step 2: Unlock or Obtain the OracleAS Integration B2B Schema User Password
Step 3: Verify Oracle Application Server Metadata Repository Initialization Parameters
Step 4: Install the J2EE and Web Cache Installation Type of Oracle Application Server
Install or upgrade to the current release of the Oracle Application Server Metadata Repository through one of the following methods.
Install an Oracle Application Server Infrastructure 10.1.2 version (includes the Oracle Application Server Metadata Repository) from the Oracle Application Server software CD-ROM.
Run Oracle Application Server Metadata Repository Creation Assistant to create the current release of the Oracle Application Server Metadata Repository from Oracle Database 10g or Oracle Database 9i version 9.2.0.5.0.
Run the Oracle Application Server Upgrade Assistant to upgrade a release 9.0.2 or 9.0.3 Oracle9iAS Metadata Repository or release 9.0.4 Oracle Application Server Metadata Repository to the current release.
See Also:
|
Ensure that you remember the OracleAS Integration B2B schema password (for the user name b2b
) from the Oracle Application Server Metadata Repository installation. You are prompted for this password if you install OracleAS Integration B2B and do not select Identity Management Access in Step 10 of "Beginning the Installation". This configures OracleAS Integration B2B with an Oracle Application Server Metadata Repository not registered with Oracle Internet Directory.
The methods for unlocking and obtaining these passwords are based on the following scenarios:
Verify that the following Oracle Application Server Metadata Repository initialization parameters are set to at least these values:
JOB_QUEUE_PROCESSES
is greater than or equal to 5
AQ_TM_PROCESSES
is greater than or equal to 5
OPEN_CURSORS
is greater than or equal to 1000
Log in to SQL*Plus on the host on which the Oracle Application Server Metadata Repository is installed.
sqlplus /NOLOG
Connect to the Oracle Application Server Metadata Repository as the SYS
user.
SQL> CONNECT SYS/password AS SYSDBA
Verify the following initialization parameter settings:
SQL> SELECT name, value FROM v$parameter WHERE name = 'JOB_QUEUE_PROCESSES'; SQL> SELECT name, value FROM v$parameter WHERE name = 'AQ_TM_PROCESSES'; SQL> SELECT name, value FROM v$parameter WHERE name = 'OPEN_CURSORS';
Reset any initialization parameters to the recommended values:
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=5 SCOPE=spfile; SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=5 SCOPE=spfile; SQL> ALTER SYSTEM SET OPEN_CURSORS=1000 SCOPE=spfile;
Stop and restart the Oracle Application Server Metadata Repository.
SQL> SHUTDOWN SQL> STARTUP
As shown in Figure 1-1, Oracle recommends that you install the J2EE and Web Cache installation type of Oracle Application Server 10g Release 2 (10.1.2) on a separate middle-tier host (not the same host on which the Oracle Application Server Metadata Repository is installed). Oracle recommends a separate host to optimize performance. You cannot use a pre-10g Release 2 (10.1.2) version of J2EE and Web Cache.
See Also: Oracle Application Server Installation Guide for your operating system for J2EE and Web Cache installation instructions |
Ensure that you remember the following information from the Oracle Application Server Metadata Repository or J2EE and Web Cache installation. You can be prompted to enter this information during OracleAS Integration B2B installation.
The Oracle Internet Directory administrator user name and password you entered during Oracle Application Server Metadata Repository installation. You need this information if you want to associate OracleAS Integration B2B with an Oracle Application Server Metadata Repository registered with Oracle Internet Directory.
The Oracle Application Server administrator's password (for user name ias_admin
) entered during J2EE and Web Cache installation. This password is also used for accessing the OracleAS Integration B2B user interface tool and the Oracle Enterprise Manager 10g Application Server Control Console. You need this password whether or not you associate OracleAS Integration B2B with an Oracle Application Server Metadata Repository registered with Oracle Internet Directory.
Follow these instructions to install OracleAS Integration B2B:
Installing OracleAS Integration B2B without Identity Management Access
Installing OracleAS Integration B2B with Identity Management Access
Ensure that all preinstallation tasks and requirements described in "Preinstallation Tasks" have been completed.
Log on to the middle-tier host on which you installed the J2EE and Web Cache installation type of Oracle Application Server.
If installing on Solaris, Linux, or HP-UX, see the appropriate Oracle Application Server Installation Guide for each operating system for instructions on:
Setting the mount point for the CD-ROM
Starting Oracle Universal Installer
Insert the OracleAS Integration CD-ROM.
Start the Oracle Universal Installer from the root of the CD-ROM or from the Disk1
directory:
On... | Do This... |
---|---|
Solaris, Linux, or HP-UX | Enter the following command at the operating system prompt:
|
Windows | Click setup.exe .
|
The Welcome screen appears.
Click Next.
The Specify File Locations screen appears.
Select the Oracle home name and directory path in which to install Oracle components in the Destination fields. The directory path must be the same one in which you installed the J2EE and Web Cache installation type. Do not change the directory path in the Source field. This is the location of OracleAS Integration B2B installation files.
Click Next.
The Select a Product to Install screen appears.
Product | Description |
---|---|
Oracle Application Server Integration InterConnect
|
Enables you to integrate heterogeneous systems such as Oracle Applications, non-Oracle applications, or third-party, messaging-oriented middleware (MOM). Oracle Application Server Integration InterConnect is a high-speed message broker suited for the data and application integration market. Integrations can be deployed within an enterprise or across enterprise boundaries through the Internet.
See Also: Oracle Application Server Integration InterConnect Installation Guide for instructions on installing Oracle Application Server Integration InterConnect |
Oracle Application Server Integration B2B
|
Enables you to design, deploy, monitor, and manage integrations between enterprises (also known as business-to-business (B2B) integrations). Oracle Application Server Integration B2B enables trading partners to conduct business using RosettaNet, electronic data interchange (EDI), or a custom business protocol. |
Select Oracle Application Server Integration B2B and click Next.
The Integration B2B Component Configuration screen displays the following components to configure and automatically start at the end of installation:
See Also: Oracle Application Server Concepts in the Oracle Application Server 10g Documentation Library for additional details about the Oracle Application Server Metadata Repository and Identity Management Access |
Select whether or not to use Identity Management Access, and click Next.
If... | Then During This Installation Process... | Go To... |
---|---|---|
You do not select Identity Management Access
|
You select an Oracle Application Server Metadata Repository to use with this OracleAS Integration B2B instance that is not registered with Oracle Internet Directory. | "Installing OracleAS Integration B2B without Identity Management Access"
|
You select Identity Management Access | You associate an Oracle Application Server Metadata Repository to use with this OracleAS Integration B2B instance that is registered with Oracle Internet Directory. | Step 1 of "Installing OracleAS Integration B2B with Identity Management Access" |
You previously selected Identity Management Access during J2EE and Web Cache installation | The check box is grayed out. You specify the login credentials for the Oracle Internet Directory to use with this OracleAS Integration B2B instance. | Step 3 of "Installing OracleAS Integration B2B with Identity Management Access" |
See Also: Oracle Application Server Installation Guide for your operating system for additional details about configuring Identity Management Access after installation if you do not want to configure it during installation |
Enter the following information on the Specify Metadata Repository for Integration B2B screen. Information is required for all fields.
Field | Description |
---|---|
Password for Integration B2B Schema (b2b) | Enter the password for the OracleAS Integration B2B schema.
See Also: "Step 2: Unlock or Obtain the OracleAS Integration B2B Schema User Password" for instructions on obtaining the |
Hostname and Port | Enter the name and the port number of the host on which the Oracle Application Server Metadata Repository database is installed. Use the following format:
Use the following format for Oracle Real Application Clusters:
|
Service Name | Enter the service name for the Oracle Application Server Metadata Repository. The service name was specified during Oracle Application Server Infrastructure installation.
The service name value reflects the global database name, which comprises the database name (for example, db_sales.us.oracle.com The service name is different from the database system identifier (SID), which uniquely identifies the database name only (for example, |
ias_admin Password | Enter the OracleAS Integration B2B password. This is the password you entered during J2EE and Web Cache installation. When installation is complete, you use this password to log in to the following tools:
See Also: Oracle Application Server Administrator's Guide in the Oracle Application Server 10g Documentation Library for instructions on resetting the |
See Also: Oracle Application Server Administrator's Guide in the Oracle Application Server 10g Documentation Library for instructions on changing the OracleAS Integration B2B schema password |
Click Next.
If the Oracle Application Server Metadata Repository you selected does not provide globalization support for OracleAS Integration B2B, an onscreen message notifies you. Make an appropriate selection:
Click Continue if you do not want globalization support.
Click Retry to select a different Oracle Application Server Metadata Repository that includes globalization support for OracleAS Integration B2B.
The Summary screen appears.
Enter the following information on the Register with Oracle Internet Directory screen to register this Oracle Application Server middle tier with Oracle Internet Directory.
Field | Description |
---|---|
Hostname | Enter the name of the host on which Oracle Internet Directory is installed. |
Port | Enter the port number for the host. |
Use only SSL connections with Oracle Internet Directory | Select the checkbox if you want to use secure socket layer (SSL) for all connections from this middle tier to Oracle Internet Directory. |
Click Next. If you specified an Oracle Internet Directory with only one realm, the Specify Login for Oracle Internet Directory screen appears.
Enter the following information on the Specify Login for Oracle Internet Directory screen.
Field | Description |
---|---|
Username | Enter a user name that belongs to the iASAdmins group. The user name you enter is authenticated against this realm. |
Password | Enter the password for this user name. |
See Also: Oracle Internet Directory Administrator's Guide in the Oracle Application Server 10g Documentation Library for a description of realms |
Click Next.
The Select Metadata Repository screen appears.
Select the Oracle Application Server Metadata Repository to use with this Oracle Application Server middle tier. Only an Oracle Application Server Metadata Repository registered with Oracle Internet Directory appears.
This Oracle Application Server Metadata Repository must include the OracleAS Integration B2B schema. The OracleAS Integration B2B schema is available in your repository if you performed one of the following tasks:
Installed the current release of the Oracle Application Server Metadata Repository
Ran Oracle Application Server Metadata Repository Creation Assistant to create the current release of the Oracle Application Server Metadata Repository in Oracle Database 10g or Oracle Database 9i version 9.2.0.5.0
Ran the Upgrade Assistant to upgrade a release 9.0.2 or 9.0.3 Oracle9iAS Metadata Repository or release 9.0.4 Oracle Application Server Metadata Repository to the current release of the Oracle Application Server Metadata Repository
Click Next.
If the Oracle Application Server Metadata Repository you selected does not provide globalization support for OracleAS Integration B2B, an onscreen message notifies you. Make an appropriate selection:
Click Continue if you do not want globalization support.
Click Retry to select a different Oracle Application Server Metadata Repository that includes globalization support for OracleAS Integration B2B.
Enter the password for OracleAS Integration B2B. This is the password you entered during J2EE and Web Cache installation. When installation is complete, you use this password when logging into the following tools:
The OracleAS Integration B2B user interface tool with the admin
user name
The Oracle Enterprise Manager 10g Application Server Control Console with the ias_admin
user name
See Also: Oracle Application Server Administrator's Guide in the Oracle Application Server 10g Documentation Library for instructions on resetting theias_admin password if you do not remember it
|
Click Next.
The Summary screen appears.
Review specific details, including the space requirements to ensure that you have sufficient disk space.
Click Install to install the components.
After installation completes, the following postinstallation configuration tools are started to automatically configure OracleAS Integration B2B.
If installation and configuration are successful, the End of Installation screen appears and displays a message saying that installation was successful. If installation or configuration is unsuccessful, see "Troubleshooting Installation or Configuration Problems".
Click Next.
The End of Installation screen displays details about your installation session, including the Oracle Application Server Metadata Repository being used, assigned port numbers, and instructions for logging into the following tools:
The OracleAS Integration B2B user interface tool
The Oracle Enterprise Manager 10g Application Server Control Console
Remember the instructions for logging into these tools. These instructions are also described in the ipsetupinfo.txt
file located in the install
subdirectory of your OracleAS Integration B2B Oracle home directory.
Click Exit.
See Also:
|
You can perform the following postinstallation configuration security tasks:
Configuring an Additional Oracle HTTP Server Outside Your Corporate Network
Configuring SSL for the Oracle HTTP Server and OracleAS Integration B2B Instances
After you install J2EE and Web Cache and OracleAS Integration B2B, an Oracle HTTP Server instance is automatically started and configured to receive messages from remote trading partners and pass them onto your OracleAS Integration B2B instance. Both instances are installed in the same Oracle home directory on the same host inside your corporate network. Figure 3-1 shows this configuration.
For security reasons, Oracle recommends that you install and configure an additional Oracle HTTP Server outside your corporate network to receive messages from remote trading partners and pass them onto the Oracle HTTP Server and OracleAS Integration B2B instances inside your corporate network. This additional Oracle HTTP Server hides the actual location of the host trading partner from all outside parties.
Figure 3-2 shows this configuration and identifies the tasks to perform to configure an additional Oracle HTTP Server outside your corporate network.
The tasks shown in Figure 3-2 are described in the following sections:
Task 1: Install the Oracle HTTP Server Outside the Corporate Network
Task 2: Configure OPMN for Oracle HTTP Server and OracleAS Integration B2B Communication
Task 3: Configure mod_oc4j for the Oracle HTTP Server and OracleAS Integration B2B
Task 4: Configure mod_proxy for the Oracle HTTP Server and OracleAS Integration B2B
Note: These instructions describe how to use thegetOPMNPort command to obtain IP address and port number information on hosts both inside and outside your corporate network. Ensure that the ports on both sides of your corporate network have been opened. Otherwise, configuration fails.
|
Install the Oracle HTTP Server on a host outside the corporate network.
The Oracle HTTP Server is installed with the J2EE and Web Cache middle tier installation type.
See Also:
|
Oracle Process Manager and Notification (OPMN) controls and monitors Oracle Application Server components and instances. This section describes how to configure OPMN for Oracle HTTP Server and OracleAS Integration B2B communication.
Note: Do not manually edit OPMN configuration files. Instead, use thedcmctl command line tool described in this section to update these files.
|
Go to the host inside your corporate network on which OracleAS Integration B2B is installed.
Go to the ORACLE_HOME
/dcm/bin
directory. This is the Oracle home directory in which OracleAS Integration B2B is installed.
Enter the following command to obtain Internet Protocol (IP) address and port number information for the OracleAS Integration B2B host:
dcmctl getOPMNPort
Output similar to the following appears:
144.52.146.244:6201
Ensure that you remember the output from this command. In Step 6 of these procedures, you update the host outside your corporate network with this information.
Go to the host outside your corporate network on which the Oracle HTTP Server is installed.
Go to the ORACLE_HOME
/dcm/bin
directory.
Enter the following commands:
dcmctl addOPMNLink output
dcmctl updateConfig
where output
is the information that displayed when you entered the command in Step 3 (for example, 144.52.146.244:6201
).
Enter the following command to obtain IP address and port number information for the Oracle HTTP Server host:
dcmctl getOPMNPort
Ensure that you remember the output from this command. In Step 10 of these procedures, you update the host inside your corporate network with this information.
Return to the host inside your corporate network on which OracleAS Integration B2B is installed.
Go to the ORACLE_HOME
/dcm/bin
directory. This is the Oracle home directory in which OracleAS Integration B2B is installed.
Enter the following commands:
dcmctl addOPMNLink output
dcmctl updateConfig
where output
is the information that displayed when you entered the command in Step 7.
mod_oc4j
is an Oracle HTTP Server module that manages the communication between the Oracle HTTP Server and Oracle Application Server Containers for J2EE (OC4J). You must configure mod_oc4j
on the Oracle HTTP Server to perform the following tasks:
Identify the message request on which to act
Determine the OC4J instance to route the message request
Communicate with the OC4J process
Go to the host inside your corporate network on which OracleAS Integration B2B is installed.
Go to the ORACLE_HOME
/dcm/bin
directory. This is the Oracle home directory in which OracleAS Integration B2B is installed.
Enter the following command:
dcmctl whichInstance
Output similar to the following appears:
midtier.qa-pc.us.oracle.com
Ensure that you remember the output from this command. In Step 6 of these procedures, you update the host outside your corporate network with this information.
Go to the host outside your corporate network on which the Oracle HTTP Server is installed.
Go to the ORACLE_HOME
/Apache/Apache/conf
directory.
Add the following lines to the mod_oc4j.conf
file:
Oc4jMount /b2b instance://B2BInstance:OC4J_B2B Oc4jMount /b2b/* instance://B2BInstance:OC4J_B2B
where B2BInstance
is the output from the whichInstance
command in Step 3 (for example, midtier.qa-pc.us.oracle.com
). For example:
Oc4jMount /b2b instance://midtier.qa-pc.us.oracle.com:OC4J_B2B Oc4jMount /b2b/* instance://midtier.qa-pc.us.oracle.com:OC4J_B2B
Save your updates.
Go to the ORACLE_HOME
/dcm/bin
directory.
Enter the following commands:
dcmctl updateConfig dcmctl restart
Test the mod_oc4j
configuration by accessing the user interface tool on the OracleAS Integration B2B host inside your corporate network:
http://HTTP_host/b2b
where HTTP_host
is the hostname of the Oracle HTTP Server outside your corporate network. The OracleAS Integration B2B user interface tool login page should appear.
mod_proxy
is an Oracle HTTP Server module that enables you to configure the Oracle HTTP Server as a proxy server.
Go to the host outside your corporate network on which the Oracle HTTP Server is installed.
Open the ORACLE_HOME
/Apache/Apache/conf/httpd.conf
file.
Remove the #
in front of the following lines:
<IfModule mod_proxy.c> ProxyRequests On Listen 4545 <Directory proxy:*> Order deny,allow Deny from all Allow from .your_domain.com </Directory> </IfModule>
Change 4545
to the proxy port number you want to use.
Change Allow
from
.your_domain.com
to specify the host or domain inside your corporate network to permit to send messages to remote trading partners outside your corporate network. These messages pass through the Oracle HTTP Server outside your corporate network before going to remote trading partners.
For example, if an OracleAS Integration B2B host named db_sales
must communicate with remote trading partners outside your corporate network, specify the following:
Allow from db_sales.us.oracle.com
If you have multiple OracleAS Integration B2B hosts in a domain named us.oracle.com
that must communicate with remote trading partners outside your corporate network, specify the following:
Allow from .us.oracle.com
Save your updates.
Go to the ORACLE_HOME
/opmn/bin
directory.
Restart the Oracle HTTP Server outside your corporate network:
opmnctl stopproc ias-component=HTTP_Server opmnctl startproc ias-component=HTTP_Server
Go to the host inside your corporate network on which OracleAS Integration B2B and Oracle HTTP Server are installed.
Open the ORACLE_HOME
/ip/config/tip.properties
file.
Provide values for the proxy hostname and the proxy port:
oracle.tip.adapter.b2b.ProxyHost=ProxyHost oracle.tip.adapter.b2b.ProxyPort=ProxyPort
where ProxyHost
is the name of the host on which the Oracle HTTP Server outside your corporate network is running and ProxyPort
is the port number configured with the Listen
parameter specified in Step 4.
Note: You can also edit these parameters from the Server Properties page of Oracle Enterprise Manager 10g Application Server Control Console. See Oracle Application Server Integration B2B User's Guide for instructions on accessing and editing the Server Properties page. |
Go to the ORACLE_HOME
/opmn/bin
directory.
Restart the Oracle HTTP Server inside your corporate network:
opmnctl stopproc ias-component=HTTP_Server opmnctl startproc ias-component=HTTP_Server
Note: You must specify the host name and endpoint address of the Oracle HTTP Server outside your corporate network on the Create Trading Partner : Transport page of the OracleAS Integration B2B user interface tool. See Table 3-1 for more details. |
You can also add secure socket layer (SSL) support to your OracleAS Integration B2B trading partner environment. Figure 3-3 shows the tasks to perform to configure SSL support.
The tasks shown in Figure 3-3 are described in the following sections:
You can configure SSL support for remote trading partner communication with the Oracle HTTP Server through either of the following components:
Oracle Enterprise Manager 10g Application Server Control Console. See the Oracle Application Server Administrator's Guide for additional details.
Oracle Process Manager and Notification Server (OPMN). Follow these procedures:
Go to the host outside your corporate network on which the Oracle HTTP Server is installed.
Open the ORACLE_HOME
/opmn/conf/opmn.xml
file.
Go to the following section:
<ias-component id="HTTP_Server">
...
<data id="start-mode" value="ssl-disabled"/>
...
</ias-component>
Change ssl-disabled
to ssl-enabled
.
Save your updates.
Go to the ORACLE_HOME
/dcm/bin
directory.
Enter the following commands:
dcmctl updateConfig dcmctl restart
Go to the ORACLE_HOME
/opmn/bin
directory.
Enter the following commands:
Test the SSL configuration by accessing the OracleAS Integration B2B user interface tool inside the corporate network.
https://HTTP_host/443/
where HTTP_host
is the hostname of the Oracle HTTP Server outside your corporate network and 443
is the default SSL port.
Note: You must also obtain and use an SSL certificate. Obtain a certificate from a certificate authority. Not performing this task means that you are not using a real certificate. |
You must also enable SSL support in the OracleAS Integration B2B user interface tool for both host and remote trading partners. OracleAS Integration B2B includes a Create Trading Partner wizard that enables you to perform these tasks (known as communication capabilities in the user interface tool). Table 3-1 provides an overview of these tasks and provides references to sections of the Oracle Application Server Integration B2B User's Guide that describe how to perform these tasks.
Table 3-1 SSL Tasks in OracleAS Integration B2B User Interface Tool
Part | Task | Chapter in User Guide | Section in Chapter |
---|---|---|---|
1 | Assign SSL for transport security with the Create Trading Partner wizard for both the host and remote trading partners: |
|
|
|
|
Chapter 7, "Creating Trading Partners" | "Page 4: Delivery Channel Page" |
|
|
Chapter 7, "Creating Trading Partners" | "Page 6: Transport Page" |
2 | Perform these host trading partner tasks: |
|
|
|
|
Chapter 8, "Managing Trading Partners" | "Managing the Host Trading Partner Wallet Password" |
|
|
Chapter 13, "System Management with Oracle Enterprise Manager 10g" | "Oracle Application Server Integration B2B Middle-Tier Instance Server Properties" |
3 | Create a remote trading partner certificate in either of two ways: |
|
|
|
|
Chapter 7, "Creating Trading Partners" | "Page 5: Document Exchange Page" |
|
|
Chapter 8, "Managing Trading Partners" | "Managing Remote Trading Partner Certificates" |
You must configure the wallet for the host trading partner.
Start Oracle Wallet Manager on the OracleAS Integration B2B inside your corporate network:
On... | Then... |
---|---|
Solaris, Linux, or HP-UX | Enter the following command:
|
Windows | Select Start > Programs > Oracle - Home_Name > Integrated Management Tools > Wallet Manager |
Click Wallet > Open.
Go to ORACLE_HOME
/Apache/Apache/conf/ssl.wlt/default
.
Click OK.
Enter the password to open the wallet. This is the same wallet password that you specified in the OracleAS Integration B2B user interface tool. (See Table 3-1.)
Click Operations > Export Certificate Request.
Export the file to a certificate.
Open the ORACLE_HOME
/ip/config/tip.properties
file.
Set the following parameter using these operating system conventions:
For Windows environments (note the double slashes):
oracle.tip.adapter.b2b.WalletLocation = file:C:\\Documents and Settings\\jk\\ORACLE\\WALLETS\\ora_wallet.txt
For UNIX environments:
oracle.tip.adapter.b2b.WalletLocation = file:/ade/jknair_b2bdev/oracle/work/genwallt/client/ora_wallet.txt
See Also: Oracle Application Server Integration B2B User's Guide for instructions on using the Oracle Enterprise Manager 10g Application Server Control Console as an alternative method for specifying the wallet location parameter value described in Step 9 |
Verify that you can access the OracleAS Integration B2B user interface tool, Oracle Enterprise Manager 10g Application Server Control Console, and transport servlet from the host on which OracleAS Integration B2B is installed. Table 3-2 provides access instructions.
Table 3-2 Accessing OracleAS Integration B2B Components
To Access The... | Enter This URL... | Enter This User Name... | Enter This Password... |
---|---|---|---|
OracleAS Integration B2B user interface tool |
http://hostname:port/b2b port is the port number OracleAS Integration B2B uses. The following sources identify the OracleAS Integration B2B port number to use:
|
admin
|
ias_admin
|
Oracle Enterprise Manager 10g Application Server Control Console | http:// hostname : port
|
ias_admin
|
ias_admin
|
Transport servlet | http:// hostname : port /b2b/transportServlet
This page lists the remote method invocation (RMI) ports associated with the transport servlet. Note: This RMI information is defined in the See Also: "Troubleshooting Transport Exception Errors Caused by Port Mismatches" |
N/A | N/A |
See Also: Oracle Application Server Integration B2B User's Guide for additional details about the OracleAS Integration B2B user interface tool, the Oracle Enterprise Manager 10g Application Server Control Console, and the transport servlet |
Note: Perform the following installation procedures if you have purchased the license for using the OracleAS Integration B2B - EDI option. This tool enables you to create and customize electronic data interchange (EDI) X12 and EDI EDIFACT business documents that you import into the OracleAS Integration B2B user interface tool. |
The OracleAS Integration B2B - Document Editor is included in the SpecBuilder.zip
file at the root of the OracleAS Integration CD-ROM in your Oracle Application Server kit. This tool enables you to create integrations between OracleAS Integration B2B trading partners that use EDI X12 and EDI EDIFACT.
Follow these instructions to install the OracleAS Integration B2B - Document Editor:
Unzip SpecBuilder.zip
.
Run setup.exe
to install the OracleAS Integration B2B - Document Editor.
You can install and run multiple OracleAS Integration B2B versions on the same host, as long as they are installed in different Oracle homes. For these additional OracleAS Integration B2B versions to function correctly, you must edit their port number and instance settings in the following configuration files after installation:
web.xml
(edit from the command prompt)
tip.properties
(edit from the Server Properties page of the Oracle Enterprise Manager 10g Application Server Control Console)
opmn.xml
(edit from the Process Management page of the Oracle Enterprise Manager 10g Application Server Control Console). This file only requires editing if you install the second OracleAS Integration B2B version while the first OracleAS Integration B2B version is not running.
Install J2EE and Web Cache and OracleAS Integration B2B into the same Oracle home for the first time on the host.
Install a second J2EE and Web Cache and OracleAS Integration B2B into a different Oracle home directory on the same host.
Open the web.xml
file for the transport server of the Oracle HTTP Server. On Windows, for example, this file is located in the J2EE_HOME
\OC4J_B2B\applications\b2b\ip\WEB-INF
directory.
Change the RMI port number and RMI instance name:
<servlet> <servlet-name> transportServlet </servlet-name> <servlet-class> oracle.tip.transport.basic.TransportServlet </servlet-class> <init-param> <param-name>rmiHost</param-name> <param-value>localhost</param-value> </init-param> <init-param> <param-name>rmiPort</param-name> <param-value>1111</param-value> </init-param> <init-param> <param-name>instanceName</param-name> <param-value>IP1</param-value> </init-param> .... .... </servlet>
Save your changes and close the file.
Go to the following URL to access the Oracle Enterprise Manager 10g Application Server Control Console for the second OracleAS Integration B2B installation:
http://hostname:port/
where:
hostname
is the name of the host on which the second OracleAS Integration B2B middle-tier instance is installed
port
is the number assigned during the second OracleAS Integration B2B installation. The following sources also identify the port number used to access the Oracle Enterprise Manager 10g Application Server Control Console:
Enter the following details to access the Oracle Enterprise Manager 10g Application Server Control Console of the second OracleAS Integration B2B installation:
Field | Value |
---|---|
Username | ias_admin |
Password | password
This is the password you specified during the second J2EE and Web Cache installation and OracleAS Integration B2B installation for the ias_admin user. |
The Oracle Application Server home page appears.
Click B2B in the Name column of the System Components table.
Click Administration.
Click Server Properties.
The Server Properties page appears.
Change the following parameter values to match those set in the web.xml
file in Step 4.
Parameter | Description | Example |
---|---|---|
Remote Method Invocation (RMI) Port | Enter a port number not currently in use. | 1111 |
RMI Instance Name | Enter an instance name that is different from the first OracleAS Integration B2B installation. | IP1 |
Click OK.
If you installed the second OracleAS Integration B2B while the first OracleAS Integration B2B was not running, you must edit the opmn.xml
file by performing Steps 13a through 13d. Otherwise, go to Step 14.
Return to the Oracle Application Server home page in the Oracle Enterprise Manager 10g Application Server Control Console.
Click B2B.
Click Stop All in the General section to stop OracleAS Integration B2B.
Click Restart All to restart OracleAS Integration B2B.
Exit the Oracle Enterprise Manager 10g Application Server Control Console.
Verify your changes by connecting to the transport servlet of Oracle HTTP Server:
http://hostname:port//b2b/transportServlet
If you are able to connect, your changes for the second OracleAS Integration B2B installation were successful.
Repeat these steps for any additional OracleAS Integration B2B installations on the same host.
This section describes how to troubleshoot OracleAS Integration B2B installation problems.
Troubleshooting OracleAS Integration B2B Schema Password Failure During Installation
Troubleshooting Transport Exception Errors Caused by Port Mismatches
Troubleshooting Integration B2B Configuration Assistant Failure
If you do not select the Identity Management Access option during OracleAS Integration B2B installation, the following error can occur when specifying the OracleAS Integration B2B schema password on the Specify Metadata Repository for Integration B2B screen:
An error occurred while validating the password of the Integration B2B schema. Either the schema does not exist in the database or an invalid password has been specified
This error occurs because the schema password must first be unlocked and changed.
See Also: "Step 2: Unlock or Obtain the OracleAS Integration B2B Schema User Password" for instructions on unlocking and changing the B2B schema password |
You can receive a transport exception error during OracleAS Integration B2B runtime stating that the RMI server was not found. This error occurs because the RMI port setting in the ORACLE_HOME
/ip/config/tip.properties
file does not match the RMI port setting in the ORACLE_HOME
/OC4J_B2B/applications/b2b/ip/WEB-INF/web.xml
file for the transport servlet of the Oracle HTTP Server (for example, both set as 1110
).
This port setting mismatch can occur during installation. To prevent this error, ensure that both port settings are the same.
For example, assume the RMI port setting in the web.xml
file is 1110 and the RMI port setting in the tip.properties
file is 1111 on the host of a buyer engaging in a business transaction using RosettaNet. If a RosettaNet partner interface process (PIP) 3A4 purchase order request message is sent from the buyer to a seller, the responding purchase order acknowledgment message sent from the seller to the buyer fails and a transport exception error appears stating that the RMI server was not found. If the RMI port in the tip.properties
file is updated to 1110 on the host of the buyer, the responding purchase order acknowledgment message is successfully received by the buyer with no transport exception error.
If you must make this update, Oracle recommends that you do not manually edit the tip.properties
file with a text editor. Instead, edit the RMI port setting from the Server Properties page of Oracle Enterprise Manager 10g Application Server Control Console.
See Also: Chapter 13, "System Management with Oracle Enterprise Manager 10g" for instructions on editing the RMI port setting in the Server Properties page of Oracle Enterprise Manager 10g Application Server Control Console |
If the Integration B2B Configuration Assistant described in Step 2 fails during installation, perform the following procedures to run this assistant manually.
See the latest installActions
YEAR_MM_DD_TIME
.log
file located in the oraInventory_location
/
logs
directory for UNIX or the Program Files\Oracle\Inventory\logs
directory for Windows.
Check for OracleAS Integration B2B error codes (AIP-52000
to AIP-52999
) in the log file.
AIP - 52000 Updating Repository information has failed. Cause : ORACLE_HOME/config/iasschema.xml may have Integration B2B specific entries. Make sure that iAS 10.1.2 middle tier is installed properly. AIP - 52001 Integration B2B Seed creation has failed Cause : The following could be the reason 1.Oracle Application Server Metadata Repository may not contain Integration B2B schema. 2.Invalid Integration B2B schema password is passed to Configuration Tool. 3.Integration B2B metadata is not in a stable state. Recreate Oracle Application Server Metadata Repository AIP - 52003 Integration B2B Instance seed creation failed Cause : The following could be the reason 1.iAS instance name is already seeded in the metadata repository. 2.Oracle Application Server Metadata Repository may not contain Integration B2B schema. 3.Invalid Integration B2B schema password is passed to Configuration Tool. 4.Integration B2B metadata is not in a stable state. Recreate Oracle Application Server Metadata Repository AIP - 52004 Updating targets.xml has failed Cause : targets.xml is corrupt in the ORACLEHOME/sysman/emd directory
Correct the problem and manually rerun the Integration B2B Configuration Assistant and all other configuration assistants that failed.
Set up the environment by running the following script in the ORACLE_HOME
/ip/install
directory:
On... | Run This Script... |
---|---|
Solaris, Linux, or HP-UX |
|
Windows | setenv.bat
|
This sets the necessary CLASSPATH
environment for the Integration B2B Configuration Assistant.
Run the Integration B2B Configuration Assistant from the command prompt:
java oracle.tip.install.ConfigTool oracle_home organization_name ip_passwd wf_passwd dbhost dbport dbservicename ias_instancename iasadmin_passwd globalDBName oidUserName oidPassword true
Some parameters specified are only valid under a specific configuration. In cases where they are not valid (that is, the question was not asked or an answer was not provided during installation), enter NULL
as the argument.
For... | Specify This Value... |
---|---|
oracle_home
|
The Oracle home directory path |
organization_name
|
NULL
|
b2b_passwd
|
The OracleAS Integration B2B schema passwordFoot 1 |
dbhost
|
The Oracle Application Server Metadata Repository hostnameFootref 1 |
dbport
|
The Oracle Application Server Metadata Repository port numberFootref 1 |
dbservicename
|
The Oracle Application Server Metadata Repository database service nameFootref 1 |
ias_instancename
|
The Oracle Application Server middle-tier instance name
The instance name is found in |
iasadmin_passwd
|
The Oracle Application Server middle-tier instance administrator (ias_admin ) password
|
globalDBName
|
The global database name for the Oracle Application Server Metadata Repository registered in Oracle Internet Directory (for example, iasdb.us.oracle.com )
|
oidUserName
|
The Oracle Internet Directory user name |
oidPassword
|
The Oracle Internet Directory password |
true
|
This parameter is required for a successful installation. |
NULL
. NULL
is case insensitive.See the ORACLE_HOME
/cfgtoollogs
directory for the log files that describe how to run the other failed configuration assistants.
OracleAS Integration B2B is installed into a subdirectory of your Oracle home directory named ip
. Table 3-3 shows the subdirectories created in the OracleAS Integration B2B home directory:
Table 3-3 Subdirectory Structure of ip Root Directory
Note: If you want to deinstall and reinstall OracleAS Integration B2B in the same Oracle home, ensure that you first remove files and subdirectories underORACLE_HOME /ip before performing the OracleAS Integration B2B reinstallation. The only directory that does not need to be removed is the log directory. Other than this directory, the ORACLE_HOME /ip directory must be empty for reinstallations into the same Oracle home.
|
Follow these instructions to deinstall OracleAS Integration B2B 10.1.2:
Start Oracle Universal Installer.
Click Deinstall Products.
Expand the Oracle home that contains the products to deinstall.
Select OracleAS Integration B2B.
Click Yes when prompted.
The oracle.tip.intg.Typical.rsp
response file for silent and noninteractive installations is available in the stage/Response
directory on Disk 1 of the OracleAS Integration CD-ROM. This file lists and describes each available variable. Three additional installation file templates are also provided. The file template to use is based on the configuration of the Oracle Application Server middle tier and the installation option you want to select for Step 10 of "Beginning the Installation".
Table 3-4 Response Files
Response File | Use This File If... |
---|---|
b2b_with_im.rsp
|
You selected Identity Management Access during J2EE and Web Cache installation.
This file lets you specify the login credentials for the Oracle Internet Directory with which you registered the Oracle Application Server middle tier during J2EE and Web Cache installation. |
b2b_mr_with_oid.rsp
|
You did not select Identity Management Access during J2EE and Web Cache installation, but want to select Identity Management Access during OracleAS Integration B2B installation.
This file lets you register the Oracle Application Server middle tier with Oracle Internet Directory and specify the login credentials for Oracle Internet Directory. |
b2b_with_mr.rsp
|
You want to select only Oracle Application Server Metadata Repository during OracleAS Integration B2B installation and did not select Identity Management Access during J2EE and Web Cache installation. |
See Also: Oracle Application Server Installation Guide for your operating system for complete instructions on using response files |