In SAS Business Intelligence packages (where Information Delivery Portal is not licensed), Xythos is not absolutely necessary. Apache can be setup as a webdav folder for SAS Web Report Studio use in storing shared and personal report metadata. This is a much simpler installation process and you loose no functionality
Two options to editing the Portal Welcome Portlet: 1. Take the welcome portlet par and change the text 2. Pg 35 of: http://support.sas.com/rnd/itech/updates/91/portal_dev.pdf Never tried this myself though … I usually just log in as sasguest and edit the entire Public Kiosk page. (Removing the Welcome Portlet and adding a
So you installed SAS v9 BI successfully, but when you download the SAS Management Console on a client site, some of the selections are missing from the menu bar on the left. (For instance, the BI Manager plug-in, a very handy way to manage your BI content.) Never fear, you
Okay, maybe dinky is not appropriate, should I say 'insecure' instead? SASGUEST and SASDEMO come to mind. Think they aren't necessary or could lead to a security breach? Well, that depends ... SASGUEST is responsible for the public kiosk page on the Information Delivery Portal. Doesn't sound like it though
I recently ran into an interesting problem with user group names in SAS BI metadata. I created a new user group to own (and then restrict access to) some Portal pages. When I tried to assign pages to the new group in the Portal I received a Java traceback with
SAS Recently updated the Third Party Software page for SAS equipment (http://support.sas.com/thirdpartysupport). In order for Xythos to successfully integrate with SAS, if SQL Server is used the database version it must be MS SQL Server 2000. MS SQL Server 2005 is not supported for the integration between Xythos and any
Special Character problems in passwords continue to cause issues, and many organizations require the use of at least 1 to pass security requirements. Specific ones to stay away from ... @ ... Just today this caused problems in remote connections to Meta Engine Libname. & ... This can affect users
If you create (in SAS Management Console) a user group with parentheses in it's name you cannot assign a Portal page to that group. A NullPointerException results instead. The workaround is "don't do that", or remove the parentheses if you did. While I haven't exhaustively tested the boundaries of this
If your SMC or other metadata-based SAS tools seem to take a long time to load up when connecting to the metadata server you may benefit from running a reorg. The %OMABAKUP macro includes a reorg parameter which reduces the amount of fragmentation in how the datasets making up SAS
