IBM i: 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. Create the IBM DB2 for i 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.

      1. Login to a remote i session.

      2. Enter the strsql command to start the interactive sql session.

      3. Enter the create schema database_name command, where database_name is the name you want to use for the database.

  2. Define the DbDriver and DbLibrary parameter values:

    1. cd WP_PROFILE/ConfigEngine/properties directory.

    2. Locate and open wkplc_dbtype.properties with any text editor.

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

        db_type.DbDriver

        db_type.DbLibrary

    4. Save changes.

  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.sh 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_iseries. The /path/to/DB/jars should be one of the following options:

          IBM DB2 for i Type 2 driver: /QIBM/ProdData/Java400/ext/db2_classes.jar
          IBM DB2 for i Type 4 driver: /QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar

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

        Running the task: You do not have to run this task more than once. You can run this task from any node in the cluster.

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

        2. Run the ConfigEngine.sh wp-node-prep-vmm-db-secured-environment -DWasPassword=foo -DDbDomain=federated.db -DVmmNodeName=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.

              IBM DB2 for i Type 2 driver: /QIBM/ProdData/Java400/ext/db2_classes.jar


              IBM DB2 for i Type 4 driver: /QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar

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

  7. Run the ConfigEngine.sh 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.sh 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.sh wp-query-repository -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to list the names and types of configured repositories.


Parent

Update user registry on i

 


+

Search Tips   |   Advanced Search