Deploy PAR with NWDS SP19

Hi All,
I am trying to deploy the PAR file from NWDS, it brings up the dialog and after i enter my password, the deployment progress is stuck, let us say at 80% and my NWDS is hung. I have to terminate it and reopen it again. I upgraded my NWDS recently from SP15 TO SP19. also my portal is on SP19. is this a bug with NWDS Patch.
Also, Just now I found that I am not able to deploy PAR files from the System Administration > Support> Portal Runtime --> Administration Console on Ep 6.0 SP19.
Did any of you guys encounter the same problems?
Any Help is appreciated.
Thanks
Message was edited by:
Reddy

Hi Reddy,
It sounds like some of the pluggins may be corrupted, have you tried reinstalling the NWDS?
Krishna Reddy

Similar Messages

How to deploy par without NWDS wizard

Hello All,
How can we deploy PAR files without NWDS wizard.
We have developed a functionality packaged in PAR, how we can deploy it on Client Side Portal, do there some way to deploy it without NWDS.
Thanks and regards
Santosh

Hi Santosh,
Yes you can deploy the par file without using the NWDS.
Please refer to the post:
<b>Re: Problems deploying par file via Netweaver Developer Studio>
Here I have mentioned the way to deploy the par file without using NWDS.
I hope this will definately help you.
Regards
Pravesh
PS: Please consider rewarding points if helpful.

Cannot deploy par from NWDS

Hi,
I am not able to deploy par file into the DEV EP instance. Since the sys # is 00, I am using 50018 as the port number and very sure that the host name is ok. the error message in sap-plugin.log suggests that the upload response is the default login page. I have attached the stacktrace from plugin.log.
[05.12.05 / 15:45] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Factory initialized !
[05.12.05 / 16:03] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Startup in progress
[05.12.05 / 16:03] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Factory initialized !
[05.12.05 / 16:31] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > Upload Error message: Upload seems to have failed
[05.12.05 / 16:31] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > Upload Response: <html><head><LINK REL=stylesheet HREF="/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/customer/Pioneer/glbl/glbl_ie5.css?6.0.13.0.1">
<LINK REL=stylesheet HREF="/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/customer/Pioneer/ur/ur_bdy_prtl_ie5.css?6.0.13.0.1">
<LINK REL=stylesheet HREF="/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/customer/Pioneer/prtl_std/prtl_std_ie5.css?6.0.13.0.1">

<META http-equiv="Content-Script-Type" content="text/javascript">
<SCRIPT src="/irj/portalapps/com.sap.portal.epcf.loader/script/standard/js13_epcf.js?6.0722"></SCRIPT>
<SCRIPT>

</SCRIPT>



<script language="JavaScript">
ur_system = ;
</script>

<title >SAP Enterprise Portal 6.0</title><meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"><link REL=STYLESHEET HREF="/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/customer/Pioneer/ur/ur_ie5.css?6.0.13.0.1" TYPE="text/css" ><link REL=STYLESHEET HREF="/irj/portalapps/com.sap.portal.runtime.logon/css/logon.css" TYPE="text/css" ><link REL=STYLESHEET HREF="/irj/portalapps/com.sap.portal.runtime.logon/css/main2.css" TYPE="text/css" ></head><body class="prtlBody urFontBaseFam urScrl">







Hi,
you can use this alternative to upload the par file
System administrator->support->portalruntime->Administration console->click on the browse button to find the par file and click the upload button.
see this link for more information
http://help.sap.com/saphelp_nw04/helpdata/en/2d/b8b2426dbec86ae10000000a155106/frameset.htm
reward useful answerd

Problem while deploying PAR from NWDS

Hi,
I am getting this error while deploying a PAR file from NWDS.
Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
more detail.
regards,
Arun

Hi
You also have the option of uploading the par by logging into the portal ...
System Administration->Support->Portal Runtime->Administration Console
just browse and upload the par file...
Create an IView from par and can see the output
Avinash

Quick par upload NWDS ERROR Unexpected end of file from server

Hi:
I can´t deploy my par file from NWDS, this is the error:
28.04.09 / 08:24] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.net.SocketException: Unexpected end of file from server
     at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:763)
     at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:626)
     at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:760)
     at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:626)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:957)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.portal.developmentTools.general.uploader.QuickPARUploader.run(QuickPARUploader.java:146)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Any idea?
Thanks a lot for your time on this thread.
Rocío.

Hi Rocio,
Check the proxy settings in NWDS and use JAVA RUNTIME 1.5.0_06-b05.
Please refer to the links below where similar problems have been resolved:
Cannot deploy par from NWDS
Can not download SOAP CLIENT TOOL
Another way of deploying the .par file is from System Administration -> Support -> Portal Runtime -> Administration Console.
Hope this resolves your issue.
Regards,
Seema Rane.
Edited by: Seema Rane on Apr 29, 2009 8:57 AM

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

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

Deploy .par fiel in WEbdynpro

Can anybody please tell me how to import and deploy .par file in WEbdynpro(NWDS)..awaiting

Importing
File -> Import -> PAR
Project name is usually something like "com.sap.parfile"
NWDS does not import the JAR files within PAR files properly.
1. Copy the par file and rename the copied par to a .zip extension.
2. Extract the new zip file
3. find .jar files.
4. Drag these jar files into the same location inside NWDS.
Exporting
1. Right click on the project name in the navigator
2. Select Export
3. Follow the steps

Error while import PAR with schedule task

Hi everybody
I've the following error while import a new PAR with schedule task in Portal NW04s
Inner Stack is:
Unable to lock the local configuration to run import "import_it.tsf.pld.cercapersone.updateadgruppofs.st.prjconfig_config_fwk_service_4692550,4692550_(ready)".
System error is "LockConfigException: Configuration framework system error: "configuration-lock-service overloaded: cannot acquire central-lock file for config://local"".
Inner Stack is:
LockConfigException: Configuration framework system error: "configuration-lock-service overloaded: cannot acquire central-lock file for config://local"
at com.sapportals.config.fwk.data.ConfigLockManager.lockWithDependent(ConfigLockManager.java:507)
thanks in advance

Hi Ram,
I've encountered the problem only on productive instance with offline deployment (Scheduler Tasks reinitialize CRT). Before a restart I have to make sure it works.
thanks for your help!
Gennaro

Deployment issue in NWDS while deploying BPM

Hi Experts,
I m getting following deployment error in NWDS (SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP11 PAT0002) while deploying BPM.
can u plz revert back if you have encountered similar issue.
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/A6D/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/1418/DC-I205.sda] failed
at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
... 11 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: TxException
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
... 12 more
Caused by: java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:621)
at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.IllegalStateException: Galaxy commit failed (for a possible cause, refer to the nested exception(s)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:117)
at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:36)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:589)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1120)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:333)
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:610)
... 24 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Transaction locked for rollback; Commit refused.
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_precommit(AbstractTransaction.java:186)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:75)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:115)
... 29 more
Caused by: com.sap.glx.core.dock.api.DockException: Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:693)
at com.sap.glx.core.dock.impl.DockingPortal.configureCallback(DockingPortal.java:495)
at com.sap.glx.core.dock.impl.DockingPortal.runConfigureCallback(DockingPortal.java:998)
at com.sap.glx.deploy.impl.DeployControllerImpl$DeployProcessor.runProcessorWork(DeployControllerImpl.java:801)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.run(DeployControllerImpl.java:624)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.access$1300(DeployControllerImpl.java:585)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:549)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:543)
at com.sap.glx.core.kernel.DefaultRuntimeManager.requestRuntimeMode(DefaultRuntimeManager.java:1110)
at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.executeDeployWork(DeployControllerImpl.java:1177)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.executeDeployActuatorCallbackWork(CoreServiceRRHandler.java:138)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.access$400(CoreServiceRRHandler.java:50)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.callCoreServiceHandlers(CoreServiceRRHandler.java:314)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.addVersion(CoreServiceRRHandler.java:337)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2565)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1535)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:339)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:261)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:251)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)
... 22 more
Caused by: com.sap.glx.adapter.api.AdapterException: Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 7b9afc88c8f151c20d38cef0d370f416 using configuration mode DEPLOYMENT
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:669)
... 41 more
Caused by: java.lang.RuntimeException: Transformer could not get lock within 60 seconds
at com.sap.glx.core.internaladapter.Transformer$Share.acquireWrite(Transformer.java:875)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor$GeneratorLocalProvider$ImplementedGeneratorLocal.acquireWrite(Transformer.java:2317)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor.insertRule(Transformer.java:2775)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationHandler.configure(Transformer.java:2930)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplateHandler.configure(Transformer.java:3472)
at com.sap.glx.core.internaladapter.Transformer.configure(Transformer.java:3675)
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:666)
... 41 more
at com.sap.engine.services.ts.transaction.TxRollbackException.writeReplace(TxRollbackException.java:163)
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:597)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1040)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1116)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
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:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
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:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:331)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:139)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:488)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:81)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
... 3 more

Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their.

(CRM-) ISA-developers: How do you work with NWDS?

Hello,
starting ISA-webapplication-development nearly 4 years ago under CRM 3.0, I used JBuilder 5 as IDE (this was the recommendation of SAP), Perforce for version-controlling and Tomcat as local webapplication-server. It took some effort to build up projects in JBuilder, but after that everything was possible I expect from a modern IDE: coding of java and JSPs with method-suggestion, syntax-check of java and JSPs, building up war- and ear-files, ...
In the last months my enterprise migrated to CRM 4.0, and now the new development tools are Netweaver Developer Studio and SAP J2EEngine 6.40. And this is the point where the problems begin: In the "ISA Development and Extension Guide" there is only documented how to build up a java-project for compiling your own classes. But compiling java classes is only one of the required development tasks I need. What about JSP development? Why use an external tool as ISA build tool to build the ear-file, then call the external SDM-tool for deploying the new web-application, if this is (theoretically) possible in NWDS?
Yes, I know that it is possible to setup J2EE-projects in NWDS.
Yes, I know that there are plugins as wst for doing jobs as JSP-syntax-checking as mentioned above.
But up to now I was not succesful to configure the NWDS with any plugins (one of the problems: I did only find Eclipse 1.3 plugins which seems to be incompatible with NWDS basing on old ecplise 1.2) or setup NWDS-projects to get the old quality of JBuilder-development.
So is there anybody out there who extended the NWDS with any plugins and built up succesfully the necessary NWDS-projects for doing all this tasks that effective ISA-webapplication-development is possible?
With best regards,
Holger Dittrich

To all,
First off let me start by saying the the SAP NetWeaver Develper Studio is designed to work more with portals than with CRM and r/3 web apps. With that said you can confidently do extreme modifications with the NWDS. IN my environment I use J2EE 6.20 and J2EE6.40 with NWDS CRM and R/3 ISA B2B B2C with the Build Tool and SDM all working without any glitches. I know, web work with SAP and no glitches but it can be done.
Use the NWDS for modifcation the Java, STRUT, JSP, HTML, and any other individual files within the web-app root.
Use the SAP Build Tool to rename and build the ear's that will be migrated through out your infrastructures landscape.
Use Software Delivery Manager (SDM) for the loose deployment of ear's and sca's. The SDM configures the library.txt and reference.txt files within the J2EE with the system libraries your version of EAR's and SCA's require.
J2EE to run the application in testing and live environment.
Let me answer one very important question. Why should I use a seperate build and delivery tool when that functoanlity is in NWDS? Remember the NWDS is designed to integrate tightly into the portals realm. Portals is a very strict environment while ISA is loose and allows for greatest amount of customizations. The Deploy and Build functonality within the NWDS are designed to work with portal apps or views not with full blown stand alone web-apps.
If anyone is interested in how to get all of the pieces to talk to each other J2EE, NWDS, Build Tool, SDM let me know through this thread. I used to teach this class for SAP America and can provide you with a docuemnt on creating an ISA project with NWDS and exporting to the Build Tool and redeploying through the SDM.

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,

Sample adapter with NWDS

Hi gurus
Could any one give me a description of how to use the sample adapter (sample_ra.sda) with NWDS so that I would be able to compile it successfully.
[I need to know what files to import and how i do it]
Thanks in advance
Jason

> - How do i import this new adapter in XI?
> - Do i need to package it in a certain way?
you have to deploy the adapter to the XI/PCK with SDM.
For this your create an RAR (ressource adapter archive) with WinZip and store this in an SDA file again with WinZip.
See here:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/eae1401b52b533e10000000a155106/frameset.htm
The adapter meta data are uploaded to Integration Repositiory, so you can create communication channels for your adapter.
> - Is it obligatory to have a PCK?
No, but with a seperate testing system you minimize the risk to disrupt the XI system with bad code
> The documentation on SDN are not very clear on the matter.
We will work on that soon
Regards
Stefan

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

Unable to upload the PAR from NWDS

Hi ,
I am unable to upload the par from NWDS as it is throwing the error "Unable to upload"
I have done the proxy settings in NWDS.
can any one tell me is there any other settings i have to do in NWDS.
Thanks
Ajay

Hi Ajay,
Have you copied the NWDS installed stuff from other system and working on that?
Anyway, you can go about this way to upload your par.
Goto System Administration -> Support -> portal runtime -> Administration console -> Browse and add your par -> say upload. Thats it and your par is uploaded:-).
Hope it helps.
Regards
Deepa
Pls reward points for helpfull answers.

Deploy PAR with NWDS SP19

Similar Messages

Maybe you are looking for