Trace Scheduler Configurations
LicenseIncluded in Int4 Shield LiteDetails
| Feature or limit | Int4 Shield Lite |
|---|---|
| SAP Integration Suite testing | Included |
Anything a license model does not include can be added through a custom license. The license installed for you is shown in the app under Profile → License. All features by license
Overview
SAP Cloud Integration switches an iFlow's trace off automatically after about ten minutes, so keeping it on means re-enabling it by hand over and over. A trace scheduler configuration does this for you: it names one SAP Cloud Integration system, lists the iFlows to keep traced, and re-enables trace logging on each of them every time it runs — on demand, or on a recurring schedule.
This matters because Int4 Suite builds tests from real messages. On SAP Cloud Integration the message content a crawler turns into test cases is kept only while the iFlow's trace is on; a message processed with tracing off is never captured and cannot be recovered later. Keeping traces on for the iFlows you want to capture is therefore the precondition for a successful crawl.
Leaving traces on indefinitely has a cost on the integration platform, so a configuration can carry an auto-stop guard: pick a folder and a test-case count, and the configuration switches itself off once that folder holds enough test cases.
The list page shows every trace scheduler configuration and lets you search, export, and open them. Selecting a configuration — or clicking Create New — opens the configuration page, where you add iFlows, set the auto-stop guard and the schedule, and start a run. Every run is recorded on the Trace Scheduler Runs page.
You only need a trace scheduler for traces you manage yourself. A scheduled SAP Cloud Integration crawler with Automatically manage trace switched on keeps the traces it needs by itself; its configuration is managed in the background and does not appear in this list.
This feature works only with SAP Cloud Integration systems.
Tasks
How to create a configuration
- Click Create New in the list toolbar. The button is disabled without the Trace Configuration: Write permission.
- In General, under Identification, enter a Name that is unique across all trace scheduler configurations, an optional Description, and pick the System Under Test. Only SAP Cloud Integration systems are offered. The system cannot be changed after the first save.
- Under Options, leave Active on. Leave Test Run Mode on for a first trial run that changes nothing on the tenant; switch it off once the configuration is right (see How to switch from test mode to live runs).
- Add the iFlows to keep traced (see How to add iFlows).
- (Optional) Set an auto-stop guard in Limit Settings and a schedule in Scheduling.
- Click Save. The configuration opens in view mode.
Saving also checks that you may run tests against the chosen system (System Under Test: Execute) and, when an auto-stop folder is set, that you may write to that folder (Folder: Write). If either is missing, the save is refused.
To start from an existing configuration instead, open it and click Copy. The new configuration is pre-filled with the same system, iFlows, limit and schedule settings, and its name gets the suffix _COPY.
How to add iFlows
The iFlows section lists the iFlows the configuration keeps traced.
- Pick the System Under Test first, so iFlows can be looked up on it.
- Click Add iFlow. A new row appears.
- Click the search button in the iFlow ID cell. The Select Interface dialog lists the integration flows deployed on the system. Narrow the list with Filter, select an iFlow and click Select (or double-click the row). The dialog fills in both iFlow ID and iFlow Name.
- Alternatively, type the iFlow ID directly, for example
Replicate_Orders_Outbound. iFlow Name is a display label only. - Clear Enabled on a row to keep the iFlow in the list but skip it in runs.
- Use the delete button at the end of a row to remove it. A saved row is only marked for removal and can be restored until you save; a row added since the last save disappears at once.
The same iFlow can be listed only once per configuration.
How to run a configuration now
- Open the configuration in view mode.
- Click Execute. The run starts in the background and a confirmation appears (Trace scheduler execution started successfully).
- Follow the result on the Trace Scheduler Runs page.
Execute appears only when the configuration has at least one iFlow. It is disabled unless you have Trace Configuration: Execute on the configuration, System Under Test: Execute on its system, and — when an auto-stop folder is set — Folder: Write on that folder.
How to keep traces on with a schedule
A single run re-enables traces once; SAP Cloud Integration switches them off again after about ten minutes. To keep traces on over a longer period, run the configuration on a recurring schedule.
- Open the configuration and click Edit.
- In Scheduling, switch on Schedule Enabled.
- Choose the Schedule Type — Single for one run at a set time, or Recurring — and fill in the start, recurrence, and end settings. For continuous tracing, repeat at an interval shorter than ten minutes.
- Click Preview Schedule to check the Next scheduled runs.
- Click Save Changes.
You become the Schedule Owner, and scheduled runs use your permissions. In view mode the section shows the schedule's Status, Next Run, Last Run and Occurrences Completed. To stop scheduled runs, switch Schedule Enabled off and save; only the owner can do that.
Scheduled runs fire only while the configuration is Active; while it is inactive, each due run is skipped.
How to stop tracing automatically with an auto-stop guard
- Open the configuration for editing and go to Limit Settings.
- Pick the Test Case Limit Folder to watch — typically the folder your crawler files its test cases into. Test cases in its subfolders count too.
- Enter the Test Case Limit, a whole number greater than zero.
- Save.
Both fields must be filled together. At the start of every run, the configuration compares the folder's test-case count with the limit. Once the count has reached the limit, that run enables no traces, the configuration switches itself to inactive, and its schedule is disabled. The run shows Limit Reached.
To resume after the guard fired, raise the limit (or choose another folder), switch Active back on, and save. Saving also re-activates the schedule.
How to switch from test mode to live runs
New configurations start with Test Run Mode on. In test mode a run does not contact SAP Cloud Integration: it only counts the enabled iFlows and records them as one simulated result.
- Run the configuration once in test mode and check on the run page that the expected number of iFlows was counted.
- Click Edit, switch Test Run Mode off, and click Save Changes.
From then on every run re-enables traces on the live tenant. The mode is recorded with each run, so earlier runs keep showing as test runs.
How to delete a configuration
- Open the configuration and click Delete.
- Confirm in the Delete Trace Scheduler Configuration dialog.
Its schedule is deleted with it. Deletion is refused while a run of the configuration is pending or running. Past runs stay in the run history, but no longer link to a configuration.
Field reference
List columns
Depending on the window width, lower-priority columns are hidden first.
| Column | Description |
|---|---|
| Name | The configuration's unique name. Click it, or the row, to open the configuration. |
| Description | Optional short note. |
| System Under Test | The SAP Cloud Integration system whose iFlows the configuration keeps traced. |
| Active | Whether scheduled runs fire. The auto-stop guard switches this off when the limit is reached. |
| Scheduled | Whether the configuration has a schedule. A schedule disabled by the auto-stop guard still counts. |
| Test Run | Whether runs are simulated without contacting SAP Cloud Integration. |
| Last Run | When the configuration last ran, as a relative time. Empty if it has never run. |
| Created By | The user who created the configuration. |
| Created Date | When the configuration was created, as a relative time. |
Type in Search configurations... to search names and descriptions. The export button saves the loaded rows to Excel or PDF as trace-scheduler-configurations.
Configuration fields
| Field | Section | Description |
|---|---|---|
| Name | General | Required, up to 100 characters, unique across all trace scheduler configurations. |
| Description | General | Optional, up to 255 characters. |
| System Under Test | General | The SAP Cloud Integration system. Fixed after the first save. |
| Active | General | On by default. Scheduled runs fire only while this is on; running by hand works either way. |
| Test Run Mode | General | On by default. Runs count the enabled iFlows without changing anything on the tenant. |
| Test Case Limit Folder | Limit Settings | Folder whose test cases, including those in subfolders, are counted for the auto-stop guard. Set together with the limit. |
| Test Case Limit | Limit Settings | Number of test cases at which the configuration stops itself. Must be greater than zero. Set together with the folder. |
| Schedule Enabled | Scheduling | Attaches a schedule. The schedule settings appear once switched on. |
| Schedule Owner | Scheduling | The user whose permissions scheduled runs use. Only users allowed to change schedule owners can pick someone else. |
| iFlow ID | iFlows | The iFlow's ID on the tenant. This is what the run uses. Required, unique within the configuration. |
| iFlow Name | iFlows | Display name, filled in by the iFlow search. Not used by the run. |
| Enabled | iFlows | Only enabled iFlows are processed by a run. |
The Admin section, shown for saved configurations, lists who created and last changed the configuration and its change history.
Tips & edge cases
- Turn tracing on before you crawl, not after. A crawl over a period when tracing was off finds nothing for that period. Set up and schedule the trace scheduler first, or let a scheduled crawler manage its traces with Automatically manage trace.
- Trace content does not stay for long. SAP Cloud Integration keeps traced message content for about an hour. Crawl soon after the traffic you want to capture.
- Running by hand ignores the active flag. You can still click Execute on an inactive configuration. If its auto-stop folder is still at the limit, that run stops at once again with Limit Reached.
- The auto-stop count can lag a little. The folder's test-case count is refreshed periodically, so a run right after a large import may still see the previous count.
- The auto-stop guard cannot be removed by clearing the fields. On a saved configuration, clearing both limit fields keeps the previous values. Raise the limit instead, or copy the configuration and leave the fields empty on the copy. If the watched folder is deleted, the configuration can only be saved again after you pick a new folder.
- Saving restarts the schedule. Every save of a configuration with a schedule recalculates the next run, sets the schedule back to active and restarts the count of completed occurrences — relevant when the schedule ends after a maximum number of occurrences.
- Only the schedule owner can save a scheduled configuration. While a schedule is attached, saving any change also saves the schedule, which only its owner may do. Users allowed to change schedule owners can pick themselves as owner first.
- Scheduled runs need the owner's permissions. If the owner loses the right to run the configuration, scheduled runs stop until the schedule is assigned to someone who can.
- Runs cannot be cancelled. A started run always runs to the end.
- Configurations have no version history. Changes are recorded in the change history in Admin, but there is no way to restore an earlier state automatically.
- Configurations are not assigned to a project scope. Configurations created here carry no project scope, so the trace configuration permissions that apply are the ones your role grants without a project scope.
Related features
- Trace Scheduler Runs — the history and results of every run.
- Crawlers — turn traced messages into test cases, with optional automatic trace management.
- Systems under test — set up the SAP Cloud Integration connection.
Prerequisites & permissions
About permissions. What you can see and do is decided by the roles assigned to your user. Each role bundles permission groups, and each permission group allows activities — Read, Write, Delete, Execute and, for schedules, Change owner — on a kind of record (for example Test Case, Automation Object, System Under Test). A role grants its groups per project scope, so you may be allowed to change records in one project but only view, or not see, those of another.
If a button is disabled, a page says you don't have access, or a list comes back empty, missing permissions are the most likely cause — or, for whole product areas, the installed licence. You can review your own access under Profile → My access; an administrator can change your roles under IAM → Users.
To open this page you need Trace Configuration: Read. Additional permissions unlock specific actions:
- Trace Configuration: Write — create, copy and edit configurations. Saving also requires System Under Test: Execute on the chosen system and, when an auto-stop folder is set, Folder: Write on that folder.
- Trace Configuration: Execute — run a configuration by hand, together with the same system and folder permissions.
- Trace Configuration: Delete — delete a configuration.
- Trace Configuration Schedule: Write — attach or change a schedule, on top of everything needed to run the configuration. Trace Configuration Schedule: Delete is needed to remove a schedule, and Trace Configuration Schedule: Change Owner to assign it to another user.
The list shows all configurations; opening one also requires the permission for the configuration's project scope.