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

Adding a database user registry on i5/OS

Add a database user registry to the default federated repository to store user account information for authorization.

1. Create the database using any relational database product that does not contain existing user and group information. The following is an example for DB2 and Oracle:

   Option	Description
   DB2	Perform the following steps to create a DB2 database: Install DB2. Open a DB2 command window and type db2 create database db_name using codeset UTF-8 territory US. Enter the following database tuning commands: db2 update database configuration for db_name using applheapsz 1024 db2 update database configuration for db_name using stmtheap 4096 db2 update database configuration for db_name using app_ctl_heap_sz 2048 db2 update database configuration for db_name using locklist 1024 db2 update database configuration for db_name using indexrec RESTART db2 update database configuration for db_name using logfilsiz 1000 db2 update database configuration for db_name using logprimary 12 db2 update database configuration for db_name using logsecond 10 db2 update database configuration for db_name using sortheap 2048 db2set DB2_RR_TO_RS=yes Warning: If you receive the following errors after running the tuning commands, you can ignore them because the system will correct itself after running the configuration task; check with your database vendor for additional information: db2 => update database configuration for lside using locklist 1024 SQL5146W  "MAXLOCKS" must be set to "MANUAL" when "LOCKLIST" is "MANUAL". "MAXLOCKS" has been set to "MANUAL". db2 => update database configuration for lside using sortheap 2048 SQL5147N  "sortheap" cannot be set to MANUAL if "sheapthres_shr" is AUTOMATIC.
   Oracle	Install Oracle, which also installs the databases.

2. Use a text editor to open the wkplc.properties file, located in the profiles/wp_profile/ConfigEngine/properties directory.
3. Enter the following parameters in the wkplc.properties file to connect remotely to the database and to the WebSphere Application Server:

   1. For ConnectionType, type remote to access the WebSphere Application Server Administrative Console remotely.
   2. For WasSoapPort, type the port number to use to access the WebSphere Application Server Administrative Console remotely.
   3. For WasUserId and WasPassword, type the WebSphere Application Server administrative user ID and password used to access the WebSphere Application Server Administrative Console remotely.
   4. Restart the server accepting SOAP requests at the port provided in the WasSoapPort parameter; by default it is the WebSphere_Portal server.
4. Enter only the following required parameters in the wkplc.properties file under the Federated DB repository heading:

   1. For federated.db.datasourcename, type the name of the data source. CAUTION:The federated.db.datasourcename value must be different than the value for the DataSourceName parameter in the wkplc_comp.properties file.
   2. For federated.db.databaseType, type the database type.
   3. For federated.db.dbURL, type the database URL.
   4. For federated.db.id, type the unique ID for the federated repository.
5. Enter only the following optional parameters in the wkplc.properties file under the Federated DB repository heading:

   1. For federated.db.dbAdminId, type the database administrator ID.
   2. For federated.db.dbAdminPassword, type the password for the database administrator ID.
   3. For federated.db.adapterClassName, type the adapter class name.
   4. For federated.db.JDBCDriverClass, type the JDBC drive class name.
   5. For federated.db.supportSorting, type true to support sorting or false to not support sorting.
   6. For federated.db.supportTransaction, type true to support transactions or false to not support transactions.
   7. For federated.db.isExtIdUnique, type true if the external ID is unique or false if the external ID is not unique.
   8. For federated.db.supportExternalName, type true if the external names are supported or false if external names are not supported.
   9. For federated.db.entityRetrievalLimit, type a numeric value to specify the retrieval limit on database entries.
   10. For federated.db.saltLength, type a numeric value for the salt length in bits; the default value is 12.
   11. For federated.db.encryptionKey, type the encryption key; the default value is rZ15ws0ely9yHk3zCs3sTMv/ho8fY17s.
6. Run the ConfigEngine.sh -profileName profile_root wp-create-db task, located in the profiles/wp_profile/ConfigEngine directory to add a database user registry to the default federated repository. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
7. Perform the following steps to stop and restart the server1 and WebSphere_Portal servers:

   1. Open a command prompt and change to the wp_profile_root/bin directory.
   2. Enter the stopServer server1 -profileName profile_root -user admin_userid -password admin_password command to stop the WebSphere Application Server. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
   3. Enter the stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password command to stop the WebSphere Portal Express server.
   4. Enter the startServer server1 -profileName profile_root command.
   5. Enter the startServer WebSphere_Portal -profileName profile_root command.
8. Optional: Run the ConfigEngine.sh -profileName profile_root wp-query-repository task, located in the profiles/wp_profile/ConfigEngine directory to list the names and types of configured repositories. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.