1. Monit 1 2 123
2. Monit 1 2 123movies
3. Monit 1 2 1/2

Dell P2419H 24 Inch LED-Backlit, Anti-Glare, 3H Hard Coating IPS Monitor - (8 ms Response, FHD 1920 x 1080 at 60Hz, 1000:1 Contrast, with ComfortView DisplayPort, VGA, HDMI and USB), Black 4.7 out of 5 stars 2,301. Aladdin Monitor is a Freeware software in the category Servers developed by Aladdin Monitor. It was checked for updates 31 times by the users of our client application UpdateStar during the last month. The latest version of Aladdin Monitor is 1.4.2, released on.

If you are installing Oracle GoldenGate Monitor Agent on a z/OS platform, see Installing Oracle GoldenGate Monitor Agent for z/OS.

This chapter contains the following sections:

2.1 Installing Oracle GoldenGate Monitor Agent

Use the Oracle Universal Installer (OUI) to install Oracle GoldenGate Monitor Agent for all non-z/OS platforms. Perform the following steps:

2.1.1 Start the Installer

1. Log in to your system.
2. Go to the directory where you downloaded the installation program.
3. Launch the installation program by invoking java -jar from the JDK directory on your system, as shown in the following table:

   For this Operating System	Use this command
   Unix
   Windows

Where fmw_12.2.1.2.0_ogg.jar is the name of the file that you downloaded for your operating system.

When the installation program appears, you are ready to begin the installation. See Install the Product for a description of each installation program screen.

Note:

Oracle GoldenGate Monitor installer will not run on shared disk.

2.1.2 Install the Product

To install the product, navigate through the Installer screens, providing the necessary information as described on the following table. This table lists the screens in the order they will appear and provides instructions for completing any necessary fields. If you want further information on any screen, click its name in the left-hand column.

2.1.3 Install Available Patches

1. Enter the My Oracle Support link into a web browser:
2. Click Sign In....

   Note:

   If you are not already logged in, the Oracle Single Sign-On page appears. Enter your Oracle user id and password and click Sign In.

   The Dashboard page appears.

3. Click the Patches & Updates tab.
4. Search for Management Pack for Oracle GoldenGate patches for your operating system.
5. Unzip the downloaded file.
6. Follow the instructions in the README.txt file, from the patch ZIP file, to verify that the patch is needed for your system and how to install the patch.

2.2 Creating and Configuring an Oracle GoldenGate Monitor Agent Instance

This topic describes the procedures for creating and configuring an Oracle GoldenGate Monitor Agent instance. This process requires these six steps:

2.2.1 Create the Oracle GoldenGate Monitor Agent Instance

1. Go to the directory that contains the Oracle GoldenGate Monitor Agent creation script, createMonitorAgentInstance.sh. For example:
2. Run the script:

   For this Operating System	Use this command
   Unix
   Windows

   The system responds:

3. Enter the absolute path to your Oracle GoldenGate home directory. For example, /u01/ogg/replication/oggcore1.
4. Enter the directory that contains your Oracle GoldenGate Monitor Agent instance, which can be an existing directory. For example, /u01/ogg/agents/oggmon/agent1. This directory should be different than the Oracle GoldenGate home directory to avoid overwriting your Oracle GoldenGate Monitor Agent JAR and configuration files the next time you install or patch Oracle GoldenGate. This directory must also be outside of OGG_AGENT_BASE_HOME directory to support patching. This directory will be referred as OGG_AGENT_INST_HOME in the following sections.

   Note:

   For Windows, you must ensure that you provide the absolute JDK8 directory path explicitly or the Monitor Agent cannot connect to the Monitor server. This directory path can also be defined in the jagent.prm file.

   The Oracle GoldenGate Monitor Agent Instance directory can be an existing directory location. In that case, you are prompted:

   If you choose yes, the execution of the script will continue and all the contents related to Oracle GoldenGate Monitor Agent will be overwritten on that location. If you choose no, the execution of the script will stop.

   The system responds:

5. Enter the unique name that you want to replace the timestamp in the startMonitorAgent.sh script file.

You can create additional instances using this same process though you must ensure that you create them in unique directories. For example, you can point a new Monitor Agent instance to the same Oracle GoldenGate Instance directory (such as, /u01/ogg/replication/oggcore1) or a different Oracle GoldenGate Monitor Agent Instance, and the Oracle GoldenGate Monitor Agent Instance directory must always be a new directory (such as, /u01/ogg/agents/oggmon/agent2). The Oracle GoldenGate Monitor Agent reports Oracle GoldenGate monitoring statistics to the Oracle GoldenGate Monitor Server based on how it is configured.

Note:

2.2.2 Update the Configuration Properties

Oracle GoldenGate Monitor Agent operates in one of two modes, Oracle GoldenGate Monitor Server or Oracle GoldenGate Enterprise Management Plug-In. You set the configuration properties for the mode you want to operate in using the following steps:

1. If you are using Oracle GoldenGate Monitor Server (not Oracle GoldenGate Enterprise Management Plug-In), copy the oggmon.properties file from the OGG_MONITORSERVER_DOMAIN/config/monitorserver/cfg directory to the OGG_AGENT_INST_HOME/cfg directory of all of your Oracle GoldenGate Monitor Agent Instances, where OGG_AGENT_INST_HOME is the absolute path to your Oracle GoldenGate Monitor Agent Instance.
2. Edit the OGG_AGENT_INST_HOME/cfg/Config.properties file.
3. Review and set the properties for one of the following modes:

   Oracle GoldenGate Monitor (OGGMON):

   jagent.host=

   Use the default or change to the complete hostname or IP of the machine where Oracle GoldenGate Monitor Agent (jagent) is running.

   jagent.jmx.port=

   Use the default or change to your preferred port.

   monitor.host=

   Set to the hostname you set during your Oracle GoldenGate Monitor Server installation in monitor.properties.

   monitor.jmx.port=

   Set to the port you set during your Oracle GoldenGate Monitor Server installation in monitor.properties.

   monitor.jmx.username=

   Set to the user name you provided during your Oracle GoldenGate Monitor Agent installation

   jagent.username=

   Set a jagent user name.

   agent.type.enabled=

   Ensure it is set to OGGMON.

   jagent.backward.compatibility=

   Ensure it is set to false.

   jagent.ssl=

   Ensure it is set to false.

   Or

   Oracle GoldenGate Enterprise Management Plug-In (OEM):

   jagent.host=

   Use the default or change to the complete hostname or IP of the machine where Oracle GoldenGate Monitor Agent (jagent) is running.

   jagent.username=

   Set a jagent user name.

   jagent.rmi.port=

   Use the default or change to a specific port.

   agent.type.enabled=

   Set it to OEM.

   jagent.backward.compatibility=

   Ensure it is set to false.

   jagent.ssl=

   Ensure it is set to false.

4. Close and save the file.

The oggmon.properties file is required to create the wallet.

Note:

If you use the Oracle GoldenGate Monitor UI to change a configuration file, you must reopen the file by clicking the Edit button. The tab title is changed to prefix with an asterisk symbol (*), which means that the text area is in edit mode. If you change any value and navigate to other sections without saving, then a confirmation dialog is displayed to inform you to save the change. Otherwise, the changed value is not retained and no messages are displayed.

2.2.3 Create Wallet Credentials

Monit 1 2 123

Navigate to the OGG_AGENT_INST_HOME/bin directory, and then use one of the following sections to create the Oracle Wallet for your operating mode, Oracle GoldenGate Monitoror Oracle GoldenGate Enterprise Management Plug-In.

2.2.3.1 Creating a Oracle GoldenGate Monitor Wallet

1. Delete any existing dirwlt directory.
2. Ensure that the oggmon.properties file is copied into the cfg directory.
3. Start creating the wallet credentials:

   For this Operating System	Use this command
   Unix
   Windows

4. Enter and confirm a user password for your jagent.username property.
5. Enter and confirm a user password for your monitor.jmx.username property.
6. 
   
   The system responds:Jan 06, 2014 5:17:22 PM oracle.security.jps.JpsStartup start INFO: Jps initializing. Jan 06, 2014 5:17:24 PM oracle.security.jps.JpsStartup start INFO: Jps started. Wallet is created successfully.

   This creates the wallet cwallet.sso and cwallet.sso.lck files in dirwlt in the OGG_AGENT_INST_HOME/cfg directory.

2.2.3.2 Creating an Oracle GoldenGate Enterprise Management Plug-In Wallet

1. Start creating the wallet credentials:

   For this Operating System	Use this command
   Unix
   Windows

2. Enter and confirm a user password for your jagent.username property.

   The system responds:

   This creates the wallet cwallet.sso and cwallet.sso.lck files in dirwlt in the OGG_AGENT_INST_HOME directory.

2.2.4 Copy the SSL Certificate Files

Note:

This step is required only if the Oracle GoldenGate Monitor Agent is running in SSL mode.

Go to the OGG_AGENT_INST_HOME/dircrt and copy the Keystore and Truststore files.

After copying the keystore and truststore files, do the following:

1. Using the pw_agent_util.sh (or .bat, on Windows) utility, update the wallet with keystore and truststore passwords, as described in 'Updating Oracle GoldenGate Monitor Agent Passwords' .
2. Update the jagent.keystore and jagent.truststore values in the config.properties file; for example:

Note:

If you are using a self-signed certificate, you can use the same file for both keystore file and truststore. If you are using a third-party signed certificate, you need to update your property file with the appropriate keystore and trust store files.

2.2.5 Preparing the Oracle GoldenGate Monitor Agent Instance for Monitoring

1. Create a file named GLOBALS in the OGG_HOME directory, if this file does not exist.
2. Edit the GLOBALS file.
3. Add ENABLEMONITORING on a new line.
4. Close and save the file.

   Note:

   Starting with Oracle GoldenGate 12.3.x, the datastore is managed internally. Therefore, you can skip Step 5 for Oracle GoldenGate 12.3.x and newer versions.
5. For GoldenGate 12.2.x and older versions, create the datastore using the CREATE DATASTORE command with SHM ID. All processes should be stopped before creating the datastore:

   GGSCI> CREATE DATASTORE SHM ID <unique positive integer>

   Note:

   For GoldenGate 12.3.x and newer versions, you do not need to create datastore manually. It gets created automatically when you start PMSRVR (performance metrics server).

2.2.6 Starting the Oracle GoldenGate Monitor Agent

1. Go to the Oracle GoldenGate GGSCI console and start Oracle GoldenGate Monitor Agent by executing the following commands:

   For GoldenGate 12.2.x and older versions:

   For GoldenGate 12.3.x and newer versions:

   You can also add autostart jagent to the mgr.prm file. In this case, you can skip the start jagent command.

2. Monitor the new Agent log file, $AGENT_HOME/logs/ogg_agent.log and resolve any issues.

   If you are using the Oracle GoldenGate Enterprise Manager Plug-In, after jAgent starts correctly you must restart the Oracle Enterprise Manager (OEM) Agent and then login to the OEM 12c console to ensure that the out-of-sync status issues for Oracle GoldenGate registered targets are resolved.

3. When Web Services become unresponsive due to BDB corruption and errors, you can recreate the datastore and restart all services.

Monit 1 2 123movies

2.2.7 Check Oracle GoldenGate Monitor Agent Instance Log Files

Once you have completed the preceding steps and Oracle GoldenGate Monitor Agent is running, the OracleOracle GoldenGate Monitor Agent log details are written to ogg_agent.log, which is in OGG_AGENT_INST_HOME/logs.

Starting with 12.2.1.2.0 release, Oracle GoldenGate Agent log file only includes errors and warnings. You can edit the OGG_AGENT_INST_HOME/cfg/logging-config.xml file to customize the log level.

2.3 Starting Multiple Oracle GoldenGate Monitor Instances

Monit 1 2 1/2

To monitor the Oracle GoldenGate Core instance through Oracle GoldenGate Monitor and Oracle GoldenGate Enterprise Manager Plug-in, multiple Oracle GoldenGate Monitor instances can be installed.

To run multiple Oracle GoldenGate Monitor Agent Instances from a single install Oracle GoldenGate Core instance:

1. Install the Oracle GoldenGate Core product.

2. Install standalone Oracle GoldenGate Monitor Agent instance 1 pointing to Oracle GoldenGate Core Instance. You can set the mode=OEM.

3. Configure Oracle GoldenGate Agent properties (Config.properties) as required for OGGPLG 12.1.0.2.0 which is under OGG_AGENT_HOME1/cfg directory.

   • The absolute path of Oracle GoldenGate home directory: OGG_CORE_HOME

   • absolute path of first OGG Agent instance directory: OGG_AGENT_HOME1

4. Change the mgr.host to the host name of the machine where Manager is running and mgr.port to the mgr port of the OGGCORE instance.

5. Make a copy of the JAVA command from OGG Core instance which is available in OGG_CORE_HOME/dirprm/jagent.prm file.

6. Create a standalone Oracle GoldenGate Monitor Agent Instance 2 pointing to the same Oracle GoldenGate Core Instance You can set the mode =OGGMON.

   • The absolute path of Oracle GoldenGate home directory: OGG_CORE_HOME

   • The absolute path of second OGG Agent instance directory: OGG_AGENT_HOME2

   Note:

   If the jagent.prm is already exists under OGG_CORE_HOME/dirprm/ the jagent.prm file will be replaced with the latest jagent.prm file.

7. Configure Oracle GoldenGate Agent properties (Config.properties) as need for Monitor 12.1.3 which is under OGG_AGENT_HOME2/cfg directory.

8. Start Oracle GoldenGate Monitor Agent instance 2 from GGSCI.

9. Execute the Java command copied in step 5 for the Monitor agent instance 1 from OGG_AGENT_HOME1 folder created in step 3 or run the script startMonitorAgentInstance_*.sh present under OGG_AGENT_HOME2/bin from the OGG_CORE_HOME location for starting the Monitor agent instance 1.

   For example: OGG_AGENT_HOME2/bin/startMonitorAgentInstance_*.sh

   Note:

   JAgent should be always be started from the OGG_CORE_HOME location because internally based on the usr.dir (the directory where Java was run) system property are used from setting the OGGC CORE location.