cancel
Showing results for 
Search instead for 
Did you mean: 

SDM doesn't deploy

Former Member
0 Kudos

Hi everybody,

I'm having trouble while deploying an SDA file through NW Developer Studio.

I can deploy this file via SDM (Remote Gui) but I cannot via NWDS.

Basically, when deployment is triggered from NWDS, I'm prompted for credentials and I then get the following sequence of messages:

- Start deployment

- Created a temporary copy

- Additional log info about the deployment

- Finished Deployment

---> Result = successfully deployed

However my application hasn't been deployed and when I check SDM log file (/user/sap/.../program/log/sdmlogxxx.log) there's no entry for the deployment I initiated.

Any clue?

Thanks,

Marco

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member185029
Active Contributor
0 Kudos

Hi,

Check your J2EE engine entry in NWDS.

If the status is success, then it should deploy your application.

Ashu

Former Member
0 Kudos

Hello,

J2EE engine has been configured correctly, SDM, dispatcher and server0 is green, I can restart J2EE engine from within NWDS.

As I said before, the message I get when I deploy is "success"...I know it's weird....

Marco

former_member185029
Active Contributor
0 Kudos

Hi,

May I know what type of application you are trying to deply?

Have to ever tried to launch the application through NWDS?

What do you see when you run ur application after deploying?

Ashu

Former Member
0 Kudos

It's a library which contains a JAAS login module.

After the deployment through SDM (Remote Gui) I have to restart the box.

Cheers

former_member185029
Active Contributor
0 Kudos

So is the problem sorted or still persists?

Ashu

Former Member
0 Kudos

It's still there.

Deployment through SDM Remote Gui is just a workaround.

Former Member
0 Kudos

Hi all,

the picture is slightly clearer now.

From NW Developer Studio, J2EE perspective, I can disable, enable, restart SDM.

Now suppose I shut it down. Then if I try to deploy it succeeds because deployment onto a different server (which I configured months back).

So this is sort of weird since in some cases it's taken the configuration specified in Windows>Preferences>SAP J2EE Engine whilst, at deployment time, other details are being used.

Any idea as to why?

Thanks,

Marco