#### To edit a virtual server

1. Expand the Configuration node and the HTTP Service node.
2. Expand the HTTP Service and Virtual Servers node.
3. Select the Virtual Server to be edited.
4. Define the Virtual Server settings as follows:

   - ID: This value identifies the virtual server internally. It is not exposed to HTTP clients. The host names that are exposed to HTTP clients must be specified in the Hosts field.

   - Hosts: Enter the host name or names for the machine on which the server is running. Use either actual or virtual host names that are registered with the DNS server for your network (and, on a UNIX system, in your `/etc/hosts` file).

   - State: Select the desired state for the virtual server. The default is On.

   - HTTP Listeners: Leave this field empty. It is filled in automatically when you create an HTTP listener and associate it with this server.

     Use of this field requires that you specify an existing HTTP listener. You must not, however, specify a listener that is used by another virtual server; if you do, an error appears in the server log when you restart the server. Since a listener must be associated with an existing virtual server when it is created, all existing listeners are used by another virtual server.

   - Default Web Module: Choose the deployed web module (if any) that is to respond to all requests that cannot be mapped to other web modules deployed to the virtual server. If a Default Web Module is not specified, the web module that has an empty context root is used. If there is no web module with an empty context root, a system default web module is created and used.

   - Log File: Enter the path name of the file where logging messages from this virtual server will appear. Leave this field empty to send logging messages to the default server log, domain-dir`/logs/server.log`.

   - docroot: the absolute path to the root document directory for the server. Default is domain-dir`/docroot.`

   - SSO: If the Enabled checkbox is not selected, then single sign-on is disabled for this virtual server, and users must authenticate separately to every application on the virtual server. The default is disabled.

     Single sign-on across applications is supported by servlets and JSP pages. This feature allows multiple applications that require the same user sign-on information to share this information, rather than have the user sign on separately for each application.

   - Specify the Access Log settings.

     - Access Logging: Use these options to enable or disable access logging. Alternatively, you can also specify if access logging is inherited from the HTTP Service.

     - Directory: Provide the absolute path to the server access logs. The default is domain-dir`/logs/access`

     - Buffer Size: Specify the buffer size. A value less than or equal to zero will disable buffering. If the field is left empty, the access log buffer size will be inherited from the HTTP Service.

     - Write Interval: Specify the interval between updating the access logs.

5. In the Additional Properties area, click Add Property to add a property for the virtual server.

   Whether you specify properties or not, the server has the default properties `docroot` and `accesslog`, set to default values.

   The following table lists the available virtual server properties.

   Property Name | Description
   --- | ---
   `sso-max-inactive-seconds` | Specifies the number of seconds after which a user’s single sign-on record becomes eligible for purging if no client activity is received. Since single sign-on applies across several applications on the same virtual server, access to any of the applications keeps the single sign-on record active. Default is 300 seconds (5 minutes). Higher values provide longer single sign-on persistence for users at the expense of more memory use on the server.
   `sso-reap-interval-seconds` | Specifies the number of seconds between purges of expired single sign-on records. Default is 60.
   `allowLinking` | If `true`, resources that are symbolic links will be served for all web applications deployed on this virtual server. Individual web applications may override this setting by using the `sun-web-app` property `allowLinking` in the `sun-web.xml` file:
       <sun-web-app>
          <property name="allowLinking"
             value="{true|false}"/>
       </sun-web-app>
   Default is `false`.

6. Click Save to save the changes.

###### See Also

- To create a Virtual Server

- To delete a Virtual Server