SAS

Information relating to SAS

Want to know what replaced Xythos in SAS 9.2/9.3 – enter the jackrabbit

Nov
16

In SAS 9.1.x the WebDav technology SAS used was powered by an open source component called Xythos.

Xthyos provided the mechanism by which the SAS Web tools (WRS, Portal etc) could read and write to a database repository (Postgres, Oracle, Sql Server etc) to store the content (WRS (XML) reports).

In SAS 9.2 / 9.3, SAS re-engineered the entire platform to remove the Xythos component and deliver what is called the SAS Content Server.

If you look under the cover, you wil find that SAS have replaced Xythos with another open source component to provide the WebDav capability, this time Apache JackRabbit.

When you start up the Web server and checkout the logs and you wil see something along the lines of:

“2011-11-11 12:42:32,836 INFO org.apache.jackrabbit.webdav.simple.SimpleWebdavServlet – WWW-Authenticate header = ‘Basic realm=”Jackrabbit Webdav Server”

Posted by Shane Gibson

0 Comments

Adding WRS to Portal in SAS 9.2 / 9.3

Nov
02

Want to add Web Report Studio as a link in the SAS 9.2/9.3 Portal with single sign-on?

Add a Portal application using the following url:

http://<your server>:<your port>/SASWebReportStudio/logonFromPortal.do

Posted by Shane Gibson

0 Comments

How to create multiple LSF users

Nov
02

By default when you install and configure LSF as part of SAS you get two users created lsfadmin and lsfuser.

Good SAS Admin practice is not use either of these accounts to schedule your production batch runs, but to create a new user for this specific task.

Of course the steps to creating new LSF users is buried in the middle of a raft of user and admin guides so most customers I deal with don;t bother.

Michael from Scorpio (he is Australian and drinking out of saucers at the moment has written a step by step blog that describes what you need to do to achieve this process over here:

Platform Suite for SAS – Dev/Test/Prod Tips

Posted by Shane Gibson

0 Comments

Adding custom content to SASPortal in SAS 9.2 & 9.3

Oct
27

Web Application Custom Content

If you wish to add custom content into SAS web applications, you may do so by placing your custom content into the appropriate custom content directory structure for the given application, and then running the SAS Deployment Manager to rebuild web applications. The custom content root directory for a given web application is

/data/SASCONFIG/Lev1/Web/Common/Server Name/Application Name/CustomContent

For example,

/data/SASCONFIG/Lev1/Web/Common/SASServer1/SASWebReportStudio4.2/CustomContent

Within that directory, there are subdirectories (for example, ears or wars) corresponding to specific archive types (ear and war files, respectively). Under the archive type directories, there are subdirectories for each specific archive—these are the root directories for each archive within the application. Custom content should be placed in the archive’s directory tree corresponding to where the content should appear within the archive.

For example, to add the ear_addon.xml file into the addons directory in the sas.webreportstudio ear file, create the

…/CustomContent/ears/sas.webreportstudio/addons

directory, and place ear_addon.xml in it. Our process knows which war files are contained within ear files, so if you want to add war_addon.jar into the WEB-INF/lib directory in the sas.webreportstudio war file within the sas.webreportstudio ear file, then create

…/CustomContent/wars/sas.webreportstudio/WEB-INF/lib

directory, and place war_addon.jar in it.

Once all your custom content is ready to be consumed, run the SAS Deployment Manager and choose to rebuild web applications. Doing so will rebuild the web applications, inserting the custom content into the archives under the appropriate paths. Note that if custom content has the same path and name of content normally included in the archive, then the custom content takes precedence.

Posted by Shane Gibson

0 Comments