Search: "business"

In the course, you'll pass through each of the Integration Life Cycle phases to create the integration from business intake to setting the alerts & monitoring triggers after the actual deployment of the integration.

Within eMagiz, there are three main integration patterns a user can configure to support their business case most optimally. First, this section will look at all three integration types in detail and specify the security measures. ==== 3.5.1 Messaging ==== Messaging is the most flexible option of the three; therefore, a wide range of options is available within eMagiz to secure the connections. eMagiz offers users the tools to set up integrations and end-points in a secure manner. eMagiz supports well-known market standards, including: * OpenID Connect * WS-Security * API Keys in combination with HTTPS/SSL * SOAP Authentication * OAuth2.0 * Basic Authentication This way, each connection between the application and the integration (end-point) can be adequately secured and gives the flexibility to confer with the external application which method suits their needs the best. ==== 3.5.2 API Gateway ==== A structure with roles and rights per role can be specified within the portal or via an external IDP to secure the front end of the API Gateway in eMagiz.

Topic and Topic Properties == Within the eMagiz platform, you can use the Event Streaming pattern to help solve your business case. A crucial part of that solution is the topics and the accompanying properties.

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

//__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).

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.