You have three Options when considering transports between systems in XI:
1. File Method - Using the standard tools in XI IR and ID it is possible to export the content to a filesystem and following this import into another environment using the import functionality. The advantage of this is that it is easy to do and not implementation overhead. The disadvantage is that you do not have clear tracability (you xhould keep all exported packages on the server).
2. Using CMS - This uses the NWDI infrastructure to transport packages between environments. Only consider this option if you have NWDI in place in your environment otherwise in my opinion the overhead is too great. It only applies to Java Objects e.g. you cant transport for example ABAP Proxy classes using this methodology.
3. Use CTS+ or enhanced CTS - This allows Java Objects to be transported to by attaching Java Objects to transport requests. This is good if you are an ABAPer and familiar with the se09.se10 transactions. It does however have and implementation overhead and also you must first export the Objects from IR and ID first as per point 1.
IF PI7.0 or PI7.1 then you can use CTS+ (for PI7.0, CTS+ is available only after a specific SP level)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.