4 Replies Latest reply: Jul 22, 2012 1:40 PM by Wilco Menge RSS

WCEM 2.0 deployment error: sap.com/SAP-WEC-ZA

Wilco Menge
Currently Being Moderated

Ladies and Gents,

 

While deploying the WCEM 2.0 components on a developer workplace 7.30 instance I run into the following situation. The following components have deployed without a problem:

MDM_JAVA_API

MDM_CONNECTOR

SAP_WEC_FRW

SAP-WEC

 

The following component contains the zero administration configuration and gives an error when being deployed with the JSPM tool:

SAP-WEC-ZA (2.0.0.1)

 

Deployment finished with error.

AS Java is not running. Check error details and their possible solution and then Resume. Archive with all relevant logs and traces is created in D:\usr\sap\WME\J00\j2ee\JSPM\log\errorReport.zip.

 

When I check the log I see the following entry:

Jul 9, 2012 4:48:52 PM   Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [vmwareinstall:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.0.2.15,port=50004,localport=4024]. Check if the host and port specified are correct and AS Java is up and running.

 

The error is correct, because my engine is running on port 50000 instead of 50004. Any idea where the incorrect port number is coming from? I know the component is optional, but it seems like a good idea to install it.

 

TIA,

 

Wilco

  • Re: WCEM 2.0 deployment error: sap.com/SAP-WEC-ZA
    Patrick Zimmermann
    Currently Being Moderated

    Hello Wilco,

     

    port 50004 is used for deployment, so this information is correct. The deployment of the system template is an offline deployment, means the J2EE has to be shutdown prior to deployment and usually starts up again after deployment. Not knowing how long the startup will take the JSPM tool tries repeatedly to connect and eventually will find the J2EE up and running and can continue with the deployment procedure. For some reasons the J2EE might 'prefer' not to come up.

    E.g. when you activated in a previous step the SAP-WEC-ZA template, and during update something goes wrong. Then the J2EE doesn't get up anymore.

    In this case you might check with the offline config tool to select another system template and try to restart the J2EE manually.

    In some cases it might be necessary to reboot the server.

    To find out why the J2EE doesn't get up the Trouble Shooting Guide provides a very good starting point:

    http://wiki.sdn.sap.com/wiki/display/TechTSG/(JAVA)+Application+Server+Java+Troubleshooting

     

    Best regards

    Patrick

Actions