Deploying the par file

Hello experts...
      Can any body have the step by step process for how to deply the par files?
please let me know if you have any weblogs?
Thanks
padma

Hi,
If you have sys admin privileges go to
Sys Admin --> Support --> Portal Runtime --> Administration Console and choose ARchive deployer
If you have java developer role assigned then you can do it from Java Development tab.
From web dynpro
http://help.sap.com/saphelp_nw04/helpdata/en/68/f64942da51690de10000000a155106/frameset.htm
Hope this helps,
Thanks,
Praveen
PS.Dont forget to reward points

Similar Messages

  • Error while deploying the par file

    while deploying  an application in NWDS we are getting the error as"operation failed,please make sure that the server is running or check the log."
    we have ensured that the server is running,but the deployment is getting failed.
    Please suggest tips to deploy the PAR file successfully.
    Thanks.

    Hi,
    We are using NWDS to create a small application to develop ( for ex jspdynpage)
    .while deploying the par file or exporting it to the server,we are getting the error as "please make sure that the server running.HTTPS protocol is not supported,please ensure that this server is not using HTTPS.
    the server is running and is shown in green.
    we have also  disabled the proxy settings.
    we have also tried by specifiing the IP of the server in the proxy settings.
    the above steps didnt work.please suggest the things to do to make this working.
    thanks,
    rajani.

  • Unable to deploy the PAR file after the first successfully deploy.

    Hi, my gurus.
    I found a problem when I developed the JspDynPage.
    That is after  first deploy the PAR file successfully,I found there is a miss in portalapp.xml, so I correct the miss and then do a second delpoy.But it didn't work.
    I goto the Server's file system to find the portalapp.xml,
    the content of xml was still the old one.
    Anyone can help me, I don't want restart the J2EE Engine,
    because the restart will last for 15mintues.
    Thanks.

    Hi,
    I dont think there is no need to restart your J2EE Engine.
    Becuase i dont think you have a requirement to create an iview from that PAR File
    If it is so delete the previous iview and create a new iview.
    From the updated PAR File in ur System
    Every Time when you uplaod the PAR the old instance will be lost.and new changes will come into effect on each upload done by you.
    There is no question of restarting ur J2EE Engine.
    Whenever there is a change in you PAR.
    Hope this Helps you.
    Thanks & Regards,
    Lokesh.
    Reward Points if helpfull

  • Issue while uploading the PAR file thru system admin- AdministrationConsole

    Hi All,
    I have downloaded the PAR file "com.sap.portal.navigation.lightdetailednavigationtree.par.bak" from system admin->support->Portal Runtime ->browse deployment->Web-Inf->deployment->PCD.
    after downloaded to the desktop for manual change in one of the JSP file rather than importing into NWDS. I have removed the bak from the file and added the .Zip to the file and i extracted the file.
    here inside i got the three folders i.e WEB-INF,PORTAL-INF and file_list. now i went to jsp file called "LightDetailedNavigationTree.JSP" , changed one small property value  in the code from false to true. after that i again zip the folders strcuture make the file name as original in the form of .PAR file. now i am trying to upload it in the portal thru system admin->portal runtime->administration console, but i am getting the deployment error as mentioned in the below.
    even though with error, the wrong version of the par file with extension .err was saved in the PCD folder strcture, and original file also still exists. now i wanted to remove the wrong version of the file from PCD, what is the procedure to delete the wrong version, here in administration console i found one button clean , but i could not able to locate the wrong file version , only original right version showing up in the clean dropdown??
    Can u tell me what is the procedure to edit the PAR file manually after downloaded to the desktop, rather than going edit thru NWDS??
    if we need to upload the PAR file after changes, do we need to delete the original PAR file before we upload the new version of the same PAR or it will be automatically overwrite the original file with the same name??
    Still i am getting confusion, please let me know how to edit the PAR file manally and how to upload the PAR file with out any isse while uploading it in the portal thru system admin->administration console??
    Any pointers in this regard would be the great help to me??
    Error as i got while uploading the par file after the changes manually. (com.sap.portal.navigation.lightdetailednavigationtree.par)
    2011-01-24_07-40-18
    Application upload failed: com.sap.portal.navigation.lightdetailednavigationtree.par
    java.util.zip.ZipException: Error opening zip file /usr/sap/BIS/DVEBMGS13/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.sap.portal.navigation.lightdetailednavigationtree.par
    *     at java.util.zip.ZipFile.open(Native Method)*
    *     at java.util.zip.ZipFile.<init>(ZipFile.java:140)*
    *     at java.util.zip.ZipFile.<init>(ZipFile.java:155)*
    *     at com.sapportals.portal.prt.deployment.ArchiveIterator.iterate(ArchiveIterator.java:39)*
    *     at com.sapportals.portal.prt.deployment.UploadProcess.upload(UploadProcess.java:60)*
    *     at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:835)*
    *     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)*
    *     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)*
    *     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)*
    *     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
    *     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)*
    *     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)*
    *     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)*
    *     at java.lang.reflect.Method.invoke(Method.java:391)*
    *     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:706)*
    *     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)*
    *     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:249)*
    *     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)*
    *     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)*
    *     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)*
    *     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)*
    *     at java.security.AccessController.doPrivileged(AccessController.java:246)*
    *     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)*
    *     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)*
    *     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)*
    *     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)*
    *     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)*
    *     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)*
    *     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)*
    *     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)*
    *     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)*
    *     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)*
    *     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)*
    *     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)*
    *     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)*
    *     at java.security.AccessController.doPrivileged(AccessController.java:219)*
    *     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)*
    *     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)*
    Can you please what are the steps if any specific while editing the PAR file manually and uploading it with out any issues??
    Thanks in advance.
    Regards,
    PortalUser
    Edited by: PortalUser100 on Jan 24, 2011 6:01 PM
    Edited by: PortalUser100 on Jan 24, 2011 6:04 PM
    Edited by: PortalUser100 on Jan 24, 2011 6:05 PM

    Hi Shusil,
    Thanks for your reply.
    I have one more dought here.
    the PAR file of lightdetailnavigation has been modified thru NWDS and deployed the PAR file by adding the required JARS.
    Now my question is, the application server which i am used as local portal server installed in my desktop.
    now this depoyed latest par file i have picked it from the workspace in the local desktop, and i am planning to upload the same PAR file in of the sandbox portal system of client , will it update successfully in the new portal apart from the deployed portal??
    i am here used the path system admin->support->portal runtime -> administrate console  ( this in the sand box system to upload the par file which was deployed in the local portal server in my desktop.
    Thanks,
    Portal user

  • Where to get the par file for visual composer application?

    Hi Gurus,
    I have referred few forum postings about transporting VC iview .
    to do that first we have to deploy the par file of the Visual composer application into the target system(QA & Prod) where ever we want to import it........
    Now my query is I went to System admin->support-Portal runtime->Root Folder-->Portal apps........
    where i have seen my Visual composer application name and otpion to download when I downloeded it it has downloded in unknown format............can i deploy this to SDM of the target system?
    Or I need to change the file format into par or par.bak file?
    please tell me how to go about it.........
    higher points will be rewarded for the useful inputs.......
    Thanks in Advance,
    Dharani

    Hi Dharani,
    Tools --> Options --> Compiler --> Check box deploy for par and mention the namespace and vendorname in the PAR prefix name
    Very similar to how its done in NWDS.
    Cheers,
    Rahul.

  • Problems with the par file of Browse Deployment

    Hi,
    I had an error message with the com.sap.portal.support.browse.default in Browse deployment, that this iView is not found.
    Fortunately I had a file with the same name, so I uploaded it, but it was the wrong one (Why do they all have the same file name?). I uploaded the par file of the masthead, so every time i click on the browse deployment link I get the masthead and now I have no chance to download other par files.
    Do I still have the right iView on the Server or in the Portal? If yes, where? Or can anybody send me the right par file?
    e-Mail: Ulli_Arndt(at)gmx.de
    Thanks in advance!
    greetings,
    Ulrike

    Hello Ulrike,
    Most companies use different servers for development and Production. The Browse Deployment Option should be used only with the development server. If you're going to use it with the Production server, there could be problems, as the two servers have a different architecture.
    Once you sign in to the DEVELOPMENT SERVER using your user id, ensure that you have the Systems Administration Role and click on the tab corresponding to the same.
    Then select Support.
    Select Portal Runtime.
    Select Browse Deployment.
    Once you do this, you'll see a filepath on top of the page just below the top level navigation area. Here's where most people commonly make a mistake.
    Ensure that the breadcrumb is EXACTLy as follows:
    ROOT/WEB-INF/deployment/temp
    If this is not the case, clcik on ROOT in the filepath displayed on your screen and navigate along the filepath above so you reach the correct iView.
    You should now see a list of files with the extension .par.bak.
    Upon downloading any of these files, the downloaded .rar file for most of the files with have the same filename. Once you unzip this file once or twice, you'll get a .par.bak file with the same filename as the one you downloaded. Rename the extracted .par.bak file by removing the .bak extension. You'll be left with a .par extension now.
    You can now import this file in NWDS and work on it as required.
    I hope this helps. Let me know if you have anyfurther questions. Screenshots are alsways helpful, especially of the filepath on the top of your screen.
    Regards,
    Farsheed

  • Error while deploying a PAR file from NWDS into an ECC.

    Hi all,
    I am getting this error while deploying a PAR file from NWDS into an ECC.
    Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
    more detail.
    My server is running properly
    1 - Where is sap-plugin.log file? I don´t find it. 
    2 - Could there be another file with another name with information about the error?
    3 - Is there another way to deploy the file directly from the ECC?
    Regards,

    Hi,
    Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
    Windows/ Prefereces / SAP Enterprise Portal
    Check the following enteries
    Alias
    Host
    Port
    Login etc.
    Regards,

  • Error in deploying the par from NWDS

    Hello,
    I am not able to deploy a par file from my NWDS, whereas I am able to deploy the same par from another machine which is in the same network. The error thrown in my machine in the file sap-plugin.log is given below. Kindly help to solve this issue
    [17.01.06 / 14:04] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Server returned HTTP response code: 407 for URL: http://212.140.143.165:57100/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=administrator&j_password=admin123&j_authscheme=default&uidpasswordlogon=log on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
         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)
    Regards,
    Rukmani

    Hi Rukmani,
    407 is "Proxy Authentication Required", which sounds like you are using a proxy and on the other machine, the network access to the portal works in fact different or the authentication mechanism is different.
    This is hard to elaborate remotely...
    Hope it helps
    Detlev

  • Unable to deploy a par file from NWDS

    Hi experts ,
    Im getting the below error on deploying a par file from my nwds studio ,
    please suggest a solution
    createDeployArchive:
          [copy] Copying 1 file to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local
    Error: E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\logs\build.xml:341: Failed to copy E:\sap_ep_prog\dc\.dtc\1\t\7FEDA11250B7CF9AB991A30B09B76536\com.***.par to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par due to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    at org.apache.tools.ant.taskdefs.Copy.doFileOperations(Copy.java:628)
    at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:421)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:116)
    at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:58)
    at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
    at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
    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.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
    at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.dcutils.DCBuildWrapper.run(DCBuildWrapper.java:49)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:252)
    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.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
    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)
    Caused by: java.io.FileNotFoundException: E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:628)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:309)
    at org.apache.tools.ant.taskdefs.Copy.doFileOperations(Copy.java:617)
    ... 62 more
    --- Nested Exception ---
    java.io.FileNotFoundException: E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:628)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:309)
    at org.apache.tools.ant.taskdefs.Copy.doFileOperations(Copy.java:617)
    at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:421)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:116)
    at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:58)
    at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
    at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
    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.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
    at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.dcutils.DCBuildWrapper.run(DCBuildWrapper.java:49)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:252)
    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.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
    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)
    Ant runtime 8.863 seconds
    Ant build finished with ERRORS
    Failed to copy E:\sap_ep_prog\dc\.dtc\1\t\7FEDA11250B7CF9AB991A30B09B76536\com.***.par to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par due to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    Error: Build stopped due to an error: Failed to copy E:\sap_ep_prog\dc\.dtc\1\t\7FEDA11250B7CF9AB991A30B09B76536\com.***.par to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par due to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    Build plugin finished at 2014-07-15 18:36:07 GMT+05:30 (IST)
    Total build plugin runtime: 9.113 seconds
    Build finished with ERROR
    Regards
    Govardan

    Hi Talviv ,
       The folder where Par file is residing  has read only property i.e
    gen->local .
    but we should not change this property of a DC folder i guess , im getting this error sometimes and some times im able to deploy with out any error.
    Regards
    Govardan

  • Deploying a Par file using ANT

    Hi All,
    Can anyone tell me the steps how to deploy a PAR file using ant script on netweaver server.Give me some sample ant file.Suggestions will be rewarded.
    Thank you in advance.
    Regards,
    Karthick

    Hi Karthick,
    see PAR-File deployment with ANT (EP6)
    Hope it helps
    Detlev

  • Help - Downloading the par file into NWDS

    Hi,
    Can anyone please tell me how to download the par file in NWDS to customize iviews.
    What is the pre-requisites?
    Is there any step by step procedure available to download the EP iViews and put our codes into that.
    Regards,
    Nirmal

    Hi Nirmal
    You can find all pars at this location :
    <Drive>:/usr/sap/<SID>/JC<Instance number>/j2ee/cluster/server<XX>/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/
    Reneme selected par name (remove .bak extension). And than follow :
    http://help.sap.com/saphelp_nw2004s/helpdata/en/96/df7f409cd50a1ae10000000a155106/frameset.htm
    Regards
    Jakub Krecicki

  • How to find the source code in the par files for B Package  Projects 50.3

    Hi,
    I want to modify the par files (related to Business Package Projects 50.3) which i imported into Netweavier Developer Studio. I didn’t find any jsp files or any java files in it.
    If any one worked in this Business Package for Projects 50.3, please give the solution.
    Thanks
    Ravi

    Ravi,
       The recommended appraoch for modifying Business Packages is by using NWDI - Netweaver Development Infrastructure.( new name for JDI)
        You should be able to make modification, package/build a new version and deploy. The pre-requisite is you need to set up NWDI on the server, create a Track in CMS(Change Management SErvice) and configure your DTR. Once done you can import the configuration file into your NW Developer Studio and make modifications.
      hope this helps.
    *points will be appreciated

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

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

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

  • Chaging WebService URL after deploying iView(PAR file)

    Hi,
    I am creating an iView using .Net PDK and will be accessing methods of a WebService using a proxy class.
    I don't want to hardcode URL of the WebService in my proxy class.
    Is there any solution by which I can read URL from some config file, so that if I want to change URL of web service, I just have to change the content of the config file instead of recompiling proxy class and deploying new PAR file.
    Regards,
    Ajay

    Hi ajay,
    You can define it as a property of the iView.
    For details see:
    .NET iView
    and:
    https://media.sdn.sap.com/html/submitted_docs/PDK_for_dotNET_10/Tutorials/Personalization.htm
    Hope that helps,
    Yoav.

  • Error while deploying the SAR file to EM Console.... MDS-01330: Failed to l

    Hi Team,
    We configured the HUDSON Tool with BPEL Projects. When I am trying to deploy the BPEL Projects to the SOA SERVER. I am getting an error associated with MDS. We never used MDS for storing teh metaData But still we are getting an error.
    10:35:42 deploy:
    10:35:42 [input] skipping input as property serverURL has already been set.
    10:35:42 [input] skipping input as property sarLocation has already been set.
    10:35:42 [deployComposite] setting user / password ..., user = weblogic
    10:35:42 [deployComposite] Processing sar = D: \ Programs \ hudson \ jobs \ P6.1_XYZ \ workspace \ XYZ/deploy/sca_XYZ_rev1.17.jar
    10:35:42 [deployComposite] Adding sar file - D: \ Programs \ hudson \ jobs \ P6.1_XYZ \ workspace \ XYZ \ deploy \ sca_XYZ_rev1.17.jar
    10:35:42 [deployComposite] Creating HTTP connection to host: 10.246.161.147, port: 8020
    10:35:44 [deployComposite] Received HTTP response from the server, response code = 500
    10:35:44 [deployComposite] ----> response code = 500, error: Error during deployment: Error occured when creating target MDS instance.: Oracle.mds.config.MDSConfigurationException: MDS-01330: Failed to load the configuration document MDS
    10:35:44 [deployComposite] MDS-01329: Unable to load the element "persistence-config"
    10:35:44 [deployComposite] MDS-01370: The configuration for use MetadataStore store metadata \ "soa-infra-store \" is invalid.
    10:35:44 [deployComposite] MDS-00922: Unable to create snapshot of heading ConnetionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl".
    10:35:44 [deployComposite] weblogic.common.resourcepool.ResourceDisabledException: Pool mds-soa is Suspended, cannot allocate resources to applications ..
    10:35:44 [deployComposite]: MDS-01330: Failed to load configuration document MDS
    10:35:44 [deployComposite] MDS-01329: Unable to load the element "persistence-config"
    10:35:44 [deployComposite] MDS-01370: The configuration for use MetadataStore store metadata \ "soa-infra-store \" is invalid.
    10:35:44 [deployComposite] MDS-00922: Unable to create snapshot of heading ConnetionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl".
    10:35:44 [deployComposite] weblogic.common.resourcepool.ResourceDisabledException: Pool mds-soa is Suspended, cannot allocate resources to applications ..
    10:35:44 [deployComposite].
    10:35:44
    10:35:44 BUILD FAILED
    10:35:44 D: \ Programs \ hudson \ jobs \ P6.1_XYZ \ workspace \ XYZ \ build.xml: 44: The following error occurred while executing this line:
    10:35:44 D: \ Oracle \ 11gR1ps1 \ jdeveloper \ bin \ ant-sca-deploy.xml: 132: Error during deployment: Error occured when creating target MDS instance.: Oracle.mds.config.MDSConfigurationException: MDS-01330 : Failed to load configuration document MDS
    10:35:44 MDS-01329: Unable to load the element "persistence-config"
    10:35:44 MDS-01370: The configuration for use MetadataStore store metadata \ "soa-infra-store \" is invalid.
    10:35:44 MDS-00922: Unable to create snapshot of heading ConnetionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl".
    10:35:44 weblogic.common.resourcepool.ResourceDisabledException: Pool mds-soa is Suspended, cannot allocate resources to applications ..
    10:35:44: MDS-01330: Failed to load configuration document MDS
    10:35:44 MDS-01329: Unable to load the element "persistence-config"
    10:35:44 MDS-01370: The configuration for use MetadataStore store metadata \ "soa-infra-store \" is invalid.
    10:35:44 MDS-00922: Unable to create snapshot of heading ConnetionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl".
    10:35:44 weblogic.common.resourcepool.ResourceDisabledException: Pool mds-soa is Suspended, cannot allocate resources to applications ..
    This is not pertaining to a single Project and this was happening with all BPEL Process.
    Please help us since it was blocking us to either delete a SAR file from EM Console as well as Deploy the SAR file to the EM Console.
    Thanks,
    Venugopal Raja

    weblogic.common.resourcepool.ResourceDisabledException: Pool mds-soa is Suspended, cannot allocate resources to applications ..Check server logs to find out why mds-soa is suspended. Make sure that datasource mds-soa is up and running on SOA servrs before deploying an application.
    Regards,
    Anuj

Maybe you are looking for