Contract Information Management System (CIMS) Technical System Architecture

Transcription

1 Technical System

2 REVISION HISTORY REVISION NUMBER ISSUE DATE PRIMARY AUTHOR(S) NOTES 1.0 2/2015 Cheryl Kelmar Software: Kami Phengphet Engineer: Pornpat Nikamanon Architect: Jim Zhou Creation of CIMS document. 2

3 The employs an optimized Oracle solution, which combines key components in computing, storage, networking and software. It employs a traditional architecture that is flexible and scalable. The CIMS' Architectural components are: Oracle Application Development Framework (ADF) and User Facing APIs Servers (Web Logic: Main, Universal Content Manager (UCM), WC_Space and Portlets) Oracle Database as a Repository and EAR files Oracle Fusion Middleware Control (OFM) = Main Server: Web Logic) JDeveloper for Coding Browser Controller (Internet Explorer and Chrome) Figure 1: CIMS 3

4 The CIMS' relies on an Oracle based application development framework (ADF), as depicted in Figure 2, which is an end to end application that builds on Java Platform, Enterprise Edition (Java EE) standards and open source technologies. The Oracle ADF model implements data controls using standard metadata interfaces that describe the service's operations and data collections, including information about the properties, methods, and types involved. An application module is the transactional component that clients use to work with application data. CIMS' customized system diagram is depicted in Figure 2. Figure 2 Application Development Framework (ADF) The ADF task flows represent the critical components toward a modular approach in defining control flow CIMS' applications. Instead of representing an application as a single large Java Server Faces (JSF) page flow, they can divided into reusable task flows. Task flows have the advantage of being able to be packaged and deployed with the application, rather than requiring a separate deployment like remote portlets. The technology stack includes the Active Data Service (ADS), which allows a user to bind ADF Faces components to an active data source. The CIMS administration domain is comprised of an Oracle WebLogic Server administration domain, which is a logically related group of Java components that includes a special WebLogic Server instance called the Administration Server. The 4

5 WebLogic Server Administration Console and Fusion Middleware Control run in the Administration Server. When a domain is created, a particular domain template is used to support a particular component, or group of components, such as the Oracle Service Oriented (SOA) Suite. The WebLogic Server Administration Console is the Web-based administration console used to manage the resources in a WebLogic Server, including the Administration and Managed Servers. Fusion Middleware Control is a web-based administration console used to manage the Oracle based Fusion Middleware. The Administration Server is the central point from which a user configures and manages all resources in the domain, and which operates as the central control entity for the configuration of the entire domain. It maintains the domain's configuration documents and distributes changes in the configuration documents. The CIMS Java EE application is delivered in an Enterprise Archive (EAR) file, which is a standard Java Archive (JAR) file with an.ear extension. Using EAR files and modules makes it possible to assemble a number of different Java EE applications using some of the same components. No extra coding is needed. It is only a matter of assembling (or packaging) various Java EE modules into Java EE EAR files. An EAR file contains Java EE modules and deployment descriptors. A deployment descriptor is an XML document with an.xml extension that describes the deployment settings of an application, a module, or a component. Because deployment descriptor information is declarative, it can be changed without the need to modify the source code. At runtime, the Java EE server reads the deployment descriptor and acts upon the application, module, or component accordingly. 5

6 Universal Content Manager (UCM) serves content to portals. A portlet is a reusable web component that can draw content from many different sources. Portlets provide a means of presenting data from multiple sources in a meaningful and related way. Portlets can display excerpts of other web sites, generate summaries of key information, perform searches, and access assembled collections of information from a variety of data sources. Because different portlets can be placed on a common page, the user receives a single-source experience. In reality, the content may be derived from multiple sources. User Facing APIs, part of ADF Components for vendor and administration portal. The content management system for CIMS is Oracle's Universal Content Management (UCM) system, which is deployed as a managed server in the WebLogic Application Server. This robust content management system provides the foundation for collaboration, offering CIMS' users the ability to manage documents and output for multiple author editing and participation. This single-architecture approach allows all managed content and services to be accessed by a common user and administration interface, improving user efficiency and reducing the amount of time required to train business users and administrators. Most systems use a content repository or a database to store page content, and other information assets that might be needed by the system. CIMS' Administration is typically done through browser-based interfaces. The content management system allows non-technical users to make changes to a website with little training. The CIMS database cluster interfaces with the Enterprise Resource Planning (ERP). In JDeveloper, individual components are configured in JSF pages to display active data. Active data is pushed to the client whenever a change event is raised by the 6

7 web data source. The data is pushed from the server to the client and displayed by the browser. The UCM's adapter configuration allows for the collection of proper identification and credentials information for the Oracle based Universal Records Management (URM) system to process security and communications. The UCM Adapter provides basic retention functions. The UCM Adapter monitors batch processes, handles communication errors with the URM, and handles large work requests by grouping them into communication blocks and processing the response in chunks. The UCM Adapter monitors its server's content vault by periodically searching the repository and informing the URM of any changes in the repository that may affect disposition processes or audit holds. Configuration information also includes mapping metadata fields and defining searches. There is one portal that contains the navigation elements are contained in the EAR files through the repository. EAR files deploy the application on the WC_Spaces server. The metadata repository in CIMS is database-based with a specific schema that belongs to a specific Oracle Fusion Middleware component. The Oracle Metadata Services (MDS) repository, contains metadata for most Oracle Fusion Middleware components. The Metadata Repository contains metadata for Oracle Fusion Middleware components, such as metadata for your applications. Managed Servers in the domain are created specifically to host those particular Oracle Fusion Middleware components. Oracle Fusion Middleware Java components, as well as customer-developed applications, are deployed to Managed Servers in the domain. 7

8 CIMS' specific Fusion Middleware components include: WebLogic Server, SOA Suite, Application Development Framework, JDeveloper, Enterprise Content Management Suite, Data Integrator and Secure Enterprise Search. The RAC provides the following key characteristics: Reliability Removes the database server as a single point of failure. If an instance fails, the remaining instances in the cluster remain open and active. Cluster ware monitors all processes and immediately restarts any failed component. Error Detection Cluster ware automatically monitors RAC databases as well as other processes and provides fast detection of problems in the environment. It also automatically recovers from failures often before users notice that a failure has occurred. Recoverability The Database includes many features that make it easy to recover from various types of failures. If an instance fails in an RAC database, it is recognized by another instance in the cluster and recovery will start automatically. Continuous Operations RAC provides continuous service for both planned and unplanned outages. If a server (or an instance) fails, the database remains open and applications continue to be able to access data, allowing for business critical workloads to finish, mostly without a delay in service delivery. The CIMS' portals support interportlet communication, and can be linked with Web Services for Remote Portals (WSRP) 2.0 portlets, such that parameters are passed between portlets and Faces components, and between portlets and the page. A user can build portals using a variety of different technologies and approaches and open 8

9 industry standards for portal-building. CIMS' specific Portal is displayed in Figure 3. CIMS' Oracle Based Portal Figure 3: CIMS Oracle Based Portal The CIMS' specific WebCenter Portal is depicted in Figure 4. CIMS' Oracle WebCenter Portal Topology Figure 4: CIMS' Oracle based WebCenter Portal Topology Figure 1: CIMS... 3 Figure 2 Application Development Framework (ADF)... 4 Figure 3: CIMS Oracle Based Portal... 9 Figure 4: CIMS' Oracle based WebCenter Portal Topology

10 10