1 soa implementation utilising best of breed at centrelink guy hutchison integration architect
TRANSCRIPT
1
SOA Implementation Utilising SOA Implementation Utilising Best Of Breed at CentrelinkBest Of Breed at Centrelink
Guy Hutchison
Integration Architect
2
AgendaAgenda
• Introduction • Thank Alex
• What is the SOA Prototype and how does it fit with a Reference Application and a Real Application
• The Prototype – Cubed• Demonstration of Prototype• Presentation and Business Tier• Integration Tier• Resource Tier – done by Ben
3
IntroductionIntroduction
• Demonstrating SOA capability within Centrelink– Built J2EE Application consuming Model204
Services rather than MQSeries transactions– Using Service Interface & ESB Components– Interface provides infrastructure to consume
service between any applications on any platform
4
Centrelink Processing EnvironmentCentrelink Processing Environment
• 12 Model204 Onlines• 14,000 Concurrent Users• 700 screens per second • 20 million screens per day• 40% of screens driven by scripts• 0.2-0.3 secs response time• 2 million MQSeries messages per day• 0.4 secs response time• 45% are self service• 3% of our CPU usage is Self Service• 5 Data centres 170,000 mips
5
Personal (CSC) Personal (Call Centre) IVR WEB0
50
100
150
Thousands
03-Oct-200316 - Sep -2005
Channel Shift
03-Oct-2003 16 - Sep -2005 ChangePersonal (CSC) 110,592 42,325 -68,267Personal (Call Centre) 76,308 112,888 36,580IVR 27,571 131,859 104,288WEB 15,842 44,915 29,073Personal Total 186,900 155,213 -31,687Self Service Total 43,413 176,774 133,361
TOTAL 230,313 331,987 101,674
6
Why SOAWhy SOA
Refresh our Infrastructure
Replace Existing Middleware
Refresh our Architecture
SOA Offered Agility
Refocus Disparate Groups
Prototype to prove these assumptions
7
SOA Prototype v Reference Application – What are the SOA Prototype v Reference Application – What are the differencesdifferences
Real Application exercising Real Application exercising ALL the Business LogicALL the Business Logic
Real Application exercising Real Application exercising ALL the Business LogicALL the Business Logic
Reference ApplicationReference ApplicationReference ApplicationReference Application
Architectural PrototypeArchitectural PrototypeArchitectural PrototypeArchitectural Prototype
8
How Much Work is Involved?How Much Work is Involved?
Mainframes, Unix Servers, Operating Systems,Comms, LAN, WAN, Routers
Middleware,COLFrame. Jframe,B2BMSS,EDX,JAS, Janus, MQ, Service Interface
UDDI, Service Developer, DBMS,Web Services, CTI
IAM, Std Shell, Batch 2, TriggersSupport Clusters, Cluster Functions
M204 Services, ADE, DIR, Fangio
Business Clusterse.g. Payments,
Assessment
BusinessStrategy
The SOA Prototype
The SOA reference Application
The first SOA Business Application
A full strength Business ApplicationEverything below this line is…Everything below this line is…Everything below this line is…Everything below this line is…
Infrastructure Foundation ServicesThe majority will deployed and configured for the prototype
9
Process FlowProcess Flow
Get Customer Reporting Summary
SelfService
ReportingService
Do Assessment
Display next Payment Details
IssueReceipt No
Services
The ApplicationThe Application
10
Demonstration of the PrototypeDemonstration of the Prototype
11
Client Presentation Business Integration Resource
J2EE Services
SAPServices
DB2DB2
OracleOracle
Common
Interceptor
Logic Gate
Locator
Context
Trace Managemt
Audit
Perf Timing
Config
CRAM Reporting
Janus Shell V1
Janus Shell V2Security
Frameworks
M204Services M204M204
MsgBroker
ClusterFunctions
WSS
ServicesLocator
ServicesRegistry(UDDI)
DataAccessObject
ServicesProxies
BusinessObject
Session Facade
ServiceLocator(local)
JanusJ2EEOther
Data SourceData
Source
Key: Components
Janus Workflow
Engine Janus Customised
Janus Legacy
StrutsController
JSP
Web Server
Business Delegate
Web Presentation
ObjectJanus Persistent
IVR Framework
NLSRFramework
Janus Connect’less
XML ScreenDefinitions
WS1
WebBrowser(xhtml 1.0)
WebBrowser
ExternalSystems
Phone
Web Services Client
http mq
xml
jdbcdto
dto
dto
xsl, JavaScript, etc.
(optional)
(optional)
html
M204 Online
ServletContainer
StrutsAction
Filters
Our Distributed On-line Architecture
12
13
Client Presentation Business Integration Resource
M204Services M204M204
ClusterFunctions
StrutsController
StrutsController
JSPJSPWeb
Browser(xhtml 1.0)
Struts ActionStruts Action
SOASOA
ApplicationLogic
ApplicationLogic
Business Delegate
e.g. customer
Presentation and Business TiersPresentation and Business Tiers
14
Integration Tier: M204 Web Services OverviewIntegration Tier: M204 Web Services Overview
– Janus Web Server running on Z/OsJanus Web Server running on Z/Os– Accepts XML messages in a standard format Accepts XML messages in a standard format
(SOAP) from external/internal sources (SOAP) from external/internal sources – Initiates M204 TransactionsInitiates M204 Transactions– Currently used to expose services for DEWR, Currently used to expose services for DEWR,
DIMIA and DEST DIMIA and DEST – Also used to communicate across ISIS Also used to communicate across ISIS
environmentsenvironments– Currently 80 web services in production with Currently 80 web services in production with
over 200,000 requests/dayover 200,000 requests/day
15
Integration Tier: High-level designIntegration Tier: High-level design
Client Client ApplicationApplication
Client Client ApplicationApplication ServiceServiceServiceService
DatabaseDatabaseDatabaseDatabase
Platform 1 Platform 2
XML Message XML Message HTTP/MQ etcHTTP/MQ etc
16
Client Client ApplicationApplication
Client Client ApplicationApplication ServiceServiceServiceService
XML Message XML Message HTTP/MQ etcHTTP/MQ etc DatabaseDatabaseDatabaseDatabase
CommonCommonFunctionalityFunctionality
CommonCommonFunctionalityFunctionality
CommonCommonFunctionalityFunctionality
CommonCommonFunctionalityFunctionality
Platform 1Platform 1 Platform 2Platform 2
Integration Tier: High-level design 2Integration Tier: High-level design 2
17XML Message HTTP/MQ etc
DatabaseDatabaseDatabaseDatabase
Platform 1Platform 1 Platform 2Platform 2
Integration Tier: High-level design 3Integration Tier: High-level design 3
RoutingRouting LockingLocking
SecuritySecurity SessionSession
CustomerContext
CustomerContext
RoutingRouting LockingLocking
SecuritySecurity SessionSession
CustomerContext
CustomerContext
Client Client ApplicationApplication
Client Client ApplicationApplication
Interface Specific to the services operation being
consumed
Generic Infrastructure to expose services to a
variety of consumers in a generic way
Proxy ObjectProxy Object Web ServerWeb Server
ServiceServiceServiceService
18
Integration Tier: What’s new for SOA?Integration Tier: What’s new for SOA?
– Web Service Description Language Web Service Description Language (WSDL) documents describe a 'new (WSDL) documents describe a 'new and improved' interface between our and improved' interface between our platforms (M204, J2EE, SAP etc)platforms (M204, J2EE, SAP etc)
– Proxy objects generated in J2EE that Proxy objects generated in J2EE that handle infrastructure under the handle infrastructure under the covers.covers.
– New way of accessing 'Services' in New way of accessing 'Services' in M204M204
19
Integration Tier: Exercising the new Infrastructure Integration Tier: Exercising the new Infrastructure
– Tools created to test exposed services– SOAP Tester provides HTTP interface to M204
WSSWSSWSSWSS Self ServiceSelf ServiceGet EligibilityGet EligibilitySelf ServiceSelf Service
Get EligibilityGet Eligibility
SOAP TESTERSOAP TESTER CORE CORE COMPONENTSCOMPONENTS
BROWSER -BROWSER - available on Centrenet (available on Centrenet (http://c204dv1c.csda.gov.au/jw/soaptest)
INPUTINPUT
OUTPUTOUTPUT
20
WebSphere and SOAWebSphere and SOA
– V 5.1.1 limited support so we added stuff– V 6.0 better support– IBM Consultancy– Product and Function specific– Installation support– Product Capability– Future proofing– Document Verification System
21
