Configure a property extension database on AIX


Overview

Configure a property extension database to store attributes the LDAP directory does not or cannot store, but which you want to include in the portal user registry.

This situation can occur when using an LDAP directory that does not allow schema extensions for new attributes. Note that it is generally preferable to store all user attributes in the main user registry. Perform this task only if you cannot add new attributes to LDAP directory.

Configure portal security with main user registry before configuring property extension database. The property extension database configuration becomes unavailable if you perform the steps in this task on the out-of-the-box security configuration then configure portal security with the main user registry.

Due to a limitation with the Virtual Member Manager (VMM), there are no tasks that let you update attributes. To change an attribute, first remove the attribute then add it again. For this reason, ensure you spell all attributes correctly and use caution when adding attributes to the property extension database.

The VMM database schema has a limit of 36 characters on the repository ID column. For this reason, use a repository ID that is 36 characters or less.


Configure a property extension database

  1. Start all appservers in target environment.

  2. Install the required .ear file on WAS.

    • Stand-alone 

        cd WP_PROFILE/ConfigEngine
      
./ConfigEngine.sh wp-la-install-ear -DWasPassword=foo

    • Clustered

      From primary node: 

        cd WP_PROFILE/ConfigEngine
       
./ConfigEngine.sh wp-la-install-ear \
                  -DWasPassword=foo \
                  -DServerName=server_name \
                  -DNodeName=node_name

    To get dmgr_server_name...

      System administrator | Deployment Manager | Configuration tab | General Properties | Name

    To get node_name...

      System administrator | Deployment Manager | Runtime tab | General Properties | Node Name

  3. Restart appservers

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

    Database Steps
    DB2

    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

    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

    1. Install SQL Server.

    2. Set Collation to case-sensitive.

      This sets tempdb collation to matche collation used for the property extension database. The tempdb collation is inherited from the master database, and is set when SQL Server is installed.

  5. Edit...

      WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

    .and set values based on database for...

      db_type.DbDriver db_type.DbLibrary

  6. Specify values for the datasource parameters in wp_add_LA.properties. Edit...

      WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties

    .and specify values for the following parameters...

      la.JdbcProviderName
      la.DbType
      la.DbUrl
      la.DbName
      la.DataSourceName
      la.DbUser
      la.DbPassword

    For a clustered environment add the following parameters to wp_add_LA.properties

      la.schemaLocation=WAS_HOME/AppServer/etc/wim/setup
      la.laPropXML=WAS_HOME/AppServer/etc/wim/setup/wimlaproperties.xml

  7. Edit...

      WP_PROFILE/properties/soap.client.props

    .and set...

      com.ibm.SOAP.requestTimeout

    .to a value is greater than 1000.

  8. For single server environment, proceed to the next step.

    For clustered environment:

    1. Create the local Deployment Manager WebSphere variable used to access the database jars: 

      cd  WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-prep-vmm-db-secured-environment \
                  -DWasPassword=foo \
                  -DDbDomain=la \
                  -Ddb_type.DmgrDbLibrary=/path/to/DB/jars \
                  -DDmgrNodeName=dmgr_node_name

      Set db_type in db_type.DmgrDbLibrary:

        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

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

      1. Verify value is set for la.DbType in wp_add_LA.properties.

      2. Create the variable used to access the VMM database jars. 

          cd WP_PROFILE/ConfigEngine
         
./ConfigEngine.sh wp-node-prep-vmm-db-secured-environment 
                  -DWasPassword=foo 
                  -DDbDomain=la 
                  -DVmmNodeName=node_name,node_name,node_name 
                  -Ddb_type.NodeDbLibrary=/path/to/DB/jars

        VmmNodeName is a list of one or more WebSphere Portal nodes names in the cell which share the same database driver paths.

        Set db_type to database, for example db2.

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

    3. Add a property extension repository to the federated or stand-alone LDAP repository. 

      cd  WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-configure-la-complete \
                  -DWasPassword=foo \
                  -DparentProperties=WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties

    4. Restart appservers to propagate changes.

    5. Specify values in wp_add_LA.properties.

      Add attributes to the property extension database one at a time. Complete this step to specify the parameters for a specific attribute then complete the next step to run the task to add that attribute. Repeat both steps for each attribute you plan to add.

      Edit...

        WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties

      .and specify values for...

        la.providerURL la.propertyName la.entityTypes la.dataType la.multiValued

      Available data types defined in com.ibm.websphere.wim.SchemaConstants:

      • String
      • Int
      • Date
      • AnySimpleType
      • AnyURI
      • Boolean
      • Long
      • Double
      • Short

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

    6. Add the attribute to the property extension database.

        cd WP_PROFILE/ConfigEngine
        ./ConfigEngine.sh wp-add-la-property -DWasPassword=foo -DparentProperties=WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties

      The attributes become available in property extension database.

    7. Add the attributes to Web Content Manager if you use Web content user profiling and/or Category selection trees.

    8. Ensure you have specified a value for la.providerURL in wp_add_LA.properties.

          cd WP_PROFILE/ConfigEngine


        ./ConfigEngine.sh add-wcm-la-attributes -DWasPassword=foo -DparentProperties=WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties

      This task makes an EJB call to WAS, which requires authentication. You may receive a prompt asking for authentication. Enter the appropriate WAS user ID and password.

      Stop and restart the appropriate servers to propagate the changes. For specific instructions, see the following link under Related tasks: Start and stop servers, dmgrs, and node agents.

    If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.


    Parent

    Update user registry on AIX


    Related tasks


    Start and stop servers, dmgrs, and node agents
    Enable LDAP security after cluster creation


    Remove attributes

     


    +

    Search Tips   |   Advanced Search