Show TOC

Configuring the Workflow Engine in a Different DomainLocate this document in the navigation structure

Use

You have the option of configuring a system in the workflow domain as the Workflow Engine. Even if you link multiple domains with domain links, the transport workflows are still processed in the Workflow Engine of the local domain. This means that you cannot access transport proposals created in a different domain. If you want to be able to administrate the transport proposals of multiple linked domains in a single Workflow Engine, then you can define the Workflow Engine of a different domain to be the Engine of your own domain as well.

When you do this, all workflows processed in the selected Workflow Engine can be accessed from all systems, regardless of whether the Engine is configured in the local domain, or whether the domain is only linked to the local domain.

Prerequisites

You have already configured a Workflow Engine in a domain, and want to be able to use it from other domains.

Note

All the functions of the transport workflow are processed locally in the Workflow Engine. All tasks are processed here and then sent to the logon systems of the users.

Therefore, for anyone who uses the transport workflow, you must create a user with the authorization S_CTS_PROJEC in the system/client in which the Workflow Engine is configured.

Procedure

To configure the Workflow Engine of a different domain, proceed as follows:

  1. Log on to the SAP System that is configured as the transport domain controller in your local domain.
  2. Call Transaction STMS and then choose to display the system overview.
  3. Choose to display the transport domain.
  4. Choose the tab Workflow Engine.
  5. Choose to switch to change mode.
  6. Choose Other Domain under Location.
  7. Enter the name of the domain whose Workflow Engine you want to process the proposals of your local domain. Save your entries and distribute the configuration change. The system performs the following actions:
    • The RFC address of the Workflow Engine is copied from the other domain.
    • The RFC destinations required for the Workflow Engine are generated.
    • All systems in the local transport domain are sent the address data of the Workflow Engine.
  8. Check the Workflow RFC connection.
Result

The transport workflow is active in your transport domain.

See also:

Deleting the Configuration of the Transport Workflow

For more information on transport administration, see Transport Workflow (Administration).

For more information on the development team, see Transport Workflow (Development).