Moving XI transports from QA to Prod server

[Former Member]

Hello,

We are getting ready to send our XI transports from the QA server to the production server. We are currently using the file transfer method - we have not yet finished setting up the CMS server.

Now my question is this:

For the Integration Repository, am I supposed to send the same file created from our dev server to the production server, or do I create a new transport file from our QA box and send that file to production? Same question applies to the Integration Directory.

For example, the FileA.tpz gets created in the dev server, exported to the QA server. Developers are done testing in QA and want to move the objects to production. Should I export the same FileA.tpz to the production box OR generate a new transport file from the QA server (FileB.tpz) and send that to production box instead?

Thanks in advance.

[Former Member · Accepted solution]

Joy,

You dont need to change the naming conventions. But to avoid confusion just do it with a different name might be same file name and at the end give like _QA etc. But you transport once again from QA. Dont copy the same from dev to production.

Instead of moving one interface at a time you can move the whole software component at a time. This will save your time. Also you should have the software component created in production before you import.

Hope this helps...

---Satish

[Former Member]

Hi,

The rule in XI transports is : export once import twice

which means the same file you have exported from Dev system will be

imported to both QA and Prod. The same rule applies for both IR and ID. But anyway in Integration Directory you need take care to create business systems & services related to QA and Prod Systems.

Thanks

Pavan

[Former Member]

OK it seems Satish is saying I should export a newly created file from the QA system and send that to the production system.

On the other hand, Pavan is saying I should use the original file created from the dev system and send that to the production system.

Which one should I do? Any blogs/articles out there that can point me in the right direction?

[Former Member]

Joy,

Ideally you should move from Dev to QA and from QA to Prod. Then everything will be in sync. If you move directly from Dev to Prod and if there any changes then they will not be in QA. So this should not happen.

Because only after developement you will move to QA. Once when you test in QA then you will move to Production from QA.

Check this weblogs for further info:

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

/people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development

/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

---Satish

[bhavesh_kantilal]

I agree with Satish. If you mode from Dev to QA and then move the QA objects to Production.

If you are going to move Dev objects directly to Prod , then what is the logic behing having a separate QA environement?

Regards

Bhavesh

[Former Member]

Thanks for the replies.

My question was whether I should move the SAME file that I exported from Dev to QA or if I should export a new file from QA when I move transports to the production system. Moving the same file from Dev to prod will still have technically been tested in the QA environment already.

I didn't know whether creating a new file in the QA environment would mess up some things, like GUID, object owners, and whatnot.

From the replies, it looks like it is ok to export a new file from QA and send that to prod, so that will be our course of action.

Thanks for all the help!