一般資訊

The GlassFish Server creates one application server instance, called server at the time of installation. You can delete the server instance and create a new instance with a different name if you prefer.

Each GlassFish Server instance has its own Java configuration, Java resources, application deployment areas, and server configuration settings. Changes to one application server instance have no effect on other application server instances. You can have one application server instance within one administrative domain.

For many users, one application server instance meets their needs. However, depending upon your environment, you might want to create one or more additional application server instances. For example, in a development environment you can use different application server instances to test different GlassFish Server configurations, or to compare and test different application deployments. Because you can easily add or delete an application server instance, you can use them to create temporary "sandbox" areas to experiment with while developing.

In addition, for each application server instance you can also create virtual servers. Within a single installed application server instance you can offer companies or individuals domain names, IP Addresses, and some administration capabilities. For the users, it is almost as if they have their own web server, without the hardware and basic server maintenance. These virtual servers do not span application server instances. For more information about virtual servers, see JVM 一般設定.

In operational deployments, for many purposes you can use virtual servers instead of multiple application server instances. However, if virtual servers do not meet your needs, you can also use multiple application server instances.

An GlassFish Server instance is not started automatically. Once you start an instance, the instance runs until you stop it. When you stop an application server instance, it stops accepting new connections, then waits for all outstanding connections to complete. If your machine crashes or is taken offline, the server quits and any requests it was servicing may be lost.

使用 「一般資訊」 頁面可驗證 GlassFish Server 設定以及檢視 Java 虛擬機器資料。

「一般資訊」 頁面包含以下資訊。

停止按鈕

按一下 「停止」 按鈕以停止 GlassFish Server。

重新啟動按鈕

按一下 「重新啟動」 按鈕以重新啟動 GlassFish Server。

檢視記錄檔按鈕

按一下「檢視記錄檔」按鈕,可檢視 GlassFish Server 實例或叢集的記錄檔。

檢視原始記錄按鈕

按一下「檢視記錄檔」按鈕,可檢視管理伺服器 (名為伺服器) 的原始記錄檔。

安全管理按鈕

安全管理頁面上按一下「安全管理」按鈕,可啟用或停用安全管理。

名稱

伺服器的名稱 current 。

狀態

伺服器實例的目前狀態。伺服器可以是已停止、已啟動或執行中。

正常執行時間

伺服器實例已連續執行的小時與分鐘數。這是唯讀欄位。

HTTP Load Balancer

The name of the load balancer, if it is enabled for the server instance.

JVM

如果按一下 「JVM 報告」,會開啟另外一個視窗並顯示 Java 虛擬機器的相關報告,包括摘要報告、記憶體管理和資源回收報告、類別載入報告以及目前執行緒傾印。

組態目錄

主機電腦上包含組態檔案 (如 domain.xml) 的目錄。

安裝的版本

產品版本識別碼。

安全管理

安全管理的目前狀態。可能的值為「已啟用」與「未啟用」。

除錯

確定是否已啟用除錯功能。若已啟用除錯功能,則會同時顯示連接埠號碼。

HTTP 連接埠

目前組態用於 HTTP 請求與回應的連接埠。

IIOP 連接埠

目前組態用於 IIOP 請求與回應的連接埠。

相關作業
Copyright © 2005, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices