Search: "business"

Business case

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz. === 2.1 Business Case === **Read and understand the following business case** As Dream Inc., we supply custom-made dream events for our customer base.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Exercise == Below the exercises for this part of the crash course. === 2.1 Complete Capture phase OMS Carrier === Below are the results expected from this exercise: * Create the Capture phase based on the business case * Ensure to add the documents to the Capture phase at the right location ** [[Gateway reponse>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.gateway-response.WebHome||target="blank"]] ** [[System reponse>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.system-response.WebHome||target="blank"]] {{info}}Note that you should save the contents of the file as an XSD and attach it to each of the lines drawn in Capture{{/info}} === 2.2 Complete Capture phase OMS Order === Below are the results expected from this exercise: * Create the Capture phase based on the business case * Ensure to add the documents to the Capture phase at the right location ** [[Gateway Order Request>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.gateway-order-request.WebHome||target="blank"]] ** [[Gateway Order Reponse>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.gateway-order-response.WebHome||target="blank"]] ** [[Example message>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.example-message.WebHome||target="blank"]] {{info}}Note that you should save the contents of the file as an XSD and attach it to each of the lines drawn in Capture{{/info}} == 3.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

A crucial part of setting up your API Gateway with the help of RESTful services is knowing to which resources (e.g., Order, Client, Employee) you want to give external parties access to your business processes via your API Gateway. Let us explore the best practices and foundational concepts to effectively set up your API Gateway.

* 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 Resource (Paths) == This microlearning focuses on the theoretical part of HTTP Resources regardless of a specific implementation in eMagiz.

Backend systems, micro-services, or access to external systems can be published, so that internal development teams and applications can access the specific APIs as part of business process execution. A typical landscape could look like this.

* One of the first angles to consider an API Gateway is when the integration is synchronous. A business process is handled via a specific application, and that business process requires data from another (micro-)service and can only proceed once that response to that data request is returned successfully.

On the one hand, Sales Orders from external clients might be sent to the Gateway, or an internal microservice could be calling an API as part of a business process whereby the API reaches out to another (external) web service.

* 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. Finishing the Design Phase == In order to be able to move to the Create Phase and the Deploy Phase some steps need to be taken.

* With entry gate, we mean: The piece of functionality that hosts all endpoints and is responsible for checking the authentication and routing messages to the correct backend operation * 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. Setting up entry gate == When we talk about the API Gateway in eMagiz, the central part where all data traffic is coming in is called the entry gate.