Professional Documents
Culture Documents
Integration Broker at Cornell
Integration Broker at Cornell
Integration Broker at Cornell
at Cornell
Kevin Leonard
CIT/Integration and Delivery
May 9, 2002
Directory Integration
PeopleSoft HR
ADABAS
(employees)
(students)
Integration
Process
SQL
FTP
Natural Pgms
Perl scripts
Directory
Others
IBM
Mercator
SeeBeyond
SoftwareAG
Tibco
BEA
Vitria
Oracle
webMethods
webMethods
Chosen because
Features
Cost
Name is misleading
It is an Integration Broker
The web part of the name makes people think
its only for web access untrue.
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
Adapters
Other Adapters
Email
JMS
JavaBeans
Vantive
Microsoft SQL
ODBC & JDBC
APIs
Security
Certificate in use
with SSL
Process Diagram
Document Types
Monitor Application
Document Tracker
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