1 / 38

Interfaces: The Next Generation Integration Broker and Similar Tools

Interfaces: The Next Generation Integration Broker and Similar Tools. Michael Stutz ( 360)757-2251 michael@stutz.us ( 888)757-2616. Michael Stutz. Interfaces: The Next Generation Integration Broker and Similar Tools. Independent PeopleSoft Consultant Started Technical

kacy
Download Presentation

Interfaces: The Next Generation Integration Broker and Similar Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interfaces: The Next Generation Integration Broker and Similar Tools Michael Stutz (360)757-2251 michael@stutz.us (888)757-2616

  2. Michael Stutz Interfaces: The Next Generation Integration Broker and Similar Tools • Independent PeopleSoft Consultant • Started Technical • Do both Functional and Technical consulting • Primary Focus HCM and Campus Solutions • 25 years of IT industry experience • 16 years of PeopleSoft consulting experience • PeopleSoft v.2.11 – v.9.1 • Lost Track of the number of PeopleSoft Projects I’ve been on • Here at OHUG to network . . . • . . . and to share my insights on the future of interfaces in the PeopleSoft environment

  3. Agenda The Stage for Change Term Demystification What Change Looks Like Integration Broker and Other Tools Interfaces: The Next Generation Integration Broker and Similar Tools

  4. History • 1925 – Smoke Signals • 1950 – The Telephone • 1975 – Greenbar(where most of our trees went) • 1985 – Magnetic Tape, followed by Diskettes • 1995 – FTP • Today

  5. The Stage is Set • PeopleSoft was designed from the ground up as a transition for large enterprise computer systems: • from mainframe based • to Client / Server based systems • Databases, although more advanced today, were, and still are where the vast majority of business data is stored

  6. The Stage is Set • With Client / Server, business rules were programmed into the online system and stored as Metadata . . . • In our case, the Metadata is coding (PeopleCode) stored in the database instead of a program file: • Business rules defined & implemented on the client • Business rules defined & implemented on the server • But ALL in the database as Metadata • . . . and ALL for the online portion of the system • Which leads us to a big motivation . . . . . . business rules are duplicated in batch programs . . . and so they also have to be maintained separately

  7. The Stage is Set • At the dawn of PeopleSoft, and still today, the vast majority of Interfaces are executed using flat files on a batch basis • For batch processing PeopleSoft doesn’t want us to mess with . . . they use COBOL • For batch processing PeopleSoft knows clients will likely need to modify . . . they use and deliver SQRs: • Reporting • Interfaces

  8. The Stage is Set • Today . . . reports have been evolving: • PeopleSoft Query • Crystal Reports • Business Intelligence • Reporting Cubes • But the interface evolution has only begun . . .

  9. What Interface Change Looks Like • Batch Mode of Interface . . . • Real Time Mode of Interface • Non-human intervention • across the Internet . . . • Removal of Business Rule Duplication • . . . with all of this, come a whole host of technology and associated acronyms and terms

  10. HTML XML WSDL WSIL UDDI API Java JMS BEA Tuxedo Jolt TCP/IP Hold onto your Seats . . . Here Comes Demystification . . . • HTTP • FTP • SMTP • SOAP • MIME • AJAX

  11. HTML • Hypertext Markup Language • Uses “<“, “>”, “/”, and a few other characters to designate code <html> <head></head> <body>Hello World </body> </html>

  12. XML • Extensible Markup Language • Uses “<“, “>”, “/”, and a few other characters to designate code, but continues on to be able to redefine itself.

  13. XSD • XML Schema Definition • A way to describe and validate XML data • Allows the same custom “tags” to be read differently in different XML documents

  14. WSDL • Web Services Definition Language • Common XML language specific to businesses WSIL • Web Services Inspection Language • Common XML language used to inspect a site for available services

  15. UDDI / UBR • Universal Description, Discovery and Integration • UDDI Business Registry • An internet directory where businesses list themselves . . . and can discover each other

  16. API • Application Program Interface • Prebuilt pieces of programs . . . used as building blocks . . . to develop a program (or enhance another program) to interface with other systems

  17. Java • The name of a software platform . . . • . . . a number of computer software products and specifications from that together provide a system for developing application software and deploying it in a cross-platform environment

  18. JMS • Java Message Server • A proprietary protocol & associated language similar in function to HTTP and HTML, only more complex

  19. Jolt • Java class library and API that provides an interface to BEA Tuxedo from remote Java clients • The company's three founders: Bill Coleman, Ed Scott and Alfred Chuang • Transactions for Unix, Extended for Distributed Operations

  20. TCP/IP • Transmission Control Protocol • Internet Protocol • The first two networking protocols defined • Today's IP networking represents a synthesis of two developments that began in the 1970s, namely LANs (Local Area Networks) and the Internet, both of which have revolutionized computing. (www.wikipedia.org)

  21. HTTP • Hypertext Transfer Protocol • Protocol for data transmission on the internet • Original purpose to provide a way to publish and retrieve HTML pages. Development of HTTP was coordinated by the W3C (World Wide Web Consortium) and the IETF (Internet Engineering Task Force), culminating in the publication of a series of (RFCs) Request for Comments like RFC 2616 (1999), which defines HTTP/1.1, the version of HTTP in common use today. (www.wikipedia.org)

  22. FTP / SFTP • File Transfer Protocol • SSH File Transfer Protocol • A common misconception is that SFTP is simply FTP run over SSH; in fact it is a new protocol designed from the ground up by the IETF SECSH working group. It is sometimes confused with Simple File Transfer Protocol. (www.wikipedia.org)

  23. Email • Specific Format & Layout • Commonly Used • Allows for Attachments SMTP • Send Mail Transfer Protocol POP • Post Office Protocol IMAP • Internet Message Access Protocol

  24. MIME • Multipurpose Internet Mail Extensions • is an Internet Standard that extends the format of e-mail to support: • text in character sets other than US-ASCII; • non-text attachments; • multi-part message bodies; and • header information in non-ASCII character sets. (www.wikipedia.org) • Most e-mail is transmitted via SMTP in MIME format • The content types defined by MIME standards are also used in communication HTTP and other protocols

  25. SOAP • Simple Object Access Protocol • A way of communicating between programs on different operating systems using HTTP and XML

  26. URL/URI • Uniform Resource Locator • Uniform Resource Identifier

  27. AJAX • Asynchronus • Javascript • and • XML

  28. Time to wake up . . .

  29. What Change Looks Like • First we have Client / Server Architecture • Which came hand in hand with • GUI Interfaces • Business Rules Stored as Metadata • Followed by • Components, • Component Interfaces, and • Application Engine

  30. What Change Looks Like • Moving more and more toward reuse of online metadata Business Rules in a batch mode • Evolving into greater use of batch mode “non-human” Component Interface integration with the outside world . . . using all the various current technology . . . with some of the newer PeopleSoft delivered tools . . . • Integration Broker • XML Publisher • Workflow

  31. What Change Looks Like Database Data: Business Information Metadata: Business Rules (PeopleCode) Object Definitions MENU COMPONENT Page Component Processor User at a Keyboard Page Page

  32. What Change Looks Like Database Data: Business Information Metadata: Business Rules (PeopleCode) Object Definitions Application Engine MENU COMPONENT Page Component Interface Component Processor User at a Keyboard Page Page Integration Broker

  33. Deals with the intricacies of XML Allows you to set up and work with templates Associates your XML with data sources Integrates with PeopleSoft Query PeopleCode Application Engine XML Publisher

  34. eMail Static and Dynamic Addressing Embedding links SMS to telephones Interacts with . . . Component Component Interface Application Engine Integration Broker Workflow

  35. Interacts with and key component in . . . XML Publisher Application Engine Workflow PeopleSoft Query

  36. Interface Direction Incoming Outgoing Round Trip Interface Synchronicity Synchronous Asynchronous Integration Broker • Interface Format • Flat Files • XML • Excel Spreadsheet • Ajax, API, Web Services, etc. • Processing • Transformations • Translations, • Filtering

  37. Skills you will need . . . Workflow Application Engine XML Publisher Query Integration Broker Interfaces: The Next Generation

  38. Interfaces: The Next Generation Integration Broker and Similar Tools Michael Stutz (360)757-2251 michael@stutz.us (888)757-2616

More Related