Related Manuals for Sun Microsystems 2005Q2
Summary of Contents for Sun Microsystems 2005Q2
- Page 1 Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 819–2553...
- Page 2 Sun, Sun Microsystems, le logo Sun, docs.sun.com, AnswerBook, AnswerBook2, et Solaris sont des marques de fabrique ou des marques déposées, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc.
-
Page 3: Table Of Contents
Contents Quick Start Variable Names and Default Paths About Application Server Administration Starting the Server Starting the Domain Administration Server M To Start the Domain on Solaris and Linux M To Start the Domain on Windows Logging in to the Admin Console M To Log In to the Admin Console Examining the Log File M To View the Domain Administration Server Log File... - Page 4 M To Restart the Cluster Verifying HTTP Session Failover M To Verify HTTP Session Failover Cleaning Up M To Uninstall Completely M To Remove the Sample Cluster Where to Go Next Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide...
-
Page 5: Quick Start
CHAPTER Quick Start Welcome to the Quick Start Guide. This guide is for developers, system administrators, and Application Server administrators who are interested in learning about the capabilities of the Sun Java System Application Server 8.1 2005Q2 software. This guide describes basic and advanced steps for using Application Server. The steps are presented in the order that you should complete them. -
Page 6: About Application Server Administration
Application Server instance that intermediates in all administrative tasks. The Domain Administration Server (DAS) provides a single secure interface for validating and executing administrative commands regardless of which interface is used. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 7: Starting The Server
A domain is a collection of configuration data, deployed applications, and machines with a designated administrator. The domain definition describes and can control the operation of several applications, stand-alone application server instances, and clusters, potentially spread over multiple machines. When the DAS is installed, a default domain called domain1 is always installed. -
Page 8: M To Start The Domain On Windows 8
Programs ⇒ Sun Microsystems ⇒ Application Server⇒ Start Admin Server. For stand-alone installations, from the Start menu, choose Programs ⇒ Sun Microsystems ⇒ Application Server EE ⇒ Start Admin Server. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 9: Logging In To The Admin Console
9. When a command prompt window opens to prompt you for the admin password and the master password, enter the passwords that you provided during installation. A window appears with a message telling that you the server is starting: Starting Domain domain1, please wait. Log redirected to domain_dir\domain1\logs\server.log... - Page 10 “Common Tasks” heading. Click the Registration tab to register your software if you have not already Tip – done so. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide...
-
Page 11: Examining The Log File
Examining the Log File Application Server instances and the Domain Administration Server produce annotated logs on the file system. By default, all errors, warnings or useful informative messages are logged. To View the Domain Administration Server Log File Steps 1. From the Common Tasks list in the right pane, click Search Log Files to launch a new browser window for Log Viewer. -
Page 12: Creating A Cluster
A cluster is a group of server instances (typically on multiple hosts) that share the same configurations, resources, and applications. A cluster facilitates load balancing across server instances and high availability through failover. You can create clusters Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... - Page 13 spanning multiple machines and manage them with the help of the node agent process on each machine. In this guide, for simplicity, our sample cluster will be on one host, the same one where the Domain Administration Server is running. You must have already started the node agent process on each machine, as described Before You Begin...
- Page 14 Click i1 to examine this instance. b. From the tabs above the General Information heading of the right pane, click Properties and see the value for HTTP_LISTENER_PORT. c. Repeat these steps for i2. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide...
-
Page 15: Deploying An Application
By default, the HTTP ports are 38081 for i1 and 38080 for i2. If these ports Note – were busy on your machine when you created these clusters, or if you had already assigned these ports to other instances and clusters, different port numbers were assigned. -
Page 16: M To Start The Cluster
To Verify the Application Deployment This procedure verifies that the application was deployed properly and is accessible on each instance in the cluster. 1. Type the following URL in your browser: Steps Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 17: Setting Up Load Balancing
http://localhost:port/clusterjsp Replace the localhost variable with the name of the system that the Domain Admin Server is running on. Replace the port variable with the value of HTTP-LISTENER-PORT for i1. This example uses http://localhost:38081/clusterjsp. 2. Add some session attribute data. 3. -
Page 18: Installing Web Server Software
Sun Java Enterprise System installer, install Web Server software using these steps: 1. Go to http://www.sun.com/downloads. Scroll down to the Web & Proxy Steps Servers heading and click Web Servers. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 19: Installing The Load Balancer Plug-In
2. Download Web Server 6.1 Service Pack 2 or higher for the locale and platform of your choice. To download, you must log in with username and password registered with MySunSM, Sun StoreSM, SunSolveSM, or the Online Support Center. If you do not have a login account, you can register online. -
Page 20: M To Create An Http Load Balancer Configuration
Verifying Load Balancing Once the application is deployed and the load balancer is running, verify that the load balancing is working. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 21: M To Verify Load Balancing
To Verify Load Balancing 1. To display the first page of the clusterjsp application, type this URL in your Steps browser: http://localhost:web_server_port/clusterjsp Replace the localhost variable with the name of the system that the Web Server is running on. Replace the web_server_port variable with the value of the port attribute of the LS element in web_server_install_dir/https-hostname/config/server.xml. -
Page 22: Cleaning Up
To completely uninstall Application Server and also uninstall the Web Server, use the following procedure. 1. Stop the Application Server processes using these commands: Steps asadmin stop-cluster FirstCluster asadmin stop-node-agent hostname asadmin stop-domain domain1 Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 23: M To Remove The Sample Cluster Only
In a Windows stand-alone installation, from the Start menu, choose Programs ⇒ Sun Microsystems ⇒ Application Server EE ⇒ Uninstall. 3. If you installed Web Server for this exercise, stop the web server instance acting as load balancer and uninstall the Web Server product. -
Page 24: Where To Go Next
Java BluePrints (http://java.sun.com/blueprints) guidelines for the Enterprise See this document for a comprehensive set of examples that demonstrate operations of the Application Server software and that can be used as application templates. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 25: Quick Start For Setting Up High Availability Failover
CHAPTER Quick Start for Setting Up High Availability Failover With the configuration used in the previous chapter, if a server instance goes down, users lose session state. This section, the second of two advanced topics, provides the steps for installing the high-availability database (HADB), creating a highly available cluster, and testing HTTP session persistence. -
Page 26: About High Availability Clusters And Hadb
The recommended system configuration values in this section are sufficient for running up to six HADB nodes and do not take into consideration other applications on the system that also use shared memory. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 27: M To Configure Your System For Hadb
To Configure Your System for HADB 1. Get root access. Steps 2. Define variables related to shared memory and semaphores. On Solaris: a. Add these lines to the /etc/system file (or if these lines are in the file as comments, uncomment them and make sure that the values match these): set shmsys:shminfo_shmmax=0x80000000 set shmsys:shminfo_shmseg=36 set semsys:seminfo_semmnu=600... -
Page 28: Installing Hadb
For more information, see “Starting the HADB Management Agent” in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 29: M To Start Hadb In A Java Enterprise System Installation On Solaris Or Linux
If starting a database with HADB nodes on several hosts, start the management agent on each host. To Start HADB in a Java Enterprise System Installation on Solaris or Linux 1. Change to the /etc/init.d directory: Steps cd /etc/init.d 2. Run the command to start the agent: ./ma-initd start To Start HADB in a Java Enterprise System Installation on Windows... -
Page 30: M To Start Hadb In A Stand-Alone Installation On Windows
HADB is to run. If you are using just one machine, you must name it twice. This simplified example runs two nodes of HADB on the same machine. In production settings, use more than one machine. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 31: Restarting The Cluster
To reduce the memory footprint of HADB for demonstration purposes, Note – execute the following hadbm command. You are prompted for the administration password. In Java Enterprise System installations: /opt/SUNWhadb/4/bin/hadbm set DataBufferPoolSize=64,LogBufferSize=25 FirstCluster In standalone Application Server installations: install_dir/hadb/4/bin/hadbm set DataBufferPoolSize=64,LogBufferSize=25 FirstCluster 2. -
Page 32: Verifying Http Session Failover
3. View the server access log files to determine which application server instance is serving the application. The log files are located here: Solaris Java Enterprise System installation: /var/opt/SUNWappserver/nodeagents/nodeagent_name/i1/logs/ access/server_access_log /var/opt/SUNWappserver/nodeagents/nodeagent_name/i2/logs/ access/server_access_log Linux Java Enterprise System installation: /var/opt/sun/appserver/nodeagents/nodeagent_name/i1/logs/ access/server_access_log Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 33: Cleaning Up
/var/opt/sun/appserver/nodeagents/nodeagent_name/i2/logs/ access/server_access_log Windows Java Enterprise System installation: install-dir\nodeagents\nodeagent_name\i1\logs\access\server_access_log install-dir\nodeagents\nodeagent_name\i2\logs\access\ server_access_log Standalone Application Server installations: install-dir/nodeagents/nodeagent_name/i1/logs/access/server_access_log install-dir/nodeagents/nodeagent_name/i2/logs/access/ server_access_log 4. Stop the Application Server instance that is serving the page. a. In the Admin Console, in the left pane, expand Clusters. b. Click FirstCluster. c. -
Page 34: M To Uninstall Completely
The x represents the release number of HADB. b. Run the command to stop the agent: ma -r At this point all processes related to Sun Java System Application Server are stopped. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide... -
Page 35: M To Remove The Sample Cluster
In a Windows standalone Application Server instance, from the Start menu, choose Programs ⇒ Sun Microsystems ⇒ Application Server EE ⇒ Uninstall. 4. If you created a new Web Server instance for this exercise, delete it: a. - Page 36 You have also cleaned up so that your system is ready for other work. See “Where to Go Next” on page 37 additional information on Application Server. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide...
-
Page 37: Where To Go Next
Where to Go Next Other resources for learning about and using Application Server are available. They include: Product details at install-dir/docs-ee/about.html. See this document for the latest information on what is new, and pointers to tutorials and other educational services. Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Release Notes See this document for late-breaking information regarding this release. - Page 38 Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide...