This section describes the single node deployment architecture.
The following figure represents Web Server in a single node deployment set up.
In the preceding figure, the Web Server deployment set up comprises the following components:
Administration Server- Administration Server is a specially configured web server instance. You can deploy web applications on the administration server.
Administration Node- Administration Node is deployed on a node or a server/host within a server farm and has the ability to communicate with the remote Administration Server. The server configurations available within the Administration Server can be deployed to this node. All the Administration Nodes within the server farm need to be homogeneous. That is, all the nodes must use the same operating system and have the same hardware architecture.
Configuration- A configuration refers to a set of all configurable elements of a Web Server instance, such as web applications, configuration files, and search collection indexes. A configuration can be created, modified, or deleted. Web Server can manage multiple configurations. Instances can be created for a configuration. Deploying a modified configuration updates the instance of that configuration.
config-store This is the file system-based repository where all the configurations are stored.
Do not edit any file in the config-store directory. The files under this directory are created by Web Server for internal use.
If you must manually edit the configuration file in the config-store directory, deploy the configuration using the wadm deploy-config command.
For more information on using this command, see the Sun Java System Web Server 7.0 Update 4 CLI Reference Manual.
Instance - An instance refers to the environment of a web server on a given node, including its configuration, log files, and other runtime artifacts such as lock databases, caches, and temporary files. For management purposes, an instance can be started, stopped, restarted, or dynamically re-configured.