IBM i clustered server: Create remote DB2 for IBM i databases
A remote database resides on a different system than WebSphere Portal. When you use a remote server, manually create the databases that are required by WebSphere Portal.Before you begin:
- The user ID and password used must have the authority to create database libraries on the remote System i5machine.
- For every property instance of a database that uses *LOCAL/schema, replace it with HostName/schema.
For example, the default database and database library name for WebSphere Portal release domain is release.DbName=wpsdb. To create this database library on a remote database, change the default value to release.DbName=hostname/wpsdb
Prerequisites
IBM i clustered server: Modify DB2 for IBM i database properties
IBM i clustered server: Create DB2 for IBM i user profilesTo create all the domain database libraries:
- Start a 5250 session on the remote database machine.
- Type the i command WRKRDBDIRE to display the Relational Database Directory Entry for Remote Location *LOCAL and make a note of the value displayed.
- Sign off from the 5250 session.
- Start a 5250 session on the local machine where WebSphere Portal is installed.
- Create a Relational Database Directory Entry on the local system for the remote system using i command WRKRDBDIRE.
- Add an entry with the following values:
Relational database
The remote relational database. Use the value noted from the prior step.
Relational database aliasThe hostname. Use the short TCP/IP hostname of the remote system
Remote locationThe domain qualified hostname. Use the full TCP/IP hostname of the remote system
TypeIP
Port number or service nameDRDA
Remote authentication methodPreferred method: ENCRYPTED
Allow lower authentication: ALWLOWER
- Create the required DB2 packages on the remote database machine by running the following command from the local machine:
JAVA CLASS(com.ibm.db2.jdbc.app.DB2PackageCreator) PARM('rdb_alias' 'userid' 'password') PROP((jdbc.drivers 'com.ibm.as400.access.AS400JDBCDriver'))
..where rdb_alias matches the name of the Relational Database Entry you created in step 2, where userid is the database administrator user ID on the remote machine, and where password is the database administrator password on the remote machine.
The output should be: Java program completed
- Press F3 to exit Java Shell Display.
- Sign off from the 5250 session.
- Start a 5250 session on the remote database machine.
- Verify the required DB2 packages were created by running the command WRKOBJ OBJ(QGPL/QSQCL*) OBJTYPE(*SQLPKG)
The output should be:
Opt Object Type Library Attribute Text QSQCLIPKGA *SQLPKG QGPL PACKAGE QSQCLIPKGC *SQLPKG QGPL PACKAGE QSQCLIPKGL *SQLPKG QGPL PACKAGE QSQCLIPKGN *SQLPKG QGPL PACKAGE QSQCLIPKGS *SQLPKG QGPL PACKAGE
- Start a 5250 session on the local machine where WebSphere Portal is installed.
cd WP_PROFILE/ConfigEngine
- Press Enter.
- Change the property values in the configuration properties files before entering the following on the command line:
ConfigEngine.sh create-database
- Press Enter.
Parent
IBM i clustered server: Prepare DB2 for IBM i
Previous
IBM i clustered server: Create DB2 for IBM i user profiles
Next topic
IBM i clustered server: Transfer DB2 for IBM i manually