|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Linux x86 B19312-04 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Linux x86 B19312-04 |
|
|
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 12.1.3, "Self-service API for Creating Trading Partners and Agreements"
Section 12.1.4, "Oracle Application Server Clustering and Integration B2B"
Section 12.1.7, "OracleAS Integration B2B Pages in Oracle Enterprise Manager"
Section 12.1.8, "Configuring OracleAS Integration B2B in Enterprise Environments"
If you see that redeployment does not reflect your design-time data changes (for example, a change in the XPath expression is not recognized), restart the B2B server as follows:
opmnctl restartproc process-type=B2BServer
Purging a retired configuration removes the associated run-time data. Oracle recommends that you do a database archive of run-time data before purging.
Only creating trading partners and agreements is supported, not updating or deleting. Also, RosettaNet collaborations are not supported in this API.
Oracle Application Server Integration B2B cannot be installed on a clustered application server middle-tier environment. Also, after you install Oracle Application Server Integration B2B on a middle tier, you cannot add it as a node on a cluster.
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.
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 topics:
This section describes corrections and clarifications to Oracle Application Server Integration B2B User's Guide, 10g Release 2 (10.1.2.0.2), part number B19370-01.
Chapter: 3, "Supported Protocols" (supp_protos.htm)
Heading: "Document Protocols"
Page: online version
The first paragraph in this section should read as follows:
The document protocol defines the document type of the message payload. Business protocols can have multiple document protocols. Document protocols follow the hierarchy shown in Figure 3-1.
Chapter: 11, "Managing Callouts" (callouts.htm)
Heading: "Tutorial: Adding Callout Usages to the RosettaNet over the Internet Transaction"
Page: 11-16 and online version
The first paragraph in this section should read as follows:
This tutorial assumes you have completed the tutorial described in "Tutorial 1: Setting Up a RosettaNet over the Internet Transaction."
Chapter: 11, "Managing Callouts" (callouts.htm)
Heading: "Tutorial: Adding Callout Usages to the RosettaNet over the Internet Transaction"
Page: 11-17 and online version
This procedure has a missing step without which the tutorial does not work.For the sending party server (Acme in the example), the remote trading partner (GlobalChips in the example) must have a Trading Partner Identifier - EDI Location Code set as PARTY_SITE_ID (3101 - as in the example) in the enqueued message on the ECXMSG queue. This does not have to be selected in the agreement; however, it must be set for the remote trading partner. Without the preceding Trading Partner Identifier, the enqueued OAG PO message cannot find the to-party information.
