Choosing a Transport Strategy

Prerequisites

Your application is closely coupled with the CTS system.
You have configured the connection between your application and the CTS server.

Procedure

Caution Caution

You only require these parameters for applications that have a close coupling with the CTS system (such as SAP NetWeaver Portal or SAP NetWeaver PI systems).

End of the caution.

Call transaction STMS.
Choose System Overview.
Select the required system by double-clicking on it.
The screen Display TMS Configuration: System <SID> appears.
Choose the Transport Tool tab page.
Switch to change mode.
Add the following parameters:
- WBO_GET_REQ_STRATEGY = Control of automatically creating a transport request when you export an object, for example, from an SAP NetWeaver Portal system or an SAP NetWeaver PI system.
  
  Note
  The short text of transport requests that have been created automatically is determined by application-specific values. More information: SAP Note 1348927. This only affects the parameter values Smart and Create.
  
  End of the note.
  
  The following values are possible:
  - Tagged
    It is checked if a preselected request is available. If a preselected request is available then this one is used. If there is not one available then no further action is taken.
  - Smart
    The system automatically creates a transport request (if no request has already been preselected) and flags it as the preselected request.
  - Create
    The system automatically creates a transport request and selects it as the standard request. This also applies if there is a preselected request. This is then no longer preselected.
  When creating a non-ABAP or dual-stack system, this value is automatically set to Smart. If you delete the parameter or if this parameter is not edited in a system, the value Tagged is set automatically.
- WBO_REL_REQ_STRATEGY = Automatically releases a transport request
  The following values are possible:
  - Auto
    The system automatically releases the transport request as soon as an object is added to the request.
  - Manual
    This is configured as the default value in the system.
    
    You must release the transport request manually or set the value of the parameter to Auto. In connection with the parameter values Tagged and Smart of the parameter WBO_GET_REQ_STRATEGY, you can attach as many objects to a request as you like with the Manual setting.

Example

Creating and releasing transport requests manually
If you use the Change Request Management or Quality Gate Management in SAP Solution Manager or an external Change Management System to manage your transport requests, then you make the following settings in the strategy parameter:
- WBO_GET_REQ_STRATEGY = Tagged
- WBO_REL_ REQ_STRATEGY = Manual
This ensures that the developer of your SAP application cannot create or release any transport requests automatically.
Automatic creation and manual release of transport requests
If you want to execute team development or if multiple objects from different application or different object type are to be transported in a request (for example, a Portal-iView together with a Java development that is to be displayed in the iView), make the following settings in the strategy parameter:
- WBO_GET_REQ_STRATEGY = Smart
- WBO_REL_ REQ_STRATEGY = Manual
  All members of a development team can attach their changes objects to the preselected request. The project leader can release the request centrally as soon as development is complete.
Automatic creation and release of transport requests
If the developers of your SAP application are to be involved as little as possible in the activities in the transport system, make the following settings in the strategy parameters:
- WBO_GET_REQ_STRATEGY = Create
- WBO_REL_ REQ_STRATEGY = Auto
  Whenever an SAP NetWeaver Portal developer, for example, exports non-ABAP objects, the system creates a new transport request automatically and then releases it.