PAR File Export
I have a Development Component it is an Enterprise Portal Application Standalone. It is a simple application for a weather magnet using RSS Feeds.
It was created by another developer and his instructions for deployment were to Right Click the project and choose Quick PAR Upload->however this option is greyed out to me. I tried to do a simple export (which is what we do with the Enterprise Portal Application Module DCs) but the project is not listed in the options of projects to select.
I have tried to create a new Enterprise Portal Application Module DC and copied this code into the new DC and it exported fine only when I tried to run the iView containing the application I received errors - I assumed the application was broken but the developer who created the application said it must be Standalone to work so I am just trying to figure out why I cannot deploy a Standalone App
Please read this:
http://help.sap.com/saphelp_nw04/helpdata/en/00/ef0942364ec417e10000000a155106/frameset.htm
Standalone application build should result in SDA file, which has PAR file inside.
SDA file, once you get it, can be deployed via SDM.
Trgards,
Slava
Similar Messages
-
Weather magnet PAR File Export Error
I have created a weather application PAR File following this blog: Create a weather magnet using xml feed from weather.com
As far as I can tell I have followed everything correctly however when I select Export to create the file I get the following error:
Nov 11, 2008 11:32:54 AM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[main,5,main]] ERROR: ep_wa: Build failed for myl.com/ep_wa(myl.com_MYLAN_1) in variant "default": The Build terminated with errors
Build log -
Development Component Build (2008-11-11 11:32:54)
Component name: ep_wa
Component vendor: myl.com
SC compartment: myl.com_MYLAN_1
Configuration: JP1_EPPHASE1_D
Location: JP1_EPPHASE1_D
Source code location: http://max-sap50:50000/dtr/ws/EPPHASE1/myl.com_MYLAN/dev/inactive/DCs/myl.com/ep_wa/_comp/
DC root folder: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_comp
DC type: Enterprise Portal
DC subtype: Portal Application Module
Host: 03-M100236
DC Model check:
All used DCs are available locally
validating dependency to build plugin "sap.com/tc/bi/bp/portalapplication"
validating dependency to public part "default" of DC "sap.com/webservices_lib"
validating dependency to public part "default" of DC "sap.com/sapxmltoolkit"
validating dependency to public part "default" of DC "sap.com/com.sapportals.htmlb"
validating dependency to public part "default" of DC "sap.com/epbc.prtapi._api"
validating dependency to public part "default" of DC "sap.com/epbc.prtpars._htmlb"
validating dependency to public part "default" of DC "sap.com/epbc.prtpars._soap"
validating dependency to public part "default" of DC "sap.com/epbc.prtapi._test"
validating dependency to public part "default" of DC "sap.com/servlet"
validating dependency to public part "default" of DC "sap.com/jaxm"
DC model check OK
Start build plugin:
using build plugin: sap.com/tc/bi/bp/portalapplication
starting build plugin from : C:Documents and Settingsm100236.dtc3DCssap.com c i pportalapplication\_compgendefaultpublicdef
Build Plugin 'PortalAppPlugin', Version 7.00 SP 15 (645_VAL_REL, built on 2008-02-16 08:47:10 CET, CL76043)
development component: ep_wa (myl.com)
software component: MYLAN (myl.com)
location: JP1_EPPHASE1_D
type: Enterprise Portal, subtype Portal Application Module
build variant: default
output location: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefault
generation folder: C:Documents and Settingsm100236.dtc3 EBC1BF499DA88943638C12CB3AD23D86
plugin start time: 2008-11-11 11:32:54 GMT-05:00 (EST)
Java VM: Java HotSpot(TM) Client VM, 1.5.0_07-b03 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Warning: Package folder "src.api" exists but is empty and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.015 seconds
Preparing data context..
No public part descriptor found for component "webservices_lib" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "sapxmltoolkit" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sapportals.htmlb" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtapi._api" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtpars._htmlb" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtpars._soap" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtapi._test" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "servlet" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "jaxm" (vendor "sap.com"), public part "default", using legacy mode.
No 'default' JDK defined, will use running VM.
Data context preparation finished in 0.032 seconds
Creating Ant build file..
Creating output file: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefaultlogs uild.xml
[Velocity] Error: VM #CreateConfigArchive: error : too few arguments to macro. Wanted 3 got 0
Using macro file: C:Documents and Settingsm100236.dtc3DCssap.com c i pportalapplication\_compgendefaultpublicdefmacros uild.vm
DC specific options:
Portal Application file name: ep_wa.par
Include sources in application: no
Deploy type: online
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Build file creation finished in 0.078 seconds
Starting Ant..
Using build file: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefaultlogs uild.xml
Using build target: build
Using Ant version: 1.6.2
compile:
[echo] Compiling Java sources in src.core
[echo] Starting Java compiler
[echo] Settings:
[echo] debug: on
[echo] optimize: off
[echo] deprecation: default
[echo] verbose: default
[echo] encoding: UTF8
[echo] source: default
[echo] target: default
[echo] source path: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compsrc.core
[echo] class path:
[echo] C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjava oot.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjavaiq-lib.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjava c_sec_wssec_lib.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjavautil.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjavawebservices_lib.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtapi._test\_compgendefaultpublicdefaultlibjavaprttest.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtpars._soap\_compgendefaultpublicdefaultlibjavacom.sap.portal.runtime.application.soap_api.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtpars._soap\_compgendefaultpublicdefaultlibjavacom.sap.portal.runtime.application.soap_core.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtapi._api\_compgendefaultpublicdefaultlibjavaprtapi.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtpars._htmlb\_compgendefaultpublicdefaultlibjavacom.sap.portal.htmlb_api.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comjaxm\_compgendefaultpublicdefaultlibjavajaxm-api.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comjaxm\_compgendefaultpublicdefaultlibjavasaaj-api.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comservlet\_compgendefaultpublicdefaultlibjavaservlet.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comsapxmltoolkit\_compgendefaultpublicdefaultlibjavasapxmltoolkit.jar
[echo] C:Documents and Settingsm100236.dtc3DCssap.comcom.sapportals.htmlb\_compgendefaultpublicdefaultlibjavahtmlb.jar
[echo] output dir: C:Documents and Settingsm100236.dtc3 EBC1BF499DA88943638C12CB3AD23D86classessrc.core
[javac] Compiling 1 source file to C:Documents and Settingsm100236.dtc3 EBC1BF499DA88943638C12CB3AD23D86classessrc.core
[javac] ERROR: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compsrc.corecommylwadisplay.java:23: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier
[javac] ERROR: (try -source 1.4 or lower to use 'enum' as an identifier)
[javac] ERROR: import com.sapportals.htmlb.enum.CellHAlign;
[javac] ERROR: ^
[javac] ERROR: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compsrc.corecommylwadisplay.java:24: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier
[javac] ERROR: (try -source 1.4 or lower to use 'enum' as an identifier)
[javac] ERROR: import com.sapportals.htmlb.enum.DropdownListBoxDesign;
[javac] ERROR: ^
[javac] 2 errors
Error: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefaultlogs uild.xml:104: Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
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:585)
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 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: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)
Ant runtime 0.047 seconds
Ant build finished with ERRORS
Compile failed; see the compiler error output for details.
Error: Build stopped due to an error: Compile failed; see the compiler error output for details.
Build plugin finished at 2008-11-11 11:32:54 GMT-05:00 (EST)
Total build plugin runtime: 0.267 seconds
Build finished with ERRORThanks Harini, That solved my Export error, however I am still having issues withthe Weather Magnet Application. After uploading it and creating a PAR File iView I am getting lots of errors that I can't figure out. (I haven't quite gotten the hang of reading the error logs yet).
#1.5 #C28BB00110020073000004F70015D02200045C10645C2F09#1227125379836#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#m100236#18970##n/a##b52d80f0b67511dd8f12c28bb0011002#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/Server#Java###Exception ID:03:09_19/11/08_0083_9333450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : ep_wa.display
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
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:524)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.myl.wa.display of Portal Component ep_wa.display because: Could not instantiate implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
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.UnsupportedClassVersionError: (com/myl/wa/display) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:224)
at com.sapportals.portal.prt.util.AutoClassLoader.findClassInternal(AutoClassLoader.java:880)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClassLocally(AutoClassLoader.java:1250)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1388)
at com.sapportals.portal.prt.util.AutoClassLoader$2.run(AutoClassLoader.java:1465)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1461)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 30 more
#1.5 #C28BB00110020073000004F90015D02200045C10645C633D#1227125379850#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#m100236#18970##n/a##b52d80f0b67511dd8f12c28bb0011002#SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Java###03:09_19/11/08_0083_9333450
[EXCEPTION]
#1#java.lang.UnsupportedClassVersionError: (com/myl/wa/display) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:224)
at com.sapportals.portal.prt.util.AutoClassLoader.findClassInternal(AutoClassLoader.java:880)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClassLocally(AutoClassLoader.java:1250)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1388)
at com.sapportals.portal.prt.util.AutoClassLoader$2.run(AutoClassLoader.java:1465)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1461)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
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)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
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:524)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #C28BB00110020070000006010015D02200045C1064C8BAFB#1227125386951#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#m100236#18970##n/a##b52d80f0b67511dd8f12c28bb0011002#SAPEngine_Application_Thread[impl:3]_17##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
#1#SOAP Fault Exception [Actor [max-sap55] com.sapportals.portal.prt.service.soap.exception.SoapFaultHandler] : The User Authentification is not correct to access to the Portal Service com.sap.portal.prt.soap.Bridge or the service was not found.
<type>java.lang.IllegalAccessError</type> -
Error while exporting a par file from NWDSVersion: 7.0.19 to portal7.0
Hi,
When i tried to export a par file from NWDS to portal. I am getting the following error. Please can any one help me to trace out this error.
21.08.09 / 15:09] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.FileNotFoundException: http://sgcsapeps:50200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=XXXXX&j_password=YYYYYYt&j_authscheme=default&uidPasswordLogon=Log%20on
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:792)
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 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)
Thanks in Advance.
Regards
BashaHi,
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, -
NWDS 7.0 Error during Quick PAR Upload and while trying Exporting PAR-File
Hello,
I am trying to use the functions "Export as PAR-File" and "Quick PAR Upload" in NWDS 7.0.
Unfortunately I got an error every time when I am trying to use this functions. I am using the package explorer in the Java perspectiv in NWDS for starting this functions. The error tells me the following:
"Unable to connect to the Portal"
"Operation failed: Please make sure the server "XY" is running or check the log (sap-plugin.log) for more detail"
Thats all.
When I am looking in the log-file I can read the following messages:
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: GET_VIEW:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: IS_VIEW_EXISTS:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: SIZE_OF_VIEW:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: READ_ENTRY:ALL]"
LOGIN.ERROR|null|| Login Method=[default] UserID=[user_Admin] IP Address=[192.168.xxx] Reason=[Cannot authenticate the user]
I have tried this with several users and their passwords. All of the users have admin-rights at least in the portal. One of them even in the SDM.
I can sucessfully deploy webdynpros from NWDS into the same Portal with this users.
We are using SAP Logon Tickets and SSO is configured working fine between Portal and backend.
We have imported Key Store File in NWDS unter Window --> Preferences --> Java Development Infrastructure.
And we are not using the NWDI.
Who knows why I cannot even export par-files? Are their any configurations missing?
Best regards,
IrisIt is mentioning about authentication.
check whether you have access to deploy directly or not ? maybe direct deployment into portal disabled .
I think you have to follow the procedure of checkout and activate procedure.
Can you clarify few things
1) Are you using NWDI Based Transports in your landscape?
Login Method=default UserID=user_Admin IP Address=http://192.168.xxx Reason=Cannot authenticate the user
http://192.168.xxx is it your development portal?
Did you clarify with admin people whether direct deployment disabled?
Koti Redd -
Error while exporting PAR file
Hi,
I am getting an error "Build of project failed" while exporting a PAR file to the project folder and it is showing that "The project was not built due to classpath errors (incomplete or involved in cycle)." I am very new to this technology, so please help me in this.Check if the required JAR files under /dist/lib or /dist/private/lib are added in the project structure.
Refer http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d58bb490-0201-0010-64a1-9e5165e5dbac?QuickLink=index&overridelayout=true
~ Dhanz -
Error on exporting a PAR file to portal
I am trying to export a portal application (java code) to PAR file in the NWDS. i am getting the following error;-
<b>PAR Upload failed:Please make sure that portal server is running.
HTTPS is not supported ,please ensure the server is not using HTTPS</b>
The PAR file is to be uploaded to the portal later.
Note:The portal application has compiled successfully.
Is it not supported in this version of the portal?
Please help
Regards
Navneet
Message was edited by:
Navneet GiriaHello Navneet,
Check these threads:
Problems deploying par file via Netweaver Developer Studio
Unable to Upload portal application from NWDS
If this does not help, try deploying from
System Administration-> Support-> Portal Runtime-> Administration Console.
At the option "Please specify a Portal Archive file (PAR) and press "upload" to store it into the PCD." Deploy your par file by giving the path.
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers -
Regarding exporting a Par file from NWDS.
HII...
I have a problem regarding the exporting a par file from NWDS. when i created any projectt my project is succesfully deployed but . it is not visible when i create any iview from par.
pls check this steps , perhaps i am missing any steps , or i m deploying it in wrong manner.
suppose i have to change the masthead brand image.
steps r .
1. download a par file.
2. do the changes in headerview.jsp file.
3. add the image in img folder.
4. add the jar file in lib folder.
5. save and quick par upload.
MY server settings r correct . but i dont know why my project is not in the list.
thanks..Hi,
You will have the par file directly under your project folder where also your .classpath and .project files exist. Also check them from windows explorer.
Without a par file, you cannot deploy your project on the server.
To create par file check this:
http://help.sap.com/saphelp_nw70/helpdata/EN/96/df7f409cd50a1ae10000000a155106/frameset.htm
Once you export the par file, you should see this par directly under your project folder.
If this is not there, then it is a problem in your NWDS.
Let me know the version of NWDS you are using.
Regards,
Praveen Gudapati -
Unable to find par file in the list in EP 7.0 when i export form NWDS
Hi All,
Can any one help me regarding that.
i upload one par file through NWDS by using export.after that when i going to create one iview from par.in the PAR list my par file is not display.
but the par file is avilable is the PCD.
can any one suggest me regarding this issue.
thanks & regards
chitta ranjan bej
portal devloper
EDS-GemsHi,
go to System Administration -->Support --> Browse Deployment and browse to the directory ROOT/WEB-INF/deployment/temp
locate the corresponding par file and Download it to your local system. If you observe the file extension, it is "bak", because SAP Portal renames the archives after it deployes the par so that it will not deploy it again. Remove the file extension .bak and rename according to the naming standards of your organization. I would recommend you to use the same naming of the file, remove "sap" and use your own company name, like com.mycompany.portal.navigation.masthead.par.
After this, you can import this par file in NWDS (Netweaver Developer Studio) by selecting File --> Import.
A word of caution, the importing does not import the jar files in the private/lib folder of the project structure. So, copy them manually to the new project you have created.
When you see the project structure, you can find the related file in dist --> PORTAL-INF -->jsp -->
You can change this file according to your needs and deploy it back to the portal.
create the ivew from par
hope it works for you
gunjan -
How to append date in YYYYMMDD format in .par file for export
Hi,
Database Version: 10.2.0.4
OS: AIX
I have an export script which reads .par file and executes "exp" to export schema.
I would like to add date in "YYYYMMDD" format for the dump file like this
owner=scott file=/exports/scott_${`date '+%Y%m%d'`}.dmp feedback=10000
I know above statement will not help, but I am giving it as example on what I want to achieve.
I want the file name as =/exports/scott_20120712.dmp
Thanks
Sarayuuser13312943 wrote:
Hi,
Database Version: 10.2.0.4
OS: AIX
I have an export script which reads .par file and executes "exp" to export schema.
I would like to add date in "YYYYMMDD" format for the dump file like this
owner=scott file=/exports/scott_${`date '+%Y%m%d'`}.dmp feedback=10000bcm@bcm-laptop:~$ export YYYYMMDD=`date '+%Y%m%d'`
bcm@bcm-laptop:~$ echo $YYYYMMDD
20120712
bcm@bcm-laptop:~$
owner=scott file=/exports/scott_${YYYYMMDD}.dmp feedback=10000 -
Exporting a .par file from portal
hello, help me please
I have a standard iview in a business package employee self-service
I need find the .par file to download this iview then import with Netweaver developer studio, I think is not created, I try in
"System Administration"==>"Support"==>"Support Desk"==>"Portal Runtime"==>"Browse deployment"==>"ROOT"==>"WEB-INF"==>"deployment"==>"pcd
but is not in there.
anyone can help me please.
Thanks.Hi,
ESS content is developped in PAR... Basically these are more of Development Components(DCs)... In order to customize them , you should have NWDI...
Below blog explains how to customize....
ESS/MSS Customization Make it Simple
If in case your customisation is minor like customizing the text, hiding/un hiding the links, then
go to the location whrere your ESS iViews are stored, click on Preview.
It will open the iView.
Then do a (Cntrl+Right Click) on the link/image which you want to hide/unhide.... u will get the options...
Regards,
Srinivas. -
Error deploying PAR file from Developer Studio (NW04)
Hello,
i've got a problem while trying to deploy a PAR file from NW Developer Studio.
The PAR Export function says
"Unable to connect to the Portal",
the portal itself gives the following response:
"ERROR: Upload failed - exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Invalid content type submitted - no multipart data"
Deploying the PAR file manually using the Administration Console (system administration tab) of the portal works fine, but why doesn't the PAR Export function of NWDS?
Thanks in advance for any help!
Regards,
JörgHi Jörg,
as a general advise, use the NWDS version corresponding to the Servers version, so in this case, upgrade (or better: install new) NWDS 2.0.14. The main reason is WebDynpro compatibility, but the deploy mechanism may need this too.
At least, give it a try and report if you have success (or not).
Hope it helps
Detlev -
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. -
Error while uploading a PAR file
Hi All,
I'm having an error when i try to upload a PAR file from Portal>Java Development>Development
The strange is that i am having the error in QA environment, in development environment i can upload it without any problem, and also it is not the first time that I upload a PAR to QA.
I hope someone can help me, i really don't know what to do...
Regards,
Nicolás.-
Here is the error:
May 8, 2009 11:46:34 AM # Client_Thread_17 Fatal Application upload failed: InvoiceTool.par
com.sapportals.portal.prt.runtime.PortalException: archive: InvoiceTool.par
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:309)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:700)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:396)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:285)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:115)
at java.lang.reflect.Method.invoke(Native Method)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:250)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:351)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:628)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:555)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:121)
at com.sapportals.portal.prt.deployment.ArchiveIntrospector.getDeploymentDescriptor(ArchiveIntrospector.java:54)
at com.sapportals.portal.prt.deployment.DeploymentManager.getDeploymentDescriptor(DeploymentManager.java:942)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:273)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:700)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:396)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:285)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:115)
at java.lang.reflect.Method.invoke(Native Method)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:250)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:351)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:628)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:555)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)Hi Nicolas,
In you development server,
1. Create a new iview (With new from PAR file option). The iView wizard gives you the option to choose the PAR file available on your development portal.
2. Now create a Transport Package. Navigate to System Administration - Transport - Export.
Navigate to your Transport Folder in PCD.
Now Create a new Transport Package and add the iView to the package (iView created earlier from PAR file).
3. Now go to Transport Package properties and Make sure, you are changing the property id prefix to * .
This will include every object associated with the iView while manually exporting.
4. Now click on the EXPORT button. This will export the required PAR file with. This in turn create an EPA file. save it to your desktop.
5. Now in Quality server,
Do the manual Import.
Navigate to System Administration - Transport - Import.
Browse the EPA file on your desktop and say IMPORT.
This way, you will be able to get your PAR file as well as your required portal object (here the iView) in quality server.
Hope this helps,
Cheers!!!!!
Biroj...
Points for useful answer will be appreciated.
Edited by: Biroj Patro on May 12, 2009 8:40 PM -
Hello,
I'm attempting to change a couple of the images on the log on page by adding them into the PAR file using a project in NWDS. After making the changes, which I believe I have done correctly, in order to create the new par file I've used the export PAR file option. I then rename the new file to our our existing filename and pass it to our BASIS team who have tried to deploy it using SDM. For some reason it won't load. (I have manually added the 2 JAR files so that is not the problem). Any ideas about what is wrong ? Any help would be appreciated.
Much obliged,
Phil.Hello
Check while creating the PAR file again after uploading the images,
is the par file created correctly or not?
is there any custom jar files added previously when the login par has created.
make sure all jar files added in PAR file while building PAR.
If PAR file generated successfully then try to deploy from System Admin as mentioned by above reply.
Cheers
Chinmaya
reward for Helpful answers. -
Hello All,
I am a newbie to SAP Netweaver platform. I am trying to create a webservice to be deployed to Enterprise Portal to be called from a .NET application. I have SAP NetWeaver Developer Studio and SAP NetWeaver 7.1 Composition Environment SP03 PAT0000 on my laptop.
I have used the Enterprise Portal Application perspective to create the project to create a portal application. I have written the code necessary ( not functional just to test) andI am trying to see how to deploy it toEnterprise Portal. Going thru the forums and docs I see the way to do this would be to generate a par file and deploy to the server. The common options I came across are to right click on the project and do "Quick Par Upload". The problem is that when I right click on the project in the studio I do not see this option. I am at a total loss at this point to figure out why.
The other option I saw was to do Right click on project and then do a export of type par. Again I do not see this option but only see SAP WAR and SAP EAR - nothing which says par.
Reading thru the forums I saw suggestions which says where I should go to Window->Preferences to set up J2EE servers. Again I do not see that option. IS there something obvious that I am missing?
Help would be greatly appreciated.
Thanks,
SujithHi Sujith,
Please Check these,
To deploy a par file into potal you have to select "Export" option when u right click on the project
Your project should be in Enterprise Portal Perspective
to do this ,
Click on the icon with + symbol near by Package explorer
Select other -> choose EP -> hit OK
Now you can see the EP icon under the icon with + symbol. click that
Now you are in EP perspective
Follow these steps to upload par into portal:
Rightclick ur project -> Export ->Next -> Select ur project ->
configure server settings -> add
Give these details:
Alias: AnyName (Eg: DEV)
Host: ur portral server name (eg: mydevserver u can pick this from portal url path)
Port: portal sever port (ex:50000)
Login:portal user name
Description: (optional)
click ok and enter the password
Hit Enter.
Now ur par file uploaded into portal
Check:
You can check this in ur portal system admin --> support -> portal deployemenyt -> serch for tur project name
Regards,
Ramganesan K
Keane Inc
Maybe you are looking for
-
Is there a workaround for moving. videofiles to Sansa Fuze
Hi all I have bought a Sansa fuze 4 gb to my wife as a christmas gift. Musik and photo are Ok to just drag and drop. But videofiles needs to be converted in order to be loaded at the player. And Sansa has its converter just for windows. Is there a wa
-
i need help and i have the new itunes thing ready to be installed but it just doesn't install. it says that it encounters problems so it stops. what can i do?'
-
I Want To Change My Payment Due Date
Change Payment DateFrom: szygw9To: ATTCustomerCareSent: 07-08-2015 7:15:33 AMRead: Not Yet ReadI want to change my payment DUE date to the first week of the month, preferrably to the 1st day of every month! Because AT&T changed my payment DUE date t
-
OWSM: problem with content routing
Hi, I am working on OWSM and i have registerd a service on owsm and tested it through it. it works fine. But the problem is when i click on content routing it gives me this error "The following exception occurred when processing the JSP: Could not co
-
Hello. I am a relati'vely Spanish new user of Creative. But I fall in love the quality-price that I obtained with the audio one of my PC with SBS 580. Now I buy a Creative ZEN 4GB. Despite I want to open this post, stops of some form, between all to