Managing Configurations

• Creating a Configuration

• Duplicating a Server Configuration

• Deploying the Server Configuration

• Deleting the Server Configuration

• Pulling Configuration Changes to the Administration Server

• Removing the Administration Node from the Server

Creating a Configuration

In order to start using the web server, you need to create a Configuration.

To create a new Configuration, perform the following tasks:

1. Click the Configuration tab. .

2. Click the New 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:

Step 1 – Set Configuration Information

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.

Step 2 — Create a Listener for the Configuration

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.

Step 3 — Configure Java, CGI and SHTML

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.

  ---

  Note –

  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.

Restore Configuration

The following steps enable you to restore a configuration that was previously deployed.

You can only restore the last seven configurations.

To Restore the Configuration

1. Click the Configuration tab.

2. Click the General sub tab > Restore sub tab.

   Select the configuration from the configuration backups list.

3. Click the Restore button.

4. Click the Deployment Pending Link on the top right of the Administration Console page to deploy the restored configuration.

   A pop-up windowappears.

5. Click the Deploy button.

Step 4 — Create an Instance

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).

Duplicating a Server Configuration

You can copy a server configuration and create a new configuration. The newly copied configuration is identical to the existing configuration. However, the new configuration will not have any instance even though the configuration from which it has been copied has instances.

To duplicate a configuration, perform the following tasks:

1. Click the Configuration tab..

2. Select the configuration from the list.

3. Click the Duplicate button..

4. In the pop-up window, enter the new configuration name and click OK.

Using CLI

To perform the action through CLI, execute the following command:

wadm> copy-config --user=admin --password-file=admin.pwd --host=serverhost 
--port=8989 --config=config1 copyconfig1

copyconfig1 is the name of the new configuration.

See CLI Reference, copy-config(1).

Deploying the Server Configuration

You need to create a configuration first to deploy on the node.

To deploy an existing configuration, perform the following tasks:

1. Click the Configurations tab.

2. Identify the configuration by selecting the configuration checkbox.

3. Click the Deploy button .

4. A new window appears, click the Deploy button to deploy the configuration.

Deleting the Server Configuration

You cannot delete a configuration if instances of the configuration are deployed to nodes. Even if the instances are deployed and not running, you cannot delete the server configuration. Stop the running instances and undeploy them to delete the configuration.

For deleting a configuration, perform the following tasks:

1. Click the Configurations tab.

2. Identify the configuration by selecting the configuration checkbox.

3. Click the Delete button.

4. A new window appears, click the OK button to delete the configuration.

Pulling Configuration Changes to the Administration Server

Whenever you make manual changes to the configuration, you should replicate the changes back into the Administration server repository as follows:

1. Manually edit the server instance's configuration files as you would do with the earlier version of Web Server (Not recommended).

2. Start the Administration Server.

3. To pull the changes back to the Administration Server repository, execute the following command.

   wadm> pull-config --user=admin --config=CONFIG_NAME

The operation may take some time depending on the configuration.

Always use the Administration Console or the wadm CLI to edit the settings. When you invoke pull-config only the contents of the <instance-dir>/config directory will be pulled into the configuration store from Web Server .

Removing the Administration Node from the Server

To Remove the Administration Node from the Server

1. Click the Nodes tab from the Common Tasks page.

2. Select the Administration Node.

   Select the Administration Node from the list

3. Click the Remove button.