You can install and configure an Enterprise Controller High Availability environment on Linux systems.
The first step in this process is to install the Enterprise Controller nodes, using a customer-managed remote database and Oracle Clusterware.
Once you have installed the Enterprise Controllers, you configure the primary Enterprise Controller through the user interface. The configuration process specifies many characteristics of the Enterprise Controller, and can install and configure one or more Proxy Controllers based on your choice of deployment:
A simple deployment configures the co-located Proxy Controller on the Enterprise Controller system.
An advanced deployment remotely installs and configures one or more Proxy Controllers on remote systems.
Installing Proxy Controllers outside of the configuration wizard lets you install and configure Proxy Controllers remotely or manually after configuring the Enterprise Controller.
Manual configuration lets you create a configuration file with the configuration details. You can enable the co-located Proxy Controller using manual configuration, but other Proxy Controllers must be configured separately.
If you decided to install Proxy Controllers outside of the configuration wizard, or if you need to install Proxy Controllers at a later date, use the procedures in the Installing Proxy Controllers chapter.
This chapter includes the following sections:
You can install Enterprise Controller software on systems that are running the Linux OS, with one Enterprise Controller configured as the primary and one or more Enterprise Controllers configured as standby systems. This enables you to switch to a different node to perform maintenance or avoid a loss of service if one node fails.
This installation installs, or upgrades to, Java Development Kit (JDK) 7 Update 101 for the use of the Enterprise Controller and Proxy Controllers. If the system already has a later version of JDK installed, then the later version of JDK is used.
Note:
If your environment includes Oracle VM Servers for x86, the Proxy Controllers that manage these systems must be modified to use JDK 6. This procedure is described in the Installing Proxy Controllers chapter.
Note:
Do not upgrade the Java version on Oracle Solaris 10 Control Domains or Logical Domains that have LDOM Manager version 3.2 or earlier installed. If you have upgraded the Java on these systems to version 1.6.0_101 or higher, downgrade to Java 1.6.0_95.
If you need a Java version greater than the version that the Enterprise Controller software installs, you must manually install the desired Java version before the Enterprise Controller software installation. For more information on manually installing Java, see Installing the Java Version Manually.
This procedure configures the software to use a remote Oracle Database. The customer-managed database must be installed and configured separately.
The script that installs the Enterprise Controller also automatically installs a Proxy Controller on the same system, but it does not enable the Proxy Controller. In the configuration steps performed as part of the primary Enterprise Controller installation, you can choose to enable this Proxy Controller.
Note:
The installation procedure requires database user name, password, and URL information. Work with your database administrator if you do not have access to this information.
Note:
If you have already installed and configured a single Enterprise Controller, you can convert to Enterprise Controller High Availability.
Installing and configuring Oracle Clusterware is the first step in setting up High Availability in your environment.
This procedure describes the steps to configure systems with High Availability.
You must install the Enterprise Controller on each cluster node before configuring the software. The first node is initially configured as the active node.
This procedure describes the steps to install the Enterprise Controllers on the first node.
Once you have installed the Enterprise Controller nodes, you configure them. This process includes configuring one Enterprise Controller as the primary node, configuring the user interface, and configuring the remaining Enterprise Controllers as standby nodes.
The following topics are covered:
Once you have installed the primary and standby Enterprise Controllers, configure the primary Enterprise Controller to act as the primary.
This procedure describes the steps to configure the primary Enterprise Controller.
After you install the Enterprise Controller, you must configure it. During the configuration process, you specify how Oracle Enterprise Manager Ops Center operates.
The following tasks are part of the configuration process:
Supplying Enterprise Controller information
Deploying one or more Proxy Controllers (optional in this wizard, but must be performed before using the software)
Registering the Enterprise Controller (optional)
Creating libraries
Choosing a connection mode and configuring services (optional in this wizard, but must be performed before using the software)
This procedure describes the complete Enterprise Controller configuration process, including Proxy Controller deployment, asset discovery, connection mode selection, and registration.
Four types of configuration are described in this section:
Simple deployment: A simple deployment configures the co-located Proxy Controller on the Enterprise Controller system. This deployment is effective for small environments.
Advanced deployment: An advanced deployment installs and configures one or more Proxy Controllers on remote systems. This deployment is effective for larger environments.
Deploy without installing a Proxy Controller: This deployment configures the Enterprise Controller without installing or configuring any Proxy Controllers. This deployment is appropriate if you intend to install and configure Proxy Controllers after configuration. Oracle Enterprise Manager Ops Center cannot function without at least one Proxy Controller.
Configuring an Enterprise Controller manually: This deployment configures the Enterprise Controller according to a configuration profile that you create. You can enable the co-located Proxy Controller using manual configuration, but other Proxy Controllers must be configured separately.
Note:
You should not install a Proxy Controller in an environment where there is a web proxy which requires authentication between the Enterprise Controller and the Proxy Controller. Many OS update functions are not usable for systems managed by such a Proxy Controller.
Note:
Oracle Enterprise Manager Ops Center has self-signed certificates that it uses for authentication between its components. If you prefer to use certificates authenticated by a Certificate Authority, perform the Substitute Certificates procedure before you install any Proxy Controllers.
A simple deployment configures the co-located Proxy Controller on the Enterprise Controller system.
Before you begin:
If you intend to operate in Disconnected Mode, acquire a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well.
Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip
on an Internet-facing system.
Unzip the bundle.
Run the harvester
script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:
# ./harvester --user <MOS user name> --password-file <password file location> --kb-only Directory /export/home/public not found. This directory will be created. Setting up local directory structure at: /export/home/public Initialization: Downloading channels.xml Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session. Distributions: Identifying and Downloading the Notifications and Seeker scripts Creating tarball... Tarball successfully created at /discon/standalone-0127.tar.gz Start time: Tue Jan 17 05:08:00 MST 2012 Completion time: Tue Jan 17 05:08:01 MST 2012 <output omitted>
Copy the resulting bundle back to the Enterprise Controller system.
If you intend to operate in Connected Mode, go to My Oracle Support page and log in to verify that you have a valid set of My Oracle Support (MOS) credentials. See Related Resources for Enterprise Controller High Availability for the link to log in.
To configure an Enterprise Controller with a Simple Deployment:
In a browser, navigate to https://<Enterprise Controller>:9443/emoc
.
The Login page is displayed.
Enter the system's root user name and password and select Ops Center as the source, then click Log In.
If the configuration detects any prerequisites that are not met, the Prerequisite Checklist page is displayed. If the Prerequisite Checklist is not displayed, skip this step.
If the Prerequisite Checklist is displayed, review the prerequisites. If necessary, cancel the configuration and make changes to the system as suggested by the checklist. Click Next.
The Enterprise Controller Setup page is displayed.
Enter the Enterprise Controller setup information, then click Next. Configuration information includes:
Enterprise Controller name: The Enterprise Controller name that is displayed in the masthead.
Administrative User: The Administrative User is given the Enterprise Controller Admin and All Assets Admin roles. Until other users are added, the Administrative User is the only user recognized by Oracle Enterprise Manager Ops Center. Select Set the Currently Logged In User as Administrative User to make the current user the Administrative User, or select Set the Following User as the Administrative User and enter a user name and password to make that user the Administrative User.
Proxy Controller Setup: This option sets the initial Proxy Controller configuration. Select Co-located Proxy.
A popup is displayed indicating that the local Proxy Controller is being configured. Click Close to close the popup, then click Next.
The Proxy Controller Status page is displayed.
View the status of the configured Proxy Controller and verify that the Proxy Controller you installed and configured is online.
(Optional) Click Check, then enter a host name or IP address. The connectivity and status of the specified host is checked.
Click Next.
The Connection Mode page is displayed.
Select a connection mode option:
Connected Mode: Oracle Enterprise Manager Ops Center downloads patches from Oracle and other vendors. The Enterprise Controller must be able to access the Internet, either directly or through an HTTP Proxy, to use Connected Mode.
If you select Connected Mode, you can also enable or disable Auto Service Request (ASR).
Disconnected Mode: Oracle Enterprise Manager Ops Center operates autonomously, and patches must be manually downloaded and supplied to the Enterprise Controller.
Click Next.
If you selected Connected Mode, the Connecting to My Oracle Support page is displayed. Enter your My Oracle Support (MOS) user name and password. You must have a valid MOS Account. If the Enterprise Controller requires an HTTP Proxy to reach the Internet, check Use HTTP Proxy and enter the HTTP Proxy information:
Server: The HTTP Proxy server.
Port: The port used to access the HTTP Proxy server.
(Optional) Authorized user name: The authorized user name is required if the HTTP Proxy can only be accessed by an authorized user.
(Optional) Password: The password is required if the HTTP Proxy can only be accessed by an authorized user.
Click Next.
If you enabled Auto Service Request (ASR), the Auto Service Request Contact page is displayed. Enter the default contact information for ASR:
First Name: The first name of the ASR contact.
Last Name: The last name of the ASR contact.
Phone: The phone number for the ASR contact.
Email: The email address for the ASR contact.
Country: The country where the assets are located.
Address 1: The address where the assets are located.
(Optional) Address 2: The second line of the address where the assets are located.
City: The city where the assets are located.
State/Province: The state or province where the assets are located.
(Optional) Zip/Postal Code: The zip or postal code where the assets are located.
Time Zone: The time zone where the assets are located.
Click Next.
The Create Software Libraries page is displayed. Oracle Enterprise Manager Ops Center either creates the libraries or connects to NAS libraries in the locations that you specify. If you are using High Availability for the Enterprise Controller, these libraries must not be created locally.
Enter a location for each library:
Software Library: This library stores firmware images, ISOs, and flash archives.
Linux and Oracle Solaris 8-10 Library: This library stores Linux and Oracle Solaris 8-10 OS images.
Click Next.
If you are configuring in Disconnected Mode, the Linux/Oracle Solaris 8-10 Software Bundle page is displayed. Enter the location of the update bundle that you downloaded before beginning this procedure.
Click Next.
The Configure DHCP for OS Provisioning page is displayed. Some OS provisioning, particularly on older hardware, requires DHCP to be configured on the Proxy Controller.
To configure DHCP for a Proxy Controller, select a Proxy Controller, then select a DHCP type from the drop-down list. Add one or more interfaces to the list of selected interfaces, then click Configure DHCP.
The Summary page is displayed.
Click Finish.
Oracle Enterprise Manager Ops Center is configured, and you are logged in to the UI.
An Advanced Deployment installs and configures one or more Proxy Controllers on remote systems.
Before you begin:
If you intend to operate in Disconnected Mode, acquire a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well.
Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip
on an Internet-facing system.
Unzip the bundle.
Run the harvester
script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:
# ./harvester --user <MOS user name> --password-file <password file location> --kb-only Directory /export/home/public not found. This directory will be created. Setting up local directory structure at: /export/home/public Initialization: Downloading channels.xml Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session. Distributions: Identifying and Downloading the Notifications and Seeker scripts Creating tarball... Tarball successfully created at /discon/standalone-0127.tar.gz Start time: Tue Jan 17 05:08:00 MST 2012 Completion time: Tue Jan 17 05:08:01 MST 2012 <output omitted>
Copy the resulting bundle back to the Enterprise Controller system.
If you intend to operate in Connected Mode, go to My Oracle Support page and log in to verify that you have a valid set of My Oracle Support (MOS) credentials. See Related Resources for Enterprise Controller High Availability for the link to log in.
To configure an Enterprise Controller with an Advanced Deployment:
In a browser, navigate to https://<Enterprise Controller>:9443/emoc
.
The Login page is displayed.
Enter the system's root user name and password and select Ops Center as the source, then click Log In.
If the configuration detects any prerequisites that are not met, the Prerequisite Checklist page is displayed. If the Prerequisite Checklist is not displayed, skip this step.
If the Prerequisite Checklist is displayed, review the prerequisites. If necessary, cancel the configuration and make changes to the system as suggested by the checklist. Click Next.
The Enterprise Controller Setup page is displayed.
Enter the Enterprise Controller setup information, then click Next. Configuration information includes:
Enterprise Controller name: The Enterprise Controller name that is displayed in the masthead.
Administrative User: The Administrative User is given the Enterprise Controller Admin and All Assets Admin roles. Until other users are added, the Administrative User is the only user recognized by Oracle Enterprise Manager Ops Center. Select Set the Currently Logged In User as Administrative User to make the current user the Administrative User, or select Set the Following User as the Administrative User and enter a user name and password to make that user the Administrative User.
Proxy Controller Setup: This option sets the initial Proxy Controller configuration. Select Remote Proxies.
The Remote Proxy Controllers page is displayed. Enter credentials for one or more remote systems, then click Next. Proxy Controllers are installed and configured on these systems.
Hostname or IP address: The host names or IP addresses of the Proxy Controller systems.
SSH User name: The SSH user name to be used to log into the systems. If root SSH access is allowed on the target system, enter the root user name and password in the SSH User and SSH Password fields.
SSH Password: The password associated with the SSH user name.
(Optional) Privileged User name: The privileged user name to be used to log in. If root SSH access is not allowed on the target system, enter the login user name and password in the SSH User and SSH Password fields, then enter the root user name and password in the Privileged Role and Role Password fields.
(Optional) Privileged Password: The password associated with the Privileged user name. Click Add to add fields for another Proxy Controller, then enter credentials for it.
The Proxy Controller Status page is displayed.
View the status of the configured Proxy Controllers and verify that the Proxy Controllers you installed and configured are online.
(Optional) Click Check, then enter a host name or IP address. The connectivity and status of the specified host is checked.
Click Next.
The Connection Mode page is displayed.
Select a connection mode option:
Connected Mode: Oracle Enterprise Manager Ops Center downloads patches from Oracle and other vendors. The Enterprise Controller must be able to access the Internet, either directly or through an HTTP Proxy, to use Connected Mode.
If you select Connected Mode, you can also enable or disable Auto Service Request (ASR).
Disconnected Mode: Oracle Enterprise Manager Ops Center operates autonomously, and patches must be manually downloaded and supplied to the Enterprise Controller.
Click Next.
If you selected Connected Mode, the Connecting to My Oracle Support page is displayed. Enter your My Oracle Support (MOS) user name and password. You must have a valid MOS Account. If the Enterprise Controller requires an HTTP Proxy to reach the Internet, check Use HTTP Proxy and enter the HTTP Proxy information:
Server: The HTTP Proxy server.
Port: The port used to access the HTTP Proxy server.
(Optional) Authorized user name: The authorized user name is required if the HTTP Proxy can only be accessed by an authorized user.
(Optional) Password: The password is required if the HTTP Proxy can only be accessed by an authorized user.
Click Next.
If you enabled Auto Service Request (ASR), the Auto Service Request Contact page is displayed. Enter the default contact information for ASRs:
First Name: The first name of the ASR contact.
Last Name: The last name of the ASR contact.
Phone: The phone number for the ASR contact.
Email: The email address for the ASR contact.
Country: The country where the assets are located.
Address 1: The address where the assets are located.
(Optional) Address 2: The second line of the address where the assets are located.
City: The city where the assets are located.
State/Province: The state or province where the assets are located.
(Optional) Zip/Postal Code: The zip or postal code where the assets are located.
Time Zone: The time zone where the assets are located.
Click Next.
The Create Software Libraries page is displayed. Oracle Enterprise Manager Ops Center either creates the libraries or connects to NAS libraries in the locations that you specify. If you are using High Availability for the Enterprise Controller, these libraries must not be created locally.
Enter a location for each library:
Software Library: This library stores firmware images, ISOs, and flash archives.
Linux and Oracle Solaris 8-10 Library: This library stores Linux and Oracle Solaris 8-10 OS images.
Click Next.
If you are configuring in Disconnected Mode, the Linux/Oracle Solaris 8-10 Software Bundle page is displayed. Enter the location of the update bundle that you downloaded before beginning this procedure.
Click Next.
The Configure DHCP for OS Provisioning page is displayed. Some OS provisioning, particularly on older hardware, requires DHCP to be configured on the Proxy Controller.
To configure DHCP for a Proxy Controller, select a Proxy Controller, then select a DHCP type from the drop-down list. Add one or more interfaces to the list of selected interfaces, then click Configure DHCP.
The Summary page is displayed.
Click Finish.
Oracle Enterprise Manager Ops Center is configured, and you are logged in to the UI.
You can configure the Enterprise Controller without installing or configuring a Proxy Controller. You can either provision one or more Proxy Controllers through the user interface or manually install and configure one or more Proxy Controllers. You must install and configure at least one Proxy Controller before using the software to manage assets.
Before you begin:
If you intend to operate in Disconnected Mode, acquire a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well.
Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip
on an Internet-facing system.
Unzip the bundle.
Run the harvester
script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:
# ./harvester --user <MOS user name> --password-file <password file location> --kb-only Directory /export/home/public not found. This directory will be created. Setting up local directory structure at: /export/home/public Initialization: Downloading channels.xml Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session. Distributions: Identifying and Downloading the Notifications and Seeker scripts Creating tarball... Tarball successfully created at /discon/standalone-0127.tar.gz Start time: Tue Jan 17 05:08:00 MST 2012 Completion time: Tue Jan 17 05:08:01 MST 2012 <output omitted>
Copy the resulting bundle back to the Enterprise Controller system.
If you intend to operate in Connected Mode, go to My Oracle Support page and log in to verify that you have a valid set of My Oracle Support (MOS) credentials. See Related Resources for Enterprise Controller High Availability for the link to log in.
To configure an Enterprise Controller without installing a Proxy Controller:
In a browser, navigate to https://<Enterprise Controller>:9443/emoc
.
The Login page is displayed.
Enter the system's root user name and password and select Ops Center as the source, then click Log In.
If the configuration detects any prerequisites that are not met, the Prerequisite Checklist page is displayed. If the Prerequisite Checklist is not displayed, skip this step.
If the Prerequisite Checklist is displayed, review the prerequisites. If necessary, cancel the configuration and make changes to the system as suggested by the checklist. Click Next.
The Enterprise Controller Setup page is displayed.
Enter the Enterprise Controller setup information, then click Next. Configuration information includes:
Enterprise Controller name: The Enterprise Controller name that is displayed in the masthead.
Administrative User: The Administrative User is given the Enterprise Controller Admin and All Assets Admin roles. Until other users are added, the Administrative User is the only user recognized by Oracle Enterprise Manager Ops Center. Select Set the Currently Logged In User as Administrative User to make the current user the Administrative User, or select Set the Following User as the Administrative User and enter a user name and password to make that user the Administrative User.
Proxy Controller Setup: This option sets the initial Proxy Controller configuration. Select Manual Setup.
The Connection Mode page is displayed.
Select a connection mode option:
Connected Mode: Oracle Enterprise Manager Ops Center downloads patches from Oracle and other vendors. The Enterprise Controller must be able to access the Internet, either directly or through an HTTP Proxy, to use Connected Mode.
If you select Connected Mode, you can also enable or disable Auto Service Request (ASR).
Disconnected Mode: Oracle Enterprise Manager Ops Center operates autonomously, and patches must be manually downloaded and supplied to the Enterprise Controller.
Click Next.
If you selected Connected Mode, the Connecting to My Oracle Support page is displayed. Enter your My Oracle Support (MOS) user name and password. You must have a valid MOS Account. If the Enterprise Controller requires an HTTP Proxy to reach the Internet, check Use HTTP Proxy and enter the HTTP Proxy information:
Server: The HTTP Proxy server.
Port: The port used to access the HTTP Proxy server.
(Optional) Authorized user name: The authorized user name is required if the HTTP Proxy can only be accessed by an authorized user.
(Optional) Password: The password is required if the HTTP Proxy can only be accessed by an authorized user.
Click Next.
If you enabled Auto Service Request (ASR), the Auto Service Request Contact page is displayed. Enter the default contact information for ASRs:
First Name: The first name of the ASR contact.
Last Name: The last name of the ASR contact.
Phone: The phone number for the ASR contact.
Email: The email address for the ASR contact.
Country: The country where the assets are located.
Address 1: The address where the assets are located.
(Optional) Address 2: The second line of the address where the assets are located.
City: The city where the assets are located.
State/Province: The state or province where the assets are located.
(Optional) Zip/Postal Code: The zip or postal code where the assets are located.
Time Zone: The time zone where the assets are located.
Click Next.
The Create Software Libraries page is displayed. Oracle Enterprise Manager Ops Center either creates the libraries or connects to NAS libraries in the locations that you specify. If you are using High Availability for the Enterprise Controller, these libraries must not be created locally.
Enter a location for each library:
Software Library: This library stores firmware images, ISOs, and flash archives.
Linux and Oracle Solaris 8-10 Library: This library stores Linux and Oracle Solaris 8-10 OS images.
Click Next.
If you are configuring in Disconnected Mode, the Linux/Oracle Solaris 8-10 Software Bundle page is displayed. Enter the location of the update bundle that you downloaded before beginning this procedure.
Click Next.
The Configure DHCP for OS Provisioning page is displayed. Some OS provisioning, particularly on older hardware, requires DHCP to be configured on the Proxy Controller.
To configure DHCP for a Proxy Controller, select a Proxy Controller, then select a DHCP type from the drop-down list. Add one or more interfaces to the list of selected interfaces, then click Configure DHCP.
The Summary page is displayed.
Click Finish.
Oracle Enterprise Manager Ops Center is configured, and you are logged in to the UI.
You can configure the Enterprise Controller using a configuration file.
You must specify the configuration parameters, including MOS credentials, ASR status, co-located Proxy Controller activation, and HTTP proxy settings.
Note:
The manual configuration process does not configure libraries. If you configure your Enterprise Controller manually, you must configure libraries through the UI.
Before you begin:
If you intend to operate in Disconnected Mode, acquire a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well.
Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip
on an Internet-facing system.
Unzip the bundle.
Run the harvester
script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:
# ./harvester --user <MOS user name> --password-file <password file location> --kb-only Directory /export/home/public not found. This directory will be created. Setting up local directory structure at: /export/home/public Initialization: Downloading channels.xml Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session. Distributions: Identifying and Downloading the Notifications and Seeker scripts Creating tarball... Tarball successfully created at /discon/standalone-0127.tar.gz Start time: Tue Jan 17 05:08:00 MST 2012 Completion time: Tue Jan 17 05:08:01 MST 2012 <output omitted>
Copy the resulting bundle back to the Enterprise Controller system.
If you intend to operate in Connected Mode, go to My Oracle Support page and log in to verify that you have a valid set of My Oracle Support (MOS) credentials. See Related Resources for Enterprise Controller High Availability for the link to log in.
To configure an Enterprise Controller manually:
As root, log on to the Enterprise Controller system.
Change to the directory used for the installation and create a configuration file. For example:
# cd /var/tmp/OC # touch EC-config
Edit the configuration file to contain the parameters of your environment. The allowed parameters are:
username=<user name>
: This user is configured as the Oracle Enterprise Manager Ops Center administrative user. The user must be present on the local file system.
update.username=<MOS user name>
: This MOS user name is used to download update content in connected mode.
update.password=<password>
: The password for the update MOS user. This parameter is required if the update.username
parameter is set.
register.username=<MOS user name>
: This MOS user name is used to register the Enterprise Controller with Oracle.
register.password=<password>
: The password for the registration MOS user. This parameter is required if the register.username
parameter is set.
mos.username=<MOS user name>
: This MOS user name is used to connect to Oracle, download product updates and other content, and enable service request creation.
mos.password=<password>
: The password for the primary MOS user. This parameter is required if the mos.username
parameter is set.
asr.mode=<enabled | disabled>
: Specifies whether Auto Service Request (ASR) should be enabled or disabled. ASR is disabled by default.
httpproxy.hostname=<host name>
: If your environment requires an HTTP proxy to reach the internet, enter the HTTP proxy host name.
httpproxy.port=<port>
: If your environment requires an HTTP proxy to reach the internet, enter the HTTP proxy port number.
httpproxy.username=<user name>
: If your environment requires an HTTP proxy to reach the internet, and the HTTP proxy requires authentication, enter a user name for the HTTP proxy.
httpproxy.password=<password>
: The password for the HTTP proxy user. This parameter is required if the httpproxy.username
parameter is set.
local.controlproxy=<enabled | disabled>
: This setting enables or disables the co-located Proxy Controller on the Enterprise Controller system.
local.controlproxy.ip=<IP>
: This IP address is used by the co-located Proxy Controller if it is enabled. This parameter is required if the local.controlproxy
parameter is set to enabled.
local.controlproxy.wait=<true | false>
: This variable specifies whether the configuration process should wait until the co-located Proxy Controller is enabled before completing.
Here is an example configuration file:
# Configuration file username=root update.username=user@company.com update.password=companypass register.username=user@company.com register.password=companypass mos.username=user@company.com mos.password=companypass asr.mode=enabled httpproxy.hostname=http.proxy.company.com httpproxy.port=80 local.controlproxy=enabled local.controlproxy.ip=10.10.24.28 local.controlproxy.wait=true
Run the /opt/sun/xvmoc/bin/ecadm
command with the configure
subcommand and the --config <configuration file>
option. For example:
./ecadm configure --config /var/tmp/EC-config ecadm: --- Enterprise Controller registered #
The Enterprise Controller is configured. If you plan to use remote Proxy Controllers, you can install and configure them manually or through the UI.
Delete the configuration file. For example:
# cd /var/tmp/OC # rm EC-config
You can view the Oracle Enterprise Manager Ops Center documents for additional information.
For more information, see these Oracle resources:
For information on supported database versions and database options, see Oracle Enterprise Manager Ops Center Certified Systems Matrix
For information on preparing the Oracle 12CDB customer-managed database for Oracle Enterprise Manager Ops Center installation, see Oracle Enterprise Manager Ops Center Administration
For information about site administration, to convert to Enterprise Controller High Availability, and for High Availability management, see the High Availability chapter of Oracle Enterprise Manager Ops Center Administration
For Oracle Clusterware installation documentation, go to http://www.oracle.com/pls/db112/portal.portal_db?selected=16
For more information on Oracle RAC, see Configuring Storage for Oracle Grid Infrastructure for a Cluster and Oracle RAC chapter of Oracle Grid Infrastructure Installation Guide
For information on certificates authenticated by a Certificate Authority, see Oracle Enterprise Manager Ops Center Security
For information on downloading the KB bundle while operating in disconnected mode, see Oracle Enterprise Manager Ops Center Use Disconnected Mode or Oracle Enterprise Manager Ops Center Administration
For My Oracle Support (MOS) page, go to https://support.oracle.com/
For information on installing Agent Controllers and discovering and managing assets and for Configuring Storage, see Oracle Enterprise Manager Ops Center Configuration Reference
The Oracle Enterprise Manager Ops Center Documentation Library is located at http://docs.oracle.com/cd/E59957_01/index.htm
For more information on product administration, see http://docs.oracle.com/cd/E59957_01/nav/administer.htm
For end-to-end examples, see the Deploy How To library at http://docs.oracle.com/cd/E59957_01/nav/deploy.htm
and the Operate How To library at http://docs.oracle.com/cd/E59957_01/nav/operate.htm
For more information on Enterprise Manager Ops Center, see the Ops Center blog at https://blogs.oracle.com/opscenter/