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
Similar Messages
-
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
RayHi 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 -
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? -
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örgHi 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 -
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 PMHi,
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 -
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;-
<b>PAR Upload failed:Please make sure that portal server is running.
HTTPS is not supported ,please ensure the server is not using HTTPS</b>
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 GiriaHello 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 -
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 KlothHi Nils,
I think you must have selected the defualt checkbox (Try and uncheck that). Also uncheck the checkbox for "<i>Yes, I want to remeber the password for deployment</i>" 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:
<i>http://khz059:52900/irj/servlet/prt/portal/</i>
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. -
Problem during uploading of .par file in Portal
Hi,
I am downloading a properly working .par file from portal in my local system. But whenever I am uploading the same par file back into the portal through NWDS, the .par file is not running properly and its Giving error.
Here is the error:
"Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.tmobile.compSumm.CompSumm of Portal Component com.tmobile.CompSumm.CompSumm because: Could not find implementation class "
Any Idea what is the problem?????Hi,
I have unzipped the .jar file from the .par file. Then I imported the .par file into NWDS. After that I have added the extacted .jar file as external jar into the project(Proerties->Java Build Path->Libraries->Add External Jars). After that I had uploaded the project into the portal.
But still its showing the same error:
"Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.ibm.test of Portal Component testing.test because: Could not find implementation class"
Any solution.....
Message was edited by: Debasish Sarkar -
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
ThanksHi 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, -
Accessing PAR files though Portal
Hi All,
I want to access the PAR file through Portal itself. So I go to the foll path
System Administration --> Support --> Portal Runtime --> Browse Deployment --> portalapps.
I am able to find the com.sap.portal.navigation.masthead
But when I try to download this file then it is trying to download com.sap.portal.support.browse.zip and not com.sap.portal.navigation.masthead
My intention is to download the PAR file from Portal itself, do some customizations and then upload the same through Portal. I don't want to use NWDS for this purpose.
Please help
Regards
Nikhil BansalHi everybody,
just some additional remarks:
- download the PAR from /WEB-INF/deployment/temp as described by Daniel in the thread referred
- if you download it by using the "View" button, Praveen is right, you have just to rename the file; if you download it by using the "Download" button, the PAR is inside the ZIP
- if importing the PAR as a project into NWDS, be aware to add the JARs manually into the /lib and the /private/lib directories, respectively; NWDS does not import the JARs automatically, and if you don't import them, deploying the PAR on the portal will lead to massive problem as then the JARs are missing...
Hope it helps
Detlev -
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,
MMHi 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 -
How to deploy.sca file in portal?
Hi
I am new to portal..can any one explain step by step process to deploy .SCA File into portal using SDM.
Thanks
RahulRahul,
Refer to this article.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e0df0afb-44fb-2b10-46b1-c026264bcbc4
Hope this helps.
Cheers!
Sandeep Tudumu -
Download PAR file from portal or Service marketplace
Hi,
Can you tell me that how we can download the par file from portal 7.3 or from marketplace.
give me the path also.
Regards,
ShashankHi
Please check the process :
http://scn.sap.com/community/netweaver-portal/blog/2012/05/10/customizing-logon-page-on-portal-73 -
Portal Run time error after deploying custom logon page par file in portal
Hi Experts,
We have customized the standard portal logon par file for client XYZ and imported it with the same name (com.sap.portal.runtime.logon.par) in portal.
It is working fine for XYZ . And another client ABC wants the same customization for them also. So we took the par file from XYZ and imported it in ABC system. But in ABC system, we are getting Portal Run time Error. When we checked the logs, it is showing error in LogonBean class.Wwe have included the necesary jar files. Could anyone help us in identifying what is missing?
Thanks
VJHello Vijay,
Please paste or attach the error log.
Regards,
Haseena -
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,
NileshDear 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.
Maybe you are looking for
-
Importing HD footage to Final Cut Express?
I am going to edit my own wedding video and I am hiring a professional to shoot the raw footage in HD. I have a small, hand held Panasonic PV-GS300 that shoots in SD on Mini DV tapes. I understand that I cannot effectively upload HD footage through t
-
PDF file prints fine from Acrobat reader XI, but not Acrobat Standard XI
I have a 2 page document that is set up as tabloid 11x17, meant to be printed duplexed and folded as a 4 pamphlet. The document with the same printer settings prints fine from Adobe Reader XI but from Adobe Standard XI, Page 1 prints fine, but page
-
How to show budget cost in the PPR screen?
Hi all, I define budget cost of project already but in PPR screen It cannot show this value. It show only actual cost. Please advice me to show this value. Thank you.
-
Can't access values in 'this' structure
-thanksok, this is really strange.... hers's my application.cfc <cfcomponent> <cfscript> this.name = "wg234rf6u"; this.applicationTimeout = createTimeSpan(0,2,0,0); this.clientmanagement= "yes"; this.loginstorage =
-
How to send fax thru sap system
Hi all, I need to send a fax thru sap system. In the given parameter I need to give email address & fax number. The result is the content I shud receive as both email & fax. As far as email is concerned no problem. But I am not receiving the content