WebSphere Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows


 

Creating remote databases

A remote database resides on a different system than WebSphere Portal Express. When you use a remote server, manually create the databases that are required by WebSphere Portal Express.

Before you begin:

To create all the domain database libraries, perform the following steps:

  1. Start a 5250 session on the remote database machine.
  2. Type the i5/OS 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 Express is installed.
  5. Create a Relational Database Directory Entry on the local system for the remote system using i5/OS 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. Temporarily change the CCSID for jobs to 37 (an example for US English environment) by running the following command: CHGJOB CCSID(37)
  8. 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
  9. Press F3 to exit Java Shell Display.
  10. Sign off from the 5250 session.
  11. Start a 5250 session on the remote database machine.
  12. 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
  13. Start a 5250 session on the local machine where WebSphere Portal Express is installed.
  14. On the command line type STRQSH or SBMJOB CMD(STRQSH)

    Use SBMJOB to submit the Qshell script as a batch job to run in *BASE pool when *INTERACT pool does not have 1GB or more of allocated memory.

  15. Click Enter.
  16. On the command line, enter the following to change directory to the UserData path: cd wp_profile_root/ConfigEngine.
  17. Click Enter.
  18. Change the property values in the configuration properties files before entering the following on the command line: ConfigEngine.sh -profileName profile_root create-database -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

    where profile_root is the name of your WebSphere Application Server profile where WebSphere Portal Express is installed.

  19. Click Enter.
Parent topic: Preparing DB2 for i5/OS Previous topic: Create user profiles
Library | Support | Terms of use |