U.S. ENVIRONMENTAL PROTECTION AGENCY The Web Service Catalog Presentation to the SOA-COI Meeting Lico Galindo, OIC April 14, 2010

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 2 Basic SOA – It’s about Services!

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 3 EPA Target Architecture

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 4 Why do we need a Web Service Catalog? Manage and organize services at EPA, allows finding the right service when in need of one, with information that includes –Service description and documentation –Information on how to use the service, parameters, operations, environment, security sensitivity, etc. –Ownership and contact information –Requirements for use – price, contracts, etc. –Other information necessary to consume the service Facilitate re-use of services

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 5 Benefits of a Web Service Catalog By facilitating sharing and reuse of services, it promotes application development of –Higher quality –Lower cost –Faster delivery –Standard built – lower maintenance Collaboration among users also help sharing in the development of new services and sharing lessons learned and best practices

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 6 RCS implements the Web Service Catalog RCS powered by COTS solution - Software AG’s Centrasite (uses UDDI standard) Register and discover services through both simple and complex searches, as well as browse for services by classification scheme Supports multiple versions of services and life- cycle for each service

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 7 RCS implements the Web Service Catalog (cont.) Allows documents related to a service Supports relationships between services, systems, schema and other services (parent- child, predecessor-successor, part of, used for/used-by) Allows manual entry/upload and automated harvesting and linking Supports notifications Support reviews and ratings

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 8 Service Types Web Services –SOAP web services –REST web services –Web Feature services –Web Map services –Composite services Other Services –Business services –Common Enabling Services –Other Technology services

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 9 Metadata about Web Services Name * Description * Service type Version * Alternate name Life cycle phase and dates * Owner * Steward * Submitter * EPA approver * Source Comments Quality ratings Keywords Links to documentation Access level Intended use Technology Classification data URI/URL * * Required

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 10 Metadata about Web Services (cont.) WS-I compliant SOAP version UDDI Key Namespace Local name Has policy attachments Functional requirements Non-functional requirements Error msgs/codes Binding Information Usage examples Release notes Demo URI/URL Tech support Tech support phone Domain Server name Server type Service family Port Access information

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 11 Classification Schemes In order to ensure that the services are easily discoverable, the following schemes are assumed: –FEA’s Service Reference Model –EPA business functions (in part, derived from BRM) –EPA media –Contributing organizations (EPA and partners) –Applicable parts of the Web Taxonomy Other classification schemes may be added: –North American Industry Classification System (NAICS) –Universal Standard Products and Services (UNSPSC) –ISO 3166 Geographic Taxonomy –GeoWeb Geographic Classification

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 12 Interfaces Manual –Extranet, for partners –Public Machine-to-Machine –Point-to-point –Service Bus

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 13 Sources of Web Services Central Data Exchange (CDX)/ENDS System of Registries (SoR) Data Warehousing (ETL) Agency-wide databases (EnviroFacts, FRS, SRS) Program databases (TRI, STORET, etc.) Geospatial Data Catalog

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 14 Security and Access RCS has group, role, and data based security to ensure that customers can only perform certain actions on certain services. Most users can only discover the service and need to contact the owner in order to consume it. A service contract may be required to consume some services Some SOA applications may be authorized to consume services dynamically Registration of new services is restricted to authorized stewards The amount of information registered about a service is determined by the owner or steward

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 15 Governance Purpose - Manages the RCS and ensures: –Continuity of operation –Quality of the components –Reusability of the components –Policy Enforcement –Improvement and expansion Workflow to include: –Submitter/developer –Steward/Reviewer –Registrar –Special Reviewer –EPA Approver

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 16 Generic Workflow - Registration

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 17 Relationship to the Enterprise Service Catalog (ESC) RCS can register multiple levels of services and components –Business services –IT services –Web services –Other components and resources –Service compositions and orchestrations RCS can store relationships among services, components and all types of services RCS will store information about projects, organizations and architectural segments and how they relate to their services This is the Enterprise Service Catalog

U.S. ENVIRONMENTAL PROTECTION AGENCY Slide 18 Next Steps Receive authorization to operate Demonstrate system to different groups Continue validating metadata and classification schemes Load web services from the System of Registries and CDX Establish governance, short-term and long-term Survey other agency services Load other agency services manually Connect to agency registries to load services automatically Continue working with EAWG to support other services Continue exploring ways to support SOA, even using the webMethods SOA suite