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

Step by Step Instructions for Configuring WebSphere Portal with Oracle

This article shows you how to transfer from default database to Oracle database in WebSphere Portal 6.1.

The article explains the various steps that are required to completely configure the WebSphere Portal to Oracle. These instructions can be used to perform the database transfer process for a stand-alone WebSphere Portal instance or can also be applied for a Clustered environment.

In WebSphere Portal 6.1, the Portal databases can be configured to DB2, Oracle or SQL Server. The portal databases can be configured to a local database server installed on the same machine or databases can be distributed to multiple database servers, located on the multiple remote database machines. This document explains how to configure the WebSphere Portal with Oracle database.

Assumptions:

WebSphere Portal 6.1 installed on a machine

Oracle 10g Server is running on a separate machine.

Steps:

1. The Oracle databases must be created manually before configuring WebSphere Portal. Make sure that all databases to be used with WebSphere Portal are created as UNICODE character set such as UTF8, AL32UTF8, or AL16UTF16.

In this scenario, I am considering creating 6 different oracle databases that will be used by WebSphere Portal. However multiple domains can share a single database, depending on your environment.

Domain                        Database

---

                      

---

Release                        RELDB

Community                   COMDB

Customization               CUSDB

Likeminds                     LMDB

Feedback                     FDBKDB

Jcr                                JCRDB

2. Make sure that the created databases are configured with the following values; the values for all databases will remain same except JCRDB that should have a value for open_cursors as 2500.

        db_block_size = 8192
        db_cache_size = 300M
        db_files = 1024
      & nbsp; log_buffer = 65536
        open_cursors = 1500  (2500 for JCR database)
        pga_aggregate_target = 200M
        pre_page_sga = true
        processes = 300
        shared_pool_size = 200M

3. If you are using remote Oracle databases, you must also copy the ojdbc14.jar file from the remote Oracle server to the WebSphere Portal/jdbc/lib
   machine. For example, the location of the jar file on the Portal machine can be C:/IBM/WebSphere/PortalServer/drivers

4. The database users should be created with certain privileges so that these users can access the Oracle databases used by WebSphere Portal.

        
create user release identified by passw0rd default tablespace ts_release temporary tablespace ts_release;
grant connect, resource to release;

create user community identified by passw0rd default tablespace ts_community temporary tablespace ts_community;
grant connect, resource to community;

create user customization identified by passw0rd default tablespace ts_customization temporary tablespace ts_customization;
grant connect, resource to customization;

create user feedback identified by passw0rd default tablespace ts_feedback temporary tablespace ts_feedback;
grant connect, resource, create session to feedback;

create user likeminds identified by passw0rd default tablespace ts_likeminds temporary tablespace ts_likeminds;
grant connect, resource, create session to likeminds;

create user jcr identified by passw0rd default tablespace ts_jcr temporary tablespace ts_jcr;
grant connect, reso urce, create session, alter session, create table, create view, create trigger, create library, execute any procedure, create sequence, insert any table to jcr;

create user wsadmin identified by passw0rd default tablespace ts_wsadmin temporary tablespace ts_wsadmin;
grant dba to feedback;

5. Use a text editor to open the properties file wp_profile_root/ConfigEngine/properties/wkplc_comp.properties and modify the values to correspond to your environment.

feedback.DbType=oracle

feedback.DbName=FDBKDB

feedback.DbSchema=feedback

feedback.DataSourceName=wpfdbkDS

feedback.DbUrl=jdbc:oracle:thin:@oracle.test.ibm.com:1521:FDBKDB

feedback.DbUser=feedback

feedback.DbPassword=passw0rd

feedback.DBA.DbUser=wsadmin

feedback.DBA.DbPassword=passw0rd

likeminds.DbType=oracle

likeminds.DbName=LMDB

likeminds.DbSchema=likeminds

likeminds.DataSourceName=wplmDS

likeminds.DbUrl=jdbc:oracle:thin:@oracle.test.ibm.com:1522:LMDB

likeminds.DbUser=likeminds

likeminds.DbPassword=passw0rd

likeminds.DBA.DbUser=wsadmin

likeminds.DBA.DbPassword=passw0rd

release.DbType=oracle

release.DbName=RELDB

release.DbSchema=release

release.DataSourceName=wprelDS

release.DbUrl=jdbc:oracle:thin:@oracle.test.ibm.com:1523:RELDB

release.DbUser=release

release.DbPassword=passw0rd

release.DBA.DbUser=wsadmin

release.DBA.DbPassword=passw0rd

community.DbType=oracle

community.DbName=COMDB

community.DbSchema=community

community.DataSourceName=wpcomDS

community.DbUrl=jdbc:oracle:thin:@oracle.test.ibm.com:1524:COMDB

community.DbUser=community

community.DbPassword=passw0rd

community.DBA.DbUser=wsadmin

community.DBA.DbPassword=passw0rd

customization.DbType=oracle

customization.DbName=CUSDB

customization.DbSchema=customization

customization.DataSourceName=wpcusDS

customization.DbUrljdbc:oracle:thin:@oracle.test.ibm.com:1525:CUSDB

customization.DbUser=customization

customization.DbPassword=passw0rd

customization.DBA.DbUser=wsadmin

customization.DBA.DbPassword=passw0rd

jcr.DbType=oracle

jcr.DbName=JCRDB

jcr.DbSchema=jcr

jcr.DataSourceName=wpjcrDS

jcr.DbUrl= jdbc:oracle:thin:@oracle.test.ibm.com:1526:JCRDB

jcr.DbUser=jcr

jcr.DbPassword=passw0rd

jcr.DBA.DbUser=wsadmin

jcr.DBA.DbPassword=passw0rd

Note that these values might be different in your case and should be changed according to your environment. For example, Oracle database host, instance port, database name, database names, user, passwords, schema names.

6. Use a text editor to open the properties file wp_profile_root/ConfigEngine/properties/wkplc_dbtype.properties and modify the following values to correspond to your environment. The value of oracle.DbLibrary must be the path where ojdbc14.jar was copied on the WebSphere Portal box.

oracle.DbDriver=oracle.jdbc.driver.OracleDriver

oracle.DbLibrary=C:/IBM/WebSphere/PortalServer/drivers/jdbc/lib/ojdbc14.jar

oracle.JdbcProviderName=wpdbJDBC_oracle

7. Open the following mapping files under wp_profile_root/PortalServer/config/tablespaces that specify the table space and index space property pairs for each database table:

community.space_mapping.properties

customization.space_mapping.properties

feedback.space_mapping.properties

jcr.space_mapping.properties

likeminds.space_mapping.properties

release.space_mapping.properties

Assign a table space to each entry in the mapping files. The table space name must be prepended by the keyword TABLESPACE and a space. For example: community.COMP_INST.tablespace=TABLESPACE TS_COMMUNITY Repeat this step for each domain that you are transferring.

8.   Create the tablespaces that are required for JCR domain using the following commands;           

Before using the following commands, replace &dbpath. with the actual database path on oracle jcr db. You also need to replace JCRDB with the name of jcr database if this is different in your case.

create tablespace ICMLFQ32 datafile '&dbpath./JCRDB/data/JCRDB_ICMLFQ32_01.dbf' size 300M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMLNF32 datafile '&dbpath./JCRDB/data/JCRDB_ICMLNF32_01.dbf' size 25M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMVFQ04 datafile '&dbpath./JCRDB/data/JCRDB_ICMVFQ04_01.dbf' size 25M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMSFQ04 datafile '&dbpath./JCRDB/data/JCRDB_ICMSFQ04_01.dbf' size 150M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMLSNDX datafile '&dbpath./JCRDB/index/JCRDB_ICMLSNDX_01.dbf' size 10M reuse autoextend on next 10M maxsize UNLIMITED extent management local autoallocate;

 

9.  Run the following commands as user SYS:

grant select on pending_trans$ to ; grant select on dba_2pc_pending to ; grant select on dba_pending_transactions to ; grant execute on dbms_system to ;

Where is the username configured in the Oracle datasource's authentication alias.

 

10. Open a command prompt and change to the directory wp_profile_root\ConfigEngine. Enter the following commands to validate configuration properties.
ConfigEngine.bat validate-database-driver
-DTransferDomainList=release,customization,community,jcr,feedback,likeminds

ConfigEngine.bat validate-database-connection
-DTransferDomainList=release,customization,community,jcr,feedback,likeminds

11. Stop both WebSphere Application Server and the WebSphere Portal server:

 

12.  Open a command prompt and change to the directory wp_profile_root\ConfigEngine. Enter the following commands to transfer the database to Oracle.
ConfigEngine.bat database-transfer
-DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DuseCustomTablespaceMapping=true
 
13. Start the Portal Server and test if you can login to the Portal Server.

Source : http://www-10.lotus.com/ldd/portalwiki.nsf/dx/06152009050451pmwebsuc.htm

IBM HTTP Server (IHS) - Installing it Silently on AIX

1) Create logical file system /IBM (or other name)
2) Download the following installation files from IBM WebSite - C1G2NML.tar.gz (WebSphere Supplements installation media)
3) Download the following FixPack files from IBM website.

Fixpacks
7.0.0-WS-IHS-AixPPC32-FP0000017.pak
7.0.0-WS-PLG-AixPPC32-FP0000017.pak

4) install IHS silently with root user
- Log on the server as root
- In /IBM/IHS7
gunzip C1G2NML.tar.gz
tar –xvf C1G2NML.tar
- Go to directory /IBM/IHS7/IHS
- Run command “cp responsefile.txt responsefile.txt.bak”
- Edit responsefile.nd.txt and set the following value
-OPT silentInstallLicenseAcceptance=”true”
-OPT allowNonRootSilentInstall=false
-OPT installLocation=”/IBM/HTTPServer”
-OPT createAdminAuth=”true”
-OPT adminAuthUser=”ihsadmin”
-OPT adminAuthPassword=”ihsadmin”
-OPT adminAuthPasswordConfirm=”ihsadmin”
-OPT runSetupAdmin=”true”
-OPT createAdminUserGroup=true
-OPT setupAdminUser=”ihsadmin”
-OPT setupAdminGroup=”ihsgroup”
-OPT washostname=”remote_was_host”
Uncomment the following options
-OPT disableOSPrereqChecking=”true”
And comment all others options
- Run the following command to install IHS7.0 server :
./install -options “responsefile.txt” -silent

See the log files in "/ihslogs/" for the installation status.

- After installation, go to directory /IBM/HTTPServer/bin, and check IHS version using “versionInfo.sh”, we will see the version of HTTP Server is 7.0.0.0, go to directory /IBM/HTTPServer/Plugins/bin, and check WebSphere Plugins version using “versionInfo.sh”, we will see the version of WebSphere Plugins version is 7.0.0.0

5)     Install Update Installer 7.0.0.17 on the server

- Go to Directory /IBM/UPDI/
- Run the command “gunzip 7.0.0.17-WS-UPDI-AixPPC32.tar.gz” and “tar –xvf 7.0.0.17-WS-UPDI-AixPPC32.tar”
- Go to Directory /IBM/cd_software/UPDI/UpdateInstaller
- Run the command “cp responsefile.updiinstaller.txt  responsefile.updiinstaller.txt.bak”
- Edit the file “responsefile.updiinstaller.txt” and set the following value
-OPT silentInstallLicenseAcceptance=”true”
-OPT installLocation=”/IBM/WebSphere/UpdateInstaller”
Uncomment the following options
-OPT disableOSPrereqChecking=”true”
-OPT disableEarlyPrereqChecking=”true”
Comment all other options
- Run the command “./install -options “responsefile.updiinstaller.txt” –silent” to install update installer

- Go to Directory /IBM/WebSpehre/UpdateInstaller to check Update Installer version, it should be “7.0.0.17 6) Install IHS and WebSphere Plugins fixpacks using Update Installer
- Go to Directory /IBM/WebSphere/UpdateInstaller/responsefiles
- Run the command “cp install.txt installIHS.txt” and “cp install.txt installPLG.txt”
- Edit installIHS.txt as the following:
-W maintenance.package=”/IBM/fixpack/7.0.0-WS-IHS-AixPPC32-FP0000017.pak”
-W product.location=”/IBM/HTTPServer”
- Edit installPLG.txt as the following:
-W maintenance.package=”/IBM/fixpack/7.0.0-WS-PLG-AixPPC32-FP0000017.pak”
-W product.location=”/IBM/HTTPServer/Plugins”
- Go to Directory /IBM/WebSphere/UpdateInstaller/bin, run the following command to apply the fixpacks
./update.sh -options responsefiles/installIHS.txt –silent
./update.sh -options responsefiles/installPLG.txt –silent

Monitor /IBM/WebSphere/UpdateInstaller/logs/tmp/updatelog.txt for updating status.

- Go to Directory /IBM/HTTPServer/bin and /IBM/HTTPServer/Plugins/bin, run the command “versionInfo.sh” to check that both version should be 7.0.0.17.
-  After installation, go to /IBM, run the following command to grant the permission
“chmod –fR 755 /IBM/HTTPServer”, “chown –fR wasuser:wasgroup /IBM/HTTPServer”
- Go to /IBM/HTTPServer/conf, edit httpd.conf and update the following values
User wasuser
Group wasgroup

- Go to /IBM/HTTPServer/bin, and run “adminctl start” and “apachectl –k start” to start IHS server.

WAS 7 ND - INSTCONFFAILED : NONROOT_INSTALL_DISALLOWED

Error located in the installation log (/ihslogs/) file for a WAS 7ND installation using a response file.

(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, ********************************************************************************
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Starting a new installation or uninstallation procedure.
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, ********************************************************************************
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Java Install Path: /opt/IBM/ITM/WebSphere/installs/WAS70/JDK/jre.pak/repository/package.java.jre/java/jre
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Name: AIX
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Architecture: ppc64
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Version: 6.1
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current User ID: wasadmin
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current User Home: /home/wasadmin
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current Working Directory: /opt/IBM/ITM/WebSphere/installs/WAS70/WAS
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.PopulateTitleBarAction, msg1, IBM WebSphere Application Server 7.0
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPFileDeleteAction, msg1, Deleting file: Source: /tmp/.aix_ISMP_lock____
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPWarningDialogAction, wrn, INSTCONFFAILED : NONROOT_INSTALL_DISALLOWED : Set the non-root install allowed setting to true in the response file before installing.
Correct the specification to proceed.
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process failed.
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=1
(04-Nov-2013 13:05:17), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED



Solving the Problem:

Edit your reponse file and add the follownig entry

-OPT allowNonRootSilentInstall=”true

IBM Business Process Manager (BPM) 8,8.0.1 and 8.5 Training

Hey Everyone

The BPM training for V8,8.0.1 and 8.5 is available from the IBM Website.URLs listed below:


http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.ibpmgr/ibpmgr/8.0/ProcessDesigner.html

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.ibpmgr/ibpmgr/8.5/ProcessDesigner.html

Your in WebSphere
Jerome Slinger

WAS 8 and 8.5 Training Labs have been Released

Hi my fellow WebSpherians

Don't forget to visit the WebSphere Application Server version 8 and 8.5 training labs.

Attached the URLS :


http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v8/was/8.0/Labs.html

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v8/was/8.5/Labs.html

Your in WebSphere
Jerome

Caching Issue in WebSphere Portal version 6.1, 7.0 and 8.0

Currently Committed database setting - Applies to DB2 v9.7 or higher and WebSphere Portal version 6.1 and 7.0

 

DB2 V9.7 introduced a new default behaviour for isolation level cursor stability (CS) (see http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.config.doc/doc/r0053556.html).
In WebSphere Portal this has implications for the cache invalidation strategy related to transactions. The new DB2 default behaviour for isolation level cursor stability (CS) is to NOT block code that wants to read data which is still being worked on in an uncommitted transaction in another thread (DB2 returns the result, as if the other transaction would not exist). But WebSphere Portal version 6.1 and 7.0 cache invalidation and refill strategies rely on the blocking at database level. With the new 'currently committed' default setting, stale data in Portal caches can occur.

Starting with Portal version 8.0 the setting of CUR_COMMIT to ENABLED is supported.

Besides the fact that CUR_COMMIT must be set to DISABLED for WebSphere Portal version 6.1 and 7.0, WebSphere Portal development does not expect a performance degradation when changing the value of CUR_COMMIT from ENABLED to DISABLED. For some scenarios with long database transactions, it could be that response times increase due to additional waits for updated data.

The setting of CUR_COMMIT is applied at database level. Therefore it is required to set CUR_COMMIT to DISABLED for the Portal database(s), containing the Portal database domains release, community, customization, jcr, feedback, and likeminds.

Disabling CUR_COMMIT in DB2 Version 9.7:

Ask your DB2 administrator to ensure that CUR_COMMIT is disabled by carrying out the following steps (for each of the Portal databases):

1. Connect to the runtime database:
   $ db2 connect to
   where represents the name of the database.
   
2. List the CUR_COMMIT parameter:
   $ db2 get db cfg show detail | grep CUR_COMMIT
   The output should look like this:
   Currently Committed (CUR_COMMIT) = DISABLED DISABLED
   
3. If the values are anything other than two times DISABLED (one for the current setting used, the other for the delayed setting specified in the configuration), change the value to DISABLED:
   $ db2 update db cfg using CUR_COMMIT DISABLED
   
4. Close the database connection:
   $ db2 connect reset
   
5. Check that no other application is connected to the database,to make the change effective (This e.g. requires to stop the Websphere Portal Server that uses the database). List the connected applications like this:
   $ db2 list applications for db
   where represents the name of the database.
   The output should look like this:
   SQL1611W No data was returned by Database System Monitor.
   
6. Ensure that the settings are correct by repeating the steps 1. and 2.

Full technote and source : http://www-01.ibm.com/support/docview.wss?uid=swg27037929&myns=swgws&mynp=OCSSHRKX&mync=E#!

Migration to an empty Portal 6.1.x will not work.

Hi All

I am posting this in reply to so many questions that came in surrounding migration.

Please note that you can experience this in 7.0 and 8.0.

 

Technote (FAQ)

Question

One is often drawn into a speculation that migration onto an empty portal will work. Migration to an empty portal will not work.

Answer

Migration to an empty portal will often fail because of various reasons. The empty portal typically contains a few content-nodes, application roles and certain other virtual resources and no other portal artifacts like portlets, pages, themes, skins. The migration scripts are typically looking for these artifacts to do the migration. And hence the failure.

Source : http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21383211

 

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