一般信息

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 实例或集群的日志文件。

“查看原始日志”按钮

单击“查看原始日志”按钮可查看管理服务器 (名为 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