Database planning

SPE runs an Apache Derby database by default.

If you are running a database from a different vendor, you must create it before installation. Contact your database administrator to create a database.

Database architecture

SPE maintains trading partner information such as envelopes, control numbers, maps, schemas, and code lists in a database. Certain processing information such as acknowledgement status, duplicate and sequence checking information, and documents waiting to be enveloped are also maintained in this database.

The Trading Partner UI also keeps login account, password, and role information in database tables. Although these tables are typically located in the same database as the trading partner and processing tables, it is possible to put these tables in a separate database. Even if these tables are in a separate database, the Trading Partner UI connects to the main SPE database for the trading partner and processing information.

Multiple SPE instances (nodes) can connect to the same database to create an SPE cluster. The SPE nodes can be on the same server as the database, or may be on different servers. The SPE nodes use a JDBC connection to connect to the database.

Databases in integrations: SPE with Sterling B2B Integrator

When SPE is integrated with Sterling B2B Integrator, SPE database tables can either be in their own unique database or added to the existing Sterling B2B Integrator database.

Clustered environments

Contact technical support in regard to database use in clustered environments.