Portal and Databases

 

+
Search Tips   |   Advanced Search

 

Contents

  1. Overview
  2. Configure DB2
  3. Validate

 

Overview

WebSphere Portal stores configuration, user identities, credentials, permissions for accessing portal resources, and user data in a database. By default, WebSphere Portal uses the Cloudscape database.

Before you begin, verify your database type is supported

Before configuring WebSphere Portal to work with DB2 or DB2 Express, ensure that the following prerequisites are met:

  • WebSphere Portal is installed with Cloudscape databases.
  • Supported database software is installed.
  • Databases and users are correctly setup for use by WebSphere Portal.

To run these tasks, configure a password in wpconfig.properties or specify the password on the command line using the following syntax: 

   WPSconfig.bat task_name -Dpassword_property_key=password_value

For Windows, be sure that DB2 is started by checking the 'service'. If attempts to re-start DB2 result in a 'logon failure' message, then go to the DB2 properties and reenter the password.

You can install the database server locally on the same machine as WebSphere Portal, or you can install the database server on a remote machine. If you install on a remote machine, configure any required database client software on the WebSphere Portal machine. After the database software is installed, some additional procedures must be performed on the database server before you can perform WebSphere Portal database transfer.

If you uninstall WebSphere Portal, you cannot reuse the WebSphere Portal and Member Manager databases when you reinstall WebSphere Portal. remove the original databases from the server and create the databases again before reinstalling WebSphere Portal.

If you choose to transfer data to another supported database, perform the database transfer before you use WebSphere Portal extensively. Large amounts of data in the databases can cause the database transfer to fail if your Java heap size is not large enough.

WebSphere Portal data and Member Manager data should be stored in one database and accessed by one database user. If WebSphere Portal V5.1 and an earlier version of WebSphere Portal coexist, the database user IDs for WebSphere Portal V5.1 must be different than earlier versions to avoid conflicts during installation.

DB2 Content Manager Runtime Edition is a data repository that runs on DB2 to store data for applications such as Personalization, Document Manager, and Lotus Workplace Web Content Management .

 

Databases

The following table demonstrates the information each application will store in the databases.

The WebSphere Portal architecture allows each of these databases to exist in one or many instances. However, the recommended architecture uses the default instance (db2inst1) that is created by the DB2 installation program).

Application Database Contains Space considerations
WebSphere Portal wpsdb Info on user customizations, for objects such as Pages, profiles, and logins. Depends on the number of Portal users and objects, such pages and portlets.
Member Manager wpsdb
Depends on the number of Portal users and objects, such pages and portlets.
Document Manager jcrdb Documents and document library configuration information. Depends on the size and number of documents created and/or uploaded by the Document Manager.
Personalization jcrdb Personalization rules and campaigns. Number and size of Personalization rules and campaigns.
Feedback fdbkdb Info logged by web sites and used for generating reports for analysis of site activity. Depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
LikeMinds lmdb Recommendations to be displayed to users when their interactions with your Web site have been analyzed and predictions generated. Depends on the amount of traffic to the site.

 

Users

The following table demonstrates the number of tables and types of objects owned by each user. The WebSphere Portal architecture allows each of the following users to exist in the same DB2 database.

Application Database user Function
WebSphere Portal wpsdbusr Owns approximately 76 tables. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.
Member Manager wmmdbusr Owns approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.
Document Manager

Personalization

icmadmin DB2 Content Manager Runtime Edition user (documents and personalization).

Will own approximately 100 tables used for document management and personalization. Tables are dynamically created based on the resources that you define for content management.

Feedback feedback Owns approximately 48 tables used for logging site and personalization usage.
Likeminds lmdbusr Owns the tables used to hold the web site usage analysis routines and recommendation text.

 

DB2 architecture

In a local database environment, WebSphere Portal and DB2 are installed on the same machine.

Figure 1. Local Database Environment

IP Address: 1.2.3.4
 
WebSphere Portal
 
     
 
DB2 Connect and server
 
 
Local Host: 127.0.0.1
 
     

 

Steps for transferring data to another supported database

Follow these steps to transfer WebSphere Portal, Member Manager, and Personalization databases to DB2.

The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, you could alternatively use the configuration wizard, a graphical user interface, to transfer data to another supported database.

A configuration template might exist to support these instructions. Refer to the...

wp_root/config/helpers

...directory for available configuration templates. Use the configuration template to update the wpconfig.properties file according to the property descriptions and recommended values provided here.

  1. Make a backup of...

    wp_root/config/wpconfig.properties

  2. Edit...

    wp_root/config/wpconfig.properties

    ...and enter the values that are appropriate for your environment.

    Database properties

    Property Value
    DbSafeMode

    If set to true, database-specific tasks, such as create, modify, and drop database, will be performed. Use if a pre-configured database (from a previous installation) already exists. If the property is set to false, the database will be updated and the pre-existing database configuration will be overwritten.

    Recommended value: false

    Default value: false

    DbType

    The type of database used to store information for WebSphere Portal.

    Recommended value: db2

    Windows/UNIX Default value: cloudscape

    WpsDbName

    The database name where you want the WebSphere Portal objects created.

    This value is also the database element in the DbUrl property.

    Recommended value: wpsdb

    Notes:

    • For DB2 and DB2 for OS/390 and z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information.

    • If you change the name of the WebSphere Portal data source due to a database migration, manually update this property in the wp_root/config/wpconfig.properties file to maintain the proper the resource reference mapping.

    Windows/UNIX Default value: wpsdb

    DbDriver

    The Java class name for the JDBC provider that WebSphere Portal uses to communicate with its databases.

    Recommended value: COM.ibm.db2.jdbc.app.DB2Driver

    Windows/UNIX Default value: com.ibm.db2j.jdbc.DB2jDriver (Cloudscape)

    DbDriverDs

    The data source for the JDBC provider that WebSphere Portal uses to communicate with its databases.

    Recommended value: COM.ibm.db2.jdbc.DB2XADataSource

    Note that the value above is case sensitive.

    Windows/UNIX Default value: com.ibm.db2j.jdbc.DB2jXADataSource (Cloudscape)

    JdbcProvider

    The name of the JDBC provider that WebSphere Portal uses to communicate with its databases.

    Recommended value: wpsdbJDBC

    Default value: wpsdbJDBC

    DbUrl

    The database URL used to access the WebSphere Portal database with JDBC, where hostname is the name of the remote server and port is the port where the appropriate database instance is listening. The value must conform to standard JDBC URL syntax.

    The database element of this value should match the value of WpsDbName.

    Recommended value: jdbc:db2:wpsdb

    Windows/UNIX Default value: jdbc:db2j:wpsdb;create=true (Cloudscape)

    DbUser

    The user ID for the database administrator.

    Recommended value: <none>

    Default value: db2admin

    DbPassword

    The password for the database administrator.

    Recommended value: <none>

    Default value: ReplaceWithYourDbAdminPwd

    DbLibrary

    The directory path where the classes for the JDBC provider are located.

    Recommended value: SQLLIBjava/db2java.zip

    In UNIX environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.

    Windows/UNIX Default value: d:/WAS51/portalserver/shared/app/cloudscape/db2j.jar

    WpsDsName

    The name of the data source that WebSphere Portal uses to communicate with its databases.

    If the WebSphere Portal data source name is changed due to database migration, which is reflected in wp_root/config/wpconfig.properties, update the resource mappings by executing the following steps:

    1. Login to the WAS Administrative Console.

    2. Select Application>Enterprise Applications.

    3. Select the WebSphere Portal application.

    4. Select the Map resource references to resources option.

    5. Change the JNDI Name for reference binding jdbc/wpsDS to specify the new data source name.

    6. Click OK.

    7. Save the configuration changes.

    Recommended value: wpsdbDS

    Default value: wpsdbDS

    WpsXDbName

    The TCP/IP alias for the database to be used as data source name.

    Required for non-Windows systems only.

    Recommended value: wps5TCP

    Default value: wps5TCP

    WpsDbNode

    This value is the node for the WebSphere Portal database

    Recommended value: wpsNode

    Default value: wpsNode

     

    DB2 Content Manager Runtime Edition properties

    Property Value
    JcrDbName

    The name of the WebSphere Portal database for DB2 Content Manager Runtime Edition tables.

    This value should also appear as the database element in JcrDbUrl

    Recommended value:

    • If using single database: wpsdb

    • If using multiple databases: jcrdb

    Default value: jcrdb

    JcrDbUser

    The DB2 Content Manager Runtime Edition database administrator UserID, which is also used as the schema name for the DB2 Content Manager Runtime Edition's tables and database resources.

    Recommended value: icmadmin

    Default value: icmadmin

    JcrDbPassword

    The DB2 Content Manager Runtime Edition database administrator password.

    Recommended value: <none>

    Default value: ReplaceWithYourDbAdminPwd

    JcrDbUrl

    The URL used to access the DB2 Content Manager Runtime Edition database with JDBC.

    The database element of this value should match the value of JcrDbName.

    Recommended value: jdbc:db2:jcrdb

    Default value: jdbc:db2j:jcrdb;create=true (Cloudscape)

    JcrXDbName

    The TCPIP Alias for the database.

    Required for Non-Windows platforms when using DB2 only.

    Recommend value: jcrdbTCP

    Default value: jcrdbTCP

    JcrDbNode

    The node for the DB2 Content Manager Runtime Edition database.

    Required for Non-Windows platforms when using DB2 only.

    Recommended value: icmNode

    Default value: icmNode

    JcrJdbcProvider

    The name of JDBC provider to be used for DB2 Content Manager Runtime Edition. You can have the same provider even if you have multiple datasources.

    Recommended value: jcr51JDBC

    Default value: jcr51JDBC

    JcrDsName

    The name of datasource to be used for DB2 Content Manager Runtime Edition.

    If the WebSphere Portal data source name is changed due to database migration, which is reflected in wp_root/config/wpconfig.properties, update the resource mappings by executing the following steps:

    1. Login to the WAS Administrative Console.

    2. Select Application>Enterprise Applications.

    3. Select the WebSphere Portal application.

    4. Select the Map resource references to resources option.

    5. Change the JNDI Name for reference binding jdbc/wpsDS to specify the new data source name.

    6. Click OK.

    7. Save the configuration changes.

    Recommended value: JCRDS

    Default value: JCRDS

    JcrGeneratedDDLPath

    Directory for the dynamic DDL files generated by DB2 Content Manager Runtime Edition. If you are using a clustered environment, this directory should be accessible to all portals in your cluster.

    Recommended value: wp_root\jcr\config\dynamic

    (where wp_root is the installation directory of WebSphere Portal)

    Default value: ${WpsInstallLocation}/jcr/config/dynamic

    (where ${WpsInstallLocation} is the installation directory of WebSphere Portal)

    JcrBinaryValueFileDir

    Temporary location for binary values

    Recommended value: ${WpsInstallLocation}/jcr/binaryValues

    Default value: ${WpsInstallLocation}/jcr/binaryValues

    JcrDebugLevel

    Debug level for DB2 Content Manager Runtime Edition database utilities. This property can be set to one of the following values:

      0 - INFO, prints status information

      1 - TRACE, provide method entry-exit information + INFO.

      2 - DEBUG, display command information and SQL statement output information.

      3 - DEBUG+, display processing information of DDL file as well as command that are been executed.

    Recommended value: 2

    Default value: 2

    JcrDbUnicode

    This property indicates whether or not the DB2 Content Manager Runtime Edition database is unicode.

    Recommended value: Y

    Default value: Y

    JcrBPCServerName

    The name of appserver with a configured Business Process Container.

    Recommended value: <none>

    Default value: server1

    JcrJMSJAASUser

    The the user id for the Java Message Service (JMS) that the workflow engine will use to communicate with the DB2 Content Manager Runtime Edition.

    Recommended value: <none>

    Default value: ReplaceWithYourJMSUserId

    JcrJMSJAASPassword

    The password for JcrJMSJAASUser.

    Recommended value: <none>

    Default value: ReplaceWithYourJMSPwd

    JcrJMSType

    Type of Java Message Service (JMS) provider used.

    Recommended value: embedded

    Default value: embedded

    JcrMQQueueManager

    The name of the WebSphere MQ Queue Manager.

    This value is not needed for WebSphere Embedded Messaging.

    Recommended value: <none>

    Default value: <none>

     

    Personalization and Feedback Database properties

    Property Value
    InitializeFeedbackDb

    Specifies whether the Feedback schema and tables will be created on transfer.

    Values:

    • false: To share a Feedback database across multiple instances of WebSphere Portal or to use a Feedback database that was initialized with a previous installation of WebSphere Portal, set this property to false and configure the remaining Feedback properties according to the pre-existing database. The data contained in your existing Feedback schema will then be preserved.

    • true: If set to true, then any existing Feedback database will be dropped and a new database will be created from scratch.

    Recommended value: true

    Default value: true

    PznDbNode

    The node for the Feedback database.

    Must be set for all non-Windows platforms when using DB2.

    Recommended value: pznNode

    Default value: pznNode

    FeedbackXDbName

    The TCP/IP alias for the Feedback database. This value is used to specify the data source on machines that are not running Windows.

    Must be set for all non-Windows platforms when using DB2.

    Recommended value: fdbk5TCP

    Windows/UNIX Default value: fdbk5TCP

    FeedbackDbName

    The name of the Feedback database.

    Notes:

    • This value is also the database element in the FeedbackDbUrl property.

    • For DB2 and DB2 for OS/390 and z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information.

    Recommended value:

    • If using single database: wpsdb

    • If using multiple databases: fdbkdb

    Windows/UNIX Default value: wpsdb

    FeedbackDbUser

    The database user for the Feedback database. This property is required for:

    • DB2

    • DB2 for OS/390 and z/OS

    Recommended value: <none>

    Default value: wcmdbadm

    FeedbackDbPassword

    The database password for feedback database.

    Recommended value: <none>

    Default value: ReplaceWithYourDbAdminPwd

    FeedbackDbUrl

    The database URL used to access the feedback database with JDBC. The value must conform to the standard JDBC URL syntax.

    The database element of this value should match the value of FeedbackDbName.

    Recommended value: jdbc:db2:dbname

    Windows/UNIX Default value: jdbc:db2j:fdbkdb;create=true (Cloudscape)

     

    LikeMinds Database properties

    Property Value
    LikemindsXDbName

    The TCP/IP Alias for the LikeMinds database. This value is used to specify the data source on machines that are not running Windows.

    Required for Non-Windows platforms when using DB2 only.

    Recommended value: lmdb5TCP

    Default value: lmdb5TCP

    LikemindsDbName

    The name of the LikeMinds database.

    This value is also the database element in the LikemindsDbUrl property.

    DB2 note: For DB2 and DB2 for OS/390 and z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information.

    Recommended value:

    • If using single database: wpsdb

    • If using multiple databases: lmdb

    Default value: wpsdb

    LikemindsDbUser

    The database user for LikeMinds database.

    This property is required for

    • DB2

    • DB2 for OS/390 and z/OS

    Recommended value: <none>

    Default value: lmadmin

    LikemindsDbPassword

    The database password for LikeMinds database.

    Recommended value: <none>

    Default value: ReplaceWithYourDbAdminPwd

    LikemindsDbUrl

    The database URL used to access the LikeMinds database with JDBC. The value must conform to the standard JDBC URL syntax.

    The database element of this value should match the value of LikemindsDbName.

    Recommended value: jdbc:db2:lmdb

    Windows/UNIX Default value: jdbc:db2j:wpsdb;create=true (Cloudscape)

     

    Member Manager properties

    Property Value
    WmmDsName

    The name of the data source that WebSphere Portal uses to communicate with the Member Manager database.

    Recommended value: wmmDS

    Default value: wmmDS

    WmmAppName

    The name of the Member Manager enterprise application, as deployed into WAS.

    Recommended value: wmmApp

    Default value: wmmApp

    WmmDbName

    The name of the Member Manager database. This value is also the database element in the WmmDbUrl property.

    If WebSphere Portal V5.1 and a previous version of WebSphere Portal coexist on the same box, this value must be different than the WebSphere Member Services database name in the previous version of WebSphere Portal.

    DB2 note: For DB2 and DB2 for OS/390 and z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information.

    Recommended value: wpsdb

    Windows/UNIX Default value: wpsdb

    WmmDbUser

    The user ID for the database administrator.

    If you are migrating from a previous version of WebSphere Portal, this value must match the database user name for the WebSphere Member Services database from the previous WebSphere Portal version.

    Recommended value: <none>

    Windows/UNIX Default value: ReplaceWithYourDbAdminId

    WmmDbPassword

    The password for the database administrator.

    Recommended value: <none>

    Default value: ReplaceWithYourDbAdminPwd

    WmmDbUrl

    The database URL used to access the Member Manager database with JDBC. The value must conform to standard JDBC URL syntax.

    The database element of this value should match the value of WmmDbName. On z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the DB2 datasource used by WebSphere Portal.

    Recommended value: jdbc:db2:wpsdb

    Windows/UNIX Default value:jdbc:db2j:wpsdb;create=true (Cloudscape)

    WmmEjbName

    The Enterprise Java Bean (like a classname) that other applications need to know it in order to communicate with it.

    Recommended value: ejb/MemberServiceHome

    Default value: ejb/MemberServiceHome

     

  3. Save the file.

  4. If you are installing multiple instances of WebSphere Portal with DB2 on AIX, change the maximum numdb MAX_NETBIOS_CONNECTIONS to increase the default configured number of databases.

    For example...

    set client MAX_NETBIOS_CONNECTIONS 254

    A message indicates success if the number was increased.

  5. cd wp_root/config.

  6. If you are using a local DB2 database on a UNIX system, export the DB2 user profile onto the administrative user.

    . /home/db2inst1/sqllib/db2profile

    ...where db2inst1 represents your database instance.

In a remote database environment, WebSphere Portal and a DB2 Connect are installed on one machine (the local machine). The DB2 server is installed on a separate machine (the remote machine).

Figure 2. Remote Database Environment

Local Machine
IP Address: 1.2.3.4
 
WebSphere Portal
 
     
 
DB2 Connect:

db2inst1

Connect to server on 1.2.3.5

 
     
 

Remote Machine
IP Address: 1.2.3.5
 
 
 

DB2 server:

db2inst1

 

 
   
     

 

Configure DB2

The first thing to do is install DB2.

If you use a remote DB2 server, manually create the databases that are required by WebSphere Portal before performing WebSphere Portal database transfer to work with DB2. If you use a local DB2, WebSphere Portal can create and set up the required databases for you.

Access a local DB2 database on a UNIX machine can cause shared memory problems. To correct these problems, treat the local database as a remote database on the local system. Follow the instructions in the creating local databases section and then also do steps 10-12 from the Create remote databases section.

When creating database instances in DB2 for use with WebSphere Portal, ensure that you create the database instances with the 32-bit setting.

 

Create local databases

If you use a local DB2 server, run the following tasks to automatically create the required databases:

  1. On the DB2 server machine, check the /etc/services file. If it does not specify a DB2 connection and interrupt service ports, specify the ports for your operating system.

    On Microsoft Windows edit the /etc/services file and add the following text (where db2inst1 is the default instance):

    db2cdb2inst1 60000/tcp

    The /etc/services file is located under...

    %systemroot%/system32/drivers/

    ...where %systemroot% is the location of the Windows operating system. For example

    C:\Windows\system32\drivers\etc\services

    On UNIX edit the /etc/services file and add the following text (where db2inst1 is the name of the DB2 instance ID on the system):

    db2cdb2inst 60000/tcp # DB2 connection service port
    db2idb2inst1 60001/tcp # DB2 interrupt service port

  2. cd wp_root/config.

  3. If WebSphere Portal is on UNIX, export the DB2 user profile (that you created when installing DB2) onto the administrative user. This gives that administrative user rights over DB2. It is important to complete this step before running database tasks.

    . /home/db2inst1/sqllib/db2profile

    ...where db2inst1 represents your database instance.

  4. Perform the following steps to set up the configuration file with values specific to your environment:

    1. Make a backup of...

      wp_root/config/wpconfig.properties

    2. Perform Step 2 of Configure WebSphere Portal for DB2.

    3. Save the file.

    To create the WebSphere Portal, Member Manager, DB2 Content Manager Runtime Edition, Feedback and LikeMinds databases... 

    ./WPSconfig.sh create-local-database-db2

  5. If WebSphere Portal is on UNIX. Export the db2instance environment...

    1. cd wp_root/config.

    2. In your .bashrc, .dshrc, or .profile file, add 

      if [ -f /home/db2inst1/sqllib/db2profile ]
then 
    . /home/db2inst1/sqllib/db2profile 
fi

      ...where db2inst1 represents your database instance.

    3. Reopen all the shells.

  6. Validate that your environment has set the DB2 profile environment variables, such as DB2INSTANCE=db2inst1 where db2inst1 represents your database instance by running the env command.

 

Create remote databases

A remote database resides on a different machine than WebSphere Portal. If you use a remote DB2 server, manually create the databases that are required by WebSphere Portal.

The client software, DB2 Client, must be properly configured to connect to the remote DB2 server instance, e.g. db2inst1.

The DB2 Client instance must use the same instance as the DB2 server. For example, if the instance that you connect to is db2inst1, the DB2 Client instance that connects to the DB2 server must also be db2inst1.

These instructions assume that a remote DB2 server and DB2 Client are already installed and running.

These instructions assume that you use DB2 Client to connect to a remote DB2 server, and that WAS, WebSphere Portal, and DB2 Client will be installed on the same machine.

WebSphere Portal V5.1 does not support the DB2 JDBC Type 3 driver, also known as Net Driver.

  1. Log in to the DB2 server machine as a user with sufficient database privileges.

  2. Initialize a DB2 command environment:

    • Windows: Open a command prompt and type...

      db2cmd

    • UNIX: At a command prompt, type...

      su - db2inst1

      ...where db2inst1 represents the database user.

      The prompt changes to $. In this mode, type "db2" at the beginning of each command and use quotation marks ("") around the entire command. For example: 

      db2 "CREATE REGULAR TABLESPACE SMS PAGESIZE 4 K MANAGED BY SYSTEM USING ('sms') BUFFERPOOL SMSPOOL"

      If you are using the Command Line Processor, the command prompt is db2=>. In this mode, commands can be entered without the "db2" prefix or the quotation marks. However, the following steps assume you are not using the CLP and are entering commands from the operating system prompt ($).

  3. Run the following commands on the DB2 server machine for each of the databases:

    1. The WebSphere Portal database (represented as wpsdb): 
      db2 "CREATE database wpsdb using codeset UTF-8 territory us"
db2 "UPDATE database configuration for wpsdb using applheapsz 16384 app_ctl_heap_sz 8192"
db2 "UPDATE database configuration for wpsdb using stmtheap 60000"
db2 "UPDATE database configuration for wpsdb using locklist 400"
db2 "UPDATE database configuration for wpsdb using indexrec RESTART"
db2 "UPDATE database configuration for wpsdb using logfilsiz 1000"
db2 "UPDATE database configuration for wpsdb using logprimary 12"
db2 "UPDATE database configuration for wpsdb using logsecond 10"

      db2set DB2_RR_TO_RS=yes
db2set DB2_EVALUNCOMMITTED=YES
db2set DB2_INLIST_TO_NLJN=YES

    2. The Feedback database (represented as fdbkdb): 
      db2 "create database fdbkdb using codeset UTF-8 territory us collate using identity"
db2 "update database configuration for fdbkdb using logprimary 4"
db2 "update database configuration for fdbkdb using logsecond 25"
db2 "update database configuration for fdbkdb using logfilsiz 4096"
db2 "update database configuration for fdbkdb using applheapsz 5120"

    3. The LikeMinds database (represented as lmdb): 
      db2 "create database lmdb using codeset UTF-8 territory us"

    4. On the DB2 server machine, enter the following commands, where: 

      db2 "CREATE database jcrdb using codeset UTF-8 territory us"
db2 "UPDATE DBM CFG USING QUERY_HEAP_SZ 32768"
db2 "UPDATE DBM CFG USING UDF_MEM_SZ 7000"
db2 "UPDATE DBM CFG USING SHEAPTHRES 10000"
db2 "UPDATE DBM CFG USING MAXAGENTS 500"
db2 "UPDATE DBM CFG USING AGENT_STACK_SZ 384"   (see note below)
db2 "UPDATE DBM CFG USING DFT_MON_TIMESTAMP OFF"

db2 "UPDATE DB CFG FOR jcrdb USING LOCKTIMEOUT 30"
db2 "UPDATE DB CFG FOR jcrdb USING LOCKLIST 1000"
db2 "UPDATE DB CFG FOR jcrdb USING STMTHEAP 16384"
db2 "UPDATE DB CFG FOR jcrdb USING AVG_APPLS 5"
db2 "UPDATE DB CFG FOR jcrdb USING SORTHEAP 256"
db2 "UPDATE DB CFG FOR jcrdb USING LOGPRIMARY 10"
db2 "UPDATE DB CFG FOR jcrdb USING LOGFILSIZ 1000"
db2 "UPDATE DB CFG FOR jcrdb USING LOGSECOND 20"
db2 "UPDATE DB CFG FOR jcrdb USING LOGBUFSZ 32"
db2 "UPDATE DB CFG FOR jcrdb USING MAXAPPLS 200"
db2 "UPDATE DB CFG FOR jcrdb USING APPLHEAPSZ 4096"
db2 "UPDATE DB CFG FOR jcrdb USING DFT_QUERYOPT 2"
db2 "UPDATE DB CFG FOR jcrdb USING DBHEAP 2400"
db2 "UPDATE DB CFG FOR jcrdb USING APP_CTL_HEAP_SZ 20000"
db2 "CONNECT TO jcrdb USER icmadmin USING dbpassword"

db2 "CREATE BUFFERPOOL ICMLSFREQBP4 SIZE 1000 PAGESIZE 4 K"
db2 "CREATE BUFFERPOOL ICMLSVOLATILEBP4 SIZE 8000 PAGESIZE 4 K"
db2 "CREATE BUFFERPOOL ICMLSMAINBP32 SIZE 8000 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL CMBMAIN4 SIZE 1000 PAGESIZE 4 K"

db2 "CREATE BUFFERPOOL OBJECTPOOL SIZE 2000 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL OBJPARTSPOOL SIZE 200 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL SMSPOOL SIZE 500 PAGESIZE 4 K"
db2 "CREATE BUFFERPOOL PARTSPOOL SIZE 100 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL BLOBPOOL SIZE 1000 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL REPLICAPOOL SIZE 1000 PAGESIZE 32 K"
db2 "CREATE BUFFERPOOL TRACKINGPOOL SIZE 250 PAGESIZE 4 K"
db2 "CREATE BUFFERPOOL VALIDATEPOOL SIZE 500 PAGESIZE 32 K"

db2 "CREATE REGULAR TABLESPACE ICMLFQ32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('ICMLFQ32') BUFFERPOOL ICMLSMAINBP32"
db2 "CREATE REGULAR TABLESPACE ICMLNF32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('ICMLNF32') BUFFERPOOL ICMLSMAINBP32"
db2 "CREATE REGULAR TABLESPACE ICMVFQ04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('ICMVFQ04') BUFFERPOOL ICMLSVOLATILEBP4"
db2 "CREATE REGULAR TABLESPACE ICMSFQ04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('ICMSFQ04') BUFFERPOOL ICMLSFREQBP4"
db2 "CREATE REGULAR TABLESPACE CMBINV04 PAGESIZE 4 K MANAGED BY SYSTEM USING ('CMBINV04') BUFFERPOOL CMBMAIN4"
db2 "CREATE SYSTEM TEMPORARY TABLESPACE ICMLSSYSTSPACE32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('icmlssystspace32') BUFFERPOOL ICMLSMAINBP32"
db2 "CREATE SYSTEM TEMPORARY TABLESPACE ICMLSSYSTSPACE4 PAGESIZE 4 K MANAGED BY SYSTEM USING ('icmlssystspace4') BUFFERPOOL ICMLSVOLATILEBP4"

db2 "CREATE REGULAR TABLESPACE OBJECTS PAGESIZE 32 K MANAGED BY SYSTEM USING ('objects') BUFFERPOOL OBJECTPOOL"
db2 "CREATE REGULAR TABLESPACE OBJPARTS PAGESIZE 32 K MANAGED BY SYSTEM USING ('objparts') BUFFERPOOL OBJPARTSPOOL"
db2 "CREATE REGULAR TABLESPACE SMS PAGESIZE 4 K MANAGED BY SYSTEM USING ('sms') BUFFERPOOL SMSPOOL"
db2 "CREATE REGULAR TABLESPACE BLOBS PAGESIZE 32 K MANAGED BY SYSTEM USING ('blobs') BUFFERPOOL BLOBPOOL"
db2 "CREATE REGULAR TABLESPACE REPLICAS PAGESIZE 32 K MANAGED BY SYSTEM USING ('replicas') BUFFERPOOL REPLICAPOOL"
db2 "CREATE REGULAR TABLESPACE TRACKING PAGESIZE 4 K MANAGED BY SYSTEM USING ('tracking') BUFFERPOOL TRACKINGPOOL"
db2 "CREATE REGULAR TABLESPACE VALIDATEITM PAGESIZE 32 K MANAGED BY SYSTEM USING ('validateitm') BUFFERPOOL VALIDATEPOOL"

db2 "DISCONNECT jcrdb"
db2 "TERMINATE"

      The command UPDATE DBM CFG USING AGENT_STACK_SZ 384 is for Windows only. Do not run this command if you are not using Windows.

  4. On the DB2 server machine, check the services file. If it does not specify DB2 connection and interrupt service ports, specify the ports for your operating system:

    • Windows:

      Edit /etc/services and add the following text (where db2inst1 is the default instance):

      db2cdb2inst1 50000/tcp

      The /etc/services file is located under...

      %systemroot%/system32/drivers/

      ...where %systemroot% is the location of the Windows operating system. For example...

      C:\Windows\system32\drivers\etc\services

    • UNIX: Edit /etc/services and add the following text (where db2inst1 is the name of the DB2 instance ID on the system): 

      db2cdb2instl 50000/tcp # DB2 connection service port
db2idb2inst1 50001/tcp # DB2 interrupt service port

  5. On the DB2 Client machine, edit /etc/services and specify the DB2 connection service port for the remote DB2 instance: 

    db2cdb2inst1 50000/tcp # DB2 connection service port
    where db2inst1 is the name of the DB2 instance ID on the system.

    Note: The connection service port on DB2 Client must match the connection service port on the DB2 server. The ports should match by number but not necessarily by name.

  6. On the DB2 server machine, set DB2COMM to TCP/IP... 

    db2set DB2COMM=TCPIP

  7. Set up the correct service name... 

    db2 "UPDATE DBM CFG USING svcename svce_name"

    ...where svce_name is the connection service name that is specified in step 5.

  8. On the DB2 Client machine, set DB2COMM to TCP/IP... 

    db2set DB2COMM=tcpip

  9. On the DB2 Client machine, catalog the TCP/IP node with the IP address of the remote database server, as follows: 

    db2 "catalog tcpip node db2_alias remote database_server_node server connection_service_port"

    where db2_alias is the alias_name of the Database Server that you are defining for the WAS node name, database_server_node is the fully qualified host.name of your database server machine, and connection_service_port is the name of the DB2 connection service port that you specified in the /etc/services file on the database server machine in step 4.

  10. On the DB2 Client machine, catalog the WebSphere Portal, Feedback and Likeminds databases, as follows:

    1. Perform this step for all installations: 

      db2 "catalog db remote_db_name_wpsdb as wpsdb_alias_name at node was_node"
db2 "catalog db remote_db_name_fdbkdb as fdbkdb_alias_name at node was_node"
db2 "catalog db remote_db_name_lmdb as lmdb_alias_name at node was_node"
      where remote_db_name_wpsdb, remote_db_name_fdbkdb are the cataloged name of the WebSphere Portal and feedback databases on the server machine, wpsdb_alias_name and fdbkdb_alias_name are the database alias names that you are defining, and was_node is the name that was used previously when you cataloged the TCP/IP node in the previous step.

    2. If you are using a separate database for the content repository. 

      db2 "catalog db remote_db_name_jcrdb as jcrdb_alias_name at node was_node"
      where remote_db_name_jcrdb is the cataloged name of the DB2 Content Manager Runtime Edition database on the server machine, jcrdb_alias_name is the database alias names that you are defining, and was_node is the name that was used previously when you cataloged the TCP/IP node in the previous step.

    3. If you are using a separate database for Member Manager, also catalog the Member Manager database. 

      db2 "catalog db remote_db_name_wmmdb as wmmdb_alias_name at node was_node"
      where remote_db_name_wmmdb is the cataloged name of the Member Manager database on the server machine, wmmdb_alias_name is the database alias names that you are defining, and was_node is the name that was used previously when you cataloged the TCP/IP node in the previous step.

  11. Log out of the DB2 client machine: 

    db2 "quit"

  12. On the DB2 Client machine, test your remote connection by issuing the following command in the DB2 command window: 

    db2 "connect to alias_name user username using password"
    where alias_name is the alias name that you defined in step 10 and username is the database user.

  13. Restart your database server.

  14. Continue to Create users.

 

Create users

It is recommended that one user with administrative rights on the operating system and the DB2 instance be used for all databases. This user can be the database administrative user that is created automatically by the DB2 installation program. If you choose to have WebSphere Portal create the databases, the database user should be given SYSADM rights.

When installing DB2, there is a limitation on what user names you can use. A common user name is db2inst1, but you can assign any user name as long as it has administrative access and follows the limitations set out here. It is recommended that you do not change the user name after creating it.

The limitations are as follows:

  • User names on UNIX can contain one to eight characters.

  • User names on Windows can contain one to 20 characters.

  • Group and instance names can contain one to eight characters.

  • Names cannot be any of the following examples: 

    users
admins
guests
public
local

  • Names cannot begin with: 

    IBM
SQL
SYS

  • Names cannot include accented characters.

 

Validate

  1. Validate configuration properties. 

    ./WPSconfig.sh validate-database-connection-wps 
./WPSconfig.sh validate-database-connection-jcr 
./WPSconfig.sh validate-database-connection-feedback 
./WPSconfig.sh validate-database-connection-likeminds 
./WPSconfig.sh validate-database-connection-wmm 
./WPSconfig.sh validate-database-driver

  2. Transfer the database...

    1. Enter the following commands to run the configuration task. 

      cd  wp_root/config.
./WPSconfig.sh database-transfer

    2. After running this task, a message indicating success should result. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig.properties file, and then repeat this step.

  3. Go to...

    WAS console | Resources | JDBC Providers

    ...and do "Test Connection" on all of the data sources.

    Verify...

    COM.ibm.db2.jdbc.DB2XADataSource

    ...is configured as the "Implementation Classname". Note that value is case sensitive.

  4. Perform a reorg check to improve performance. (Do the following set of steps for each database alias in the property file: WpsDbName and FeedbackDbName.)

    1. Connect to a database with the following command: 
      db2 connect to database_alias user db2admin_userid using password

      Additional option may be required if additional security was installed. Refer to DB2 Universal Database commands by example for links to a downloadable command reference.

    2. Once connected, run the following commands from the DB2 prompt: 
      reorgchk update statistics on table all
terminate
c:\> db2rbind database_name -l db2rbind.out -u db2_admin -p password

    3. In the output file, look in the reorg column for entries marked with a * (star or asterisk). For each line with a *, note the tablename and run the following command for each tablename: 
      db2 reorg table tablename

  5. Manually verify the classpath information on WAS, and update it if necessary. Perform the following steps to add required DB2 JDBC provider files to the WAS classpath. If this installation of WebSphere Portal is federated into a cell that is managed by the WAS deployment manager, these steps should be performed on the Administrative Console for the deployment manager.

    1. Open the Administrative Console by accessing the following URL in a browser: 
      http://hostname.setgetweb.com:9090/admin
      where hostname.setgetweb.com:9090 is the host.name and port of the machine where WAS is running.

    2. After logging in, click Servers > Application Servers, and then click WebSphere_Portal from the list of application servers.

    3. Click Process Definition from the list of additional properties, and then click Java Virtual Machine from the list of additional properties.

    4. In the Classpath field, enter the directory path where the db2java.zip file is located. Note that this directory path must also match the value you specified for the DbLibrary property in the wpconfig.properties file. For example, C:/PROGRA~1/SQLLIB/java/db2java.zip.

    5. Click OK.

    6. Click the Save link to go to the Save page, and then click Save.

    Cluster users: Because JVM settings are node-specific and not synchronized across nodes, specify the classpath value for each cluster member.

  6. Change to the directory was_root/bin.

  7. Enter the following command:

    startServer WebSphere_Portal.

 

To use the WebSphere Portal database to hold information for applications such as Document Manager, Personalization, Feedback and Likeminds, use the same configuration values for similar properties. For example, use the value for WpsDbName for JcrDbName, FeedbackDbName, and LikemindsDbName.

Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

If you are using a remote database, be sure to enter the values for the remote server.

Use / instead of \ for all platforms.

Some values, shown here in italics, might need to be modified to your specific environment.

There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.

If you are following the recommended architecture in Plan for DB2, the Value listed for each property in the following table represents the DB2-specific information that is required to configure WebSphere Portal to DB2.

 

Verify the connection with WAS

Access the WAS administrative console

http://<host.domain>:<port_number>/admin

...and go to...

Resources | JDBC Providers | wpsdbJDBC | Data Sources

Check the data source that you want to test. click Test Connection to verify the database connection.

If configuration parameters have been changed, you might have to restart WAS for the test to complete.

 

Verify DB2 Content Manager Runtime Edition in a browser

Verify that the database server is installed and working properly using a browser or through the WAS administrative console.

Open the portal in a browser:

http://<host.domain>:<port_number>/wps/portal

Click on the Document Manager tab. If the portlet is displayed, DB2 Content Manager Runtime Edition is set up correctly.

Access the WAS administrative console by entering

http://<host.domain.com>:<port_number>/admin

...and go to...

Resources | JDBC Providers | jcrdbJDBC | Data Sources

...and check the data source that you want to test click Test Connection to verify the database connection.

If configuration parameters have been changed, you might have to restart WAS for the test to complete.

 

Verify WebSphere Portal in a browser

Verify that the WebSphere Portal appserver is running by opening the portal in a browser...

http://<host.domain>:<port_number>/wps/portal

...where host.domain is the fully qualified host.name of the machine where WebSphere Portal is running and port_number is the transport port that is created by WAS.

There may be an error if any of the following conditions appear.

  • When trying to access the portal you may get a 503 error.

  • If you had any locale problems with your database, you could see invalid characters, such as ????, after logging in. This may happen if the character set of the database is not UTF-8 compliant.

  • If something went wrong with the data that was transfered, you may not be able to login. Portal will indicate you entered an invalid user ID and password even though you know it is valid.

 

Next steps

  1. Install DB2
  2. Install DB2 for OS/390 and z/OS
  3. Install Oracle
  4. Install SQL Server
  5. Troubleshooting
  6. Managing Security
  7. Which Distributed Edition of DB2 Universal Database V8 is Right for You?

 

Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.