ページ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
ページ2に含まれる内容の要旨
Copyright 2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
ページ3に含まれる内容の要旨
Contents 1 Quick Start 5 Variable Names and Default Paths 5 About Application Server Administration 6 Starting the Server 7 Starting the Domain Administration Server 7 To Start the Domain on Solaris and Linux 7 To Start the Domain on Windows 8 Logging in to the Admin Console 9 To Log In to the Admin Console 9 Examining the Log File 11 To View the Domain Administration Server Log File 11 Creating a Cluster 12 To Start the Node Agent 12 To Create a Cluster 12 Deploying an Application 1
ページ4に含まれる内容の要旨
Starting Load Balancing 20 Verifying Load Balancing 20 To Verify Load Balancing 21 Cleaning Up 22 To Uninstall Completely 22 To Remove the Sample Cluster Only 23 Where to Go Next 24 2 Quick Start for Setting Up High Availability Failover 25 About High Availability Clusters and HADB 26 HADB Preinstallation Steps 26 To Configure Your System for HADB 27 Installing HADB 28 To Install HADB 28 Starting HADB 28 To Start HADB in a Java Enterprise System Installation on Solaris or Linux 29 T
ページ5に含まれる内容の要旨
CHAPTER 1 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. The basic steps, which usually require less than 45 minutes to complete, are in these sectio
ページ6に含まれる内容の要旨
Variable Name Description and Path install-dir By default, the Application Server installation directory is located here: Solaris Java Enterprise System installations: /opt/SUNWappserver/appserver Linux Java Enterprise System installations: /opt/sun/appserver/ Windows Java Enterprise System installations: SystemDrive:\Sun\ApplicationServer Solaris and Linux stand-alone Application Server installations, non-root user: user_home_directory/SUNWappserver Solaris and Linux stand-alone Appli
ページ7に含まれる内容の要旨
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. You work with the default domain in this guide. To complete most of the steps presented in this guide, you will use the
ページ8に含まれる内容の要旨
Set the value ofAS_ADMIN_USER to the admin user you specified when you installed the Application Server. For example, setenv AS_ADMIN_USER admin 3. Start the server by entering this command from the install-dir: asadmin start-domain domain1 When you are prompted for the admin password and the master password, enter the passwords that you provided during installation. 4. A message appears telling you that the Domain Administration Server is starting: Starting Domain domain1, please wait. Log redir
ページ9に含まれる内容の要旨
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... When the startup process has completed, you see an additional message: Domain domain1 started. Press any key to continue ... 10. Press a key to close the message window. Logg
ページ10に含まれる内容の要旨
Note – If a popup window appears with a message such asWebsiteCertified by an Unknown Authority, click OK. This message appears because your browser does not recognize the self-signed certificate that the Domain Administration Server uses to service the Admin Console over the secure transmission protocol. 2. When the log in window appears, enter the admin user name and password. 3. Click Log In. When the Admin Console appears, it looks like this: In the left pane, select what you want to manage f
ページ11に含まれる内容の要旨
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. 2. In the Log Viewer window, select “server” from the Instance Name drop–down list and click Search. The Domain Admi
ページ12に含まれる内容の要旨
Next Steps In this section you started the Domain Administration Server and confirmed that it is running. You also logged in to the Admin Console and used the Log Viewer. You can stop the Quick Start trail here if you do not wish to continue, or you can go on to the next section. Creating a Cluster This section, the second of three basic topics, explains how to create a cluster that contains two Application Server instances. For simplicity, the cluster runs completely within one machine. This top
ページ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. Before You You must have already started the node agent process on each machine, as described Begin in previous section. When you specify instances during cluster creation, you must associate the instance with a running node agent for the machine on which you want
ページ14に含まれる内容の要旨
7. Click OK. The create process can take a few minutes. Note – This exercise requires automatically assigned port numbers for HTTP, HTTPS, IIOP and IIOPS. You can change them later, if desired. When the create process is completed, the Cluster Created Successfully page appears, andFirstCluster appears in the tree in the left pane. A copy of the configuration templatedefault-config was made for this cluster, and the name FirstCluster-config was assigned to it. 8. In the left pane, expand Clusters
ページ15に含まれる内容の要旨
Note – By default, the HTTP ports are 38081 for i1 and 38080 for i2. If these ports 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. Next Steps In this section you have created a simple cluster on a single machine. You can also create clusters spanning multiple machines using the same basic steps (as long as you have the software installed and a node agent running on each m
ページ16に含まれる内容の要旨
7. Click OK. The clusterjsp application is now deployed to FirstCluster. To Start the Cluster Steps 1. In the tree on the left pane, click the FirstCluster node under Clusters. 2. In the right pane, click the General tab if it is not already active. 3. Click the Start Instances button to start the cluster. 4. Verify that it has started by checking that the Status field, which indicates what instances are running. To Verify the Application Deployment This procedure verifies that the application
ページ17に含まれる内容の要旨
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 ofHTTP-LISTENER-PORT for i1. This example useshttp://localhost:38081/clusterjsp. 2. Add some session attribute data. 3. Examine the Session and Host information displayed. For example: Executed From Server: localhost Server Port Number: 38081 Executed Server IP Address: 198.19.255.255 Session Created: Day Mon 05 1
ページ18に含まれる内容の要旨
This topic presents the following steps: “Installing Web Server Software” on page 18 “Installing the Load Balancer Plug-in” on page 19 “Creating a Load Balancer Configuration” on page 19 “Starting Load Balancing” on page 20 “Verifying Load Balancing” on page 20 Installing Web Server Software If you already have Web Server software installed, and if you can identify a Web Server instance to serve as the load balancer, note the location of this instance in the file system and skip to “Inst
ページ19に含まれる内容の要旨
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. 3. Follow the instructions to install Web Server software. You must: a. Extract the software from the compressed archive. b. Run the setup program. If you need additional information, see the Web Server inst
ページ20に含まれる内容の要旨
To Create an HTTP Load Balancer Configuration Steps 1. Create a load balancer configuration calledMyLbConfig targeted to the cluster FirstCluster: asadmin create-http-lb-config --target FirstCluster MyLbConfig 2. Enable the FirstCluster cluster and the clusterjsp application deployed in it for HTTP load balancing: asadmin enable-http-lb-server FirstCluster asadmin enable-http-lb-application --name clusterjsp FirstCluster 3. Create a health checker for the load balancer, which signals when an ins
