4 Configuring and Starting Monitor Server

4.2.1.1 Before You Begin

Before attempting to configure a domain for MySQL, the following values must be set:

SET GLOBAL INNODB_FILE_PER_TABLE="ON";
SET GLOBAL INNODB_FILE_FORMAT="Barracuda";
SET GLOBAL INNODB_LARGE_PREFIX="ON";
SET GLOBAL LOG_BIN_TRUST_FUNCTION_CREATORS="ON"; 

4.2.1.2 Create the MySQL Repository

To create a MySQL repository, use this procedure:

1. Follow the instructions in Section 3.2, "Creating a Repository" to create a repository; however, note the following exceptions for a MySQL repository:

   1. When you reach the Database Connection Details screen, set Database Type to MySQL database and set the appropriate connection information. Click Next.

      The Select Components screen appears.

   2. On the Select Components screen, select only Monitor Server and Service Table (by default, Service Table should already be selected).

2. Follow the remaining repository creation process. You should have these schemata generated:

   • OGGMON (the product-specific schema)

   • STB

4.2.1.3 Create a Compact WebLogic Server Domain

The next task is to create a compact Oracle WebLogic Server domain.

To create the compact Oracle WebLogic Server domain for MySQL, you need to run the script monitorServerCreateCompactDomain.sh, which was installed with Oracle GoldenGate Monitor Server.

To create the domain, use this procedure:

1. Go to ORACLE_HOME/oggmon/monitor_server/bin/ (ORACLE_HOME\oggmon\monitor_server\bin\ on Windows).

2. Copy the file ../samples/monitorServerCompactDomain.properties to the ORACLE_HOME/oggmon/monitor_server/bin/ directory. This file contains the default settings required to create a domain. Update the domain location and data source settings property values appropriately.

3. Update the following properties with the appropriate data:

   • weblogic server

   • database

4. Save the file.

5. Enter ./monitorServerCreateCompactDomain.sh monitorServerCompactDomain.properties (assuming that monitorServerCompactDomain.properties is copied under ORACLE_HOME/oggmon/monitor_server/bin/).

   The WebLogic Scripting Tool (WLST), a command-line scripting environment that you can use to create, manage, and monitor WebLogic domains, opens, prompting you to provide specific information about the new domain.

   Initializing WebLogic Scripting Tool (WLST) ...
   
   Welcome to WebLogic Server Administration Scripting Shell
   
   Type help() for help on available commands
   
   Please enter WebLogic domain administrator(weblogic) password : 
   [Confirm]    WebLogic domain administrator(weblogic) password : 
   Please enter MonitorServer respository database password           : 
   Please enter MonitorServer JMX password           : 
   Please enter MonitorServer Keystore password           : 
   Please enter MonitorServer Truststore password           : 
   Please enter MonitorServer SMTP email password           : 
   Given WebLogic location - WL_HOME : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver
   MonitorServer Template Jar file path : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver/../oggmon/common/templates/wls/monitor_server_compact_template_12.1.3.jar
   Basic WebLogic Template Jar file path : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver/common/templates/wls/wls.jar
   JRF Template Jar file path : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver/../oracle_common/common/templates/wls/oracle.jrf_template_12.1.3.jar
   Creating Domain at Location : /scratch/monitor/wl-domains/domain_1
    
   Updating MonitorServer Domain ...
   Domain Admin Console URL : http://<Host>:7071/console
   MonitorServer URL : http://<Host>:7071/monitor
   WebLogic Domain administrator user name : weblogic
    
   Exiting WebLogic Scripting Tool
   

   Note:

   For more information about WLST, see Understanding the WebLogic Scripting Tool

6. At the prompts, enter passwords for the following properties:

   • weblogic domain administrator (user - weblogic)

   • MonitorServer repository database

   • MonitorServer JMX

   • MonitorServer Keystore

   • MonitorServer Truststore

   • MonitorServer SMTP email

7. Exit WLST.

4.2.2.1 Before You Begin

Before you begin, do the following:

• Set:

  ISOLATION LEVEL,ALTER DATABASE $(DATABASE_NAME) SET READ_COMMITTED_SNAPSHOT ON
  

• Ensure the database is case-sensitive:

  DECLARE @collate sysname
     select @collate = convert(sysname, serverproperty('Collation'))
  IF ( charindex(N'_CI', @collate) > 0 )
  BEGIN
     select @collate = replace(@collate, N'_CI', N'_CS')
     exec ('ALTER database $(DATABASE_NAME) COLLATE ' + @collate)
  

4.2.2.2 Create the SQL Server Repository

To create a SQL Server repository, use this procedure:

1. Follow the instructions in Section 3.2, "Creating a Repository" to create a repository; however, note the following exceptions for SQL Server:

   1. When you reach the Database Connection Details screen, set Database Type to SQL Server database and set the appropriate connection information. Click Next.

      The Select Components screen appears.

   2. On the Select Components screen, select Monitor Server and Service Table (by default, this should already be selected).

2. Follow the remaining repository creation process. You should have these schema generated:

   • OGGMON (the product-specific schema)

   • STB

4.2.2.3 Create a Compact WebLogic Server Domain

The next task is to create a compact Oracle WebLogic Server domain.

To create the compact Oracle WebLogic Server domain for SQL Server, you need to run the script monitorServerCreateCompactDomain.sh, which was installed with Oracle GoldenGate Monitor Server.

To create the domain, use this procedure:

1. Go to ORACLE_HOME/oggmon/monitor_server/bin/.

2. Copy the file ../samples/monitorServerCompactDomain.properties to the ORACLE_HOME/oggmon/monitor_server/bin/ directory. This file contains the default settings required to create a domain. Update the domain location and datasource settings property values appropriately.

3. Update the following properties with the appropriate data:

   • weblogic server

   • database

4. Save the file.

5. Enter ./monitorServerCreateCompactDomain.sh monitorServerCompactDomain.properties (assuming that the monitorServerCompactDomain.properties file is copied under ORACLE_HOME/oggmon/monitor_server/bin).

   The WebLogic Scripting Tool (WLST), a command-line scripting environment that you can use to create, manage, and monitor WebLogic domains, opens, prompting you to provide specific information about the new domain.

   Initializing WebLogic Scripting Tool (WLST) ...
   
   Welcome to WebLogic Server Administration Scripting Shell
   
   Type help() for help on available commands
   
   Please enter WebLogic domain administrator(weblogic) password : 
   [Confirm]    WebLogic domain administrator(weblogic) password : 
   Please enter MonitorServer respository database password           : 
   Please enter MonitorServer JMX password           : 
   Please enter MonitorServer Keystore password           : 
   Please enter MonitorServer Truststore password           : 
   Please enter MonitorServer SMTP email password           : 
   Given WebLogic location - WL_HOME : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver
   MonitorServer Template Jar file path : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver/../oggmon/common/templates/wls/monitor_server_compact_template_12.1.3.jar
   Basic WebLogic Template Jar file path : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver/common/templates/wls/wls.jar
   JRF Template Jar file path : /scratch/rporandl/Oracle/WLS_12.1.3_Feb16/wlserver/../oracle_common/common/templates/wls/oracle.jrf_template_12.1.3.jar
   Creating Domain at Location : /scratch/monitor/wl-domains/domain_2
    
   Updating MonitorServer Domain ...
   Domain Admin Console URL : http://<Host>:7091/console
   MonitorServer URL : http://<Host>:7091/monitor
   WebLogic Domain administrator user name : weblogic
    
   Exiting WebLogic Scripting Tool.
   

   Note:

   For more information about WLST, see Understanding the WebLogic Scripting Tool

6. At the prompts, enter passwords for the following properties:

   • weblogic domain administrator (user - weblogic)

   • MonitorServer repository database

   • MonitorServer JMX

   • MonitorServer Keystore

   • MonitorServer Truststore

   • MonitorServer SMTP email

7. Exit WLST.

4.3.2.1 Importing the MIB File

The GoldenGate-Monitor-mib.mib file is delivered to the cfg subdirectory during the installation of Oracle GoldenGate Monitor. This contains the Management Information Base (MIB) definitions the target uses to interpret the alerts. If you need to interpret information received in the traps, import this file to the target tool.

4.3.2.2 Configuring SNMP Alerts

The SNMP alert is configured in the SNMPJMXMapping.xml file that is delivered to the cfg subdirectory during the Oracle GoldenGate installation.

Any changes to the SNMPJMXMapping.xml file must be made outside of the Oracle GoldenGate Monitor user interface by the host administrator that installed the Oracle GoldenGate Monitor Server software.

You should only change the sections of the SNMPJMXMapping.xml file that set the SNMP version and define the targets.

.
.
.
<MIBTree>
.
.
.
 <notifications type="NOTIFICATIONS">
  <notification version="2" enabled="true">
   <targets>
    <target timeout="200" retry="0">localhost/162
    </target>
   </targets>
.
.
.
  </notification>
  <notification version="1" enabled="false">
   <targets>
    <target>localhost/162
    </target>
   </targets>
.
.
.
  </notification>
 </notifications>
</MIBTree>

4.3.2.3 Setting the SNMP Version

The SNMP version is initially set based on the entry during installation. You can change it later by resetting the notification version 1 enabled value and notification version 2 enabled value. Set one to true and the other to false.

The targets that are defined for the enabled version are used. The targets for the disabled version are ignored.

4.3.2.4 Setting the SNMP Targets

Define your targets within the <target> </target> tags by entering the host name and port number.

4.3.3.1 Setting Up Command-Line Handlers

The Oracle GoldenGate Monitor installation delivers files to help you configure your CLI interface. These are delivered to the cfg subdirectory of the installation location.

• CommandLineHandlers.xml

  The CLI interface is configured in the CommandLineHandlers.xml file.

  Two example CommandLineHandlers.xml files, one for UNIX and one for Windows, are included with the installation. Each contains sample syntax for configuring a CLI interface. You can copy the appropriate version and then add and change arguments to create the CommandLineHandlers.xml that will configure your CLI interface.

  Note:

  The CommandLineHandlers.xml file must be set up outside of the Oracle GoldenGate Monitor user interface by the Oracle GoldenGate Monitor Server host administrator that installed the system.

• CommandLineHandlers.xsd

  This file contains the definition for the CommandLineHandlers.xml file. It can be used to generate the CommandLineHandlers.xml using a commercial or open source XML generation tool that creates sample XML from XSD.

After you configure the CommandLineHandlers.xml, stop and restart the Oracle GoldenGate Monitor Server to activate the changes. See Starting Oracle GoldenGate Monitor Server for directions on how to do this.

<?xml version="1.0" encoding="UTF-8"?>
<CommandLineHandlers . . .>
<CommandLineHandler dateTimeFormat="MMddyyyyHHmmssSSS"
  executeIn="/home/user" name="CMDLINE">
    <externalCommand>touch</externalCommand>
    <arguments>
      <argument argText="filename" name="hostname"
      presentIfEmpty="true" quoted="false"/>
  </arguments>
  <alertMappings>
    <alertMapping alertField="host" name="hostname"/>
  </alertMappings>
  </CommandLineHandler>
</CommandLineHandlers>s

<CommandLineHandler dateTimeFormat="MMddyyyyHHmmssSSS" 
executeIn="/home/user" name="CMDLINE">

<externalCommand>touch</externalCommand>
<arguments>
    <argument argText="filename" name="hostname"
    presentIfEmpty="true" quoted="false"/>
</arguments>
<alertMappings>
    <alertMapping alertField="host" name="hostname"/>
</alertMappings>

4.3.3.2 Sample Command-Line Handlers

These examples run a batch script on the Oracle GoldenGate Monitor Server.

<?xml version="1.0" encoding="UTF-8"?>
<CommandLineHandlers
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.yourlocation/monitor/commandlinehandlers/CommandLineHandlers.xsd">
  <CommandLineHandler dateTimeFormat="MMddyyyyHHmmssSSS"
  executeIn="C:\" name="CMDLINE">
    <externalCommand>c:\sample_cli.bat</externalCommand>
    <arguments>
      <argument argText="" name="hostname" presentIfEmpty="true" quoted="false"/>
    </arguments>
    <alertMappings>
      <alertMapping alertField="host" name="hostname"/>
    </alertMappings>
  </CommandLineHandler>
</CommandLineHandlers>

<?xml version="1.0" encoding="UTF-8"?>
<CommandLineHandlers
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.yourlocation/monitor/commandlinehandlers/CommandLineHandlers.xsd">
  <CommandLineHandler dateTimeFormat="MMddyyyyHHmmssSSS"    executeIn="/home/user" name="CMDLINE">
    <externalCommand>bash</externalCommand>
    <arguments>
      <argument argText="/home/user/sample_cli.sh" name="hostname"  presentIfEmpty="true" quoted="true"/>
    </arguments>
    <alertMappings>
     <alertMapping alertField="host" name="hostname"/>
    </alertMappings>
  </CommandLineHandler>
</CommandLineHandlers>