240 likes | 396 Views
Integration Broker at Cornell. Kevin Leonard CIT/Integration and Delivery May 9, 2002. Directory Integration. ADABAS (students). PeopleSoft HR (employees). Integration Process. SQL FTP Natural Pgms Perl scripts. Directory. Integration Broker is what?.
E N D
Integration Broker at Cornell Kevin Leonard CIT/Integration and Delivery May 9, 2002
Directory Integration ADABAS (students) PeopleSoft HR (employees) Integration Process SQL FTP Natural Pgms Perl scripts Directory
Integration Broker is what? Enables disparate systems to share information in common manner. The central control and storage point that mediates events to and from applications, managing the essential queuing, routing, filtering and storing of information in an reliable and secure manner.
Integration Brokers Vendors Gartner – Magic Quadrant IBM SeeBeyond Tibco Vitria webMethods Others Mercator SoftwareAG BEA Oracle
webMethods • Chosen because… • Features • Cost • Name is misleading… • It is an Integration Broker • The “web” part of the name makes people think it’s only for web access… untrue.
What can it do? • Just a few examples • Notice changes to PS data and apply the changes to the directory or student data • Notice changes to the directory data and apply the changes to PS or student • Notice data changes to any table or field in an Oracle or Informix database and publish events • Notice changes in flat files and process as appropriate
Goals When data is altered in our PeopleSoft system populate those changes to the Directory, without any changes to the PeopleSoft applications or the Directory software. Same for Student System. Provide an infrastructure to allow these types of interactions between other systems
Event Driven • Event driven • Integrations are built by a developer • When an event happens a process is triggered within the Broker • The process determines what happens, how data is transformed and moved from one place to another • Two phase commit is not available, must use a compensating transactions if back-out is desired
Broker • The Enterprise Server Broker is the main engine • Message repository when using guaranteed delivery • Data transformation • Event handling • Publish and subscribe • Synchronous messaging • “Near real time” updating
Adapters • Adapters are configured to interface with our infrastructure • PeopleSoft (via app server) • Directory (via LDAP) • Oracle • Informix • Student (via CUSSP) • File IO (flat files) • XML
Other Adapters • Adapters we haven’t purchased but may have interest in the future… • Email • JMS • JavaBeans • Vantive • Microsoft SQL • ODBC & JDBC
APIs • We’ll probably use these • Java • JMS • These are available, but we don’t have plans to use them today • C • CORBA
Certificate in use with SSL Security
Issues • Where is the starting point(data of record)? • What does the business process require to be done? • Should a workflow process be triggered on the event completion of XXX? • This is all new tools but yet old problems. • WE HAVE THE TECHNOLOGY !!
More Information • http://solutions.cit.cornell.edu/Apps/webmethods • http://www.webmethods.com