Business scenarios

Let's see 4 scenarios with the 3 phases and the relevant contract types.

Scenario 1 - Input, Mediation and Output contracts

Imagine an organization that needs to receive a zip file containing all the invoices issued by its branches throughout the country. Data Mover can access each branch repository every hour, retrieve the invoices issued in the last hour, create the zip file, and send it to the head office along with an email confirmation to a specific user.

Let's identify the actions associated with the three phases and define the corresponding contracts:

• Input phase: every hour, Data Mover connects to each branch repository (data producers) to get the files. An Input contract is needed.

• Mediation phase: files are zipped in Data Mover with a Mediation contract.

• Output phase: Data Mover sends the files to the head office (data consumer) and a confirmation via email to a user. An Output contract is needed.

This is the visual representation of the scenario:

A detailed description of how to implement this business scenario is available on the Create Input, Mediation and Output contracts page and sub-pages.

Scenario 2 - Input, Mediation and Connection contracts

This scenario is similar to the previous one. The difference is that instead of waiting for the zip files to be sent, the organization connects to Data Mover and collects the zip files with all the invoices issued by its branches. In this case, Data Mover must be configured to access the branch repository, retrieve the invoices issued in the last hour, create the zip file and store them in a specific folder. Then, the head office connects to Data Mover to collect the zip files.

In this scenario, these are actions associated with the three phases and the corresponding contracts:

• Input phase: at a regular interval, Data Mover connects to each branch repository (data producer) to get the files with an Input contract.

• Mediation phase: files are zipped in Data Mover with a Mediation contract.

• Output phase: Data Mover stores the zip files in a folder and sends the confirmation via email to a user. The head office (data consumer) collects the zip files. This is implemented with a Connection contract.

This is the visual representation of the scenario:

A detailed description of how to implement this business scenario is available on the Create Input, Mediation and Connection contracts page and sub-pages.

Scenario 3 – Connection, Mediation and Output contracts

Imagine an insurance company that must receive all policies issued by agencies nationwide by the end of the day. Files must be received in a specific format. Data Mover can receive these files from each agency, encrypt them, and create a zip file for each agency. Then, it can send the zip files to the insurance company.

In this scenario, these are actions associated with the three phases and the corresponding contracts:

• Input phase: the insurance agencies (data producer) connect to Data Mover and send the policies issued. A Connection contract is needed.

• Mediation phase: the policies are encrypted and zipped with a Mediation contract.

• Output phase: Data Mover sends the zip files to the insurance company (data consumer) with an Output contract.

This is the visual representation of the scenario:

A detailed description of how to implement this business scenario is available on the Create Connection, Mediation and Output contracts page and sub-pages.

Scenario 4 – Connection, Mediation and Connection contracts

This scenario is similar to the previous one. The difference is that instead of waiting for the zip files to be sent, the insurance company connects to Data Mover and collects the zip files with all the policies issued by its agencies. So, Data Mover receives the files from each agency, encrypts them, and creates a zip file for each agency, which it stores in a folder. Then, the insurance company connects to Data Mover to collect the ZIP files.

In this scenario, these are actions associated with the three phases and the corresponding contracts:

• Input phase: the insurance agencies (data producer) connect to Data Mover and send the policies issued. A Connection contract is needed.

• Mediation phase: the policies are encrypted and zipped, with a Mediation contract.

• Output phase: Data Mover stores the zip files in a folder and the insurance company (data consumer) collects the files. A Connection contract is needed.

This is the visual representation of the scenario:

A detailed description of how to implement this business scenario is available on the Connection, Mediation and Connection contracts page and sub-pages.