Application Server
Transcription
Application Server
WebSphere Application Server Concept Frédéric Dutheil [email protected] Certified IT Architect WebSphere Technical Sales and Solutions 1 WebSphere Application Server Les éditions disponibles WAS WASND ND WAS WASzOS zOS WAS WASHypevisor Hypevisor WAS WAS WAS WASExpress Express WAS WASLiberty LibertyProfile Profile Core CoreEdition Edition Un serveur d’application innovant rapide et hautement personnalisable. “use what do you need” Fournit un accès sécurisé, un moteur de haute performance pour des transactions de taille moyenne avec des capacités de clustering et de cache applicatif. Permet une haute disponibilité, avec des capacités de performance et de gestion avancées, pour des applications à mission critique. Application Server The platform on which Java language-based applications run. It provides services that can be used by business applications, such as database connectivity, threading, and workload management. Application Server Architecture Internal architecture of WebSphere Application Server Available in ND platform only. Base and Express doesn’t have this capability Standalone Application Servers each application server acts as a unique entity (functions independent from all others) each can be managed from its own administrative console stand-alone servers can be managed from a central point by using administrative agents and a job manager Distributed Application Servers a distributed server configuration ‒ built by the Network Deployment packaging ‒ enable central administration, workload management, and failover Profiles Runtime environments are built by creating profiles. Product files ‒ a set of read-only static files or product binary files that are shared by any instances of the WebSphere Application Server product. Configuration files (profiles) ‒ a set of user-customizable data files. This file set includes WebSphere configuration, installed applications, resource adapters, properties, log files, and so on. Profiles Each profile is stored in a unique directory path Cell A grouping of nodes into a single administrative domain. In the Base and Express configurations: ‒ contains one node and that node contains one server Cell in ND Environment A Cell is a virtual unit that is built of a Deployment Manager and one or more nodes. The Deployment Manager is a process (in fact it is an special WAS instance) responsible for ‒ ‒ ‒ ‒ Managing the installation and maintenance of Applications Connection Pools and other resources related to a J2EE environment Centralizing user repositories for application Centralizing WAS authentication and authorization. Can contains nodes that are running on mixed platform Node, Node Agent, Server The Node ‒ virtual unit that is built of a Node Agent and one or more Server instances One Node = One Profile The Node Agent ‒ Process responsible for spawning and killing server processes and also responsible for configuration synchronization between the Deployment Manager and the Node. Servers ‒ Java process responsible for serving J2EE requests (eg.: serving JSP/JSF pages, serving EJB calls, consuming JMS queues, etc). Cell in Standalone & Network Deployment Environment Admin Agent is a component that provides enhanced management capabilities for stand-alone (Express and Base) application servers Web Server Plug-in The web server plug-in is used to route requests to one of multiple application servers Cluster virtual units that groups Servers servers is managed together resources added to the Cluster are propagated to every Server that makes up the cluster Provide highly available ‒ because requests are automatically routed to the running servers in the event of a failure A cell can include no clusters, one cluster, or multiple clusters Optimizes the distribution of client processing requests Workload management in term of ‒ Servlet using HTTP traffic-handling device, e.g IBM HTTP Server ‒ EJB requests Vertical & Horizontal Clustering (Scaling) Vertical Horizontal Mixed Clustering http://www.ibm.com/software/fr/websphere/