you need to use --config-dir ... View more

Vault is one of the first things configured, I think what you're encountering is a proxy error, not really a Vault issue. Have you configured a proxy server on the OS? Did you include all the hostnames as directed in the no_proxy list?     https://go.documentation.sas.com/?cdcId=calcdc&cdcVersion=3.5&docsetId=dplyml0phy0lax&docsetTarget=n1xuw0txf5apocn1g83wdd8olnrf.htm&locale=en     ... View more

If they haven't called (and it's a critical issue)  that's the first thing to do: https://support.sas.com/en/technical-support/services-policies.html#hours   For Critical Support Requests after Normal Support Hours Calls to SAS Technical Support for critical requests after normal support hours are directed to one of the SAS worldwide support centers in North America, Europe, or Asia/Pacific, thus providing 24-hour, follow-the-sun support. Customers can update tracks electronically 24x7. However, for new requests or for existing tracks with requests that become critical outside of normal business hours, customers must also call SAS Technical Support. The phone number is available on the Contact SAS Technical Support web page. When customers call, they must press 2 for Technical Support, listen to the greeting in its entirety, and then press 0 to start follow-the-sun support. Note: After-hours support is available only in English and is limited to critical requests for software products under Standard Support. Because the support is in English, it is important that customers are able to adequately discuss their request in English. SAS provides self-help resources such as support.sas.com and the SAS Support Communities for software products under Limited Support. Customers can search these resources for potential circumventions to issues that are similar to the one that they are experiencing. In addition, customers can access the SAS Support Site website and email support services 24 hours a day. ... View more

https://go.documentation.sas.com/?docsetId=bimtag&docsetTarget=n1bxtemg7dvpkwn14a7xf8lwt1g6.htm&docsetVersion=9.4&locale=en   Is the doc chapter for JMS Broker. The primary consumers are the web application servers, you can search for "brokerURL" in the various LevX/Web/WebAppServer/SASServer*/conf/server.xml files to see the reference. It's used to sync queues and topics across multiple JVMs.      ... View more

multiple managed servers means the applications are divided into multiple web application servers, running in different JVMs on different ports.  There is still only ever 1 copy of each. You would have SASServer1_1 SASServer2_1 SASServer12_1 (which numbered servers you have, varies based on what products you have installed)   Horizontal clustering means you have more than one machine hosting middle tiers (which from your description sounds like a no). You do have multiple copies - just not on the same machine   So midtier #1 would look like SASServer1_1 SASServer2_1 SASServer12_1   And midtier #2 would also have SASServer1_1 SASServer2_1 SASServer12_1     Vertical clustering means you have multiple copies of a server on a single host,  eg, SASServer1_1 SASServer1_2 SASServer2_1 SASServer2_2 SASServer12_1 SASServer12_2   The best file to check is LevX/Web/WebServer/conf/sas.conf   It will list every application, and what server(s) are serving it. So when you search for "BalancerMember", you will find various proxy stanzas, and in a non clustered deployment, each stanza will only have one member, in a clustered setup, you would find multiple balancer members per each proxy.    BalancerMember   Not clustered: <Proxy balancer://hostname_Cluster1> BalancerMember ... ...  </Proxy>   Clustered: <Proxy balancer://hostname_Cluster1> BalancerMember ... BalancerMember ... ...  </Proxy> ... View more