This page (revision-14) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
14 26-Nov-2021 10:22 11 KB rforbes to previous
13 26-Nov-2021 10:22 11 KB rforbes to previous | to last
12 26-Nov-2021 10:22 11 KB jmyers to previous | to last
11 26-Nov-2021 10:22 11 KB jmyers to previous | to last
10 26-Nov-2021 10:22 11 KB jmyers to previous | to last
9 26-Nov-2021 10:22 11 KB jmyers to previous | to last
8 26-Nov-2021 10:22 11 KB jmyers to previous | to last
7 26-Nov-2021 10:22 14 KB jmyers to previous | to last
6 26-Nov-2021 10:22 14 KB jmyers to previous | to last
5 26-Nov-2021 10:22 14 KB jmyers to previous | to last
4 26-Nov-2021 10:22 14 KB jmyers to previous | to last
3 26-Nov-2021 10:22 14 KB jmyers to previous | to last Load Sharing & Separate Report Server ==> LOAD SHARING AND SEPARATE REPORT SERVER
2 26-Nov-2021 10:22 14 KB jmyers to previous | to last
1 26-Nov-2021 10:22 14 KB jmyers to last

Page References

Incoming links Outgoing links
LOAD SHARING AND SEPARATE REPORT SERVER
LOAD SHARING AND SEPARATE REPORT SERVER

Version management

Difference between version and

At line 1 changed 2 lines
Load Sharing & Separate Report Server
Project Objective
[{TableOfContents }]
!!!LOAD SHARING AND SEPARATE REPORT SERVER
!!Project Objective
At line 10 added one line
At line 12 added one line
At line 14 added one line
At line 10 changed one line
Project Iterations
!!Project Iterations
At line 18 changed one line
Related CCARE Cases/Defects
!!Related CCARE Cases/Defects
At line 26 changed one line
Requirements / Features
!!Requirements / Features
At line 28 removed 10 lines
Separate Report Server
• Deploy an application instance to launch and process all reports
• Automatically forward report launching, running and scheduling to correct instance
• Scheduled reports must be run by Report Server instance
• Report status feedback information on report forms must be maintained
• Only (1) Report Server should exist for each database
• Requirement is that this instance is given higher system memory (heap size)
• [2nd] Divvy services & watchers between application and report server appropriately
• [3rd] Limit number of reports to run simultaneously and schedule others (Queuing)
• [4th] Remove unneeded packages from report server EAR file
At line 39 changed 5 lines
Load Sharing
• Deploy multiple applications in parallel to evenly share load of users
• Automatically forward users logins to available instances in 'Round-Robin' pattern
• Do not rely on connection information saved on client - check server for every login
• [5th] Implement Oracle specifications to support Clustering/Load Balancing
!Separate Report Server
*Deploy an application instance to launch and process all reports
*Automatically forward report launching, running and scheduling to correct instance
*Scheduled reports must be run by Report Server instance
*Report status feedback information on report forms must be maintained
*Only (1) Report Server should exist for each database
*Requirement is that this instance is given higher system memory (heap size)
*[2nd] Divvy services & watchers between application and report server appropriately
*[3rd] Limit number of reports to run simultaneously and schedule others (Queuing)
*[4th] Remove unneeded packages from report server EAR file
At line 45 changed 6 lines
Common Features
• Feature should not be mandatory (ie) only used as needed
• Number and location of application instances must be configurable
• Configuration file on server file system specifies available applications
• Configuration file should be monitored to allow for dynamic updating without restarting applications
• Must be seamless to user - login as normal and system will forward requests between available instances
!Load Sharing
*Deploy multiple applications in parallel to evenly share load of users
*Automatically forward users logins to available instances in 'Round-Robin' pattern
*Do not rely on connection information saved on client - check server for every login
*[5th] Implement Oracle specifications to support Clustering/Load Balancing
At line 53 added 6 lines
!Common Features
*Feature should not be mandatory (ie) only used as needed
*Number and location of application instances must be configurable
*Configuration file on server file system specifies available applications
*Configuration file should be monitored to allow for dynamic updating without restarting applications
*Must be seamless to user - login as normal and system will forward requests between available instances
At line 53 changed 9 lines
Development Approach
This is an optional section to describe the steps the developer would go through in fulfilling the project goals.
See Implementation section below.
Implementation
!!Implementation
At line 63 changed one line
Overview
!Overview
At line 66 changed 3 lines
Application Implementation
Connections
There are two types of connections made when launching EPersonality; First, the client must visit a link on a web server to download several files which include the java archive (JAR) files containing our code, JARs containing pictures, icons and configuration files, as well as a JNLP file. The JNLP file contains the information to make the second connection to the application server, through which all application communication is routed thereafter. A sample of this part of the JNLP file is included below:
!Application Implementation
;Connections:There are two types of connections made when launching EPersonality; First, the client must visit a link on a web server to download several files which include the java archive (JAR) files containing our code, JARs containing pictures, icons and configuration files, as well as a JNLP file. The JNLP file contains the information to make the second connection to the application server, through which all application communication is routed thereafter. A sample of this part of the JNLP file is included below:
At line 76 changed 2 lines
Configuration File
We created a configuration file on the server which contains a comma-separated list of all available application instances as well as a report server instance. A sample of the file is included below:
;Configuration File:We created a configuration file on the server which contains a comma-separated list of all available application instances as well as a report server instance. A sample of the file is included below:
At line 85 changed 3 lines
Servlet
We built a small Java Servlet into the application to 'serve up' this information to clients application when they want to connect. The servlet will iterate over the list for every login, such that the first user logging in will be directed to the first server in the list, the second user login will be directed to the second server in the list, and so on. The servlet will continually repeat through the list in an effort to distribute online users evenly over the available applications. Each client will also retrieve the report server information, in the event they wish to run a report at any time during their session.
;Servlet:We built a small Java Servlet into the application to 'serve up' this information to clients application when they want to connect. The servlet will iterate over the list for every login, such that the first user logging in will be directed to the first server in the list, the second user login will be directed to the second server in the list, and so on. The servlet will continually repeat through the list in an effort to distribute online users evenly over the available applications. Each client will also retrieve the report server information, in the event they wish to run a report at any time during their session.
At line 92 changed 2 lines
Client Side
Now, when launching EPersonality, three connections are made, the first to download the JARs and JNLP, the second to connect to the servlet and retrieve information to make the third connection to the server which will handle all application communication. The second step also receives connection information to a report server, and a fourth connection may be made if the user launches a report during their session.
;Client Side:Now, when launching EPersonality, three connections are made, the first to download the JARs and JNLP, the second to connect to the servlet and retrieve information to make the third connection to the server which will handle all application communication. The second step also receives connection information to a report server, and a fourth connection may be made if the user launches a report during their session.
At line 96 changed one line
Set Up
!Set Up
This page (revision-14) was last changed on 26-Nov-2021 10:22 by rforbesTop