Siebel Installation Guide for Microsoft Windows > Installing and Configuring the Siebel Web Server Extension > Postinstallation Tasks for the SWSE and the Web Server >

Updating Web Server Static Files on SWSE Using the Siebel Enterprise Security Token

This topic is part of Postinstallation Tasks for the SWSE and the Web Server.

The Siebel Enterprise Security Token is the password your Siebel administrator uses to refresh static files, such as application image files or cascading style sheet files, on your Web server. Your developers may have placed updated versions of these files on the Siebel Server (in the webmaster subdirectory) after customizing the Siebel application with Siebel Tools.

The Web server contacts the Siebel Server, refreshing these static files each time the administrator restarts the Web server. However, administrators can refresh the static files by entering this token in a command line, particularly when deploying multiple Web servers.

You set the value of the Siebel Enterprise Security Token during configuration of the SWSE logical profile, as described in Creating the SWSE Logical Profile. This value is defined as the value for the SiebEntSecToken parameter in the eapps.cfg file for your SWSE installation. By default, this value is encrypted.

NOTE:  If passwords are encrypted in eapps.cfg, to change the value, you must either reconfigure the SWSE and specify the new password in the SWSE Configuration Wizard, or use the encryptstring utility to encrypt the password before you add it manually to the eapps.cfg file. Directly editing passwords in the eapps.cfg file is suitable only when encryption is not used.

For more information about managing encrypted passwords in the eapps.cfg file, see Siebel Security Guide.

It is not necessary to restart the Web server every time the Web server static files in the SWSE directory must be refreshed. Instead, you can use the Siebel Enterprise Security Token you specified when you configured the SWSE, as described below.

For each language-specific application, the directory on the SWSE where the static files are cached is determined by the setting of the WebPublicRootDir parameter in the eapps.cfg file.

NOTE:  The Siebel Enterprise Security Token was formerly known as the Web Update Protection Key, and the corresponding parameter name (now SiebEntSecToken) was formerly WebUpdatePassword.

To refresh the static files on the Web server

  1. Start a Web browser session.
  2. Type the following URL into the browser:



    • host = The name of the Web server machine.
    • port = The Web server listen port (not required if using the default port, 80).
    • application = Any Siebel application hosted by this Web server (such as callcenter_enu, sales_deu, and so on).
    • EnterpriseSecurityToken = The unencrypted version of the Siebel Enterprise Security Token, which is defined in the eapps.cfg file by the SiebEntSecToken parameter.

      For example:


Siebel Installation Guide for Microsoft Windows Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.