Transport shows successful in CMS, but actually it is not!

[Former Member]

Hi,

I am working on a SAP E-Commerce application which has been customized based on the requirements. Recently, I checked out a development component and did some changes in one of the jsp files in it. I could see the changes in the development portal after check-in and activation. This activity was then released and transported to quality portal.

When I tested in the quality portal, I couldn't find the changes. In the Change Management Service, the transport seems to be successful as I could see the transport object in the 'Approval' tab. But, when I check the details of the transport object, the transport object did not contain the recently changed jsp file. Instead, the modified date of that jsp file was still dated to the year 2005.

I did a portal transport for the second time by checking out the same file just to check if this time the transport would be successful. Alas! the new transport object also did not contain the changed file when I checked the details in the approval tab.

Please throw some light on this!

Thanks & Regards,

Yuvaraj

[ErvinSzolke · Accepted solution]

Hi,

could you please test the whole development cycle again in the following order?

1. make a change again, i.e. check out something, do some change which can be easily tested in runtime (like changing a label, etc) and check in your change

2. activate your change

3. release it

4. go cms webui, to the transport studio and import the change into cons (test in run-time, whether you can see the change)

5. assemble

6. import into test.system (after succesful import check, whether you can see the change)

Please let me know whether you still don't see the change. Prerequisite is that all the above points are succesful.

Any of these steps are not succesful, will influence the upcoming step.

Thank you!

Regards,

Ervin

Edited by: Ervin Szolke on Sep 2, 2010 10:35 PM

[Former Member · Accepted solution]

Hi Ervin,

Thanks! The transport issue has been resolved!

Two months ago, the NWDI track that I'm using was changed. As a result, there was a mismatch in the dc versions of dev and Q. I created new transport objects for the custom b2b component and the custcrmprj component. The basis team manually changed the version of the transport objects to a higher level than the version in Q. The transport has been successful.

The custom b2b component and custcrm component in development and quality portals are now exactly the same. But in quality portal, the application is now giving a runtime error as soon as we login. I will create a new thread for getting help on this issue.

Thanks!

Yuvaraj

[ErvinSzolke · Accepted solution]

Hi,

you are welcome, I am glad to hear that the problem is resolved.

Feel free to create a new entry for the runtime error.

Regards,

Ervin

[ErvinSzolke]

Hi,

could you please go to the transport studio, to the Test Tab and check the "Details..." button of the import you have executed recently? You'll find it using the "Go to history" button of this tab It has three log files (DTR import and CBS make will show "not needed" or similar since in test phase you don't have version control and build any more since the SCA is already assembled, but indeed you should have a log for deployment).

Approval is one step further, after importing the changes into quality ("Test" tab). Approve will enable the SC to show up on production tab (plus trigger transport if track connections are set up). The question is rather whether your changes got deployed at the phase of importing on the Test tab. If I understand properly you miss the change from the quality, so I assume you refer to the runtime system which you have specified for the "Test" phase in NWDI.

Caveat factor:

Further, as you know the SC will assemble the changes always from the cons/active workspace, i.e. you need to ensure that you have imported the change into cons, executed a new assembly, and imported it again into test only afterwards. Else, the change is not part of the production (the SCA file). If this is not the case, then we really need to concentrate on the deployment in test phase.

I hope this helps.

Best Regards,

Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

Edited by: Ervin Szolke on Sep 1, 2010 12:36 PM

[Former Member]

Hi Ervin,

I have got the SDM deploy log from the 'Test' tab itself.

In the 'Approval' tab, I do not see any logs on click of 'Details' button. I could only see the content of the transport object.

Regards,

Yuvaraj

[former_member214355]

Hi

Maybe the SDM-Deploy log will provide more details?

Thanks

Kenny

[Former Member]

Hi Kenny,

I have checked the SDM Deploy log as well. In the SDM deploy log it shows as 'Ended with result not needed'.

20100812135034 Info :Starting Step SDM-deploy at 2010-08-12 13:50:34.0324 -4:00

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

20100812135034 Info :Step SDM-deploy ended with result 'not needed' at 2010-08-12 13:50:34.0326 -4:00

When I checked my NWDI Activity in DTR, the activity content shows the jsp file which I have modified.

Regards,

Yuvaraj