Configure a property extension database on Linux

You can configure a property extension database (previously referred to as a lookaside database) to store attributes that the LDAP directory does not or cannot store, but which you want to include in the portal user registry. This situation often occurs when you are using an LDAP directory that does not allow schema extensions for new attributes to support portal applications. When you configure a property extension database, you effectively extend the user registry to make new attributes available as part of the portal user profile. However, it is generally preferable to store all user attributes in the main user registry. You should perform this task only if you cannot add new attributes to LDAP directory. This topic explains how to configure property extensions in a single server environment and in a clustered environment.

To configure a property extension database, do the following:

  1. This task requires server connections. Perform the following as appropriate:

    • In a standalone environment, ensure the server1 and WebSphere_Portal servers are running.

    • In a clustered environment, stop all application servers on the system including server1 and WebSphere_Portal then start the nodeagent and dmgr servers.

  2. Install the required Enterprise Archive (.ear) file on WAS.

    Environment Steps
    Standalone

    1. Open a command prompt.

      2. cd WP_PROFILE/ConfigEngine


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

    Cluster

    1. Open a command prompt on the primary node.

      2. cd WP_PROFILE/ConfigEngine

      on the primary node.
      ./ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name

    You can find the dmgr_server_name value in the WAS console under

    System administrator -> Deployment Manager -> Configuration tab -> General Properties -> Name.

    You can find the node_name value in the WAS console under

    System administrator -> Deployment Manager -> Runtime tab -> General Properties -> Node Name.

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

  4. 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.

  5. Define the DbDriver and DbLibrary parameter values:

    1. cd WP_PROFILE/ConfigEngine/properties

    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.

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

    1. cd WP_PROFILE/ConfigEngine/config/helpers

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

    3. Specify values for the following parameters:

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

        Add parameters for a clustered environment: Add the following parameters to the wp_add_LA.properties if you are setting up the property extension database on a clustered environment:

          la.schemaLocation=WAS_HOME/AppServer/etc/wim/setup

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

        where WAS_HOME is the local path on dmgr node.

    4. Save and close wp_add_LA.properties.

  7. 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.

  8. If you are performing this task in a single server environment, proceed to the next step. If you are performing this task in a clustered environment...

    1. Open a command prompt.

    2. cd WP_PROFILE/ConfigEngine

    3. Run the following task to create the local Deployment Manager WebSphere variable used to access the database jars: ./ConfigEngine.sh wp-prep-vmm-db-secured-environment -DWasPassword=foo -DDbDomain=la -Ddb_type.DmgrDbLibrary=/path/to/DB/jars -DDmgrNodeName=dmgr_node_name

        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/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

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

      1. Ensure you have specified the property value for la.DbType in the wp_add_LA.properties.
        ./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 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.

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

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

    1. Open a command prompt.

    2. cd WP_PROFILE/ConfigEngine

    3. Run the following task: ./ConfigEngine.sh wp-configure-la-complete -DWasPassword=foo -DparentProperties=WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties

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

  11. Specify values for the following parameters in wp_add_LA.properties.

      Add several attributes: You must 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.

      1. cd WP_PROFILE/ConfigEngine/config/helpers

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

      3. Specify values for the following parameters:

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

          Values for the dataType parameter: 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.

  12. Add the attribute to the property extension database.

    1. Open a command prompt.

    2. cd WP_PROFILE/ConfigEngine

    3. Run the following task: ./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.

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

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

      2. Open a command prompt.

      3. cd WP_PROFILE/ConfigEngine

      4. Run the following task: ./ConfigEngine.sh add-wcm-la-attributes -DWasPassword=foo -DparentProperties=WP_PROFILE/ConfigEngine/config/helpers/wp_add_LA.properties.

      Receiving an authentication prompt: 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.

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

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 Linux


Related tasks


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


Remove attributes

  Updated step 2. Submitted by Serge G Perras on Nov 4, 2011 12:22:54 AM

Re: Configure a property extension database on Linux

It is important to note that this will not work in a clustered environment with WAS 7 before fixpack 19 (7.0.0.19).

http://www-01.ibm.com/support/docview.wss?uid=swg1PM24181


+

Search Tips   |   Advanced Search