SAS Enterprise Miner and SAS Forecast Server require post-installation steps in order to work in a vertically clustered middle tier environment.

Vertical clustering is the practice of deploying multiple identically configured web application server instances on a single machine. After adding a vertical cluster member in your middle tier environment, you need to update some configuration properties.

In a vertical cluster of SAS^® Web Application Server instances where the SASWIPServices web application is deployed, the following JVM parameters need to be unique:

• sas.auto.publish.host
• sas.auto.publish.port
• sas.auto.publish.protocol

These JVM parameters are configured in setenv.sh (on UNIX) or setenv.bat (on Windows) under SASConfig/Lev#/Web/WebAppServer/bin.

When you add a vertical cluster member, the value of the sas.auto.publish.host property is set to the host name. Since the web application server instances in a vertical cluster are not on different hosts, the value for sas.auto.publish.host is the same for all of the cluster members. In this case, you need to set the -Dsas.auto.publish.host value for each server to a different host name. One way to achieve this setting is to create a DNS alias, and update the sas.auto.publish.host to use the alias.

Follow these steps to create this alias.

1. Stop middle tier services on all middle tier nodes.

2. If you have a hybrid cluster with a mix of horizontal and vertical clusters, then edit the "setenv" script on each middle tier node. Edit for all vertical cluster members where SASWIPServices is deployed. By default, SASWIPServices is deployed to SASServer1_X. You need to modify the -Dsas.auto.publish.host values for the vertical cluster members of SASServer1 cluster.

   Example: you have a mix of horizontal and vertical clusters for SASServer1, with the following server instances:

   • Middle tier node1 (mid1) has SASServer1_1 and SASServer1_2
   • Middle tier node2 (mid2) has SASServer1_1 and SASServer1_2

   Update setenv.sh on mid1 and mid2

   mid1
   • SASServer1_1 -Dsas.auto.publish.host=mid1hostname
   • SASServer1_2 change this -Dsas.auto.publish.host=DNS Alias of mid1
   mid2
   • SASServer1_1 -Dsas.auto.publish.host=mid2hostname
   • SASServer1_2 change this -Dsas.auto.publish.host=DNS Alias of mid2
3. After the changes are saved, restart all the middle tier services.

Note: If the above JVM properties are not updated correctly for a vertical cluster, then intermittent SAS Enterprise Miner errors occur. One of the common symptoms is a pop-up error in SAS Enterprise Miner client with this message:

Stateful processing was unable to find an object matching the passed id <object id>. 
It is likely the backing session timed out or was otherwise destroyed Or the object was 
previously deleted by the client.

The above error can also occur due to other causes.

The steps are valid on SAS Enterprise Miner and Forecast Server versions that use SAS^® 9.4.

Operating System and Release Information