SUPPORT / SAMPLES & SAS NOTES
 

Support

Installation Note 49711: Updating a SAS® 9.3 Metadata Server-based environment to use Java 7 in the Windows environment

DetailsAboutRate It

This SAS Note is still under development. We apologize for the inconvenience. Please contact SAS Technical Support for additional steps and considerations necessary to install SAS® 9.3 (TS1M2) Metadata Server based deployments using Java 7 on Windows.

This note assumes that you have read and are familiar with SAS Note 49296: "Using Java 7 with SAS® 9.3 TS1M2."


Requirements

  1. Your SAS installation must be SAS 9.3 TS1M2.
  2. SAS® 9.2 and earlier releases of SAS 9.3 are not supported.

    If you are not currently running SAS 9.3 TS1M2, you must first update your installation by applying maintenance. You can request maintenance by completing this form, or by contacting your SAS Installation Representative, or by contacting your SAS account team. (If you need help with identifying your account team, call SAS directly at 1-800-727-0025, option 2.)

  3. Download and install the 64-bit Java Development Kit (JDK) 1.7 Update 15 or later and the 32-bit JRE 1.7 Update 15 or later. Links to vendor sites are provided on our Third Party Software for SAS® 9.3 (TS1M0, TS1M1, and TS1M2) page, for your convenience. As a best practice for the JRE 1.7 installation, install the JRE using the static option. For more details, see SAS Note 48593: "The Oracle automatic update of Windows 32-bit Java 6 to Java 7 might affect the SAS® installation if Java 6 is removed from your system."


  4. If you already have the 64-bit JDK 1.7 Update 15 or later and the 32-bit JRE 1.7 Update 15 or later installed on your system, run the java -fullversion command from the bin directory to ensure that its baseline is at or above our supported minimum baseline.

Steps to Verify That the JRE Baseline Is 32-bit JRE 1.7 Update 15 or Later and Is Functional

  1. Click Start ► Run and enter cmd.
  2. Navigate to the bin directory. For example:
  3. cd\

    cd "C:\Program Files (x86)\Java\jre1.7.0_15\bin\"

  4. Use the -fullversion command to make sure that the JRE is functional:
  5. java -fullversion

    You should then see the following:

    java full version "1.7.0_15-b03"

    If you do not see 1.7.0_15 or later displayed, install the correct JRE.

    If you have a 32-bit Windows operating system, the default JRE location is C:\Program Files\Java\jre.....


Steps to Verify That the JDK Baseline Is 64-bit JDK 1.7 Update 15 or Later and Is Functional

  1. Click Start ► Run and enter cmd.
  2. Navigate to the bin directory. For example:
  3. cd\

    cd "C:\Program Files\Java\jdk1.7.0_15\bin\"

  4. Use the -fullversion command to make sure that the JDK is functional:
  5. java -fullversion


    The following is displayed:

    java full version "1.7.0_15-b03"

    If you do not see 1.7.0_15 or later displayed, install the correct JDK.

New versions of supported web application servers are required to update your SAS 9.3 (TS1M2) deployment to use Java 7. Complete the manual steps to upgrade your existing web application server as detailed in "Upgrading Web Application Servers That Are Used with the SAS® 9.3 Middle-Tier Configuration"


Note: When determining whether to reference the minor or major upgrade sections in the documentation, keep in mind that Oracle WebLogic and JBoss Community (once supported) are major upgrades, whereas steps for IBM WebSphere and JBoss EAP depend on your current release. If you have additional questions regarding the web application server steps, create a track with SAS Technical Support with the Mid-Tier team.

After the Requirements Are in Place

  1. Ensure that there are no SAS services or processes running on the machine, including your Web Application Server (for example, JBoss). Use Windows Services and the Task Manager to verify that there are no services or processes on the machine.

    1. For Services, select Start ► Run and enter services.msc.
      For Windows 7, enter services.msc in the "Search programs and files" command box.
    2. Look for any SAS services (for example, the SAS>sup>® PC Files Server or SAS [EntBIServer-Lev1] SASMeta - Metadata Server)
    3. If the service is started, select the item and click Stop.


  2. For Task Manager, right-click an empty space on the taskbar and then select Task Manager (alternatively, you can press and hold the Ctrl+Alt+Delete keys to start the Task Manager).
  3. If any of these processes is running, select and stop it:
         sas.exe 
         spawner.exe 
         objspawn.exe
  4. Follow the steps in the Configuring SAS® 9.3 to Use an Alternative Java Runtime Environment or Java Development Kit document.


  5. As an alternative to the manual steps under "Windows for SAS® Foundation Software" and "Reconfiguring the Standard SAS Application Launcher," you can use the Automated Configuration Changer tool to automatically make changes to the sassw.config file and the sasv9.cfg file for you. The Configuration Changer tool makes a backup of the original files before it makes any changes.

    If you use the Configuration Changer tool and you have a Middle Tier (Web Tier) in your deployment, these are the only steps left to perform in the alternative JRE or JDK for Windows:

    1. Reconfiguring SAS 9.3 Remote Services
    2. Java Development Kits and Java Application Servers
    3. Follow the steps in the SAS Hot Fix Analysis, Download and Deployment Tool's "Usage Guide" to download and apply hot fixes. Ensure that Java 7-specific hot fixes listed under the hot fix tabs in links at SAS Note 49296: "Using Java 7 with SAS® 9.3 TS1M2.." are included as appropriate for products in your installation. A good practice is to download the hot fixes to the SASHOME/InstallMisc/HotFixes/New directory (the default location on Windows is C:\Program Files\SASHome\InstallMisc\HotFixes\New).


  6. Make sure you start the SAS services back up (starting with the SAS Metadata Server).


  7. Verify your middle tier deployment by following validation steps in your Instructions.html file under the Lev1/Documents directory (for example: C:\SAS\Config\Lev1\Documents\Instructions.html).

Use the Automated Configuration Changer Tool

This tool does not install Java. It just does what the manual steps in Option A, above, do. If this automated process does not successfully complete for you, follow the manual configuration steps in Option A, above.

  1. To access the Configuration Changer, click here to download the ZIP file that contains the executable file.


  2. Open the ZIP file and double-click the Configuration Changer executable file.


  3. Run the executable file.


  4. When you see the following prompt, click Open.
  5. image label



  6. Double-click the executable file.
  7. image label



  8. In response to the following caution, click Yes.


  9. image label

  10. The Welcome banner appears. Click Next.


  11. image label

  12. Per the prompt, make sure that you have closed all SAS sessions, processes, and clients before you proceed. (Keep them closed throughout the process.) Click Next.


  13. image label

  14. If the tool detects the recommended Java 7 version on your system, and both condition statements are green, click Next. Otherwise, click Select my own Java Runtime Environment.


  15. image label

  16. Click Browse and navigate to your Java 7 JRE directory. (For example: C:\Program Files(x86\Java\jrel.7.0_15.) Click Next.


  17. image label

  18. In the next dialog box, make sure that the path that appears in the field is correct. Then click Next.


  19. image label

  20. In response to the "Let's begin" prompt, click Start.

    image label


  21. Wait while the reconfiguration process runs—it takes only a few seconds.


  22. image label

  23. When the "Success" message appears, click Exit.


  24. image label




Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemBase SASMicrosoft Windows Server 2003 for x649.3_M29.3 TS1M2
Microsoft Windows Server 2003 Standard Edition9.3_M29.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition9.3_M29.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition9.3_M29.3 TS1M2
Microsoft® Windows® for x649.3_M29.3 TS1M2
Microsoft Windows Server 20089.3_M29.3 TS1M2
Microsoft Windows Server 2008 for x649.3_M29.3 TS1M2
Microsoft Windows XP Professional9.3_M29.3 TS1M2
Windows 7 Enterprise 32 bit9.3_M29.3 TS1M2
Windows 7 Enterprise x649.3_M29.3 TS1M2
Windows 7 Home Premium 32 bit9.3_M29.3 TS1M2
Windows 7 Home Premium x649.3_M29.3 TS1M2
Windows 7 Professional 32 bit9.3_M29.3 TS1M2
Windows 7 Professional x649.3_M29.3 TS1M2
Windows 7 Ultimate 32 bit9.3_M29.3 TS1M2
Windows 7 Ultimate x649.3_M29.3 TS1M2
Windows Vista9.3_M29.3 TS1M2
Windows Vista for x649.3_M29.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.