Configuring a property extension database on i5/OS

Configure IBM^® WebSphere^® Portal Express to use a property extension to store additional attributes that cannot be stored in the LDAP user registry.

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 the following data source parameters in the wkplc.properties file under the Lookaside Database Properties heading:
   1. For la.JdbcProviderName, type the name of the JDBC provider used for this property extension.
      Note: If you are using the same database type for your federated database user registry and your property extension, la.JdbcProviderName and federated.db.JdbcProviderName must be the same. If not using the same database type, these values must be different.
      CAUTION:
      The la.JdbcProviderName value must be different than the value for the JdbcProviderName parameter in the wkplc_dbtype.properties file.
   2. For la.DbType, enter the type of database used for the database domain, for example db2
   3. For la.DbName, type the name of the property extension database.
      Note: This value must also appear as the database element in the la.DbUrl parameter.
      DB2 only note: This value is the TCPIP.
   4. For la.DbSchema, type the property extension database domain schema name. Use the target database management system documentation to define a valid schema name.
   5. For la.DataSourceName, type the data source name for the federated database domain.
      CAUTION:
      The la.DataSourceName value must be different than the value for the DataSourceName parameter in the wkplc_comp.properties file.
   6. For la.DbUrl, type the URL for the property extension domain database.
   7. For la.DbUser, type the database administrator user ID.
   8. For la.DbPassword, type the password for the database administrator user ID.
   9. Required for local DB2 using type 2 JDBC driver: For la.XDbName, type the property extension database alias that needs to be set if you want to call create-database and/or setup-database.
   10. Required for DB2: For la.DbNode, type the node for the property extension database domain that needs to be set if you want to call create-database and/or setup-database.
5. Enter the following extensions parameters in the wkplc.properties file under the Lookaside Database Properties heading:
   1. For la.documentURI, type the name of the file to be created for the property extension database.
   2. For la.file, type the full path to the file containing the input parameters.
6. Enter the following lookaside table parameters in the wkplc.properties file under the Lookaside Database Properties heading:
   1. For la.schemaLocation, type the location of the AppServer/etc/wim/setup directory.
   2. Required if using Derby as the property extension database, for la.derbySystemHome, type the home directory for the Derby database.
   3. For la.laPropXML, type the location of the property extension repository definition XML file.
   4. For la.reportSqlError, type true to report SQL errors while setting up databases or type false to not report errors.
   5. For la.entityRetrievalLimit, type a numeric value to specify the maximum number of entities that the system can retrieve from the database with a single query. The default value is 50.
7. Save your changes to the wkplc.properties file.
8. Run the ConfigEngine.sh -profileName profile_root wp-configure-la-complete 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.
9. 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.
10. Use a text editor to open the wkplc.properties file, located in the profiles/wp_profile/ConfigEngine/properties directory.
11. Enter the following add property parameters in the wkplc.properties file under the Lookaside Database Properties heading:
    1. For la.nsURI, type the address for the namespace URI.
    2. For la.providerURL, type the provide URL.
    3. For la.propertyName, type the name of the property you are adding.
    4. For la.entityTypes, type the entity types for the property you are adding.
    5. For la.dataType, type the data type for the property you are adding; for example string.
    6. For la.multiValued, type true if the property contains multiple values or false if the property contains only one value.
    7. For la.repositoryId, type the name of the repository for the property you are adding.
12. Save your changes to the wkplc.properties file.
13. Run the ConfigEngine.sh -profileName profile_root wp-add-la-property task, located in the profiles/wp_profile/ConfigEngine directory to add a new property to the property extension configuration.
14. 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.