Configure a property extension database on i5/OS

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

In a single server environment the WebSphere_Portal and server1 servers can be either stopped or started.

In a clustered environment stop all appservers on the system including WebSphere_Portal and server1 and then start the nodeagent and deployment manager servers before starting the following task. Configure a property extension for your user registry model:

Use the wp_add_LA.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 your wp_add_LA.properties helper file.

  1. Install the .ear file for adding properties...

    Option Description
    Standalone cd profile_root/ConfigEngine
    ConfigEngine.sh wp-la-install-ear -DWasPassword=password
    Cluster Run...

      ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name

    ...only on the primary node, from...

      profile_root/ConfigEngine

    Where the default value for dmgr_server_name is dmgr; you can look up the dmgr_server_name value in the admin console under System administrator > Deployment Manager > Configuration tab > General Properties > Name.

    Where node_name is the name of the node where the deployment manager resides; you can look up the node_name value in the admin console under System administrator > Deployment Manager > Runtime tab > General Properties > Node Name.

  2. Propagate the security changes:

    Option Description
    Standalone

    1. stopServer server1 -username admin_userid -password admin_password

      ...from...

        profile_root/bin

    2. stopServer WebSphere_Portal -username admin_userid -password admin_password

      ...from...

        profile_root/bin

    3. startServer server1

      ...from...

        profile_root/bin

    4. startServer WebSphere_Portal

      ...from...

        profile_root/bin

    Cluster

    1. stopManager-username admin_userid -password admin_password, from the DMGR_PROFILE/bin

    2. stopNode -username admin_userid -password admin_password from the profile_root/bin directory

    3. stopServer WebSphere_Portal -username admin_userid -password admin_password

      ...from...

        profile_root/bin

    4. startManager, from the DMGR_PROFILE/bin

    5. startNode

      ...from...

        profile_root/bin

    6. startServer WebSphere_Portal

      ...from...

        profile_root/bin

  3. To create the DB2 for i5/OS database:

    1. Login to a remote i5/OS 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.

  4. Perform the following steps to define the DbDriver and DbLibrary parameter values:

    1. Edit wkplc_dbtype.properties, located in the profile_root/ConfigEngine/propertiesdirectory.

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

      • db_type.DbDriver

      • db_type.DbLibrary

    3. Save changes.

  5. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  6. Enter a value for the following parameters under the VMM Property Extension Properties heading:

    Important cluster information: Add the following parameters to wkplc.properties if you have a clustered production environment:

    • la.schemaLocation=WAS_install_location_on_DMGR/AppServer/etc/wim/setup

    • la.laPropXML=WAS_install_location_on_DMGR/AppServer/etc/wim/setup/wimlaproperties.xml

    where WAS_install_location_on_DMGR is the local path on your deployment manager node.

  7. Edit the soap.client.props file, located in the profile/wp_profile/properties directory. Change the com.ibm.SOAP.requestTimeout value to 1000.

  8. Perform the following steps in a clustered environment:

    1. Run...

        ConfigEngine.sh wp-prep-vmm-db-secured-environment -DWasPassword=password -DDbDomain=la|federated.db -Ddb_type.DmgrDbLibrary=/path/to/DB/jars/on/Dmgr -DDmgrNodeName=dmgr_node_name

      ...from...

        profile_root/ConfigEngine

      ...to create the local Deployment Manager WebSphere variable used to access the database jars.

      Where DbDomain is either la or federated.db depending on whether you are using a property extension database (la) or a database user registry (federated.db). 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/on/Dmgr should be one of the following options:

      • DB2 for i5/OS Type 2 driver:

        /QIBM/ProdData/Java400/ext/db2_classes.jar

      • DB2 for i5/OS Type 4 driver:

        /QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar

    2. If you configured a database user registry or a property extension database, run the following task for EACH WebSphere Portal node that participates in the cluster to set up access to the database drivers; if multiple nodes share the same database library path you can submit a comma separated list of node names:

      This task does not need to be executed from the node identified in the VmmNodeName parameter.

      1. Set the property value for federated.db.DbType if using a database user registry and set the property value for la.DbType if using a property extension database in wkplc.properties.

      2. Run...

          ConfigEngine.sh wp-node-prep-vmm-db-secured-environment -DWasPassword=password -DDbDomain=la|federated.db -DVmmNodeName=node_name -Ddb_type.NodeDbLibrary=/path/to/DB/jars

        ...from profile_root/ConfigEngine on each node to create the variable used to access the VMM database jars.

        Where DbDomain is either la or federated.db depending on whether you are using a property extension database (la) or a database user registry (federated.db). 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.

        The /path/to/DB/jars should be one of the following options:

        • DB2 for i5/OS Type 2 driver:

          /QIBM/ProdData/Java400/ext/db2_classes.jar

        • DB2 for i5/OS Type 4 driver:

          /QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar

    3. Run...

        ConfigEngine.sh wp-connect-database-vmm -DWasPassword=password -DDbDomain=la|federated.db

      ...to connect to the VMM database, where DbDomain is either la or federated.db depending on whether you are using a property extension database (la) or a database user registry (federated.db).

    4. Cycle all necessary servers to propagate changes.

  9. Run...

      ConfigEngine.sh wp-configure-la-complete -DWasPassword=password task, from profile_root/ConfigEngine, to add a property extension repository to the federated or standalone LDAP repository.

    • Propagate the security changes:

      Option Description
      Standalone

      1. stopServer server1 -username admin_userid -password admin_password

        ...from...

          profile_root/bin

      2. stopServer WebSphere_Portal -username admin_userid -password admin_password

        ...from...

          profile_root/bin

      3. startServer server1

        ...from...

          profile_root/bin

      4. startServer WebSphere_Portal

        ...from...

          profile_root/bin

      Cluster

      1. stopManager-username admin_userid -password admin_password, from the DMGR_PROFILE/bin

      2. stopNode -username admin_userid -password admin_password from the profile_root/bin directory

      3. stopServer WebSphere_Portal -username admin_userid -password admin_password

        ...from...

          profile_root/bin

      4. startManager, from the DMGR_PROFILE/bin

      5. startNode

        ...from...

          profile_root/bin

      6. startServer WebSphere_Portal

        ...from...

          profile_root/bin

    • Enter a value for the following parameters under the VMM Property Extension Properties heading:

      A complete overview of valid dataType values can be found in the Configure a property extension repository in a federated repository configuration file in WAS v6.1 or in the Configure a property extension repository in a federated repository configuration file in WAS v7.0. All constant values of DATA_TYPE_* fields are valid input for la.dataType.

    • Run...

        ConfigEngine.sh wp-add-la-property -DWasPassword=password task, from...

          profile_root/ConfigEngine

        ...to add a new property to the property extension configuration. Then perform the following steps if you use any of the following Web Content Management features:

        1. Enter the la.providerURL parameter value in wkplc.properties if you have not already provided a value for the parameter.

        2. Run...

            ConfigEngine.sh add-wcm-la-attributes -DWasPassword=password

        These tasks perform an EJB call to WAS, which must authenticate against WAS. Depending on the configuration in sas.client.props, you may receive a popup window or a command line prompt asking for user identity and password. Enter the WAS user ID and password.

      • Propagate the security changes:

        Option Description
        Standalone

        1. stopServer server1 -username admin_userid -password admin_password

          ...from...

            profile_root/bin

        2. stopServer WebSphere_Portal -username admin_userid -password admin_password

          ...from...

            profile_root/bin

        3. startServer server1

          ...from...

            profile_root/bin

        4. startServer WebSphere_Portal

          ...from...

            profile_root/bin

        Cluster

        1. stopManager-username admin_userid -password admin_password, from the DMGR_PROFILE/bin

        2. stopNode -username admin_userid -password admin_password from the profile_root/bin directory

        3. stopServer WebSphere_Portal -username admin_userid -password admin_password

          ...from...

            profile_root/bin

        4. startManager, from the DMGR_PROFILE/bin

        5. startNode

          ...from...

            profile_root/bin

        6. startServer WebSphere_Portal

          ...from...

            profile_root/bin

If you configured your property extension database on the out-of-the-box security configuration and then configured your LDAP user registry, the properties that you added to the property extension, before configuring LDAP user registry, will not be available. Run...

, described above, to add the property to the configuration.

If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.


Parent topic:

Updating the user registry on i5/OS


Related tasks


Enable LDAP security after cluster creation