Deploying Content Manually to the SAS Content Server

Overview

SAS Web applications such as the SAS Information Delivery Portal and SAS Web Report Studio require the availability of content for its users. The SAS Content Server provides a WebDAV content repository that stores digital content (such as documents, reports, and images) that is created and used by SAS client applications.
To enable the availability of the content in the SAS Content Server, you can load content, update existing content, and adjust Web applications that store SBIP URLs. These tasks can be automated or they can be performed manually.
The following table shows the choices available in the SAS Deployment Wizard, and the results or manual tasks that follow these choices.
Selecting Automatic Options or Manual Performance of Tasks
Options Selected in SAS Deployment Wizard
Results and Instructions for Manual Tasks
Web Application Server: Automatic Configuration
Web Application Server: Automatic Deployment
The Web application server is configured automatically. SAS Web applications are deployed automatically, and content is loaded to the SAS Content Server. If applicable, Web applications that store SBIP URLs are adjusted automatically.
Web Application Server: Automatic Configuration
Manually deploy Web applications, load the content to the SAS Content Server, and adjust any Web applications that store SBIP URLs.
The Web application server is configured automatically. Instructions are provided on how to manually deploy SAS Web applications, load content to the SAS Content Server, and adjust any Web applications that store SBIP URLs.
Manually configure the Web application server, deploy the Web applications, load the content to the SAS Content Server, and adjust any Web applications that store SBIP URLs.
Instructions are provided on how to perform all tasks manually.
The following table shows when you can load or update content (and adjust URLs) either automatically or manually.
Criteria for Deploying Content to the SAS Content Server
Configuration of Web Application Server
Deployment of Web Applications
Load Content
Update Content
Adjust URLs
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Manual
Manual
Manual
Manual
Manual
Manual
Manual
Manual
Manual
The following table shows the files associated with loading content to the SAS Content Server or updating content. The filename for the batch or script file includes the order number.

Security Considerations for SAS Content Server Scripts

The scripts that are described in this section for loading content, updating content, and adjusting URLs use the SAS Administrator and SAS Trusted User credentials. For deployments that performed a manual deployment of the SAS Web applications, these scripts include the user IDs and an encoded form of the password. For deployments that performed an automatic deployment of the SAS Web applications, the scripts include the user IDs, but do not include the passwords in any form.
Passwords in these files, whether added by the SAS Deployment Wizard, or by a SAS administrator, are not updated with the Update passwords feature of the SAS Deployment Manager. Running the scripts with an expired password, or no password, provides a log result like the following example:
Log File Example for Invalid Credentials
config.init:
     [echo] ant.version=Apache Ant version 1.7.0 compiled on December 13 2006
     [echo] ant.file=/opt/SASHome/SASWebInfrastructurePlatform/9.3/Config/webinfpltfm_config.xml
     [echo] file.encoding=ISO646-US
     [echo] about to read property file because config.init.set=${config.init.set}
[GetObjectProperties] Error connecting to the metadata server: Access denied.
[GetObjectProperties]    Host: hostname.example.com
[GetObjectProperties]    Port: 8561
[GetObjectProperties]    User: sasadm@saspw
[GetObjectProperties]    m_mdFactory: com.sas.metadata.remote.MdFactoryImpl@74db2c
[GetObjectProperties] Error finding foundation repository: Encountered metadata exception.

BUILD FAILED
/opt/SASHome/SASDeploymentManager/9.3/products/
cfgwizard__93345__prt__xx__sp0__1/Utilities/configuration_targets.xml:95: null
If you need to update or add a password, use the PWENCODE procedure. The following code example shows how to generate the encoded form of the password changeit. Copy and paste the result into the scripts.
PWENCODE Procedure Example
proc pwencode in="changeit" method=sas002; run;
The SAS log shows the value to copy and paste into the script:
{SAS002}4DE4CF4F130AC6BE4A6934E0596C8222
After you run the scripts, remove the encoded form of the passwords from the scripts as an additional security measure.

Load Content Manually to the SAS Content Server

If you deploy SAS Web applications manually, you need to load content manually to the SAS Content Server. For information about how to load content manually for SAS Web applications, see your Instructions.html file.
Use the following batch file or shell script to load content manually:
  • On Windows:
    SAS-config-dir\Lev1\Web\Utilities\manualLoadContent-OrderNumber.bat
  • On UNIX and z/OS:
    SAS-config-dir/Lev1/Web/Utilities/manualLoadContent.sh-OrderNumber.sh
If Web applications were deployed manually, this script contains the credentials for the SAS Administrator, as well as the SAS Trusted User. The password is always encrypted in the file. After loading content successfully, remove credentials for the SAS Administrator and the SAS Trusted User.
If Web applications were deployed automatically, the script does not contain the required credentials. You must manually enter the required credentials in this script file.

Update Content Manually for the SAS Content Server

If you deploy updated SAS Web applications manually, you must manually update the DAV content in the SAS Content Server. For more information, see your UpdateInstructions.html file, which is located in the SAS-config-dir /Lev1/Documents directory.
You must update content manually before portal content is promoted to SAS Information Delivery Portal 4.3. In this case, data explorations must be converted to reports, and directive URLs should be adjusted manually. For more information, see Promote the Entire Portal Application Tree in SAS Intelligence Platform: Web Application Administration Guide.
Use the following batch file or shell script to update the DAV content manually:
  • On Windows:
    SAS-config-dir\Lev1\Web\Utilities\manualUpdateContent-OrderNumber.bat
  • On UNIX and z/OS:
    SAS-config-dir/Lev1/Web/Utilities/manualUpdateContent-OrderNumber.sh
If Web applications were deployed manually, this script contains the credentials for the SAS Administrator, as well as the SAS Trusted User. The password is always encrypted in the file. After loading content successfully, remove credentials for the SAS Administrator and the SAS Trusted User.
If Web applications were deployed automatically, the script does not contain the required credentials. You must manually enter the required credentials in this script file.

Adjust Directive URLs Manually

Directive URLs are updated either during the migration of a product from one version to another version, or when a product's content is modified and updates are required. When the script is run to adjust URLs, it updates references to metadata that has moved either during migration or an upgrade. These references are stored as SBIP URLs.
You must update content manually before portal content is promoted to SAS Information Delivery Portal 4.3. In this case, data explorations must be converted to reports and directive URLs should be adjusted manually. For more information, see Promote the Entire Portal Application Tree in SAS Intelligence Platform: Web Application Administration Guide.
Here are some examples of instances that require adjusting URLs manually:
  • When a migration is performed, some reports might be moved to a user’s home folder. If there were references to the data in those reports (in the form of SBIP URLs), then those references are updated by the script.
  • During a migration or an upgrade, data explorations are converted to reports. If there were references to the data explorations (in the form of SBIP URLs), then those references are updated by the script.
After updating content manually for the SAS Content Server, adjust directive URLs manually by running the appropriate script or batch file:
  • On Windows:
    SAS-config-dir\Lev1\Web\Utilities\manualAdjustURLs-OrderNumber.bat
  • On UNIX and z/OS:
    SAS-config-dir/Lev1/Web/Utilities/manualAdjustURLs-OrderNumber.sh
The instructions for running the script or batch file are provided in the Instructions.html migration or the UpdateInstructions.html file during an upgrade. The script contains the credentials for the SAS Administrator, as well as the SAS Trusted User. The password is always encrypted. When you have successfully loaded the content, remove the credentials for the SAS Administrator and the SAS Trusted User.

Log Files Generated by the Scripts

When any of the scripts in the previous sections are run, log files are produced for each SAS Web application that is affected. Log messages are written to a file called product-name_script-name_date-and-time.log For UNIX and z/OS machines, the log filename always includes the date and timestamp. For Windows machines, the log filename includes the date and timestamp for machines that use an English locale only.
These log files are located in the following directories:
On Windows:
SAS-config-dir\Lev1\Logs\Configure
On UNIX and z/OS:
SAS-config-dir/Lev1/Logs/Configure