Customized Web Content is not Visible after Upgrade to Secure Global Desktop, Version 5.2 (Doc ID 2030287.1)

Last updated on JULY 15, 2015

Applies to:

Oracle Secure Global Desktop - Version 5.2 to 5.2 [Release 5.0]
Information in this document applies to any platform.

Symptoms

Administrators of older Secure Global Desktop (SGD) deployments will find the procedures to customize--or maintain previously customized--web pages in legacy deployments has changed with SGD 5.2.

Historically, updating or adding content within the htdocs directory of SGD's active Apache instance was sufficient to present that content to users.   After upgrading to 5.2, this procedure will no longer work as expected.

For example:

  1. A customer deployment maintains a customized 'Welcome' page for SGD, index_en.html .

  2. After upgrading an existing system from SGD 5.1 to 5.2, the SGD administrator identifies the latest active htdocs directory, per legacy procedure:  
  3. The SGD Administrator archives the default file, then copies the updated index_en.html into this htdocs directory, taking care to verify correct file ownership and permission.

  4. The updated page is not seen as expected by connecting clients -- even after restart of SGD Webservices.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms