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

Similar Messages

  • 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">
    <!-- EPCF: BOB Core -->
    <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>
    <!--
    EPCM.relaxDocumentDomain();
    EPCM.init( );
    EPCM.DSM.init( );
    function SAPWP_receiveSessInfo( sessInfo, frameRef ){
      EPCM.DSM.processSession( sessInfo, frameRef );
    //-->
    </SCRIPT>
    <!-- EPCF: EOB Core -->
    <!-- HTML Business for Java, 60NW_VAL_REL, 145109, Wed Jul 13 10:38:22 PDT 2005 -->
    <!-- HTMLB: begin VARS -->
    <script language="JavaScript">
    ur_system = ;
    </script>
    <!-- HTMLB: end   VARS -->
    <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">
    <!-- EPCF: Component com.sap.portal.runtime.logon.certlogon, hnlfbdolaebaghofikiedbahpmidieno -->
    <!-- EPCF: Component com.sap.portal.runtime.logon.default, hobbmlmpbnllcpciikmkhjahpmidieno -->
    <!-- component context:com.sap.portal.runtime.logon.default-->
    <!-- class: com.sapportals.portal.ume.component.logon.SAPMLogonComponent-->
    <!-- trying to go to page umLogonPage-->
    <!-- before including jsp resource umLogonPage.jsp-->

    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

  • 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.

  • 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

  • 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

  • Problems deploying par file via Netweaver Developer Studio

    Hello,
    I have problems deploying a par file using the SAP Netweaver Developer Studio.
    In the SNWDS i configure the following:
    Window -> Preferences -> SAP Enterprise Portal
    Alias: IEP
    Host: khz059
    Port: 52900
    Login: Administrator
    Description: Testportal
    The logon Url of the portal is http://khz059:5290052900/irj/portal
    If i try to upload a par file via "Quick PAR Upload" i get the error messages:
    "Unable to connect to the portal
    Operation failed: Please make sure the server 'IEP' (khz059:52900) is running or check the log (sap-plugin.log) for more detail."
    Am I using the proper settings? Am I using the wrong port?
    I don't know whats wrong.
    Can anyone help me?
    The logfile shows:
    [12.09.05 / 14:53] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Error writing to server
         at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:302)
         at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:314)
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:634)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
         at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
         at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:519)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.portal.developmentTools.general.uploader.QuickPARUploader.run(QuickPARUploader.java:146)
         at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
         at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
         at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Best regards,
    Nils Kloth

    Hi Nils,
    I think you must have selected the defualt checkbox (Try and uncheck that). Also uncheck the checkbox for "<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.

  • 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,

  • 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

  • Passing Parameters from Par component to WebDynpro Application

    Hi all,
    We have a created a WebDynPro and par application. Also we want to pass the parameters from Par component to WebDynPro Application. ( not in query string as application parameters property of webdynpro iView).
    Is it possible to do so? if yes then how?
    Please help us......
    Thanks and regards,
    Prath.

    Hi ,
    If the iviews are on the same page you can use portal eventing for that
    see the documents on portal eventing
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/ep/_d-f/enterprise%20portal%20client.pdf">EPCF pdf</a>
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/d3/3857422d095542e10000000a1550b0/frameset.htm">EPCF</a>
    Hope this helps you
    Regards
    Rohit

  • Error deploying PAR file from Developer Studio (NW04)

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

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

  • Error while deploying .par file through system admin

    I have tried to modify logon.par file but when I was try deploy that file again through system admin then I got this error...................
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    com.sapportals.portal.ume.component.logon.SAPMLogonComponent.
    Exception id: 10:19_11/05/07_0006_13454550
    See the details for the exception ID in the log file
    Please help me out I am using sneak preview 7.0
    Detailed Error Log & Trace
    =========================================================
    Exception ID:08:55_11/05/07_0002_13454550
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.portal.support.browse.default
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonComponent of Portal Component com.sap.portal.support.browse.default because: Could not find implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:242)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 26 more
    Caused by: java.lang.ClassNotFoundException: com.sapportals.portal.ume.component.logon.SAPMLogonComponent
    Found in negative cache
    Loader Info -
    ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@3389d1]
    Parent loader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@1b7a6fa]
    References:
       not registered!
    No resources !
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 30 more

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

  • 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

  • Deploy PAR from Ep5 to EP6 problem

    Hi ,
    I am now using EP6 and i need to deploy a PAR file ( generated in EP5) into the portal using ( System administrator /support / portal runtime / Admin console ..) to upload it into PCD , the upload was processed successfully [ but i see that in the list  :
    <i> Server ID      Local version Repository version  
    P1  4206950 <b> undefined  undefined</b>  ( while others : 5.0.5.4 )</i>And then in the content management when i want to create a new iview from PAR file , i can not see it in the list ( P1.PAR ) that i have just deployed ....till now i am very confused about it , anyone can help me to deploy it ( I need it urgently right )
    Thanks ,
                   Qui nguyen

    Hi vankat ,
    First i'd like to thank so musch for your answer , i've done like that i saw it in the PCD but when i preview it the following errors occur:
      Portal Runtime Error
    <i>An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Could not find portal application .
    Exception id: 01:05_26/12/06_0034_4206950
    See the details for the exception ID in the log file</i>
    And
      <i>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/Development..............g.dev_iview
    Component Name : null
    Page could not create the iView.
    See the details for the exception ID in the log file</i>
    What are the above lines mean and how to recover it ? and if i want to look for the log file where i can find it in the server ?
    Thanks ,

  • Deploy par files with code from NWDI

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

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

  • Unable to Deploy and Run a WebDynPro Application in NWCE 7.1 DS

    I have successfully built a test application in WebDynPro within the NWCE 7.1, but every time I try to deploy and run the application I get the following error:
    No default system is configured in SAP System Registry [ERROR: Apr 24, 2008 10:32:51 AM /userOut/daView_category (eclipse.UserOutLocation) [Thread[Worker-19,5,main]] ]
    It seems like a straightforward error, but when I go to the System Registry I cannot see how to set up a default system for the application.  There is no "DefaultSystem" entry and so I am sure that I have to add one, but cannot find any documentation to help me do this.
    Thanks.

    First, thanks for the fast responses. 
    I had gone to SAP AS JAVA preference before, but couldn't figure out how to get my system to show up in the dropdown box.  When you put in the server name and the 0 instance, it then finds the system and all instances under the system.  That was my missing link.
    I can now deploy and run and move on to my next (inevitable) problem.
    Thanks again.

Maybe you are looking for