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 92 changed 2 lines
Deployment Types
The same EAR can be used for all 3 types of deployments: Load Sharing, Report Server and Stand Alone applications. An example of a stand-alone application is one application instance to one database. With the exception of stand-alone applications, all instances must define the deployment type as one of the following JVM arguments:
;Deployment Types:The same EAR can be used for all 3 types of deployments: Load Sharing, Report Server and Stand Alone applications. An example of a stand-alone application is one application instance to one database. With the exception of stand-alone applications, all instances must define the deployment type as one of the following JVM arguments:
At line 98 changed 2 lines
Instance options
Load Sharing instances can be deployed in several ways:
;Instance options:Load Sharing instances can be deployed in several ways:
At line 108 changed 2 lines
Configuration File Location
A file named connections.config must be created for every application deployment, and modified by the system administrator to reflect the available deployments. The applications listens for changes to this file and they are picked up in a matter of seconds.
;Configuration File Location:A file named connections.config must be created for every application deployment, and modified by the system administrator to reflect the available deployments. The applications listens for changes to this file and they are picked up in a matter of seconds.
At line 114 changed 2 lines
Changes to JNLP file
Since the RMI port is now retrieved from the Servlet when the client side application starts up, there is no need to add it into the JNLP file. However, if a PORT argument is in the JNLP file, the client will use it to connect to the same RMI port every time (ie) It will use the old implementation to connect to the server and no load sharing or separate report server will be accessed, even if they exist.
;Changes to JNLP file:Since the RMI port is now retrieved from the Servlet when the client side application starts up, there is no need to add it into the JNLP file. However, if a PORT argument is in the JNLP file, the client will use it to connect to the same RMI port every time (ie) It will use the old implementation to connect to the server and no load sharing or separate report server will be accessed, even if they exist.
At line 123 changed 2 lines
File Attachment Folders
If the report server is setup on a different machine, the file attachments folder must be accessible to this server as well in order to save and retrieve report output files. In this case, you must also specify the network path, rather than the local machine path to the directory on the IMST preferences tab.
;File Attachment Folders:If the report server is setup on a different machine, the file attachments folder must be accessible to this server as well in order to save and retrieve report output files. In this case, you must also specify the network path, rather than the local machine path to the directory on the IMST preferences tab.
At line 126 changed 2 lines
Suggested Deployments
Every instance can be placed on a different machine, or they can all run within the same application server. It depends on available system resources, and the cost of licensing more application servers.
;Suggested Deployments:Every instance can be placed on a different machine, or they can all run within the same application server. It depends on available system resources, and the cost of licensing more application servers.
At line 132 changed 3 lines
Questions / Additional Notes
!Questions / Additional Notes
At line 136 changed 5 lines
• What are the specifications needed to support Clustering in an Oracle Application Server?
• Is Clustering easier to support in a WebLogic Application Server?
• Should we consider supporting more than one Report Server instance?
• Can the configuration file be replaced with logic reading connection info directly from OAS?
• Need to form suggested deployment configurations and memory settings (Separate Project)
*What are the specifications needed to support Clustering in an Oracle Application Server?
*Is Clustering easier to support in a WebLogic Application Server?
*Should we consider supporting more than one Report Server instance?
*Can the configuration file be replaced with logic reading connection info directly from OAS?
*Need to form suggested deployment configurations and memory settings (Separate Project)
At line 142 changed one line
Development Problems / Issues
!Development Problems / Issues
At line 148 changed one line
Resources Released
!Resources Released
At line 150 changed 4 lines
• Sample ePersonality.JNLP file
• Sample connections.config file
• Deployment descriptor web.xml
• Source code changes
*Sample ePersonality.JNLP file
*Sample connections.config file
*Deployment descriptor web.xml
*Source code changes
At line 155 removed one line
This page (revision-14) was last changed on 26-Nov-2021 10:22 by rforbesTop