So now we have discussed about the identification manager and we have also discussed about the internal
systems and we have seen that how identification manager will be used to provide identities or certificates
for all the different modules.
Now, internal systems are the core important aspects of your legacy or enterprise based system, and
these internal systems need to interact with your blockchain module and application module.
For those interaction capabilities, we provision the integration module.
Now let's go and learn about integration.
Module Integration module is used as a integration gateway between different internal systems and services.
These API services can be exposed for applications or for any internal system.
Most of the enterprises utilizes Enterprise Service Bus as a integration module.
Enterprise Service Bus enables the different applications to connect with each other and provide a common
ground for all these applications to operate continuously in synchronous.
There are many enterprise service bus tools available in the market.
Some of the primary tools are Biztalk Server Open, ESP and IBM integration bus.
The primary duties of an integration module is to route messages between different services.
It will also monitor and control the routing of messages and exchange between all the services under
enterprise solution.
Then it will also help you to communicate between service components.
Moreover, integration module will also help you to control the deployment and versioning of the services.
For example, if you are upgrading your internal systems, you might need to upgrade your integration
capabilities.
Also to make sure that your complete enterprise project is running smoothly.
It will also help you to remove the redundant services.
Integration module also provides some support services like event handling, data transformation message
and event queuing, sequencing security or exception handling protocol conversion or enforcing proper
quality of communication service.
This is a generalized view for the Enterprise Service bus.
This is related to the integration module.
As you can see, we have labeled the service flow data, existing applications and new service logic
below the Enterprise Service bus.
And on top of it we have the portals which are going to use the services.
We also have the soap service request which will help to integrate with J2 or Dotnet services.
And finally, we have a business to business interaction capabilities.
So all these different services and all these different data flows are connected to each other through
a common runtime environment which act as a enterprise service bus.
Here when we are dealing with the enterprise blockchain solution, this enterprise service bus will
be used to interact with the blockchain services.
So you will have your internal systems build up.
These internal systems are going to interact with the applications and blockchain services through the
Enterprise Service bus or any other integration service as per your project.
Now let's go and learn about blockchain modules, which are part of your conceptual view under architecture.