Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Basic Administration Oracle Solaris 10 1/13 Information Library |
1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
13. Managing the Oracle Solaris Boot Archives (Tasks)
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
17. Working With Oracle Configuration Manager
Introduction to Oracle Configuration Manager
Managing Oracle Configuration Manager (Tasks)
How to Enable the Oracle Configuration Manager Service
How to Disable the Oracle Configuration Manager Service
How to Manually Register With the Oracle Repository
How to Change the Time or Frequency of Data Collection
18. Managing Services (Overview)
20. Managing Software (Overview)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
Oracle uses support credentials and network connectivity information that is collected before or during an installation or upgrade to associate product registration with a specific user account. If no support credentials or network connectivity information is specified, the Auto Registration process assumes a direct HTTP network connection (no proxy), and the registration is anonymous.
Note - Data loaded anonymously is not tied to any organization and cannot be associated with any service requests.
To register your system by specifying support credentials, you must have a valid My Oracle Support account. Support credentials consist of a user name and password that enable you to authenticate to Oracle's support portal. If you do not have a My Oracle Support account, see My Oracle Support.
Tip - If you have provided your My Oracle Support credentials during installation, you can retrieve and use the system information to more effectively manage your inventory.
For information about obtaining a My Oracle Support account, go to http://www.oracle.com/us/support/index.html.
You can provide support credentials, as follows:
Before or during an installation or upgrade
Before an automatic installation or upgrade (by using either network installation or Oracle Solaris JumpStart), you can provide support credentials by adding the new auto_reg keyword to your sysidcfg file. The same keyword can be used to set up an anonymous registration or to disable the Auto Registration feature. If you do not add the auto_reg keyword to the sysidcfg file, you are prompted to provide your support credentials during the installation or upgrade process.
During an interactive installation or upgrade, you are prompted for your support credentials. Alternately, you can register anonymously. During an interactive installation or upgrade, you can also provide network configuration information, such as the proxy server and proxy port.
During an installation or upgrade, you can use the new -k option in the Oracle Solaris Live Upgrade command to provide your support credentials and proxy information, or to register anonymously.
Note - If Oracle Configuration Manager is already installed on your system and you have configured it to use a custom configuration directory with the ORACLE_CONFIG_HOME environment variable, perform the following steps before upgrading the Oracle Solaris OS.
Move the existing Oracle Configuration Manager configuration directory to the /opt/ocm/config_home directory.
Update any other custom scripts or programs to reflect this new location.
You must perform these steps because, the Oracle Solaris OS installation process expects either a standard Oracle Configuration Manager configuration or an ORACLE_CONFIG_HOME environment variable set to the /opt/ocm/config_home directory.
If you do not perform these steps during an upgrade, Oracle Configuration Manager will be configured to use the /opt/ocm/config_home directory and any prior configuration or log information is not available to Oracle Configuration Manager.
After an installation or upgrade
After an installation, you can use the /opt/ocm/ccr/bin/configCCR command to transition a system from being anonymously registered to fully-registered by providing named support credentials.