on 07-06-2006 7:05 AM
What is the transport mechanism in XI??
How to transport from Development system to Production syatem.
Is there anyway other than Import or Export??
Thanks in advance,
Jeevan.
Yup, as Vijaya said, there are two ways of transport mechancism. Import and Export is just like a file transfer. And CMS is the transport mechancism with version management. For more information, plz have a look at this site
http://help.sap.com/saphelp_nw2004s/helpdata/en/84/e8763c997fda50e10000000a11405a/frameset.htm<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/84/e8763c997fda50e10000000a11405a/frameset.htm">Transport Mechanism</a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jeevan (and others) -
There is a very good step-by-step guide - <a href="http://service.sap.com/~sapidb/011000358700005550532005E/HowToTransportXIwithCMS.pdf">How ToTransport XI Content Using CMS</a> - already out there on SAP Service Marketplace. This will get you up and running with CMS.
And fyi, there are other very informative How To guides for XI and NetWeaver in general at the following URL:
http://service.sap.com/nw-howtoguides
Regards,
Jin
Hi ,
You can transport object in Xi using
1>Manual method or
2>CMS .
Please refer following links
http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm
Go through these weblogs to get an idea about transporting objects using CMS
1. /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
2. /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
3./people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
Thanks ,
Suvarna
Award pts if it helps .
When you migrate the Integration Server and the Integration Builder, you install a new IS/IB
3.0 on additional hardware. After completing the Customizing on IS 3.0, you use XI tools to
migrate XI configuration and runtime data from the IS 2.0 to the IS 3.0 system. Finally, you
have to switch the addressing for all application systems, adapters, and SLD parts from IS
2.0 to IS 3.0.
You can prepare most steps in setting up Release 3.0 without interrupting the operative use
of Release 2.0. Therefore, the XI downtime is kept to a minimum.
The basics of the migration procedure are as follows:
...
1. Installation and Customizing of Integration Server and Integration Builder (XI 3.0) on a
standby host machine (all-in-one)
2. Migration of SLD data from Release 2.0 to 3.0.
3. Migration of XI Integration Builder data from Release 2.0 to 3.0.
4. Cache refresh.
5. XI downtime starts, which disables the input stream into IS 2.0 / IS 3.0.
6. Migration of essential runtime data.
7. XI downtime ends, which enables the input stream into IS 3.0 again.
8. Address switching of adapters and application systems from IS 2.0 to IS 3.0.
Migration starts with the upgrade of the DEV landscape (including the DEV SLD) to Release
3.0
After upgrading the DEV landscape, there is no way to transport configuration data
from the DEV 3.0 landscape to the QA 2.0 or PRD 2.0 landscapes.
We recommend that you perform all required transports from DEV to QA or
PRD before the migration procedure is started for the whole landscape.
If you need to make configuration changes after the DEV landscape migration to DEV
3.0, for example, for emergency corrections, you need to make the configuration
changes separately and in parallel for DEV 3.0 as well as for QA 2.0 and PRD 2.0.
The transport mechanisms for the SLD and Integration Builder are described in the Online
Help.
All application systems in the DEV landscape must switch their addressing to the new
Integration Server 3.0 of the DEV landscape. For more information, see the relevant sections
below.
you could detaild information from this link
http://help.sap.com/bp_bpmv130/Documentation/Upgrade/XI_Upgrade_Guide.pdf
reward the points if it helps
Regards
Naim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
"What is the transport mechanism in XI??"
This is a mechanism to transport objects (that you have created in one SLD/XI repository) into another SLD/XI repository.
"How to transport from Development system to Production syatem.
Is there anyway other than Import or Export??"
the CMS tranpost system is another way of transporting.
Go through these weblogs to get a brief idea about transporting objects using CMS system..in XI
1. /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
2. /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
3./people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
Regards,
Sushumna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There are two trnasport mechanism,
1. CMS
2. Import and Export of Objects.
The details are available is help.sap.com
Regards
Vijaya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.