General workflow for installing the software binaries of Enterprise Manager with plug-ins first, and then configuring the installation at a later point in graphical mode.

1. Installing the Enterprise Manager Software Only With Plug-ins in Graphical Mode
2. Running the Root Script
3. Evaluate Non-SYS User Creation
4. Apply Release Update
5. Configuring the Enterprise Manager Software Only in Graphical Mode
6. Performing Postconfiguration Tasks After Configuring the Enterprise Manager Software Only in Graphical Mode

This section explains how you can install only the software binaries of Enterprise Manager with Plug-ins at one point in graphical mode, and configure the installation at a later point.

To install Enterprise Manager for a production site, follow these steps:

1. Invoke the Enterprise Manager Installation Wizard.

   Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Creating Operating System Groups and Users for Enterprise Manager in the Oracle Enterprise Manager Basic Installation Guide.

   ./em24100_<platform>.bin [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For example, for Linux platform, run /u1/software/em/em24100_linux64.bin [-invPtrLoc <absolute_path_to_oraInst.loc>]

   Note:

   • To invoke the installation wizard on UNIX platforms, run em24100_<platform>.bin. To invoke on Microsoft Windows platforms, run setup_em24100_win64.exe.

   • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

     The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

     For example,

     ./em24100_linux64.bin -J-Djava.io.tmpdir=/u01/software/em24/stage/

   • Ensure that there are no white spaces in the name of the directory where you download and run the Enterprise Manager software from. For example, do not download and run the software from a directory titled EM Software because there is a white space between the two words of the directory name.

   • The INSTALL_SWONLY_WITH_PLUGINS parameter is not supported starting with Enterprise Manager 13c Release 5. If you execute the ./em24100_<platform>.bin script using the INSTALL_SWONLY_WITH_PLUGINS parameter, you will receive an invalid parameter error message since the parameter is no longer supported.

2. Click Next.

3. Select Installation Type.

   On the Installation Types screen, select Create a new Enterprise Manager system, then select Install software only with plug-ins

   

4. Click Next.

5. (Recommended) Install Software Updates.

   On the Software Updates screen, select Search for Updates, and then select one of the following options to apply the latest software updates:

   • Local Directory, if you do not have Internet connectivity on your host, and want to download the updates in offline mode and apply them while performing the installation.

   • My Oracle Support, if you have Internet connectivity on your host, and want to connect to My Oracle Support directly via the installer to download the updates in online mode and apply them while performing the installation.

   For more information on these options, and for instructions to download and apply the software updates using these options, see the Enterprise Manager Advanced Installation and Configuration Guide.

   Note:

   The Software Updates screen uses the built-in feature Auto Update to automatically download and deploy the latest recommended patches while installing or upgrading Enterprise Manager. This way, you do not have to keep a manual check on the patches released by Oracle. All patches required by the installer for successful installation and upgrade are automatically detected and downloaded from My Oracle Support, and applied during the installation or upgrade, thus reducing the known issues and potential failures. Oracle strongly recommends using this feature, and applying the software updates while the installation is in progress.

   Note:

   During installation, you will be prompted for the details of a database where Oracle Management Repository can be configured. If you plan to provide the details of a database that already has an Oracle Management Repository preconfigured using the database templates offered by Oracle, then the software updates selected on this screen cannot be automatically applied. In such a case, you must manually download and apply these software updates after the installation.

   Note:

   Despite providing the My Oracle Support credentials, if you are unable to download the software updates, then exit the installer, and invoke the installer again passing the -showProxy parameter in the following way:

   <Software_Location>/em24100_<platform>.bin SHOW_PROXY=true

6. Click Next.

   If Enterprise Manager is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).

   If Enterprise Manager is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:

   <system drive>\Program Files\Oracle\Inventory
   

7. Enter Oracle Inventory Details.

   On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.

   1. Enter the full path to a directory where the inventory files and directories can be placed.

      Note:

      • If this is the first Oracle product on the host, then the default central inventory location is <home directory>/oraInventory. However, if you already have some Oracle products on the host, then the central inventory location can be found in the oraInst.loc file. The oraInst.loc file is located in the /etc directory for Linux and AIX, and in the /var/opt/oracle directory for Solaris, HP-UX, and Tru64.

      • Ensure that you have read, write, and execute permissions on the default inventory directory. If you do not have the required permissions, then exit the installer, invoke the installer again with the INVENTORY_LOCATION parameter, and pass the absolute path to the alternative inventory location.

        For example,

        <Software_Location>/em24100_<platform>.bin INVENTORY_LOCATION=<absolute_path_to_inventory_directory>

        Alternatively, invoke the installer with the -invPtrLoc parameter, and pass the absolute path to the oraInst.loc file that contains the alternative inventory location.

        For example,

        <Software_Location>/em24100_<platform>.bin -invPtrLoc <absolute_path_to_oraInst.loc>

        However, note that these parameters are supported only on UNIX platforms, and not on Microsoft Windows platforms.

   2. Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.

8. Click Next.

9. Check Prerequisites.

   

   On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.

   The installation wizard runs the prerequisite checks automatically when you come to this screen. For example, it checks for the required operating system patches and operating system packages.

   The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

   If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

   Note:

   You can choose to ignore the checks with Warning status by clicking Ignore. However, all package requirements must be met or fixed before proceeding any further.

10. Click Next.

    Note:

    If a prerequisite check fails reporting a missing package, then make sure you install the required package, and click Rerun. The installation wizard validates the package name as well as the version, so make sure you install the packages of the minimum versions, see Package Requirements for Enterprise Manager in the Oracle Enterprise Manager Basic Installation Guide.

11. Enter Installation Details.

    

    On the Installation Details screen, do the following:

    1. Enter the Middleware home where you want to install the OMS and other core components. This is essentially the Oracle home.

       Note:

       • The Enterprise Manager Installation Wizard installs Oracle WebLogic Server 12c Release 2 (12.2.1.4.0) and JDK 1.8.0_431 by default in this middleware home directory you enter here. A preinstalled JDK or Oracle WebLogic Server is not supported from 13c Release 1 onwards.

       • Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms.

         For example, the middleware home path C:\Oracle\MW\EM containing only 15 characters is acceptable. However, C:\OracleSoftware\OracleMiddleware\OracleEnterpriseManager\OMS\newrelease\oms containing more than 25 characters is not acceptable for Microsoft Windows platforms.

    2. Enter the absolute path to the agent base directory, a location outside the middleware home where the Management Agent can be installed. For example, if the middleware home is /u01/software/em24/middleware, then you can specify the agent base directory as /u01/software/em24/agentbasedir.

       Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.

       Note:

       Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms.

       For example, the middleware home path C:\Oracle\MW\EM containing only 15 characters is acceptable. However, C:\OracleSoftware\OracleMiddleware\OracleEnterpriseManager\OMS\newrelease\oms containing more than 25 characters is not acceptable for Microsoft Windows platforms.

    3. Validate the name of the host where you want to configure the OMS.

       The host name appears as a fully qualified name, or as a virtual host name if your host is configured with virtual machine. If the installation wizard was invoked with a value for ORACLE_HOSTNAME, then this field is prepopulated with that name.

       Accept the default host name, or enter a fully qualified domain name that is registered in the DNS and is accessible from other network hosts, or enter an alias host name that is defined in the /etc/hosts file on all the OMS instances at this site.

       Note:

       The host name must resolve to the local host or virtual host because the host name is used for the local Oracle WebLogic Server as well as the Oracle Management Service. Do not provide a remote host or a load balancer virtual host in this field. Do not enter an IP address. Do not use underscores in the name. Short names are allowed, but you will see a warning, so Oracle recommends that you enter a fully qualified domain name instead.

12. Click Next.

13. Select Plug-Ins.

    On the Select Plug-Ins screen, select the optional plug-ins you want to install from the software kit (DVD, downloaded software) while installing the Enterprise Manager system.

    Plug-Ins are pluggable entities that offer special management capabilities customized to suit specific target types or solution areas.

    The pre-selected rows are mandatory plug-ins that will be installed by default. Select the optional ones you want to install.

    Note:

    If you select a deprecated plug-in that is supported only in the current release, but not in any of the future releases, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the deployment of such plug-ins.

    Note:

    During installation, if you want to install a plug-in that is not available in the software kit, then refer to the point about installing additional plug-ins in Section 4.4.1.1.1.

    For details, see Using Advanced Script Options While Configuring the Enterprise Manager Software Using the Install Software Only Method in Graphical Mode.

14. Click Next.

    Note:

    • If you are connecting to an Oracle RAC database, and if you have specified the virtual IP address of one of its nodes, then the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster. Update the connection string and click OK. If you want to test the connection, click Test Connection.

    • If your Oracle RAC database is configured with Single Client Access Name (SCAN) listener, then you can enter a connection string using the SCAN listener.

    • If you are connecting to an Oracle Database that is configured with CDB or PDB, then make sure you open the PDB before you provide the PDB details on this screen.

    • If you see an error stating that the connection to the database failed with ORA-01017 invalid user name/password, then follow these steps to resolve the issue:

      (1) Verify that SYS password provided is valid.

      (2) Verify that the database initialization parameter REMOTE_LOGIN_PASSWORDFILE is set to Shared or Exclusive.

      (3) Verify that password file with the file name orapw<SID> exists in the <ORACLE_HOME>/dbs directory of the database home. If it does not, create a password file using the ORAPWD command.

    • For information on all the database initialization parameters that are set, and all the prerequisite checks that are run, and for instructions to run the prerequisite checks manually if they fail, see Installing Oracle Enterprise Manager in the Oracle Enterprise Manager Basic Installation Guide.

15. Review and Install.

    

    On the Review screen, review the details you provided for the selected installation type.

    • If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

    • After you verify the details, if you are satisfied, click Install to begin the software only installation process.

16. Track the Progress.

    On the Install Progress Details screen, view the overall progress (in percentage) of the installation.

17. End the Installation.

    On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

18. Run Scripts.

    Once the software binaries are copied, you are prompted to run the allroot.sh script, and the oraInstRoot.sh script if this is the first Oracle product installation on the host. Open another window, log in as root, and manually run the scripts.

    If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script.

    The install software only with plug-ins has been completed. Now you can proceed with the next step, the configuration process.

(For UNIX Only) After you install the software binaries of Enterprise Manager, log in as a root user in a new terminal and run the following scripts:

• If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.

  For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:

  $HOME/oraInventory/oraInstRoot.sh

  Note:

  If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

  /usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh

• Run the allroot.sh script from the Oracle home of the OMS host:

  $<ORACLE_HOME>/allroot.sh

  Note:

  If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

  /usr/local/bin/sudo $<ORACLE_HOME>/allroot.sh

Since security is a growing concern, Oracle provides the option to perform the installation, configuration and patching of the OMS using a non-privileged administrator user, also known as non-SYS user.

You are prompted to make the selection of creating and performing the installation using SYS or non-SYS user during the Database User Details step from Configuring the Enterprise Manager Software Only in Graphical Mode.

If there's a Release Update available, Oracle recommends to apply the latest Release Update after installing the Enterprise Manager software binaries.

A Release Update (RU), previously known as Bundle Patch, is an official Oracle patch that can be applied on top of Enterprise Manager 24ai Release 1 main release on an Oracle Home using the omspatcher apply -bitonly command.

For more information about patching and the omspatcher utility, see Patching Oracle Management Service and the Repository in the Enterprise Manager Administrator's Guide.

1. Invoke the Enterprise Manager Installation Wizard

   Invoke the installation wizard in graphical mode. (On Unix, make sure you invoke the installation wizard as a user who belongs to the oinstall group you created. For information about creating operating system groups and users see, Creating Operating System Groups and Users for Enterprise Manager in the Oracle Enterprise Manager Basic Installation Guide.

   $<ORACLE_HOME>/sysman/install/ConfigureGC.sh [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For Microsoft Windows platforms, invoke ConfigureGC.bat script.

   Optional Parameter:

   • The -invPtrLoc parameter is supported only on UNIX platforms. Do not use it on Microsoft Windows platforms.

   For more information additional advanced options you can pass while invoking the ConfigureGC script, see Using Advanced Script Options While Configuring the Enterprise Manager Software Using the Install Software Only Method in Graphical Mode.

   Note:

   • While installing the software binaries as described in Installing the Enterprise Manager Software Only With Plug-ins in Graphical Mode, if you had passed the argument -invPtrLoc, then you need to pass the same argument in this step as well.

   • The only way to configure the software only installation is to run the ConfigureGC.sh (or ConfigureGC.bat on Microsoft Windows) script. DO NOT run the individual configuration assistants to configure a software only installation. If you want to run the individual configuration assistants to configure the installation for some reason, then contact Oracle Support.

   • If you have already configured a software only installation (the Oracle home) using the ConfigureGC.sh script (or ConfigureGC.bat on Microsoft Windows, then DO NOT try to reconfigure it—either using the script or using the individual configuration assistants.

   • If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.pl script from the Oracle home to rerun the Configuration Assistant in silent mode. For Microsoft Windows platforms, invoke runConfig.pl script.

     $<ORACLE_HOME>/oui/bin/runConfig.pl <absolute_path_to_Middleware_home>

     If the runConfig.pl script fails, then clean up your environment and redo the installation.

2. Select Installation Type

   On the Installation Types screen, select Create a new Enterprise Manager system.

   
   

   

   
   

3. Click Next.

4. Enter WebLogic Server Configuration Details

   

   On the WebLogic Server Configuration Details screen, enter the credentials for the WebLogic Server user account and the Node Manager user account, and validate the path to the Oracle Management Service instance base location. Ensure that the Oracle Management Service instance base location is outside the middleware home

   Note:

   • Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.

   • Ensure that the Oracle Management Service instance base location is outside the middleware home.

   By default, the WebLogic Domain name is GCDomain, and the Node Manager name is nodemanager. These are non-editable fields. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager.

   A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

   Note:

   On Microsoft Windows, a Node Manager service is NOT created. This is an expected behavior.

   By default, the Oracle Management Service instance base location is gc_inst, which is created outside the Middleware home for storing all configuration details related to the OMS.

5. Click Next.

6. Enter Database Connection Details

   

   On the Database Connection Details screen, do the following:

   1. Enter the Database connection details.

      Provide the following details of the existing certified database where the Management Repository needs to get created:

      • Database host name.
      • Port (Database listener port).
      • Service/SID (Database service id).
      • SYS Password (Password of the SYS database user).

      If you have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance.

      The installer uses this information to connect to the existing database for creating the SYSMAN schema and plug-in schemas. If you provide details of a database that already has a preconfigured Management Repository, then the installer only creates plug-in schemas.

      Note:

      • For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Enterprise Manager Basic Installation Guide.

      • If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN122140_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter on the Repository Configuration Details screen).

      • The PDB name will always be empdbrepos irrespective of the CDB name if the PDB is created with the above listed templates. However, if the CDB is created with <domain name> then the PDB will be empdbrepos.<domain name>. For more information see, Creating a Database Instance with Preconfigured Repository Using Database Templates in the Oracle Enterprise Manager Basic Installation Guide.

      • If you are providing the details of a pluggable database (PDB), then use the full service name instead of the alias. For example, pdb.example.com. If you are providing the details of a lone-pluggable database (Lone-PDB), then use the full service name. For example, pdb.example.com. If you are providing the details of a non-container database (Non-CDB), then use the SID.

      • To identify whether your database is a certified database listed in the certification matrix, access the certification matrix as described in Accessing the Enterprise Manager Certification Matrix in the Oracle Enterprise Manager Basic Installation Guide.

      • For information on all the database initialization parameters that are set, and all the prerequisite checks that are run, and for instructions to run the prerequisite checks manually if they fail, see Overview of the EM Prerequisite Kit in the Oracle Enterprise Manager Basic Installation Guide.

   2. Select the deployment size from the Deployment Size list to indicate the number of targets you plan to monitor, the number of Management Agents you plan to have, and the number of concurrent user sessions you plan to have.

      The prerequisite checks are run regardless of the selection you make, but the values to be set for the various parameters checked depend on the selection you make.

      For more information on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer to What Is a Deployment Size for Enterprise Manager in an Advanced Configuration?.

      Table 4-1 describes each deployment size.

      Table 4-1 Deployment Size

      Deployment Size	Targets Count	Management Agents Count	Concurrent User Session Count
      Small	Up to 999	Up to 99	Up to 10
      Medium	Between 1000 and 9999	Between 100 and 999	Between 10 and 24
      Large	10,000 or more	1000 or more	Between 25 and 50

   3. (Optional) Check the Select to provide Database SSL Configuration Details (one-way SSL) checkbox if the database is one-way SSL configured. The truststore details are required for one-way SSL configuration.

      Provide the database truststore file and password.

   4. (Optional) Check the Select to provide Database SSL Configuration Details (two-way SSL) checkbox if the database is two-way SSL configured. The keystore details are required for two-way SSL configuration.

      Provide the database keystore file and password.

      PKCS12 wallet file format is supported.

7. Click Next.

   Note:

   If the database you are connecting to is a database instance created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure the deployment size you select on this screen matches with the deployment size you selected in the Oracle Database Configuration Assistant (DBCA) while creating the database instance.

   If you want to select a deployment size different from the deployment size you had selected while creating the database instance using DBCA, then do one of the following:

   • Select the deployment size of your choice on this screen, and click Next. When you see errors, fix the parameters in the database, then return to this screen to continue with the installation. To automatically fix the parameters using Oracle-supplied SQL scripts, see the Enterprise Manager Basic Installation Guide.

   • Minimize the installer, create another database instance with a template for the desired deployment size, then return to this screen and select the matching deployment size. For instructions, see the Enterprise Manager Basic Installation Guide.

8. Enter Database User Details

   

   On the Database User Details screen, select if you want to perform the installation using SYS or non-SYS database user.

   Note:

   Starting with Enterprise Manager 13c Release 5 Update 15 (13.5.0.15) or higher, you can perform the configuration using the SYS admin user (default option) or a different user, known as a non-SYS admin user.

   SYS is the default user in the Repository database.

   A non-SYS user is a less privileged administrator user of the Repository database that still allows you to perform Enterprise Manager administration tasks.

   If the Perform Installation using non-SYS user is selected, you need to provide the database user name and password for the non-SYS user. The non-SYS user name should have the SYSMAN_ prefix as part of user name. For example, you can enter SYSMAN_ADMIN under DB Username. If the user doesn't exist, the Enterprise Manager installer creates the new user in the Repository database.

   Click Next.

9. Check the Database Prerequisites.

   

   On the Database Prerequisite Checks screen, check the status of the database prerequisites performed by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation. Then click Next.

   The installation wizard runs the database prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed or Succeeded.

   If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Check Again to check the database prerequisites again.

   • If the Auto Fixable column is Yes, you can click on Auto Fix and the installer will fix the issue automatically.
   • If the recommendation indicates that the Correction Type is Manual, you need to fix the issue manually.

   After you complete reviewing and fixing the prerequisites results, click Next.

   The Information pop-up window is displayed.

   Review the important information provided and then click OK.

10. Click Next.

11. Enter Enterprise Manager Configuration Details

    

    On the Repository Configuration Details screen, do the following:

    1. For SYSMAN Password, enter and confirm a password for creating the SYSMAN user account.

       The SYSMAN user account is used for creating the SYSMAN schema, which holds most of the relational data used in managing Enterprise Manager. SYSMAN is also the super administrator for Enterprise Manager.

       Note:

       • Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.

       • If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN122140_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter on this screen.

    2. For Agent Registration Password, enter and confirm a password for registering the new Management Agents that join the Enterprise Manager system.

       Note:

       Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.

    3. For Management Tablespace, enter the absolute path to the location where the data file for management tablespace (mgmt.dbf) can be stored. The installer uses this information for storing data about the monitored targets, their metrics, and so on. Ensure that the specified path leads up to the file name.

       For example, /u01/oracle/prod/oradata/mgmt.dbf

       If the database is on Oracle Automatic Storage Management (Oracle ASM), then the path must look like: +<disk_group>/<sid>/<subdir_path_if_any>/<datafilename>.dbf

       For example, +DATA/oemrsp01d/datafile/mgmt.dbf

    4. For Configuration Data Tablespace, enter the absolute path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf) can be stored. This is required for storing configuration information collected from the monitored targets. Ensure that the specified path leads up to the file name.

       For example, /u01/oracle/prod/oradata/mgmt_ecm_depot1.dbf

       If the database is on Oracle Automatic Storage Management (Oracle ASM), then the path must look like: +<disk_group>/<sid>/<subdir_path_if_any>/<datafilename>.dbf

       For example, +DATA/oemrsp01d/datafile/mgmt_ecm_depot1.dbf

    5. For JVM Diagnostics Data Tablespace, enter the absolute path to a location where the data file for JVM Diagnostics data tablespace (mgmt_deepdive.dbf) can be stored. Ensure that the specified path leads up to the file name. Enterprise Manager requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).

       For example, /u01/oracle/prod/oradata/mgmt_deepdive.dbf

       If the database is on Oracle Automatic Storage Management (Oracle ASM), then the path must look like: +<disk_group>/<sid>/<subdir_path_if_any>/<datafilename>.dbf

       For example, +DATA/oemrsp01d/datafile/mgmt_deepdive.dbf

12. Click Next.

13. Configure Shared Locations.

    On the Enterprise Manager Shared Location Details screen, do the following:

    1. Configure Oracle Software Library. Oracle Software Library (Software Library) is a feature within Enterprise Manager that acts as a repository to store software entities such as software patches, virtual appliance images, reference gold images, application software, and their associated directive scripts. You require the Software Library for operations such as provisioning and patching.

       When checking Configure Oracle Software Library check box, enter the absolute path leading up to a unique directory name. By default, the storage location that is configured is the OMS Shared File System location, Oracle strongly recommends that the location you enter is a mounted location on the OMS host. This helps when you install additional OMS instances that can use the same mounted Software Library location.

       Note:

       Software Library supports two types of storage locations, mainly OMS Shared File System location and OMS Agent File System location. To understand these storage locations, see Upload File Locations in the Oracle Enterprise Manager Administrator's Guide..

       For some reason, if you are unable to configure an OMS Shared File System location, then configure an OMS Agent Storage location. For instructions, see Configuring an OMS Agent File system Location in the Oracle Enterprise Manager Administrator's Guide.

       Note:

       • Configuring the Software Library at the time of installation is optional. Even if you do not select this option and configure it now, your installation will succeed. You always have the option of configuring the Software Library later using the Initial Setup Console or the Software Library Administration Console (available within the Enterprise Manager Console). However, Oracle strongly recommends that you select this option and configure it at the time of installation so that the installer can automatically configure it for you. This saves time and effort, and enables you to install an additional OMS, immediately after the first OMS, and configure it to use the same Software Library location.

       • Once the Software Library is configured, you can view the location details in the Software Library Administration Console. To access this console, from the Setup menu, select Provisioning and Patching, then select Software Library.

14. Click Next.

15. Review Port Configuration Details

    

    On the Port Configuration Details screen, customize the ports to be used for various components.

    You can enter an available custom port that is either within or outside the port range recommended by Oracle.

    To verify if a port is free, run the following command:

    • On Unix:

      netstat -anp | grep <port no>

    • On Microsoft Windows:

      netstat -an|findstr <port_no>

    However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini file and select the file.

    Note:

    If the staticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed.

    The staticports.ini file is available in the following location:

    <Software_Extracted_Location>/response

16. Click Next.

17. Review and Configure

    

    On the Review screen, review the details you provided for the selected installation type.

    • If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

    • After you verify the details, click Configure to begin the configuration process.

18. Track the Configuration Progress

    On the Configuration Details screen, view the overall progress (in percentage) of the configuration.

    Note:

    • If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and retry the configuration assistant.

    • If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.pl script from the Oracle home of the OMS host to rerun the configuration assistant in silent mode. For Microsoft Windows platforms, invoke the runConfig.pl script.

      $<ORACLE_HOME>/oui/bin/runConfig.pl <absolute_path_to_Middleware_home>

      If the runConfig.pl script fails, then clean up your environment and redo the installation.

19. End the Installation

    On the Finish screen, you should see information pertaining to the configuration of the Enterprise Manager. Review the information and click Close to exit the installation wizard.

    Note:

    If a Server Load Balancer (SLB) is configured in your environment, and the upload port is locked, then configure the SLB for JVMD Engines, and then secure the OMS.

    If an SLB is configured in your environment, but the upload port is unlocked, then decide whether you want to route the JVMD traffic through the SLB. If you do, then configure the SLB for JVMD Engines, and then secure the OMS.

    To secure the OMS, run the following command from the bin directory of the Oracle home of the OMS host:

    <ORACLE_HOME>/bin/emctl secure oms -host <SLB host>-slb_jvmd_http_port <JVMD_SLB_HTTP_Port> -slb_jvmd_https_port <JVMD_SLB_HTTPS_Port> -sysman_pwd <system_password> -reg_pwd <agent_registration_password>

Perform the post-install steps as described in Performing Postinstallation Tasks After Installing an Enterprise Manager System chapter from the Enterprise Manager Basic Installation Guide.

General Worklfow for installing the software binaries of Enterprise Manager with plug-ins first, and then configuring the installation at a later point in graphical mode.

1. Installing the Enterprise Manager Software Only with Plug-ins in Silent Mode
2. Running the Root Script
3. Evaluate Non-SYS User Creation
4. Apply Release Update
5. Configuring the Enterprise Manager Software Only in Silent Mode
6. Performing Postconfiguration Tasks After Configuring the Enterprise Manager Software Only in Silent Mode

To install only the software binaries of Enterprise Manager in silent mode, follow these steps:

(For UNIX Only) After you install the software binaries of Enterprise Manager, log in as a root user in a new terminal and run the following scripts:

• If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.

  For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:

  $HOME/oraInventory/oraInstRoot.sh

  Note:

  If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

  /usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh

• Run the allroot.sh script from the OMS home:

  $<ORACLE_HOME>/allroot.sh

  Note:

  If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

  /usr/local/bin/sudo $<ORACLE_HOME>/allroot.sh

Since security is a growing concern, Oracle provides the option to perform the installation, configuration and patching of the OMS using a non-privileged administrator user, also known as non-SYS user.

You are prompted to make the selection of creating and performing the installation using SYS or non-SYS user during the Database User Details step from Configuring the Enterprise Manager Software Only in Graphical Mode.

If there's a Release Update available, Oracle recommends to apply the latest Release Update after installing the Enterprise Manager software binaries.

A Release Update (RU), previously known as Bundle Patch, is an official Oracle patch that can be applied on top of Enterprise Manager 24ai Release 1 main release on an Oracle Home using the omspatcher apply -bitonly command.

For more information about patching and the omspatcher utility, see Patching Oracle Management Service and the Repository in the Enterprise Manager Administrator's Guide.

Server Load Balancer Considerations:

If a Server Load Balancer (SLB) is configured in your environment, and the upload port is locked, then configure the SLB for JVMD Engines, and then secure the OMS.

If an SLB is configured in your environment, but the upload port is unlocked, then decide whether you want to route the JVMD traffic through the SLB. If you do, then configure the SLB for JVMD Engines, and then secure the OMS.

<ORACLE_HOME>/bin/emctl secure oms -host <SLB host>-slb_jvmd_http_port <JVMD_SLB_HTTP_Port> -slb_jvmd_https_port <JVMD_SLB_HTTPS_Port> -sysman_pwd <system_password> -reg_pwd <agent_registration_password>

Other Considerations:

• If a prerequisite check fails reporting a missing package, then make sure you install the required package, and retry the installation. The installer validates the package name as well as the version, so make sure you install the minimum version of the packages mentioned in the Enterprise Manager Basic Installation Guide. To understand the logic the installer uses to verify these packages, see the Enterprise Manager Basic Installation Guide.

• If any repository-related prerequisite check fails, then run the check manually. For instructions, see the appendix on EM Prerequisite Kit in the Enterprise Manager Basic Installation Guide.

• If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and rerun the configuration assistant.

Perform the post-install steps as described in Performing Postinstallation Tasks After Installing an Enterprise Manager System section that is available in the Enterprise Manager Basic Installation Guide.