Error deploying custom EAR file from NWDS to Portal 7.4

[SandipAgarwalla]

Hi All

I am trying to deploy a custom EAR file to our Portal 7.4 SP7 system. The EAR file was a PAR file running correctly on the old system EP 7.0

I migrated it to PAR using the support tool, and while deploying it on the server using NWDS 7.31, I am getting errors

Exception occurred during the 'Deploy' operation.
Cause:Cannot obtain deployment client
Exception:
com.sap.ide.eclipse.deployer.api.APIException: Could not retrieve deployment system configuration for EPX. Please check if the system is running.

Yesterday only we change the SDEFAULT parameter to DEFAULT and rebooted the EP servers couple of times. The server does not ask for OS level User ID anymore, but I cant seem to deploy ears from NWDS

Any help.

Thanks

Sandip

[hugo_amo · Accepted solution]

Hi Sandip,

change service/protectedwebmethods = DEFAULT and retry.

Regards,

Hugo

[SandipAgarwalla · Accepted solution]

Hi Hugo

Thanks for looking into this. I have already changed the parameter to DEFAULT, and rebooted the server.

Thanks

Sandip

[SandipAgarwalla · Accepted solution]

Ok, the NWDS is really working weird here. I shut it down couple of times, and tried deploying - it allowed..

I think the NWDS version is buggy..Once in a while it still ask for OS user ID & Password though I have changed the profile param.

Ok, now when  I try to deploy I get a different error..Here is the exception

  Description:
  1. Exception during generating components of [sap.com/com.us.<vendor>.portal.navigation.masthead] application in [servlet_jsp] container.
  -> zip entry name contained non-utf8 chars, try system property sun.zip.altEncoding


Exception:
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_com.us.fujitsu.fnc.portal.navigation.masthead] failed
  at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
  at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
  at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
  at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:278)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: java.lang.IllegalArgumentException: zip entry name contained non-utf8 chars, try system property sun.zip.altEncoding
  at java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:303)
  at java.util.zip.ZipInputStream.getFileName(ZipInputStream.java:436)
  at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
  at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:82)
  at com.sap.portal.prt.core.bundle.ResourceBundleExtractor.iterate(ResourceBundleExtractor.java:167)
  at com.sap.portal.prt.core.bundle.ResourceBundleExtractor.handleEvent(ResourceBundleExtractor.java:87)
  at com.sap.portal.prt.deployment.DeploymentManager.distributeEvent(DeploymentManager.java:544)

To me it looks like something to do with JDK or JVM being used

For your kind attention please.

Regards

Sandip

[ErvinSzolke · Accepted solution]

Hi Sandip,

the only thing crosses my mind that if you use NWDS 731 and deploy to 740 then NWDS has to be 5 SPs higher than the SP of your 740 engine.

See 1791485 - NWDS 7.3 EHP1 as development environment for SAP NetWeaver 7.4

Regarding JDK

Also, are you using sapvm, or other jdk from other vendors? Perhaps it is worth to try other jdks.

Regarding passwords:

it is worth to wipe out the secure store from the preferences of your NWDS, restart NWDS and then try again (it should ask for credentials only once, make sure you enter properly, and that you leave the checkbox checked so the password can be properly cached by the nwds).

Regarding the error message itself:

Did you google for "zip entry name contained non-utf8 chars, try system property sun.zip.altEncoding" ?

Perhaps that also gives some idea too.

Best Regards,

Ervin

[dror_last · Accepted solution]

During deployment of a Portal Web Module, The Portal extracts the WAR file which resides inside the EAR to look for resource bundle files.

It seems that there is some corruption of the war contained in the EAR file with regards to the entry names inside it. Please inspect the different entry names and try opening it with some standard tool such as winrar.

[SandipAgarwalla · Accepted solution]

Hi Ervin

Thanks for your reply.

The server is at 7.4 SP07, and NWDS is 731 SP13 PL0 ..I cleared the secure store, and all but still the same problem...

Regarding the error, it was actually a PAR file that was converted to EAR using the Portal PAR migration tool.. Not sure what is wrong.

Thanks

Sandip

[SandipAgarwalla · Accepted solution]

Hi Dror

The EAR file is actually a migrated PAR file from the old version. I used the Portal PAR migration tool to convert it to EAR. Now deploying to 7.4 gives this error. The PAR is running fine in the old version.

Regards

Sandip

[dror_last · Accepted solution]

Is it possible of you to provide both the PAR and the migrated EAR?

[SandipAgarwalla · Accepted solution]

Hi Dror

I just emailed you at your sap email id (first.lastname@sap.com)

Thanks for extending your help.

Sandip

[dror_last · Accepted solution]

Hi Sandip,

There was a JAR inside the WAR file that was corrupted and also not possible to open successfully using Winrar.

I copied the original one from the PAR and now the deployment should work.

I have sent you a mail with the corrected EAR file.

Best Regards,

Dror.

[SandipAgarwalla · Accepted solution]

Ervin

I just used a lower version of NWDS, 731 SP12 PL05, even then it asks for the OS logon id. We changed the profile parameter on the server, but still the same issue.

Very strange, unless something else is missing.

Regards

Sandip