Before You Begin

This tutorial guides you through launching an Oracle Enterprise Manager instance in OCI Marketplace. The time to complete this setup is approximately 1 hour.

Overview

Oracle Enterprise Manager is a complete, integrated, and business-driven enterprise cloud management solution. Oracle Enterprise Manager has built-in management capabilities of the Oracle stack for traditional and cloud environments that enables you to monitor and manage the complete Oracle IT infrastructure from a single console.

Key Capabilities of Oracle Enterprise Manager

• A complete cloud lifecycle management solution enabling you to quickly set up, manage, and support enterprise clouds and traditional Oracle IT environments from applications to disk.
• Maximum return on IT management investment through the best solutions for intelligent management of the Oracle stack and engineered systems with real-time integration of Oracle's knowledge base with each customer environment.
• Best service levels for traditional and cloud applications through business-driven application management.

On OCI Marketplace, Oracle Enterprise Manager is configured with a single Instance repository, deployed in a single VM instance, and the data is persisted in the block storage volume:

What is new in this package

This release provides the ability to deploy Oracle Enterprise Manager in sizes Small, Medium and Large based on selected VM shapes.

This Oracle Enterprise Manager installation is preconfigured with the following:

• Uses the latest OCI linux image: OL 7.7 (with CVE fixes)
• Updated with the latest January 2020 Bundle Patch - OMS & Agent Platform, includes OMS side plugin updates and agent side plugin updates for DB & SI
• Updated middleware tier with 12.1.3/October 2019 PSU and patched with the critical de-serialization vulnerability fix (CVE-2019-2729, part of Patch 29633448)
• Oracle Management Repository runs on Oracle Database 19.5 (October PSU)
• Latest Enterprise Manager certified JDK update 241
• Most recent diag kit update to version: 19.09.30

Available Plug-ins for 13.3

The following is a list of all available plug-ins for Oracle Entreprise Manager on OCI 13.3 release. Some plug-ins are available by default within OMS, these are marked as On Management Server. Of the available plug-ins, some are downloaded but not deployed within OMS until you decide to enable them; these plug-ins are marked as Latest Downloaded. Plug-ins available for download, but not yet downloaded or deployed are marked as Latest Available.

• Enterprise Manager for Zero Data Loss Recovery Appliance (13.3.2.0.0)
• Enterprise Manager for Oracle Database (13.3.2.0.0)
• Enterprise Manager for Big Data Appliance (13.3.1.0.0)
• Enterprise Manager for Oracle Virtualization (13.3.1.0.0)
• Enterprise Manager for Cloud Services Management (13.3.2.0.0)
• Enterprise Manager for Oracle Consolidation Planning and Chargeback
• Enterprise Manager for Oracle Fusion Middleware (13.3.1.0.0)
• Enterprise Manager for Oracle Cloud (13.3.2.0.0)
• Enterprise Manager for Oracle Siebel (13.3.1.0.0)
• Enterprise Manager for Oracle Exadata (13.3.2.0.0)
• Enterprise Manager for Storage Management (13.3.1.0.0)
• Enterprise Manager for Oracle Cloud Framework (13.3.2.0.0)
• Enterprise Manager for Systems Infrastructure (13.3.2.0.0)
• Enterprise Manager for Oracle Virtual Infrastructure (13.3.2.0.0)
• Enterprise Manager for Oracle Fusion Applications (13.3.1.0.0)
• Enterprise Manager for Oracle Audit Vault and Database Firewall (13.3.1.0.0)

Note: For this release plug-ins marked as (13.3.2.0.0) have been updated with the latest features and code improvements for this release.

For more information regarding the latest patch updates and plug-ins available for Oracle Entreprise Manager 13.3 on OCI, see: Enterprise Manager 13.3 Master Bundle Patch List.

Perform Prerequisites

Before deploying Oracle Enterprise Manager,  review the following information and perform all prerequisite tasks described below.

1. Review licensing requirements and ensure you have the appropriate licenses for the environment you are going to manage. The Oracle Enterprise Manager licensing information is available in the Enterprise Manager Licensing Information User Manual.
2. Ensure that your Oracle Cloud Infrastructure account service has limits for the shapes and block storage adequate for the Enterprise Manager sizing you wish to deploy: Small (400GB), Medium (600GB), Large (700GB).  For more information, see Oracle Cloud Compute Services.

   EM Installation Size	OCI Shape	OMS Parameters	Database Paramaters
   Small	VM.Standard2.1, VM.Standard2.2, VM.Standard2.4, VM.Standard2.8, VM.DenseIO2.8, VM.Standard2.16, VM.DenseIO2.16, VM.Standard.E2.1, VM.Standard.E2.2, VM.Standard.E2.4, VM.Standard.E2.8	OMS_HEAP_MAX=1740M OMS_PERMGEN_MAX=612M jbo.ampool.maxavailablesize=50 jbo.recyclethreshold=50	logfile=290M sga_target=3000000000 pga_aggregate_target=1000000000
   Medium	VM.Standard2.24, VM.DenseIO2.24	OMS_HEAP_MAX=4096M OMS_PERMGEN_MAX=768M jbo.ampool.maxavailablesize=100 jbo.recyclethreshold=100	logfile=580M sga_target=5000000000 pga_aggregate_target=1340000000
   Large	BM.Standard2.52, BM.DenseIO2.52, BM.Standard.E2.64	OMS_HEAP_MAX=8192M OMS_PERMGEN_MAX=1024M jbo.ampool.maxavailablesize=200 jbo.recyclethreshold=200	logfile=960M sga_target=8000000000 pga_aggregate_target=1600000000

3. Obtain the OCID of the Compartment where the Oracle Enterprise Manager VM Instance will be created.  This information will be used later in your setup.  For details on obtaining the OCID see Managing Compartments.
4. The remaining steps must be completed by an OCI Administrator.  Create a Dynamic Group to group all instances of the compartment and add the following rule:

   ALL {instance.compartment.id = '<compartment ocid>'}

   The following is an example of this rule:

   ALL {instance.compartment.id = 'ocid1.compartment.oc1.aaaaaaaa24qo6imwe3alhqqg44taorogkxxxkdp6jykuyixxxiuwxqxxy5q'}

   

   See Managing Dynamic Groups for further details.

5. Create a policy with the following rules within the root compartment of tenancy:

   Allow dynamic-group <your group> to manage instance-family in tenancy
   Allow dynamic-group <your group> to manage volume-family in tenancy

   

   See Managing policies for further details.

6. As a user with Oracle Cloud Administrator permissions, create a Virtual Cloud Network (VCN) with subnets.
   
   If using public subnets, you access your instance over the internet using its public IP address, so your route tables will direct traffic to an internet gateway. In this case, create your VCN with Public Subnet and Internet Gateway elements. See Creating Virtual Cloud Networks.
   
   NOTE: In this release for 13.3 deployments and up, the OCI deployment flow has a new default option Do not assign a public IP address. For public VCN's select Assign a public IP address.
   

   

   If using private subnets, you need to complete a few extra tasks:

   • Create a Service Gateway in your VCN. For information on creating service gateways see Access to Oracle Services: Service Gateway.
   • Create a routing table with a Route Rule that has the Target Type the Service Gateway created above.
   • Add the Egress rules on the Default security list with the service you just created. 

   For further information on VCN's, see VCNs and Subnets.

7. Update the default Security List of the VCN and add the following Stateful Ingress rules:

   Destination Port Range	Protocol Type	Service
   22	TCP	SSH
   7803	TCP	Console
   4903	TCP	Agent Upload
   7301	TCP	JVMD
   9851	TCP	BIP

   See security lists for further details.

8. Create the SSH public key that will be used to access the EM instance. See Creating a Key Pair for further details.

Deploy Enterprise Manager

1. Sign in to OCI and from the OCI Main Menu navigate to Marketplace. Search and click on Oracle Enterprise Manager 13.3.

   

2. Review the Oracle Enterprise Manager overview and click on Launch Instance.
3. Select the package version and compartment; accept the terms of use and click on Launch Instance.
4. On the next page specify the following:
   • Instance name: any name for your VM instance
   • Availability Domain
   • Choose an available VM shape that best suits your needs. The following is a list of minimum size recommended shapes to use in production:
     • VM.Standard 2.8, for small installations
     • VM.Standard 2.24, for medium installations
     • BM.Standard 2.52, for large installations
5. Choose the SSH key file you created earlier under prerequisites or paste the SSH keys.

   

6. Select the network compartment, virtual cloud network and subnet compartments you created earlier under prerequsites and then click Create.
7. The instance will be in Provisioning mode initially. Verify that the VM instance is created and its status shows as RUNNING.

   

   NOTE: The Oracle Enterprise Manager configuration within the newly created VM will take 30 minutes to complete.

8. Locate and copy the Public IP Address of your new instance from the Instance Details page.

   

9. Connect to your VM instance with the ssh key you created earlier. Use the following connection format:
   ssh –i <private ssh key file> opc@<EM VM public IP Address>.

   $ ssh –i ./id_rsa opc@<EM VM public ip address>

10. Switch to the oracle user:

    $ sudo su – oracle

11. Monitor the installation progress by looking at the real-time, streaming output of the installation log file:

    $ sudo -s
    $ tail –f /var/log/emgc_install.log

    If any errors are reported, see the Troubleshoot Oracle Enterprise Manager Deployment section.
12. To verify that the installation completed successfully, check the OMS status:

    $ /u01/app/em13c/middleware/bin/emctl status oms
    Oracle Enterprise Manager Cloud Control 13c Release 3
    Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. 
    WebTier is Up 
    Oracle Management Server is Up 
    JVMD Engine is Up 
    BI Publisher Server is Up 
    

    If, the OMS status shows errors, review the Troubleshoot Oracle Enterprise Manager Deployment section.
13. The password for the Enterprise Manager user sysman, EM Agent Registration Password, Fusion Middleware user weblogic and Node Manager are set initially to the value: welcome1
    Change the sysman password with the following command:

    $ /u01/app/em13c/middleware/bin/emctl config oms -change_repos_pwd

14. The complete details of this EM installation are available in the README.FIRST file.  Review them:

    $ cat /home/oracle/README.FIRST
    ...
    Public EM url: https://ip_address:7803/em
    Private EM url: https://ip_address:7803/em
    Ports used by this deployment at /u01/app/em13c/middleware/install/portlist.ini
    Database location: /u01/app/database/product
    Database name: emrep
    EM Middleware Home location: /u01/app/em13c/middleware
    EM Agent Home location: /u01/app/em13c/emagent/agent_13.3.0.0.0
    EM Diagnostic Kit (omsvfy): /u01/app/em13c/middleware/emdiag
    EM Diagnostic Kit (repvfy): /u01/app/em13c/middleware/emdiag_rep
    EM Diagnostic Kit (agtvfy): /u01/app/em13c/emagent/agent_13.3.0.0.0/emdiag
    ...
    To start all processes, as the user oracle, run the script /home/oracle/start_all.sh
    To stop all processes, as the user oracle, run the script /home/oracle/stop_all.sh
    

15. Login to the OEM Console by navigating to: https://<public ip address>:7803/em
    Alternatively, update the local host (located in /etc/hosts) name resolution file to have the following entry:

    <public ip address> emcc.marketplace.com emcc

    and access EM by navigating to: https://emcc.marketplace.com:7803/em.

Troubleshoot Oracle Enterprise Manager Deployment

Errors will be written to the log file /var/log/emgc_install.log. Examine the log file:

$ sudo -s
$ tail -100 /var/log/emgc_install.log                            

If you notice OCI Authentication issues, make sure the dynamic group and policies set properly. Verify all tasks mentioned in the Perform Prerequisites section. To rerun the script, examine first the output of the process status command to be sure no oracle processes are running:

$ ps –ef 

Then, rerun the configuration script:

$ cd /root/bootstrap
$ ./oms_firstboot_init.sh

Use Oracle Enterprise Manager

Oracle Enterprise Manager can be used to monitor and manage on-premises or cloud resources like database systems or Fusion Middleware targets. Monitoring can be done using local Cloud Control Agents.

For details on getting started with monitoring various targets, review the following resources:

• To install agents on your hosts, see Cloud Control Basic Installation Guide.
Before installing local Cloud Control Agents, the following entry needs to be made in /etc/hosts file of the host or VM instance where the target is running:

emcc.marketplace.com <private IP address of the EM VM>

• To discover targets, see Discovery.
• To setup monitoring see Monitoring and Managing Targets.
• To setup Oracle Cloud Infrastructure Email Delivery Service with SMTP see Configure SMTP Connection.

Want to Learn More?

• Oracle Enterprise Manager general information
  
• Oracle Enterprise Manager Documentation Library