Hi,   Just a process question I'm dealing with. With the task of deploying a new 9.4 platform, I'm currently dealing with a Network Security guy who wants to harden the server ports BEFORE the Mit-Tier server gets deployed. Shouldn't this step be done AFTER the deployment, when you can clearly analyze ALL the ports involved.   The install keeps failing because some ports are not made available.   Anyone experienced this? input appreciated!     Rex           ... View more

Hi,   If you have to deal with 'Forecast Server/Studio' or SAS CPM, those client applications need to work with the 'sas-environment.xml' file.   If you have multiple SAS environments (like most), it's possible to set this file with the description of ALL your SAS environments. SAS users can then just select the appropriate environment they want to work it.   In our case, the following is kind of a puzzle. All 3 environments are identical, but the environment list (i.e. Forecast Stuio) only displays 2 of the 3 available. We've switched with settings all we want, the 'DEV' one NEVER appears on the list:   <environments xmlns="http://www.sas.com/xml/schema/sas-environments-9.4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.sas.com/xml/schema/sas-environments-9.4 http://www.sas.com/xml/schema/sas-environments-9.4/sas-environments-9.4.xsd" version="2.0"> <environment platform-version="9.4" default="false" name="default"> <desc>PROD - prod.server.ip</desc> <service-registry>http://prod.server.ip:7980/SASWIPClientAccess/remote/ServiceRegistry</service-registry> <service-registry interface-type="soap">http://prod.server.ip:7980/SASWIPSoapServices/services/ServiceRegistry</service-registry> <service-registry interface-type="rest">http://prod.server.ip:7980/SASWIPClientAccess/rest/</service-registry> </environment> <environment platform-version="9.4" default="false" name="default1"> <desc>DEV - dev.server.ip</desc> <service-registry>http://dev.server.ip:7980/SASWIPClientAccess/remote/ServiceRegistry</service-registry> <service-registry interface-type="soap">http://dev.server.ip:7980/SASWIPSoapServices/services/ServiceRegistry</service-registry> <service-registry interface-type="rest">http://dev.server.ip:7980/SASWIPClientAccess/rest/</service-registry> </environment> <environment platform-version="9.4" default="false" name="default2"> <desc>STAGING - staging.server.ip</desc> <service-registry>http://staging.server.ip:7980/SASWIPClientAccess/remote/ServiceRegistry</service-registry> <service-registry interface-type="soap">http://staging.server.ip:7980/SASWIPSoapServices/services/ServiceRegistry</service-registry> <service-registry interface-type="rest">http://staging.server.ip:7980/SASWIPClientAccess/rest/</service-registry> </environment> </environments>   Sorry for the display, a cut/paste in a text editor makes it easier to read. (See attached)     Any input appreciated,       Thank you!   ... View more

Hi,   I've inherited SAS platforms that have the following folder structure:   - Dev:        /sas/config/Lev1 - Staging:    /sas/Config/Lev1   Notice the 'C'apital c on the staging (Config). If it was MS-Windows we wouldn't bother, but it's Linux, which means case sensitive.   This adds a burden when writing bash scripts for various maintenance purposes. WHERE can we update/change the folder once it's deployed?       Thank you,       ... View more