![]() |
|
Timing diagnostics in Pramati Server gives an idea about various operations and the performance of Server and application. It enables to identify and analyze an activity, and helps to calculate the time taken by a logical unit of operation. This helps to identify and eliminate bottlenecks at runtime. It provides an inside view of the time taken by various business operations and helps to split time across sub tasks. To know more, read add link to Server diagnostics.
Pramati Server provides the following diagnostic data:
The Web-based Pramati Server Management Console is the primary tool that manages and monitors the Server instances, clusters, and J2EE applications deployed on them. The Console provides a customizable infrastructure for enterprise server administrators. Dynamic monitoring, tuning, and control of applications enable to optimally deploy resources and extract maximum performance in any deployment scenario.
Application parameters such as bean pool size can be set from the Deploy Tool while preparing an application for deployment. jars, wars, and ears can be deployed independently in a target Server environment. Deploy Tool should be aware of the target Server environment properties. To deploy any application, Deploy Tool first starts the Server.
Console and Deploy Tool internally setup the Server XMLs. When needed, the XML files can be setup by the administrator.
Server parameters can be modified by editing server-config.xml, located at <install_dir>/server/nodes/StandAlone/<node_name>/config/.
For clusters, cluster-config.xml is located at <install_dir>/server/nodes/Cluster/<cluster_name>/config/.
Application parameters can be tuned by modifying:
pramati-j2ee-server.xml, which is application specific and contains parameters for configuring bean pool sizepramati-or-map.xml, which is entity bean specific and contains O-R mapping information and flags for concurrency and exclusion types
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |