1 Application Development Trends Articles The SOA-wise enterprise By Alan Radding Gartner expects service-oriented architectures to provide the basis for 80 percent of new development projects by Most enterprises today, however, report having launched only isolated Web services projects. Despite the fanfare about services, few orgs have a good grasp of how to deploy these architectures enterprise-wide. What's still needed are clearly defined best practices for deploying and managing SOAs, which can help orgs identify worthwhile initiatives, establish governance, button down security and so on. The Big Idea Fundamentals of SOA Find a legitimate business need by focusing on a messy problem that can be fixed with a few granular services. Establish a framework for governance in conjunction with your SOA architecture design and fill in the governance details as you go. Build in security and identity management from the start; do not rely only on existing network security. Plan from the outset for how you will manage and troubleshoot your SOA environment as it grows larger. Some industry gurus claim best practices already exist. Others argue that it is too early. Too few enterprise-scale SOA developments exist for solid best practices to emerge, they contend. Early adopters can only tell you what worked for them. Still, short of stumbling around in the dark, here are some practices around business value, governance, security, and management. The more involved issues such as testing, orchestration and reuse come into play but later in the game. Need for best practices The State of Utah is one example. Utah's environmental department is using Web services to share information with the federal Environmental Protection Agency. The state's criminal justice system relies on Web services to speed access to data in systems operated by a slew of cities, counties and state agencies. Through the magic of Web services, "a policeman can pull over a motorist and look up all kinds of information from different systems," says Randy Hughes, technical architect, State of Utah, office of the CIO.
2 At this level, SOA is simple. "Think back to EDI," Hughes suggests. "You need an architecture for exchanging information. Web services make it easy." However, Utah's Web services only provide read-only access to the data. "Today, we cannot run highvolume transactions," Hughes explains. So what's holding up Utah's effort? "We need to lay out the whole foundation," Hughes says. "What kind of data is available, how it is accessed, how it is published." That's the hard part. The state also needs a comprehensive approach to security and identity management. In short, Utah, like most orgs jumping into SOA, needs the kind of guidance only a set of SOA best practices can provide. Five Points of Entry IBM has identified five entry points to SOA: 1. People projects that improve productivity by facilitating access to data. 2. Process projects that improve processes starting at the department level, and then rolling out enterprise-wide. 3. Information projects that integrate information through federated views of data. 4. Connectivity projects that speed messaging among heterogeneous systems while ensuring quality of service. 5. Reusability projects that encourage and reward service reuse. Alan Radding SOA best practices can help orgs at every stage of the SOA process, from identifying worthwhile SOA initiatives to establishing effective governance. Other initial process concerns include buttoning down security and managing the whole thing once it is deployed. Best practice 1: Identify the business problem No app-dev project should start without a good business justification, but the problem seems worse with SOA. "The tools make it so easy. You can take any legacy component and turn it into a service," says Paul Lipton, senior architect, enterprise systems management at CA. As a result, "companies just skip the value proposition."
3 Not every project lends itself to SOA or makes business sense. "My techies want to try SOA with the payroll system," says the chief architect at a Houston aerospace and defense contractor. "OK, the payroll system is old and needs updating. But do they really want to do what amounts to putting payroll data on the Net? That's what I call the cool-tool syndrome." On the other hand, the company has an aging, mainframe-based asset management system that tracks machinery and equipment. Many internal groups need to access and update this system. Subcontractors and outside business partners also rely on it. Faced with the high cost of providing access to all these users, and high attrition within the ranks of aging mainframe experts, the business case for SOA here looked very good. "We did this with SOA because of all the messaging involved," says the chief architect. "It made sense from a business standpoint. But even then, this is only a temporary fix. Eventually, we're going to have to transition to something else." At many companies, the techies decide to start with a neat little project that can score a fast, easy win. "They are starting in the wrong place because even when they succeed, they won't have helped the business," asserts Doug Houseman, director of Capgemini, a consulting firm with a large SOA practice. Instead, he advises the dev team to "go into the messy areas, the areas everyone is scared to touch. That way you get some impact from your SOA." Messy areas typically are those where things change fast. Once you have identified a messy area, focus on one particularly messy step and build one or two services that clean it up. For example, a long term customer may have overdue invoices due to unresolved customer service issues. It would be good if the accounts receivable system could communicate with the customer service system before sending a pay-up letter or cutting off the customer. A few small services could check various systems and kick out the customer for special handling under certain conditions. "You want granular services here so you can keep up with the changes," Houseman says. See separate story, "Five points of entry."
4 Best practice 2: Address governance at the start The architecture determines the standards, protocols, tools and technologies the enterprise will use to build services. Governance addresses issues such as which services to develop in the first place, how they will be managed, who owns them, and how they will be secured. Tools in this space include Infravio X-Registry Platform, Mindreef Coral, and Systinet Governance Interoperability Framework. In May, 15 vendors-amberpoint, Infravio, JBoss and SOA Software, among others-joined forces to support SOA Link, an end-to-end governance interoperability initiative. Developers, however, tend to discount governance. They treat it as another administrative detail they can put off until the end, like filing time sheets. Not so. "Governance is a big deal. It must be part of the architecture review from the start," insists Robert Kelley, partner at systems integrator LiquidHub in Pennsylvania. Governance entails the specification of the policies under which the SOA will function. "It addresses the construction of the services and the use of the services," Kelley explains. Many IT teams learn the hard way that governance should have been addressed early on. Railinc, a subsidiary of the Association of American Railroads, encountered this problem. The company maintains a repository of all the rail equipment of the Class-1 U.S. railroads. Sharing this information is critical if rail cars from different railroads are to be connected and moved. Railinc turned to SOA to give it internal and external access to this data. "By using SOA, we don't have to dictate what systems our customers can use," says Garry Grandlienard, director of enterprise architecture. Using IBM WebSphere, Grandlienard's developers began by identifying services they needed and started building them. "We are going over our application portfolio looking for reusable services," he says. One service might check with the master equipment database. Another might retrieve certain characteristics of a piece of equipment. A notification service might send s or faxes. "In each case, we have to think through the interface, figure out what parameters are required, and what we can make available to the user," Grandlienard says.
5 Today, Railinc has multiple project teams building services and everyone wants to reuse services built by other teams. Until this point, the effort has progressed very well except for one thing. "We have not yet addressed the governance issue," he admits. Now Grandlienard is trying to add governance after the fact. "We're working informally with the development managers. This is a sales job." Coming up with a comprehensive set of governance principles, however, is a daunting challenge. One that may put the dev team in the middle of corporate politicking. "You need governance but you don't need to solve all the problems of the world," says Jim Crew, formerly the director of data center infrastructure at Merrill Lynch and now a VP at SOA Software. Instead he recommends going with something that is good enough for now even if it isn't complete or perfect. ZapThink Senior Analyst Jason Bloomberg agrees with this approach: "We recommend you have a governance framework, but you don't have to work out all the details before you start. Otherwise, you'll end up with paralysis by analysis." Bloomberg suggests pinning down a few key governance principles to start, such as how services will be reused and by whom. When you're a small shop, it's easier to cut corners. With only four of its eight developers working on SOA, "we're small enough to be self-governing," says Sean Carey, software architect at SPS Commerce, Minneapolis. "We just work out everything among ourselves as needed." SPS offers hosted and managed B2B services. The company turned to SOA to handle file-based integration and to give customers easier access to its backend infrastructure. Enterprises will move through three phases of SOA governance, says Sajay Sethunath, chief architect in Bearing Point's financial services group. The first phase consists of policies and standards to govern the underlying XML fabric. The second phase addresses standards around the repository, management of service level agreements, and enterprise-wide interdependencies. The third phase governs the crossing of organizational boundaries and closely resembles Business Process Management.
6 Best practice 3: Think security Like governance, security has to be considered from the start. Orgs need to specify who is responsible for each and use directories to manage the information. "With the current state of SOA, security is left to you," says Utah's office of the CIO's technical architect Hughes. "You have to figure out how to set it up. You really need an identity management system. We currently use the Utah master directory, but it is not a full-blown ID management system." Relying on network security is not enough, warn early adopters and analysts. "By designing security in upfront, you head off some big problems," advises the defense contractor's chief architect. ZapThink's Bloomberg, who calls security the first roadblock to SOA, agrees: "People think that SOA is XML-based so a network firewall is all you need. Well, a firewall is not enough." He recommends implementing a wide range of emerging SOA security tools. These tools, such as AmberPoint SOA Management and SOA Software XML VPN Controller, act as intermediaries, often in the form of appliances. For example, XML accelerators and firewalls check the traffic against policies and lists, validate the XML schema, block malformed XML, and verify authentication and authorization. SOA gateways serve similar functions. Other appliances can federate identities among multiple systems. Products here include IBM Data - apower XS40 XML Security Gateway and SOA Software's XML VPN Appliance. "We do not have enough data to identify best security practices," says Dennis Gaughan, research director of AMR Research, Boston. "A lot of the security models today are built at the application level. I think we need to get more fine-grained than that. With SOA, we need to look at security for small pieces of an application." Capgemini's Houseman agrees: "The big difference with SOA security is that you have to do it at the service level, not at the application level." To accomplish this, the service must be well documented. "You have to say in plain business language what this service is, what it does, what happens under which conditions, and the consequences of doing it wrong," he explains. Best practice 4: Don't forget management Like security, it's important to address the management issues at the start of an enterprise-scale SOA project. The first SOA project is generally easy to manage-just a couple of services, a few users and light traffic. But what happens when your SOA efforts succeed? Now, IT is looking at dozens, if not hundreds, of services used by thousands of users. Services that are reused repeatedly in new composite apps. What happens when a service fails or performance degrades to the point where users notice? "Today, much of the management must be done manually," says LiquidHub's Kelley. "The management tools are primitive."
7 IT traditionally has managed networks, apps and infrastructure separately. With SOA those distinctions blur. "You need to integrate the management of all parts of IT," he adds. Despite the loosely coupled nature of SOA services, "there are still a lot of dependencies," CA's Lipton points out. And because services are intended to look like a black box, he says, "you don't know what those services are doing inside," which complicates management. Orgs need "to create a plan to manage those services," Lipton advises. Specifically, IT teams must figure out how to see into and control the service. Tools such as Actional Looking Glass (acquired by Sonic Software, which is owned by Progress Software), AmberPoint SOA Management System, Infravio X-Registry, IBM WebSphere and Tivoli products, CA Unicenter and others are mature enough to manage effectively, according to ZapThink's Bloomberg. He recommends a metadata-driven management infrastructure built around policies, SLAs, and truly independent services. Still, enterprises early into their SOA effort are not quite ready to invest in management tools for their fledging projects. "We looked at AmberPoint and Actional but didn't see any value given where we are now. We just don't have enough services," Railinc's Grandlienard says. It's important to remember best practices aren't magic. They only point out what IT dev teams should be doing and suggest how to do it. If you create poor policies or fail to use updated threat lists, your governance and security will suffer despite best practices. Developers and managers too often regard best practices the way kids regard admonishments to, say, brush after every meal. Yet, when problems crop up, the highly paid consultants go first to these best practices and almost invariably find the source of the problem.
Copyright Rational Software 2002 http://www.therationaledge.com/content/oct_02/m_webtesting_jb.jsp Testing Web Services Today and Tomorrow by Jason Bloomberg Senior Analyst ZapThink LLC With all the attention
What You Need to Know About Transitioning to SOA written by: David A. Kelly, ebizq Analyst What You Need to Know About Transitioning to SOA Organizations are increasingly turning to service-oriented architectures
Topic Change Governance for the Agile Enterprise a Service Oriented Architecture (SOA) Perspective Document White Paper Author(s) Kelly A. Shaw, Ph.D. Research Analyst, Serena Software Brent Carlson, VP
IBM Global Services April 2008 Five best practices for deploying a successful service-oriented architecture Leveraging lessons learned from the IBM Academy of Technology Executive Summary Today s innovative
Smart SOA application integration with WebSphere software To support your business objectives Achieving business agility and cost optimization by reducing IT complexity. The value of adding ESB enrichment
Accenture Public Service Platform Taking SOA from the Whiteboard to the Data Center and Beyond Technology Challenges Are Daunting Today s information technology executives are tackling increasingly complex
IBM Information Management January 2008 IBM Information Management software Enterprise Information Management, Enterprise Content Management, Master Data Management How Do They Fit Together An IBM Whitepaper
Federal Enterprise Architecture and Service-Oriented Architecture Concepts and Synergies Melvin Greer Chief Strategist, SOA / Cloud Computing Certified Enterprise Architect Copyright August 19, 2010 2010
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7, No. 8, November-December 2008 What s Your Information Agenda? Mahesh H. Dodani,
Service management White paper Manage access control effectively across the enterprise with IBM solutions. July 2008 2 Contents 2 Overview 2 Understand today s requirements for developing effective access
SOA Governance & Security How BPM Can Help Philip Larson, Director of Product Management, Appian Corporation Copyright 2006 Appian Corporation. All rights reserved. Agenda! SOA Intro! How BPM And SOA Fit
THE NAME OF THE GAME: KANAME The Key to SOA Governance: Understanding the Essence of by Keith Swenson Kaname is a Japanese term meaning essence. In a Japanese fan, the bottom piece that keeps the fan together
Visible Solutions Strategic Enterprise Application Integration By Alan Perkins Chief Solutions Architect ASG Federal The biggest problem facing CIO's today is their existing applications. Enterprise Application
Presentation Outline Key Business Imperatives Service Oriented Architecture Defined Oracle SOA Platform 10.1.3 SOA Maturity/Adoption Model Demo Q&A Key Business Imperatives Increased Competition Requires
WHITE PAPER Data Center Fabrics Why the Right Choice is so Important to Your Business Introduction Data center fabrics are emerging as the preferred architecture for next-generation virtualized data centers,
Zen or Tao of SOA & Software As A Service David Moskowitz Productivity Solutions, Inc. David Moskowitz: The Zen or Tao of SOA and Software as a Service Slide 1 Agenda Common vocabulary When to use / not
-Oriented Architecture and Software Engineering T-86.5165 Seminar on Enterprise Information Systems (2008) 1.4.2008 Characteristics of SOA The software resources in a SOA are represented as services based
HP SOA Systinet software Govern the Lifecycle of SOA-based Applications Complete Lifecycle Governance: Accelerate application modernization and gain IT agility through more rapid and consistent SOA adoption
IBM SOA SOA Governance and the Service Lifecycle Naveen Sachdeva firstname.lastname@example.org IBM Software Group 2007 IBM Corporation IBM SOA Agenda What is SOA Governance? Why SOA Governance? Importance of SOA
The Definitive Guide to SOA Governance and Lifecycle Management By Miko Matsumura, webmethods VP of SOA Product Marketing March 2007 TABLE OF CONTENTS HOW TO AVOID READING THIS PAPER... 4 EXECUTIVE SUMMARY...
Application integration solutions To support your IT objectives IBM WebSphere application integration software: A faster way to respond to new business-driven opportunities. Market conditions and business
IBM Global Services September 2008 Reaping the rewards of your serviceoriented architecture infrastructure How real-life organizations are adding up the cost savings and benefits Executive summary Growing
IBM Global Technology Services January 2008 How service-oriented architecture (SOA) impacts your IT infrastructure Satisfying the demands of dynamic business processes Page No.2 Contents 2 Introduction
Concept Proposal A standards based SOA Framework for Interoperable Enterprise Content Management Mike Connor email@example.com Paul Fontaine Paul.Fontaine@ost.dot.gov What is it? IECM Framework Vision:
Advisory Services Business Systems Integration Framework for SOA services Service-oriented architecture can transform the IT landscape by increasing efficiencies and decreasing costs. But the architecture
Providing business intelligence for your software assets IBM Rational Asset Manager Highlights A collaborative software development asset management solution, IBM Enabling effective asset management Rational
Enterprise Digital Identity Architecture Roadmap Technical White Paper Author: Radovan Semančík Date: April 2005 (updated September 2005) Version: 1.2 Abstract: This document describes the available digital
Introduction Raju Alluri SOA adoption is evolutionary rather than revolutionary. It is a journey and not an end state. There are many challenges in the SOA journey. First and foremost, the challenge is
Helping organizations secure and govern application services for SOA, Web and the Cloud SOA WEB CLOUD layer7tech.com firstname.lastname@example.org @layer7 Layer 7 offers industry-leading XML security, runtime SOA
cloud accelerators Can big data transform your business? The cloud forces us to have a different kind of discipline around data security, mostly because it breaks down the assumption that we have any kind
C o n s u lt i n g S e r v i c e s TIBCO Service-Oriented IT Organizational Structure Best Practices: An Introduction HIGHLIGHTS: The information described here is part of a series of introductory best
Service Virtualization: Managing Change in a Service-Oriented Architecture Abstract Load balancers, name servers (for example, Domain Name System [DNS]), and stock brokerage services are examples of virtual
Franchise Grows 35 Percent in 5 Months with Custom Solution Designed by IT Firm Overview Country or Region: United States Industry: Professional services IT services Partner Profile Based in Phoenix, Arizona,
Evaluation of SOA Vendors A Technical White Paper from Firstservis Author: Alexander Roussekov, Senior SOA Architect, Firstservis Pty Ltd. Abstract This paper describes a SOA Vendors Evaluation Methodology
zapthink zapnote ZAPTHINK ZAPNOTE Doc. ID: ZTZN-1221 Released December 3, 2007 BOOMI ONDEMAND INTEGRATION AT THE SPEED OF THE INTERNET Analyst: David S. Linthicum Abstract Integration engines don t always
SOA policy management White paper April 2009 Realizing business flexibility through integrated How integrated management supports business flexibility, consistency and accountability John Falkl, distinguished
SEPTEMBER 2013 Buyer s Guide to Big Data Integration Sponsored by Contents Introduction 1 Challenges of Big Data Integration: New and Old 1 What You Need for Big Data Integration 3 Preferred Technology
Gain a competitive edge through optimized B2B file transfer Contents: 1 Centralized systems enable business success 2 Business benefits of strategic file transfer that you can experience for yourself 2
Whitepaper Create a single 360 view of Red Hat JBoss Data Virtualization consolidates master and transactional Red Hat JBoss Data Virtualization can play diverse roles in a master management initiative,
Independent Insight for Oriented Practice An SOA Roadmap John C. Butler Chief Architect A CBDI Partner Company www.cbdiforum.com Agenda! SOA Vision and Opportunity! SOA Roadmap Concepts and Maturity Levels!
Security Information and Event Management (SIEM) Audit Kevin Savoy Audit Director Strategic Risk Management SIEM just another acronym? What is it Why Advanced Persistent Threats (APTs) Audit Objectives
A practical guide to SOA for IT management White paper Executive summary...2 The business value of SOA...3 Management guidelines...3 SOA requires visibility, trust and control...6 Understanding the SOA
IBM SOA Setting the stage for a new era in Sugandh Mehta Distinguished Engineer IBM Global 2007-2008 IBM Corporation What is Driving Today? The Changing Landscape in the Globally Integrated Economy Forges
.org MSExchange Gold Award Microsoft MVP Brien Posey Takes a Look at InBoxer s Anti-Risk Appliance MSExchange.org Gives InBoxer Its Gold Award For A Perfect 5-Star Rating A perfect fivestar rating, because
E-Guide Tips for adopting a private cloud strategy to overcome IT challenges and realize benefits Many companies have heard the hype around private cloud computing, but some may have a difficult time deciding
Service Oriented Architecture 1 COMPILED BY BJ CHAPTER 9 Service Oriented architecture(soa) Defining SOA. Business value of SOA SOA characteristics. Concept of a service, Enterprise Service Bus (ESB) SOA
Service-Oriented Architecture and its Implications for Software Life Cycle Activities Grace A. Lewis Software Engineering Institute Integration of Software-Intensive Systems (ISIS) Initiative Agenda SOA:
How to Sell Your Municipals at the Right Price Back in the fifties and sixties, when the municipal bond market as we know it today was in its infancy, it was difficult to feel assured that you were getting
Managing the Growing Appification of Business Since the iphone mobile device burst onto the scene in 2007, companies have spent a lot of time, money and attention developing apps that enable them to engage
Integrate CRM and ERP for Better Intelligence Businesses benefit when information flows freely between systems By Leonard Klie Posted Sep 1, 2015 Technology is an accelerant. It will add fuel to whatever
AN INFORMATIONWEEK BUSINESS TECHNOLOGY NETWORK WHITE PAPER The role of Service Level Agreements in Successful SOA Deployments Getting the most from SOA means gathering the right metrics for SOA SLAs Brought
SOA REFERENCE ARCHITECTURE: WEB TIER SOA Blueprint A structured blog by Yogish Pai Web Application Tier The primary requirement for this tier is that all the business systems and solutions be accessible
White Paper Delivering Web Services Security: September 2003 Copyright 2003 Entrust. All rights reserved. Entrust is a registered trademark of Entrust, Inc. in the United States and certain other countries.
Industry models for financial markets The IBM Financial Markets Industry Models: Greater insight for greater value Executive summary Changes in market mechanisms have led to a rapid increase in the number
An Oracle White Paper June 2009 Integration Technologies for Primavera Solutions Introduction... 1 The Integration Challenge... 2 Integration Methods for Primavera Solutions... 2 Integration Application
SOA REFERENCE ARCHITECTURE: SERVICE TIER SOA Blueprint A structured blog by Yogish Pai Service Tier The service tier is the primary enabler of the SOA and includes the components described in this section.
Service-Oriented Architecture Foundation James T. Hennig, Chief Architect SOAF A email@example.com "If you are not interoperable, you are not on the net, you are not contributing, you are not benefiting,
SIF 3: A NEW BEGINNING The SIF Implementation Specification Defines common data formats and rules of interaction and architecture, and is made up of two parts: SIF Infrastructure Implementation Specification
7 Best Practices for Business Process Management in Customer Service 7 Best Practices for Business Process Management in Customer Service Table of Contents Introduction 3 Defining Your Process 3 Empowering
Microsoft SOA Roadmap Application Platform for SOA and BPM Thomas Reimer Enterprise Technology Strategist, SOA and BPM Microsoft Corporation (EMEA) Trends and Roadmap THE FUTURE OF DYNAMIC IT Market Trends
E-Business On Demand Deploying SOA using IBM s Enterprise Integration Messaging Specification () Architecture and Development Process November, 2005 Copyright Agenda Why deploy a Service Oriented Architecture
Architectural Requirements for an SOA Based on Web s Jim Bole VP, Engineering Infravio, Inc. April 23, 2003 Agenda! Web s is an integration technology! Web s role in an SOA! Unique Features and Challenges
Architectures Computing & 2009-11-06 Architectures Computing & SERVICE-ORIENTED COMPUTING (SOC) A new computing paradigm revolving around the concept of software as a service Assumes that entire systems
TechTarget Application Development Media ESB E-Guide E-Guide The enterprise service bus is a key element in a service-oriented architecture; and often times, it can be used as an incremental starting point
Software Development Life-cycle Hygiene with Message Broker in end-to-end SOA Tips for building and maintaining a working SOA implementation in MB Stuart Smith - Consultant, Smart421 firstname.lastname@example.org
Testing service-oriented architecture (SOA) applications and services White paper Table of contents Introduction.................................................................. 3 Understanding SOA............................................................
White Paper Decision Services: The Next SOA Challenge Decision Services: The Next SOA Challenge White Paper ILOG, June 2006 Do not duplicate without permission. ILOG, CPLEX and their respective logotypes
Abstract SOA : To Do or Not to Do Gopala Krishna Behara and K.T.R.B Sarma As business moves from Web services to SOA, adoption and successful implementations of SOA become more evident. The goal of SOA
Open Source, Component Systems, Agile, and SOA Projects Terry Vogt Lead Associate Booz Allen Hamilton Sept 13, 2011 Ready for what s next 1 Booz Allen Hamilton 1 Agenda Background Open Source Component
International Journal of Advanced Computer Science and Information Technology (IJACSIT) Vol. 1, No.1, October 2012, Page: 25-31, ISSN: 2296-1739 Helvetic Editions LTD, Switzerland www.elvedit.com A Service
Business Intelligence The ESB and Microsoft BI The role of the Enterprise Service Bus in Microsoft s BI Framework Gijsbert Gijs in t Veld CTO, BizTalk Server MVP email@example.com About motion10
Service Virtualization A faster, more efficient and less costly way to develop and test enterprise-class applications As cloud and mobile computing gain rapid acceptance, IT departments are expected to
The Next Generation of IT Management Jason Andrew Vice President, Marketing & Communications BMC Has Outperformed the Market Growing Stock Price Over 130 Percent in 5 Years BMC +134% IBM +76% HP +50% NASDAQ
5 Pillars of API Management with CA Technologies Introduction: Managing the new open enterprise Realizing the Opportunities of the API Economy Across industry sectors, the boundaries of the traditional
Flat Rate Per Claim -vs- Percentage Billing Fees A Devil's Advocate View Assuming a full service solution, there are basically two methods billing services use to charge for their services, either a percentage
N AT I O N A L A S S O C I AT I O N O F S TAT E C H I E F I N F O R M AT I O N O F F I C E R S Enterprise Architecture Maturity Model 167 West Main Street, Suite 600 Lexington, KY 40507 P: 859-514-9153
White Paper: Security and Agility in the API Economy Optimizing and securing your APIs with ViewDS Identity Solutions and Layer 7 Security and Agility in the API Economy The API Economy is more than the
Making Data Available on the Web By Simba Technologies Inc. SimbaEngine ODBC SDK Introduction Many companies use web-based services to automate business processes like sales, track items like packages,
Hosted PRESENTS... Reasons to Switch from SourceSafe: Why SourceAnywhere Hosted Makes Life Easier for Systems Administrators and Developers Maintaining a version control system is resource intensive. Look
Connectivity and integration Executive brief Optimize the potential of ERP systems through IBM SMART SOA integration strategies. Page 2 Contents 2 Executive overview 3 A problem of integration 4 How this
SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) VERSION 2.1 SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS 1 TABLE OF CONTENTS INTRODUCTION... 3 About The Service-Oriented Modeling Framework
IBM Software for WebSphere Redbook Overview Patterns: SOA Design with WebSphere Message Broker and WebSphere ESB Presenter: Kim Clark Email: firstname.lastname@example.org Date: 27/02/2007 SOA Design with WebSphere
IBM API Management Overview Please Note IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential
International Research Journal of Applied and Basic Sciences 2013 Available online at www.irjabs.com ISSN 2251838X / Vol, 5 (11): 14381445 Science Explorer Publications Presenting a model for the deployment
SOA and VO-s Steve Stein Mari-Klara Oja International School of New Media Models of Virtual Organizations Dr. Oliver Bohl Overview / Context of SOA VO/VE (idea) from static mainframes to dynamic arrangements
Service Oriented Architecture and the DBA Kathy Komer Aetna Inc. New England DB2 Users Group Tuesday June 12 1:00-2:15 Service Oriented Architecture and the DBA What is Service Oriented Architecture (SOA)