The Initial Setup Console is a GUI-rich console within the Enterprise Manager Cloud Control Console that can be used as a starting point to set up Enterprise Manager Cloud Control, track the progress of each setup task you perform, and identify tasks that are still pending. You can perform all the steps at the same time, or do some now and the rest later.
The setup steps listed in the Initial Setup Console are also available as separate menu options, but Oracle recommends that you perform steps using the console as it provides an overall readiness status in a single view.
Note:
Only a super administrator can access the Initial Setup Console.
This chapter describes how you can use the Initial Setup Console to perform all the setup tasks. In particular, this chapter covers the following:
Configuring Oracle Software Library Using the Initial Setup Console to Store Software Entities
Configuring Proxies for OMS-to-Management Agent Communication
Configuring Proxies Using the Initial Setup Console for OMS-My Oracle Support Communication
Adding Additional Oracle Management Service Using the Initial Setup Console
Configuring Outgoing Mail Servers (SMTP Servers) Using the Initial Setup Console
Registering My Oracle Support Credentials Using the Initial Setup Console
Oracle Software Library (Software Library) is a repository that stores software entities such as software patches, virtual appliance images, reference gold images, application software, and their associated directive scripts.
You can configure the Software Library while or after installing Enterprise Manager Cloud Control.
If you configured the Software Library while installing Enterprise Manager Cloud Control, then this particular setup task in the Initial Setup Console appears as complete. In this case, you can move over to the next setup task.
If you did not configure the Software Library while installing Enterprise Manager Cloud Control, then this setup task in the Initial Setup Console appears as incomplete. In this case, you must follow the instructions outlined in this topic to complete the task.
If you do not want to configure the Software Library from the Initial Setup Console, then you can configure it later from the Software Library Administration Console, which is available within the Enterprise Manager Cloud Control Console.
For instructions to configure it from the Software Library Administration Console, see Oracle Enterprise Manager Cloud Control Administrator's Guide.
If you upgraded from an earlier release of Enterprise Manager Cloud Control, then this setup task in the Initial Setup Console always appears as complete because during upgrade, the Software Library location from the earlier is automatically is carried over.
Software Library supports two types of storage locations, mainly OMS Shared File System location and OMS Agent File System location. Oracle strongly recommends that you configure the OMS Shared File System location. To understand these storage locations, see Oracle Enterprise Manager Cloud Control Administrator's Guide.
To configure an OMS Shared File System location for the Software Library, using the Initial Setup Console, follow these steps:
You can secure the communication between Oracle Management Service (OMS) and Oracle Management Agents (Management Agents) by configuring a proxy. You can configure one proxy for all Management Agents, one proxy for a set of Management Agents and none for the rest, or different proxies for different sets of Management Agents.
In addition, you can configure two or more proxies as redundant proxies to support high availability of the proxies configured for OMS and Management Agent communication. Under such circumstances, by default, the proxy that is up and running is selected for communication, regardless of the status of the other proxies. Before starting to communicate if a proxy is found to be inactive or down, then an alternate proxy configured for that Management Agent is selected. However, note that after the communication begins through a particular proxy, if that proxy turns inactive or shuts down, then no fallback mechanism is currently available to select an alternate proxy that is up and running.
Note:
NTLM-based Microsoft proxies are not supported. To enable access through such proxies, add all the available agent hosts to the Unauthenticated Sites Properties of the NTLM-based Microsoft proxy.
Local addresses of each OMS automatically bypass the proxy.
If you have already configured a proxy, then this setup task appears as if it is complete.
To configure a proxy using the Initial Setup Console for OMS-Management Agent communication, follow these steps:
Oracle Management Service (OMS) uses the Internet connectivity on its host to connect to My Oracle Support periodically to download patches, patch sets, patch recommendations, and Automated Release Updates (ARU) seed data. By default, Enterprise Manager Cloud Control assumes that there is no proxy server configured between the OMS and My Oracle Support. However, to secure the communication, you can add a proxy server between the two entities, and then register it as a proxy target in Enterprise Manager Cloud Control.
Note:
If you have already configured a proxy, then this setup task appears as if it is complete.
To configure a proxy using the Initial Setup Console for OMS-My Oracle Support communication, follow these steps:
When you install Enterprise Manager Cloud Control, by default, the installer installs one Oracle Management Service along with one Oracle Management Agent. While this default configuration suits smaller environments, typically in larger production environments, you might require additional OMS instances to help reduce the load on a single Oracle Management Service, improve the efficiency of the data flow, and offer high availability of your Enterprise Manager system.
Note:
If you have already added an additional OMS, then this setup task appears as if it is complete.
To add an additional Oracle Management Service using the Initial Setup Console, follow these steps:
Notifications keep you informed when specific incidents, events, or problems arise, and thereby enable you to take corrective or preventive actions to circumvent the reported issue. Enterprise Manager uses different mechanisms for sending these notifications, including email, SNMP traps, or running custom scripts, or all three. Before Enterprise Manager Cloud Control can send e-mail notifications, you must set up the outgoing mail servers (SMTP servers).
Note:
If you have already configured the SMTP servers, then this setup task appears as if it is complete.
To configure outgoing mail servers so that Enterprise Manager can send e-mail notifications, follow these steps:
My Oracle Support connectivity enables you to view service request information, obtain patch recommendations, and download plug-ins and other entities to the Software Library, all from within the Enterprise Manager Cloud Control Console. To automatically sign in to My Oracle Support from within the Enterprise Manager Cloud Control Console, you must register the My Oracle Support credentials with Enterprise Manager Cloud Control.
Note:
If you have already registered the My Oracle Support credentials, then this setup task appears as if it is complete.
To register the My Oracle Support Credentials using the Initial Setup Console, follow these steps:
Users are administrators who are authorized to log in and use Enterprise Manager Cloud Control. Users belong to one or the other role defined in Enterprise Manager, and perform only those operations to which they are entitled.
By default, users can be either Super Administrators who have full access privileges to all the targets, Repository Owners who manage Oracle Management Repository, or Regular Administrators who normally use Enterprise Manager Cloud Control.
Note:
If you have already created a set of users, then this setup task appears as if it is complete.
To create administrators using the Initial Setup Console, follow these steps:
Roles are a collection of Enterprise Manager resource privileges, or target privileges, or both, which are granted to administrators who use Enterprise Manager Cloud Control. Roles can be based upon geographic location (for example, a role for Canadian administrators to manage Canadian systems), line of business (for example, a role for administrators of the human resource systems or the sales systems), or any other model. After you have created administrators, the next step is to create roles and assign administrators to those specific roles.
Note:
If you have already created a set of roles, then this setup task appears as if it is complete.
To create roles using the Initial Setup Console, follow these steps: