Windows stand-alone: Add a database user registry

Add a database user registry to the default federated repository to store user account information for authentication and authorization. You can add multiple database user registries to the default federated repository although you can only add one database user registry at a time.

In single server environments, you do not have to start or stop the WebSphere_Portal and server1 servers to complete the following steps. In clustered environments, stop all application servers on system, including WebSphere_Portal, then start the nodeagent and dmgr servers before you begin any of the following steps.

Add a database user registry to the default federated repository; repeat these steps for each additional database user registry that you plan to add: Use the wp_add_DB.properties helper file, located in...

...when performing this task to ensure the correct properties are entered. In the instructions below, when the step refers to wkplc.properties, you will use wp_add_DB.properties helper file.

    Run backupConfig.

  1. Set up a new database, including creating a new user with appropriate database privileges for accessing the database:

      Instructions for setting up databases: Refer to the appropriate documentation for the type of database you want to set up.
      Consulting database administrator: The task of setting up a new database is typically performed by a database administrator. However, the following steps are provided for reference in the event you are creating a stand-alone database for testing or demonstration purposes. Consult database administrator before proceeding with the following steps if you plan to create a database for a production environment.

      Database Steps
      DB2® Create a DB2 database:

      1. Install DB2.

      2. Enter the following database tuning commands: 

          db2 "CREATE DB dbname using codeset UTF-8 territory us PAGESIZE 8192"
db2 "UPDATE DB CFG FOR dbname USING applheapsz 4096"
db2 "UPDATE DB CFG FOR dbname USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR dbname USING stmtheap 32768"
db2 "UPDATE DB CFG FOR dbname USING dbheap 2400"
db2 "UPDATE DB CFG FOR dbname USING locklist 1000"
db2 "UPDATE DB CFG FOR dbname USING logfilsiz 4000"
db2 "UPDATE DB CFG FOR dbname USING logprimary 12"
db2 "UPDATE DB CFG FOR dbname USING logsecond 20"
db2 "UPDATE DB CFG FOR dbname USING logbufsz 32"
db2 "UPDATE DB CFG FOR dbname USING avg_appls 5"
db2 "UPDATE DB CFG FOR dbname USING locktimeout 30"
db2 "UPDATE DB CFG FOR dbname using AUTO_MAINT off"

      Oracle Create an Oracle database:

      1. Install Oracle using UNICODE Database and National character sets such as UTF8, AL32UTF8, or AL16UTF16.

      2. Configure the database in Dedicated Server Mode.

      3. Enter the recommended initial buffer pool sizes or set them according to business needs:

        • db_block_size = 8192

        • db_cache_size = 300M

        • db_files = 1024

        • log_buffer = 65536

        • open_cursors = 1500

        • pga_aggregate_target = 200M

        • pre_page_sga = true

        • processes = 300

        • shared_pool_size = 200M

      SQL Server Create an SQL Server database:

      1. Install SQL Server.

      2. Set Collation to case-sensitive.

      Install SQL Server with the appropriate portal database collation so that tempdb collation setting matches the collation you use for the property extension database. The tempdb collation is inherited from the master database, which you set when you install SQL Server.

  2. Define the DbDriver and DbLibrary parameter values:

    1. Edit wkplc_dbtype.properties file, located in the WP_PROFILE/ConfigEngine/properties directory.

    2. Enter a value for the following parameters under the appropriate database type properties heading:

        db_type.DbDriver

        db_type.DbLibrary

    3. Save changes.

      Limitation: The WAS UserManagement component (VMM) requires access to the following database libraries to use the VMM database functions such as Property Extension and database user registry, however, if the Portal is using the DB2 Type 2 driver, due to functional limitations, VMM must use the DB2 Type 4 driver; see Configure a JDBC provider and datasource for federated repositories for additional information:

        DB2 Type 2 driver: db2java.zip
        DB2 Type 4 driver: db2jcc.jar;db2jcc_license_cu.jar
        DB2 for z/OSType 2 driver: db2java.zip
        DB2 for z/OS Type 4 driver: db2jcc.jar;db2jcc_license_cisuz.jar;db2jcc_javax.jar
        Oracle: ojdbc14.jar
        SQL Server JDBC driver provided by Microsoft: sqljdbc.jar
        SQL Server JDBC driver provided by DataDirect: sqlserver.jar;base.jar;util.jar
      Perform the following steps add the library paths to the VMM_JDBC_CLASSPATH variable:

      1. Logon to the WAS console.

      2. Click Environment -> WebSphere Variables.

      3. Select scope: cell.

      4. Select the VMM_JDBC_CLASSPATH variable or click New to create the variable if it does not exist.

      5. Enter the complete paths to the library files, separated by ';", in the Value field; for example, enter D:/IBM/SQLLIB/java/db2jcc.jar;D:/IBM/SQLLIB/java/db2jcc_license_cu.jar.

      Copy the above library files into the appserver/lib directory. Then stop and restart the server1 and WebSphere_Portal servers to load the library files. In a clustered environment, also stop and restart the Deployment Manager and the nodeagents.

  3. Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties

  4. Enter a value under the VMM Federated Database Properties heading:

        federated.db.DataSourceName
        federated.db.DbType
        federated.db.DbUrl
        federated.db.id
        federated.db.baseDN
        federated.db.DbUser
        federated.db.DbPassword
        federated.db.DbName

  5. Change the value for the com.ibm.SOAP.requestTimeout parameter to 1000.

    1. cd WP_PROFILE/properties

    2. Locate and open soap.client.props with any text editor.

    3. Locate the com.ibm.SOAP.requestTimeout parameter and ensure the value is greater than 1000.

    4. Save and close soap.client.props.

  6. In a clustered environment:

    1. Run the ConfigEngine.bat wp-prep-vmm-db-secured-environment -DWasPassword=foo -DDbDomain=federated.db -Ddb_type.DmgrDbLibrary=/path/to/DB/jars -DDmgrNodeName=dmgr_node_name task from the WP_PROFILE/ConfigEngine to create the local Deployment Manager WebSphere variable used to access the database jars.

        The db_type in db_type.DmgrDbLibrary should be set to the type of database you are using, for example db2. The /path/to/DB/jars should be one of the following options:

          DB2 Type 2 driver: db2java.zip


          DB2 Type 4 driver: db2jcc.jar;db2jcc_license_cu.jar


          DB2 for z/OS Type 2 driver: db2java.zip


          DB2 for z/OS Type 4 driver: db2jcc.jar;db2jcc_license_cisuz.jar;db2jcc_javax.jar


          Oracle: ojdbc14.jar


          SQL Server JDBC driver provided by Microsoft: sqljdbc.jar


          SQL Server JDBC driver provided by DataDirect: sqlserver.jar;base.jar;util.jar

    2. Run the following task. Include each node name as a comma separated list in the command:

      1. Set the property value for federated.db.DbType in wkplc.properties if you are using a database user registry or if the cell is migrated from a previous version.

      2. Run the ConfigEngine.bat wp-node-prep-vmm-db-secured-environment -DWasPassword=foo -DDbDomain=federated.db -DVmmNodeName=node_name,node_name,node_name -Ddb_type.NodeDbLibrary=/path/to/DB/jars task from the WP_PROFILE/ConfigEngine on each node to create the variable used to access the VMM database jars.

          VmmNodeName is a list of one or more WebSphere Portal nodes names in the cell which share the same database driver paths. The db_type in db_type.NodeDbLibrary should be set to the type of database you are using, for example db2.

    3. Stop and restart all necessary servers to propagate changes.

  7. Run the ConfigEngine.bat wp-create-db -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to add a database user registry to the default federated repository.

      Users who are not in an LDAP do not have awareness and cannot see if other users are online. This can happen if you install WebSphere Portal and then enable a Federated LDAP or Federated database user repository that does not contain that user. Also, users who sign up using the Self Care portlet do not have awareness.

  8. Stop and restart the appropriate servers to propagate the changes.

  9. To update the user registry where new users and groups are stored:

      If you are using multiple LDAP user registries and/or a database user registry, only run this task for the user registry that you want to define as the default user registry where new users and groups are stored.

      1. Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties

      2. Enter a value under the VMM supported entity types configuration heading:

            personAccountParent
            groupParent
            personAccountRdnProperties
            groupRdnProperties
          The parameters groupParent and personAccountParent must be set to the same value. For example:

            personAccountParent=dc=yourco,dc=com

            groupParent=dc=yourco,dc=com

      3. Save changes to wkplc.properties.

      4. Run the ConfigEngine.bat wp-set-entitytypes -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to delete the old attributes before adding the new attributes.

      5. Stop and restart all necessary servers to propagate changes.

  10. Optional. Run the ConfigEngine.bat wp-query-repository -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to list the names and types of configured repositories.


Parent

Configure the default federated repository


Related tasks


Start and stop servers, dmgrs, and node agents

 


+

Search Tips   |   Advanced Search