Centralized ACMS Environment and Web Services Specification for Project CUMULUS
This document outlines the high-level functional specifications for a centrally hosted ACMS environment designed to ensure secure HTTPS connectivity for client web services and data management. It includes the setup of individual client database instances on a single server and the integration of Agresso Smart Client via Citrix for systems administration. The project incorporates web services that comply with XCRI standards, provides a resource service for HR module population, and supports XML and SOAP. Additionally, it details integration using Microsoft BizTalk for monitoring and data orchestration.
Centralized ACMS Environment and Web Services Specification for Project CUMULUS
E N D
Presentation Transcript
Project CUMULUSHIGH LEVEL FUNCTIONAL SPECIFICATION ENVIRONMENT: • A Centrally Hosted ACMS Environment Comprising Of: • Secure HTTPS Connectivity To Individual Client Web Sites • Individual Client Database Instances On A Single Database Server • Agresso Smart Client Via Citrix Or Application Managed Service For Systems Administration • To Implement Microsoft ISA Server/Forefront Server To Manage Authentication
Project CUMULUSHIGH LEVEL FUNCTIONAL SPECIFICATION WEB SERVICES: • Secure HTTPS Connectivity To Individual Web Services Instances Per Client Organisation • To Provide A Curriculum Web Service That Will Be XCRI Compliant (See Detailed Spec.) • To Provide A Resource Web Service For Inbound Traffic Only That Will Be Used To Populate The ABW HR Module Within The Centrally Hosted ACMS Installation. • To Provide An Attributes Web Service , Which Will Be Two-way For The Retrieval And Updating Of Attribute Values (Reference Data) • All Web Services Will Conform To XML & SOAP Standards
Project CUMULUSHIGH LEVEL FUNCTIONAL SPECIFICATION INTEGRATION: • Using The Microsoft BizTalk SQL LOB Adapter We Will Monitor For Table Changes From Within ACMS • The BizTalk Orchestration Will Retrieve Change Data, Provide Transforms, And Allow For The Output Of Data To External Systems TO BE DEFINED: • A List Of External Systems To Be Used For The Testing Of The Proof Of Concept • Orchestration (Workflow) Requirements
