WIXLIB

The Good, The Bad and The Ugly: Mainframe SOAImplementation Best PracticesCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.

Mainframe Integration ApproachesEnterprise SOAMigrate partsReplaceSOA EnableCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 2

SOA Goals Reduce cost through reuse Increase agility to better align IT and the Business Build applications fasterUse existing business logic rather than rewriting each timeMinimize cost of maintenance and upgrade by allowing incremental updatesAllow rapid change through business process management and compositiontoolsAllow incremental updates to enterprise applicationsMinimize change cycles with business granular interfacesReduce the risk, fragility and complexity of integration by improvinginteroperability through standards Reduce investment in and risk of brittle proprietary integration techniquesand technologiesReduce frequency of data error caused by duplicationCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 3

SOA Challenges End-to-end security - trust and protect the privacy of message senders,receivers, and contentIdentify, manage, and repair exceptions as they occurReliability and performance of a distributed set of services andconsumersInteroperability between different platforms and technologiesDecoupling of services and consumersMeasure and prove the business value of SOA to offset cost concernsControl of (govern) the proliferation of duplicate or otherwiseunnecessary servicesFacilitate the identification of appropriate services by potential users toreduce initial development costManage the lifecycle of services to minimize the cost and risk ofongoing maintenance and changeSimplify the actual USE of appropriate services (decoupling location,transport, policy, standards, messaging styles)Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 4

Top Pitfalls of Mainframe SOA Processing off of the mainframe Edge interfaces Middle tier servers Off mainframe security or proprietary security Fat client development Ignoring human assets Uni-directional integration Lack of centralization Lack of end-to-end monitoring, integrated testing, and errorlogging Doesn’t get the big pictureCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 5

Mainframe SOA Can I have it all?Is it possible to incorporate the mainframe into an enterprise wide SOA yetstill get all the benefits of the mainframe performance, reliability,scalability, manageability and cost effectiveness?Yes.Here’s how Run your SOAP stack on the mainframe. Take advantage of the power of the mainframe – reliability,performance, scalability, manageability and cost effectiveness. Put your SOA next to your enterprise assets.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 6

Enterprise SOA theory and practice.Enterprise SOA must address two different sets of issues:1. Essential Components (what you need to build an SOA)2. Practical Implementation (what you need to run an SOA)Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 7

Essential Components of Enterprise SOASecuritySupport for ArchitecturalStandardsPolicy ManagementSOAP & XML CapabilityChange & ReleaseManagementWorkflowManagementMonitoring, Logging &Audit ControlsDevelopment ToolsRegistryCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 8

SOA is an Architectural Framework Service Oriented Architecture is a framework for the loosecoupling of services. All SOA implementations have thefollowing key characteristics: Self-describing interfaces using Web Services DescriptionLanguage (WSDL) Request/response messages using SOAP The services are documented in a registry (UDDI) The service is associated with a quality of service (QoS) bymeans of a Policy. The key QoS element is securityCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 9

Security You’ll need to support Authentication, Authorization, Integrity,Confidentiality and Non-Repudiation. WS-Security provides all of these SAML (Security Assertion Markup Language) implements authentication. Canalso use along with RACF or LDAPXACML (eXtensible Access Control Markup Language) implementsauthorizationIntegrity is implemented with XML Signature. This is a pre-requisite for SAMLConfidentiality is implemented with XML encryption. It allows for flexibleencryption (only encrypt what needs to be encrypted) and substantiallyreduces CPU compared to SSL (which encrypts everything on the wire)Non-Repudiation is dependent on public-key cryptology. You can’t deny(repudiate), because your key is half of the only pair able to encrypt/decryptUsing WS-Security your mainframe SOA will be able to interoperatewith all other SOA participants. Isn’t that the point of SOA?You’ll need to implement WS-Security on the mainframe to eliminate“last mile” vulnerability.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 10

Policy Management A Policy Definition Point (PDP, for example, SOA Software’s PolicyManager) is used to define policies for services.A Policy Implementation Point (PIP) implements policies.WS-SecurityPolicy indicates the policy assertions which apply to WebServices Security.WS-PolicyAttachment associates the WS-Policy with the WSDL.WS-Policy externalizes the rules, without it your developers arerequired to hand code your policies, with it a PIP enforces the policiesexternal to your programs.WS-Policy is essential for proper SOA governanceCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 11

Monitoring, Logging and Auditing Monitoring, logging and auditing are necessary to measure and manageperformance and diagnose and debug problems.Measurement is the key to SLA management. Without monitoring youwon’t be able to measure your effectiveness.Monitoring, logging and audit are essential to make a solutiongovernable.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 12

Registry A Registry enables governance (you can’t govern what you don’t know). A Registry enables reuse. You can’t reuse services that you can’t find. All services need to be automatically documented in a registry. A registry is the foundation of a Service Oriented Architecture, anarchitect won’t design a building that lacks a foundationCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 13

The SOA PlatformCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 14

SOA Infrastructure SolutionsThis is theGovernanceringCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 15

SOA Infrastructure Solutions SOA Infrastructure includesGovernance, Management andSecurity linked together through SOAPolicy Management Governance offers no value without aruntime solution to enforce policiesand feed back metrics andcompliance data Runtime solutions (security andmanagement) offer minimal valuewithout central policy control andvalue-added service governancecapabilitiesCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 16

Standards-based Closed-loop SOA Infrastructure Closed loop means: Defining and managing actionable policies in agovernance solution at design-timeEnforcing these policies via deep integrationwith a management solution at run-timeAuditing that these policies are being enforcedUsing industry standards (WS-Policy, WSMEX) where appropriate for metadatainterchangeClosed loop infrastructure enables demand andValue Management Collect performance, usage and exceptionstatistics at run-timeTrack these statistics via the governancesolutionUse live, audited information to drive valuebased decisions about the effectiveness ofdifferent services and organizationsProvide developers with up to the minuteinformation about a service in runtime toinform their decisions about which services touseManage supply and demand to ensuremaximum efficiency and benefit from SOACopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 17

Closed-loop vs Broken-loop Integrated (closed-loop)solutions are best-ofbreedThere are no examples ofintegrated standalonesolutions in productionCopyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 18

Enterprise SOA Practical ImplementationNow that we understand the essential components, let’sexamine some practical aspects of Enterprise SOA.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 20

How do you keep the mainframe’s speed and reliability?Run your SOAP stack on the mainframe.It doesn’t make sense to integrate the mainframe into an SOA by usingoff-mainframe middleware and/or middle tier servers. Implementingmainframe SOA doesn’t have to mean introducing bottlenecks and pointsof failure.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 21

How do you ensure a low MIPS overhead? Be fanatical about performance – your SOA will fail if it drives MIPSusage up by more than a small percentage. Use compiled languages. Take advantage of hardware assistance for cryptology.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 22

Scalability and FailoverIt’s easy to scale down. Scaling up takes planning. Exploit SYSPLEX/CICSPLEX architecture. Run under WorkLoad Manager. Use IP port sharing and SYSPLEX Distributor tohandle workload. Think of your SOA as supporting your business. Usemonitoring tools to monitor your SOA environmentthrough a “dashboard”.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 23

Operations How will you diagnose production outages? What was in that failing SOAP request? How will you manage changes? How is the environment running? Are you meeting your SLAs? How will you prevent unauthorized access?Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 24

StandardsQ: How do you make sure your implementation doesn’t get left behind?A: Standards. Standards reduce the risk of committing to a technology that will beunsupported in future.Standards allow greater choice of vendors and the availability of alarger talent pool.Copyright 2012 SOA Software, Inc. All Rights Reserved. All content subject to confidentiality agreement between SOA Software and Customer.Slide 25