How to Force the Secure Global Desktop Gateway to Reload Proxy Configuration Without Restarting (Doc ID 1444858.1)

Last updated on MAY 21, 2014

Applies to:

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

Goal

In a production environment, it may be necessary to force the Secure Global Desktop (SGD) Gateway server to reload its configuration files without dropping active connections.  

This document describes the procedure to do so, when a formal restart of Gateway services is not possible without a planned maintenance window. 

Example:  The administrator has disabled the /balance-manager, and needs to start the functionality so that they can modify the load balance sets.

Note: Not all configuration changes to the SGD GW may be reloaded in this manner.  Changes to Java, or diagnostic logging, will require a more formal restart of services, and should be scheduled during a planned maintenance window.  

Solution

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