What is the Architecture of the Pramati Server?
Pramati Server, with the embedded Pramati Message Server, ensures a high-performance, scalable, and robust platform for component-based J2EE applications. It also provides a comprehensive set of tools for server management and administration.
What are the features of the Pramati Services Framework?
The Pramati Services framework allows standard infrastructure services, as well as specific Server services, to be plugged-in to the platform. It enables compatibility with other platform services by allowing them to plug-in or write to published APIs.
The Services Framework is a part of the Pramati kernel that consists of the following modules:
- Lifecycle Manager for managing services lifecycle
- Service Dependency Manager for taking care of services compatibility
- Configuration Manager for managing services configuration
- Java Authentication and Authorization Service based (JAAS-based) security infrastructure that offers security wrapper for deployed applications
- Advanced Management Framework that exposes Server APIs for remote management
- Logging for logging error, warning, and stack trace information
What are the features of the Pramati Security Framework?
The Server implements a JAAS framework that enables the application security realm to be selected based on business requirements.
What are the features of the Pramati Clustering Framework?
The Server provides a Cluster Services module for transparent and pluggable load balancing algorithms and failover mechanisms. This service works on a peer-to-peer model, with no master-slave relationship, and has no points of failure.
What are the features of the Pramati Server Management Console?
The Server ships with a Web-based Management Console that interacts with JMX-based management models, JSPs, and configurable MBean components. Administrators can customize the Console to create multiple views on a server. The Console provides a customizable infrastructure for enterprise server administrators. Through dynamic monitoring, tuning, and control of applications, system administrators can optimally deploy resources and extract maximum performance in any deployment scenario.
The Console can be configured to communicate alerts and other information to WAP-enabled devices. The Server is managed using the Console that relies on the Administration Service to list all Server configurations on the LAN. The Console is often used for deploying applications and configuring them. The Console is recommended as it has an intuitive interface.
Most of the activities that are performed by administrators are focused around configuring, tuning, and monitoring applications. Deploying of applications and configuring them is normally a one time activity, which is usually done using the Console.
An administrator can deploy and configure applications by using the Server command shell, or the Console. An administrator can also deploy and configure resources by either manually editing the XML configuration files present in the <install_dir>/server/nodes/<node_name>/config directory, or using the Server command shell. Of all the above, the Console is most often used (and recommended) as it has a more intuitive interface.
This guide discusses in details about how to manage Pramati Server using the Console, as also the ways in which you can use the Server command shell and the XML files to configure your resources and/or applications.
However, before you start reading about how to manage applications or components of the Server, it is suggested you read the topics covered under Pramati Server Technical Reference that discuss some necessary concepts for a better understanding of the Server and it’s architecture.
What are the features of the Pramati Server Administration Service?
The Server is configured and started using the Server Administration Service. The Service equips the administrator to:
- Discover various Server instances running on the LAN through a discovery mechanism based on User Datagram Protocol (UDP)
- Configure and start:
- The Server on local or remote host
- A Server Cluster on local or remote hosts
- Pramati Message Server on local or remote hosts
The Deploy Tool is designed for EJB 2.0 component deployment requirements. It provides an automatic resolution of Container Managed Relationships (CMRs) against target database schema, and writes the deployment descriptors. It provides the key intermediate step of preparing and saving the archives for distribution to multiple servers. It enables quick deployment on local and remote Servers by mapping the application to the target environment and writing server-specific descriptors.
The Deploy Tool:
- Assists in complex O-R mapping between entity beans and multiple databases
- Resolves relationships defined in the abstract persistence schema of the application with the database relationships
- Prepares archives for deployment by resolving O-R Mappings
- Allows setting of security, application resources (JMS, Mail, XA Connectors), and environment settings
- Validates enterprise archives for conformance to J2EE technologies
- Highlights incomplete tasks until the archive is fully validated and ready to be deployed
- Enables seamless deployment of applications on a cluster of J2EE Servers
Related Topics:
| 
