This paper explains briefly how the SOA implementation process and the description of the path stages of SOA

1. How the detailed process of SOA ?
SOA works like a charger for many functions, or in other words SOA builds an interface that
can be accessed by various software. So far, a software built by binding data and processing
tools in a series. Similarly, the increasing number of data traffic between software that will
increase the cost for its implementation. SOA technology is tasked to alleviate the problem
by reducing the barriers of integration between different platforms. To illustrate how SOA
works in a company or business institution, can take samples of goods purchased
transactions via the internet by a netter or customer. In an IT system retailer using a SOA,
online purchases of goods that trigger a series of other transactions. For example, the
customer's credit card is verified, the delivery department is notified, the warehouse is
requested to adjust the inventory, and the bookkeeping records are updated. These
transactions are inputs of information sent through different systems or software, which are
sometimes unsuitable and can not relate to one another. However, SOA technology has
enabled the infrastructure that supports such transactions to be integrated and combined
integrally.
Explanation of the image path of the architecture-oriented service process
below
The SOA architecture in the above image will be built using SCA modeling which describes
the components to be constructed with the following paths :
• Initially built Management Application & Console to process application and console
settings that will communicate with each other in the system.

2. • Furthermore, every application or console is registered in the Registry System and
distributed also to Metadata Repository which serves as a storage warehouse for the
application or console that will be used as a service
• For a collection of applications and consoles distributed by Management Application &
Console to Metadata Repository properly validated, the Registry System performs the
verification process to Metadata Repository, does each application and console contained
in Metadata Repository have been registered? this process is necessary for each
application or console can be used as a service by the user (customers)
• A collection of applications and consoles stored in the Metadata Repository will be called
in the Security Service process to ensure that the application and console are safe to use
as a service
• Any user, whether human (customer) or non-human (device) elements that will access
such applications and consoles, needs to connect with a dedicated mainframe displaying
services to touchscreen display media, servers that use both Net.Asp and J2EE.Asp
platforms
• Mainframe, Net.Asp platform server as well as J2EE platform server.Asp is connected with
ESB (Enterprise Service Bus) that manages the flow of messages across different
applications, orchestrates communications and allows a method to access data messaging
applications. This process is not for data integration but rather a messaging mechanism.
• The ESB (Enterprise Service Bus) is connected to the mainframe provider network, the
Net.Asp platform server and the J2EE.Asp platform server, which can then be accessed by
stakeholders outside the company through a data communication network of different
types (proxies, VPNs)
Explanation of the chart below
?