Track Connections

Track connections enable you to construct landscapes from sequential tracks and fine-tune the flow of software components in these landscapes.

A track connection consists of the following parameters:

• Source track

  Track from which you want to transport software component archives (SCAs) into a follow-on track

• Target track

  Track into which you want to import software component archives from a source track

• Connection type

  The connection type determines the direction of the flow of software. The following types are defined:

  • Transport connection

    A standard connection between two tracks. You use this connection type to define the direction of software changes through your landscape. Only completely assembled software component archives (SCAs) are transported through transport connections.

  • Repair connection

    You use a repair connection to specify that changes from a follow-on track can be imported back into a preceding track. Individual change requests are transported through repair connections. This is relevant for maintaining an application. See Back Transports in NWDI .

• Connection option

  You can use the connection options to restrict the number of software components that are transported through a track connection. You can choose from one of the following options:

  • Transport All Software Components

    This option is the default for all connections. All software components defined in the source track and target track are transported.

  • Transport Developed Software Components

    When this option is set, only those software components are transported that are developed in the source track.

  • Transport Required Software Components

    When this option is set, only those software components are transported that are configured as prerequisite software components in the source track.

  • Transport Selected Software Components

    When this option is set, you can select your own list of software components to be transported.