T3151 Appendix C - AOSOS Current Architecture.docx

EXHIBIT I

AOSOS Application Suite Architecture Information

Hardware Architecture

The current AOSOS platform’s two components, AOSOS and Job Zone/Job Source, run in a virtual environment in the state’s enterprise data center.

The hardware is scaled to fit the state’s processing requirements.

The AOSOS Mediated Application supports the Windows operating system through Windows 10, and must be accessed via Microsoft Edge, with various additional compatibility features.

The Administration, Reporting, Phased Technical Refresh (PTR)/NextGen and Self-Service client application, Job Zone, were designed to run on most commonly available browser/operating system platforms.

Tier 4 – Database Servers The Database servers house the transaction and data warehouse Oracle databases.

Tier 3 – Search/Auxiliary Server and Report Server (opt) The Job and Seeker search engines run on these servers, as does the Key server and several batch and utility services.

There is an optional Report Server that can take some load off the Search/Aux Server by running reports from the Warehouse Database.

Tier 2 – Application Servers The IE Sun Solaris Web server (Web Server) only works for users who are working in IE. The JZ/CZ Sun Solaris Web Server allows users to work in most current browsers and takes advantage of Java technology.

The Linux Web Server is part of a change called the “Phased Technical Refresh” (PTR). This software is designed but the hardware is not yet purchased. It is not yet final how this will fit into the current technical design. This server will allow users to work in most current browsers. It takes advantage of the latest stable Java technology and will allow for a responsive design.

The Web Server distributes the client software to the various Tier 1 clients and processes requests from the Self Service and Administration clients. Requests from the Mediated client or API clients are passed from the Web server to one or more Application servers. The Application servers contain the complex business logic that drives search engine queries and queries/updates to the transaction database.

Tier 1 – Client PCs and APIs Using a browser, the Mediated, Self Service and Administration clients connect to the Web server through the state WAN or the public Internet. State applications using the AOSOS APIs connect to the Web server using HTTP from within the state’s data center Local Area Network (LAN). The Vendor will be able to use a VPN connection to obtain access to the state’s data center LAN.

Hardware Sizing Considerations

Sizing for an AOSOS installation begins with identifying the number of total and concurrent users for each business process, and identifying the anticipated number of customers and job orders. Detailed sizing will include the number of employers and service providers. Planning must also account for anticipated growth in the volume of data, the number of state agencies that will use AOSOS, and the transaction volume from state systems using the AOSOS APIs.

For states that require multiple Application servers, the load on each of the servers must be balanced for optimum throughput. This can be accomplished through the AOSOS software configuration or by using a hardware load balancer.

AOSOS Hosted Solutions

In a hosted AOSOS system, the Tier 2 through 4 servers – including the equipment, software and databases – are hosted and maintained by the AOSOS SC. Hosting is an alternative for states seeking to minimize their up-front investment. States that choose this option are still responsible for client PCs and public interface/WAN connectivity to the hosted system. For more information on the AOSOS Hosted solution, contact the America’s One Stop Operating System Service Center.

Base Network Configuration

Network bandwidth requirements will vary from state to state based on the number of concurrent users, the types of requests, and the volume of data being retrieved and updated. All network costs are the responsibility of the state.

All AOSOS installations have four major network components:

• State WAN

• Public Internet Connectivity

• State Data Center LAN

• VPN

State WAN

The state’s Wide Area Network (WAN) is used to connect AOSOS users in local Career Center offices with the state’s data center. Implementation of the state WAN, or use of an existing state WAN, is coordinated by the state. Physical network configuration is at the state’s discretion, as long as it supports TCP/IP and meets the bandwidth requirements for the number of concurrent users.

Public Internet Connectivity

The public internet may also be used to connect AOSOS users to the state’s data center. Interfaces from the public internet to the State Data Center LAN can be supplied and designed by the state. Public Internet connectivity must meet certain performance requirements for AOSOS.

State Data Center LAN

The data center LAN is at the core of the state’s AOSOS implementation. It provides secured communications between Tier 2 through Tier 4 servers for all application processing, and connects the servers to the state WAN and the public internet. Physical network configuration for the data center LAN follows fixed guidelines for specific sub-networks and server connectivity. Implementation of the state’s AOSOS data center LAN is the responsibility of the state.

VPN

The VPN is used to allow secured monitoring, upgrades and support by the vendor.

The following diagram shows an overview of a typical AOSOS network implementation:

AOSOS Software Architecture The AOSOS software architecture is comprised of three tiers that follow the industry standard Model-View-Controller (MVC) architecture. With MVC, and as implemented within AOSOS, aspects of the how the data is logically and physically housed and the business rules associated to the data are called the “model”. These are kept separate from the application’s visible presentation and input, or its “view”. The “control” layer manages the interactions between the business data and its rules and how that data is viewed by dispatching requests and controlling process flow. AOSOS implements the MVC architecture by separating presentation logic from application request and control logic from business rules and data storage.

Presentation Logic Tier The AOSOS presentation logic tier handles the mechanics of how data is presented to the system’s user. It manages how the data is visually organized and displayed, with simple edits such as numeric and date edits, and selection from value lists. This tier has four operational modes: four distinct applications supporting the three primary user communities, plus the Integrated API. All operational modes are supported by extensive user documentation, which is integrated directly into the four applications.

Mediated Client Application The Mediated AOSOS client application is the primary interface for counselors and intake resources. It includes modules for detailed customer information, comprehensive assessment and customer services, for employers and jobs, and for providers and service offerings. Each module is supported by search functions, custom tabs and customizable security rules. The staff module provides an inbox of system-generated reminders, customer referrals and a payment approval function for supervisors. Other features included are customizable messaging, attachments, correspondence, alterable links and personalized search results.

The Mediated application was designed to incorporate the power of a traditional client/server business application together with the portability of a browser-based web application. Although rendered via a browser, the users do not "browse" the system; the Mediated application is a powerful operational business system designed to meet the specific needs of workforce professionals. It is designed visually to simulate the look and feel of a traditional client/server application. The users interact with the system according to the workflow rules embedded within it. The major modules are presented as a series of tabbed windows. Buttons provide navigation to lower level modules, or display pop-up windows. Errors captured by both presentation and application layers are displayed using a standard pop-up window.

Drop-down selection lists are used throughout the application to simplify data entry while enforcing basic data integrity.

The Mediated AOSOS application is also designed to use internetworking technologies to deliver the application over any TCP/IP connection (such as internet, state WAN or intranet, or data center LAN) to any sufficiently large Windows XP (and up) PC using Internet Explorer 7.0 or higher and other standard browsers. No specialized installation is required to deploy the application.

Data is transmitted to and from the Mediated application using HTTP over a Secure Sockets Layer (SSL) connection. The transactions are represented as XML (eXtensible Markup Language) data islands. XML allows data to be transmitted as documents that conform to the layouts expected by the application logic tier. The application leverages Microsoft's ActiveX objects capabilities to store and manipulate XML-based transaction data. Most presentation markup is handled by HTML directly, supported by Cascading Style Sheets (CSS).

Modules and tabs are implemented using I-Frames that allows several layers of web page to be managed simultaneously, but only allow one layer to be visible at one time. XSL Transforms are used to dynamically generate the HTML for some pop-up windows. JScript is used to manage communications with the state's data center web server, for data binding, for navigation and other utility functions. It also provides any client-side security and edits needed to use the system efficiently.

Self-Service Client Application The JobZone/CareerZone application consists of five tiers: the Client Tier, the Presentation Tier, the Business Tier, the Enterprise Information Tier and the Database Tier. Client Tier supports the HTTP client and services client. Presentation Tier is implemented with JavaServer Faces, Facelets and PrimeFaces component library. The Business Tier contains application-specific business logic, system-level services and security. The Enterprise Information Tier consists of the Glassfish application server, which is bundled with Apache Felix as an OSGi framework. The Database Tier uses Oracle 10g or higher.

JobZone is focused on the needs of adult job seekers. CareerZone is focused on the needs of middle school and high school youth. Together they provide for visually appealing career exploration and self-assessment. Job seekers maintain account information, resumes and cover letters. Youth maintain a variety of age-specific career counseling-focused data points to create a career plan document. Google Translate option is available sot that job seekers can read JobZone/CareerZone in other languages. JobZone/CareerZone (JZ/CZ) was developed using Open Source Java Frameworks and components as a true SOA-based application that fully integrates with AOSOS. The system has the ability to operate on standalone PCs without internet connectivity.

The complete technology stack of JZ/CZ is as follows:

· GlassFish Server Open Source Edition

· Spring Framework

· EclipseLink JPA (Included in GlassFish Server)

· Spring Integration

· Maven

· Spring WebFlow

· jQuery

· HTML and CSS

· Java Server Faces (JSF)

· NetBeans

· Eclipse

· Spring Dynamic Modules

Administration Client Application The Administration client application provides selected state administrative resources the ability to maintain the state's list of workforce staff and offices, the state's security rules, its state-configurable lists of values and any Custom Tab functionality used by the state. It also allows for maintenance of the state's funds and its federal reporting performance measures. The Administration application uses the same technology profile as the Self-Service application.

Reports Access and Maintenance Client Application The Reports Access and Maintenance client application provides authorized users the ability to generate and view federal and local reports and extracts generated by the system.

Local WIA Management Reports Application This fifth application graphical user interface (GUI) is available and may possibly require future maintenance if business rules change. It provides authorized users the ability to view federal and local reports generated by the system. This application provides the Local WIA Management Reports (LWIA-MR) developed by the State of New York to supply localized versions of WIA reporting data to WIBs and offices. These capabilities will be supplemented by additional reporting features designed to support local management, operations and performance reporting.

Integrated API To provide a means for state applications to interface with AOSOS, the standard set of XML documents used to communicate between the Mediated client application and the application logic tier has been formalized as an Application Programming Interface (API). The Integrated API for AOSOS is the published set of XML documents used to provide standard access to all AOSOS business rules and data resources. The Integrated API may be used to integrate AOSOS data to a state's back-end legacy application, or to create another front-end client application for a specialized user group.

This capability affords states the ability to seamlessly integrate AOSOS data with other state data resources. It can also be used for initial data conversion, and for ongoing conversion as new agencies are brought online.

Application Logic Tier The application logic, or “middle tier", is founded on an object-oriented application framework that serves as the proxy between transactional business information represented by classes and their physical representations as database tables and search engine indices. The application framework handles all utility functions, such as parsing XML documents, basic field edits and error handling. The framework also provides database inquiries and updates, dynamic query generation, security authentication and authorization, and resource management. Business information classes are layered on top of the framework. These provide all application-specific business rules such as complex validation logic and specialized processing.

Relationships between instances of the business objects are managed at this level, both between parent and child objects and in lists of peer-level objects.

The Mediated and Self-Service applications both use the Middle Tier classes, as does the Integrated API. The Mediated application and API make full use of the underlying application framework, whereas the Self-Service application leverages the Middle Tier class business logic from within specialized business classes for Self-Service executed by the Active Server Page (ASP) server. The ASP server also generates the pages for the Administration application.

All web pages and XML documents are served by the Apache web server. Apache handles interactions with the Middle Tier and the ASP server, as well as data encryption using SSL. All business logic in this tier is written in Python, a powerful object-oriented language. Objects developed in C are used to perform some low-level utility processing. Client session information is managed by a MySQL database in this tier.

Also, included within the application logic tier are batch processes managed by UNIX shell scripts. These include background tasks such as generating staff inbox reminders, removing aged data and running automated job searches for Self-Service customers. Specialized interfaces are also managed though batch scripts. Currently these include feeding resume data to, and job data both to and from external Job Bank web sites, creating the WIASRD and TAPR files, loading wage data from the state's Unemployment Insurance system, writing IVR (Interactive Voice Response) requests to the state's third party IVR system, and interfacing fund obligations and payments to the state's fiscal system. Finally, the application logic tier includes all reporting scripts, which process and summarize data in the warehouse to create the reporting data accessed from the Reports Access and Maintenance application. Batch processes are written in Python.

Data Storage Tier AOSOS is delivered to use either the Enterprise Edition or Standard Edition 10 as its DBMS. Oracle manages the storage and all interactions with persistent data, and can support very high transaction volumes. It provides a robust, scalable platform and handles issues such as concurrency, rollbacks and commits, and backup and recovery.

The data tables are organized into two schemas. The primary schema holds all business transaction and supporting data. The warehouse schema contains both current and historical transaction data, as well as generated reporting data. It supports all mandated reporting at the federal, state and local level, as well as ad hoc queries using the state's third-party query software. In keeping with the architectural principle of isolating business logic from data storage, only minimal use is made of Oracle triggers, functions and stored procedures for low-level, non-business purposes. This also simplifies the task of moving to another DBMS platform should that become a requirement.

This tier also contains two specialized, non-persistent data structures used in searching for job seekers and job orders. The seeker and job search indices are engineered to respond rapidly to the very complex query capabilities supported by the Mediated and Self-Service applications, including geographic and text-based searches.

Processing in this tier includes scripts to populate and maintain the search indices, and to import data from the primary database to the warehouse database.

Bid Solicitation 25DPP01053 image1.png image2.emf

Microsoft_Visio_2003-2010_Drawing.vsd Cloud

IBM Compatible

Router

Hub

Tower box

Server

Minicomputer

Bridge

Public Internet

OSOS Clients

Router

State WAN or Intranet

Public Switch

State Interfaces/API

Admin Switch

Web Servers

App Server

App Server

Search Server

Database Server

Warehouse Server

Backup Switch

VPN

Vendor Support

Firewall other state machines

State

LAN

OSOS Clients

AOSOS RFP Exhibit 1: Network Configuration 1/8/2018

Report Server

PTR

image3.emf