Monitor message processing and manage your integration artifacts and security material such like certificates and user credentials, for example.
This screen is the central dashboard that helps you to monitor your active scenarios and to monitor and manage all artifacts and data storages that are associated with your scenarios.
See also:
Display messages processed by SAP Integration Suite and analyze errors if message processing failed.
You can customize this section by adding or deleting tiles or by changing the filter settings for each tile. To change the filter settings of a tile, right-click the tile and select Edit. You can filter for the message status, for the time period in which the message has been processed, and for the related integration artifact. Click a tile to display more information on the messages that meet the filter criteria.
See also:
Did you know?
You can also access most entities represented on this screen by an OData V2 application
programming interface (API). You find the APIs and their documentation on SAP Business Accelerator Hub at: Message Processing Logs
.
Get an overview of integration artifacts, such as integration flows and value mappings, check out their deploy status and find more details for each artifact.
You can customize this section by adding or deleting tiles or by changing the filter settings for each tile. To change the filter settings of a tile, right-click the tile and select Edit. You can filter for the deploy status of the artifact and the artifact type. Click a tile to display more information on the artifacts that meet the filter criteria. You find then further details relevant to run your integration scenarios, such like integration flow endpoint addresses, for example.
For example, when you've deployed an integration flow, this screen is the place where you can check out the deploy status and find the endpoint address that a sender system requires to connect to the integration flow.
See also:
Did you know?
You can also access most entities represented on this screen by an OData V2
application programming interface (API). You find the APIs and their documentation
on SAP Business Accelerator Hub at: Integration Content
.
Manage various kind of data required to configure the security level of your scenario. In this section, you can manage objects used to specify secure connections of SAP Integration Suite and remote systems and to design scenarios that include digital signing and encryption of messages.
Furthermore, you can perform outbound connectivity tests.
In the various sections, you can manage:
Security Material
Artifacts such like User Credentials artifacts or OAuth2 Client Credentials Grant artifacts that contain the credentials and other data required to set up a secure outbound connection to a receiver system.
You can deploy new artifacts or edit existing ones.
Keystore
Keys uploaded to the SAP Integration Suite keystore. The keystore contains key pairs and certificates used for both inbound and outbound connections.
PGP Keys
Keys required to set up scenarios with digital encryption and signing based on Pretty Good Privacy (PGP).
Access Policies
Rules that allow you to restrict the access to integration artifacts and their associated data.
JDBC Material
Artifacts that define the secure connection of SAP Integration Suite with remote database systems (when you use integration flows with the JDBC adapter).
User Roles
Roles that allow you to restrict the access of sender systems to integration flow endpoints.
Connectivity Tests
Test tools that allow you to test the outbound connection of SAP Integration Suite to receiver systems (for the supported transport protocols).
See also:
Did you know?
You can also access most entities represented on this screen by an OData V2 application
programming interface (API). You find the APIs and their documentation on SAP
Business Accelerator Hub at: Security Content
.
Manage temporary data storages associated with your tenant. These are, for example, data stores (containing data that is used during the processing of integration flows), variables (used by integration flows), and JMS queues.
In the various sections, you can monitor and manage:
Data Stores |
Storage to which an integration flow step can write the message to make it available for subsequent steps in the same integration flow or for other integration flows. |
Variables |
Storage to which an integration flow step can write a variable value (such like a timestamp) to make it available for subsequent steps in the same integration flow or other integration flows. |
Message Queues |
Storage used by adapters such like the JMS adapter and the XI adapter. A message queue stores an incoming message temporarily and schedules it for processing. |
Number Ranges |
Storage for unique sequence numbers processed in scenarios using Electronic Data Interchange (EDI) message processing. Number rages help to detect and avoid message duplicates. |
Partner Directory |
Storage for partner-specific information used to parameterize integration flows in communication networks with numerous partners. |
See also:
Did you know?
You can also access most entities represented on this screen by an OData V2 application
programming interface (API). You find the APIs and their documentation on SAP
Business Accelerator Hub at: Message
Stores
.
Monitor and analyze errors that occurred during inbound HTTP processing (and documented in system log files).
See also:
Did you know?
You can also access most entities represented on this screen by an OData V2 application
programming interface (API). You find the APIs and their documentation on SAP
Business Accelerator Hub at: Log
Files
.
Display and manage lock entries that are created by the system to avoid the same message being processed several times in parallel.
Display and unlock integration artifacts and packages that are locked by the users of SAP Integration Suite.
See also:
Get an overview of the number of messages processed by integration flows during a selected time range.
Using this feature, you can find out, for example, which integration flows cause a high message throughput.
See also: