JOURNAL OF COMPUTING, VOLUME 3, ISSUE 2, FEBRUARY 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.

COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG

158

Service Integration to CSOA Application: Bridge Interface between Service Provider and Consumer
Sheikh Muhammad Saqib1, Shakeel Ahmad1, Bashir Ahmad1, Muhammad Ahmad Jan1, Muhammad Zubair Asghar and Muhammad Javed1
1

Institute of Computing and Information Technology Gomal University, D.I.Khan, Pakistan

Abstract: Careful installation of a CSOA (Customized-SOA) application is not the satisfaction of end users. Users want new changes and needs in their own services. Integration of these services is the major problem. Because developers are on one side and users are on other sides. This problem may occur due to software and hardware components incompatibility. BI (Bridge Interface) can solve these issues, if CSOA will have been made up of BOSM (Business Oriented Service Model). BI will integrate the new services or updated services to client machine only on request from user side without any confliction. For new CSOA application, each developer from different location can integrate developed services to actual application through BI. BI will work on the basis of contract between development companies and consumers.
Keywords: CSOA, BOSM, BI, Service

I. Introduction:
Comprehensive and separate description of the integration phase is required, if services or activities are developed Experiences in separate from locations. different

Integration problem can be solved but there is lack of experts in SOA. Standards are still a problem for ESB (Enterprise Service Bus) or even a meaningful definition. ESB is a special layer which delivers messages between applications. Integration in SOA is still an art to connecting the legacy systems [3].

organizations and companies compiled the different practices for integration [1]. Existing software may be failure due to day by day increasing graph of

technology. This software requires new features. Integration is the major

problems for these services.

Properly

Fig-1: SOA Work Flow
Since CSOA applications just provides the different services to each user according to their needs. These services are loosely coupled and can be

managing challenges i.e. maintaining commitment within the organization, managing the complexities of

distributed teams is the success for integration [2].

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 2, FEBRUARY 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG

159

developed every where. These services require purpose. a channel And for integrating after the

several business domain [4] [7]. Due to loosely coupled and services as black box, SOA has more importance in recent architectural graph. In SOA service is a unit of independent deployment and versioning. SOA architecture consist of a reference database of services (SOA Registry), a flow for services in SOA registry (Work Flow), reader for work flow (Service Broker), handling the service (SOA supervisor) [6].

also

implementation of CSOA application, there may be some issues can arise with respect to maintenance. As developers and users both belong to different places then integration of newly or updated services may cause the problem. BI (Bridge Interface) will communicate the issues between user side & development side and also install the new features or services to the client machine. After the development of CSOA applications by following BOSM a contract can be signed companies between and development side for

consumer

maintenance through BI.

II. Service Oriented Architecture:
Simply collection of services is known as service-oriented architecture. Data can be travel over these services or can coordinate some activities. Service-oriented architecture (SOA) is a flexible set of design principles used during the phases and of systems in

Fig-2: SOA Architecture

III. BOSM:
For proper management and utilizing the basic characteristics of SOA BOSM (Business Oriented Service Model) has been established. It is a development framework for analysis, design and construction of CSOA application which uses the best practices from Rational

development computing. In SOA

integration

based

applications

all

Unified Process Model and Service Oriented Modeling and Architecture.

functionality are packed in a suit, which can be used in separate system from

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 2, FEBRUARY 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG

160

BOSM consists of four phases i.e. BOSI, BOSS, BOSR and BOSD. Business Oriented Service Identification (BOSI) determines role of stack holders, reused & reusable services and worth of service with respect to future. Its user stories can be useful for estimating development cost. Business Oriented Service Specification (BOSS) uses coding standard and

IV. Bridge Interface (BI):
Since CSOA provides only logical services to end user (such as local messages, daily attendance etc), there must be an interface with development side for maintenance. BI will work if application is made up of BOSM. After the successful installation of

CSOA application, maintenance is the major and critical part of any model. Bridge Interface (BI) is the maintenance part of BOSM, which will be partially execute on user machine and partially execute on developer machine and will follow the same protocol. So user gets feel free to run and maintain CSOA application.
In te rn et

metaphor for creating functional and technical components. So any new developer can easily continue the work of existing developer. Business Oriented Service Realization (BOSR) determines exact matching of analyzed services with existing stored service, after adding the some changes if required, BOSR take a unit testing on those services and then plug-in to the system. Newly developing services will be shifted to next phase. Unit testing will reduce begs problem which can occur after the implementation. Business Oriented Service Deployment (BOSD), handover the product to Beta

Developer Machine I

User Machine

B

Fig-3: Bridge Interface Partially installed on Both Machine BI on consumer side will contain an interface for sending story card; story card is the ‘core practice and easy way for getting requirements’ of BOSI. This card will be sent to SOA registry, which will be the central storage place for both sides. SOA work flow and service

consumer after the beta testing.

testing is useful for enhancing the quality of product and real time

validation [5].

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 2, FEBRUARY 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG

161

broker will be activated on service provider side. Since on both sides there will be the same protocol so

will send this query to service broker with BOSI results such as availability, user story, business glossary, scope and its dependent services. Now developer will apply BOSS, BOSR & BOSD on this service and make the service as separate unit. After the creation of this service, SOA-supervisor will store this service in service library with its Manuel and plug-in this service to CSOA application on user machine through BI. And will send a signal to user, that service has been plug-in successfully.

communication will be reliable. In SOA work flow, BOSI will contain all

information about requested users so SOA-supervisor will check the validity then make the attention on sending service. It will check this service in

service library, if it will exist, then SOAsupervisor will plug-in this service to consumer side. If this service will not exist in library then SOA-Supervisor

Fig-4: Bridge Interface for solving CSOA-Integration problem

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 2, FEBRUARY 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG

162

V. Conclusion:
Problems, new changes, failure and exceptions can occur any time. Analyst can not stay over client side forever. Since in CSOA applications, services are loosely coupled. So any new service can easily incorporated in system. So BI will be the reliable mean between consumer and provider side for maintenance, if CSOA application is made up of BOSM. Through BI, consumer can send a new request in shape of story card. BI will determine its flow from BOSI and will send this work flow to next steps BOSS, BOSR and BOSD. After applying these phases, requested services will be

References:
[1] Stig Larsson,’ Software product integration: A case study-based synthesis of reference models’; Information and Software Technology,

Volume 51, Issue 6, June 2009, Pages 10661080, 2009 Elsevier B.V. [2] Rikard Land, ‘Software systems in-house integration: Architecture, processes practices, Information and and strategy Software selection’; Technology,

Volume 49, Issue 5, May 2007, Pages 419444, 2007 Elsevier B.V. [3] Eric Roch ,’Has SOA Solved EAI Problems?’ 2008 url: http://it.toolbox.com/blogs/the-soa-

blog/has-soa-solved-eai-problems-22411 [4] Douglas K. Barry,’ Service-oriented architecture (SOA) definition’; [5] MS-Thesis on Business Oriented Service Model: Coordination of SOA and RUP, Sheikh Muhammad Saqib 2011. [6] SOA : Service Oriented Architecture: url:http://www.dotnetspark.com/kb/271service-oriented-architecture-soaterview.aspx [7] Service-oriented architecture;

developed from existing or from scratch. Then this requested service will be automatically plug-in to consumer side.

http://en.wikipedia.org/wiki/Serviceoriented_architecture