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:
- 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 Express 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
- Preparing for creation of databases
- Create user profiles
To create all the domain database libraries, perform the following
steps:
- Start a 5250 session on the remote database machine.
- 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.
- Sign off from the 5250 session.
- Start a 5250 session on the local machine where WebSphere Portal Express is
installed.
- Create a Relational Database Directory Entry on the local system
for the remote system using i5/OS 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 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
- Temporarily change the CCSID for jobs to 37 (an example for US
English environment) by running the following command: CHGJOB CCSID(37)
- 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 Express is
installed.
- 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.
- Click Enter.
- On the command line, enter the following to change directory to
the UserData path: cd wp_profile_root/ConfigEngine.
- Click Enter.
- 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.
- Click Enter.
Parent topic: Preparing DB2 for i5/OS
Previous topic: Create user profiles
|
|
|