Do you like my blog? Follow me on Twitter X

XI/PI: Step-by-Step Guide to XI Transports Using CMS – Part I

CMS is the recommended way of transporting SAP XI Objects. It helps you to carry out transports in a more organized manner allowing you to keep track of transports, thus ensuring proper traceability. In this three-part article series, we will understand how to carry out SAP XI transports using CMS.

One can transport SAP XI objects either by using File System Transports (Export/Import way) or by using the CMS (Change Management Service). Many a times, File system transport is preferred over CMS. However, transporting via CMS is the recommended way as it helps you to carry out transports in a more organized manner allowing you to keep track of transports, thus ensuring proper traceability. In this article series, we will understand how to carry out SAP XI transports using CMS.

Ensure that the following steps have been completed before proceeding:

  • Install CMS Components for XI on the SAP XI J2EE Server
  • Create all relevant service users with proper roles and authorizations
  • Maintain CMS related parameters for IR and ID in the Exchange Profile
  • Define Business system groups in the SLD as per the landscape
  • Maintain the Transport targets in the SLD
  • Create a transport domain in the CMS Landscape Configurator and maintain LSADMIN user for the same
  • Create tracks for IR and ID objects

Now let us understand how to transport SLD objects.

Transporting Products

  • Exporting SLD ObjectsIn the SLD of the source system, choose ‘Software Catalog’
  • Navigate to the Product version you wish to transport
  • Click on ‘Export’
  • Download the presented ZIP file on your local desktop
  • Now, logon to SLD of the target system
  • Click on ‘Administration’ and then click on ‘Import’
  • Specify the path of the ZIP file downloaded from source SLD.
  • Import the file using the ‘Import File’ button
  • A success message will be displayed
  • Verify that the Product is indeed available in the target SLD

Transporting Technical Systems

  • Importing SLD ObjectsIn the SLD of the source system, choose ‘Technical Landscape’
  • Select the Technical System you wish to transport
  • Click on ‘Export’
  • Download the presented ZIP file on your local desktop
  • Now, logon to SLD of the target system
  • Click on ‘Administration’ and then click on ‘Import’
  • Specify the path of the ZIP file downloaded from source SLD.
  • Import the file using the ‘Import File’ button
  • A success message will be displayed
  • Verify that the Technical system is indeed available in the target SLD

Transporting Business Systems

Business systems are transported in the same way as products and technical systems. However, one point should be noted: You must assign Business System Groups and Transport Targets for every business system you wish to transport.

Let’s say, BS_DEV is a business system in SAP XI development system. All ID objects that use BS_DEV, after transport to SAP XI production system should have the business system BS_PRD instead of BS_DEV.

For the above case, BS_DEV should be defined in SAP XI development system as follows

  • Related Integration Server – DVX (SAP XI Dev Server)
  • Group – DEV
  • Transport Target – Group: PRD Target: BS_PRD

BS_PRD should be defined in SAP XI development system as follows

  • Related Integration Server – PRX (SAP XI Production Server)
  • Group – PRD
  • Transport Source – Group: DEV Source: BS_DEV

To transport a business system

  • In the SLD of the source system, choose ‘Business Landscape’
  • Select the Business System you wish to transport
  • Click on ‘Export’
  • Download the presented ZIP file on your local desktop
  • Now, logon to SLD of the target system
  • Click on ‘Administration’ and then click on ‘Import’
  • Specify the path of the zip file downloaded from source SLD.
  • Import the file using the ‘Import File’ button
  • A success message will be displayed
  • Verify that the Business system is indeed available in the target SLD

CMS LogonSynchronizing the CMS Data with SLD

CMS should be updated whenever a product/software component is created/updated in the SLD.

  • Access the CMS using the URL http://<hostname>:<J2EE Port>/devinf
  • Choose ‘Change Management Service’
  • Logon using the XIRIG user
  • Go to Landscape Configurator
  • Select the IR track on the left
  • Go to ‘Domain Data’ tab on the right
  • Click on the ‘Update CMS’ button

Update CMS

  • Add Software Component to the trackOnce done, go to ‘Track Data’ tab
  • Add your software component to the track using the ‘Add SC…’ button
  • Choose ‘Save’
  • Status message will be displayed at the bottom of the page

Thus, we are done with the SLD part. Some points should be noted though –

  • During transports, it is suggested to use XISUPER user id in both source and target SLDs
  • In CMS, always use user id XIRIG
  • Whenever a product or software component is added/updated in source SLD, do not Forget to ‘Update CMS’
  • Assign correct Business System Group to every business system and maintain ‘Transport Targets’ to source business systems

In the next part, we will see how to transport Integration Repository objects using CMS.

Comments

  1. Deepak Jaiswal says:

    Hi Riyaz,
    awesome blog.Thanks for such step by step explanation.
    Thanks
    Deepak

  2. Harish says:

    Hi Riyaz,

    Very nice blog on CMS for XI transports. I really appreciate your effort. Thanks alot. I have question. In my landscape we have 4 system landscape. We have included pre-prod and i am trying configure CMS to include pre-prod system. So far i have done is, i created seperated track and did trac connection but my question is i defined pre-prod as Dev system on second track. I am not able to see the transports in Pre-prod landscape. Can you please suggest how do i go about configuring.

    Thanks alot in advance.

    Good work..

    Regards
    Harish

  3. Vincent says:

    Hello,

    I have an issue about splitting a single edi document (204 transaction) into multiple idocs based on the count in the L11 segment.

    I am working on a scenario where the source is an EDI 204 document. Now in this document, the L11 segment has a count of the total number of items in the source EDI document.
    ISA
    ST
    .
    .
    .
    .
    L11*1110*BC <——- 2 is the number of OIDs that can appear
    OID*1
    LAD*CAS*3*****BL*84985197*CG*ZZ*AM*000521*122
    LAD*******CC*CC12345678*CO*CO12345678*PM*PM123456
    OID*2
    .
    .
    .
    OID*910
    .
    .
    OID*911
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    OID*1110
    .
    SE*14*8744
    IEA
    Now both the OIDs are in a single ST-SE EDI document. The requirement is that if the number of OID segments exceed 910 in a single document, then the output needs to be split with one idoc containing 910 items (OID, LAD, LAD…). The next set of 910 OIDs (from OID*911 onwards)need to be output into a new idoc.

    The header part for both the idocs would be the same. Only the detail part would differ for the next set of OID, LAD segments.

    I do not intend to use BPM. I want to achieve this using using graphical mapping.

    Awaiting your replies.

    Thank you
    Vincent

  4. Riyaz says:

    Thanks Krish,

    I will be putting up two more blog posts on CMS transports shortly.

    Regards,
    Riyaz

  1. maheshbabu says:

    please tell me,
    sap pi/xi in sld using bussiness system for groups,transports,install products briely define

  2. Krishna says:

    Hi Riyaz,
    thanks for excellent blog on CMS. You made this concept very simple for me.

    Please keep blogging.

    Thanks
    Krish