NWDS deployment error: system not responding

[irijsdijk]

Hello,

I can't deploy EAR files or BPM processes to the PO DEV server. Credentials are OK, systems has been added as AS Java, system is up & running. I'm using PO 7.5 SP07 and NWDS 7.5 SP07.

These are the error:

Status ERROR
Plugin : com.sap.ide.tools.services
code=0
Deployment problems


children=[
Status ERROR
Plugin : com.sap.ide.tools.services
code=0
Deployment failed
com.sap.ide.eclipse.deployer.api.APIException: System XXX not responding.
at com.sap.ide.eclipse.deployer.DeployerPlugin.getCurrentServerInfo(DeployerPlugin.java:94)
at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:246)
at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:218)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:255)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
]

The same NWDS installation with a different PO 7.5 environment works fine. Also collegues don't have any trouble deploying BPM processes.

Any ideas what might cause this?

[former_member189220]

Would you please re-add the SAP AS Java system (target deployment RTS), when you navigate in the NWDS -> Window -> Show View -> Other, and select the Management Console. Right click on SAP Systems, add system, and enter the hostname and instance number. (The instance number is very important if you would like to deploy to a particular instance). "The same NWDS installation with a different PO 7.5 environment works fine", this prompts that probably the NWDS might not connect to this particular instance. You might check what kind of services are listening to which port:

1. display of these 2 commands:

netstat -ano

tasklist

2. Match the process name >>> PID >>> IP:port

Yet, I need to elaborate. If indeed, the target deployment is an AS Java Cluster architecture as it is explained here:

https://help.sap.com/saphelp_nw73ehp1/helpdata/en/4b/1b7a48eb2770d3e10000000a42189b/frameset.htm

then all the Instances and Java Processes are using the same database. Then it does not matter to which node you do deploy, because the synchronization process will automatically distribute the newly deployed archive to all the instances. Most probably, either incorrect host and/or instance number are not configured or there is a kind of a network problem (if the AS Java is added in the MMC perspective and you might see it this deployment event is very strange).

[former_member191044]

Are your colleagues deploying on the same exact server? Is it a cluster and maybe your config tries to deploy onto a node where some services are not started. You could try to let the whole dev restart and try again after.

/Tobias

[former_member189220]

By the way, in my previous comment I have neglected one very important fact: "I'm using PO 7.5 SP07 and NWDS 7.5 SP07."

This means that the P4 default port is 5xx04 not 5xx18!

Please cross check the configuration settings to the P4 port in the instance profiles in the profile folder on the AS Java Server. The path of AS Java profile folder is:

\usr\sap\<SID>\SYS\profile

[irijsdijk]

I keep seeing this at the SAP management console:

[former_member189220]

One might not achieve deployment from the NWDS to AS Java when the deployment port of the latter is not accessible.

Please cross check whether this port is open and active in SAP MMC console on the AS Java itself.

If is open there, then please contact the network administrators. Most probably this port is not open in a firewall or other network device.

[irijsdijk]

Yes. It is a cluster indeed. Is there a way to force deployment on a specific node?

[former_member189220]

I believe with "node" you do mean instance. You just need to configure this instance number when you add the SAP AS Java system in the MMC perspective in the NWDS. Then the deployment will be routed to this instance.

Yet, if it is indeed a cluster - it does not matter to which instance you do the deployment because the database is only one (for all the instances).