Search: "business"

* With securing we mean: Configuring a method that will be used to validate that the clients are who they say they are * With API Gateway we mean: A collection of RESTful API operations that can be published to the outside world to give them access to applications that are linked to your business process == 3. Security == While "security" is a broad term, this microlearning focuses specifically on the general security measures that ensure clients can prove their identity to the API Gateway, i.e., how clients should prove to the API Gateway that they are who they say they are.

. * With roles, we mean: Any action that is available to be executed on an internal system that you want to make publicly available via the API Gateway * With users, we mean: Any system or user that is granted access to such actions via the role * With API Gateway, we mean: A collection of RESTful API operations that can be published to the outside world to give them access to applications that are linked to your business process == 3. Configure roles and users == A crucial part of setting up your API Gateway with the help of RESTful services is defining which client has access to which operation.

In case consumers exist that need to read each message for a different usage or business process, you need to make sure that these Group IDs are different (each group ID has its own offset).

Based on the filter and the business requirements, whether to delete and when to delete could differ.

. === 3.3 How to get your key signed by a trusted party === In some cases, an external party with whom we do business asks us to manage the certificate but has the requirement that the certificate that we have created and manage needs to be signed by a trusted party before it can be used in the field.

Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).

Before we dive into the various scenarios, we would like to define some general remarks: * Make sure that your active release mimics what is currently running on an environment, as the upgrade will result in a clean slate based on the active release. * For business-critical processes, we advise stopping these processes before executing the upgrade * You will experience a short amount of downtime while executing this upgrade * Each scenario has some additional specific restrictions and considerations. ===1.1 Cloud Only=== If your complete solution runs in the cloud, you need to upgrade to the latest cloud template suitable for your model.

The advice would be to analyze whether the current heap memory settings are still valid ** If you see a decrease in heap memory slightly after the spike in CPU this is an indication that the runtime was temporarily busy with garbage collection (a standard process within Java) to free up memory.

//__Loading bar when searching for log entries__// To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search.

In case consumers exist that need to read each message for a different usage or business process, you need to make sure that these Group IDs are different (each group ID has its own offset).