This section describes supported operating systems, mandatory ESRs, and prerequisite supporting files and add-ons.
The Sun B2B Suite requires an Oracle database and a directory server for LDAP.
The following Oracle databases are compatible.
Oracle 9i (9.0.1, 9.1, 9.2)
Oracle 10g (10.1 and 10.2)
The following LDAP servers are compatible
Sun Java System (Sun ONE) Directory Server version 5.2
Directory Server version 6
Sun B2B Suite 5.1.1 is compatible with the following operating system platforms.
Sun Solaris 8 (on SPARC), 9 (on SPARC), and 10 (on SPARC) with required patches
HP-UX v11i (11.11) on PA-RISC, and 11i v2.0 (11.23) on Itanium with required patches and parameter changes
IBM AIX 5L, versions 5.2 and 5.3, with required maintenance level patches
Microsoft Windows 2000 SP3 and SP4, Windows XP SP1 and SP2, and Windows Server 2003 SP1
Red Hat Enterprise Linux AS 4 (on Intel x86)
Minimum hardware requirements are covered in detail in the Sun Java Composite Application Platform Suite Installation Guide.
Before running any of the B2B sample projects on a Windows machine, make sure that you have at least 2 GB of available RAM to ensure optimal performance.
This section lists installation dependencies, including software fixes (ESRs), and add-ons.
You must install the following ESRs if you intend to run the Sun B2B Suite on top of Java CAPS 5.1.2.
Java CAPS 5.1.2 ESR 104326 for eGate Integrator, Enterprise Designer, on all supported platforms:
When there is a general exception in a Java Collaboration, the error message appears, but the stack trace is missing from the server log. After this ESR is installed, the stack trace is written to the server log, as it was in the previous version of the product.
Java CAPS 5.1.2 ESR 104492 for the LDAP eWay on all supported platforms:
If the LDAP server goes down during runtime, it cannot process input files, and an error message is generated. This occurs even after the server comes back up and is caused by the LDAP being unable to reconnect to the Logical Host until it is completely restarted. After this ESR is installed, you will see when the LDAP server is restarted and the eWay connection is established. Pending data is then be processed automatically, without having to restart the Logical Host.
Java CAPS 5.1.2 ESR 104562 for eGate Integrator, Logical Host, on all supported platforms:
When publishing a large number of relatively large messages, the JMS server sometimes stops sending messages to the clients. This has been noticed particularly on Sun Solaris 10 platforms. After this ESR is installed, the JMS server no longer stops sending messages under the stated conditions.
Java CAPS 5.1.2 ESR 105190 for eInsight on all supported platforms:
When an eInsight Business Process is configured to persist for reporting and a sub process is invoked by the Business Process, the Business Process may fail to respond after invoking the sub process. This is accompanied by BPEL exceptions. After this ESR is installed, the above issue no longer occurs.
Java CAPS 5.1.2 ESR 106011 for eGate Integrator, Enterprise Designer, on UNIX platforms:
The runtime code (EAR file) generated by commandline codegen on UNIX does not work correctly. After this ESR is installed, the EAR file generated by commandline codegen on UNIX works correctly.
Java CAPS 5.1.2 ESR 6613784 for eInsight Business Process Manager on all supported platforms:
When the WSDL has many operations that share one fault message with the same fault name, the fault content is set on the wrong fault container. After this ESR is installed, the message is caught in the correct fault handler. Also, the WLM pagination loses focus on the task during checkin/checkout and execute operations. After this ESR is installed, the focus remains on the task that is being worked on by the user.
To run the Sun B2B Suite on Java CAPS 5.1.3, you must be running Java CAPS 5.1.3 with Update 1.
Before installing the Sun B2B Suite .sar files, you must install a collection of supporting .sar files and install them in the prescribed order.
Before uploading eXchange.sar, you must first upload:
Before uploading AS2_Manager.sar or ebXML_Manager.sar, you must first upload:
Before uploading X12_Manager.sar or HIPAA_Manager.sar, you must first upload:
Before uploading protocol _OTD_Validation_ version.sar, you must first upload: