What is the best practice to manage versions in XI?

[Former Member]

Hi!

Is there any <b>good</b> “best practice” ways to manage versions in XI.

Have a challenging scenario with many legacy systems and many interfaces per legacy system.

Should I put all the different interfaces for one legacy system under one namespace in the Integration Repository or should I make one own namespace for each interface.

Or is there other approaches, that I should consider to get a environment that is “easily” maintained.

br.samuli

[Former Member]

Hi,

The document "<i>SAP XI 2.0 Customer developments modif. in Integration Rep.pdf</i>" answered almost all my questions.

Is there a 3.0 document done? Couldn't find it on the Ramp-Up pages.

br.samuli

[Former Member]

Hi,

In our project we have defined our own naming conventions/namespaces.

For instance, we have agreed that we will group all interfaces (from all offices worldwide and different projects) into one single product version.

This global custom product will in turn be divided into different SWC (Software Components) and SWCV (Software Component versions).

So for each business scenario we will create separate SWC's and when necessary create new versions of these SWC's.

This means that each SWC should contain all the required objects to support a complete integration scenario i.e. inbound/outbound-interfaces, data types, msg types, business scenario's etc...

Regards,

Rob.

[Former Member]

Hi Samuli,

Most company have their own standards. You might want to ask first what their approach is. Also, see if this document is any help:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/sap xi 2.0 customer developments modif. in integration rep.pdf

Enjoy!

John Ta