Essbase components; for example, MaxL, can control SSL at session level by connecting to Essbase Agent using secure as the transport keyword. For example, you can establish a secure connection between MaxL and Essbase Agent by executing one of the following commands from a MaxL Console:
login admin welcome1 on hostA:PORT:secure
login admin welcome1 on hostA:secure
Per-session control takes priority over configuration settings specified in essbase.cfg. If no transport keyword is specified, Essbase clients use the value set for ClientPreferredMode to determine whether to initiate a secure connection with Oracle Essbase. If ClientPreferredMode setting is not set to secure, the communication always occurs over a nonsecure channel.