By default, the database settings are set for the Derby database on ITXA. To use a different database for ITXA and for the Trading Partner UI, update the configuration settings. To use the Trading Partner UI, you must also configure the database settings that are used by your web server.
About this task
The database configuration is used by the ITXA command line utilities, and by the IBM® Integration
Bus nodes and the UI for accessing ITXA trading partner information.
Prerequisite:
If moving to a DB2®, Oracle, or SQL Server database and the database does not exist, contact your database administrator to create a database. The database must be created before you deploy any packs, or (if not deploying packs) before you run an spedbinit command.
Note: 10.0.1.9 and later versions of ITXA no longer include the Derby client or support the Derby database.
Procedure
-
If you are not using the installed Derby database, update the database configuration to point to the new database: edit the /spe_install_dir/dbprops.cfg file according to the database type that you are using.
-
Make sure the JDBC drivers for the new database are included in the CLASSPATH for ITXA and have permission to execute.
For example, the driver filename for DB2 is db2jcc4.jar, and it is included in the DB2 installation directories.
The JDBC driver file is typically included in the necessary CLASSPATH under these conditions:
Example for DB2 database:
- Copy db2jcc4.jar to C:\IBM\Standards Processing Engine n.n.n\jars and start a new console session.
- Copy db2jcc4.jar DB2 SQLLIB to C:\IBM\Standards Processing Engine n.n.n\tpuiserver\usr\servers\defaultServer\apps\spe.war\WEB-INF\lib and restart the Trading Partner UI.
-
From an ITXA console session, run the appropriate spedeploy-packs command for your pack installation and deployment scenario:
-
Update the tpuiserver/usr/servers/defaultServer/server.xml file for your UI server configuration.
This connection is used to access the database tables that the Trading Partner UI uses to manage login accounts and roles.
where
- defaultServer
- Server configuration name
Example:
This entry tells the web server where to find the database for non-SSL connection:
<dataSource id="tenx" jndiName="jdbc/tenx">
<jdbcDriver libraryRef="DB2Lib"/>
<properties.db2.jcc createDatabase="false" databaseName="spe201" password="passw0rd" portNumber="50000" serverName="localhost" shutdownDatabase="false" user="administrator" currentSchema="dbCurrentSchema"/>
</dataSource>
<library id="DB2Lib" name="DB2Lib">
<fileset dir="${server.config.dir}/apps/spe.war/WEB-INF/lib" includes="db2jcc4.jar"/></library>
<dataSource id="tenx" jndiName="jdbc/tenx">
<jdbcDriver libraryRef="DB2Lib"/>
<properties.db2.jcc createDatabase="false" databaseName="spe201" password="passw0rd" portNumber="50001" serverName="localhost" shutdownDatabase="false" user="administrator" currentSchema="dbCurrentSchema" sslConnection="true"/>
</dataSource>
<library id="DB2Lib" name="DB2Lib">
<fileset dir="${server.config.dir}/apps/spe.war/WEB-INF/lib" includes="db2jcc4.jar"/></library>
See Configuring a web server for the Trading Partner UI.
-
Stop and start the Trading Partner user interface and any runtime applications that are calling SPE.
-
If you are using ITX Design Studio or the Sterling B2B Integrator Map Editor to deploy or test maps on ITXA, update the database connection preferences for those design tools.
For example, to change Design Studio preferences for ITXA to use DB2 instead of Derby, configure settings similar to the following, as well as changing the user ID and login:
jdbc:db2://server:50000/spe201
com.ibm.db2.jcc.DB2Driver
-
(DB2 databases only) To prevent issues that can result when a DB2 transaction log is full, you can increase the size and number of log files.