on 01-24-2011 5:01 PM
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,
Editing PAR file manually will always run into some issue, so it is not recommended to edit it locally.
Always use NWDS to deploy the PAR file by adding all required JAR files.
If you are deploying the PAR file with the same name then it will automatically get overwritten, you dont have to delete the old version manually.
Manual edit is Not recommended.
Hope this helps!!!
Thanks.
Sushil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
Hi,
If you want to upload the modified par file on to the server (any), you just need to give the server details and your login credentials in NWDS to do so.
When you are done with all the changes in par file, Right click on the project and select export and then select the PAR file.
Check on both the check-boxes and enter your target server details. This will fulfill your requirement. And will be available for iView creation as well.
Regards,
Nishant Singh
There is always a scope for error if you are trying to modify the par files manually. Make sure you package your files in the correct format after your changes are done.
For standard par files, it is always recommended to take a backup of the par file before making changes. Also, when you deploy them back on to the portal - use a custom name instead of the original name.
I am not sure why would you not want to use NWDS ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.