JDK Product Registration Information
Registering the JDK
Product Registration begins with the JDK Registration Login page that is launched in your browser after the JDK installation completes (on Windows, click the Finish button on the last installer panel). Log in to your existing Oracle Single Sign-On (SSO) account (http://support.oracle.com/) to register the JDK. If you do not have an existing account, you can create one during the registration process.
You can also complete product registration at any time after installation by opening the register.html file located in the directory where the JDK is located on your system (typically C:\Program Files\Java\jdk1.6.0_05 on Windows, /usr/jdk/jdk1.6.0_05 on Solaris and /usr/java/jdk1.6.0_05 on Linux for JDK6 update 5 release as an example).
About the Product Registration Data Oracle Collects
During the product registration process, Oracle collects digital product identifiers from the Oracle Java Development Kit (JDK) and general information about your system. The collected data provides important feedback to Oracle in order to improve the user experience and to optimize the programs and services we offer customers.
- Who Sends Information to Oracle?
- How Is Information Sent to Oracle?
- When Is Information Sent to Oracle?
- What Information is Sent to Oracle?
WHO Sends Information to Oracle?
Registration data is sent to Oracle when the user successfully installs the JDK and gets the JDK Registration Login page on the web. If you do not register, the data will not be saved. The system that contains the JDK must be connected to the Internet.
HOW Is Information Sent to Oracle?
Small encrypted XML messages are transported via a secure SSL connection over the Internet.
WHEN Is Information Sent to Oracle?
Registration is optional. Registration data is sent to Oracle when the user successfully installs the JDK and gets the JDK Registration Login page on the web. If you do not register, the data will not be saved.
The JDK Registration process has two steps:
- In the first step, the product registration data will be collected at the end of the installation and sent to Oracle only when the JDK Registration Login page is opened.
- In the second step, the user registers the JDK by logging in and clicking the "Register Now" button on the JDK Registration Login page.
WHAT Information is Sent to Oracle?
As part of the registration process, the user's Oracle SSO ID is sent to Oracle. When the registration is submitted, the following product registration information is sent to Oracle:
| Data Name | Value |
|---|---|
| Instance Identifier | Unique identifier for that instance of the JDK |
| Product Name | Name of the JDK (e.g. Java SE 6 Development Kit) |
| Product Identifer | Unique identifier for the product being registered |
| Product Vendor | Vendor of the JDK (e.g. Oracle) |
| Product Version | Version of the JDK (e.g. 1.6.0_05) |
| Parent Name | The parent product of the registered JDK (e.g. Java Platform Standard Edition 6 (Java SE 6)) |
| Parent Identifer | Unique identifier for the parent of the JDK |
| Timestamp | The time the product was registered |
| Source | JDK distribution mechanism (bundle or installer name) |
| Container | The name of the product's container (e.g. "global") |
The following information is sent to Oracle about the system on which the registered JDK resides:
| Data Name | Value |
|---|---|
| Host | The hostname of the system |
| System | The Operating System |
| Release | The version of the Operating System |
| Architecture | The Physical hardware architecture (like SPARC or AMD64) |
| Platform | The hardware platform name (e.g. Oracle SPARC T3-1) |
| Manufacturer | The hardware manufacturer (e.g. Oracle) |
| CPU Manufacturer | The CPU manufacturer (like AuthenticAMD or GenuineIntel) |
| HostID | Host ID of the system |
| Serial Number | Chassis serial number of the system |
Host ID and serial number will only be used to correlate products registered for a particular machine and this allows Oracle to provide better support and updates including:
- provide information when a change in one version of a product on your system would have an impact on other products you have running (related to performance, compatibility or security, for example)
- enable us to better test and optimize performance for your system
- effectively communicate our product or service offerings based on the software you have installed on your system
The above information is collected with the Service Tags technology. For more details on Service Tags and how the information we receive via Service Tags can help you track and manage your Oracle assets.
For more information on Oracle's Privacy Policy see Oracle's Privacy Policy or contact privacy_ww@oracle.com.