In SAS Customer Intelligence Studio, you typically can sign off from user sessions by selecting Administration ► User Sessions ► user-session(s)  ► Log Off (where user-session(s) is one or more sessions from which you want to log off).  

Note that you can log off from user sessions only where the Pending Processes column shows 0, as illustrated below.

However, you might not be able to log off from user sessions under the following circumstances:

• if SAS^® Customer Intelligence is configured to use the Secure Sockets Layer (SSL)
• if SAS Customer Intelligence is deployed on a clustered middle tier, either in a vertical cluster (multiple application-server instances are hosted on the same physical machine) or in a horizontal cluster (the application is deployed on multiple physical machines)

The following steps explain how to enable log-off capability when you use SSL and when you use the middle tier.

When You Use SSL

To enable log-off capability when you use SSL:

1. Open the following file (specific to your operating environment) to modify the start-up arguments for the SAS^® Web Application Server:
   • In UNIX or Linux operating environments, open the setenv.sh file that is located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.
   • In Microsoft Windows operating environments, open the wrapper.conf file that is located in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory.
2. Add the following three java.additional parameters to the file:
   • -Dsas.ci.cluster.protocol=https
   • -Dsas.ci.cluster.hostname=load-balancer-hostname
   • -Dsas.auto.publish.port=8943

   Note: If the environment is not configured to use the default port, use the HTTPS port number.

   The HTTPS port number can be found in the SASServer6 catalina.properties file that resides in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\Conf directory.

   Under UNIX, the port number is the value for the bio.https.port property. Under Windows, the port number is the value for the nio.https.port property. This file is the most likely place to find the value.

When You Use a Clustered Middle Tier

To enable log-off capability when you use a clustered middle tier: 

1. If you use multiple SAS^® Web Servers in addition to an upper-level load balancer (either an external load balancer or a SAS Web Server that is used as load balancer), set the Dsas.ci.cluster.hostname and Dsas.auto.publish.port values to the SAS Web Server node rather than the top-level load balancer. To do that, open the following file (specific to your operating environment) to modify the start-up arguments for the SAS Web Application Server:
   • In UNIX or Linux operating environments, open the setenv.sh file that is located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.
   • In Microsoft Windows operating environments, open the wrapper.conf file that is located in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory.
2. Add the following three java.additional parameters to the file:
   • -Dsas.ci.cluster.protocol=https
   • -Dsas.ci.cluster.hostname=SAS-Web-Server-host-name
   • -Dsas.auto.publish.port=SAS-Web-Server-port-number

   Consider the following examples:

3. If you have middle-tier node 1, the SAS Web Server host name mid01.sas.com, and listening port 8943, the parameters should look like the following :
   -Dsas.ci.cluster.protocol=https
   -Dsas.ci.cluster.hostname=mid01.sas.com
   -Dsas.auto.publish.port=8943 /* In this example, the port for the web-server cluster */
                                /* node is 8943 rather than 443.                        */
4. If you have middle-tier node 2, the SAS Web Server host name mid02.sas.com, and listening port 8943, the parameters should look like this:
   -dsas.ci.cluster.protocol=https
   -Dsas.ci.cluster.hostname=mid02.sas.com
   -Dsas.auto.publish.port=8943 /* In this example, the port for the web-server cluster */
                                /* node is 8943 rather than 443.                        */

After changing the setenv.sh or wrapper.conf file a restart of the Web Server is necessary.

Operating System and Release Information