These steps are a measure to get you current NOW. NOTE: With the CM1 5.4 Release and the 8.0 upgrade, you will select a JRE location during the upgrade process. Then follow these steps based on your operating system: Essentially you install the latest JRE 1.8 via operating system or vendor. Updating the JRE is relatively easy for a System Administrator. How to Update the Shipped JRE Using Symbolic Links On Windows and Solaris, it will most commonly be the long term support the license Java 1.8 purchased from Oracle for the server. On Linux systems this will most commonly be the 1.8 JRE provided by the OpenJDK project. Symbolic Links to the 64-bit and 32-bit 1.8 JRE provided by the Operating System or JRE vendor can then be created in place of those folders. This removes the version of Java originally shipped with Percussion (and will likely be required to mitigate a security finding of an old or dated Java). To simplify Java updates, the JRE and JRE64 folders originally shipped by Percussion can be removed. Percussion will look for a JRE64 and JRE folder under the installation root folder when it runs. For Linux or Solaris a good overview can be found here. Documentation on Symbolic Links for Windows can be found here. A Symbolic Link is essentially a file or directory that links to a file, directory, or device at a different location on the file system. Distributions and Vendors push security updates to the Operating System on a regular basis and the Admin can rely on System updates to keep systems secure.Īll versions of Windows and Linux currently support Symbolic Links. From a System Administrator and Security Specialist perspective, it is ideal to rely on the Operating System update mechanism when possible for keeping system libraries such as Java up to date. Percussion CM1/Rhythmyx is supported in mixed environments including Linux, Windows, and Solaris. Simplifying Server Side Java Security Updates Developers building custom Java Extensions on their machines will require a 1.8 JDK, or a JDK capable of generating 1.8 compliant byte code, on their Development machines. IBMs JRE has not been tested, but may work fine as it is 1.8 standards compliant. We have tested Percussion with Open JRE and Oracle JRE. Percussion currently requires a 1.8 Java standard compliant Java Runtime Environment (JRE) in order for it to run. Customers that are developing Java Extensions to Percussion will need a JDK installed to compile and build those extensions, so it may be common to have a JDK installed on a Development instance of Percusion, but it is not required. ![]() Percussion does not require a Java Development Kit (JDK) to be installed in order for it to run. * Not released or available at the current time. This article describes our recommended strategy and best practice for customers in meeting the JRE 1.8 pre-requisite. ![]() Effective with the 732_20190510 Patch level of Percussion Rhythmyx and the 5315_20190520 patch for Percussion CM1 we will no longer ship a JRE with future Patches or releases. Oracle's many licensing changes for Java over the last several years have made this deployment model for Java not tenable. For consistency in customer experience, Percussion server products have historically shipped with a bundled Java Runtime. Percussion CM1 and Percussion Rhythmyx use Java technologies on the server for the application server and on client desktops to run features like the Desktop Content Explorer.
0 Comments
Leave a Reply. |