leader replacement system - Department of Public Social Services ...

More documents

Recommendations

Info

Los Angeles County Department of Public Social Services LEADER Replacement System (LRS) 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 Liberty Alliance and OASIS have defined a large number of Web service security standards. Eventually, the work of both groups will probably be merged into a single set of standards. WS-Security seems to be the most widely used while many other standards within WS* are still evolving. However, this should not deter security mechanisms from being designed into Web services. California Service Centers The ultimate vision is to consolidate business services provided to constituents into a collection of federated service centers. SOA will play a key part in how these services are implemented. Please see California Service Centers SOA White Paper , for complete details. Following is a brief description of the key components. Consolidated Service Centers Clark Kelso, State CIO on 4/21/2006 authored Government Services on the Web: California In- Touch . This document introduces the notion of providing a better customer experience at reduced cost to the state via moving to consolidated service centers. The new California Service Center (CSC) will lead the way to a more customer-friendly E- government based on a services oriented (SOA) environment. From a strategic perspective, the California Service Center will be the customer-facing site. It will intelligently redirect to the appropriate service centers which will be working together in a federated manner. Shared Services Collectively, the service centers will leverage shared services, such as Identity, Search, Real Simple Syndication (subscriptions, news), Address Verification, and a common Payment engine to name a few. Shared services will be built in a federated manner but deployed and operationally managed centrally. That is, many departments will contribute shared services but they will be hosted in a small number of data centers. SOA Infrastructure Operationally, service centers will utilize an enterprise infrastructure approach. That is, they will be deployed and managed in a small number of SOA-based data centers. Mission critical services will be deployed in a redundant manner across data centers to minimize single point of failures. This implies collaboration in the area of configuration and release management across data centers to achieve a high degree of availability, scalability, and reliability. An SOA infrastructure must support XML message processing and application integration. This functionality is normally handled by an ESB. LRS RFP - Attachment H (Technical Exhibits) Page 33 November 30, 2007
Los Angeles County Department of Public Social Services LEADER Replacement System (LRS) 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 Enterprise Service Bus Application integration and service interoperability are of paramount importance in a shared services environment. Because applications are located on many different hardware and software platforms, connecting these environments in a manner that meets availability, scalability, and user performance expectations, uniform service interoperability platforms must be carefully chosen. These typically fall into two categories: For Windows-based platforms, Microsoft handles standards-based messaging and application connectivity via incorporating Windows Communication Framework functionality into an upcoming release called Windows Vista. In the Java world, there are quite a few choices. Some of the more popular ones are IBM WebSphere ESB, BEA AquaLogic Service Bus, Oracle Fusion, Cape Clear ESB, Sonic Software ESB, SAP NetWeaver, and others. California SOA Center of Excellence Introduction A successful state-wide SOA program will require both centralized and federated components. Singular vision & goals, governance, enterprise repository management, and several operational functions (certification lab, UDDI repository, maintain service reference model, service help desk, and search taxonomy) should be centralized. Service development (and possibly some SOA operations) should be federated to the producing departments. In some of the above functions, centralized does not mean single instance. For example one would establish at least two UDDI repositories for scalability and accessibility. Because SOA components are designed for enterprise use, there are a number of critical governance and operational issues that need to be addressed. Such as: • How will developers be supported? • How will business architects and technical architects determine which shared services already exist? • How will SOA services be mapped to business services? • How will service versioning and release packaging be controlled? • How will services be certified? • How will services be tested for performance, availability, and scalability? • How will services usage be monitored and reported? • How will developers locate code for an existing service? • How will service contract compliance among data centers be handled? • Will there be a centralized, state-wide help desk? • How will service troubleshooting be handled at an enterprise level? (A composite service might consist of 4 services, each running in a different data center.) • Will there be example services and demo applications? • Will there be a state-wide search service utilizing a common language? (a taxonomy)? LRS RFP - Attachment H (Technical Exhibits) Page 34 November 30, 2007
Page 1 and 2: LEADER REPLACEMENT SYSTEM Request f
Page 3 and 4: Los Angeles County Department of Pu
Page 17 and 18: 266 Function Operating Systems Clie
Page 35: Los Angeles County Department of Pu
Page 53: Los Angeles County Department of Pu

leader replacement system - Department of Public Social Services ...

Create successful ePaper yourself

Delete template?

Save as template?