|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
|
Previous |
Next |
This chapter describes issues associated with Oracle Application Server Integration B2B (OracleAS Integration B2B). It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
Section 13.1.3, "Using Callouts with a DTD-Based XML Document"
Section 13.1.4, "Custom Protocol with SMTP Transport Does Not Work in an End-to-End Scenario"
Section 13.1.5, "SETENV Script Does Not Add the Java Subdirectory in the Correct ORACLE_HOME Path"
Section 13.1.7, "OracleAS Integration B2B Pages in Oracle Enterprise Manager"
Section 13.1.8, "Configuring OracleAS Integration B2B in Enterprise Environments"
Logging in as the b2b user, without first assigning a role to the b2b user, produces a blank page. You must first log in as admin and assign a role to the b2b user. Then the b2b user can log in, with functionality based on the assigned role.
SMTP for EDI is not supported in Oracle Application Server 10g Release 2 (10.1.2).
If you invoke a callout with a DTD-based XML document, you must include the following declaration:
standalone="yes" to <?xml ...?>
Not including this declaration results in the following callout runtime exception error:
java.net.MalformedURLException
The end-to-end scenario using Custom Protocol with SMTP transport does not work. However, the buyer can send a message and the seller can receive a message independently.
The ip/install/setenv.bat script does not add the correct directory structure, which is ORACLE_HOME/jdk/bin. Instead it incorrectly adds a nonexistent directory, ORACLE_HOME/Apache/jdk/bin, to the path for the Java executable. If another version of Java is installed in the environment, then the enqueue scripts with the tutorials do not work properly.
You cannot update the password for the predefined admin user. Instead, create a new user and assign it the Administrator role. You can update the password for this new user.
If you are using OracleAS Integration B2B in a non-English language, note that parts of some OracleAS Integration B2B pages in Oracle Enterprise Manager 10g Application Server Control appear only in English.
In a typical Oracle Application Server environment, the Oracle Application Server middle tier with its installations of J2EE and Web Cache and OracleAS Integration B2B communicates with the OracleAS Infrastructure tier and its installation of the OracleAS Metadata Repository.
You can also configure OracleAS Integration B2B to run in enterprise environments. Enterprise environments are slightly different than the typical Oracle Application Server environment in that they include an additional middle tier known as a web tier that is installed and configured outside your corporate network. The web tier includes the J2EE and Web Cache install type. However, there is no installation of OracleAS Integration B2B and no applications are deployed on the web tier. The web tier is used only to exchange HTTP requests (through the Oracle HTTP Server) with the Oracle Application Server middle tier (and its installations of J2EE and Web Cache and OracleAS Integration B2B). The Oracle Application Server middle tier, in turn, communicates with the OracleAS Infrastructure tier and its installation of the OracleAS Metadata Repository.
To use OracleAS Integration B2B in enterprise environments with a web tier, you must perform the following configuration tasks:
On the Oracle Application Server middle tier (with its installations of J2EE and Web Cache and OracleAS Integration B2B):
Go to the ORACLE_HOME/opmn/conf directory.
Use a text editor to open opmn.xml.
Find the entry for OC4J_B2B.
Change the range of AJP Ports from 3301-3400 to 3301-3301.
This enables OC4J_B2B to run on just one AJP port.
Save your changes.
On the web tier (with its installation of only J2EE and Web Cache):
Go to the ORACLE_HOME/Apache/Apache/conf directory.
Use a text editor to open mod_oc4j.conf.
Add the following entries near the end of the file, but before the </IfModule> line. These entries enable AJP routing to communicate with the configured OC4J_B2B:
Oc4jMount /b2b ajp13://hostname:ajpport Oc4jMount /b2b/* ajp13://hostname:ajpport
where:
hostname is the name of the host on which the Oracle Application Server middle tier is installed
ajpport is the AJP port range that you configured on the Oracle Application Server middle tier
Save your changes.
|
See Also: Oracle Application Server Integration B2B Installation Guide for additional instructions on configuring a web tier (and its Oracle HTTP Server) outside your corporate network |
This section describes installation issues and workarounds. It includes the following topics:
If secure socket layer (SSL) is not enabled on Oracle Internet Directory (OID) but the J2EE midtier instance is registered to OID (through manual configuration), then OracleAS Integration B2B installation fails.
If you are installing OracleAS Integration B2B on a Red Hat Enterprise Linux 2.1 Update5 system, the OPMN Configuration Assistant may fail because it cannot start up HTTP_Server. This is due to an issue in Update5 that will be fixed in Update6 (within the e.57 kernel). The workaround to get around this failure in Update5 is the following:
Check if orphaned httpd processes are left behind by executing the following command:
$ ps -efw | grep your_j2ee_oracle_home/Apache
This should return processes where the parent process id is 1, similar to the following:
oracle 4973 1 0 Jan05 ? 0:00:00
/project1/j2ee/ohome/Apache/Apache/bin/httpd
If there are orphaned httpd processes, get the pid of those processes and kill them using the following command:
$ kill -9 pid
Go back to the Oracle Universal Installer (OUI) installation session and click Retry to retry the OPMN Configuration Assistant.
This section describes known errors in the documentation. It includes the following topic:
This section describes corrections and clarifications to Oracle Application Server Integration B2B Installation Guide.
Chapter: 3, "Oracle Application Server Integration B2B Installation Procedures"
Heading: "Directory Structure"
Page: 3-27
The Oracle Application Server Integration B2B Installation Guide is not installed in the ORACLE_HOME/ip/doc directory. This guide is not installed and is only available from the /doc directory of the OracleAS Integration B2B software CD-ROM.
Chapter: 3, "Oracle Application Server Integration B2B Installation Procedures"
Heading: "OracleAS Integration B2B - Document Editor Installation"
Page: 3-21
Step 2 should state the following:
2. Run setup.exe from the Application directory.
When you unzip SpecBuilder.zip, two subdirectories are created, Application and Standards.
