I Migrated the EP Database to different machine and made neccessary changes in the portal to make it point to the new database.
Then i tried to change the custom deployed applications to make it point to new database. so Got the somecomp.par.bak from /<Portal_installation_path>/cluster/server/services/
servlet_jsp/work/jspTemp/irj/root/WEB-INF/deployment/pcd. Imported it into Eclipse, changed connection properties code, built it and coverted to par file. Deployed that file into portal using java developement tab. Even after uploading a new par, application is still pointing to old database.
While deploying, it wrote some log into error_log file as follows:
Jan 13, 2006 9:43:38 AM ...rtal.prt.service.config.ConfigDeploymentService [Client_Thread_14] Warning": An upload sequence w
ill start now. Please do not stop the server or serious deployment issues may arise.
Jan 13, 2006 9:43:39 AM ...rtal.prt.service.config.ConfigDeploymentService [Client_Thread_14] Warning": The upload sequence
is now complete, all the upgrades have been performed.
warning: Jar is empty: /usr/sap/AAA/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/po
What may be the cause of this error?
EP6 SP2 Patch 29
SAPJ2EE 6.20 Patch 29
Message was edited by: nilz