Error while deplye logon par file in NWDS
Hello Everybody,
Here I am using EP 7 and SP 14. I have to change my Portal Logon PAR file as I have to add some hyperlinks in my par file.
Now problem is , after importing par file in NWDS i made some changes.Then at the time of exporting file, it ask for deployement. When i deploye par file it is throwing error:
Operation Faliled:please make sure server is running or check log for more details.
so i checked the logs. It is like :
java.io.IOException: Server returned HTTP response code: 500 for URL: http://epdev:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=&j_password=null&j_authscheme=default&uidPasswordLogon=Log%20on
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Kindly help me out. i'll be really very thankfull.
Thanks & Regards
Nivedita
Hi Nivedita,
You could try to delete the entry from the NWDS preferences and set the data there again. Set all the needed information like the portal host name, port, user name. And try not to select the option to save the passwords and check if NWDS does ask for a password then. (Also restart NWDS, I learnt that restart sometimes works wonders :P )
If it yet doesnt work, build the par file and then logon to the portal as administrator and go to tab System Administration->Support->Portal Runtime->Administration Console. Browse to your par file and click on upload.
Good Luck!
GLM
Similar Messages
-
Error while importing logon par file into NWDS.
Dear Friends ,
I m trying to customise the logon screen for my project. For this I have downloaded the "com.sap.portal.runtime.logon.par.bak" from portal server instance with the help of basis team. I have locally saved this file on my desktop[. I have renamed the file as .par and removed the .bak extension. Now I have tried to import the file onto NWDS in EP perspective by following File>Import>Par file. But its giving me this error:
error in opening zip file
Reason: Sorry, an error occured creating the new project.
The plugin "com.sap.portal.plugins.config-archiver caused an exception during the
"Unpack" Operation See log for more details.
In some of the solutions provided in SDN saying that after renaming the file to par open with zip if i done it is again showing the error as "Start of the central directory not found .Zip file corrupt.Possible cause :file transfer error."
Kindly suggest me the solution.
Thanks and regards.Hi,
I think you have taken this file from a wrong path and hence this issue.
Pls download the par file from the below path and try importing it into EP perspective..
System admin> Support>Portal Runtime > Browse Deployment>
Browse through the following to find the com.sap.portal.runtime.logon.par.bak file:
WEB-INF u2013> deployment u2013> pcd
Root>WEB-INF>Portal>Portalapps> temp--> download the com.sap.portal.runtime.logon.par.bak
Regards,
Vijay.
Edited by: VijayKPappala on Sep 7, 2011 8:46 AM -
Error while deploying a PAR file from NWDS into an ECC.
Hi all,
I am getting this error while deploying a PAR file from NWDS into an ECC.
Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
more detail.
My server is running properly
1 - Where is sap-plugin.log file? I don´t find it.
2 - Could there be another file with another name with information about the error?
3 - Is there another way to deploy the file directly from the ECC?
Regards,Hi,
Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
Windows/ Prefereces / SAP Enterprise Portal
Check the following enteries
Alias
Host
Port
Login etc.
Regards, -
Error while importing logon par file
Hi
I have to do logon page customisation for that i have taken com.sap.portal.runtime.logon.par.bak file from basis team and i saved it to my desktop .Now i have renamed it to com.sap.portal.runtime.logon.par and trying to import to my NWDS.
So i opend EP perspective file->import->browsed the par file in place of Archive file name when i click on finish it is showing the error "invalid END header(bad central directory offset).
"The plugin com.sap.portal.plugins.config-archiver"caused an exception during the unpack operation.see log for more details"
Can anybody please let me know the reason for this error .
Thanks in advance.Hi,
After renaming com.sap.portal.runtime.logon.par.bak to com.sap.portal.runtime.logon.par. Try opening the file with winrar/winzip to see if you have a right par file structure. On some portal versions, when you open com.sap.portal.runtime.logon.par file, you have again a com.sap.portal.runtime.logon.par file inside it.
So if you find com.sap.portal.runtime.logon.par file inside com.sap.portal.runtime.logon.par. Then just extract it again and try importing it into NWDS.
Please refer to [link|NWDS Log - PAR import error;
Hope this helps!!
Thanks & Regards
Vijay -
Error while deploying the par file
while deploying an application in NWDS we are getting the error as"operation failed,please make sure that the server is running or check the log."
we have ensured that the server is running,but the deployment is getting failed.
Please suggest tips to deploy the PAR file successfully.
Thanks.Hi,
We are using NWDS to create a small application to develop ( for ex jspdynpage)
.while deploying the par file or exporting it to the server,we are getting the error as "please make sure that the server running.HTTPS protocol is not supported,please ensure that this server is not using HTTPS.
the server is running and is shown in green.
we have also disabled the proxy settings.
we have also tried by specifiing the IP of the server in the proxy settings.
the above steps didnt work.please suggest the things to do to make this working.
thanks,
rajani. -
Error while uploading the PAR file of Production to UAT-
Hi Experts,
Could you please help me out in resolving the error which i'm facing while uploading the PAR file.
1. I have downloaded the par file from the production, imported to my NWDS.
2. Made changes to my HeadiView.jsp
3. I want to test my implementation in UAT.So i have uploaded the PAR to UAT system.
4. Below is the error i'm getting from the Log trace.
#1.#D27E2000F002008200000020000BD0FE0004436CD4EBF6C2#1200034614604#com.sap.porta
l.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#BVISHALA#17971##adcapsap18.
uk_QP0_16441150#BVISHALA#5d8f9460c01111dcafa2d27e2000f002#Thread[PRT-Async 2,5,P
RT-Async]##0#0#Error##Java###06:56_11/01/08_16441150
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in in
it method
Component : com.tw.navigation.Masthead.HeaderiView
at com.sapportals.portal.prt.component.PortalComponentContext.init(Porta
lComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refr
esh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getC
ontext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getCompone
ntContext(PortalComponentRequest.java:387)
at com.sapportals.portal.pb.PageBuilder.createIviewProfile(PageBuilder.j
ava:443)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.j
ava:233)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:6
36)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEve
nt(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:816
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEve
nt(CachablePortalComponent.java:703)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode
.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.j
ava:368)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.
java:340)
at com.sapportals.portal.navigation.PortalLauncher.doOnNodeReady(PortalL
auncher.java:318)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEve
nt(AbstractPortalComponent.java:388)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode
.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.j
ava:368)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.
java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(P
ortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(
ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatc
her.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:242
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.ja
va:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.se
rvice(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcher
Impl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcher
Impl.forward(RequestDispatcherImpl.java:377)
at com.sap.portal.navigation.Gateway.service(Gateway.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServle
t(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleReq
uest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServle
t(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServle
t(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebCo
ntainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(Requ
estAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:9
5)
at com.sap.engine.services.httpserver.server.Processor.request(Processor
.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSes
sionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRu
nner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:3
7)
at java.security.AccessController.doPrivileged(AccessController.java:215
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.ja
va:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:1
70)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationExc
eption: Could not instantiate implementation class com.btexx.pct.easyWCM.navigat
ion.masthead.HeaderiView of Portal Component com.tw.navigation.Masthead.HeaderiV
iew because: Could not find implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getIn
stanceInternal(PortalComponentItemFacade.java:242)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getCo
mponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponen
tInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getCompone
nt(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(Porta
lComponentContext.java:242)
... 44 more
Caused by: java.lang.ClassNotFoundException: com.btexx.pct.easyWCM.navigation.ma
sthead.HeaderiView
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getIn
stanceInternal(PortalComponentItemFacade.java:228)
... 48 more
Kindly help me to resolve this issue.
Many Thanks,
B.Vishali.Hi,
The problem might be caused by the version inconsistency of your J2EE and Portal Platform.
Please check the version of your J2EE and Portal.
Best Regards,
Assaf -
Error while exporting a par file from NWDSVersion: 7.0.19 to portal7.0
Hi,
When i tried to export a par file from NWDS to portal. I am getting the following error. Please can any one help me to trace out this error.
21.08.09 / 15:09] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.FileNotFoundException: http://sgcsapeps:50200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=XXXXX&j_password=YYYYYYt&j_authscheme=default&uidPasswordLogon=Log%20on
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:792)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Thanks in Advance.
Regards
BashaHi,
Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
Windows/ Prefereces / SAP Enterprise Portal
Check the following enteries
Alias
Host
Port
Login etc.
Regards, -
Error while uploading a PAR file
Hi All,
I'm having an error when i try to upload a PAR file from Portal>Java Development>Development
The strange is that i am having the error in QA environment, in development environment i can upload it without any problem, and also it is not the first time that I upload a PAR to QA.
I hope someone can help me, i really don't know what to do...
Regards,
Nicolás.-
Here is the error:
May 8, 2009 11:46:34 AM # Client_Thread_17 Fatal Application upload failed: InvoiceTool.par
com.sapportals.portal.prt.runtime.PortalException: archive: InvoiceTool.par
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:309)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:700)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:396)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:285)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:115)
at java.lang.reflect.Method.invoke(Native Method)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:250)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:351)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:628)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:555)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
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.(ZipFile.java:121)
at com.sapportals.portal.prt.deployment.ArchiveIntrospector.getDeploymentDescriptor(ArchiveIntrospector.java:54)
at com.sapportals.portal.prt.deployment.DeploymentManager.getDeploymentDescriptor(DeploymentManager.java:942)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:273)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:700)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:396)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:285)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:115)
at java.lang.reflect.Method.invoke(Native Method)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:250)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:351)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:628)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:555)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
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)Hi Nicolas,
In you development server,
1. Create a new iview (With new from PAR file option). The iView wizard gives you the option to choose the PAR file available on your development portal.
2. Now create a Transport Package. Navigate to System Administration - Transport - Export.
Navigate to your Transport Folder in PCD.
Now Create a new Transport Package and add the iView to the package (iView created earlier from PAR file).
3. Now go to Transport Package properties and Make sure, you are changing the property id prefix to * .
This will include every object associated with the iView while manually exporting.
4. Now click on the EXPORT button. This will export the required PAR file with. This in turn create an EPA file. save it to your desktop.
5. Now in Quality server,
Do the manual Import.
Navigate to System Administration - Transport - Import.
Browse the EPA file on your desktop and say IMPORT.
This way, you will be able to get your PAR file as well as your required portal object (here the iView) in quality server.
Hope this helps,
Cheers!!!!!
Biroj...
Points for useful answer will be appreciated.
Edited by: Biroj Patro on May 12, 2009 8:40 PM -
Getting error while uploading the PAR file into SAPEP
I have created one .PAR file in SAPEP6.0 SP2 and i deployed it is working fine but if i deploy the same PAR file into SAPEP6.0 SP13 it is generating error
Deployment failed - exception caught: Application upload failed: ConnectorService.par - more detail at: C:\usr\sap\E13\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\ConnectorService.par.log
and in log file it is generating as
Application upload failed: ConnectorService.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: ConnectorService.par
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException
Cannot assign a zero-length byte array to host variable 18.
at com.sapportals.portal.pcd.pl.PlFactory.handleUnexpectedSQLError(PlFactory.java:2490)
at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:652)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildOnPersistence(XfsContext.java:1360)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1118)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1076)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:846)
at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:185)
at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:188)
at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:244)
at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:133)
at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:500)
at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:425)
at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:426)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:446)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:460)
at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1317)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:501)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:663)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:668)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.updateObject(ApplicationRepositoryService.java:717)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeApplication(ApplicationRepositoryService.java:389)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:306)
... 34 more
Caused by: com.sap.sql.log.OpenSQLException: Cannot assign a zero-length byte array to host variable 18.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
at com.sap.sql.jdbc.common.dispatch.BlobHostVariable.setBinaryStream(BlobHostVariable.java:143)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:776)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setBinaryStream(PreparedStatementWrapper.java:401)
at com.sapportals.portal.pcd.pl.AttributeHeadersTable.storeAttribute(AttributeHeadersTable.java:431)
at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:248)
at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:541)
at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:616)
at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:640)Hi,
The problem might be caused by the version inconsistency of your J2EE and Portal Platform.
Please check the version of your J2EE and Portal.
Best Regards,
Assaf -
Problem while deploying new logon screen par file via NWDS
hi
i have a problem with deploying .par files out of the NWDS.
i want to change the look of the logon screen in our EP Portal (SAP NetWeaver 2004s).
when i just import the (working one) par file into NWDS and deploy it without ANY changes i get then an error when trying to call the portal:
instead of the logonscreen i get some IView error (like IView: N/A).
if i just copy the par file, and put it back to the pcd, everything works fine.
my problem seems to be the "compiling/deploying" via NWDS.
any suggestions?
i followed the guide:
http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
i followed also the BLOG:
Modifying The Logon Par(or customising the Logon Screen)
and the help:
http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
thanks for your help.
markusMarkus,
If you import the par file using NWDS, most likely you wouldn't import the associated jar files (I think 2 jars) that are originally part of the par file. So, when you make changes and update your custom jar, it would lack the two jars and your application would fail. Try downloading the par file using System Administration -> Support -> PCD Administration -> Browse Deployment..
Save the jar file on desktop and then import it to NWDS.
Hope this helps,
Kiran -
Error Importaing PAR file in NWDS
Hello All,
I am trying to import a PAR file in nwds. While doing so I am getting the follwing error:
C:\SAP\SAP\NewParProject\dist\PORTAL-INF\META-INF\CVS(Access is denied)
Reason:
Sorry an error occured creating the project.
The Plugin "com.sap.portal.plugins.config-archiver" caised an exception during the "Unpack" operation.
Can you guys help me in resolving this. This is not the first time I am getting this, but previously also when I downloaded some par from our SAP Portal, i got this error.
We are on SP 16 in nwds.
Thanks
AnirbanHello Jitender,
I think you are reffering to server log.
But as the problem is happening in NWDS in my local system, so I am attaching the NWDS log here.
[01.04.09 / 11:18] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.openPar.OpenParWizard > No Information
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:313)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.openPar.OpenParWizard.performFinish(OpenParWizard.java:232)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:96)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:286)
at com.sap.ide.eclipse.startup.Main.run(Main.java:795)
at com.sap.ide.eclipse.startup.Main.main(Main.java:602)
Caused by: java.lang.NullPointerException
at com.sap.portal.util.eclipse.FinishResult.addInformationsInTaskView(FinishResult.java:158)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.openPar.OpenParWizard$1.run(OpenParWizard.java:100)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
... 35 more -
Error 500 when trying to upload PAR file from NWDS
Since few weeks now, I'm not able to directly upload a par file from NWDS. I'm always getting a operation failed error. In the sap-plugin.log file I've found the following trace:
[21.04.09 / 17:51] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 500 for URL: http://myserver.com:50500/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=mylogin&j_password=mypwd&j_authscheme=default&uidpasswordlogon=log%20on
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1170)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at com.sap.portal.developmentTools.general.uploader.QuickPARUploader.run(QuickPARUploader.java:146)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)Developing for iphone can be amazingly complicated and frustrating. (even before you start coding). The process of having to create a Certificate, to approving the Certificate, to Assigning the deviceIDs to the certificate, to creating the AppIDs, to creating the provisioning profiles and then creating the .p12 file... is just too tedious.
I solved the problem of the "Entitlements are not valid". The AppID i had set in the iPhone Developer Portal did not match that of the AppID i had set in the Adobe Flash CS5 -> Publish Settings. (ie. com.yourdomainname.yourappname). After I re-entered my AppID and compile, i was able to sync the .ipa file into my ipad.
I wish the error message had been a little more descriptive. Could have saved me a whole day.
I hope this helps others. But my guess is, if you don't set the 40 character device ID correctly, or the email in the signingcertificate correctly, you'll get this same generic error message. -
Issue while uploading the PAR file thru system admin- AdministrationConsole
Hi All,
I have downloaded the PAR file "com.sap.portal.navigation.lightdetailednavigationtree.par.bak" from system admin->support->Portal Runtime ->browse deployment->Web-Inf->deployment->PCD.
after downloaded to the desktop for manual change in one of the JSP file rather than importing into NWDS. I have removed the bak from the file and added the .Zip to the file and i extracted the file.
here inside i got the three folders i.e WEB-INF,PORTAL-INF and file_list. now i went to jsp file called "LightDetailedNavigationTree.JSP" , changed one small property value in the code from false to true. after that i again zip the folders strcuture make the file name as original in the form of .PAR file. now i am trying to upload it in the portal thru system admin->portal runtime->administration console, but i am getting the deployment error as mentioned in the below.
even though with error, the wrong version of the par file with extension .err was saved in the PCD folder strcture, and original file also still exists. now i wanted to remove the wrong version of the file from PCD, what is the procedure to delete the wrong version, here in administration console i found one button clean , but i could not able to locate the wrong file version , only original right version showing up in the clean dropdown??
Can u tell me what is the procedure to edit the PAR file manually after downloaded to the desktop, rather than going edit thru NWDS??
if we need to upload the PAR file after changes, do we need to delete the original PAR file before we upload the new version of the same PAR or it will be automatically overwrite the original file with the same name??
Still i am getting confusion, please let me know how to edit the PAR file manally and how to upload the PAR file with out any isse while uploading it in the portal thru system admin->administration console??
Any pointers in this regard would be the great help to me??
Error as i got while uploading the par file after the changes manually. (com.sap.portal.navigation.lightdetailednavigationtree.par)
2011-01-24_07-40-18
Application upload failed: com.sap.portal.navigation.lightdetailednavigationtree.par
java.util.zip.ZipException: Error opening zip file /usr/sap/BIS/DVEBMGS13/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.sap.portal.navigation.lightdetailednavigationtree.par
* at java.util.zip.ZipFile.open(Native Method)*
* at java.util.zip.ZipFile.<init>(ZipFile.java:140)*
* at java.util.zip.ZipFile.<init>(ZipFile.java:155)*
* at com.sapportals.portal.prt.deployment.ArchiveIterator.iterate(ArchiveIterator.java:39)*
* at com.sapportals.portal.prt.deployment.UploadProcess.upload(UploadProcess.java:60)*
* at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:835)*
* at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)*
* at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)*
* at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)*
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
* at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)*
* at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)*
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)*
* at java.lang.reflect.Method.invoke(Method.java:391)*
* at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:706)*
* at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)*
* at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:249)*
* at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)*
* at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)*
* at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)*
* at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)*
* at java.security.AccessController.doPrivileged(AccessController.java:246)*
* at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)*
* at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)*
* at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)*
* at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)*
* at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)*
* at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)*
* at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)*
* at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)*
* at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)*
* at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)*
* at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)*
* at java.security.AccessController.doPrivileged(AccessController.java:219)*
* at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)*
* at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)*
Can you please what are the steps if any specific while editing the PAR file manually and uploading it with out any issues??
Thanks in advance.
Regards,
PortalUser
Edited by: PortalUser100 on Jan 24, 2011 6:01 PM
Edited by: PortalUser100 on Jan 24, 2011 6:04 PM
Edited by: PortalUser100 on Jan 24, 2011 6:05 PMHi Shusil,
Thanks for your reply.
I have one more dought here.
the PAR file of lightdetailnavigation has been modified thru NWDS and deployed the PAR file by adding the required JARS.
Now my question is, the application server which i am used as local portal server installed in my desktop.
now this depoyed latest par file i have picked it from the workspace in the local desktop, and i am planning to upload the same PAR file in of the sandbox portal system of client , will it update successfully in the new portal apart from the deployed portal??
i am here used the path system admin->support->portal runtime -> administrate console ( this in the sand box system to upload the par file which was deployed in the local portal server in my desktop.
Thanks,
Portal user -
Hi Experts,
Some questions that I hope someone can verify:
1. When we download a PAR file from Portal and import into NWDS, do references to JAR files not get imported? (for e.g. I see the Portal Logon component require adding of certain jar files)
2. What are the differences between the PAR files in the following path (downloaded via System admin>support>Portal Runtime>Browse ):
-ROOT/WEB-INF/deployment/temp
-ROOT/WEB-INF/portal/portalapps
Thanks,
ZMHi,
Whenever a PAR file is imported into the NWDS the JAR files will not be imported automatically.You need to copy it in the right location manually.
Regarding the second question , ROOT/WEB-INF/deployment/temp will have the complete PAR file (also I compared the size of logon PAR file)
-ROOT/WEB-INF/deployment/temp --356234
-ROOT/WEB-INF/portal/portalapps--4096
I guess the different path are for different necessity of the same portal application. While temp folder has the PAR file of the portal application, the portalapps might contain files and reference to launch the Portal application.
When you download from the portalapps folder you will not get the PAR file.
Any information on the second question are welcome..
Regards
Karthiheyan M -
Error occuring during importing .par file
Hi all,
I m trying to customise the logon screen for my project. For this I have downloaded the "com.sap.portal.runtime.logon.par.bak" from System administration>Support->Portal Runtime->Browse Deployement. I have locally saved this file on C:\temporary. I have renamed the file as .par and removed the .bak extension. Now I have tried to import the file onto NWDS in EP perspective by following File>Import-->Par file. But its giving me this error:
error in opening zip file
Reason: Sorry, an error occured creating the new project.
The plugin "com.sap.portal.plugins.config-archiver caused an exception during the
"Unpack" Operation See log for more details.
However, in my package explorer in NWDS I can see a project created and with the structure. But in Portal-INF I cant see seven jsp files and four text files which comprises of basic functionality of the Logon Page.
Can anyone suggest me a solution to this?
Regards,
Priyanka.Hi,
After renaming com.sap.portal.runtime.logon.par.bak to com.sap.portal.runtime.logon.par. Try opening the file with winrar/winzip to see if you have a right par file structure. On some portal versions, when you open com.sap.portal.runtime.logon.par file, you have again a com.sap.portal.runtime.logon.par file inside it.
So if you find com.sap.portal.runtime.logon.par file inside com.sap.portal.runtime.logon.par. Then just extract it again and try importing it into NWDS.
Greetings,
Praveen Gudapati
[Points are always welcome for helpful answers]
Maybe you are looking for
-
Lost my iphone 5 and want your help to get it. Have my apple id for 2 devices
Lost my iphone 5 and need your help please since i downloaded find my iphone and can only locate my ipad
-
My printer keeps printing things on only 1/4 of the page
I can not figure out how to print something correctly I guess. It keeps printing things only taking up 1/4 of the page..and it's driving me nuts! I can't figure out how to fix it. Help please?! =)
-
What technical scenario need for an Plan Driven?
Hello experts. First of all; thanks four yours help and sorry for my english... I want implant an Plan Driven with SRM 5.0 and ECC 6.0. My dude is the follow: what is the best technical scenario ? Classic or Classic extended ? I explain a little: 1.-
-
ODI Procedure to read a directory/folder in interface during package.
Hello, A have a ODI package including 1 procedure and 1 interface I will like get the filename in interface (datastore source) with procedure. Its possible? Thanks!
-
I was told by Adobe there wasn't any help for "free" (Flash Player) products. Explaining that my company was a paid user of other Adobe products i.e. Dreamweaver, got me transferred to Tech Support who claimed there weren't any known Flash crash issu