IBM i clustered server: Create remote DB2 for IBM i databases

When we use a remote server, manually create the required databases.

Before beginning:

• The user ID and password used must have the authority to create database libraries on the remote System i5 machine.

• 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. If you wanted 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 groups and assign users for IBM DB2 for i

IBM i clustered server: Create DB2 for IBM i user profiles

To create all the domain database libraries:

1. Start a 5250 session on the remote database machine.

2. Type the IBM i command WRKRDBDIRE to display the Relational Database Directory Entry for Remote Location *LOCAL and make a note of the value displayed.

3. Sign off from the 5250 session.

4. Start a 5250 session on the local machine where WebSphere Portal is installed.

5. Create a Relational Database Directory Entry on the local system for the remote system using IBM i command WRKRDBDIRE.

6. Add an entry with the following values:

   Relational database

   The remote relational database. Use the value noted from the prior step.

   Relational database alias

   The hostname. Use the short TCP/IP hostname of the remote system

   Remote location

   The domain qualified hostname. Use the full TCP/IP hostname of the remote system

   Type

   IP

   Port number or service name

   DRDA

   Remote authentication method

   • Preferred method: ENCRYPTED

   • Allow lower authentication: ALWLOWER

7. 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 createdd 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

8. Press F3 to exit Java Shell Display.

9. Sign off from the 5250 session.

10. Start a 5250 session on the remote database machine.

11. 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
    

12. Start a 5250 session on the local machine where WebSphere Portal is installed.

13. On the command line to change directories: cd WP_PROFILE/ConfigEngine.

14. Press Enter.

15. Change the property values in the configuration properties files before entering the following on the command line: ConfigEngine.sh create-database

16. 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: IBM i clustered server: Grant privileges to IBM DB2 for i database users