activation, on wich server it deploys now?

[Former Member]

my setup:

nwdi development : -> sap java dev server (no auto deploy)

nwdi consolidation: -> sap java dev server (no auto deploy)

nwdi test -> sap java quality server (no auto deploy)

now.. when i activate.. does it normaly have to deploy to the sap java system that is linked to the nwdi development ? or at least show me some components queueing in cms development tab?

What happens: nothing is deployed on sap java dev system.. , no components have com into the cms development tab.

when i release! they come into the cms consolidation tab and if i import. they deploy.

what am i missing here?

Edited by: bjorn corluy on Nov 21, 2008 11:07 AM

[Former Member · Accepted solution]

Hi,

When you activate and release your activity it gets deployed in to your developement system and will be ready to be imported into consolidation system.

This is the way it works. After activating and releasing the activity you can test in development system.

Also when you say no auto deploy, did you check the checkbox disable automatic deployment in the track? If this is checked then only automatic deployment will not happen and you need to manually deploy using the below path.

http;//host:port/TCS/Deployer and provide your buildspace name and submit.

Buildspace name you can check in CBS

ex;<domain>_D_<trackname>

Thanks,

Gopi

[Former Member]

Thanx all.. solved.

[Former Member]

Bjorn,

I recommend you to clear checkbox "Disable automatic deployment" for

nwdi development : -> sap java dev server

nwdi consolidation: -> sap java dev server

This way when activity is released it is centrally built by CBS and deployed on java dev server automatically.

For test, you will need import in the Cons tab, assemble and import to Test.

This setup makes life easier for both developers and admins.

I understand this is what you were asking for.

Regards,

Slava

[snehal_kendre]

HI,

sap java dev server (no auto deploy).

so its not going to deploy automatically.. ..

in cms development tab->deployment check it