The following section describes the steps involved for editing a server configuration. The general settings include settings for MIME, log, WebDAV and monitoring.
In the HTTP protocol used by web browsers to communicate with web server, the file extension of the URL is not used to determine the type of information that the server will return. Indeed, there may be no file extension at all at the end of the URL. Instead, the web server specifies the correct MIME type using a Content-type: header when it responds to the web browsers HTTP request.
You can view the configured MIME mappings for a configuration by performing the following tasks:
Click Configurations tab
Identify the configuration by selecting the configuration checkbox.
Click MIME Types sub tab under General Settings tab.
The MIME Mappings page has a list of MIME headers and values for the selected configuration. To add a new MIME mapping, perform the following tasks:
Click Configurations tab
Identify the configuration by selecting the configuration checkbox.
Click MIME Types sub tab under General Settings tab.
Click New MIME Mappings button and configure the following properties:
MIME Header -- Select from Content-type, Content-encoding and Content-language.
MIME Value -- Enter the value for the MIME header. For example, For Content-type MIME header, the MIME value could be text/plain, text/html etc.
File Suffix -- File extension for the MIME value. For example, For text/html MIME value, the file extension could be htm/html.
Click Save button to save the new MIME mapping.
The server performs monitoring actions through SNMP. SNMP is a protocol used to exchange data about network activity. With SNMP, data travels between a managed device and a network management station (NMS). A managed device is anything that runs SNMP: hosts, routers, your web server, and other servers on your network. The NMS is a machine used to remotely manage that network. Usually, the NMS software will provide a graph to display collected data or use that data to make sure the server is operating within a particular tolerance.
The NMS is usually a powerful workstation with one or more network management applications installed. A network management application such as HP OpenView graphically shows information about managed devices, such as your web servers. For example, it might show which servers in your enterprise are up or down, or the number and type of error messages received. When you use SNMP with the Sun Java System Web Server, this information is transferred between the NMS and the server through the use of two types of agents, the subagent and the master agent.
The subagent gathers information about the server and passes the information to the server's master agent. Every Sun Java System Web Server, except for the Administration Server, has as subagent.
Note - After making any SNMP configuration changes, you must click the Save button, then restart SNMP subagent.
For changing monitoring settings for the configuration, perform the following tasks:
Click Configurations tab.
Select the configuration for which you need to change monitoring settings.
Click Monitoring Settings sub tab
For changing general monitoring settings for a configuration, edit the values under the General Settings section. The following table provides the field description of general monitoring parameters
Table 5 Field Description > General Monitoring Settings
For changing SNMP subagent settings for a configuration, edit the values under the SNMP Subagent Settings section. The following table provides the field description of SNMP Subagent parameters:
Table 6 Field Description > SNMP Subagent Settings
See Configuring WebDAV Properties
Instances can be re-configured or restarted based on scheduled events. You can set a specific time and interval for scheduling automatic instance reconfiguration.
For scheduling events, perform the following tasks:
Click Configuration tab and select the configuration.
Click General sub tab > Scheduled Events sub tab.
Scheduled Events page provide a list of already configured scheduled events. This page also provides option to create or remove scheduled events.
The following table provides a brief description of all fields in the Scheduled Events page.
Table 7 Field Description > Scheduled Events page
Field | Description |
Event | The scheduled event. For example, Restart Event /Reconfig. Event |
Time | The configured time when the events will start. |
Day | Day of the week when the event will start. From Sunday to Saturday. |
Day of Month | From 1 to 31 |
Month | From January to December |
Interval | Time interval/period after which the event restarts. |
For adding a new Scheduled Event, perform the following tasks:
Click Configuration tab and select the configuration.
Click General sub tab > Scheduled Events sub tab.
Click New button.
The following table provides a brief description of all fields in the New Event Schedule page.
Table 8 Field Description > New Event Schedule page
Field | Description |
Event |
|
Time | The configured time when the event will start. Select the hour and minutes value from the drop down box. Every Day -- Starts the event specified every day at the specified time. Specific Days -- Starts the event specified at specific days. 1. Days -- Specify any day from Sunday to Saturday. 2. Dates -- Specify any day of the month from 1 to 31 as comma separated entries. For example, 4,23,9 Specific Months -- Starts the event specified at the specific time and month. Specify month from January to December. |
Interval | Start the specified event after this time period. 1. Every Hours -- Select the number of hours from the drop down box. 2. Every Seconds -- Select the number of seconds from the drop down box. |
For deleting a configured Scheduled Event, perform the following tasks:
Click Configuration tab and select the configuration.
Click General sub tab > Scheduled Events sub tab.
Select the scheduled event and click Delete button.
From this section, you can restore the configuration that were deployed earlier.
Note - You can only restore the last seven configuration.
To Restore the Configuration
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 new popup window opens up.
Click the Deploy button
From this section, you can configure advanced properties of the server including HTTP and Localization settings.
For modifying the advanced properties of the configuration, perform the following tasks:
Click Configuration tab and select the configuration.
Click General sub tab > Advanced sub tab.
Modify the values for the parameters listed in the following table.
Table 9 Field Description > Advanced Properties
Field | Description |
|---|---|
Server User | Specify the user name for the Server process. Default is root. |
Platform | 32/64 bit. The platform mode in which the server will run. Refer to the Installation and Migration Guide for installing Server in 64 bit mode. |
Temporary Directory | Provide the path to the temporary directory for Server internal usage. Make sure that the Server User you have specified has access to write to this directory. |
HTTP Protocol Version | Highest HTTP protocol version the server supports. The default is HTTP/1.1. |
HTTP Server Header | Name of the server software and version. Default value is Sun-Java-System-Web-Server/7.0 |
Favorite Icon | Enabling this option results in Server replying to requests for favicon.ico with its own built-in icon file. Enabled/Disabled. |
Localization-Default Language | Default language for messages displayed to administrators and content served to clients. For instance, en-us. |
Localization-Negotiate Client Language | Indicates whether the server attempts to use the Accept-language HTTP header to negotiate the content language with clients. Disabled by default. |