Installation Instructions for Hot Fix D47001

64-bit Enabled Solaris

Hot fix D47001 addresses the issue(s) in SAS Portal and Portlets 4.2_M2 on 64-bit Enabled Solaris as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/D47.html#D47001

This hot fix contains updates to the following software components:

SAS BI Portlets 4.2_M1
SAS Information Delivery Portal 4.2_M2

IMPORTANT NOTES

1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

2. You must have Administrator Privileges on your CLIENT or SERVER machine.

3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

4. This hot fix should be installed using the same userid who performed the initial software installation.

INSTALLATION

To install the hot fix, on each machine:

1. Verify that the installation binary has execute permission. If it does not, use the chmod command to make it executable.

$> chmod 755 D47001s6.bin

export DISPLAY=<your_node_name>:0

<path_to_downloaded_file>/D47001s6.bin

./D47001s6.bin

If components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.

See the Maintenance Installation Tool (MIT) documentation for more details on the installation of hot fixes.

This completes the installation of D47001. Please perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

SAS BI Portlets 4.2_M1
SAS Information Delivery Portal 4.2_M2

SAS BI Portlets 4.2_M1

This hot fix requires post-installation steps that will update the web application deployed to your application server.

Step 1: Re-build Web Applications

In order for this step to execute correctly, the Metadata Server must be running.

1.1 Set the DISPLAY environment variable, for example

$ export DISPLAY=<displayname>:0

1.2 Invoke the SAS Deployment Manager 9.2

From the SASDeploymentManager directory execute config.sh, for example

$ cd <SASHOME>/SASDeploymentManager/9.2
$ ./config.sh

1.3 Select a language in the Choose Language box

1.4 Select Rebuild Web Applications

1.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

1.6 Specify Connection Information, including the sasadm User ID and Password

1.7 Select SAS BI Portlets 4.2 as the Web Application to Rebuild

1.8 Verify the information on the Summary screen and select Start

1.9 Select Finish when the deployment is complete

This process will update the sas.biportlets4.2.ear files in <CONFIGDIR>/Lev1/Web/Staging.
A backup of the original ear files will be placed in the Backup directory.

Step 2: Re-deploy Web Applications

2.1 Re-deploy the web applications based on the instructions in SAS Web Application Administration Guide, Chapter 8, for the web application server you are using.

SAS Information Delivery Portal 4.2_M2

This hot fix requires post-installation steps that will update the web application deployed to your application server.

Step 1: Re-build Information Delivery Portal PAR Files

In order for this step to execute correctly, the Metadata Server must be running.

1.1 Open a Windows Command Prompt

1.2 Setup the environment by issuing the following commands:

	cd <CONFIGDIR>/Lev1/Utilities
	export TWELVEBYTE=javaportal
	export STDLOGNAME=<CONFIGDIR>/Lev1/Logs/Configure/javaportal_RebuildSASPARs.log
	export LEVEL_ROOT=<CONFIGDIR>/Lev1

1.3 Re-build the PAR files

launchconfigtarget.sh -f <SASHOME>/SASInformationDeliveryPortal/4.2/Config/javaportal_config.xml
-Doma.person.admin.login.userid="sasadm@saspw"
-Doma.person.admin.login.passwd="xxxxxx"
-Dmetadata.connection.userid="sasadm@saspw"
-Dmetadata.connection.passwd="xxxxxx"
-Doma.authenticationdomain.name="DefaultAuth" RebuildSASPARs

1.4 Verifying update

After executing the script in step 1.3, you must review the javaportal_RebuildSASPARs.log file in <CONFIGDIR>/Lev1/Logs/Configure
to make sure no errors occurred and the script executed successfully.

Step 2:(Optional) Update metadata properties used by WebDAV files in the Portal

See instructions in SAS Note 41845

Step 3: Re-build Web Applications

In order for this step to execute correctly, the Metadata Server must be running.

3.1 Set the DISPLAY environment variable, for example

$ export DISPLAY=<displayname>:0

3.2 Invoke the SAS Deployment Manager 9.2

From the SASDeploymentManager directory execute config.sh, for example

$ cd <SASHOME>/SASDeploymentManager/9.2
$ ./config.sh

3.3 Select a language in the Choose Language box

3.4 Select Rebuild Web Applications

3.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

3.6 Specify Connection Information, including the sasadm User ID and Password

3.7 Select SAS Information Delivery Portal 4.2 as the Web Application to Rebuild

3.8 Verify the information on the Summary screen and select Start

3.9 Select Finish when the deployment is complete

This process will update the sas.portal4.2 ear file and sas.packageviewer4.2 ear file in <CONFIGDIR>/Lev1/Web/Staging.
A backup of the original ear files will be placed in the Backup directory.

Step 4: Re-deploy Web Applications

Re-deploy the web applications based on the instructions in SAS Web Application Administration Guide, Chapter 8, for the web application server you are using.

This completes the installation of hot fix D47001 on 64-bit Enabled Solaris.