The Diary of a Tech Warrior: November 2013

Wednesday, November 27, 2013

How to generate a thread dump and heap dump in WebSphere 7 on UNIX/LINUX/AIX

So you want to manually invoke a heapdump?

SSH/Telnet to the box.
Get to your WebSphere 7 AppServer/bin directory, e.g. /opt/Was7/AppServer/bin.
Run ./wsadmin.sh -profileName myProfileName -user wasadmin -password adminpassword (substitute your WAS profile name, user and password of course).
This will give you a prompt where you can enter commands.
First, we set a substitution variable with the full name of the object representing our app server:
set jvm [$AdminControl completeObjectName type=JVM,process=MyServerName,*]
Next, we can invoke the dumpThreads and/or generateHeapDump methods of that object:
$AdminControl invoke $jvm dumpThreads
$AdminControl invoke $jvm generateHeapDump
By default, the commands above will place the dump files in the root directory for your application profile, e.g. /opt/Was70/AppServer/profiles/myAppProfile.

And you are done :-)

Thursday, November 21, 2013

Portal v7002 fixpack installation fails with "Target `check-portal-level-CF' does not exist in this project

When installing the Portal v7002 fixpack on a binary Portal installation after installing any cumulative fix, the 7002 fixpack installation may fail with "Target `check-portal-level-CF' does not exist in this
project"

Symptom

In the console output at the time of the failure, you see the following exception:
=============================
Result: StdErr: BUILD FAILED
Result: StdErr: Target `check-portal-level-CF' does not exist in this project. It is used from target `action-validate-portal-version-for-multProfile-CF'.
Result: StdErr:
Result: StdErr: Total time: 4 seconds
Log: ExecCmd::launch returns 1
Task 2 out of 630; End Uninstalling fix ' PM49013', component 'wp.ptf.config'.
Task 3 out of 630; Begin Completing fix ' PM49013' subTmpDir to be cleaned up: /tmp/ptfs
The directory does not exist, or is not a directory, continue to run: /tmp/ptfs
Fix pack installation has failed. Consult
/usr/WebSphere7/PortalServer/version/log/20120217_085936_PM49013_uninsta
ll.log for error details.
chmod -R 550 /usr/WebSphere7/PortalServer done!
UpdateInstaller.puiReturnCode is 9
End of [ ./updatePortal.sh ]
=============================

A similar error can be seen in the ConfigTrace.log as well.

Cause

This issue occurs when the user has done the following:

- Installed Portal as a binary installation

- Upgraded Portal to v7001 + any CF

- Created a profile (or migrated)

- Updated the wps.properties with the new profile information

- Attempted to upgrade to v7002

The first step for any fixpack installation is to remove all fixes and cumulative fixes. The CF uninstall fails in this case and that is why the fixpack fails.

The CF uninstall fails because of a defect in the Portal Update Installer that prevents any fix or CF from uninstalling cleanly when it was originally installed on a binary install. This will be fixed in a later version of the Portal Update Installer.

Resolving the problem

If you encounter this exception, you must take the following steps to resolve it:

1. Edit the PortalServer/wps.properties file
2. Remove the ProfileName and ProfilePath parameters from it.
3. Manually uninstall the cumulative fix(es) you have applied
4. If the following file still exists after the CF uninstall, manually remove it:

PortalServer/installer/wp.config/config/includes/preconfig_cumulative_fix.xml

5. Edit the PortalServer/wps.properties file again and add ProfileName and ProfilePath back to the file.
6. Reattempt the 7002 fixpack installation.

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

Wednesday, November 20, 2013

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

Monday, November 18, 2013

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:

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

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

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

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;

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.

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

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

Monday, November 4, 2013

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

The Diary of a Tech Warrior