Integration of Independent Applications and EAI Systems using Service Oriented Enterprise Bus and Open System Application Development Standards

Transcription

1 I.J. Information Technology and Computer Science, 2013, 07, 1-11 Publihed Online June 2013 in MECS ( DOI: /ijitc Integration of Independent Application and EAI Sytem uing Oriented Enterprie Bu and Open Sytem Application Development Standard Quit-Apheti Keter, MIEEE Lecturer at the Faculty of Informatic, Ghana Technology Univerity College Dr. Koumadi Koudjo M Lecturer at the Graduate School, Ghana Technology Univerity College kkoumadi@gtuc.edu.gh. Prof. Nii.Narku Quaynor Profeor, Department Computer Science and Information Technology, Univerity of Cape Coat Abtract Buinee today are dependent on cutom enterprie oftware and web application from independent oftware developer and oftware companie. Thi create a lot of problem uch a integration, interoperability, ecurity, and ytem maintenance. Enterprie Application Integration (EAI) and Buine-to-Buine integration control everal key technologie and wift advancement in technology to meet the increaing need for integration in the enterprie which often reult in a lot of challenge due to difference between one proprietary approach and another. Thi paper eek to provide an approach of integrating independent application and EAI ytem by uing Web ervice tandard and open application development tandard in dealing with the challenge faced in integrating application. Thi will make it poible for organization to add a new layer of abtraction that i open, tandard-baed, and eay to integrate with any new or exiting ytem and alo make eay for data dicovery a well a building of new concept from exiting data. The combination of Oriented Architecture and Web ervice will be ued to provide a rapid integration olution and alo publihing ervice in a manner that new concept can eaily be built from exiting ervice. Index Term Integration, Interoperability, Oriented Architecture, Open Sytem Application, Enterprie Application Integration I. Introduction Enterprie Application Integration (EAI) i the proce of linking different application together within a ingle organization or acro organization boundarie in order to implify and automate buine procee to the greatet extent poible, while at the ame time avoiding having to make change to the exiting application or data tructure. In the word of the Gartner Group, EAI i the unlimited haring of data and buine procee among any connected application or data ource in the enterprie [1]. A corporate dependence on technology ha grown more complex and far reaching, the need for a method of integrating diparate application into a unified et of buine procee ha emerged a a priority. Uer and buine manager are demanding that eamle bridge be built to join them. In effect, they are demanding that way be found to bind thee application into a ingle, unified enterprie application. The development of Enterprie Application Integration (EAI), which allow many of the tovepipe application that exit today to hare both procee and data, allow u to finally anwer thi demand. [2] In today' enterprie infratructure, ytem and application integration i a critical concern. Enterprie Application Integration ha exited ince the early 2000, but the central problem that it attempt to olve i much older. EAI i an approach, or more accurately, a general category of approache, to providing interoperability between the multiple diparate ytem that make up a typical enterprie infratructure. Enterprie architecture, by their nature, tend to conit of many ytem and application, which provide the

2 2 Integration of Independent Application and EAI Sytem uing Oriented Enterprie Bu and Open Sytem Application Development Standard variou ervice the company relie upon to conduct their day to day buine. A ingle organization might ue eparate ytem, either developed in-houe or licened from a third party vendor, to manage their upply chain, cutomer relationhip, employee information, and buine logic. [3] Oriented architecture (SOA) ha gained popularity in recent year due to it enabling functionality or ervice to upgrade and extend exiting oftware application. SOA i an architectural approach to build and deploy oftware application that i interoperable by deign.soa ha grown a companie endeavor to leverage their exiting client bae and to integrate their acquired oftware with their client exiting ERP ytem and alo it make oftware connectivity capabilitie very eay. Unlike EAI no middleware i needed a adoption of tandard enable ervice to interact directly. It alo enhance reuability capacity of oftware, reulting longer life of exiting aet. A ucceful SOA implementation make it eaier to cutomize and upgrade exiting application thereby reducing total cot of ownerhip. [4] EAI product prove to be expenive, conume coniderable time and effort and are ubject to high project failure rate. Additionally, becaue thee cutom application are proprietary, many of the project reult in additional difficultie. Importantly, modification to uch application require developing almot the entire ytem from cratch. Recent experience how that a better anwer i available by uing Web ervice tandard. The adoption of ervice oriented Architecture and web ervice provide a rapid olution to olving thi problem faced by organization [5] [6] [7]. The paper ha the following tructure: ection II conit of related work, ection III give information on the methodology, ection IV dicue the approach ued for the integration, V talk about implementation a well a reult and concluded the paper. II. Related Work Enterprie application Integration enable an enterprie to integrate it exiting application and ytem and to add new technologie and application to the mix. Enterprie organization mut weigh the cot of replacing exiting ytem with new ytem againt the cot of merging exiting ytem with new ytem. Dicarding exiting ytem i never an eay choice: companie have inveted huge um of money to intall, ue, and cutomize thee ytem. Not only are their peronnel comfortable with uing thee ytem, even if the oftware i rife with drawback, but often the company' way of doing buine ha evolved to fit with thee ytem. It i difficult to jut walk away from uch an invetment. Likewie, bringing in a replacement ytem ha it cot: there' the purchae price of the new ytem, plu the training and cutomization cot. The invetment in the new ytem can be a large, if not larger, than the invetment in the exiting ytem [8]. Prior to EAI, integrating application and data within a corporate environment wa an expenive and riky propoition. Companie were trying to merge application that often ran on different hardware platform and had no protocol for communicating with other oftware package outide of their own narrowly defined realm. In a ene, companie had iland of buine function and data, and each iland exited in it own, eparate problem domain a hown in figure1 [8]. Fig. 1: A Typical Enterprie Domain Prior to the development of EAI-type approache, the problem of integration were largely handled uing point-to-point integration. In a point-to-point integration model, a unique connector component i implemented for each pair of application or ytem that mut communicate. Thi connector handle all data tranformation, integration, and any other meaging related ervice that mut take place between only the pecific pair of component it i deigned to integrate. When ued with mall infratructure, where only two or three ytem mut be integrated, thi model can work quite well, providing a lightweight integration olution tailor-made to the need of the infratructure. However, a additional component are added to an infratructure, the number of point-to-point connection required to create comprehenive integration architecture begin to increae exponentially. A threecomponent infratructure require only three point-topoint connection to be conidered fully integrated. By comparion, the addition of jut two more component increae thi number to 10 connector. Thi i already approaching an unmanageable level of complexity, and once an infratructure include 8 or 9 component ytem, and the number of connection jump into the 30, point-to-point integration i no longer a viable option. Each of thee connector mut be eparately developed and maintained acro ytem verion change, calability change, and more (or, in ome cae, even purchaed at high cot from a vendor), and the unuitability of point-to-point integration for complex enterprie cenario become painfully clear.[3]

3 Integration of Independent Application and EAI Sytem 3 uing Oriented Enterprie Bu and Open Sytem Application Development Standard Thee EAI-type approache face a lot of problem over time: The data exchange among different ytem i inevitable during the proce of Enterprie Application Integration. Coniderable quantitie of data would probably be migrated from one ytem to another after a fixed period of time. Under other circumtance, data repreenting buine tatu in one ytem are required to keep ynchronized with that on other ytem imultaneouly [9]. A in AllBook, in the vat majority of cae the computer ytem upporting the internal functioning of the enterprie have been developed independently to manage the tak of individual buine unit. Exiting ytem manage their own data, following their own data model and governed by their own buine rule. Thi lead to the technical problem experienced by AllBook International, in which application are not able to communicate with each other with the reliability and efficiency eential to afely implement the complex buine procee of a modern enterprie. Thi reulted in technological difficultie a a reult of ad-hoc integration olution, uch a remote call, direct reading and writing to application pace, or bridge and file tranfer ued for communication. In addition, application cannot eaily exchange information a the format and repreentation of enterprie data are different, and therefore numerou complex individual interpretation are required [10]. Figure 2 and Figure 3 depict the actual ituation at a major Autralian bank in the mid 90 and 2004 repectively. The boxe repreent application, with arrow or line howing their point-to-point interconnection. A comparion of the two figure how that not only the problem ha not been olved over the period, but that it may have actually become even wore. The dilemma for the bank analyt i how to properly manage the development maintenance and evolution of thee ytem. It i difficult to determine what i to be hared between application. But the ue of point-to-point interface reulted in a myriad of interface format and technologie that have to be created and maintained; making it very difficult to accommodate the new application that will be inevitably required. [10]. With the introduction of the Web, enterprie application integration ha taken on a larger ignificance beyond that of merging application ytem. Enterprie erver now handle and maintain huge amount of data and buine logic. The Web enable eay information and ervice acce and it ha become a principal mean of communication. An enterprie mut be able to make it buine data acceible to other, from internal employee to external partner, upplier, and buyer. Figure 4 illutrate thi Web direction to which enterprie are currently moving. The ucce of the Java programming language and the J2EE platform are play a key role in a Web-driven application integration, in large part becaue they make it eaier to develop and implement Web-baed application. [8] Fig. 2: A Typical Enterprie Domain Fig. 3: The ituation in a major Autralian bank-ii A buinee etablih Web preence, Web-driven EAI become more eential. Enterprie need to integrate their exiting application and enterprie ytem to drive their buine-to-conumer and buine-to-buine interaction, plu their other Web ervice. Succe in e-buine i driven by an enterprie' ability to integrate exiting application and extend the reach of thee application to Web-baed acce. [8] Primarily, ervice are implemented a (WS) which are defined by the W3C a oftware ytem deigned to upport interoperable machine-tomachine interaction over a network [11].It ha an interface decribed in a machine-proceable format. Other ytem interact with the Web ervice in a manner precribed by it decription uing SOAPmeage, typically conveyed uing HTTP with an XML erialization in conjunction with other Webrelated tandard [11].

4 4 Integration of Independent Application and EAI Sytem uing Oriented Enterprie Bu and Open Sytem Application Development Standard Fig. 4: Web-driven Application Integration Inherently, a ervice i a oftware component that contain a collection of related oftware functionalitie reuable for different purpoe. It deliver uch operation a data torage, data proceing, mathematical and cientific computation, and networking. It i governed by a producer-conumer model in which a ervice i delivered by a ervice provider known a the producer which own the facilitie for hoting, running, and maintaining the ervice, and the client known a the conumer which connect and ue ervice functionalitie. [12]. Much of the reearch regarding SOA tackle more granular technical iue of development and implementation of Web ervice, which may be a reult of the aforeaid miconception [7]. Few paper e.g., [13],[14], deal with the much larger problem of defining what SOA mean to the organization and how thi definition hould then provide the guidance for the development of component to meet buine information need[15]. The Information Technology adoption literature targeting a methodology for development tate that there are five categorie of factor influencing the deciion to adopt SOA (i.e., environmental, organizational, individual, technology, and tak characteritic [16]. Thee ame factor hould be addreed by the methodology for implementing SOA project [17]. Two SOA methodologie that attempt to embody ome or all of thee factor are dicued below. Teti (2006), an indutry analyt, provide a methodology, which entail creating a viion, contruction, and execution. He ugget that thi model i applicable to many project, but pecifically addree SOA. The viion creation i driven by a number of inter- and intra-organizational iue that define tak important to the individual and the firm (i.e., the contituency); the contruction addree the technology required to accomplih the tak; and execution eek to enure that SOA will facilitate information exchange in the environment. Bell (2008) provide a SOA methodology that take a more technical approach. It profee that all oftware can be conidered a ervice that are deigned baed on the informational tak of the organization, configured for tranmiion in the working environment, contructed with available technologie, and deployed for ue by individual. The methodology repreent a conceptual tructure that bring together ditributed ervice baed on the functionality [18]. A tudy of the Government of Ghana Minitry Integration project wa carried out by Keter et al (2012) where SOA with web ervice wa ued to demontrate the integration of eight minitrie. The exiting ytem within the minitrie were uing a variety of architectural model, language and platform that were not compatible with each other. On the other hand, the Government wa not ready to put in place a new IT infratructure to replace the exiting one. But the aim of the IT project wa to connect all the minitrie uch that they can interoperate and provide ervice to each other and alo create a new platform where new ervice in the future can be added without changing the entire ytem. The application wa developed from the propoed ytem architecture which aimed at providing interoperability functionalitie through rich Internet client and XML for all the minitrie. [19] III. Methodology Providing ervice through the Web i rapidly becoming the emerging trend. Enterprie are recognizing that it i important for them to provide more of their ervice, uch a cutomer upport and product catalog, through the Web. Enterprie have come to ee that having uch ervice available both in a traditional manner and over the Web enhance their buine. The technology cenario i evolving at a breathtaking pace, and EAI i now increaingly being driven by Web-driven requirement and technologie. Web-driven application integration, by making data and ervice more eaily and widely acceible enhance efficiency in buine procee. For example, an online tock trading application offered by the financial ervice indutry mut be able to handle tranaction whoe number can increae rapidly. It i bet, too, if the enterprie can retain the flexibility to develop and add in new application and extend it exiting application. Up till now, application were claified a either front-office or back-office application. Frontoffice application are conidered to face the cutomer or end uer. Front-office application include application for cutomer relationhip management and marketing automation. Back-office application provide the information infratructure for running the back-end buine procee of an enterprie. Application provided by an enterprie reource planning (ERP) ytem are good example of back-office application. Traditional EAI focued on integrating the front- and back-office application. However, traditional EAI i becoming Web-driven EAI. Rather than being targeted to the front end or the back end, mot EAI application are now integrated for the front and back end and Web

5 Integration of Independent Application and EAI Sytem 5 uing Oriented Enterprie Bu and Open Sytem Application Development Standard enabled. Jut a it i imperative for an enterprie information ytem (EIS) to move to a Web-baed architecture, enterprie application need to be deployed on widely adopted tandard application platform. [8] SOA with web ervice change the way buinee are undertaken and it i a technique of deign that guide all apect of creating and uing buine ervice throughout their lifecycle Thu, from their conception to their retirement [1]. And alo in defining and conditioning the IT infratructure that allow different application to exchange data and participate in buine procee regardle of the operating ytem or programming language underlying thoe application [20]. SOA i eentially a collection of ervice which communicate with each other. With SOA, buine ervice are conitently repreented and partitioned cleanly. The Web ervice alo upport interoperable machine-to-machine interaction over a network through an interface decribed by the Web Decription Language (WSDL) [21]. The ervice are the fundamental unit of the architecture for haring buine information acro department and application boundarie [22]. Thi paper eek to provide an approach of integrating independent application by uing Web ervice tandard and open application development tandard in dealing with the challenge faced in integrating application. Thi will make it poible for organization to add a new layer of abtraction that i open, tandard-baed, and eay to integrate with any new or exiting ytem and alo make eay for data dicovery a well a building of new concept from exiting data. The combination of Oriented Architecture and Web ervice will be ued to provide a rapid integration olution uch that the ytem can interoperate and provide ervice to each other, a well a provide an avenue for addition of new ervice in the future by interconnecting with other ervice without changing the entire ytem and alo publihing ervice in a manner that new concept can eaily be built from exiting ervice. However in high hope of achieving thee aim, the exiting IT infratructure will not be replaced by a new one due to extenive invetment made in the exiting ytem. Thi i becaue they have an enormou amount of ueful data tored in them, o it' not practical to dicard exiting ytem. The approach that will be ued will meet the requirement of IT project by making application to be more compoed of ervice rather than writing code from cratch. The approach will ave code and provide a tandard way for each of the component of an IT ytem to interact with hared ervice, enable component to become building block for reue, hift focu to application aemble rather than deign, create new application out of exiting component and integrate application ytem both internally and externally. SOA with web ervice will be ued for the entire proce of building and deploying the application for the project. Thi effectively lower the overall cot and improve the ability to rapidly change and evolve IT ytem within an organization. The approach will alo facilitate the compoition of ervice acro diparate piece of oftware, whether old or new; departmental, enterprie-wide, or inter-enterprie; mainframe, mid-tier, PC, or mobile device, to treamline IT procee and eliminate barrier to IT environment improvement within and outide organization [22] IV. The Approach The approach ued wa to get all the independent ytem reiding within each organization connected o that they can eaily exchange data irrepective of the platform upon which they are running on and make the ervice available for uage by external ytem during tranaction. A multi-layer architecture approach wa ued to develop a client-erver ytem to make information proceing poible within the organization and alo making ome ervice acceible. The architecture of a client erver ytem coniting of Web brower, ervlet middleware and databae erver for proceing tranaction wa developed and ervice publihed in the ervice bu. Some end-uer application were developed uing HTML form for uer-input and thi lower the data requirement of the client' brower verion and it doe not impoe the requirement of a Java-enabled brower with the latet JDK patch. A middle tier with a Web erver running Java ervlet wa et up and the Java ervlet wa ued to acce the databae with JDBC driver. A back-end databae erver wa et up and Web ervice were developed to make it poible for external organization to requet for information from the databae through the internet. Web ervice with SOA wa ued to provide an open tandard and machine-readable model (WSDL) for creating explicit, implementation-independent decription of ervice interface and communication mechanim that are location-tranparent and interoperable. For complexity and unreliability of integrating complex infratructure uing a point to point approach to be taken care of, a middleware will be ued to centralize and tandardize integration practice acro the entire infratructure. A eparate connector to connect each application requiring, component in an EAI-baed infratructure ue tandardized method to connect to a ervice bu (SOA) that i reponible for providing integration, meage brokering, and reliability functionalitie to the entire network. The ytem bundle together adapter for connectivity, data tranformation engine convert data to an appropriate format for uage by requeter, modular integration engine handle many different complex routing cenario imultaneouly, and other component preent a unified integration olution. A central integration

6 6 Integration of Independent Application and EAI Sytem uing Oriented Enterprie Bu and Open Sytem Application Development Standard mechanim wa ued to further conolidate tak. Thi create more room for a more flexible architecture, where new component can be added and removed a needed, by changing the configuration of the provider by imply developing modular component making a ingle ervice to be eaily re-ued by multiple application. Requetor Provider upport for uch functionality a a rule engine, intelligent meage routing, and meage tranformation, all on top of the bae functionality provided by the application erver. The buine proce layer erve a the top-mot layer for the platform and repreent an enterprie' unique way of doing buine. Thi buine proce layer expoe buine proce level abtraction by providing upport for buine proce modeling and for the buine proce engine. Buine Proce Layer Buine Proce Modeling Buine Proce Engine requet infratructure Data warehoue infratructure infratructure Fig. 5: Web enabled ytem for provider and requetor Integration Layer Buine Proce Modeling Intelligent Routing Rule Engine Meage Tranformation Application Development Tool and Framework In the figure above, language and protocol were tandardized to eliminate the need for many different middleware infratructure and the interaction were baed on protocol redeigned and the internal functionality etting were made available a a ervice. -oriented architecture ha tandardization a a key policy in implementing web ervice for eay integration of multiple incompatible application. Web ervice provide an entry point for acceing local ervice and with homogeneou component that reduce the difficultie of integration. Web ervice were expoed through the interface the functionality performed by the internal ytem and thi make the ervice dicoverable and acceible through the Web in a controlled manner(figure 5) and (Figure 6). Homogeneou component were built to reduced the difficultie of integration and tandardized. decription wa made richer and more detailed, covering apect beyond the ervice interface. The application integration in environment encompae three layer: a buine proce layer, an integration layer, and an application erver layer (Figure 6). Each layer, in turn, hold technologie that erve a the application erver integration building block. The application erver layer enable an application integration project to link not only with exiting enterprie ytem but alo with the Web. The application integration platform add an integration layer on top of application erver. Thi integration layer provide upport for application development tool and framework. Thee development tool and integration framework are baed on the application programming model, and they rely on metadata for generating and providing ervice. The integration layer alo add Application Server Layer XML Support Web Component container Aynchronou meaging Web Communication Protocol Fig. 6: Application Integration Layer Directory XML Meaging Tranaction Security Connector To integrate application at the buine logic layer, ytem were enabled to conume and provide XMLbaed Web ervice. The Decription Language (WSDL) contract were ued to decribe the interface to thee ytem. And interoperability wa further made poible by making the implementation compliant with the pecification. Figure 8 howed Oriented Integrated architecture of Enterprie reource. The Enterprie Reource and Operational Sytem conit of exiting application, legacy and COTS ytem, CRM and ERP application, and older OO implementation. Integration provide acce to the reource and ytem of Enterprie Reource and Operational Sytem and the component wrap integration ervice and provide a ingle point of contact for integration ervice. Buine repreent a logical grouping of

7 Publihed Integration of Independent Application and EAI Sytem 7 uing Oriented Enterprie Bu and Open Sytem Application Development Standard component, integration ervice and operation and alo provide high level buine functionality throughout the enterprie a well a provide a ervice interface layer of abtraction to the functionality of component and Integration. Buine Procee a a erie of activitie executed in an ordered equence according to a et of buine rule (called a choreography or buine proce model) and buine event. Buine Procee Buine Component and Integration Enterprie Reource Middleware Fig. 8: Oriented Integrated Architecture Company A Middleware Company B Company C Middleware Fig. 7: Web enabled ytem for provider and requetor Fig. 9: Integrated Sytem via a Bu With integrated enterprie ytem, buinee can now focu on core competencie, reduce pending, and reue exiting information in new way without a major overhaul of their exiting infratructure. Thi will help them to have flexibility in their ervice delivery, ave cot, and be efficient in ervice delivery. Figure 9 illutrate the dynamim of platform interoperability and intercommunication of between integrated ytem via a Bu. The metadata of a regitry network wa tored in an ontology way and publihed for eay data dicovery making it eay for earche to be done to find partner

8 8 Integration of Independent Application and EAI Sytem uing Oriented Enterprie Bu and Open Sytem Application Development Standard with product baed on price range or availability, or to find high quality partner. Thi made it poible for application, buinee, partner and upplier to analyze information about the regitrie and their characteritic to effectively carry out the proce of ervice dicovery. V. Reult The implementation wa done by building a 3-tier databae application that ue Java ervlet and the Java Databae Connection (JDBC). The three tier conit of Client Tier or uer interface, Middle Tier or buine logic and Data Storage Tier. The three logical tier were implemented to correpond to three type hot namely: the brower or GUI Application to erve the client, Web Server or Application Server and the Databae Server (often an RDBMS or Relational Databae). Servlet wa ued for creating HTML uer interface page. The ervlet JavaBean were reponible for buine logic and Java clae reponible for data acce. Thee object ued were JDBC to query the databae. The HttpServlet cla provide method, uch a doget and dopot, for handling HTTP-pecific ervice. The web client conit of two part: Dynamic web page containing variou type of markup language uch a HTML and XML, which are generated by web component running in the web tier and web brower, which render the page received from the erver. The application client directly acce enterprie bean running in the buine tier. The client interact with Java EE erver, enabling the Java EE platform to interoperate with legacy ytem, client, and non-java language. The buine tier compriing the buine component and entailing the buine code, which i the logic that meet the need of a particular buine domain, i handled by enterprie bean running on the buine tier. The enterprie bean receive data from client program, procee it and end it to the enterprie information ytem tier for torage or end it back to the client program. The enterprie information ytem tier handle EIS oftware and include enterprie infratructure ytem, uch a enterprie reource planning (ERP), mainframe tranaction proceing, databae ytem, and other legacy information ytem. The Java EE application component might accee the enterprie information ytem for databae connectivity. The HTML form for uer-input receive input for a form. The form i proceed by a ervlet which reide in a Tomcat erver after it ha been filled and ubmitted by a uer. The middle tier wa developed with a Web erver running Java ervlet which accee a databae and return an HTML page liting the data. Each field on the form tore information that can be tranmitted to the web erver and then ent to a Java ervlet. Web brower then communicate with the erver by uing HTTP. After a uer fill the form and ubmit it, the form data i then ent to a erver uing two kind of HTTP requet: get and pot. Java ervlet handle both of thee requet through method inherited from the HttpServlet cla: doget(httpservletrequet, HttpServletRepone) and dopot(httpservletrequet, HttpServletRepone). The doget() and dopot() method have two argument: an HttpServletRequet object and an HttpServletRepone object. The ervlet communicate with the uer by ending back an HTML document, a graphic file, or other type of information upported by the web brower. It end thi information by calling the method of the HttpServletRepone cla. Fig. 10: Architecture of JDBC A MySQL back-end databae erver wa et up in order for the java ervlet to acce information in the databae uing JDBC driver exited. The JDBC i a java API for connecting program written in java to relational databae. It ha a data acce interface, aee many data ource and perform common tak like connection pooling, batch update and tranaction management. Above i the architecture of the JDBC. It i a two-tier architecture where the top level i viible to application program and the lower level conit of driver for individual engine. The general tep taken in etting up the back-end databae erver are a follow: Importing the package Regitering the JDBC driver Opening a Connection to the Databae Creating a Statement Object Executing a Query and Returning a Reult Set Object Proceing the Reult Set Cloing the Reult Set and Statement Object Cloing the Connection

9 Integration of Independent Application and EAI Sytem 9 uing Oriented Enterprie Bu and Open Sytem Application Development Standard Below i the connect cla code nippet implemented for connecting to the MySQL relational databae back-end erver and a querydatabae cla for querying the databae. public cla Connect { public tatic void main (String[] arg) { Connection conn = null; try { String uername = "quit"; String paword = "keter"; String url = "jdbc:myql://localhot/backenderver"; Cla.forName ("com.myql.jdbc.driver").newintance (); conn = DriverManager.getConnection (url, uername, paword); Sytem.out.println ("Databae connection etablihed"); } catch (Exception e) { Sytem.err.println ("Cannot connect to databae erver"); } finally { if (conn!= null) { try { conn.cloe (); Sytem.out.println ("Databae connection terminated"); } catch (Exception e) { /* ignore cloe error */ } }}}} import java.ql.*; import java.util.*; public cla querydatabae { public Vector requetinformation() { Connection conn = getmysqlconnection(); Vector<String> repone = new Vector<String>(); try { Statement t = conn.createstatement(); ReultSet rec = t.executequery( SELECT * FROM curricula ORDER BY RAND() LIMIT 1 ); if (rec.next()) { repone.addelement( ok ); repone.addelement(rec.getstring( url )); repone.addelement(rec.getstring( title )); repone.addelement(rec.getstring( decription )); } ele { repone.addelement( databae error: no record found ); catch (SQLException qe) { repone.addelement( databae error: + qe.getmeage()); } } private Connection getmysqlconnection() { Connection conn = null; The web ervice were created to enable external ytem to requet for information from internal ytem. Beide SOAP, One of the mot popular technologie in creating web ervice i XML-RPC, a protocol for uing Hypertext Tranfer Protocol (HTTP) and Extenible Markup Language (XML) for remote procedure call. An XML-RPC client i a program that connect to a erver, call a method on a program on that erver, and tore the reult. Uing Apache XML-RPC, the proce i comparable to calling any other method in Java becaue we don t have to create an XML requet, pare an XML repone, or connect to the erver uing one of Java networking clae. In the org.apache.xmlrpc package, the XmlRpcClient cla repreent a client. An XmlRpcClient object can be created in three way, each of which require the URL of the erver: n XmlRpcClient(String) Create a client connecting to an addre pecified by the String, which mut be a valid web addre (uch a or web addre and port number (uch a n XmlRpcClient(URL) Create a client connecting to the pecified URL object n XmlRpcClient(String, int) Create a client connecting to the pecified hotname To call the remote method on the XML-RPC erver, We called the XmlRpcClient object execute( String, Vector) object with two argument: n The name of the method n The vector that hold the method argument The name of the method wa pecified without any parenthee or argument. Following i the code nippet we ued to intantiate a new XML-RPC client and call the method: XmlRpcClient client = new XmlRpcClient( ); Vector param = new Vector(); Object reult = client.execute( keter.requetinformation, param); The execute() method return an Object that contain the repone. Thi object wa cat to one of the data type ent to a method a argument: Boolean, byte[], Date, Double, Integer, String, Hahtable, or Vector. Like other networking method in Java, execute() throw a java.net.ioexception exception if an input/output error occur during the connection between client and erver. There alo an XmlRpcException exception that i thrown if the erver report an XMLRPC error. At the end web ervice were expoed through the interface the functionality performed by the internal ytem and thi make the ervice dicoverable and acceible through the Web in a controlled manner. Homogeneou component were built to reduced the difficultie of integration and tandardized. The application integration in environment encompae

10 10 Integration of Independent Application and EAI Sytem uing Oriented Enterprie Bu and Open Sytem Application Development Standard three layer: a buine proce layer, an integration layer, and an application erver layer. Each layer, in turn, hold technologie that erve a the application erver integration building block. The application erver layer enable an application integration project to link not only with exiting enterprie ytem but alo with the Web. The application integration platform add an integration layer on top of application erver. To integrate application at the buine logic layer, ytem were enabled to conume and provide XMLbaed Web ervice. VI. Concluion Uing SOA with web ervice did not only reduce the management, maintenance time and cot but it alo reduce the amount of deployed code. Moreover, the architecture did not only erve a the blueprint for the ytem but alo the project team tructure, documentation organization, work breakdown tructure, cheduling, planning, budgeting, unit teting and integration. The architecture etablihed the communication and coordination mechanim among component. were created and they can be reued in multiple and alo new ervice and application can be created quickly and eaily ued with a combination of new and old ervice. Importantly, ervice were modeled independently of their execution environment. Reference [1] Gable, and Julie, Enterprie application integration, Information Management Journal, March/April, [2] David S. Linthicum (1999). Enterprie Application Integration p6. [3] Undertanding Enterprie Application Integration - The Benefit of ESB for EAI (2012). Available: [4] Enterprie Application Integration & Oriented Architecture (2012). Available: -application-integration-ervice-orientedarchitecture.htm [5] Prof. Paul A. Stramann.What i a Oriented Architecture - George Maon Univerity, November 19, 2007 [6] Quay H. Mahmoud, (2005). -Oriented Architecture (SOA) and : The Road to Enterprie Application Integration (EAI).Available: /oa html [7] Architecture Uage Scenario, W3C Working Group Note, H. He, H. Haa, D. Orchard, 11 February 2004 Available: [8] Rahul Sharma Beth Stearn Tony Ng (2001).J2EE Connector Architecture and Enterprie Application Integration.pp1-3. [9] Dongjin Yu et al.(2009) Oriented Enterprie Application Integration and it Implementation Baed on Open Source Software Proceeding of the Second Sympoium International Computer Science and Computational Technology(ISCSCT 09). p.229 [10] George Fernandez (2006), A Federated Approach to Enterprie Integration. Thei pp [11] Gloary, W3C, 2004, [online] [12] Builder, C., Banke, S., and Nordin, R., Command Concept: A Theory Derived from the Practice of Command and Control, RAND Corporation, [13] Ren, M. and K. Lyytinen (2008) "Building Enterprie Architecture Agility and Sutenance with SOA," Communication of the Aociation for Information Sytem 22(1), pp [14] Papazoglou, M. P., and D. Georgakopoulo, D. (2003) -Oriented Computing, Communication of the ACM, 46(10), pp [15] Schulte, S., Repp, N., Berbner, R., Steinmetz, and R. Schaarchmidt (2007) -Oriented Architecture Paradigm: Major Trend or Hype for the German Banking Indutry? Proceeding of the 13th America Conference on Information Sytem (AMCIS). [16] Teti, F. (2006) Develop a -Oriented Architecture Methodology, Databae Advior Magazine, (current Oct. 15, 2007). [17] Kwon, T. and R. Zmud (1987) Unifying the Fragmented Model of Information Sytem Implementation, in R.J. Boland and R. Hirchheim (Ed.), Critical Iue in Information Sytem Reearch, New York: Wiley. [18] Haine, M. (2007) The Impact of - Oriented Application Development of Software Development Methodology, Proceeding of the 40th Annual Hawaii International Conference on Sytem Science (HICSS). [19] Keter, Q. A., Gyankumah, G. N., & Kayode, A. I. (2012). Uing Standard for Dealing with Complexitie of Multiple Incompatible Application. International Journal of Information Technology, 4.

11 Integration of Independent Application and EAI Sytem 11 uing Oriented Enterprie Bu and Open Sytem Application Development Standard [20] Bell, M. (2008) -Oriented Modeling: Analyi, Deign, and Architecture, New York: Wiley. [21] XML Information Set, W3C Recommendation, J. Cowan, R. Tobin, 24 October 2001 Available: / [22] Ervin Ramollari1 et al. A Survey of Oriented Development Methodologie. The 2nd European Young Reearcher Workhop on Oriented Computing Author Profile Quit-Apheti Keter, MIEEE: i a global award winner 2010 (Firt place Winner with Gold), in Canada Toronto, of the NSBE Conulting Deign Olympiad Award and ha been recognized a a Global Conulting Deign Engineer. He i a PhD tudent in Computer Science. The PhD program i in collaboration between the AWBC/USFC Academic Without Border/Univeritaire San Frontiere (formerly AHED-Academic for Higher Education and Development) Canada and the Department of Computer Science and In-formation Technology (DCSIT), Univerity of Cape Coat. He had a Mater of Software Engineering degree from the OUM, Malayia and BSC in Phyic from the Univerity of Cape Coat-UCC Ghana. He ha worked in variou capacitie a a peer reviewer for IEEE ICAST Conference, lecturer and Head of Comput-er cience department. He i currently a lecturer and Head of Digital Forenic Laboratory Department at the Ghana Technology Univerity. Prof. Nii Narku Quaynor: i a Jonathan B. Potel Award Winner 2007 from the IETF (The Internet Engineering Tak Force) and a cientit and engineer who ha played an important role in the introduction and development of the Internet throughout Africa. He i a Profeor at the Univerity of Cape Coat Univerity, Ghana. He wa the director of ICANN for the African Region in 2000.Quaynor graduated in engineering cience from Dartmouth College in 1972 and received a Bachelor of Engineering degree from the Thayer School of Engineering there in He then tudied Computer Science, obtaining an M.S. from the State Univerity of New York at StonyBrook in 1974 and a Ph.D. from the ame intitution in He wa founding chairman of AfriNIC, a member of the United Nation Secretary General Adviory Group on ICT, member of the ITU Telecom Board, Chair and of the OAU Internet Tak Force, Preident of the Internet Society of Ghana, and member of the Worldbank Infodev TAP. Dr. Koumadi, Koudjo M: i a 2009 Wilke Award Winner BCS. He i the director of the International Intitute of Technology and Management (IITM), Togo and a lecturer at Ghana Technology Graduate School. He i a member of IEEE He had hi PhD in Telecommunication Engineering at the Advanced Intitute of Science and Technology (KAIST), in Daejeon Korea. Mater in Telecommunication Engineering at the Advanced Intitute of Science and Technology (KAIST), in Daejeon Korea and B.Sc in Telecommunication Engineering Beijing Univerity of Pot and Telecommunication in Beijing, China. He may be reached at kkou-madi@gtuc.edu.gh.