Status: resolved
Oracle Team Productivity Center: 11.1.1.2.0
Oracle WebLogic Server: 10.3.2
Environment: TELDE
First of all I wish all my readers out there a HAPPY AND SUCCESSFUL NEW YEAR 2010!
In a previous post I have blogged about setting up (a clean) Oracle Team Productivity Center Server. In this post I want to share my experience if you upgrade an existing OTPC database repository to 11.1.1.2 but want to install the otpc.war on a clean WLS 10.3.2 domain.
Issue
Tool/Area | Action |
Client | Start Xming |
Putty | Login as oracle {setup your environment} [oracle@telde ~]$ cd /u01/product/oracle/middleware/11.1.1/tpc/ [oracle@telde tpc]$ java -jar tpcinstaller.jar |
Installer | 1.Provide the database connection properties to the existing OTPC repository 2.Choose the autodeploy directory of a clean WLS 10.3.2 domain 3.Start installation |
You will encounter the following error |
So how to solve the installation error if you want to install on a clean WLS 10.3.2 domain?
Solution
Tool/Area | Action |
Putty | Login as oracle {setup your environment} OK so now we need to manually install the otpc.war into weblogic domain. 1) We first verify that it is included in the tpcinstaller: [oracle@telde tmp]$ jar -vft tpcinstaller.jar | grep otpc 2) Now we extract it and copy otpc.war to the domain home/autodeploy [oracle@telde tmp]$ jar -xf tpcinstaller.jar lib/otpc.war 3)Run the tpcinstaller once again!!!! 4)Start the WebLogic server [oracle@telde tmp]$cd $DH |
Background information
During installation of OTPC the otcp.war is modified so that it contains the correct database connection information.
[oracle@telde autodeploy]$ cd /u01/app/oracle/product/11.1.1.2/middleware/user_projects/domains/base_domain/autodeploy/
[oracle@telde autodeploy]$ ls -l
total 24252
-rw-r--r-- 1 oracle oinstall 8309132 Nov 5 07:43 otpc.war
-rw-r--r-- 1 oracle oinstall 16485122 Oct 30 01:33 otpc.war-1257402576730
-rw-r----- 1 oracle oinstall 2131 Nov 4 02:07 readme.txt
Those connection properties are stored in persistence.xml which itself is contained in _wl_cls_gen.jar file.
So if you encounter connection problems persistence.xml in the exploded app directory is the file you should first look to verify the connection properties.
No comments:
Post a Comment