Managing Your SAS Deployment

Removing a SAS Configuration

The topics contained in this section are:

Overview of Removing a SAS Configuration

The Remove Existing Configuration feature of the SAS Deployment Manager provides an automated way to remove one more products of a SAS Intelligence Platform configuration from your environment. With this feature, you can remove the configurations of all SAS products or just selected products from a machine. You can remove configuration information only, or you can also remove associated user-created content. (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.)

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]

[SAS Deployment Manager]

Note: The SAS Deployment Manager does not uninstall or otherwise affect the SAS software that is located in the SAS installation directory. To uninstall SAS software, see Overview of Uninstalling the SAS Intelligence Platform. [cautionend]

The Remove Existing Configuration feature of the SAS Deployment Manager is useful for the following purposes:

to remove a product that you will no longer be using
to move a product (for example, a SAS Application Server) from one machine to another. In this situation you would do the following:
1. Use the SAS Deployment Manager to remove the product's configuration from the first machine.
2. Use the SAS Deployment Wizard to install and configure the product on the second machine.
to recover from errors in the initial configuration of a product or to implement different configuration options for a product. In these situations you would do the following:
1. Use the SAS Deployment Manager to remove the product's configuration.
2. Use the SAS Deployment Wizard to configure the product on the same machine, and select different configuration options than you selected previously.

When you remove a product's configuration, the SAS Deployment Manager performs the following tasks:

stops the product (or the associated service) if it is running, as well as any dependent products (or associated services). For example:
- If you are removing the configuration of a running OLAP server, then it stops the server. If the server is installed as a Windows service, then it stops the service.
- If you are removing the configuration of a running metadata server, then it stops the server (or the associated Windows service). It also stops any running servers and services that depend on the metadata server, OLAP servers, stored process servers, table servers, workspace servers, pooled workspace servers, batch servers, SAS/SHARE servers, and SAS/CONNECT servers.
  
  Note: The SAS Deployment Manager does not stop the object spawner. You must do this manually.
- If you are removing the configuration for SAS Foundation Services, then it stops the SAS Services Application (Remote Services) or the associated Windows service.
deletes metadata objects that contain the product's configuration information. For example, if you remove a server configuration, then the server's metadata definition is removed and the server no longer appears in the Server Manager tree in SAS Management Console.
on Windows systems, deletes shortcuts that are associated with the product. For example, if you remove a server configuration, then any shortcuts for starting, stopping, pausing, or resuming the server are deleted.
on Windows systems, deletes the service (if applicable) that is associated with the product. For example, if you remove a server configuration, and if the server runs as a Windows service, then the service is removed.
deletes configuration files and directories that are associated with the product. For example, if you remove the configuration for a SAS OLAP server, then the server's configuration directory, files, scripts, sasusers directory, and logs directory are deleted. The only exception is sasv9_usermods.cfg, which is retained if its contents have changed since the initial installation.
deletes site-specific portal content if you are removing the configuration for the SAS Information Delivery Portal and if you select the option to Remove user content for SAS Information Delivery Portal. The content that is removed includes portal pages; portlets; changes to page navigation, page layout, and package sort order; and other similar customizations.
determines whether other products in your deployment depend on the removed products. If dependent products exist, and if you have not selected those products for removal, then the SAS Deployment Manager prompts you to remove them. For example, the SAS BI Dashboard depends on the SAS Information Delivery Portal. If you remove the configuration for the SAS Information Delivery Portal, but you do not remove the configuration for the SAS BI Dashboard, then the SAS Deployment Manager prompts you to remove it. For more information about dependencies, see Identify Dependent SAS Products.
creates an HTML page that lists the items that were removed and describes any additional manual tasks that you need to perform. The page is created in a temporary location. You should save it to a permanent location on your network or file system.
writes detailed log messages to a file called product-name_unconfigure_date-and-time, where product-name identifies the product that was removed. The deployment manager writes this file to SAS-configuration-directory\Levn\Logs\Configure.

Summary of Steps for Removing a SAS Configuration

Here is a summary of the steps that you should take when removing a configuration:

Determine which products' configurations to remove.
Determine which products depend on the products that you are removing. You will need to remove the configuration for each of these products. For details, see Identify Dependent SAS Products.
For each product that you plan to remove, identify the machine where it is installed.

In a single-machine installation, you can remove the configurations of multiple products as well their dependent products in a single execution of the SAS Deployment Manager.

In a multiple-machine installations, you should remove middle-tier products first. Then remove products on the SAS server tier. If you are removing the metadata server, you should remove it last.
Create a complete backup of your system before removing a configuration. This backup should include a correct backup of the metadata server. (See Best Practices for Backing Up and Restoring Your System in SAS Intelligence Platform: System Administration Guide.) This step is important because it is not possible to undo the removal of a configuration.
If you are removing a server, you might want to stop the server (or its associated service), although this is not required. However, you must stop the object spawner if you are removing one of the servers that it runs.

Note: The only exception is the metadata server, which must be running.
If you are unconfiguring a SAS Web application, then depending on the operating system and the Web application server that you are using, do the following:
- JBoss:
  
  Always stop the JBoss Web application server before unconfiguring any of the SAS Web applications.
- WebLogic:
  - On UNIX, keep the WebLogic Web application server running while unconfiguring the SAS Web application.
  - On Windows, always stop the WebLogic Web application server before unconfiguring any of the SAS Web applications. (Make sure that the WebLogic Node Manager is running.)
- WebSphere:
  
  Ensure that the WebSphere Deployment Manager (dmgr) server and nodeagent server are running while unconfiguring the SAS Web application. All application servers (for example, SASServer1) should be stopped.
If you are unconfiguring a SAS middle tier on UNIX, first stop SAS Remote Services before running the SAS Deployment Manager.
When all of the preparatory steps are complete, follow the steps that are described in Remove a Configuration.

Identify Dependent SAS Products

If you remove the configuration of a product that another product depends on, then the dependent product will not be able to function. Therefore, when you remove a product's configuration, the SAS Deployment Manager requires that you also remove the configurations of any dependent products.

Product dependencies are shown in the following table. If you remove the configuration for a product in the left column, then you must also remove the configurations for all of the products that are in the right column opposite that product. For example:

If you remove the SAS BI Dashboard configuration, then you do not need to remove any other products. No products depend on the SAS BI Dashboard.
If you remove the SAS BI Report Services Workspace Configuration, then you must also remove the following dependent products: BI Report Services, SAS BI Dashboard, SAS Web Report Studio, and SAS Web Report Viewer.
If you remove the SAS Metadata Server configuration, then you must remove all other products.

Dependencies in the SAS Intelligence Platform
Product	Dependent Products*
BI Report Services	None
MySQL Database Server	SAS Shared Services (unless SAS Shared Services is using the SAS Table Server) SAS Solutions Services
Platform Process Manager	SAS Web Report Studio and SAS BI Dashboard (if report scheduling is enabled via Platform Process Manager)
SAS Application Server Context	All products except Platform Process Manager
SAS BI Dashboard	None
SAS BI Report Services Workspace Configuration	BI Report Services SAS BI Dashboard SAS Web Report Studio SAS Web Report Viewer
SAS Foundation Services	Web application server (JBoss, WebLogic, or WebSphere) SAS BI Dashboard SAS Help Viewer Metadata Configuration SAS Information Delivery Portal SAS Information Delivery Portal JPS Extension SAS Shared Services SAS Web Report Studio SAS Web Report Viewer SAS Web Infrastructure Platform
SAS Grid Manager Control Server Configuration	SAS Grid Manager Node Configuration
SAS Grid Manager Control Server Configuration (with other grid middleware)	SAS Grid Manager Node Configuration (with other grid middleware)
SAS Information Delivery Portal	SAS BI Dashboard SAS BI Portlets SAS Shared Services
SAS Metadata Server	All products
SAS Object Spawner	BI Report Services Operating System Scheduling Services SAS BI Dashboard SAS BI Report Services Workspace Configuration SAS Pooled Workspace Server SAS Shared Services SAS Stored Process Server SAS Web Report Studio SAS Web Report Viewer SAS Workspace Server
SAS Pooled Workspace Server	SAS BI Dashboard SAS BI Report Services Workspace Configuration SAS Shared Services (if used by SAS Table Server)
SAS Shared Services	None
SAS Solutions Services	None
SAS Stored Process Server	None
SAS Table Server	SAS Shared Services (unless SAS Shared Services is using MySQL Database Server)
SAS Web Infrastructure Platform	SAS BI Dashboard SAS BI Portlets SAS Information Delivery Portal SAS Web Report Studio SAS Web Report Viewer SAS Themes
SAS Web Report Studio	SAS BI Dashboard SAS BI Portlets
SAS Workspace Server	SAS BI Dashboard
Web application server (JBoss, WebLogic, or WebSphere)	SAS BI Dashboard SAS BI Portlets SAS Help Viewer Metadata Configuration SAS Information Delivery Portal SAS Shared Services SAS Web Report Studio SAS Web Report Viewer SAS Web Infrastructure Platform SAS Themes
* These products depend on the product in column 1. Therefore, they must be removed if the product in column 1 is removed.

Note: On z/OS, using the SAS Deployment Manager to remove a Web Application Server Network Deployment configuration also removes the Web application server itself from the node. In the third maintenance release of SAS 9.2, the SAS Deployment Wizard does not support configuring a WebSphere Application Server on z/OS. Therefore, contact your WebSphere System Administrator to redefine the node's Web application servers after unconfiguration. [cautionend]

When you remove a product's configuration, the SAS Deployment Manager checks to see whether your deployment plan includes any products that depend on that product. If dependent products exist, and if you have not selected those products for removal, then the SAS Deployment Manager prompts you to remove them.

Remove a Configuration

In a single-machine installation, you can remove the configurations of multiple products as well their dependent products in a single execution of the SAS Deployment Manager.

[SAS Deployment Manager]

In a multiple-machine installations, you should remove middle-tier product configurations first. Then remove product configurations on the SAS server tier. If you are removing the metadata server configuration, then you should remove it last.

Note: When removing a configuration, the SAS Deployment Manager does not delete any configuration log files associated with the configuration. However, server log files are removed. [cautionend]

Follow these steps to run the SAS Deployment Manager to remove the configurations from each machine:

Make sure that you have completed the preparatory steps that are described in Summary of Steps for Removing a SAS Configuration.
On the host machine for the products whose configurations you are removing, 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 Remove Existing Configuration.

If you are removing the SAS Information Delivery Portal, then you can also select the option to remove user content that is associated with the portal. If you select this option, the SAS Deployment Manager removes portal pages; portlets; changes to page navigation, page layout, and package sort order; and other similar customizations.

CAUTION:
Use caution when choosing the option to remove user content for the SAS Information Delivery Portal.
The content cannot be recovered unless you have a complete backup of your system.
In the next page, specify the configuration directory and the level (for example, Lev1) from which the configuration is to be removed.
In the next page, enter the user ID and password for an unrestricted administrative user.
On the next page, select the check boxes for the products that you want to remove. For each product that you select, be sure to also include the other products on the machine that depend on that product (see Identify Dependent SAS Products).
Detailed log messages are written to a file called product-name_unconfigure_date-and-time.log, where product-name identifies the product that was removed. The deployment manager writes this file to SAS-configuration-directory\Levn\Logs\Configure.
When the configuration removal is complete, the Additional Resources page is displayed. In this page, click on the following document name:

configuration-name-and-level_ConfigurationRemoval.html

The document contains details about the products that were removed and additional manual steps that you might need to perform. The document is created in a temporary location. You should save it on your network or your file system so that you can refer to it later.

For details about what occurs when you remove a configuration, see Overview of Removing a SAS Configuration.

After removing the configuration, you might need to take one of the following additional steps, depending on the reason for the removal:

run the SAS Deployment Wizard to create a new configuration. For details, see Configuring SAS Products.
uninstall the associated software (if you will no longer be using the product on the current machine, or if you will be reinstalling the software on the current machine). For details, see Overview of Uninstalling the SAS Intelligence Platform.

Top of Page