Password Utility 1.2

This utility provides a way of making required updates to the configurations of SAS Financial Management 4.2, SAS Strategic Performance Management 2.2 and SAS Human Capital Management 4.1 when any of the following passwords are changed:

• Default Portal Users
  • SAS Administrator
  • SAS Trusted User
  • SAS Guest
  • SAS Web Administrator
  • SAS General Server User
• Default Solutions Users
  • Solutions Role Administrator
• Others
  • WebLogic Administrator
  • MySQL Administrator

Note: Not all installations include all products. Configurations may vary, especially with respect to Domain Servers.

Update Your Configuration

1. Un-Deploy the wars and ears in WebLogic. Stop all WebLogic managed servers and the SAS Services. If you installed these items as Windows services, stop and uninstall the services.
2. If you have changed the passwords for the Solutions Role Administrator or the Solutions Installer, change their passwords in OMR using the SAS Management Console.
3. If you have changed the password of the MySQL Administrator
   Make sure to change the passwords for sqladmin and sqladmin@localhost.
   1. Change the password of the Group Login for the MySQL Users group in OMR using the SAS Management Console.
   2. Log in to the WebLogic Console at the following location: http://<applicationserver>:7501/console.
   3. On the home page under Services Configurations, JDBC click on Connection Pools.
   4. Click on each of the following connection pools (as applicable) then change and confirm the MySQL Administrator password:
      • HCMCP
      • ODCSConnectionPool
      • SASSDMConnectionPool
      • SPMDS
4. Unzip Passwords.zip to Lev1\Utilities\SASSolutionsServices
   Note: This utility will attempt to update the passwords in the managed server start scripts and service installation scripts in bea\user_projects\domains\SASSolutions. If this behavior is undesirable, delete (mid-tier) the WebLogic.txt file in Lev1\Utilities\SASSolutionsServices\Paswords\xml. In this case you will not be able to use the deploy scripts for the Portal or Solutions applications since they will not be able to start your servers. You will have to deploy manually. You may still use the scripts to deploy SAS Web OLAP Viewer for Java, SAS Web Report Studio and SAS Web Report Viewer (required).
5. Run Lev1\Utilities\SASSolutionsServices\Paswords\bin\PasswordUtility.bat. It will display a text file to provide new password values. For a single machine installation, the utility need only be run once. For a multiple machine installation, run it once on the data tier then once on the mid-tier.
6. Follow the instructions using the official doc at http://support.sas.com/rnd/itech/doc9/portal_admin/security/ag_changepass.html
   Please note the following deviations from the "Changing Passwords for User or Group Credentials" doc:
   • Instruction 4.a: It is unnecessary to use the PROC PWENCODE to encode passwords. The encoded passwords can be found in Lev1\Utilities\SASSolutionsServices\Paswords\tmp\Passwords.properties. 
   • Instruction 6: Follow all instructions for the various products, except do not redeploy the wars to the J2EE application server at this time. Continue with these instructions.
7. Copy the Portal.war, SASPreferences.war and SASStoredProcess.war from SAS_HOME\Web\Portal2.0.1 to the SAS\SASSolutionsConfig\Lev1\web\webapps directory.
8. Unzip the wars to the exploded subdirectory.
9. Stop and Start the metadata server, spawner and all other SAS servers.
10. Deploy your web applications using the following scripts (as applicable) in Lev1\Utilities\SASSolutionsServices\Deployment\bin:
    1. SolutionsConfigureAndDeploy.bat
    2. PerformancePrepareToDeploy.bat
    3. PerformanceConfigureAndDeploy.bat
    4. HCMPrepareToDeploy.bat
    5. HCMConfigureAndDeploy.bat
    6. FinancePrepareToDeploy.bat
    7. FinanceConfigureAndDeploy.bat
    8. WebOlapViewer.bat (SASManagedServer must be running)
11. Start your Domain Servers using the provided shortcuts the run the following scripts (as applicable):
    1. HRWebReportStudio.bat
    2. HRWebReportViewer.bat
    3. FoundationWebReportStudio.bat
    4. FoundationWebReportViewer.bat
    5. SolutionsWebReportStudio.bat
    6. SolutionsWebReportViewer.bat
    7. PerfMgmtWebReportStudio.bat
    8. PerfMgmtWebReportViewer.bat
    9. FinanceWebReportStudio.bat
    10. FinanceWebReportViewer.bat
12. If you are using Windows services, you may stop your Managed Servers and the SAS Services, reinstall then start the services.
13. Once all applications are up and running, the process is complete.

Deploying and Un-Deploying Web Applications

While use of the deployment scripts is recommended, the following information is for manually deploying all Solutions EAR files and Portal WAR files. The EAR files and WAR files should have been deployed as part of each Solution's install. Note that Web OLAP Viewer for Java, SAS Web Report Studio and SAS Web Report Viewer will not be updated properly if you do not use the scripts.

Deploy

1. If SAS Solutions Services are not running, execute the following to deploy them: run Program Files\SAS\SASSolutionsServices\1.2\RemoteServices\startRemoteServices.bat
2. If WebLogic is not started, then start SASODCSServer, SASManagedServer and any Domain Servers being used, such as HRServer.
3. Wait until the services have initialized and Managed Serer is running.
4. Copy the applications in the exploded directory to bea\user_projects\domains\SASSolutions\applications
5. Deploy all of the applications using the following instructions.

War Files

1. Log in to the WebLogic Console at the following location: http://<applicationserver>:7501/console.
2. From the tree on the left-hand side, expand Deployments.
3. Click Web Application Modules, then click the Deploy a new Web application Module link.
4. Click Applications.
5. Deploy a war by selecting it, item and then clicking Target Module .
6. Click SASManagedServer for Portal applications or the appropriate Domain Server for SAS Web Report Studio and SAS Web Report Viewer war files, then click Continue.
7. Change Source Accessibility to “I will make the web application module accessible from the following location”, and then click Deploy.
8. Wait for the application to say “active” before continuing with the next Web application.

Ear Files

1. Log in to the WebLogic Console at the following location: http://<applicationserver>:7501/console.
2. From the tree on the left-hand side, expand Deployments.
3. Click Applications, and then click the Deploy a new Application link.
4. Click Applications.
5. Deploy an ear by selecting it, then click Target Application.
6. Click SASManagedServer or SASODCSServer for ODCS, then click Continue.
7. Change Source Accessibility to “I will make the web application module accessible from the following location”, and then click Deploy.
8. Wait for the application to specify “active” before continuing with the next ear.

Un-Deploy

1. Log in to the WebLogic Console at the following location: http://<applicationserver>:7501/console.
2. From the tree on the left-hand side, expand Deployments.
3. Click Web Application Modules to un-deploy wars or Applications to un-deploy ears. 
4. Un-Deploy the war/ear by pressing the trash can to the right of the name. Click Yes to confirm.