Version Control & Migration to new Environment

[Former Member]

Hi

I am new to XI and would like to get suggestions on the following

1. How do you normally do version contol in xi ? Is it using the history availabe with xi iteself or you export different versions to files ..Suggestions are welcome

2. How do you normaly move the code across environements .. Say QA to PROD ..... Is it by using import / export ...? Any other methiods ....suggestions

3. How do you migrate bug fixes ... Say u have a change only in the message mapping or channel . Do u move only the changed object? or is it better to move the entire scenerio ?

4. Any other items that should be taken care of while doing the above actions

thanks

Prashanth

[STALANKI]

To start with read this /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi

[Former Member]

Prasanth,

1.How do you normally do version contol in xi ? Is it using the history availabe with xi iteself or you export different versions to files ..Suggestions are welcome

This we can select from the history available in XI itself.

2. How do you normaly move the code across environements .. Say QA to PROD ..... Is it by using import / export ...? Any other methiods ....suggestions

We can do import and export via CMS or file transport.

This Weblogs will answer all you about this:

/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi

/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation

/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview

/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms

3. How do you migrate bug fixes ... Say u have a change only in the message mapping or channel . Do u move only the changed object? or is it better to move the entire scenerio ?

If there is any change say ex. Message mapping we can only transport this object. But the best practice would be to transport entire namespace or the entire scenario.

---Satish

[Former Member]

Hi

1)SLD (system landscape directory)will perform version management

2)(Change Management Service) in the SAP Exchange Infrastructure

CMS was originally designed for use in Java development and was only later adapted to suit XI requirements.In the XI 3.0 environment, CMS is used to transport changes and customer developments in the Integration Repository and Integration Directory of the development system consistently through the system landscape. Transporting using CMS rather than the file system simplifies this process significantly, since you no longer have to copy (export and import) the files manually.

3)You have to perform accroding to the scenario.

for more info ://help.sap.com/saphelp_nw04/helpdata/en/e1/69a740aa053a13e10000000a155106/frameset.htm

For more information about error messages, current problems, and solutions, see SAP Note 780297.

http://help.sap.com/saphelp_nw04/helpdata/en/e1/69a740aa053a13e10000000a155106/frameset.htm

Cheers,

Shyam.