Managing Your SAS Deployment

Updating the SID File in Metadata for SAS Solutions

The topics contained in this section are:

About Updating the SID File in Metadata for SAS Solutions

There are two situations when you might need to update the SAS installation data (SID) file in metadata for SAS solutions:

when you add a SAS solution to your SAS 9.2 deployment
when you need to renew your software license for a SAS solution

About Adding a SAS Solution to Your Deployment

When you deploy a SAS solution on a middle-tier machine that does not also contain SAS Foundation, you must update the SID file in metadata using the SAS Deployment Manager from the machine on which the SETINIT for the solution is enabled. For more information, see Update the SID File in Metadata for SAS Solutions.

About Renewing Your Software License for SAS Solutions

SAS 9.2 ships with a 30-day initial license, or SETINIT. When your new SETINIT arrives, you must renew it on every machine that runs SAS 9.2 software using the typical method according to your operating system: SAS Renewal Tool (Windows), SAS Setup (UNIX), and RENEW job (z/OS). For more information, see the instructions appropriate for your operating system on the Install Center, located at http://support.sas.com/documentation/installcenter/92/index.html (search for "renewal").

Some SAS 9.2 solutions that depend on a SAS middle tier require you to perform an additional step. You will know when you have to update your middle-tier SETINIT when you receive error messages that your SAS license has expired. You must run the SAS Deployment Manager on the machine that the SETINIT is intended for. During the process, the deployment manager locates the new SETINIT and loads it into SAS metadata, effectively renewing your SAS solution software. (For more information about the other Deployment Manager features, see Overview of SAS Deployment Manager and SAS Web Administration Console in the SAS Intelligence Platform: System Administration Guide.)

Update the SID File in Metadata for SAS Solutions

After you add a SAS solution to your deployment, or renew your SAS software, some SAS 9.2 solutions that depend on a SAS middle tier require you to apply the new SETINIT in metadata. This procedure involves using the SAS Deployment Manager to update the SID file in your SAS metadata repository.

Note: You can automate running the deployment manager when you need to perform the same configuration action on many machines in your deployment. The deployment manager uses the same record and playback mechanism as the SAS Deployment Wizard to perform a non-interactive, silent configuration. For more information, see Overview of Automating the SAS Installation on Multiple Machines. [cautionend]

To apply your new software license for middle-tier SAS solutions, follow these steps:

Make sure that you have first done the following:
- obtained your new SETINIT from your SAS representative.
  
  Your SETINIT is contained in a SAS installation data file (sometimes referred to as a SID) that is attached to your software order e-mail (SOE).
- renewed your software license on each machine that runs SAS 9.2.
  
  Follow the instructions appropriate for your operating system located at http://support.sas.com/documentation/installcenter/92/index.html (search for "renewal").
- added your newly licensed software to each machine in your deployment.
  
  For more information, see Adding SAS Products.
If you received more than one SID file, you must make sure that you locate the correct one in order to perform the steps that follow. For more information, see Determine Which SID File to Update in Metadata.
Make sure that you have saved the new SID file on the machine that the SETINIT is intended for.

Note: On z/OS machines only, save the new SID file to the following path:

SASHome/SASFoundation/9.2/setinit.sas

For example:

/usr/lpp/SAS/SAS_92/SASFoundation/9.2/setinit.sas
Make sure that the metadata server is running.
Log on to the machine that the SETINIT is intended for as the SAS Installer user.

This is the user with which your SAS deployment was installed. For more information, see Required External User Accounts for SAS.
Navigate to SAS-installation-directory/SASDeploymentManager/9.2 and launch config.exe (Windows), config.sh (UNIX), or config.rexx (z/OS). On Windows, you can use the shortcut on the Start menu.
In the SAS Deployment Manager, select Update SID File in Metadata.
On the next page, specify the configuration directory and the level (for example, Lev1) for your SAS Solution.
On the next page, enter the user ID and password for an unrestricted administrative user.
On the next page, enter the absolute path to the new SID file on the machine.
Click Start.

When the deployment manager has successfully updated your SETINIT, you should see a page similar to the following:
Click Finish.

The deployment manager has located the new SETINIT and loaded it into metadata. Your SAS solution software has been renewed.
Repeat steps 4 - 11 on any other machines that run a SAS Solution.
Restart your SAS Web application server.

For more information, see Starting and Stopping Web Application Servers in the SAS Intelligence Platform: System Administration Guide.

Note: If you have more than one SAS Web application server, restart the one on which the SASWebInfrastructurePlatformServices9.2 application is running. You can determine which Web application server runs the SASWebInfrastructurePlatformServices9.2 application by consulting your Web application administrative console.

Determine Which SID File to Update in Metadata

If you received more than one SID file, you must make sure that you locate the correct one with which to update your metadata. To determine which SID file to use, follow these steps:

Locate the SAS order number that contains the SAS solution you are adding or whose license you are renewing.

If you do not know the order number, refer to your software order e-mail (SOE).
Locate the tech support site number that contains the SAS solution that you are adding or renewing.

A listing of the tech support site numbers and the SAS product to which they apply can be found in the soi.html file in your SAS Software Depot located under the install_doc/order-number subdirectory. For example: C:\SAS 9.2 Depot\install_doc\507863\soi.html.
SID files are named using this convention:

product_order-number_tech-support-site-number_operating-system.txt

For example: SAS92_507873_70082502_SUN_Sparc.txt.
Open the SID file and verify that the SAS solution is declared in the file.
Record the name of the SID file. You will need to know which SID file to use when performing the steps in Update the SID File in Metadata for SAS Solutions.

Top of Page