Migration of existing CIG connection to a different System ID

[dgromilovi]

Dear experts,

I want to migrate the existing CIG project which is in status "In production" and connect it to a different System. Does anyone have any experience with this? I have both test and production connections within the same CIG project so deleting it is not an option since production has to keep running.

While if I create a new project and use it to connect one test Ariba system to the new S4 Hana system, question is what to expect of the existing test and prod connection from an old project.

Thank you in advnace,
Dinko

[AndreMiranda]

As I mentioned earlier, you can have as many systems or projects as you need, and they will not impact each other since each will have a unique SystemID and URL for connection.

For this new project, you may assign a dummy SystemID in the test environment and use the real one for production. If you're utilizing the SAP Business Network, the SystemID is included within the cXML data that is sent to CIG. Consequently, CIG will route the document to the appropriate ERP.

This arrangement is similar to having multiple systems in a test environment—like sandbox, development, QA, and UAT; all within different projects, with CIG routing the documents back to them.

[dgromilovi]

I understand that I can have as many unique system IDs and projects but can I connect all those to the one ariba test realm and route the documents at the same time to different systems eg. sanbox, dev,QA...?

So my point is:

• I have Ariba realm 55140
• I have System IDs(different connections): TST1, TS2, TS3
• I want to connect 55140 to TST1, TS2 and TS3 at the same time

Can I accomplish that?

[AndreMiranda]

I believe you cannot change the SystemID after you move the project to production.

You can try to open a ticket to have that changed for you, or you could create a new project and deploy to production.

Remember that CIG is a middleware and should accept multiple SystemIDs; you have also to configure this new system in the network as well, if you are using other Ariba apps it is required to use custom routing instead.

[dgromilovi]

Dear Andre,

Thank you for your answer. Biggest challenge here is the fact that production and test connections are created within the same project so we have to keep it on since we need to maintain productive connection, so idea is to create a new project just for test and connect it to the new system and the main question here is, how this will impact existing connection and will the test ariba then route correctly to the new backend system?

Best regards,
Dinko