Postgres is not Oracle. I recently did just what you are suggesting for a product wanting a later version of Postgres than we distribute. In general, there was no real difference between setting up for the external server than for an "internal" server. We had to decide to use the same JDBC jar as we use for the internal installations in order to prevent conflicts since tcServer puts each referenced jar in the same directory for actual use. The additional metadata from what I've already called out is to setup a Server Component in the Server Manager plugin to hook your SAS Client Connection to. In fact, I believe you wind up creating both at once. One caveat on client software, we didn't really use any during configurations or migrations because we expect the user to see to managing third party databases. You may want to copy the client scripts from your Postgres server machine to the SAS machine. ... View more

I believe what you want is the Per-user job slot limit.  In the Grid Manager module it is under Batch Hosts on the Advanced tab. ... View more

What defines a job as an orphan? Or is setting a run time wall a more appropriate way of handling this? ... View more

You're on the right track.  Essentially, we want users to see their batch/background results without having to download the results.  We have users who need to hop on SAS Studio, run some reports, see those results but make sure a copy of those results don't end up on the local machine they're using, either in their download folder or some temp folder. One way we thought of making sure this doesn't happen was running SAS Studio in a browser on a remote desktop so no matter what they did in that session, nothing would end up on the local machine.  ... View more

See http://support.sas.com/documentation/cdl/en/connref/69581/HTML/default/viewer.htm#p1eyablk3vvdlkn1h5euyczvt585.htm   ... View more

So that helps us with how we can configure the underlying storage. So if i understand you correctly, we can share all of SASHome where SAS is installed across every node in the cluster, but for SASConfig only share this directory(technically a separate mount for this to work) with the Compute Tier and Metadata Server. For the Mid-Tier it should be able to see the /SASHome where the installs are, and each /SASConfig should be local to each node.   Do you have documentation that says how to configure the Mid-Tier in this way? I have looked at all the documentation that i can find and cannot find any documentation referencing your recommendation. ... View more

It is not hard to convert the authentication from /etc/passwd to LDAP. It requires changes to few files in your SAS Foundation Directory. You can proceed with /etc/passwd as your authentication. ##- Please type your reply above this line. Simple formatting, no attachments. -## ... View more