Search: "business"

A high percentage indicates that the CPU is very busy handling the message traffic of that process, which indicates that other processes handled by that same CPU(s) might experience delays or issues.

* With exit gate, we mean: The piece of functionality that connects to the backend operation to execute the action on behalf of the client that is calling the API * 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 The exit gate is created by eMagiz based on the configuration in Design.

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

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 and specify the security measures. === 3.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 securely. 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 best suits their needs. === 3.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.

When you want to create your systems, you need to ask yourself the following questions: * What systems are relevant in our business case? * What is the purpose of each system?

. * 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. HTTP Operations == A crucial part of setting up your (API) Gateway with the help of RESTful services is knowing what HTTP Operations are and how you can use them to control what parties can change via your (API) Gateway.

The advice is to shorten your display name to seven characters to represent the technical name and let the namespace URL reflect what your eMagiz model is about (i.e name of a business, organizational unit, etc.). An example of such a implementation would be: [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-project-settings--generic-project-settings.png]] === 3.2 Specific Settings === The specific settings could change over time as your integration landscape is growing leading to other decisions being made.

. * 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. When setting up your API Gateway integration the process of doing things is to start at the backend operation and based on that expose an operation in the API Gateway. == 3.

. * 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 linked to your business process. == 3. Swagger UI == The Swagger UI is a user interface that external parties can access via the browser to see the specifications of your API Gateway and test their solutions simultaneously.

Considering impact of downtime == In this microlearning, we will learn what you should consider determining the impact of downtime on the business. We will consider the impact when some specific part of the integration solution experiences downtime.