Create databases and users for DB2

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

Create databases and users for DB2

This section provides information on setting up DB2 to work with WebSphere Portal Express.

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

Before you begin

You should have completed Installing DB2.

Note the following information:

If WebSphere Portal Express Version 6.0 and an earlier version of WebSphere Portal Express coexist, the database user IDs for WebSphere Portal Express Version 6.0 must be different than earlier versions to avoid conflicts during database transfer.
When using the same database user ID, the name of all WebSphere Portal Express databases, the name of all TCPIP Alias for the WebSphere Portal Express databases, and the name of all of the nodes must be different.
Accessing a local DB2 database on a Linux 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 remote databases section if you are manually creating a database. If you follow the instructions in the Creating local databases section to create a local DB2 database, the remote database on the local system is configured by create-local-database-db2.
The tablespace LMTABLESPACE is reserved for LikeMinds. LikeMinds and Portal Personalization will drop this tablespace during uninstallation of LikeMinds and certain database transfer tasks.
In certain cases modifications to the values given in these steps are necessary. In these cases, the changes must be made according to the DB2 documentation http://www.ibm.com/software/data/db2/.
When the DB2 Universal JDBC driver (type 4 mode) is used, connect to the database directly. Do not connect to an alias database (gateway), but specify the real database name in the JDBC connection URL (dbdomain.DbUrl) and in the database name property (dbdomain.DbName).
If you plan to transfer multiple instances of WebSphere Portal Express, increase the default number of configured databases. For example, to change the default number to 30, enter the following command at the database prompt: UPDATE DATABASE MANAGER CONFIGURATION USING NUMDB 30. A message confirms successful completion of the update.

Create users

IBM recommends 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 Express 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. IBM recommends that you do not change the user name after creating it.

The limitations are as follows:
User names on Linux 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.
Take care to create users in an environment that has the same settings as the actual runtime environment. For example, avoid creating a user in an English environment if you plan to use that user in a Turkish environment.
Following are the basic steps to create new users and granting the privileges. For more information, refer to the DB2 product documentation.

From the DB2 Control Center, expand the object tree until you find the DB Users folder.
Right-click the DB Users folder and select Create/Add from the pop-up menu. The Create DB User notebook opens.
In the User name field, type a 1-8 character user ID.
Click the tab for the type of object for which you want to grant privileges to the user ID. The privileges can be altered pertaining to the user.
Click OK to save your changes and close the window.

Create local databases

If you use a local DB2 server, run the following tasks to automatically create the required databases as a remote database on the local system:

Notes:

When using create-local-database-db2 to create a remote DB2 database on the local system in a non-Windows, you will need the following database properties:

dbdomain.DbName The name of the database.
dbdomain.XDbName TCPIP Alias for the database.
Notes:

For DB2^® Content Manager Runtime Edition, this property is the database for tables.
While creating databases, the values for dbdomain.DbName and dbdomain.XDbName must be different in the wpconfig_dbdomain.properties file.
The property dbdomain.XDbName is not evaluated if a JDBC connection URL for the DB2 Universal JDBC driver (type 4 mode) is specified in dbdomain.DbUrl.

Depending on which database domain has to be configured, dbdomain will be replaced by:

release
customization
community
jcr
feedback
likeminds
wmm
Open a command prompt, and change to the directory portal_server_root/config.
If WebSphere Portal Express is on Linux, 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.

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

Locate the following files and create a backup copy of each before changing any values:

portal_server_root/config/wpconfig.properties
portal_server_root/config/wpconfig_dbdomain.properties
portal_server_root/config/wpconfig_dbtype.properties

Use a text editor to open the properties files and enter the values that are appropriate for your environment. Tip:

IBM recommends to print out the properties tables in this step for reference while modifying the properties files.
Make sure to enter the appropriate values for each instance of each property. In wpconfig_dbdomain.properties, most properties are repeated for each domain.

Notes:

The WebSphere Portal Express database can be used to hold information for applications such as Document Manager, Personalization, Feedback and LikeMinds. In this case, the user should use similar naming conventions for property values such as release.DbName, jcr.DbName, feedback.DbName, and likeminds.DbName. For example:

releaseDbName=wpsdb
jcr.DbName=jcrdb
feedback.DbName=fdbkdb
likeminds.DbName=lkmddb

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.
The value listed for each property in the following tables represents the specific information that is required to configure WebSphere Portal Express to your target database.
Depending on which database domain has to be configured, dbdomain may need to be replaced by:

release
customization
community
jcr
feedback
likeminds
wmm

The values for at least one of the following properties must be unique for the release, customization, community, and jcr domains:

dbdomain.DbType
dbdomain.DbName
dbdomain.DbUrl
dbdomain.DbSchema
If you use the same values for all four properties across the release, customization, community, and JCR domains, the database-transfer task will fail. If DbUser, DbUrl, and DbPassword are not the same across domains, the value for DataSourceName must differ from the DataSourceName of the other domains. In other words, this value must be unique for the database domain.
Do not modify the values for the sync and designer database domains. These domains are not used by WebSphere Portal Express and the values should remain pointing to the default database.
Update the following properties in the file wpconfig_dbdomain.properties.

Database domain properties
Property Value
dbdomain.DbType The type of database used to store information for WebSphere Portal Express.

Type: Alphanumeric text string

Recommended:

DB2: db2

dbdomain.DbName The name of the WebSphere Portal Express domain database and schema.

Notes:

This value is also the database element in the dbdomain.DbUrl property.
For non-Windows platforms when using DB2, this value is the TCPIP Alias for the database.

Type: Alphanumeric text string

Notes:

For DB2 this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information.
For DB2, this value must be different from the value of dbdomain.XDbName.
If you change the name of the WebSphere Portal Express data source due to a database migration, manually update this property in the portal_server_root/config/wpconfig_dbdomain.properties file to maintain the proper resource reference mapping.

Recommended value for all domains:

Release: release
Community: comm
Customization: cust
JCR: jcrdb
WMM: wmmdb
Feedback: fdbkdb
LikeMinds: lmdb

dbdomain.DbSchema The schema name of the database domain.

Notes:

For i5/OS: dbdomain.DbSchema must match the postfix of dbdomain.DbName after /. For example, if release.DbName=*LOCAL/REL60, then release.DbSchema=REL60.
Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems, for example on i5/OS.

Notes:

This property is not used on Member Manager, which only uses the dbdomain.DbUser name as the schema.
Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems.
For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same.
For Oracle only: For non-feedback domains, DbSchema and DbUser MUST be the same. For Feeback domains, the default schema name is FEEDBACK. If the value is set to something besides FEEDBACK, you also have to set the schemaName property in <wps_home>/shared/app/config/services/FeedbackService.properties to the new schema.

Type: Alphanumeric text string

Default value: dbdomain

dbdomain.DbUrl The database URL used to access the WebSphere Portal Express database with JDBC. The value must conform to standard JDBC URL syntax.

The database element of this value should match the value of dbdomain.DbName.
Type: Alphanumeric text string, conforming to standard JDBC URL syntax
Recommended:

DB2:

jdbc:db2:wpsdb
jdbc:db2://db2server.mycompany.com:50000/wpsdb:returnAlias=0;
Please refer to the DB2 documentation for the correct syntax of the JDBC URL.

JDBC type 2 connection:

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.apdv.java.doc/doc/cjvjt2cn.htm
Example: jdbc:db2:wpsdb

JDBC type 4 connection:

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.apdv.java.doc/doc/cjvclrrt.htm
Example: jdbc:db2://db2server.mycompany.com:50000/wpsdb:returnAlias=0;
The name of the database must be used in the URL; for example, wpsdb. The alias of the database should not be used in the URL.

dbdomain.DbUser
The user ID for the database administrator.

Notes:

For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same.
For Oracle and SQL Server, if the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property.
For Oracle only: For non-feedback domains, DbSchema and DbUser MUST be the same. For Feeback domains, the default schema name is FEEDBACK. If the value is set to something besides FEEDBACK, you also have to set the schemaName property in <wps_home>/shared/app/config/services/FeedbackService.properties to the new schema.

Type: Alphanumeric text string

Default for all domains: wpdb2ins ReplacewithyourDBAdminUser
Recommended:

Release: releaseusr
Community: communityusr
Customization: customizationusr
JCR: icmadmin
WMM: wmmdbusr
Feedback: feedback
LikeMinds: lmdbusr

dbdomain.DbPassword
The password for the database administrator.

A value must be set for this property; it cannot be empty.
Type: Alphanumeric text string

Default for all domains: ReplaceWithYourDbAdminPwd

dbdomain.XDbName
The database loop back alias that needs to be set if you plan to use the create-local-database-db2 task.

Notes:

For DB2, this value must be different from the value of dbdomain.DbName.

Type: Alphanumeric text string
Default value:

Release: wps6TCP
Community: wps6TCP
Customization: wps6TCP
WMM: wps6TCP
JCR: wps6TCP
Feedback: fdbk6TCP
LikeMinds: lmdb6TCP

dbdomain.DbNode
The value for the node database.

Required for non-Windows platforms when using DB2 only.
Type: Alphanumeric text string
Default values:

Release: wpsNode
Community: wpsNode
Customization: wpsNode
JCR: wpsNode
WMM: wpsNode
Feedback value: pznNode
LikeMinds value: pznNode

dbdomain.DataSourceName
The name of the data store that WebSphere Portal Express uses to communicate with its databases.

Notes:

If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains. In other words, this value must be unique for the database domain.
The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName.
i5/OS: The value for dbdomain.DataSourceName must match the postfix of dbdomain.DbSchema name. For example, if release.DbSchema=REL60, then release.DataSourcename=REL60. This name must be unique for each database schema.
Follow the documentation of the target database management system in order to define a valid schema name, as restrictions apply for some database management systems.

Type: Alphanumeric text string
Default values:

Release: wpsdbDS
Community: wpsdbDS
Customization: wpsdbDS
JCR: JCRDS
WMM: wpsdbDS
Feedback: feedback5
LikeMinds: lmdbDS

Update the following properties in the file wpconfig_dbtype.properties.

Database type properties
Property Value
DbSafeMode This only applies to database-specific tasks. If this property is set to true, database-specific tasks, such as create/modify/drop database, will not be performed. The property should be used 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: false

Default: false

db2.DbDriver The name of the class that SqlProcessor will use to import SQL files.

The JDBC driver class name depends on the JDBC connection type that will be used.
Recommended:

For JDBC type 2 connections: COM.ibm.db2.jdbc.app.DB2Driver
For JDBC type 4 connections: com.ibm.db2.jcc.DB2Driver

db2.DbLibrary The directory and name of the .zip or .jar file that contains the JDBC driver class.

The value depends on the JDBC connection type that will be used. For JDBC type 2 connections the JDBC driver archive is named db2java.zip, but for JDBC type 4 connections the archive is split into two files: db2jcc.jar, which contains the JDBC driver, and db2jcc_license_*.jar, which contains the corresponding license. The name of the license archive depends on the actual license. For licensed connections to DB2 on Windows, Linux and Linux the file may be named db2jcc_license_cu.jar. The JDBC driver archives can be found in the DB2 installation directory in the "sqllib/java" subdirectory.
Recommended:

JDBC Type 2 connection: db2_install/java/db2java.zip
JDBC Type 4 connection: db2_install/java/db2jcc.jar:db2_install/java/db2jcc_license_cu.jar

In Linux environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.
db2.JdbcProviderName The name of the JDBC provider that WebSphere Portal Express uses to communicate with its databases.
Type: Alphanumeric text string

Update the following properties in the file wpconfig.properties.

WebSphere Application Server properties
Property Description
WasPassword The password for WebSphere Application Server security authentication.

If a value is specified for WasPassword, a value must also be specified for WasUserid. If WasPassword is left blank, WasUserid must also be left blank.
Type: Alphanumeric text string

Recommended: Set this value according to a environment.

Default: ReplaceWithYourWASUserPwd

Save the file.

To create the WebSphere Portal Express, Member Manager, DB2 Content Manager Runtime Edition, Feedback and LikeMinds databases, type the following command:

Linux:
./WPSconfig.sh create-local-database-db2 -DDbPassword=password -DJcrDbPassword=password -DFeedbackDbPassword=password -DLikemindsDbPassword=password -DWmmDbPassword=password
Windows:
WPSconfig.bat create-local-database-db2 -DDbPassword=password -DJcrDbPassword=password -DFeedbackDbPassword=password -DLikemindsDbPassword=password -DWmmDbPassword=password
Perform this step only if WebSphere Portal Express is on Linux. Use the following steps to export the db2instance environment in your profile:
Open a command prompt, and change to the root directory /.
In your .bashrc, .dshrc, or .profile file, add the following:
if [ -f /home/db2inst1/sqllib/db2profile ]; then . /home/db2inst1/sqllib/db2profile; fi
where db2inst1 represents your database instance.
Reopen all the shells.
Validate that your environment has set the DB2 profile environment variables, such as DB2INSTANCE=db2inst1 wheredb2inst1 represents your database instance by running the env command.
Perform this step only if WebSphere Portal Express is on Linux. 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:
Use a text editor to open the file /etc/services and add the following text (where db2inst1 is the default instance): db2c_db2inst1 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.
Linux:
Use a text editor to open the file /etc/services and add the following text (where db2inst1 is the name of the DB2 instance ID on the system):
db2c_db2inst1 50000/tcp # DB2 connection service port db2i_db2inst1 50001/tcp # DB2 interrupt service port
Perform this step only if WebSphere Portal Express is on Linux. On the DB2 server machine, set DB2COMM to TCP/IP by using the db2set command, as follows:
db2set DB2COMM=TCPIP
Perform this step only if WebSphere Portal Express is on Linux. Set up the correct service name by entering the following command on the DB2 server machine:
db2 "UPDATE DBM CFG USING svcename svce_name"
where svce_name is the connection service port name that is specified in step 7.
Create remote databases

A remote database resides on a different machine than WebSphere Portal Express. If you use a remote DB2 server, manually create the databases that are required by WebSphere Portal Express. See Planning for DB2 for more information on the database architecture recommendations. Before creating these databases, note the following information:

If the DB2 JDBC type 4 driver is used, only the instructions on the remote server are required. You do not need to install the DB2 client software, and you do not need to complete the steps related to the DB2 client.
The client software, DB2 Client, must be properly configured to connect to the remote DB2 server instance, for example, db2inst1.
These instructions assume that a remote DB2 server and DB2 Client are already installed and running. For information on installing DB2 Client, see the DB2 product documentation.
These instructions assume that you use DB2 Client to connect to a remote DB2 server, and that WebSphere Application Server, WebSphere Portal Express, and DB2 Client will be installed on the same machine.

WebSphere Portal Express Version 6.0 does not support the DB2 JDBC Type 3 driver, also known as Net Driver.
Log in to the DB2 server machine as a user with sufficient database privileges.
Ensure that the user you are using for the JCR Database User has been created, granted appropriate privileges, and has a password assigned to it. If the user has not been created, refer to the Creating users section for information on how to create users.
Initialize a DB2 command environment:

Windows:
Open a command prompt and type db2cmd.
Linux:
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 Lind Processor (refer to your DB2 documentation for details), 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 $ prompt.
Run the following command on the DB2 server machine to configure the DB2 database instance:For DB2 Version 8:
db2set DB2_RR_TO_RS=yes db2set DB2_EVALUNCOMMITTED=YES
db2set DB2_INLIST_TO_NLJN=YES
db2 "UPDATE DBM CFG USING query_heap_sz 32768"
db2 "UPDATE DBM CFG USING maxagents 500"
db2 "UPDATE DBM CFG USING sheapthres 50000"
For DB2 Version 9:
db2set DB2_RR_TO_RS=yes db2set DB2_EVALUNCOMMITTED=YES
db2set DB2_INLIST_TO_NLJN=YES
db2 "UPDATE DBM CFG USING query_heap_sz 32768"
db2 "UPDATE DBM CFG USING maxagents 500"
db2 "UPDATE DBM CFG USING sheapthres 0"
Run the following commands on the DB2 server machine to create the necessary databases:
Notes:

Please replace dbname with the actual name of the database; run the commands several times and each time replace dbname with the actual values for release, community, customization, jcrdb, wmm, fdbkdb, and lmdb.
Database names can contain one to eight characters.
By default, all databases collate using the UCA400_NO collation of DB2. As this collation may not be suitable for certain needs, you may decide to change this collation in the 'CREATE DB' command below. Please refer to the DB2 InfoCenter for more information on this topic.
db2 "CREATE DB dbname using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"
db2 "UPDATE DB CFG FOR dbname USING applheapsz 2048"
db2 "UPDATE DB CFG FOR dbname USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR dbname USING stmtheap 8192"
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 1000"
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"
On the DB2 server machine, run the following commands, where:

jcrdb is the name of the database used to store user data and objects
icmadmin is the database user for jcrdb
This value can be replaced with any id that has administrative authority.
dbpassword is the password for jcrdb

These steps are only required for the database for the DB2 Content Manager Runtime Edition (jcrdb).
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 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 "DISCONNECT jcrdb"
db2 "TERMINATE"
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:
Use a text editor to open the file /etc/services and add the following text (where db2inst1 is the default instance): db2c_db2inst1 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.
Linux:
Use a text editor to open the file /etc/services and add the following text (where db2inst1 is the name of the DB2 instance ID on the system):
db2c_db2inst1 50000/tcp # DB2 connection service port db2i_db2inst1 50001/tcp # DB2 interrupt service port
If you are using a JDBC Type 2 connection: On the DB2 Client machine, use a text editor to open the /etc/services file. If it does not specify the DB2 connection service port, add the following text to specify the port for the remote DB2 instance:
db2c_db2inst1 50000/tcp # DB2 connection service port
where db2inst1 is the name of the DB2 instance ID on the system.
The connection service port on the DB2 Client machine, WebSphere Portal Express server, must match the connection service port on the DB2 server. The ports should match by number but not necessarily by name.
On the DB2 server machine, set DB2COMM to TCP/IP by using the db2set command, as follows:
db2set DB2COMM=TCPIP
Set up the correct service name by entering the following command on the DB2 server machine:
db2 "UPDATE DBM CFG USING svcename svce_name"
where svce_name is the connection service port name that is specified in step 8.
If you are using a JDBC Type 2 connection: On the DB2 Client machine, set DB2COMM to TCP/IP by using the db2set command, as follows:
db2set DB2COMM=tcpip
If you are using a JDBC Type 2 connection: On the DB2 Client machine, WebSphere Portal Express server, catalog the TCP/IP node with the IP address of the remote database server, as follows:
db2 "catalog tcpip node remote_db_node_alias remote database_server_node server connection_service_port"
where remote_db_node_alias is the alias name of the Database Server that you are defining for the WebSphere Application Server 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 8.
The alias name can contain one to eight characters.
If you are using a JDBC Type 2 connection: On the DB2 Client machine, WebSphere Portal Express server, catalog the WebSphere Portal Express, JCR, Member Manager, Feedback and LikeMinds databases as follows:
Perform this step for all installations:
db2 "catalog db remote_db_name_release as release_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_community as comm_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_customization as cust_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_fdbkdb as fdbkdb_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_lmdb as lmdb_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_jcrdb as jcrdb_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_wmmdb as wmmdb_alias_name at node remote_db_node_alias"
where remote_db_name_<domain>, is the cataloged name of the databases on the server machine for each domain, <domain>_alias_name, is the database alias names that you are defining, remote_db_node_alias is the name that was used previously when you cataloged the TCP/IP node in the previous step.
The alias for each database must be different from the actual database name, and can only contain up to eight characters.
If you are using a JDBC Type 2 connection: Log out of the DB2 Client machine by entering the following command:
db2 "quit"
If you are using a JDBC Type 2 connection: On theDB2 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 14 and username is the database user.
Restart your database server.
Continue to Creating users.
Next steps

You have completed this step. Continue to the next step.

Parent topic:
Configuring DB2

Previous topic
Installing DB2

Next topic
Transferring DB2

Database domain properties
Property	Value
dbdomain.DbType	The type of database used to store information for WebSphere Portal Express. Type: Alphanumeric text string Recommended: DB2: db2
dbdomain.DbName	The name of the WebSphere Portal Express domain database and schema. Notes: This value is also the database element in the dbdomain.DbUrl property. For non-Windows platforms when using DB2, this value is the TCPIP Alias for the database. Type: Alphanumeric text string Notes: For DB2 this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information. For DB2, this value must be different from the value of dbdomain.XDbName. If you change the name of the WebSphere Portal Express data source due to a database migration, manually update this property in the portal_server_root/config/wpconfig_dbdomain.properties file to maintain the proper resource reference mapping. Recommended value for all domains: Release: release Community: comm Customization: cust JCR: jcrdb WMM: wmmdb Feedback: fdbkdb LikeMinds: lmdb
dbdomain.DbSchema	The schema name of the database domain. Notes: For i5/OS: dbdomain.DbSchema must match the postfix of dbdomain.DbName after /. For example, if release.DbName=LOCAL/REL60, then release.DbSchema=REL60. Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems, for example on i5/OS. Notes: This property is not used on Member Manager, which only uses the dbdomain.DbUser name as the schema. Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems. For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same. For Oracle only:* For non-feedback domains, DbSchema and DbUser MUST be the same. For Feeback domains, the default schema name is FEEDBACK. If the value is set to something besides FEEDBACK, you also have to set the schemaName property in <wps_home>/shared/app/config/services/FeedbackService.properties to the new schema. Type: Alphanumeric text string Default value: dbdomain
dbdomain.DbUrl	The database URL used to access the WebSphere Portal Express database with JDBC. The value must conform to standard JDBC URL syntax. The database element of this value should match the value of dbdomain.DbName. Type: Alphanumeric text string, conforming to standard JDBC URL syntax Recommended: DB2: jdbc:db2:wpsdb jdbc:db2://db2server.mycompany.com:50000/wpsdb:returnAlias=0; Please refer to the DB2 documentation for the correct syntax of the JDBC URL. JDBC type 2 connection: http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.apdv.java.doc/doc/cjvjt2cn.htm Example: jdbc:db2:wpsdb JDBC type 4 connection: http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.apdv.java.doc/doc/cjvclrrt.htm Example: jdbc:db2://db2server.mycompany.com:50000/wpsdb:returnAlias=0; The name of the database must be used in the URL; for example, wpsdb. The alias of the database should not be used in the URL.
dbdomain.DbUser	The user ID for the database administrator. Notes: For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same. For Oracle and SQL Server, if the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property. For Oracle only: For non-feedback domains, DbSchema and DbUser MUST be the same. For Feeback domains, the default schema name is FEEDBACK. If the value is set to something besides FEEDBACK, you also have to set the schemaName property in <wps_home>/shared/app/config/services/FeedbackService.properties to the new schema. Type: Alphanumeric text string Default for all domains: wpdb2ins ReplacewithyourDBAdminUser Recommended: Release: releaseusr Community: communityusr Customization: customizationusr JCR: icmadmin WMM: wmmdbusr Feedback: feedback LikeMinds: lmdbusr
dbdomain.DbPassword	The password for the database administrator. A value must be set for this property; it cannot be empty. Type: Alphanumeric text string Default for all domains: ReplaceWithYourDbAdminPwd
dbdomain.XDbName	The database loop back alias that needs to be set if you plan to use the create-local-database-db2 task. Notes: For DB2, this value must be different from the value of dbdomain.DbName. Type: Alphanumeric text string Default value: Release: wps6TCP Community: wps6TCP Customization: wps6TCP WMM: wps6TCP JCR: wps6TCP Feedback: fdbk6TCP LikeMinds: lmdb6TCP
dbdomain.DbNode	The value for the node database. Required for non-Windows platforms when using DB2 only. Type: Alphanumeric text string Default values: Release: wpsNode Community: wpsNode Customization: wpsNode JCR: wpsNode WMM: wpsNode Feedback value: pznNode LikeMinds value: pznNode
dbdomain.DataSourceName	The name of the data store that WebSphere Portal Express uses to communicate with its databases. Notes: If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains. In other words, this value must be unique for the database domain. The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName. i5/OS: The value for dbdomain.DataSourceName must match the postfix of dbdomain.DbSchema name. For example, if release.DbSchema=REL60, then release.DataSourcename=REL60. This name must be unique for each database schema. Follow the documentation of the target database management system in order to define a valid schema name, as restrictions apply for some database management systems. Type: Alphanumeric text string Default values: Release: wpsdbDS Community: wpsdbDS Customization: wpsdbDS JCR: JCRDS WMM: wpsdbDS Feedback: feedback5 LikeMinds: lmdbDS

Database type properties
Property	Value
DbSafeMode	This only applies to database-specific tasks. If this property is set to true, database-specific tasks, such as create/modify/drop database, will not be performed. The property should be used 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: false Default: false
db2.DbDriver	The name of the class that SqlProcessor will use to import SQL files. The JDBC driver class name depends on the JDBC connection type that will be used. Recommended: For JDBC type 2 connections: COM.ibm.db2.jdbc.app.DB2Driver For JDBC type 4 connections: com.ibm.db2.jcc.DB2Driver
db2.DbLibrary	The directory and name of the .zip or .jar file that contains the JDBC driver class. The value depends on the JDBC connection type that will be used. For JDBC type 2 connections the JDBC driver archive is named db2java.zip, but for JDBC type 4 connections the archive is split into two files: db2jcc.jar, which contains the JDBC driver, and db2jcc_license_*.jar, which contains the corresponding license. The name of the license archive depends on the actual license. For licensed connections to DB2 on Windows, Linux and Linux the file may be named db2jcc_license_cu.jar. The JDBC driver archives can be found in the DB2 installation directory in the "sqllib/java" subdirectory. Recommended: JDBC Type 2 connection: db2_install/java/db2java.zip JDBC Type 4 connection: db2_install/java/db2jcc.jar:db2_install/java/db2jcc_license_cu.jar In Linux environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.
db2.JdbcProviderName	The name of the JDBC provider that WebSphere Portal Express uses to communicate with its databases. Type: Alphanumeric text string