Deployment getting aborted on J2EE Engine from NWDS

Question

Hi,
While i am trying to deploy the Java WebDynPro code on J2EE Engine its giving me the following error.
Apr 9, 2008 10:24:53 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sghrdpr7
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/NUZHAT1/LOCALS1/Temp/temp21573sap.comfixedtoolbar.ear
Deployment exception : Server sghrdpr7 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sghrdpr7 at port 50118: sghrdpr7
Inner exception was :
Server sghrdpr7 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sghrdpr7 at port 50118: sghrdpr7
The deployment is getting aborted.
I have tried telnet for the port number from my end and that is successfull.
Now i dont where the problem is????????
Please help urgently

Answer 1

Hi,
Have you checked whether the deployment with the SDM directly works or not ? (not through NWDI).
Also, for the SDM deployment to function correctly, make sure of the following :
Please make sure to set :                                                                               
- the P4 host to localhost in the Secure Store (setting localhost is a workaround if you have multiple hostnames (virtual/physical)
- the secure store should have the correct password for the j2ee_admin(in case of dual stack) or administrator(in case of java only) as SDM server takes the password from secure store for the login to j2ee engine as administrator which is required for the deployment.
- SAPLOCALHOST, SAPGLOBALHOST, and SAPGLOBALHOSTFULL value in the SCS &
JC profiles must point to the desired hostname/IP. If they don't exist 
please create and set accordingly.        
- in the sdmrepository.sdc file, the following                         
values are set expected with expected host :                           
      <mshost>                                                         
        *hostname**                                                  
     </mshost>                                                         
     <msport>                                                          
        **port -can be found in dev_ms file*                         
     </msport>                                                                               
Please restart the cluster.                                                                               
Try to deploy using SDM without the workaround.                                                                               
If the deployment fails, please paste the exception/error from the lastest sdm log from SDM\program\log directory and corresponding exception from the latest defaultrace file from server0\log directory.
Hope the above helps.
Regards,
Snehal