Skip to Content
avatar image
Former Member

Organizing integration projects into SWCV/Namespaces for CMS

Hi,

I have a question regarding how to organize different integration projects into SWCV/namespaces in order to be able to send the different projects into production using CMS independently.

We are using XI for all data from/to our SAP system landscape, and using BizTalk (BZ) for integration scenarios between the different system landscapes in our company.

Basically, we thought we could organize the different integration projects between XI and BZ using just one SWCV where each project has it own namespace;

BIZTALK

<namespace for project 1>

<namespace for project 2>

<namespace for project n>

But when using the CMS for transport, we cannot separate which transport to assemble when they are related to the same SWCV. Thus, 2 different projects with BZ interface and several transports to Consolidation, they will all be assembled even if just one of the projects is supposed to be transported to production.

Can someone verify this?

Seems to me that we must reorganize and create a BZ SWCV for each project?

BIZTALK_PRJ1

<namespace for project 1>

BIZTALK_PRJ2

<namespace for project 2>

This will give us a lot of different SWCVs for one system, and the same is valid for all our different SAP systems…

Best regards

Torstein

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jan 11, 2006 at 06:01 PM

    Hi,

    Check these links,

    /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

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e

    Hope this might help you.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 12, 2006 at 09:18 AM

    Thank you for the links, but I have already looked into the most resources regarding CMS, it is up and running, working just great, BUT no one is explaning in detail how to organize different integration projects (IR/ID) in order to be able to transport projects independently to production.

    best regards

    Torstein

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 12, 2006 at 11:11 AM

    I would recommend to use one namespace per interface and then you can group the inetrafces accordingly to a swcv.

    You can definetly import the objects at the name space level and even minute level of objects also.So if u donot want to transport objects of other project you can do so.

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

    it may be helpful.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you again, but I think I have to rephrase my question;

      We are using the CMS option for transporting objects between Dev, Qual and Prod.

      Introduction; you have a SWCV with 2 different namespaces for 2 different interfaces/projects. It is easy to transport to Consolidation, but all imported transports are automatically placed into the Assembly Queue (transports are assembled into a service pack before approval and import to production).

      At the Assembly stage, you can only select transports based on SWCV, you cannot select which transport to use, but all transports related to one SWCV will automatically be assembled.

      Thus, if 2 different projects, separated into two namespaces in one SWCV, have transports to Consolidation, all the transports will be assembled.

      If using File transports this is not a problem, but the it seems to me that it should be possible to separate which transports to select for assemble based on SWCV AND namespace.

      Comments?

      Best regards

      Torstein Nesby