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

Similar Messages

Error deploying PAR file from Developer Studio (NW04)

Hello,
i've got a problem while trying to deploy a PAR file from NW Developer Studio.
The PAR Export function says
"Unable to connect to the Portal",
the portal itself gives the following response:
"ERROR: Upload failed - exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Invalid content type submitted - no multipart data"
Deploying the PAR file manually using the Administration Console (system administration tab) of the portal works fine, but why doesn't the PAR Export function of NWDS?
Thanks in advance for any help!
Regards,
Jörg

Hi Jörg,
as a general advise, use the NWDS version corresponding to the Servers version, so in this case, upgrade (or better: install new) NWDS 2.0.14. The main reason is WebDynpro compatibility, but the deploy mechanism may need this too.
At least, give it a try and report if you have success (or not).
Hope it helps
Detlev

Problems deploying par file via Netweaver Developer Studio

Hello,
I have problems deploying a par file using the SAP Netweaver Developer Studio.
In the SNWDS i configure the following:
Window -> Preferences -> SAP Enterprise Portal
Alias: IEP
Host: khz059
Port: 52900
Login: Administrator
Description: Testportal
The logon Url of the portal is http://khz059:5290052900/irj/portal
If i try to upload a par file via "Quick PAR Upload" i get the error messages:
"Unable to connect to the portal
Operation failed: Please make sure the server 'IEP' (khz059:52900) is running or check the log (sap-plugin.log) for more detail."
Am I using the proper settings? Am I using the wrong port?
I don't know whats wrong.
Can anyone help me?
The logfile shows:
[12.09.05 / 14:53] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Error writing to server
 at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:302)
 at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:314)
 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:634)
 at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
 at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
 at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
 at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
 at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
 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:519)
 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: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)
Best regards,
Nils Kloth

Hi Nils,
I think you must have selected the defualt checkbox (Try and uncheck that). Also uncheck the checkbox for "Yes, I want to remeber the password for deployment" if it is also selected. When you deploy the par file now enter the password and try to deploy. I think this will solve your problem.
Apart from this, try this methos of deploying the Par file.
1) Save you project. Right click it and "Quick par Upload".
2) On your browser type
"http://<your_server_name>:50000/irj/servlet/prt/portal/"
Your case:
http://khz059:52900/irj/servlet/prt/portal/
or same page you can get by navigating:
System Administration-> Support-> Portal Runtime-> Administration Console.
3) 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.
Now you file is deployed on the server. If you want to create an Iview from this deployed .par file then :
1) On your portal. Follow the path: Content Administrator-> Portal Content -> Portal Content(sub-option). Right click -> New from par ->iView.
2) Here in the list you will find the par file which you have uploaded. Proceed as said.
3) You will finally have an iView. Right click it and preview it.
I hope this solves your problem.
Regards
Pravesh
PS: Please consider rewarding points if helpful.

Deployed par file does not show as an iview create option

Hello Experts,
I modified the com.sap.portal.runtime.masthead par app and deployed it to the portal as myCustomMasthead.
I see the par file in under the Support Workset in the portal, but when I'm in content admin and try to create an iview from the deployed par file template, the option for the deployed par does not show? Do I need to request basis to bounce the J2ee engine? What might be wrong?
Any advice will be appreciated.
Regards,
MM

Hi Nishant,
Yes the file exists under ROOT/WEB-INF/portal/portalapps.
And I am not using iview from template option, I am using iview from par file option.
I did not deploy the par file from NWDS, I created the par file in NWDS and then manually deployed the par file using the par uploader tool in the portal.
Do I need to do anything in the portalapp.xml file? This is what my portalapp.xml file looks like:
<application>
<application-config>
 <property name="ClassLoadingPolicy" value="5.0"/>
 <property name="DeploymentPolicy" value="5.0"/>
 <property name="AuthenticationPolicy" value="5.0"/>
</application-config>
<components/>
<services/>
</application>
Then there is also another portalapp.xml in the dist folder that has all this SAP stuff inside it. The top line says not to modify the file.
I bounced the J2EE Engine but it didnt fix the issue.
MM

Par file Error

Hi
While I am trying to export par file from NWDS I am getting below error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com.sapportals.portal.navigation.HeaderiView.
Exception id: 01:10_14/11/06_0091_13329050
See the details for the exception ID in the log file
Thanks in Advance
Dev

hi devara,
when you import standerd par files in the NWDS, some files dont get included in your project. you have to manually include these files in the project.
you will get the "com.sap.portal.navigation.masthead_core.jar" file in the
portal inf-->private->lib--com.sap.portal.navigation.masthead_core.jar
in your original par file.
just copy this file and paste in your project .

Different ways to deploye .par file

Hi,
How many ways we have to deploy .par file. As per my knowledge folloing are the ways
1. Deploying from NWDS
2. Portal -> Java Developer -> Portal Deployment
Is there any other way to deploy the par file like we can deploy .ear files from SDM.
We would like to remove PDK. So, the Java Developer role will be deleted.
Please let me know if we have any other ways to deploy
Thanks

Hi Bobby,
This is another way for PAR deploy
System Administration -- Support -- Portal Runtime -- Administration Console
Apart from that you check these links out :
Converting .EAR file to .SDA
Also for intro..,
http://help.sap.com/saphelp_nw04/helpdata/en/2d/b8b2426dbec86ae10000000a155106/frameset.htm
SAP Note: 696084 (For Multiple PAR deployment)
Regards,

NWDS - Error deploying .par file to portal (EP 7)

I am unable to deploy a par file to our portal (EP7 SP12) using NWDS (7.0.06).
I can use the Administration Console to upload par files, but when using the deployment option in NWDS it gives me the following error message:
Operation failed: Please make sure the server 'ALIAS' (SERVER:PORT) is running or check the log (sap-plugin.log) for more detail.
My user id has the "super_admin_role", the "ContentManager" role, and the "Administrator" role assigned.
The log file shows that the upload is getting an HTML 401 error (Unauthorized), but if I paste the link below into my web browser, it takes me to the file upload page.
sap-plugin.log
[04.02.08 / 15:13] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 401 for URL: http://SERVER:PORT/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=***********&j_password=********&j_authscheme=default&uidPasswordLogon=Log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
     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:519)
     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)

Dhruv...
Thanks for your response. I checked the settings for the Server Message Port. I have the default values enabled. "SAP J2EE engine is installed on remote host" is selected with "Message Server Host" set to "localhost" and the "Message Server Port" set to 3601.
When I change the Message Server Port to 3901, I get an additional error regarding HTTPS protocal not being supported. When I change the proxy settings, I still get the same error message that I was receiving before.
I have verified that my account is not locked, and I have already re-installed NWDS twice, which did not fix the problem.
Thanks...
Bill

Error while deploying .par file through system admin

I have tried to modify logon.par file but when I was try deploy that file again through system admin then I got this error...................
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com.sapportals.portal.ume.component.logon.SAPMLogonComponent.
Exception id: 10:19_11/05/07_0006_13454550
See the details for the exception ID in the log file
Please help me out I am using sneak preview 7.0
Detailed Error Log & Trace
=========================================================
Exception ID:08:55_11/05/07_0002_13454550
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.support.browse.default
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     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.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonComponent of Portal Component com.sap.portal.support.browse.default because: Could not find implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:242)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 26 more
Caused by: java.lang.ClassNotFoundException: com.sapportals.portal.ume.component.logon.SAPMLogonComponent
Found in negative cache
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@3389d1]
Parent loader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@1b7a6fa]
References:
   not registered!
No resources !
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 30 more

Hi,
      Open ur PAR file then double click on PORTAL-INF -> lib->Select 2 jar files
         1.com.sap.portal.runtime.logon_api.jar
         2.umelogonbase.jar
Copy those jar file & paste in to lib in ur application.
Regards,
Senthil kumar K.

Error while deploying PAR files for JSPDynPage & HTMLB

Hi,
I am facing following error while exporting the PAR file.
PAR upload failed:
*Please make sure the server ***** is running. HTTPS protocol is not supported, please ensure this server is not using HTTPS.*
I checked with the server. It is running fine.
Please help..
Regards,
Niraj

hi niraj,
Login into portal System Administration->support->portal runtime->Browse Deployment
select web-inf (Browse)-deployment(Browse) check you par file...
Other way around...
go to portal content -> create iveiw ->using Par (not using template)->select ur par file....and done..
Regards
parth

Sharepoint 2010 question : Error while deploying wsp file in using managment shell (power script)

When I tried to deploy the wsp's using managment shell (power shell scripts) everything looks good.
When I go and take a look the "manage farm solutions" thru sharepoint central admin, I see the deployment failed in two servers.
Error is
Could not load file or assembly 'c:\windows\Temp\solution-cxxxxxxxxxxxxxx\xxx.xxx.dll" or one of its dependencies. Access is denied.
Can you please let me know what could be the reason.
Note : I have two app servers and two web servers setup. The deployment is sucessful in 2 apps servers . but 2 web servers are giving error.
Thanks
Pichaimani

Hi,
According to your post, my understanding is that you wanted to failed to deploy the wsp's using managment shell.
You need to make sure that the dll is registered in the GAC.
Go to %Windows%\assembly. If the dll isn't there , you need to install it to the GAC on the server. Simply drag it into that folder in Windows Explorer, and it should install itself.
Here is a similar thread for your reference:
http://stackoverflow.com/questions/1265505/sharepoint-could-not-load-file-or-assembly-the-system-cannot-find-the-file-sp
Best Regards,
Linda Li
Linda Li
TechNet Community Support

PAR Upload Error from NWDS

I'm unable to export a PAR file from NWDS to the Portal. I go into the com.sap.ep.connectionManager log and find the error captured there with the URL address that NWDS was attempting to connect to and drop it in a browser. This results in the following error message:
ERROR: Upload failed - exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Invalid content type submitted - no multipart data
Has anyone encountered this and has a solution?
Thanks in advance!

Thanks for the response, Yoav.
There is not a problem with uploading the par file. I can enter Java Development-Tools-PRT Admin Console and use the Archive Uploader to store the par file in the PCD.
This appears to be a problem with NWDS communicating with the portal and the way the file is presented for upload. I am using NWDS SP11 with EP 6 SP11 and PDK 6 SP9.
Thanks again,
Steve

Deploy par files with code from NWDI

Hello Experts,
I have migrated some par files to NWDI and they are deployed via SDM as SDA files.
From eclipse it is possible to deploy the par files with Code. Is this possible from NWDI that the par files are deployed with code to the portal server.
Regards
Sundeep

Hi Satish,
I am using NWDS, and then check in the Portal DC which is then deployed on the runtime system.
My question is during deployment via NWDI is it possible that the par is deployed with code.
Earlier we were using eclipse for par based development, and this was possible in eclips.
With NWDI i dont think it is possible to control if the par should be deployed on the portal server with code included.
Regards
Sundeep

Runtime exeception after deploying PAR file in portal

Hi ,
I am facing an issue during the deployment of PAR file in our Quality portal. I have download the PAR file from the system-->import to the NWDS--> did the modification (only to the properties files as part of my requirement) -->Export as PAR file. I then undeploy the previous earlier PAR file and then upload the modified PAR file in portal. When i test the application , i received portal runtime error.
I have also tried by downloading the PAR file for the same application from the production portal and tried importing to Quality system without making any modification to the PAR. I still face the same issue.
Due to this issue, i am not able to bring the application back as its not getting deployed properly. Can anyone help me on this.
Regards
Ray

Hi Ray,
Are you sure your file is getting deployed properly. Can you verify if the time stamp of the PAR file is getting updated on each deployment or after you upload it through Portal.
Also, please check the PAR file (size and it's contents by unzipping the PAR file) that you've downloaded from PROD and deploying on QAS to ensure that the file is not corrupted by any means during downloading.
You can also ask your BASIS team to provide the PAR file directly from PROD server and try to upload it on QAS instead of you downloading it from PROD portal.
Also, you can follow the below steps to download the PAR file yourself from PROD portal with Administrator ID:
Browse to the following location : System administration->Support->Portal Runtime->Browse deployment->ROOT/WEB-INF/deployment/temp
1. Find and Identify the PAR file and Copy the name of PAR file.
2. Click on view instead of download link to save the PAR file. Keep the name of PAR file same while saving with .par extension.
3. Deploy this file on QAS Portal.
Please let us know the results.
BR,
Anurag

Unable to Deploy Par File in the Portal

Hi Experts,
When i'm trying to deploy the par file to the portal after Configuring the server settings it's giving me an error.
"Operation Failed: Please make sure the server 'DEV' (hostname:port) is running or check the log (sap-plugin.log) for more detail "
And please guide me where i can find the log file sap-pluginng to check the logs as i'm new to the NWDS i'm not able to locate the file.
Regards,
Nilesh

Dear Nilesh,
Check that you have set the followings configurations:
- Windows -> Preferences -> SAP J2EE Engine:
Message Server host: Portal Server
Message Server port: ms of portal 390x (not 50x00) you cand find your message server port in http://server:port/index.html -> System Information (Message server table)
- Windows -> Preferencies -> Sap Enterprise Portal (there you need to put the 50x00 port).
Try with this a comment, regards.

Deploye par file into portal

When I tried to deploye the par file into portal using file->Export->PAR file, I am getting an error says "unfortunately the upload of your PAR was not sucessfule. ....
Error message: Upload seems to have faild" ... Because of this I am not able to upload the PAR file to portal. Any Idea? Please help
Pages: 1 Back to Thread List
Threads: [ Previous | Next ]

I tryied to do it manaulay and able to upload it. but when I run it, I am getting some error says
An exception occurred while processing a request for :
iView : com.flightsafety.hr.EmployeeAddressChange.EmployeeAddressChangenew
Component Name : com.flightsafety.hr.EmployeeAddressChange.EmployeeAddressChangenew
Internal error: empty page context.
Exception id: 10:14_10/01/07_0214_6394050
See the details for the exception ID in the log file
Have any Idea?

Deploy par file error using NWDS

Similar Messages

Maybe you are looking for