Integrate 2 PI System into 1 PI Systen

[Former Member]

Hello,

I have the following problem:

we have 2 customers, every customer has a PI system and his own SLD,

- is it possibble, to integrate this 2 PI Systems into 1 PI system ?

- should we crate a new SLD with the components form the both SLD´s for the new PI system ?

- is it possible to measure the PI traffic for every customer (customer 1 and customer 2) in this new PI (to determine the SAP licence fees) ?

Thank you in advance

Kind regards

Uwe

[former_member183906]

The communication via web service may have advantages, if you want communicate with non XI systems.

In your scenario, there is direct communication between XI engines, so you can go for XI adapter. The XI adapter which is normally used to configure the exchange of messages with in an Integration Server, canbe extended to exchange messages between the two Integration Servers in the scenario.

Please verify if if you have the common SLD for both XI systems. its preferable to go for seperate SLDs

Check out the similar threads, XI to XI scenarios:

These links will definitely give you an idea about the current situation.

[Former Member]

Hello,

I want to move/migrate the content (Integration Directory, Integration Repository) from the existing PI system from customer/company 1 and the extisting PI system from customer/company 2 into (they are 2 companies) into a new PI system and deactivate the existing PI systems from customer 1 and 2.

(at the moment, the 2 PI systems was hosted in our data center)

I want to use one PI (the new system) system for both companies (like an Application Service Provider).

[former_member183906]

Hii Uwe..

There are two types of transport mechanisms in XI.

1.File Level Transport: Files are exported and imported into SAP XI OS level folders of development and QA respectively. This is relatively easy as there is no need of setting up any additional softwareu2019s but its risky as the process is not automated as the files have to be FTPu2019ed from development to QA XI boxes and any failure of the transport cannot be tracked and audit logs will not be available.

2.Change Management System (CMS): This is a GUI based tool, which has to be installed on the XI box for providing the user-friendly browser which is used for automating the transport mechanism and tracking any transport failures. However there is an initial level effort for setting up the CMS and stabilising it.

Depending on the complexity and time lines we can choose any of the transport mechanism. Since our interfaces are not that complex due to generalisation of the IR and ID objects and due to the unavailability of basis at the client site we have chosen the file level transport mechanism. After setting up the SLD in QA with the required transport targets for business systems of SLD the exercise of transporting the targets took 3 days time for 120 IR and ID objects with work load shared by 2 people.

Let me list down the transport process quickly and an appropriate way for ease of transition to different boxes.

Process in SLD:

1.We need to set different transport targets for the required business systems which are used in the scenario objects (ID) of developments. It is just assigning the business system of development to another business system of QA, which is just the replica of dev BS.

2.We need to export the SLD objects from the development to QA SLD. Detailed process can be referred from service market place or SAPHELP.

Process in IR:

1.We need to organise the IR objects in the name spaces properly and ensure that all objects of the name space are correctly available. Ex: Message types, Data types are present in the appropriate name spaces.

2.We need to ensure all the usage dependency objects for the required if any are also available.

3.We can transport the objects at the name space level or SWCV level initially depending on the complexity. We can do it by using the Tools->Export Design Objects Wizard in the development IR. We can see that the file that is getting generated using the wizard has the name File: XI3_0_SWCV Description_Version number.tpz when exported at the SWC level and File: XI3_0_SWCV Description-nsps_Version number.tpz when exported at namespace level. We need to ensure that all the reference objects also are exported together to avoid run time failures in QA box. For Ex: We have generic message types, data types, BPMu2019u2019s which are used by all namespaces in the corresponding SWCV. When we are importing the interface specific name spaces into QA IR it has imported successfully as we do not need activate the objects in QA IR. But when we tested it has given run time errors that required message type or data type cannot be found. We re-imported the generic name space objects and usage dependency objects into QA IR, tested the interface and it works fine after that.

4.We can transport each and every individual object of the IR like data type, message type,idoc type,rfc ..etcu2026by using the same wizard and the file name that is generated when exporting individual objects is File: XI3_0_SWCV Description -objs_VersionNumber.tpz

5.We have to make sure that if any custom RFC modules are developed for JCO calls that required connection parameters have to be changed to point to appropriate sand box. However this can be avoided by using gethostname and getclientname methods in JCO calls.

6.We also need to ensure that if any custom ABAP objects are developed in XI box those requests also have to be transported for avoiding run time failures in QA XI box.

Process in ID:

1.We can export configuration object either at the scenario or service or individual object level.

2.File Name conventions in the ID:

File: XI3_0_directory-selection_VersionNumber.tpz- Export of Individual Objects

File: XI3_0_ScenarioName_VersionNumber.tpz- Export of Scenario Objects

File: XI3_0_ServiceName_VersionNumber.tpz- Export of Service Objects

File: XI3_0_PartyName_VersionNumber.tpz- Export of Party Objects

3.However we can transport at the scenario level initially so that we can have a clear logical grouping of whether all the required individual objects like sender agreements, receiver determinations..etc are present for an interface to work.

4.Unlike IR when we import the scenarios in ID the configuration metadata will be lost and have to be manually entered in the QA ID. For Ex: Parameters like source directory, filename scheme, FTP server will vanish and have to be entered appropriately as required for QA sand box. After entering the metadata we need to activate all the scenario objects in the ID. After successful activation your interfaces are ready for testing.

Process in Runtime:

1.Check in the transaction SXMB_MONI of QA ABAP stack whether the interfaces are working as desired.

I just tried to put up my little experience in the blog thinking that it can be useful. As far as I understand from my little experience versioning and transporting mechanisms in XI is good if the objects are clearly understood.

These links ll be used as reference !!

SLD Transport

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d64...

http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm

content transport with cms:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db...

Configuration of CMS in Central NWDI & SLD to transport XI objects:

XI Software Logistics Solution III: CMS:

Refer the configuring group and transport group for Business systems.

http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/frameset.htm

How to handle SLD for Tranporting Dev to Quality ser

https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df1...

Pls check this PDF doc

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa/soa-management...

Vijayant

[former_member192295]

Hi,

It is possible and we can transport IR & ID objects without any problem, but SLD point of view better to make central SLD. It will help more.