SAS stated that the Information Map Portal hasn't changed much since 9.1.3, but there are a couple of really well placed modifications. Included are my notes on the benefits of moving to Portal 4.2: No xythos - using SAS Content Server now Sticky Pages renamed to Persistent Additional Reference: What's
Tag: business intelligence
New jBoss installs might store excessive logging due to a malformed comment in log4j.properties that threw JBoss into a debug state on startup. There was a comment tag in the jboss-log4j.xml file something like !-- -------------Add new line here à All of the additional hyphens were causing the SASServer1 to
After completing several SAS 9.2 BI and EBI installations, I must profess my love for the improvements: greener! - cds shipped by customer request only, default is Electronic Download faster! less manual steps fewer system user accounts many more sample plans available for more 'standard' installs significant reduction in post-install
![Differences in SAS Enterprise Guide 4.1 and 4.2](https://blogs.sas.com/content/sastraining/files/2009/09/Default-Results-in-EG42.jpg)
SAS Enterprise Guide uses HTML as the output default format. So for converted projects in SAS EG 4.2, there is a possible situation where the reports fail to view. Change the default back to HTML (or deploy SAS EG 4.2 with that format option selected). The option in 4.2 is
You can utilize IIS on your standard web server to connect to the jBoss SAS Installation. There are three steps that must be followed to the T: 1. On IIS Machine A. Create a file location for the dll and properties files. (This location via be referenced via a virtual
![Solving problems with Twitter Friends - Using SAS EG 4.1 in a SAS 9.2 Server Environment](https://blogs.sas.com/content/sastraining/files/2009/09/Issue-Tweet.jpg)
Twitter is an EXCELLENT resource to get SAS friends' feedback on issues. Take for instance the tweet yesterday from @CaroleJesse concerning EG 4.1 issues after installing 9.2 on the Server. @hollandnumerics responded that a command line step could be run to register the 9.2 system. See the dialog below and
![Supporting a SAS Server Architecture](https://blogs.sas.com/content/sastraining/files/2009/08/subzero.jpg)
My prerogative has always been to share my knowledge with the entire SAS user community (hence this blog & all my SAS papers). For an approach to supporting the entire SAS Server Architecture, I presented a paper at the SGF 2009 conference and created a Wiki page in SASCommunity.org to
![Creating a Date Range Prompt in Web Report Studio - SAS 9.2 Version](https://blogs.sas.com/content/sastraining/files/2009/08/4-IMS-FinalFilterSelection.png)
There is actually many more PROMPT types available in SAS 9.2 than the prior version. Including ranges for date, time, text, and numeric! The 'Date Range' type specifically replaces the workarounds necessary in a prior version. (See these workarounds in post: Creating a Date Range Prompt in Web Report Studio
![Creating a Date Range Prompt in Web Report Studio](https://blogs.sas.com/content/sastraining/files/2009/07/daterange_wrs.jpg)
Getting a date prompt that filters on a range of dates requires an Information Map with a date variable that exists twice on the Information Map, two different prompts, and application of both within a Web Report Studio Report. Included are steps to get this to work. Within Information Map
Instead of writing proc metalib statements, SAS has a custom task that you can download into Enterprise Guide. This interface provides non-SAS coders a quick mechanism to register new tables created on the server to the Metadata Library. http://support.sas.com/demosdownloads/setupcat.jsp?cat=SAS%20Enterprise%20Guide