Академический Документы
Профессиональный Документы
Культура Документы
1) J2EE Technologies
Description The capability of a system to process client requests with little or no down time Distributing incoming client Load-balancing requests to system resources
The capability of a system to transfer control to a backup component when a fault occurs The capability of a system to process increasing client request volume without service degradation The capability of a system to identify users and control access to sensitive data A measure of the ease with which a system can be upgraded, debugged, configured and reconfigured
Client-tier Protocols:
Supported TCP/IP Protocols:
Application server:
An Application Server does the following:
It provide services that support the execution and availability of deployed applications It handles heavier processing tasks than a Web server does
Definition: Server
1). A server is an instance of weblogic. Server executing in a JVM.
2). A server:
Definition: Machine
1). A machine is a computer that hosts WebLogic Server. 2). A machine:
Runs a supported operating system platform Can host multiple WebLogic Server instances
Definition: Cluster
1). A cluster is a logical group of WLS servers. 2). WebLogic clusters provide automatic:
Definition: Domain
1). A domain is a logically related group of WebLogic Server resources that you manage as a unit. 2). A domain provides one point of administration. 3). A WebLogic Server domain can logically separate:
Is transparent to applications Can be configured and administered, for technical or business reasons, even after applications are developed or in production
Development, test and production applications Administration and operational responsibilities Organizational or business divisions
Stores the configuration information and logs for a domain Runs the WebLogic administration console
contacts the admin server for configuration information runs business applications in a production environment
Command-line scripting interface for managing and monitoring WebLogic Server instances, clusters, and domains Based on 100% pure Java implementation of Python Modes of operation (script / interactive) (online / offline) Provides a repeatable process for propagating configuration changes across environments Quickly allows environments to be replicated and migrated
Java utility that runs as separate process from WebLogic Server Can be run automatically in the background, as a Windows service or a Unix daemon Runs on the same computers as the managed servers Lets you monitor managed servers regardless of its location with respect to its Administration Server Can be used to start and stop managed server (manage managed server) Can automatically restart a Managed Server after an unexpected failure Is optional Is Domain-Independent Cannot used to start or stop an Administration Server
Configure WebLogic Server services, such as database connectivity (JDBC) and messaging (JMS) Configure security parameters, including managing users, groups, and roles Configure and deploy your applications Monitor server and application performance View server and domain log files View application deployment descriptors Edit selected run-time application deployment descriptor elements Administration Console Online Help
High performance JVM optimized for Intel architectures Ensure reliability, scalability, manageability, and flexibility for Java applications Comes with Runtime Analyser which enables the developer to handle runtime issues. Has a memory leak detector which can be used during development as well as production time. Comes along with a Management Console. Works on either the Windows or Linux operating system Supports both 32-bit or 64-bit architectures Ease of Use because included with your WebLogic Server installation
Webserver Plug-ins:
Plug-ins are provided with your WebLogic Server installation that allow WebLogic Server to operate with different webservers.
Plug-ins provided for: Apache Web server Microsoft IIS Sun Web server
ConsoleApp Helps us to Start and Stop servers from a from admin console Only if the Servers are configured to run with Machines, because Every machine has a Nodemnager Associated with it. If a Server is not assigned a Machine/NodeManager then it cannot be started using the Administartion Console. AdminServer helps us to Migrate Servers and Services within the domain. AdminServer helps us to Deploy Applications within the domaintargeted to ManagedServers/Clusters or targeted to AdminServer itself. There must be exactly One Administration Server in domain. Usually we can deploy applications on AdminServer/ManagedServers/Clusters But for Production environments, it is Not recommend to hosting application logic or resources on the Administration Server.
What is NodeManager?
A Node Manager process is not associated with a specific WebLogic domain but with a machine. Node Manager process to control server instances in any WebLogic Server domain until the server instances reside on the same machine as the Node Manager process. Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements. A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process.
Types of NodeManagers?
1). Java Based Nodemanager: This can be used in Windiows as well as UNIX based Operating systems. Java Based Node Manager is not supported on Open VMS, OS/390, AS400, UnixWare, or Tru64 UNIX. 2). Script Based Nodemanager: This nodemanager can be used in UNIX based operating systems. The advantage of the script-based Node Manager is that it can remotely manage servers over a network that has been configured to use SSH. For More Information on NodeManager please refer to: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html And http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html