Transporting XI object

[Former Member]

Hi Gurus,

I need to know about Transporting XI object. What object we can transport and what objects we cannot. If we can transport complete senarion what is use of software product and component.

[Former Member · Accepted solution]

Hi,

Check this link

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Thanks,

RamuV

[Former Member]

HI

Refer the below links for assistance

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

https://forums.sdn.sap.com/click.jspa?searchID=13214292&messageID=5176673

Configuring Groups and Transport Targets.

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

also have a look at:

Transporting XI Objects

http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/content.htm

Software Component:

u2022 Software Component: Represents a collection of all versions of a software component. Software components represent the reusable modules of a product. They can be upgraded or have patches installed.

u2022 Software Component Version: Represents a particular version of a software component.

u2022 Software Feature: Represents a particular aspect of the product functions. It is a logical link between Product Version and Software Component Version.

Product: Represents a collection of all versions of a product. A product is a unit that can be delivered, is visible to the customer, and that is installable and renewable. In an SAP environment, a product corresponds to an SAP technical component

.we can install mutiple software component in one product.

Product

A collection of all versions of a product. A product is a unit that is delivered, visible to the customer, and is installable and renewable. In an SAP environment, a product corresponds to an SAP technical component.

u2022 Product version

A particular version of a product.

u2022 Software component

A collection of all versions of a software component. Software components represent the reusable modules of a product. You can upgrade them or install patches on them.

u2022 Software component version

A particular version of a software component.

u2022 Software unit

A particular aspect of the product functions. It is a logical link between the product version and the software component version.

Product:

Products are a unit that can be delivered, is visible to the customer, and that is installable and renewable. As mentioned before, the SAP Products are readily

available (i.e., SAP APO, SAP Automotive, etc).

Software Component:

Software Components represent the reusable modules of a product. As mentioned before, SAP Software is readily available (i.e., Adobe Document, CRM Mobile Client, etc)

as u asked....we have Technical Systems in XI are the conceptual representation of a physical system, such as a physical SAP server with a number of Software Components installed.which gives u details about technical systems wether it is a JAVA system ,ABAP system,or some legacy system....

in case business system,it gives u the logic,i mean Business Systems in XI are the conceptual representation of a logical system, such as a specific client on a SAP server or a 3rd Party payroll application.

SLD is the place where u can define systems that are existing in ur landscape. using these systems u can transfer data from one sRepresents a collection of all versions of a product. A product is a unit that can be delivered, is visible to the customer, and that is installable and renewable. In an SAP environment, a product corresponds to an SAP technical component

http://help.sap.com/saphelp_nw04/helpdata/en/29/17647d028113439108ce1161263b6e/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/87/59c5726d8b5141bf22831a6ce79d8a/content.htm

/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

/people/scott.braker/blog/2005/01/20/software-deploymentcomponent-archive-basics

Software components combine components (DCs) to larger units for delivery and deployment.

u2022 Every top-level component must be assigned to exactly one software component.

u2022 Child components always belong to the same software component as their parent.

u2022 The assignment of DCs to software components is not static and may change over time.

u2022 Software components cannot be nested into each other.

Software components have globally unique names, which are structured according to the rules for DC names. You must define the name when you create the software component; the name cannot be changed later. Names of software components usually consist of a vendor ID and only one segment, such as sap.com/crm.

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/01ea90ab24235de10000000a1553f7/frameset.htm

You can create this in SLD>Software Catalog>new Software component and create the SWC with the new version.

As you know, the SWC acts as place holder for all your design objects. In simple terms, the newer version will be an enhancement to your older released version with added functionality.

Also refer to the following links on help.sap.com for more detailed explanation and look for the compatibility changes when developing a new software component version.

http://help.sap.com/saphelp_nw04/helpdata/en/29/17647d028113439108ce1161263b6e/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/87/59c5726d8b5141bf22831a6ce79d8a/content.htm

/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

/people/scott.braker/blog/2005/01/20/software-deploymentcomponent-archive-basics

cheers

[Former Member]

hi,

You have 2 options

1)File Transports

You have to export from one server and import into target server....

a)IR(You can find the exported .tpz file here)

to export

Usr/sap/XID/sys/global/xi/repository_server/export

to import from export file

Usr/sap/XID/sys/global/xi/repository_server/import

b)ID(You can find the exported .tpz file here)

to export

Usr/sap/XID/sys/global/xi/integration_server/export

to import

Usr/sap/XID/sys/global/xi/integration_server/import

Configuring Groups and Transport Targets.

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

also have a look at:

Transporting XI Objects

http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/content.htm

2)CMS

/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

Thanks,

Viajya

[Former Member]

If you want a simple file transport:

Go for "tools/export design objects" and choose the objects, you wanna transport. They will be put to /usr/sap/<SID>/sys/global/xi/repository_server/export. Copy them to other system in parallel folder import. Then "tools/import design objects"...Directory transports in the same way...

[Former Member]

Hi seshagiri,

Check this link

https://forums.sdn.sap.com/click.jspa?searchID=13214292&messageID=5176673

Regards,

Ramesh.

[former_member859847]

Hi,

Please check the following points step by step.

Transport Objects From DEV->QAV->PRD

Before exporting make sure that the objects are activated.

Perform the following to import/export ID objects.

1. To export or import directory objects, call the configuration maintenance screen of the Integration Builder.

2. Call the context menu for an object in a collaboration profile in the Integration Builder navigation tree and choose Exportu2026.or choose Tools ® Export Configuration Objectsu2026

3. Select the Transport Using File System mode and follow the wizardu2019s instructions. When selecting individual objects, you can use drag and drop to drag the objects from the navigation tree and drop them in the object selection field.

The Integration Builder saves a binary export file with the suffix tpz in the export directory of the directory server

Do not change the file name of the export file. If you do, the Integration Builder will not accept it as the appropriate file when you import.

4. To import the export file(s) to another Integration Directory, first copy or move it to the import directory of the target directory.

5. Call the configuration maintenance screen of the Integration Builder for the target directory. Choose Tools ® Import Configuration Objects...

6. Select the export file saved in the import directory by using the dialog box that appears.

If the import is successful, the export file is moved to the subdirectory /xi/directory_server/importedFiles. The objects are not activated when they are imported into the target directory. They are visible in the change list of the user who imported them.

7. Check the imported objects in the change list and adjust the configuration data to match your system landscape, if necessary.

8. Activate the change list that contains the imported objects.

warm regards

mahesh.