NWDS 7.0 does not deploy PAR

Hi experts,
I am trying to directly deploy my PAR file to my portal server. For this I have done the following settings in my NWDS.
1. Window->Preferences->SAP J2EE Engine -> Selected the first radio button i.e installed on a remore host, and gave message server host and message server port.
2. Window->Preferences->SAP Enterprise Portal -> Filled in the necessary details for the alias, host ,port, login.
Now when I try to right click on my project and say "Quick Par Upload" it gives the following error :
"Operation failed: Please make sure the server 'Sandbox' (xyzabc:3941) is running or check the log (sap-plugin.log) for more detail.
I checked and my portal server is up and running.
Please suggest what could be the problem.

Hi Ramganesan,
Window->Preferences->SAP Enterprise Portal -> Filled in the necessary details for the alias, host ,port, login.---- Done
Please check these,
1.Portal Server is up now? --- YES
2.Please check user id and password -
Thats correct
3. Doed that portal user id has required roles and permission to deploy a content? --- How do I check this ?
4. You code is error free? ---- Yes
5. Host Name shuld be portal server host name eg: sapeptraining -
This is correct too
6. Port shud be portal server host.. eg: 50000 -
This is correct too
then Right click on the project -> export -> par file -> next -> check the check bosxes -> finish --- This is where the problem comes. It doesnt prompt for username and/or password, it gives an error

Similar Messages

WebService annoated with @stateless does not deploy in WLS11g

To facilitate the packaging and the deployment of a web service, i annotate it with the @stateless annotation. In this way the web service is packaged with all my others ejb in the same jar. When i deploy the jar that is also packaged in an ear, i have got the following error message :
Unable to find ejb-jar with uri lock-impl in ear at D:\cless2009\CoreBuild\out\lib\WLS_cless\wls_cless.ear
This is part of the code of my web service :
@Stateless
@WebService(name = "ChangeStatus", targetNamespace = "http://cless.gemalto.com/ChangeStatus")
@XmlSeeAlso({
ObjectFactory.class
public class ChangeStatusWS implements ChangeStatus
As you can see, the web service is also annotated with @stateless but without any @Local or @Remote definition.
the jar does not contain any ejb-jar.xml, weblogic-ejb-jar.xml.
Can you tell me what's wrong with this way of doing things ?
Some help would be appreciated. Thanks.

See here under my application.xml
<?xml version="1.0" encoding="ASCII"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5">
<display-name>ClessServer</display-name>
<module>
<ejb>util.jar</ejb>
</module>
<module>
<ejb>repository-impl.jar</ejb>
</module>
<module>
<ejb>workflow-impl.jar</ejb>
</module>
<module>
<ejb>swift-listener.jar</ejb>
</module>
<module>
<ejb>counters-impl.jar</ejb>
</module>
<module>
<ejb>perso-impl.jar</ejb>
</module>
<module>
<ejb>serviceDelivery-impl.jar</ejb>
</module>
<module>
<ejb>lock-impl.jar</ejb>
</module>
<module>
<ejb>deletion-impl.jar</ejb>
</module>
<module>
<ejb>customerCare-impl.jar</ejb>
</module>
</application>
and my weblogic-application.xml :
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd">

<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
</wls:weblogic-application>
The lock-impl.jar is in my ear at the root of the ear file.
Edited by: fmosse on 11 août 2009 04:38

BPEL plugin for Eclipse does not deploy ?

As far as I heard there is a BPEL plugin for Eclipse.
Is this correct ? Where do I get this plugin?
Is this true that I can develop but not deploy code
with this plugin?

So what is correct here. All of the tutorials and quick guides are all using Eclipse. I am trying to test 10.1.3 SOA version as I am currently on 10.1.2.0 w/ JDev being my designer.
J-Dev BPEL plugin changed quite a bit, so I wanted to RTFM but they are all in Eclipse.
Like these for instance
http://www.oracle.com/technology/products/ias/bpel/pdf/orabpel-QuickStart.pdf
http://www.oracle.com/technology/products/ias/bpel/pdf/orabpel-Tutorial1-HelloWorldTutorial.pdf
So whats the dill pickles?

EJBTutorial application does not deploy

Hello
I used Workshop for Weblogic 9.2(on Windows) to go through the steps to create the EJB application which comes as part of the tutorial(Visit Bean). The tutorial uses Beehive controls to build the app. After building the app, i created an EAR file via the workshop Export option to be able to deploy it on a WL server running on Linux.
On the Linux system, i first created a regular WL domain and then extended the domain to include the Beehive template. When i attempt to deploy the application EAR that was generated using Workshop, i get the following exception
javax.enterprise.deploy.model.exceptions.DDBeanCreateException: [J2EE Deployment SPI:260142]The descriptor at 'META-INF/annotation-manifest.xml' in module 'VisitWebTest.war' is not recognized, and could not be parsed
Any clues as to why this might be happening?
Thanks
Ramdas

Raj,
I was able to create a regular WLS domain and then extend it to include the workshop template. But the same error persists. This time I imported the pre-created EJB Tutorial zip file into my Workshop on windows and exported it to a EAR. I used this EAR to deploy it to the domain on Linux. When i attempt to activate the deployment changes, this is what i get:
An error occurred during activation of changes, please see the log for details.
Message icon - Error Exception preparing module: EJBModule(VisitEJBProject.jar) Unable to deploy EJB: VisitEJBProject.jar from VisitEJBProject.jar: There are 1 nested errors: weblogic.ejb.container.compliance.ComplianceException: In EJB VisitBean, there is an ejbPostCreate method ejbPostCreate(java.lang.Integer) that has no matching ejbCreate method. at weblogic.ejb.container.compliance.EntityBeanClassChecker.doCheckCreatesMatchPostCreates(EntityBeanClassChecker.java:117) at weblogic.ejb.container.compliance.EJB20EntityBeanClassChecker.checkCreatesMatchPostCreates(EJB20EntityBeanClassChecker.java:68) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object
I checked the VisitBean code and it did not have an ejbPostCreate(java.lang.Integer) method.
-Ramdas

Dashcode widget works in dashcode but does not deploy correctly n dashboard

My question is exactly as stated in the subject line. I recently was working on my first widget and was creating an RSS feed from AppleInsider (I know one already exists but I want one that I made) in Dashcode in XCode 3. Everything works perfectly fine in Dashcode and nothing is wrong when I runt the debugger but when I deploy my widget in Dashboard all I see is the normal widget minus the info button and rss feed and it is blank where the rss feed would normally be seen. All I can do is move the widget around. I have tried saving the widget and then installing it in my dashboard and every other possible combination and nothing seems to work. Any information at all would be greatly appreciated. Thanks a million!!

If I remember well, I think that there is a wrongly defined key (or totally undefined) in Info.plist that it required for the Widget to operate correctly. Check for the AllowNetWorkAccess key.
Also, you should check the log files for possible error messages.
Mihalis.

Unable to load the EJB module. DeploymentContext does not contain any EJB.

I'm writing an enterprise application to familiarize myself with Glassfish 3.1.2 and EJB 3.1. I've created several local, stateless beans, and injected one into a JSF managed bean. The ejb and web modules compile fine, but when I launch the application with Glassfish I get the following startup error and the application does not deploy. I don't understand what it means, can someone ellaborate?
SEVERE: Exception while invoking class org.glassfish.ejb.startup.EjbDeployer prepare method
SEVERE: Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
SEVERE: Exception while preparing the app
SEVERE: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
org.glassfish.deployment.common.DeploymentException: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
     at org.glassfish.javaee.full.deployment.EarDeployer.prepare(EarDeployer.java:166)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
     at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
     at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
     at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
     at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
     at java.lang.Thread.run(Thread.java:722)

My guess is that you deployed an ejb without bean in it. when you have an ejb module, be sure you have at least one bean present.
Are you sure you have implementend some beans? Or did you do this only in the web module?
Try adding an @Stateless bean doing nothing in you ejb module, redeploy and let me know if that works

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

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

Deployed KM Scheduler Task Does Not Appear in Global Services / Scheduler T

Hi All,
I've deployed a portal service and a KM scheduler task in the same DC but cannot see the scheduler task listed under System Admin -> System Config -> Knowledge Management -> Content Management -> Global Services -> Scheduler Tasks.
The service works correctly and performs its periodic processing once on initialisation of the service, and I can see the resulting log statements to make sure it has worked.
Both the service and the scheduler task are packed inside the same DC, which builds and deploys without any errors.
There are no errors in the log regarding the deployment of the DC, or the scheduler task.
There is a log statement about registering the classloader for the DC, which I assume is the statement in the IRFServiceWrapper init() that goes:
CrtClassLoaderRegistry.addClassLoader(this.getKey(), this.getClass().getClassLoader());
But I still dont see the task listed in Global Services -> Scheduler Tasks.
Does anyone know what might be causing this or how to diagnose the problem further?
Cheers,
Steve

Hi Srini,
No it doesn't it just has the run method which is generated automatically.
I have created a local Portal Application project, which is not in a DC, and this also does not have a default constructor ether but appears in the Scheduler Tasks list as soon as it is deployed.
I also tried to create a Portal Applicaiton DC and Portal Applicaiton (Packaged as SDA) DC and despite the scheduler task being the same, both the DC tasks do not appear in the Scheduler Tasks.
The only one I can get to work is the local Portal Application project. This is no use as we cant store this in DTR (unless someone can explain how to do this???).
The Portal Application project packages up the RF Framework JARS inside its PAR file, but the DC and SDA projects dont, so I tried including them via an Assembly Public Part to an External Library DC, which does include the JARs in the deployment files but they still dont appear in the Scheduler Tasks.
Has anyone out there got a working Scheduler Task in a Portal Application DC?
Cheers,
Steve

NWDS - Error deploying .par file to portal (EP 7)

I am unable to deploy a par file to our portal (EP7 SP12) using NWDS (7.0.06).
I can use the Administration Console to upload par files, but when using the deployment option in NWDS it gives me the following error message:
Operation failed: Please make sure the server 'ALIAS' (SERVER:PORT) is running or check the log (sap-plugin.log) for more detail.
My user id has the "super_admin_role", the "ContentManager" role, and the "Administrator" role assigned.
The log file shows that the upload is getting an HTML 401 error (Unauthorized), but if I paste the link below into my web browser, it takes me to the file upload page.
sap-plugin.log
[04.02.08 / 15:13] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 401 for URL: http://SERVER:PORT/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=***********&j_password=********&j_authscheme=default&uidPasswordLogon=Log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:519)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
     at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

Dhruv...
Thanks for your response. I checked the settings for the Server Message Port. I have the default values enabled. "SAP J2EE engine is installed on remote host" is selected with "Message Server Host" set to "localhost" and the "Message Server Port" set to 3601.
When I change the Message Server Port to 3901, I get an additional error regarding HTTPS protocal not being supported. When I change the proxy settings, I still get the same error message that I was receiving before.
I have verified that my account is not locked, and I have already re-installed NWDS twice, which did not fix the problem.
Thanks...
Bill

Error while deploying BPM : DC bpm_0/bl/ddic does not contain any archives for deployment

Hi All,
I'm using SAP PO 7.31 single stack. I've created a simple BPM in NWDS. I'm able to successfuly build the BPM which I created but when I "Deploy" it throws the below error.
DC bpm_0/bl/caf/metadata does not contain any archives for deployment
DC bpm_0/bl/ddic does not contain any archives for deployment
DC bpm_0/bl/caf/dictionary does not contain any archives for deployment
Not sure what/where to check and fix the issue. Can you please help me in fixing the issue?
Thanks
Raj.

Dear Raj,
I am looking into this.
In the meantime can you try this also.
xxx/pr/pm: Deployment error,&nbsp;GD&nbsp;|&nbsp;ABAP,&nbsp;SAP,&nbsp;benX AG,&nbsp;benXBrain,&a…
Thanks & Regards,
Patralekha

Deployed PAR file webservices are not displayed in SOAP admin

Hi,
we were facing the problem with customized PAR file deployment and
associated webservices.We have deployed the the PAR file on two
different versions of EP as given below.
EP6.0(WAS620)-SP2(J2EE and Portal versions are identical)
EP6.0(WAS640)-SP13(J2EE and Portal versions are identical)
The problem was the webservices has been shown in the case of
EP6.0(WAS620)-SP2 under SOAP Administration and not shown in case
of EP6.0(WAS640)-SP13.Is there any specific version made PAR files are
required for each of above portal versions or any other way to
check the webservcies in EP6.0(SP13).
Kindly help us to resolve this issue.

Hi Swetha ,
in Bypass scenario if you are fetching a flat file from source to target some time you are not able to view the file in payload .However it does not make any difference as you are simply tunnling the file not doing any transformation with it .
If it is a flat file in sender CC just make 1 .file type as bin or 2 . file type as text and encoding as UTF-8 and then check you can view the file content or not .check with both bin and text ( one by one ) .might be you will able to view payload in MONI with any one of that setting in sender CC .
Regards,
Saurabh

Com.sap.portal.admin.acleditor.par not deployed properly during ep install

Hi,
We are installing ep on top of a java add-in.
The version of ep is sp3. After the installation when i check the pcd folder coom.portal.admin.acleditor.par is not deployed.
Log has Fatal applciation upload failed. and there is some error which says xml declaration is not allowd here.
When i try to access the portal page its loading for a long time and giveing page cannot be displayed.
Portal analyzer gives clean results except for this par file.
Please help.
Regards
Bharathwaj

Hi Bharathwaj,
> Do you think the upgradation of the this
> to SP13 will solve the issue. ??
No, I wouldn't advise to upgrade a really broken installation. You may give it a try, but the success probability I wouldn't expect as too high...
> Does a EP upgrade create a clean install again..
> or just add a few more files ???
It deploys new portal applications and/or redeploys existing ones which have changes (bug fixed). So theoratically if a PAR is broken, a new one may be fixed; on the other hand, the installation seems to be buggy in it's kernel, in such a case, the root cause seems to be something else than "only" one failed PAR upload.
> Is there any log file which says what are the steps
> it had skipped..
Beneath the default.trc to check for the portal runtime, SAPInst has it's own logs under the temporary inst dir.
Hope it helps
Detlev

NWDS 7 does not compile JSPs

I have recently downloaded NWDS tool that comes with the NW04s trial version (NWDS version 7).
When I create portal components (par files), NWDS does not compile the java files. It creates a par file even with errors in Java. Is this a new "feature" of NWDS? am I missing anything?

Create DC for the JSP also. It will work.

NWDS 7.0 does not deploy PAR

Similar Messages

Maybe you are looking for