2010 OHUG - Integration Broker (822.3 KB) - Mscc.us

fortnecessityusefulSoftware and s/w Development

Dec 14, 2013 (3 years and 10 months ago)

119 views

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


D
o 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

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

History


1925


Smoke Signals


1950


The Telephone


1975


Greenbar

(where most of our trees went)


1985


Magnetic Tape, followed by Diskettes


1995


FTP


Today

The Stage is Set


PeopleSoft was designed from the ground up as
a transition for large enterprise computer
systems:

o
from mainframe based

o
to Client / Server based systems


Databases, although more advanced today,
were, and still are where the vast majority of
business data is stored

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:

o
Business rules defined & implemented on the client

o
Business rules defined & implemented on the server

o
But ALL in the database as Metadata

o
. . . 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

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:

o
Reporting

o
Interfaces

The Stage is Set


Today . . . reports have been evolving:

o
PeopleSoft Query

o
Crystal Reports

o
Business Intelligence

o
Reporting Cubes



But the interface evolution has only begun . . .

What Interface Change Looks Like


Batch Mode of Interface . . .


Real Time Mode of Interface

o
Non
-
human intervention

o
across the Internet . . .


Removal of Business Rule Duplication


. . . with all of this, come a whole host of
technology and associated acronyms and terms

Hold onto your Seats . . .


HTML


XML


WSDL


WSIL


UDDI


API


Java


JMS


BEA


Tuxedo


Jolt


TCP/IP

Here Comes Demystification . . .


HTTP


FTP


SMTP


SOAP


MIME


AJAX

HTML


Hypertext Markup Language


Uses “<“, “>”, “/”, and a few other characters to
designate code


<html>

<head></head>

<body>Hello World

</body>

</html>

XML


Extensible Markup Language


Uses “<“, “>”, “/”, and a few other characters
to designate code, but continues on to be
able to redefine itself.

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

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

UDDI / UBR


Universal Description, Discovery and
Integration


UDDI Business Registry


An internet directory where businesses list
themselves . . . and
can discover each
other

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

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

JMS


Java Message Server


A proprietary protocol & associated language similar
in function to HTTP and HTML, only more
complex

Jolt


Java class library and API that provides an interface
to BEA Tuxedo from remote Java clients

o
The company's three founders: Bill Coleman, Ed Scott and
Alfred Chuang

o
Transactions for Unix, Extended for Distributed Operations



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)

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)


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)


Email


Specific Format & Layout


Commonly Used


Allows for Attachments

SMTP


Send Mail Transfer Protocol

POP


Post Office Protocol

IMAP


Internet Message Access Protocol

MIME


Multipurpose Internet Mail Extensions


is an Internet Standard that extends the format of e
-
mail to support:

o
text in character sets other than US
-
ASCII;

o
non
-
text attachments;

o
multi
-
part message bodies; and

o
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

SOAP


Simple Object Access Protocol


A way of communicating between programs
on different operating systems using HTTP
and
XML

URL/URI


Uniform Resource Locator


Uniform
Resource Identifier

AJAX


Asynchronus


Javascript

o
and


XML

Time to wake up . . .


What Change Looks Like


First we have Client / Server Architecture


Which came hand in hand with

o
GUI Interfaces

o
Business Rules Stored as Metadata


Followed by

o
Components,

o
Component Interfaces, and

o
Application Engine


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 . . .

o
Integration Broker

o
XML Publisher

o
Workflow



MENU











COMPONENT









What Change Looks Like

Page

Page

Page

Database

Data:


Business Information

Metadata:


Business Rules

(PeopleCode)

Object Definitions

Component

Processor

User

at a Keyboard


MENU











COMPONENT









What Change Looks Like

Page

Page

Page

Database

Data:


Business Information

Metadata:


Business Rules

(PeopleCode)

Object Definitions

Component

Processor

User

at a Keyboard

Component

I
nterface

Application

Engine

Integration

Broker

XML Publisher


Deals with the intricacies of XML


Allows you to set up and work with
templates


Associates your XML with data sources


Integrates with

o
PeopleSoft Query

o
PeopleCode

o
Application Engine

Workflow


eMail

o
Static and Dynamic Addressing

o
Embedding links

o
SMS to telephones


Interacts with . . .

o
Component

o
Component Interface

o
Application Engine

o
Integration Broker

PeopleSoft Query

Interacts with and key component in . . .

o
XML Publisher

o
Application Engine

o
Workflow

Integration Broker


Interface Direction

o
Incoming

o
Outgoing

o
Round Trip



Interface
Synchronicity

o
Synchronous

o
Asynchronous



Interface Format

o
Flat Files

o
XML

o
Excel Spreadsheet

o
Ajax, API, Web
Services, etc.


Processing

o
Transformations

o
T
ranslations
,

o
F
iltering


Interfaces: The Next Generation

Skills you will need . . .


Workflow


Application Engine


XML Publisher


Query


Integration Broker


Interfaces: The Next Generation

Integration Broker and Similar Tools

Michael
Stutz


(
360)757
-
2251

michael@stutz.us


(
888)757
-
2616