No par file in PCD

Hi,
I'm facing a peculiar condition here. I recentally reinstalled my EP 7.0 server. Now there is no PAR file in
'C:\usr\sap\J2E\JC01\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd'
directory. However, 'temp' directory has all the PAR files in it.
'C:\usr\sap\J2E\JC01\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp'
Is this a known issue - or an issue after all because my portal is running fine - though I'm having problems in changing logon image files.
If this is an issue - what is the remedy for this.
Thanks in advance.
Vishwas.

It is not issue. That's quite all right.

Similar Messages

Question about par file...

Hi,
There are two followin par file in pcd root directory
I don't know their uses...so give me answer for which purpose they use/
1> com.sap.portal.runtime.flash.flashanywhere
2> com.sap.portal.runtime.flash
Thanks in advace

Hi Nisarg
There doesn't seem to be a documentation for those files anywhere. Nevertheless, you could still figure out what those two files do by importing them into your NWDS.
You should find the files at this location on the server.
<J2EE_Engine_Instance>\j2ee\cluster\server<X>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
Import them into your NWDS and see what function they perform
Hope that helped
Best Regards
Priya

The PCD folder with all par files in the portal is empty

Hi all gurus.
I have a customer that failed with a transport of iviews between two portals, the par file was not included even if attribute "include dependent objects" was checked.
I have met this problem before and the only(?) solution is to download the par file separately and import it into the receiving portal and then create a new iview from it.
Here is my problem: when I at this certain customers portal go to "System Administration > Support > Support Desk > Portal Runtime > Test and Configuration Tools > Browse Deployment" and then browse to "Root > WEB-INF > deployment > pcd" that last folder is empty! Blank!!!
On all portals I've seen that folder alwasys shows all standard par files along with deployed stuff but here the folder just shows a white page with the text "The folder is empty".
I don't think it's a matter of authority since I have added "super-admin role" and all possible content admin roles to my user without any change, the folder is still empty.
Does anyone have an idear about what is going on here?
Best regards
Benny Lange

Hi Raghu.
Your are missing my point: it's not about what content to export, it's about the folder being totally empty. I can't see the par files belonging to our deployed code either.
Of course I could upload the par file from Eclipse workbench from where I first uploaded the par file to the development enivironment, but I find it alarming that the folder is empty when it's full of par files in every single portal I have seen so far.
Best regards
Benny

Migrated PAR file does not appear in PCD

Hi,
I have migrated a par file, using the migration tool, and deployed the ear file successfully using NWDS.
I can see the deployed application in NWA but not in PCD, under 'Portal Application'.
I am missing something?

Hi Jack,
I assume you are using EP 7.3x and that you have inside the par a portal application. is that correct?
Search for it in content Administration-->Portal Applications:
If you still cannot find it there, make sure that in the portal application PortalApp.xml file you do not have the line:
<property name="com.sap.portal.pcm.admin.isTechnical" value="true"
This hides it from the administration.
Best Regards,
Tal

Why is the PAR file located in portalapps, pcd and temp folders???

Hi all - I downloaded the com.sap.portal.runtime.logon.par.bak file to make changes to the logon page. I renamed the PAR file after it was downloaded, made my changes, and exported back into the portal. Everything is fine....I just have a question in terms of what the difference is between what appears to be 3 locations where this file is located. First, it appears that the file I exported is now located at:
ROOT/WEB-INF/portal/portalapps (timestamp 10:25:22 AM)
However, there are backup versions (.bak) located in the following locations;
ROOT/WEB-INF/deployment/pcd (timestamp 10:24:46 AM)
ROOT/WEB-INF/deployment/temp (timestamp 10:25:06 AM)
It appears as though the file is loaded into pcd, then to temp, and then to portalapps? What exactly is it doing, and why are there 2 backup files?
Regards,
Steve

I understand the problem. Here are some ideas:
1) Permission repair only affects files in the system, userfiles are ignored.
2) For large file transfer, you must be hardwired. Wi-Fi is insufficient for transferring large files.
3) When copying Mac files to a Windows filesystem, illegal characters in a filename will cause the operation to stop without any informational error message. In any case, copying large files to a Windows machine is not very reliable. I recommend Mac-formatted network storage.
4) When attempting to mount a nonexistent network disk, Finder stalls with a 5 minute timeout. The solution is to add a "Quit Finder" menu item to the Finder icon in the Dock.
5) If the machine uses a dynamic localnet address, Finder is unable to locate an aliased network disk that has changed. You need to mount the disk with the "Connect to Server" dialog first to fix the aliase(s). A DNS setup may help to locate machines by hostname rather than IP address.
6) Switches are problematic. If you are using switches rather than routers you may be seeing congestion on machines connected to the switch.
7) I highly recommend rsync triggered by a cronjob running in the wee hours of the morning. rsync is robust and persistent in file copying.

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 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

Deploy par file error using NWDS

Hi
I developed a portal service for activity report. After i deploy the service i get an Java Iview Runtime error in portal and our portal is down. I found the error which is a null reference in portal service i wrote.I fixed the problem, but i can't deploy par file using neither NWDS. Is there any other ways to deploy the par file. Please help.
Thanks
Edited by: Ozkan Onay on Jan 31, 2008 8:11 PM
Edited by: Ozkan Onay on Jan 31, 2008 8:16 PM

Hi,
To deploy the application, you can without NWDS but not without server running. Server should be up for deploying any application. Go to Drive:\usr\sap\J2E\JCXX\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
and ..\deployment\temp folders. Delete your project. It will be cleaned from the portal. Now restart the server. It will be up.
Regards,
Harini S

Not able to get the standard par files

Hi,
I downloaded the standard par file from ROOT/WEB-INF/deployment/pcd (download this folder). My problem is I am not able to extract the par.bak file from the downloaded zip file. But I able to exract the par.bak file for custom created portal componet's par file.
What would me the problem?
Kindly help me out.
Ram

Hi,
Rename the par.bak file to par and then try to import it into NWDS. This will create a project in NWDS and you can start playing around with the project files. When you import par file no jar files are imported into NWDS, so you should do it manually.
Check this how to import par file into NWDS:
importing a .par file
Regards,
Praveen Gudapati

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 PM

Hi 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

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

Error while uploading par file

Hi,
I am trying to upload par file for the first time. When I try to deploy the par file, I am getting message saying, 'Operation failed: Please make surethe server 'Myportal' (host:port) is running or check the log( sap-plugin.log) for more details'/
I have tried to open the portal http://host:port/irj/portal. I am able to open the portal and can login successfully also. This means that the portal is running ( Am I right ?).
I have tried to upload the par file directly from the portal using
system admin>support>portal runtime>Administration console--Archive uploader.
I got the error messages as given below.
INFO: Detected Portal Archive File: HelloProject.par
INFO: Deployment failed - exception caught: Application upload failed: HelloProject.par - more detail at: E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\HelloProject.par.log
Please guide me about what could be the pbm and how to solve this.
Thanks in advance.
Regards,
Vishnu Priya

Hi Vishnu,
Are you trying to upload a PAR file from the NWDS?
if then you need to configure the J2EE engine correctly before doing so
for that matter you need the port number and also have that the SDM password for deployement
Once these are ready ...go to the J2EE engine tab available on the bottom corner.And make sure the J2EE engine is working. or the server is up.Is this what you are looking for.....if yes.....just reply...I can continue with the deployment..
Regards
Arun

Sap-plugin error when deploying a par file

Hi,
We are getting sap-plugin error when ever we are trying to deploy the application to the portal.Even after restarting the server the problem is not getting solved.
The application we are trying to deploy is perfectly alright as we tested the same earlier.
Can any one provide some inputs to solve this issue.
To add some more points
In brief ,we are not able to deploy our Portal applications . It is giving us error like this
NFO: Detected Portal Archive File: com.abc.par
INFO: Deployment failed - exception caught: Application upload failed: com.abc.par - more detail at: /usr/sap/POD/JC30/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.abc.par.log
We got this error many times , but after some time , when we restart the portal it works,
this time it is not working even after I restarted the server many times

hi all, i have same problem with upload of .par file, it doesn't work both from the portal and from the NWDS,
here i post first part of log file:
this is sap-plugin.log :
[16.05.07 / 13:05] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > Upload Response: <?xml version="1.0" encoding="utf-8"?>
<query-result><info><type>1</type><message>Detected Portal Archive File: test.par</message></info><info><type>1</type><message>Deployment failed - exception caught: Application upload failed: test.par - more detail at: C:\usr\sap\SWB\DVEBMGS02\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\test.par.log</message></info></query-result>
this is test.par.log :
2007-05-16_12-03-10
Application upload failed: test.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: test.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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
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)
 ... 54 more

Error on exporting a PAR file to portal

I am trying to export a portal application (java code) to PAR file in the NWDS. i am getting the following error;-
PAR Upload failed:Please make sure that portal server is running.
HTTPS is not supported ,please ensure the server is not using HTTPS
The PAR file is to be uploaded to the portal later.
Note:The portal application has compiled successfully.
Is it not supported in this version of the portal?
Please help
Regards
Navneet
Message was edited by:
Navneet Giria

Hello Navneet,
Check these threads:
Problems deploying par file via Netweaver Developer Studio
Unable to Upload portal application from NWDS
If this does not help, try deploying from
System Administration-> Support-> Portal Runtime-> Administration Console.
At the option "Please specify a Portal Archive file (PAR) and press "upload" to store it into the PCD." Deploy your par file by giving the path.
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers

Error uploading a PAR file

Hello,
an upload of a new PARFile ends with the foll. error.
Anybody seen before?
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 java.io.ByteArrayInputStream object of length 0 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.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:838)
     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)
     ... 54 more

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

No par file in PCD

Similar Messages

Maybe you are looking for