Skip to Content
author's profile photo Lakshmikanthaiah S
0
Lakshmikanthaiah S

Problem in running Portal Deployment Analyzer

Posted on Jan 22, 2005 at 04:38 AM 9 Views

Please solve my problems as below

1.The Portal Deployment Analyzer 'go.bat' not found in the below path.

/usr/sap/<SAP J2EE instance name>/j2ee/j2ee_<instance number>/analyzer.

2. The below folder contain error file: com.sapportals.pct.troom.actionitems.par.err

/usr/sap/<SAP J2EE instance name>/j2ee/j2ee_<instance number>/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/deployment/pcd

and the also com.sapportals.pct.troom.actionitems.par contains as below message

Jan 13, 2005 12:31:16 PM # ClusterManager co... Fatal Application upload failed: com.sapportals.pct.troom.actionitems.par

com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: com.sapportals.pct.troom.actionitems.par

at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:308)

at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:696)

at com.sapportals.portal.prt.deployment.DeploymentManager.populateRuntimeRepository(DeploymentManager.java:506)

at com.sapportals.portal.prt.deployment.DeploymentManager.runtimeRepositoryDeployment(DeploymentManager.java:276)

at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:368)

at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)

at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)

at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)

at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)

at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)

at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)

at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)

at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)

at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)

at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)

at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)

at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)

at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)

at java.security.AccessController.doPrivileged(Native Method)

at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)

Caused by: java.util.zip.ZipException: error in opening zip file

at java.util.zip.ZipFile.open(Native Method)

at java.util.zip.ZipFile.<init>(ZipFile.java:105)

at java.util.zip.ZipFile.<init>(ZipFile.java:121)

at com.sapportals.portal.prt.deployment.ArchiveIntrospector.getDeploymentDescriptor(ArchiveIntrospector.java:54)

at com.sapportals.portal.prt.deployment.DeploymentManager.getDeploymentDescriptor(DeploymentManager.java:938)

....

Please any body provide me the solution for the same,

i just want to run the portal deployment analyzer to test my installation

thanx in advance

regards

kantha

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Detlev Beutner
    Detlev Beutner
    Posted on Jan 22, 2005 at 01:24 PM
    0

    Hi Kantha,

    again the question, on what version you are on.

    1. At least on J2EE Engine 6.20, the analyzer tool is to be found under \usr\sap\<...>\j2ee\j2ee_<...>\tools\analyze [analyzerGUI.bat] or under \usr\sap\<...>\j2ee\j2ee_<...>\tools\analyzer [go.bat], depending on the patch level.

    2. See install notes for unsuccessful deployments:

    -

    In case of deployment failures, perform the following steps:

    UNIX only: If there are *.PAR.ERR files after deployment, go to the directory where those files are located and run one of the following lines:

    For *.PAR.ERR files:

    ls -d .par.err | sed 's/\(.\)\.par.err$/mv & \1.par/' | sh

    These scripts remove the ERR suffix from the file name (all PAR.ERR files to PAR).

    Windows only: If there are *.PAR.ERR files after deployment, go to the directory where those files are located and rename the files using the Windows Explorer.

    Of course, it is also possible to rename the *.PAR.ERR files manually.

    1. Restart SAP J2EE Engine.

    If on UNIX, you need to restart the SAP J2EE Engine with account j2eeadm.

    -

    Hope it helps

    Detlev

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.