So is SPM 5.1 released?

I haven’t seen any announcements, but then again I might have missed it.

Here are the docs I have found so far:

• Installation Instructions–Release 5.1 of the SAS Performance Management Solutions
  Installation Instructions for Release 5.1 of the SAS® Performance Management Solutions Copyright Notice The correct bibliographic citation for this manual is as follows: SAS Institute Inc., Installation Instructions …

  http://support.sas.com/documentation/installcenter/en/ikfmofrii/63034/PDF/default/install.pdf, 433KB
  

• 37794 – Post-migration steps required for SAS® Strategy Management
  The SAS Demo User account must be modified in the SASSDM in order for that user to be able to access SAS Strategy Management content.

  http://support.sas.com/kb/37/794.html, 18KB

Let me know if you know.

I found a public doc on the old ABC Tech support site here, that explains the steps. I have also cut and paste the content below in case the doc disappears.

One thing to note is that if you have two SAS servers wanting to talk via this SAS Share link (i.e one with SAS ABM and the other with SAS DI or EG etc) you need to make sure the SAS Share names are identical on both servers or it wont work!

Oh and don’t forget that you need SAS Share OLEDB client on every PC that wants to export/import. You can install this from the SAS ABM Client install page on your ABM Webserver.

Using SAS/SHARE to Import and Export SAS ABM Datasets

SAS Technical Support

You can set SHARE to run in Batch SAS mode or as a Windows Service. We will show you both methods.

IA: SETTING UP A SIMPLE SHARE SERVER – IN BATCH SAS MODE

From the server console (in this example the server is cornell.na.sas.com):

• Create an empty folder in c:\ and call it sas_lab. We will want to have c:\sas_lab as the default Library for this example.
• Copy the following basic SHARE script to a blank Notepad and save it as: “c:\sas_lab\share.sas”:

   /* share.sas */

   options comamid=tcp;

        libname sas_lab 'c:\sas_lab';

   proc server authenticate=optional;

   run;

Remember: libname should not exceed 8 characters.

·       Create the share.sas shortcut (i.e. “C:\Program Files\SAS\SAS 9.1\sas.exe C:\sas_lab\share.sas”) and drop it to the primary user’s Startup folder. This will autoload the script each time this user logs in to the console.

·       Goto SHARE server’s services file (typically in c:\winnt\system32\drivers\etc\ folder) – and let’s reserve a unique port for our share1:

If you put the line at the very end of the services file, put a carriage return at the end of the line.

·       Finally, double click on the shortcut file. If we’ve done this correctly, you should see a Window screen that looks like the following:

IB: SETTING UP A SIMPLE SHARE SERVER – AS A WINDOWS SERVICE

Everything else here is similar to section 1A – except, instead of creating the share.sas shortcut, you would register share.sas as a Windows Service – using SAS Service Configuration Utility. This utility is bundled with SAS 9.

·       Goto Start >> Programs >> SAS >> SAS 9.1 Utilities >> SAS Service Configuration Utility:

• Give a simple name for both Service Name and Display Name. Start Type should be Automatic.
• Service Path is very important. If you’ve installed SAS 9.1 to its default location, you can cut and paste the following parameter:

“C:\Program Files\SAS\SAS 9.1\sas.exe” -noterminal -unbuflog -sysin “C:\sas_lab\share.sas” -log “C:\sas_lab\%b %d %Y at %H%M.log” -logparm “rollover=session”

For detailed explanation of what this parameter means, check SAS 9 documentation.

• Goto “Account” tab. Here you can use “System Account” or other account with Log on as a service and Act as part of the operating system user rights.
• Click “Install” and make sure your SAS SHARE1 Service is started (Control Panel >> Admin. Tools):

II: SETTING UP A SIMPLE SHARE CLIENT

It is important to understand that when we say “client”, we’re not just talking about the end-user desktops. In ABM context, the ABM server is a “SHARE client” – and such the ABM server must have the correct SHARE client configuration. It is quite simple to set your client (or your “server” client) to talk to the SHARE server. It involves primarily two steps:

• Each SHARE Client services file (typically in c:\winnt\system32\drivers\etc\ folder) must contain the share Id and the reserved tcp port (see previous section on “setting up a simple SHARE server”).
• Each SHARE Client must install SAS/SHARE 9.1 (higher) OLE DB Provider, sasoledb.exe.

This file can be downloaded from the ABM Client Install page:

http://YOUR_ABM_SERVER/SasSolutions/ABM/download/sasoledb/sasoledb.exe

Where YOUR_ABM_SERVER is the name of your ABM Server.

During the Setup, make sure you select “SAS/SHARE Server access”.

III: EXPORTING ABM DATA TO SAS DATASETS

Once we’ve setup SHARE server, configured SHARE clients and tested it, we’re ready to generate the Staging SAS Datasets.

• Login to SAS ABM from your desktop
• File >> Export – this will launch the Export Data Wizard

Note: If you ran into “Server Application Error” at this point, ensure the server’s local user account called IWAM_<serverName> is not disabled.

• Choose “Database” and click Next.
• Click “Browse” and you’ll be presented with the list of Data Providers registered on your desktop.

At this point you want to choose “SAS SHARE Data Provider 9.1” – if you don’t see this, run the sasoledb.exe on your desktop (see previous section on “setting up a simple SHARE client”).

• Hit “Next” and in this particular example, specify share1 as the Data Source and cornell.na.sas.com as the Location.

• Don’t forget to specify the default Library as well. Goto All tab, double click on Extended Properties. In our example we call it sas_lab which is pointing to the server’s c:\sas_lab folder.

• Also in the All tab, if you’re using SAS 8, don’t forget to set SAS Server Release to 8.
• Follow the rest of the Export Wizard instructions.
• Once the Export is finished successfully, you should be able to check the Staging Datasets:

IV: IMPORTING ABM DATA FROM SAS DATASETS

Importing ABM data from SAS Datasets is similar to Exporting. Instead of launching Export Data Wizard, you’d launch ABM’s Import Data Wizard by going to File >> Import >> Data. The Data Link steps is the same as the Export, you’d select SAS SHARE Data Provider and specify the same Connection properties and Library Reference. At the end of a successful Import (no errors), don’t forget to Calculate the Model.

V: SUMMARY

We must first setup the SAS SHARE server and start it. Then we make sure the ABM server services file has registered the unique SAS/SHARE TCP port. Both ABM server and ABM client should install the SAS SHARE OLEDB provider from the Client Install page. The rest is just a matter of following the ABM Export/Import wizards, as described in this article.

One final note: although this article talks about Staging Datasets Imports/Exports – through File >> Import (Export) >> Model Data, the same concept is applicable to Report Datasets Imports/Exports – through File >> import (Export) >> Report Data.