Redwood Documentation

Product Documentation

 

›Promoting Objects

RunMyJobsAutomation Concepts

Automation Concepts

  • Central Scheduling Concepts
  • Automating Processes Across the System Landscape
  • Processes, Chains, and History
  • Queues and Process Servers
  • Workload
  • SAP Systems
  • Events and Event Definitions
  • Scheduling
  • Applications
  • Editing Objects in XML

Locks and Events

  • Prevent Simultaneous Execution of Processes
  • Creating Locks
  • Creating Event-Driven Schedules with Events

Documents

  • Documenting Code, Procedures, and Messages with Documents

Applications

  • Organizing Processes in Applications
  • Creating Applications

End User Overviews

  • End User Interfaces
  • Process Monitors Overview
  • Process Monitors Overview Columns
  • User Message Monitor
  • Designing User Message Forms
  • User Message Monitor Columns
  • Interacting with User Messages
  • Feeds

Managing Output Formats

  • Managing Output Formats

Regular Activities

  • Regular Activities for Redwood Server

Promoting Objects

  • Migrating Objects with the Promotion Module
  • Exporting Redwood Server Objects
  • Export Rule Sets
  • Creating Export Rule Sets
  • Importing Objects
  • Importing Redwood Server Objects with Imports
  • Using Import Rule Sets to Customize Imports
  • Importing Objects with Import Rule Sets
  • Creating Remote Systems
  • Promotion Reaction Processes
  • Integrating Redwood Server Promotion into SAP CTS+
  • Pusher Process Definitions for SAP CTS+ Integration

Backup and Recovery

  • Backup and Recovery of Redwood Server
  • Database Backup
  • Restore Data from Backup

Reference

  • Managing Output Formats
← Integrating Redwood Server Promotion into SAP CTS+Backup and Recovery of Redwood Server →

Pusher Process Definitions for SAP CTS+ Integration

The pusher process definition is used to forward the objects to the SAP CTS+ transport domain controller and initiates the transport request. By default, it creates a new request as the Request number parameter does not have a default value; for CTS this means that the default request of the user is not used. You use an existing request (the user's default request) by specifying default in the Request number parameter; alternatively, you specify the request number. The process will lookup requests for the user specified on the XBP tab of the SAP System for the client you selected in the Client field and use the default for that SAP system if the Client field is empty. You do not fill the Request number field if you want a new request created; this, however, assumes that you use either the Smart or Create transport request strategy ( WBO_GET_REQ_STRATEGY ).

The transport will fail in the following situations:

  • You specified Default in the Request number field and the user as defined on the SAP system does not have a default request
  • You specify an invalid Request number
  • You use Tagged transport request strategy and you do not fill the Request number field

Note that the request is released automatically by default as the Release request parameter has a default value of Yes. You can change the defaults in the process definition, however, you should duplicate it prior to customizing it as it will get overwritten if you import a CTS+ CAR file again.

tip

If you set the Queue and all mandatory parameters, you will not get the submit wizard and will be able to promote objects seamlessly via CTS+.

Parameters

NameDescriptionUseDirectionMandatory
SAP_SYSTEMSSAP SystemThe SAP System connected to the transport domain controllerInYes
CLIENTClientThe client; if left empty, the default client will be usedInNo, default will be used; the client user must have the SAP_CTS_PLUS role or equivalent authorizations
TARGET_SIDSID of the transport source systemThe SID of the transport domain controllerInYes
REQUESTRequest numberThe request number; if specified, the request number must exist on the transport domain controller and be accessible by the user specified in the client. If the user has a default request, you specify default. This parameter will be filled with the request number if a new request has been created or the user's default request was used.In/OutNo
DESCRIPTIONDescription for the new request (optional)Description for the request; only applicable if a new request needs to be createdInNo
RELEASE_REQUESTRelease requestIf this parameter is set to Yes, then the request will be released automatically. The transport strategy for releasing requests (WBO_REL_REQ_STRATEGY) must be Auto for the process to successfully release the request.InYes
CTS_URLAddressThe URL to the Transport Organizer Web UIOutN/A
DataDataThe location of the CAR file on the central Redwood Server.OutN/A
CTS_MESSAGEMessageThe message returned by the CTS+ system.OutN/A

The other parameters are purely reaction job-specific.

See Also

  • Integrating Redwood Server Promotion into SAP CTS+
  • Choosing a Transport Strategy
  • Promotion Reaction Processes
← Integrating Redwood Server Promotion into SAP CTS+Backup and Recovery of Redwood Server →
  • Parameters
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |