Approach -1
Approach -2
Design Description
The above diagram gives a sneak preview of high-level implementation model of the proposal. The Service environment can have n- number of internal system running under IT department. It can be in a client environment either the client is providing services or an Environment provided by us, since we are the IT people.
Our scenario thinks about how the data can be shared across the proposed system by mean of certain rules it handles .For example, if the proposed system needs only limited information from the existing database it can be retrieved through Web services and using XML orchestration . Data synchronization Engine (DSE) enables the service to synchronize the data between the existing applications and proposed system .We can ensure the client that the data being secure with them by means of defined orchestration mechanism. Any client can communicate with DSE for sharing the data for services and can be getting a copy of the transaction made at service points. It enables a client to ensure on data security. The data base serves at service end always keep the necessary data for their transaction. This enables an application to retrieve the required data from their environment. A web service running at both ends can be used to orchestrate the transaction.
The application framework handles logistics needed for a client. We can place n number of logistic components (services) based on different domains here. Therefore, it enables n umber of clients to access it by looking up the rules generated by rule engine. These components eventually communicate to the data through Data Access Mechanism. Application Request Processing Engine (ARPE) makes the rule looking up the orchestration and decides which logistics must be tracked by means of a client call.
Any application running for any clients above this layer can make use of Application framework components by giving a request to the ARPE. This ensures security across multiple clients and their logistics. This can be configured by clients using a secure connection.
The above approaches differ in Data Access Mechanism. A client may not will to share the data at initial level. In this prospect, we can follow the first approach. The above given approaches are not being a full implementation of the new model. Any review comments will be added along with this.
Deployment Model
Description
Application Access Layer is any client system that supports internally or externally to a business process . It can be thick client application that accesses the data for verification or validation purpose. Or It can be just a internet based or thin client environment that make use of data. This need to have only limited configuration features
SOA Service layer, A layer that ensure a highly integrated and secure data handling mechanism to the client. It can be run at a service provider’s environment. Since we are the IT people we can ensure the data security and service privacy using latest technology. A client can ensure the security of both data and service through a secure data connection mechanism. We can ensure this through a secure connection mechanism. A client can have control over this by a defined rules signed by both client and service provider.
A temporary database/memory representation of data can be provided at service layer based on signed rules for better data security and dynamic data retrieval to the clients using modern database features.
A legacy system data can fetched here for faster transaction purposes and be can saved back to the client’s data centers periodically
Secure Data layer, This can be a legacy system data centers or atabases running on multiple environment at client side. Secure data transaction with service layer can be enforced by rule signed by both Service providers and client. Once the client is willing to share the data we can dynamically get the data from the data centers.
0 comments:
Post a Comment