Java Jre-6u29-windows-i586 Download BEST
Ilse Thiara
We had spent hours try to get a working version for the newly installed 7.6.2.4 build 669 having same issue, EMC support recommend latest java of course such as update 26, 27. but none of these work to launch NMC.
In the past people were complaining about java inclusion as it made package bigger for download so this has been dropped. As java is required and not something coming from EMC excluding it make sense. update 26 should have worked for you and if it didn't it may only indicate java cache was not cleaned up.
Simply include the java recipe wherever you would like Java installed, such as a run list (recipe[java]) or a cookbook (include_recipe 'java'). By default, OpenJDK 6 is installed. The install_flavor attribute is used to determine which JDK to install (OpenJDK, Oracle, IBM, or Windows), and jdk_version specifies which version to install (currently 6 and 7 are supported for all JDK types, 8 for Oracle only).
Include the default recipe in a run list or recipe to get java. By default
the openjdk flavor of Java is installed, but this can be changed by
using the install_flavor attribute. By default on Windows platform
systems, the install_flavor is windows.
NOTE: In most cases, including just the default recipe will be sufficient.
It's possible to include the install_type recipes directly, as long as
the necessary attributes (such as java_home) are set.
On platforms such as SmartOS that require the acceptance of a license
agreement during package installation, set
node['java']['accept_license_agreement'] to true in order to indicate
that you accept the license.
As of 26 March 2012 you can no longer directly download the JDK from
Oracle's website without using a special cookie. This cookbook uses
that cookie to download the oracle recipe on your behalf, however the
java::oracle recipe forces you to set either override the
node['java']['oracle']['accept_oracle_download_terms'] to true or
set up a private repository accessible by HTTP.
For both RHEL and Debian families, this recipe pulls the binary
distribution from the Oracle website, and installs it in the default
JAVA_HOME for each distribution. For Debian, this is
/usr/lib/jvm/default-java. For RHEl, this is /usr/lib/jvm/java.
After putting the binaries in place, the java::oracle recipe updates
/usr/bin/java to point to the installed JDK using the
update-alternatives script. This is all handled in the java_ark
LWRP.
The java::ibm recipe is used to install the IBM version of Java.
Note that IBM requires you to create an account and log in to
download the binary installer for your platform. You must accept the
license agreement with IBM to use their version of Java. In this
cookbook, you indicate this by setting
node['java']['ibm']['accept_ibm_download_terms'] to true. You must
also host the binary on your own HTTP server to have an automated
installation. The node['java']['ibm']['url'] attribute must be set
to a valid https/http URL; the URL is checked for validity in the recipe.
This cookbook contains the java_ark LWRP. Generally speaking this
LWRP is deprecated in favor of ark from the
ark cookbook, but it is
still used in this cookbook for handling the Oracle JDK installation.
It is acceptable to set the node['java']['jdk_version'] to a specific version if required for your software to run, eg software xyz requires Java 8 to run. Refrain from pinning to specific patches of the JDK to allow users to consume security updates.
Include the java recipe wherever you would like Java installed, such as a run list (recipe[java]) or a cookbook (include_recipe 'java'). By default, OpenJDK 6 is installed. The install_flavor attribute is used to determine which JDK to install (AdoptOpenJDK, OpenJDK, Oracle, IBM, or Windows), and jdk_version specifies which version to install (currently 6 and 7 are supported for all JDK types, 8 and 10 for Oracle and AdoptOpenJDK ).
Include the default recipe in a run list or recipe to get java. By default the openjdk flavor of Java is installed, but this can be changed by using the install_flavor attribute. By default on Windows platform systems, the install_flavor is windows and on Mac OS X platform systems, the install_flavor is homebrew.
On platforms such as SmartOS that require the acceptance of a license agreement during package installation, set node['java']['accept_license_agreement'] to true in order to indicate that you accept the license.
You can not directly download the JDK from Oracle's website without using a special cookie. This cookbook uses that cookie to download the oracle recipe on your behalf, however the java::oracle recipe forces you to set either override the node['java']['oracle']['accept_oracle_download_terms'] to true or set up a private repository accessible by HTTP.
For both RHEL and Debian families, this recipe pulls the binary distribution from the Oracle website, and installs it in the default JAVA_HOME for each distribution. For Debian, this is /usr/lib/jvm/default-java. For RHEL, this is /usr/lib/jvm/java.
After putting the binaries in place, the java::oracle recipe updates /usr/bin/java to point to the installed JDK using the update-alternatives script. This is all handled in the java_oracle_install resource.
While public YUM repos for Oracle Java 7 and prior are available, you need to download the RPMs manually for Java 8 and make your own internal repository. This must be done to use this recipe to install Oracle Java 8 via RPM. You will also likely need to set node['java']['oracle_rpm']['package_name'] to jdk1.8.0_40, replacing 40 with the most current version in your local repo.
Because as of 26 March 2012 you can no longer directly download the JDK msi from Oracle's website without using a special cookie. This recipe requires you to set node['java']['oracle']['accept_oracle_download_terms'] to true or host it internally on your own http repo or s3 bucket.
The java::ibm recipe is used to install the IBM version of Java. Note that IBM requires you to create an account and log in to download the binary installer for your platform. You must accept the license agreement with IBM to use their version of Java. In this cookbook, you indicate this by setting node['java']['ibm']['accept_ibm_download_terms'] to true. You must also host the binary on your own HTTP server to have an automated installation. The node['java']['ibm']['url'] attribute must be set to a valid https/http URL; the URL is checked for validity in the recipe.
The java::notify recipe contains a log resource whose :write action is called when a JDK version changes. This gives cookbook authors a way to subscribe to JDK changes and take actions (say restart a java service):
This cookbook contains the java_certificate resource which simplifies adding certificates to a java keystore. It can also populate the keystore with a certificate retrieved from a given SSL end-point. It defaults to the default keystore /jre/lib/security/cacerts for Java 8 or below and /lib/security/cacerts for Java 9+ with the default password if a specific keystore is not provided.
This cookbook contains the java_jce resource, which installs the Java Cryptography Extension (JCE) policy files for a given Java installation. It defaults to installing the JCE files into the Java location defined by cookbook attributes, but it can be customized to install to arbitrary Java locations. Please note that if node['java']['oracle']['jce']['enabled'] is set to true, this custom resource will be run automatically.
df19127ead