As a consultant working for multiple clients, having JBoss installed on a laptop is common to perform demonstrations or to develop SAS BI applications. JBoss can become flaky over time and be a source of frustration for local installations because the operating environment changes very frequently compared to a server environment. Digging through logs trying to find a direct answer to why a report link does not work or why a BI Dashboard indicator will not link properly is a huge headache. I have experienced instances where some web applications work and others do not. A simple configuration task can be performed to prevent a lot of these random issues – especially for mobile laptops which change environments frequently. It involves adding an additional JVM option to the scripts or batch files which start the web application server (JBoss) and the SAS Remote Services service. Binding JBoss The 9.3 Mid-Tier administration guide describes how to set the JGroups Bind Address for JBoss, Weblogic, and WebSphere. The JGroup Bind Address needs to be set for SAS Remote Services and JBoss (or whatever the mid-tier application server is). The bind address MUST be the same for both JBoss and SAS Remote […]
Read more →