Chapter 3 Notes on Installation and Tuning

This section describes new features and modifications to installation and tuning.

Installation

Before uploading either the AS2 Protocol Manager or ebXML Protocol Manager .sar files, you must first upload the SME toolkit components, and you must do so in the same browser session in which you uploaded the delivery protocol. Specifically, when you are about to upload either AS2_Manager.sar or ebXML_Manager.sar, you must first upload the following 5.1.5 SME toolkit .sar files:

• smeks.sar

• SMEWebServices.sar

If you upload another delivery protocol later, but in a different session, you must re-upload both of the 5.1.5 SME toolkit .sar files.

Configuration

There are no changes to the configuration process.

Networking

There is no impact on networking.

Scaling

On typical hardware (Sun Fire™ V440 with four SPARC® CPUs running Solaris 10 with 8 GB of memory), horizontal scalability is improved by up to 45%.

An updated white paper on scaling can be found at http://jcaps-b2b.dev.java.net

Reliability

As part of final verification testing, on typical hardware (Sun Fire V440 with four SPARC CPUs running Solaris 10 with 8 GB of memory), a week-long period of continuous throughput was observed without message loss or downtime, maintaining a throughput of more than 3 transactions per second.

An updated white paper on reliability can be found at http://jcaps-b2b.dev.java.net

Performance

On typical hardware (Sun Fire V440 with four SPARC CPUs running Solaris 10 with 8 GB of memory), throughput of up to 5.26 transactions per second was consistently and repeatedly achieved for both outbound and inbound scenarios.

An updated white paper on performance can be found at http://jcaps-b2b.dev.java.net