In order to start using the web server, you need to create a Configuration.
To create a new Configuration, perform the following tasks:
Click theConfiguration tab. .
Click theNew button.
The wizard guides you through the settings available for creating a Configuration. The following sections provide a description of the fields available in wizard pages:
This wizard page enables you to set the generic information for the new configuration
Set the following parameters in the wizard page:
Configuration Name — Add a new unique name for your configuration.
Server Name — Add a server name for the new configuration. It can be same as the configuration name.
Document Root — Enter a valid document root, wherein all the deployed web applications maintain their directories. The default value is ../docs You can enter the path of any valid directory on the server
64 Bit — Enable/Disable 64–bit support for the web server. The default is disable.
Server User — If the server is running on a UNIX-based system, provide a valid user name for the server process. For example, root.
This wizard page enables you to set the HTTP listener properties for the new Configuration
Set the following parameters in the wizard page:
Port — the Port number where the configuration binds to and listens for requests.
IP Address — the IP address of the host machine. Type * for setting all available IP addresses.
This wizard page enables you to configure properties related to Java/CGI and SHTML.
Set the following parameters in the wizard page:
Java — Enabled. By default Java is enabled.Warning: Do not disable Java if you need to deploy Java-based web applications using this configuration. Set the home for the Java SE directory. The default value is the directory pointing to the bundled Java SE directory. You can select either the default Java SE directory or specify a new path.
When the Web Server instance is not serving any Java web applications, you can disable Java using the disable-java CLI command or through the administration console. For example, FastCGI and reverse proxy plug-in are non-Java applications. Disabling Java will reduce the memory usage of the Web Server instance. By default, the instance is Java enabled.
For more information on disabling Java, see the CLI reference disable-java(1) and enable-java(1).
CGI — None (Disables CGI support), Enable as File Type (Enables CGI support) and Directory (Specify the URI and path where the CGI documents will be stored).
SHTML — By default SHTML is disabled.
The following steps enable you to restore a configuration that was previously deployed.
You can only restore the last seven configurations.
Click the Configuration tab.
Click the General sub tab > Restore sub tab.
Select the configuration from the configuration backups list.
Click the Restore button.
Click the Deployment Pending Link on the top right of the Administration Console page to deploy the restored configuration.
A pop-up windowappears.
Click the Deploy button.
This wizard page enables you to create an instance for the new Configuration.
Set the following parameters in the wizard page:
Configuration — Name of the new Configuration.
Select Nodes — Select the nodes for creating an instance of the new configuration. Select nodes from the available list and click the Add or Add All button to add the nodes.
Using CLI
To create a configuration through CLI, execute the following command:
wadm> create-config --doc-root=[DOCROOT] --jdk-home=[JAVAHOME] --server-user=[SERVERUSER] [--document-root=serverdocroot] [--platform=32|64] --http-port=port --server-name=servername CONFIGNAME |
config1 is the name of the new configuration.
See CLI Reference, create-config(1).