Landscapes configuration

Name of landscape

Deploy after transport defines whether objects imported to current system are deployed or not.

(Only for binary landscapes) Enable Naming Validation enables objects names mappings validation on transport level. If you have a rule TEST.*, related objects can’t be mapped to TST.* Naming validation rules should be uploaded for agent related to a source landscape item (upload naming convention rules).

Make a snapshot of Transport configuration before approval - if true, transport configuration is cached once transport is sent to approval. The option is visible if Require Transport Approval option is enabled for at least one landscape item.

Restrict Execution enables transport executors configuration.

Transport Executors defines executors. This option is available only if Restrict Execution is true.

Allow transport of older versions allows import older versions to target systems.

Enable 'Inherit from source' by default for existing target objects changes default behavior of inheritance flag for existing objects to 'Inherit from source'. Default values is false, that means 'Inherit from target' flag for existing objects.

Use 'Default Value' of Externalized Parameters instead of 'Configured Value' changes IFlow Externalized Parameters values used in transport configuration. IFlow Externalized Parameters have 'Default Value' and 'Configured Value'. When this option is enabled and the parameter has 'Inherit from source' mode, the 'Default Value' will be used.

Set Transport Configuration as 'Default Values' for Edge runtime writes the values from the transport configuration into the target IFlow model as 'Default Value' of the externalized parameters, in addition to applying the IFlow configuration through the Public API. It’s a temporary workaround for SAP Integration Suite keeping externalized parameter configuration separately per runtime: an Edge Integration Cell runtime configuration can be neither read nor written through the Public API, so writing the values as default values is the only way to deliver them during transport. The option applies per IFlow — only IFlows whose runtime profile resolves to an Edge Integration Cell runtime on the target system are affected. IFlows resolved for the Cloud Integration runtime keep their configured values as usual, and on a target system without an Edge runtime the option changes nothing.

Restrict Access enables restricted access to the landscape.

Landscape Developers defines users who are allowed to work with the landscape. This option is available only if Restrict Access is true.

(Only for binary landscapes) Scheduled transports execution time configures left bound for import process execution. After configured time global scheduler will have a pulse each 5 minutes. If a lot of transports are scheduled around same period, then target system may be overloaded with transports for some period of time. So that not all transports will be scheduled and executed in time.

Attach all dependent objects for B2B transports defines whether dependent objects of B2B objects attached to the ticket are attached automatically to the tickets and transports or not. All dependent objects will be attached automatically during the following operations:

Auto-activate B2B agreements defines whether agreements imported to current system are activated (for not activated agreements) and updated (for edited agreements) automatically or not.

Customize TPM import settings (since 2606) defines whether the agreement import selections are customized during transport import. It’s disabled by default. When enabled, you can configure the import selections (modeled on SAP’s Action Import Agreement screen), which are then applied when the TPM agreement is imported. The settings are applied at import time (even for Locked Version landscapes).

Suppress warnings for Auxiliary B2B objects - allow imports always defines whether warning related to Auxiliary B2B objects should be suppressed or not. Auxiliary B2B objects are:

Allow B2B transports of Draft state (since 2606) defines whether B2B objects in Draft state can be added to transports and transported. It’s disabled by default, so adding a Draft object to a transport is blocked. When enabled, agreements, agreement templates and B2B scenarios in Draft state can be transported. It’s useful when you don’t use TPM versioning and keep these objects permanently in Draft. Drafts of Message Implementation Guidelines and Mapping Guidelines remain blocked. The option is defined per landscape, so it must be enabled on every landscape in the transport chain; when a Draft object is blocked, the message names the landscape and points to this option.

Parameter mapping rules defines name mapping rules. Several Rule Types are supported and depending on chosen types different configuration is required.

Parameter values replacement defines parameter values replacement rules for transport configuration parameters. To enable this feature during landscape creation switch Configure on. Then for each landscape item you can define rule type (substring or exact match) and parameter values which will be used in transport configuration parameters.

Transport validation tags configures tags either technical or not-technical. If a tag is detected in an object during the creation of transport, it will be displayed as a warning. This functionality allows for easily tracking of non-blocking issues resulting from transport validation.

(Only for binary landscapes) 'Deny if matches' criteria defines criteria for objects that will not be attached to tickets and transports. So such objects can’t be imported. You can define criteria Object name patterns (as regular expression appended by list of types if it is needed), Object Types and Object Tags.

(Only for binary landscapes) 'Allow if matches' criteria defines criteria for objects that will be attached to tickets and transports. Only objects match this criteria can be imported. You can define criteria Object name patterns (as regular expression), Object Types and Object Tags. If the criteria is defined and object doesn’t match all filters, then its devops is denied (in other words, if object matches any filter - its devops is allowed).

(Only for binary landscapes) 'Deny if object exists' criteria defines criteria for objects that will not be attached to tickets and transports if target objects exist. So such objects can be imported only if corresponding objects don’t exist on target system. You can define criteria Object name patterns (as regular expression), Object Types and Object Tags.

Email integration enables or disables emails sending for approval and import operations. Configure the settings:

(Only for binary landscapes) Ticket Management System Integration configures send message request used to fetch external tickets.

[
    {
        "ID": "<ID>",
        "URL": "<URL>",
        "Title": "<Title>",
        "Description": "<Description>",
        "Status": "<Status>"
    },
    {...},
    ...
]

(Only for binary landscapes) Webhook integration defines events which should fire via webhook. To configure webhook go to Integrations page and create HTTP(S) integration.

Name of landscape

(Only for binary landscapes) Enable Naming Validation enables objects names mappings validation on transport level. If you have a rule TEST.*, related objects can’t be mapped to TST.* Naming validation rules should be uploaded for agent related to a source landscape item (upload naming convention rules).

Require Transport Approval enables review step between transport creation and import.

Transport Reviewers defines reviewers. This option is available only if Require Transport Approval is true.

Make a snapshot of Transport configuration before approval - if true, transport configuration is cached once transport is sent to approval. The option is visible if Require Transport Approval option is enabled for at least one landscape item.

Restrict Execution enables transport executors configuration.

Transport Executors defines executors. This option is available only if Restrict Execution is true.

Enable 'Inherit from source' by default for existing target objects changes default behavior of inheritance flag for existing objects to 'Inherit from source'. Default values is false, that means 'Inherit from target' flag for existing objects.

Restrict Access enables restricted access to the landscape.

Landscape Developers defines users who are allowed to work with the landscape. This option is available only if Restrict Access is true.

(Only for binary landscapes) Scheduled transports execution time configures left bound for import process execution. After configured time global scheduler will have a pulse each 5 minutes. If a lot of transports are scheduled around same period, then target system may be overloaded with transports for some period of time. So that not all transports will be scheduled and executed in time.

Parameter mapping rules defines name mapping rules. Several Rule Types are supported and depending on chosen types different configuration is required.

Parameter values replacement defines parameter values replacement rules for transport configuration parameters. To enable this feature during landscape creation switch Configure on. Then for each landscape item you can define rule type (substring or exact match) and parameter values which will be used in transport configuration parameters.

Transport validation tags configures tags either technical or not-technical. If a tag is detected in an object during the creation of transport, it will be displayed as a warning. This functionality allows for easily tracking of non-blocking issues resulting from transport validation.

(Only for binary landscapes) 'Deny if matches' criteria defines criteria for objects that will not be attached to tickets and transports. So such objects can’t be imported. You can define criteria Object name patterns (as regular expression appended by list of types if it is needed), Object Types and Object Tags.

(Only for binary landscapes) 'Allow if matches' criteria defines criteria for objects that will be attached to tickets and transports. Only objects match this criteria can be imported. You can define criteria Object name patterns (as regular expression), Object Types and Object Tags. If the criteria is defined and object doesn’t match all filters, then its devops is denied (in other words, if object matches any filter - its devops is allowed).

(Only for binary landscapes) 'Deny if object exists' criteria defines criteria for objects that will not be attached to tickets and transports if target objects exist. So such objects can be imported only if corresponding objects don’t exist on target system. You can define criteria Object name patterns (as regular expression), Object Types and Object Tags.

Email integration enables or disables emails sending for approval and import operations. Configure the settings:

(Only for binary landscapes) Ticket Management System Integration configures send message request used to fetch external tickets.

[
    {
        "ID": "<ID>",
        "URL": "<URL>",
        "Title": "<Title>",
        "Description": "<Description>",
        "Status": "<Status>"
    },
    {...},
    ...
]

(Only for binary landscapes) Webhook integration defines events which should fire via webhook. To configure webhook go to Integrations page and create HTTP(S) integration.