Development Overview Guide - x100.docs.unionsg.comx100.docs.unionsg.com/SystemOverview2_50.pdf · 2...

Copyright © Union System Global

Development Overview

Guide

Release 2.50

UNION SYSTEM

GLOBAL

MARCH 9, 2015

Development Overview Guide Release 2.50

i

Copyright © Union Systems Global

Copyright and Trademark Notifications

X.100 is a Trademark of Union System Global.


ii


Copyright © 2013 by Union System Global

All rights reserved. No part of this document may be reproduced, distributed, or

transmitted in any form or by any means, including photocopying, recording, or

other electronic or mechanical methods, without the prior written permission of

Union System Global, except in the case of brief quotations embodied in critical

reviews and certain other noncommercial uses permitted by copyright law. For

permission requests, write to Union System Global, addressed “Attention:

Permissions Coordinator,” at the address below.

Union System Global

No 4, Jungle Lane,

Lartebiokorshie, Accra, Ghana

Phone: +233 302 678178

Fax: + 233 302 679981

E-mail: [email protected]


iii



iv


Table of Contents

1 INTRODUCTION ................................................................................1-1

1.1 Union UBS Functional architecture overview .............................................................1-2

1.2 UNION UBS Technical architecture overview............................................................1-3

2 OVERVIEW OF FORMS 11G ...........................................................2-4

2.1 Oracle Forms Developer ....................................................................................................2-4

2.2 Oracle Forms Services .......................................................................................................2-4

2.3 Oracle WebLogic Server ...................................................................................................2-5

2.4 The Oracle Forms Client...................................................................................................2-5

2.5 Forms applications ..............................................................................................................2-5

2.5.1 Forms Runtime Process ............................................................................................2-6

2.5.2 Forms Listener Servlet..............................................................................................2-6

3 ORACLE DATABASE ........................................................................3-7

4 CONNECTION PROCESS .................................................................4-8

5 OPERATIONAL SUMMARY ..........................................................5-11


1-1


1 INTRODUCTION

This development overview document provides the bird’s eye view of Union

UBS Application development. It touches the concepts, frameworks and tools

required for guidance.

Union Application development consists of three parts:

Framework development.

Tools development.

Application components development using Framework/Tools.


1-2


1.1 UNION UBS FUNCTIONAL ARCHITECTURE

OVERVIEW

This diagram provides the functional architecture of the Union UBS.


1-3


1.2 UNION UBS TECHNICAL ARCHITECTURE

OVERVIEW

The diagram depicted below represents the tiered union technical

architecture:

User Interface tier uses any Java supported Browser system

available on most OS today.

Process tier is developed using Oracle 11G forms and Reports

systems with about 10% infusion of Java and JavaScript’s - It

is a pure Oracle tool for development and SQL, CoreJava and

PL-SQL as a base inner tools for development

Application and Integration tier employs 100% of Oracle

WebLogic 11G server with an option for clustering (Picture of

this will be shown more vividly in the next few pages)

Database tier runs fully on Oracle 11G relational Database

using SQL, PL-SQL and Core Java for Development.


2-4


2 OVERVIEW OF FORMS 11G

Oracle Forms is a component of Oracle Fusion Middleware. Oracle Forms is

used to develop and deploy Forms applications. The Forms applications

provide a user interface to access Oracle Database in an efficient and tightly-

coupled way. The applications can be integrated with Java and web services

to take advantage of service oriented architectures (SOA).

Oracle Forms includes the following:

Oracle Forms Developer, used to develop and compile Forms

applications.

Oracle Forms Services, a server component, used to deploy the

applications.

2.1 ORACLE FORMS DEVELOPER

Oracle Forms Developer is used to develop a form that can access an

Oracle database and present the data. Wizards and utilities are provided

to speed up application development. The source form (*.fmb) is

created and compiled into an "executable" (*.fmx). The Forms

application is run (interpreted) by the Forms Runtime process.

2.2 ORACLE FORMS SERVICES

Oracle Forms Services is a comprehensive application framework

optimized to deploy Forms applications in a multitier environment. It

takes advantage of the ease and accessibility of the Web and elevates it

from a static information-publishing mechanism to an environment

capable of supporting complex applications.

The Form applications that you design and develop in Oracle Forms

Developer are deployed on Oracle Fusion Middleware. These

applications run on the middle tier (see next diagram). The user

interface is presented on the client tier as a Java applet in the client's

browser.


2-5


This guide describes the configuration files, and environment variables

that can be used to customize deployment of Forms applications. It also

provides information on performance, logging and monitoring your

deployment. You can use Oracle Fusion Middleware Enterprise

Manager Control to manage the configuration files, and environment

variables, and monitor the deployment.

2.3 ORACLE WEBLOGIC SERVER

Oracle WebLogic Server 11g is an application server for building and

deploying enterprise Java EE applications with support for new

features for lowering cost of operations, improving performance and

supporting the Oracle applications portfolio.

Regardless of whether you want to create a staging, production, or

testing environment, you begin by creating a WebLogic domain. A

WebLogic domain includes instances of WebLogic Server, of which

one is configured as an Administration Server. The Administration

Server maintains configuration data for a domain. You can deploy your

application on Administration Server but it is recommended to create a

managed server and deploy your application in managed server.

2.4 THE ORACLE FORMS CLIENT

When a user runs a Forms session, the Forms Client - a thin 100

percent Java applet - Dynamically downloads from the Oracle Fusion

Middleware Application Server. This generic Java Applet provides the

user interface for the associated Forms Runtime process on the middle

tier, and handles user interaction and visual feedback such as that

generated by navigating between items or checking a checkbox. The

same Java applet is used for all Forms application, therefore it is

downloaded only once and cached on the client and so is available for

subsequent.

2.5 FORMS APPLICATIONS


2-6


In order to run a Java applet in a browser, it is necessary to have a Java

Virtual Machine (JVM) installed. The JVM is installed on the client

and is platform dependent. Oracle recommends and certifies Sun's JRE

1.6 for this release of Oracle Forms Services.

2.5.1 FORMS RUNTIME PROCESS

The Forms Runtime process is the process that maintains a connection

to the database on behalf of the Forms Client. The process is created

when a user accesses a page containing a Forms application. The

process is automatically stopped as soon as the user closes the Forms

application or terminates the browser window.

2.5.2 FORMS LISTENER SERVLET

The listener servlet manages the following services in the form

application.

The creation of a Forms Runtime process for each client when

a user requests to run a Forms application.

The Forms Listener Servlet is also in charge of stopping the

Runtime process as the user closes the Forms application or

terminates the browser window.

Network communications between the client and its associated

Forms Runtime process.


3-7


3 ORACLE DATABASE

Oracle Database is the latest generation of RDBMS. Among the numerous

capabilities are unlimited scalability and industry- leading reliability with

Oracle Real Application Clusters; high availability technology including

advancements in standby database technology (Oracle Data Guard); and

built-in OLAP, data mining and Extract, Transform and Load (ETL)

functions.

The diagram below shows the full Picture of the Unions Universal Banking

System deployment on Oracle three tier Architecture.


4-8


4 CONNECTION PROCESS


4-9


The user chooses a Link from a web page or types a URL directly in

the browser (Link or IP address should point directly Union Universal

banking as directed by the administrator)

The HTTP Listener interprets the URL that is passed and displays an

HTML page containing an <EMBED> or <OBJECT> tag (depending

on which browser is used) that describes the Forms Java Client to the

browser. The URL that is passed calls the Forms Servlet to create an

HTML page dynamically based on the base.html files located on the

web server.

The Client receives the HTML file served by the HTTP Listener. The

tag in the HTML file will supply the information required to locate

the Java Class files that make up the Forms Java Client. Within the

tag in the HTML file you would also supply information about the

form that should run, and any other parameters that you want to pass

to your Forms session, such as the Login information. The tag

definition also contains instructions on what Forms Services to run

and many parameters which can help you to customize aspects of the

Java Client such as the look-and-feel, color schemes etc.

The HTML file might also contain other HTML attributes such as

those to tell the browser to run this particular applet using a particular

version of the JRE on the client.

The browser then asks the HTTP Listener for the Java Class files

from the location specified in the HTML file. The CODEBASE

parameter in the HTML file is used to define this. The files may be

downloaded individually or as an “Archive”. This archive will have

an extension of .JAR or .CAB and can be best thought of as a .ZIP file

containing all of individual CLASS files required by the Applet. The

use of a JAR or CAB file speeds up the download of the Java Client

and enables caching on the client for subsequent calls. The ARCHIVE

parameter defines which (if any) .JAR or CAB file should be used.

The JRE plug-in will carry out the additional step of checking the

version of the Forms Client Java code available on the HTTP Listener

and will only download it if it turns out to be newer that any version

that the plug-in currently has cached.


4-10


The CLASS or JAR files are downloaded (if not already present) to

the browser and the Java applet starts.

The Java Client applet sends a request to start a Forms session

through the HTTP Listener to the Forms Listener Servlet. The Forms

Listener Servlet is defined by the server URL parameter in the HTML

file’s tag.

After receiving the connection request from the Java Client, the

Forms Listener Servlet starts a new Forms Runtime process for this

client. You can define user specific environments for each runtime

process by setting the Servlet initialization env File parameter in the

configuration file – formsweb.cfg - to a specific environment file,

default file is default.env and this file contains for example the Forms

ORACLE_HOME and FORMS_PATH.

The Forms Runtime process allocated to this client, loads the module

specified in the HTML file and any libraries and menus that are

required by that form. All communication between the Forms Client

and the Forms Runtime process is passed through the Forms Listener

Servlet.

The user is prompted for database login information, if this had not

already been supplied, and the connection to the database server is

established.


5-11


5 OPERATIONAL SUMMARY

X.100 comprises of four base components stored in the database

Tables - Holds the physical data in these structures.

View - Represents Data definitions logic used for mostly reporting.

Triggers - Used for event driven activities, SMS alerts, e-mails.

Procedures - This component hold the entire logic for all calculations

e.g. Interest calculations, Loan payments and many more.

Below Table shows Key TABLEs in the database deployed by X.100.

Table Names Description

G_ledger

Keeps record of all accounts both internal and external with balances

AC_trans

Keeps record of all transactions centrally in the database

Customer Keeps primary record of all customers(KYC)

Av_bals

Is a working Table and keeps all the daily calculations of interest , fees and COT ; It also stores the statistical balances of accounts like Maximum, Minimum, average balances

Facility Keeps records of loans and overdraft Details

Repayment_schedule Keeps records of loan repayments and schedules

Treasury Keeps records of all Investments e

Cheque_requisition keeps Cheque requisition details

INTB_Requisition Internet Bank Request

ATM_Accounts keep all Valid Atm Card Users

ATM_Requisition All Atm Card Request

SMS Requisition keeps SMS Requisition details

Account_balances_Month Stores Daily account balances(Historical)

Balance_sheet Keeps all the Balance sheet details

Cheque_issuance keeps Cheque issuance details

Branch Keeps Branch information


5-12


Branch_cash keeps the Branch cash

Code_desc ALL the codes and Parameters used in the system

Development Overview Guide - x100.docs.unionsg.comx100.docs.unionsg.com/SystemOverview2_50.pdf · 2...

Documents

Transcript of Development Overview Guide - x100.docs.unionsg.comx100.docs.unionsg.com/SystemOverview2_50.pdf · 2...