SDM deploy not needed'

[Former Member]

Hi all,

We have configured in NWDI two tracks: in the first one we have development as runtime system and in the second one we have consolidation and production as runtime systems.

The components were deployed in the three environments through NWDI.

After some changes, we transported the code from one track to another without problem. Currently, the code is in development and qa servers and we are ready to move it to production. But when we try to transport it to production, the import finishes in seconds and the changes are not on the server.

The log says:

20090409015934 Info :Starting Step SDM-deploy at 2009-04-09 01:59:34.0666 +1:00

20090409015934 Info :empty list of archives for deployment: nothing done

20090409015934 Info :Step SDM-deploy ended with result 'not needed' at 2009-04-09 01:59:34.0666 +1:00

We had had the same problem transporting to QA. In that moment, we had QA configured as test runtime system. We found that changing to consolidation (before assembly) the problem was resolved. We did that and it worked.

Do you have any suggestion about what we could do in production?

In production we made the following tests:

1. we added to queue the component from history and imported it again but we had the same behavior.

2. We checked the track configuration as well. The

Thanks in advance,

Paula

[Former Member · Accepted solution]

hi,

I am working on SAP ECO and we had the same problems with deployment to production. The problem was based at the assembly step.

NWDI tells you only to assemble the SHRWEB component but you also have to assemble the CUSTPRJ Component again. Only when you assemble CUSTPRJ again, a new EAR file is created and deployed successfully to production environment.

Regards

Michael

[Former Member · Accepted solution]

Hi Michael,

thank you! It worked!

[Former Member]

Hi Paula,

I guess you are doing this first time into this environment. It looks like you missed importing some deltas from QA that require the original code base to work, and this original import was not executed. Please see there are any activities left open and which was not imported.

Thanks

Krish

[Former Member]

Hi Anil,

We are working on SAP E-Commerce.

We imported the dependencies also. We use the same procedure in the three environments. We have this problem only in production.

Thanks in advance.

[mahendran_balasubramani3]

Hi paula,

have you checked the Production phase in the CBS? is this the first time you are moving the DCs to production?

If so, you just create the SCA file once again from the first track and then check wheter all the DCs are precsented in the SCA file or not. and then you impot the SCA file to the second track.

Or, if you are not moving for the first time to the Production environment, once again you reimport the SCA.

[Former Member]

Hi Paula,

In general its not the recommended way to go for different tracks. Why cant we define all the systems in single track. even we can work with different tracks but these kind of problems where no one faces will rises.

The log says:

20090409015934 Info :Starting Step SDM-deploy at 2009-04-09 01:59:34.0666 +1:00

20090409015934 Info :empty list of archives for deployment: nothing done

20090409015934 Info :Step SDM-deploy ended with result 'not needed' at 2009-04-09 01:59:34.0666 +1:00

this warning clearly mentioning that empty list of archive for deployment means the file which you have deployed is not containing the source. First we need to import the dependedt SCA files and after that we need to import the required source related SCA files.

do we know on which development you are working on(like ESS or E-Commerce).

Regards,

Anil.