How the Auto Registration Process Works

During a system reboot, the Auto Registration SMF service checks your system's configuration against the information in the Service Tag Registry to determine whether any changes have occurred since the last reboot. If changes are discovered, a service tag for the newly installed product, for example, the Oracle Solaris 10 9/10 OS, is sent to the Oracle Product Registration System and registered with your recorded support credentials, or anonymously, if no support credentials were provided. The data is transmitted by using a Hypertext Transfer Protocol Secure (HTTPS) connection. If no changes are detected during a reboot, no registration is performed.

Although Auto Registration feature is enabled by default, you can optionally disable the feature. For information, see How to Disable the Auto Registration SMF Service.

The Auto Registration SMF service runs in global zones only.

In addition to the Auto Registration SMF service, the Auto Registration process consists of several other components that work together to affect auto registration of your system's assets. The following figure illustrates these components and their relationship to each other.

Auto Registration consists of the following components:

• Auto Registration command-line interface

  The Auto Registration CLI (/usr/sbin/regadm) enables a privileged system administrator Auto Registration on an Oracle Solaris system. Single commands can be executed from the command line or automated through the use of a script in large server environments. For more information, see the regadm(1M) man page and Registering Your System by Using the regadm Command.

• Oracle Product Registration System

  The Oracle Product Registration System consists of web services that are deployed on the public Internet. These services are responsible for implementing the registration of products.

• Secure transport mechanism

  Oracle uses a secure, one-way transport system for access to its registration system. Client-generated information is encrypted with a private key. Registered products are extracted from the Service Tag Registry and then uploaded to My Oracle Support through the use of a secure HTTPS connection (port 443). The use of an HTTPS connection creates a secure channel over an insecure network. If no HTTP proxy and port are specified during registration, a direct network connection is used. Communications are outbound and are initiated from a customer system only.

• Auto Registration data elements

  The data elements that comprise a registration are identical to the data elements that are used in the Service Tag schema. For more information about the data that is transmitted to the Oracle Product Registration System, go to https://inventory.sun.com/inventory/.