Creating the WebSphere Portal 7 databases

Creating DB2 database

A remote database resides on a different system than Web Sphere Portal. When you use a remote server, you must manually create the databases that are required by Web Sphere Portal.

Before creating these databases, note the following information:

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

o The client software, DB2 Connect, must be correctly configured to connect to the remote DB2 server instance, for example, db2inst1.

These instructions assume that a remote DB2 server and DB2 Connect are already installed and running. For information on installing DB2 Connect, see the DB2 product documentation.
These instructions assume that you are using DB2 Connect to connect to a remote DB2 server, and that WebSphere Application Server, WebSphere Portal, and DB2 Connect are installed on the same system

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

       $ db2inst1/password (A common user name is db2inst1)

2. Ensure that the user database 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 topic for information on how to create users.

3. Initialize a DB2 command environment by opening a command prompt and typing su - db2inst1

4. Run the following commands on the DB2 server system to configure the DB2 database instance:    

      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 50000"

5. Run the following commands on the DB2 server system to create the necessary databases:

 Notes:

          * Replace dbname with the actual name of the database. Run the commands and each time replace dbname with the actual values for release, community, customization, Java Content Repository, Feedback, and Likeminds.

            Remember: DB2 database names cannot exceed eight characters. Therefore, consider using these database names: release, commun, custom, jcrdb, fdbkdb, and lmdb.

               I.      create release db:

db2 "CREATE DB release using codeset UTF-8 territory us PAGESIZE 8192"

db2 "UPDATE DB CFG FOR release USING applheapsz 4096"

db2 "UPDATE DB CFG FOR release USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR release USING stmtheap 32768"

db2 "UPDATE DB CFG FOR release USING dbheap 2400"

db2 "UPDATE DB CFG FOR release USING locklist 1000"

db2 "UPDATE DB CFG FOR release USING logfilsiz 4000"

db2 "UPDATE DB CFG FOR release USING logprimary 12"

db2 "UPDATE DB CFG FOR release USING logsecond 20"

db2 "UPDATE DB CFG FOR release USING logbufsz 32"

db2 "UPDATE DB CFG FOR release USING avg_appls 5"

db2 "UPDATE DB CFG FOR release USING locktimeout 30"

db2 "UPDATE DB CFG FOR release using AUTO_MAINT off"

             II.      create community db

db2 "CREATE DB commun using codeset UTF-8 territory us PAGESIZE 8192"

db2 "UPDATE DB CFG FOR commun USING applheapsz 4096"

db2 "UPDATE DB CFG FOR commun USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR commun USING stmtheap 32768"

db2 "UPDATE DB CFG FOR commun USING dbheap 2400"

db2 "UPDATE DB CFG FOR commun USING locklist 1000"

db2 "UPDATE DB CFG FOR commun USING logfilsiz 4000"

db2 "UPDATE DB CFG FOR commun USING logprimary 12"

db2 "UPDATE DB CFG FOR commun USING logsecond 20"

db2 "UPDATE DB CFG FOR commun USING logbufsz 32"

db2 "UPDATE DB CFG FOR commun USING avg_appls 5"

db2 "UPDATE DB CFG FOR commun USING locktimeout 30"

db2 "UPDATE DB CFG FOR commun using AUTO_MAINT off"

           III.      creating customization db

db2 "CREATE DB custom using codeset UTF-8 territory us PAGESIZE 8192"

db2 "UPDATE DB CFG FOR custom USING applheapsz 4096"

db2 "UPDATE DB CFG FOR custom USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR custom USING stmtheap 32768"

db2 "UPDATE DB CFG FOR custom USING dbheap 2400"

db2 "UPDATE DB CFG FOR custom USING locklist 1000"

db2 "UPDATE DB CFG FOR custom USING logfilsiz 4000"

db2 "UPDATE DB CFG FOR custom USING logprimary 12"

db2 "UPDATE DB CFG FOR custom USING logsecond 20"

db2 "UPDATE DB CFG FOR custom USING logbufsz 32"

db2 "UPDATE DB CFG FOR custom USING avg_appls 5"

db2 "UPDATE DB CFG FOR custom USING locktimeout 30"

db2 "UPDATE DB CFG FOR custom using AUTO_MAINT off"

          IV.      creating jcrdb db

db2 "CREATE DB jcrdb using codeset UTF-8 territory us PAGESIZE 8192"

db2 "UPDATE DB CFG FOR jcrdb USING applheapsz 4096"

db2 "UPDATE DB CFG FOR jcrdb USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR jcrdb USING stmtheap 32768"

db2 "UPDATE DB CFG FOR jcrdb USING dbheap 2400"

db2 "UPDATE DB CFG FOR jcrdb USING locklist 1000"

db2 "UPDATE DB CFG FOR jcrdb USING logfilsiz 4000"

db2 "UPDATE DB CFG FOR jcrdb USING logprimary 12"

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 avg_appls 5"

db2 "UPDATE DB CFG FOR jcrdb USING locktimeout 30"

 V.      creating fdbkdb db

                                                                                                     

db2 "UPDATE DB CFG FOR jcrdb using AUTO_MAINT off"

db2 "CREATE DB fdbkdb using codeset UTF-8 territory us PAGESIZE 8192"  

 db2 "UPDATE DB CFG FOR fdbkdb USING applheapsz 4096"

db2 "UPDATE DB CFG FOR fdbkdb USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR fdbkdb USING stmtheap 32768"

db2 "UPDATE DB CFG FOR fdbkdb USING dbheap 2400"

db2 "UPDATE DB CFG FOR fdbkdb USING locklist 1000"

db2 "UPDATE DB CFG FOR fdbkdb USING logfilsiz 4000"

db2 "UPDATE DB CFG FOR fdbkdb USING logprimary 12"

db2 "UPDATE DB CFG FOR fdbkdb USING logsecond 20"

db2 "UPDATE DB CFG FOR fdbkdb USING logbufsz 32"

db2 "UPDATE DB CFG FOR fdbkdb USING avg_appls 5"

db2 "UPDATE DB CFG FOR fdbkdb USING locktimeout 30"

db2 "UPDATE DB CFG FOR fdbkdb using AUTO_MAINT off"

          VI.      creating lmdb db

db2 "CREATE DB lmdb using codeset UTF-8 territory us PAGESIZE 8192"

db2 "UPDATE DB CFG FOR lmdb USING applheapsz 4096"

db2 "UPDATE DB CFG FOR lmdb USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR lmdb USING stmtheap 32768"

db2 "UPDATE DB CFG FOR lmdb USING dbheap 2400"

db2 "UPDATE DB CFG FOR lmdb USING locklist 1000"

db2 "UPDATE DB CFG FOR lmdb USING logfilsiz 4000"

db2 "UPDATE DB CFG FOR lmdb USING logprimary 12"

db2 "UPDATE DB CFG FOR lmdb USING logsecond 20"

db2 "UPDATE DB CFG FOR lmdb USING logbufsz 32"

db2 "UPDATE DB CFG FOR lmdb USING avg_appls 5"

db2 "UPDATE DB CFG FOR lmdb USING locktimeout 30"

db2 "UPDATE DB CFG FOR lmdb using AUTO_MAINT off"

6. Complete the following:

          On the DB2 server system, run the following commands. This step is only required for the IBM Java Content     

          Repository database (jcrdb).

                * jcrdb is the name of the database used to store user data and objects

                * jcr is the database user for jcrdb

                  Note: This value can be replaced with any ID that has administrative authority.

                * dbpassword is the password for jcrdb

db2 "CONNECT TO jcrdb USER db2inst1 USING password"

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"

7. On the DB2 server system, check the services file. If it does not specify DB2 connection and interrupt service ports,

     specify the ports for your operating system:

    Use a text editor to open the file vi /etc/services and add the following text (where db2inst1 is the name of the DB2    

     instance ID on the system):

    (Shift G -- end of line in vi editor)

db2c_db2inst1 50000/tcp # DB2 connection service port

db2i_db2inst1 50001/tcp # DB2 interrupt service port

8. On the DB2 server system, set DB2COMM to TCP/IP by using the db2set command:

     db2set DB2COMM=TCPIP

9. Set up the correct service name by entering the following command on the DB2 server system:

db2 "UPDATE DBM CFG USING svcename db2c_db2inst1"

where svce_name is the connection service port name that is specified above.

DB2 Migration

In addition, the database administrator user “db2inst1” will be used as the user ID for each database.

For Cluster :All of the steps in this section will be done from the primary Portal node.

                                                                             

1. Stop the WebSphere_Portal and server1 by executing the following commands from the command window in the   

    /bin directory:

         stopServer.bat WebSphere_Portal -user -password 

         stopServer.bat server1 -user -password   pwd>

2. Ensure the database Enterprise Edition is installed and configured on the node.

    Since we are using Type 4 Drivers for DB2, all that is needed is to copy the db2jcc.jar and db2jcc_license_cu.jar   

    files from the DB2 server (/opt/ibm/db2/V9.7/java)to some directory on the primary Portal server.

3. From the /ConfigEngine/properties directory, make a backup of the following files:

wkplc.properties

wkplc_dbtype.properties

wkplc_dbdomin.properties

4. Edit the wkplc_dbtype.properties file and make the following changes:

    copy jars from db2 server to portal and give the path here:

             db2.DbDriver=com.ibm.db2.jcc.DB2Driver

             db2.DbLibrary=C:/IBM/db2drivers/db2jcc.jar;C:/IBM/db2drivers/db2jcc_license_cu.jar

             db2.JdbcProviderName=wpdbJDBC_db2

NOTE: The entry for db2.DbLibrary is an example only. Please ensure this is a valid path on your system.For Windows the separator is ; and Unix its : (e.g /opt/db2jars/db2jcc4.jar:/opt/db2jars/db2jcc_license_cu.jar)

5. Edit the wkplc_comp.properties file and make the following changes: ( Use wkplc_dbdomain.properties in Portal 7.0    

    instead wkplc_comp)

feedback.DbType=db2

feedback.DbName=fdbkdb    

feedback.DbSchema=FEEDBACK

feedback.DataSourceName=wpdbDS_fdbk

feedback.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/fdbkdb:returnAlias=0;

feedback.DbUser=db2inst1

feedback.DbPassword=password

feedback.DBA.DbUser=db2inst1

feedback.DBA.DbPassword=password

likeminds.DbType=db2

likeminds.DbName=lmdb

likeminds.DbSchema=likeminds

likeminds.DataSourceName=wpdbDS_lmdb

likeminds.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/lmdb:returnAlias=0;   

likeminds.DbUser=db2inst1

likeminds.DbPassword=password

likeminds.DBA.DbUser=db2inst1

likeminds.DBA.DbPassword=password

release.DbType=db2

release.DbName= release

release.DbSchema=release

release.DataSourceName=wpdbDS_release

release.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/release:returnAlias=0;

release.DbUser=db2inst1

release.DbPassword=password

release.DBA.DbUser=db2inst1

release.DBA.DbPassword=password

community.DbType=db2

community.DbName=commun

community.DbSchema=community

community.DataSourceName=wpdbDS_commun

community.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/commun:returnAlias=0;

community.DbUser=db2inst1

community.DbPassword=password

community.DBA.DbUser=db2inst1

community.DBA.DbPassword=password

customization.DbType=db2

customization.DbName=custom

customization.DbSchema=customization

customization.DataSourceName=wpdbDS_custom

customization.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/custom:returnAlias=0;

customization.DbUser=db2inst1

customization.DbPassword=password

customization.DBA.DbUser=db2inst1

customization.DBA.DbPassword=password

jcr.DbType=db2

jcr.DbName=jcrdb

jcr.DbSchema=jcr

jcr.DataSourceName=wpdbDS_jcrdb

jcr.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/jcrdb:returnAlias=0;

jcr.DbUser=db2inst1

jcr.DbPassword=password

jcr.DBA.DbUser=db2inst1

jcr.DBA.DbPassword=password

Update the following property in the file wkplc.properties.

 For WasPassword, type the password for the WebSphere Application Server security authentication used in your  

 environment.

PortalAdminPwd=password

WasPassword=password

6. From a command window, change directories to /ConfigEngine

7. Execute the following ConfigEngine scripts to validate the database properties:

ConfigEngine.bat validate-database-driver

ConfigEngine.bat validate-database-connection

8. Execute the following ConfigEngine script to transfer the database from Derby to DB2:

ConfigEngine.bat database-transfer -DPortalAdminPwd= -DWasPassword=

9.Restart all servers and check the logs. (server1 and WebSphere_Portal)

source : http://www-10.lotus.com/ldd/portalwiki.nsf/dx/ConfigureWeb_Sphere_Portal_to_use_DB2

Wpcollector tool, new in WebSphere Portal 7.0 and 8.0

Wpcollector is a new command line tool that automates the collection of portal logs and configuration files and optionally assists the customer with sending those files to IBM Support, saving valuable time. Using automated log collection early in the PMR life cycle can greatly reduce the number of doc requests that are made by Support. Wpcollector is an excellent tool for those customers that are not able to download and install ISA Lite in their portal environment.

Wpcollector is delivered with WebSphere Portal beginning with the 7.0 release. A significant difference between wpcollector and ISA Lite is that ISA Lite will automatically enable the correct traceString and collect the appropriate files based on the problem type selected in the ISA Lite GUI. Wpcollector, however, does not currently have a mechanism for the user to specify the problem type. Therefore, if tracing is required for the problem, the customer must manually enable traceStrings and recreate the problem PRIOR to running wpcollector. Similarly, because wpcollector consists of only 1 script, it collects all of the files for all of the various problem types each time the tool is run.

To run wpcollector, please follow the steps, below:

• If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below:

• If using Microsoft Windows, Unix/Linux, or IBM i, run the following script from the /PortalServer/bin/ directory to begin the collection:
  
  Windows: wpcollector.bat
  Unix/Linux: wpcollector.sh
  i: wpcollector.sh
  Tip: To specify the option for automatically sending the collection to IBM Support via FTP, use the "pmr" parameter. This will associate the collection with the PMR (Problem Management Record) specified. Be sure to format the number using either periods or commas. For example:
  wpcollector.bat -Dpmr=nnnnn.bbb.ccc (nnnnn=PMR number, bbb=branch, ccc=country code)
  Tip: To specify the option for collecting files for the Deployment Manager profile, use the "dmgr.root" parameter. For example:
  wpcollector.bat -Ddmgr.root=/opt/IBM/WebSphere/profiles/dmgr_profile
• If using IBM z/OS, proceed as follows:
  
  Start the WebSphere Portal Customization Dialog.
  In the Portal configuration panel, select Collect Diagnostics.
  Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS).
  Tip: To specify the option for automatically sending the collection to IBM Support via FTP, respond to the "Transmit PMR Data" prompt with "Y" in the ISPF panel as follows:
  Transmit PMR data to IBM .................................: Y
  Tip: To collect data from the Deployment Manager, the only requirement is to submit the job from the system where the Deployment Manager is installed (i.e. so it can access the files). There is no prompt in the ISPF panel for this.
  
  
• If the automatic send/FTP option was not specified, a manual transfer of the collection to IBM will be necessary. Locate the wp.mustgather-.zip file or the -wp.mustgather-.zip file in the <wp_profile_root>/filesForAutoPD/ directory and follow the instructions in "Exchanging information with IBM Technical Support for problem determination" to manually FTP the collection to IBM. If using z/OS, there may be additional z/OS-specific files required, such as WebSphere Portal servant region or controller region joblogs. Wpcollector currently does not collect these files. Your L2 Support Engineer will inform you in the event these files are needed and provide instructions for collecting them. 

Do not underestimate this tool as when raising a PMR it is best to ensure that IBM support have all the information they need.

Happy Trails
Jerome Slinger

WCM page and authoring portlet may not display after migration

Greetings Fellow WebSpherians

I am posting this one in response to a few queries that were mailed to me and here's to it being helpful :

After migrating to IBM WebSphere Portal V7.0, you may not be able to navigate to or display the Web Content Manager (WCM) out-of-box page or the authoring portlet. In addition, some related functions in the user interface might not work or might generate exceptions when accessed. Clicking buttons in the authoring portlet may generate the following error in the log:

IWKAP0009E: Servlet not enabled.

If this occurs, you must re-enable these features manually after migration.

Cause

The migration process can disable some new out-of-the-box features if the feature did not exist in the previous release or if it was updated. In particular, the Portal page required for the reserved authoring portlet is missing and the permissions on the AJAX proxy servlet are not set correctly.

Resolving the problem

To re-enable the affected features manually after migration, do the following:

1. Make sure that the page on which the WCM authoring portlet is installed uses a theme with client-side rendering such as the Page Builder theme.
2. Deploy the hidden Portal page on which the reserved authoring portlet is installed.

3. Run the following task from the wp_profile_root / Config Engine directory.

Cluster note: Run this task on the primary node in a V7 clustered environment.

Windows:
ConfigEngine.bat install-wcm-hidden-authoring-page -DWasPassword=password

UNIX:
./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=password

i/System:
ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=password

z/OS (run from the UNIX shell) :
./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=password

No restart of the Portal server is required.