12 Oracle Application Server Integration B2B

This chapter describes issues associated with Oracle Application Server Integration B2B (OracleAS Integration B2B). It includes the following topics:

Section 12.1, "General Issues and Workarounds"
Section 12.2, "Documentation Errata"

12.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topics:

Section 12.1.1, "B2B User Login Must Have a Role"
Section 12.1.2, "SMTP for EDI Is Not Supported"
Section 12.1.3, "Using Callouts with a DTD-Based XML Document"
Section 12.1.4, "Custom Protocol with SMTP Transport Does Not Work in an End-to-End Scenario"
Section 12.1.5, "SETENV Script Does Not Add the Java Subdirectory in the Correct ORACLE_HOME Path"
Section 12.1.6, "No More than 10 Collaborations or Business Actions Can Be Displayed Under Operational Capabilities"
Section 12.1.7, "No More than 10 Approved Agreements Can Be Displayed"
Section 12.1.8, "Cannot Update the admin User Password"

12.1.1 B2B User Login Must Have a Role

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.

12.1.2 SMTP for EDI Is Not Supported

SMTP for EDI is not supported in Oracle Application Server 10g Release 2 (10.1.2).

12.1.3 Using Callouts with a DTD-Based XML Document

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

12.1.4 Custom Protocol with SMTP Transport Does Not Work in an End-to-End Scenario

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.

12.1.5 SETENV Script Does Not Add the Java Subdirectory in the Correct ORACLE_HOME Path

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.

12.1.6 No More than 10 Collaborations or Business Actions Can Be Displayed Under Operational Capabilities

The Operational Capabilities section of the Business Protocol Details: protocol_name page lists a maximum of 10 collaborations or business actions. If more than 10 collaborations or business actions exist, it is not possible to view them in the user interface.

12.1.7 No More than 10 Approved Agreements Can Be Displayed

A maximum of 10 approved agreements to be deployed during the creation of a configuration can be displayed.

12.1.8 Cannot Update the admin User Password

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.

12.2 Documentation Errata

This section describes known errors in the documentation. It includes the following topic:

Section 12.2.1, "Installation Documentation"

12.2.1 Installation Documentation

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.