4 Configuring and Starting Monitor Server

This chapter describes the procedures for using the Configuration Wizard to create a WebLogic domain for both Oracle and non-Oracle databases (for this version, non-Oracle databases refers to SQL Server). It also includes instructions for starting the server once these domains have been created.

This chapter contains these sections:

Configuring Oracle GoldenGate Monitor Server for Oracle Databases

This section guides you through the steps required to set up a WebLogic domain if you are using an Oracle database. If you are running either a SQL Server database, see Configuring Oracle GoldenGate Monitor Server for SQL Server Databases.

Create the Oracle Database Repository

To create a Oracle Database repository, use this procedure:

  1. Follow the instructions in 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 Oracle 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

    • OPSS

    • IAU

    • IAU_APPEND

    • IAU_VIEWER

Configuring Oracle GoldenGate Monitor Server for SQL Server Databases

In addition to Oracle databases, Oracle GoldenGate Monitor also supports the SQL Server database. The configuration instructions covered in Configuring Oracle GoldenGate Monitor Server for Oracle Databases applies only to that database provider. For the SQL Server database, you need to use the same tools though follow somewhat different procedures. Those procedures are explained in this section:

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)

Create the SQL Server Repository

To create a SQL Server repository, use this procedure:

  1. Follow the instructions in 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

    • OPSS

    • IAU

    • IAU_APPEND

    • IAU_VIEWER

Creating the WebLogic Server Domain

You will use the WebLogic Server Configuration Wizard to create the domain for all supported databases. This tool guides you through the process of creating a WebLogic domain by selecting the product components to include in your domain or by selecting template JAR files. If necessary, you can also customize the domain to suit your environment by adding and configuring Managed Servers, clusters, and machine definitions, or customizing predefined JDBC data sources and JMS file store directories. The procedures in this chapter will guide you through the simplest configuration scenario. To learn more about other capabilities of the Configuration Wizard, see Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Assuming WebLogic Server is installed properly (see Install Oracle WebLogic Server 12c (12.2.1)), launch the Configuration Wizard by doing the following:

On Linux:

$ ORACLE_HOME/oracle_common/common/bin/config.sh

On Windows:

C:\ORACLE_HOME\oracle_common\common\bin\config.cmd

For specifics about ORACLE_HOME, see Install Oracle WebLogic Server 12c (12.2.1).

The Configuration Wizard starts and the Configuration Type screen appears.

To create the domain, navigate the Configuration Wizard screens providing the necessary information as described on the following table. For additional, generic information on each screen, click the screen name in the Screen column:

Screen Configuration Action

Configuration Type

Ensure Create a new domain is selected then:

  • In Domain location, enter the absolute path outside of ORACLE_HOME.; for example:

    /scratch/my_user/oggmon1221_domain

  • Click Next.

Templates

  1. Select Oracle GoldenGate Monitor Server Domain-12.2.1 (oggmon). Additional packages are automatically selected.

  2. Click Next.

Administrative Account

  1. Enter a Name and Password (and confirm the password). These are your WebLogic Server console log-in credentials.

  2. Click Next.

Domain Mode and JDK

  1. In Domain Mode, select Production.

  2. In JDK, select your preferred JDK; for example:

    Oracle HotSpot 1.8.0_40-ea /usr/java/jdk1.8.0_40

  3. Click Next.

Database Configuration Type

  1. Ensure RCU data radio button is selected.

  2. Enter the database connection information.

  3. Enter the Schema owner, which is the prefix you specified when creating your repository appended with _STB; for example, DEV_STB.

  4. Enter the Password.

  5. Click Get RCU Configuration.

  6. Click Next.

JDBC Component Schema

Verify the schema information and click Next.

JDBC Component Schema Test

Verify the schema information and click Next.

Credentials

  1. For each Key Name, enter a Username and Password.

  2. Click Next.

Advanced Configuration

  1. Select Administrative Server and Managed Serves, Cluster, and Coherence.

  2. Click Next.

Administration Server

By default, the server name is AdminServer and the port is 7001, although you can always change default values. For example, you can change the server name AdminServer to OGGMONAdminServer.

If port 7001 is already in use, replace it with an unused port number.Make selections as necessary and click Next.

Managed Servers

The managed server name is already populated with the default, MONITORSERVER_server1, and the port number with 7003. You can change these values, if desired. Also, if port 7003 is already in use, replace it with an unused port number.

Either accept the defaults of update the data and click Next.

Clusters

Click Next.

Coherence Cluster

Click Next.

Machines

Click Next.

Configuration Summary

Review the configuration details and click Create.

Configuration Progress

When configuration creation is complete, click Next.

Configuration Success

  1. Make note of the Administration Server URL for MonitorServer administration.

  2. Click Finish.

The WebLogic Server domain for the Monitor product with Oracle database is now configured.

Completing Monitor Server Configuration

The final steps in configuring Oracle GoldenGate Monitor Server is setting properties as defined in this section.

Configure the JMX Server Properties

  1. At your server prompt, run the configuration utility as follows:

    On Linux:

    $ ./updateOGGMonitorConfig.sh

    On Windows:

    C:\updateOGGMonitorConfig.bat

    This configuration utility is used to update configuration information for Oracle GoldenGate Monitor Server. All fields are required; you can use Ctrl+C to exit.

  2. Enter the absolute path for your Oracle GoldenGate Monitor Server (oggmon) domain, for example: 
    /scratch/prod/OGGMON_INSTALLS/oggmon_stage9_domain

    The system responds:

    You have entered the domain path as : /scratch/prod/OGGMON_INSTALLS/oggmon_stage9_domain
  3. Enter your JMX hostname or IP address. For example, server1.us.domain.com.
  4. Enter your JMX Server Port. For example, 6502.
  5. Enter your JMX Server Username. For example, jmxuser.
  6. Enter the database type for your Oracle GoldenGate Monitor Server using 1 for Oracle Database and 2 for SQL Server.

    The utility completes. After successful execution of this script, the Secure Key properties file, oggmon.properties, is created in encoded format, and contains all of the configuration information you just provided. This Secure Key is added to your Oracle GoldenGate Monitor Server Oracle wallet.

  7. Copy the oggmon.properties file to the cfg directory of your Oracle GoldenGate Monitor Agent instance. For Oracle GoldenGate Monitor Server, the directory is MonitorServer_WLS_Domain/config/monitorserver/cfg; for Monitor Agent, the directory is MonitorAgent_Instance_Home/cfg.

Starting Oracle GoldenGate Monitor Server

To verify that you have successfully Oracle GoldenGate Monitor Server, start the server. This is a two-to-three-step process comprised of:

Starting the Oracle WebLogic Administration Server

To start the Administration Server, do the following:

  1. Navigate to the MONITOR_DOMAIN directory (for example, /apps/oggmon_domain or apps\oggmon_domain on Windows) and start the server:

    On Linux:

    $./startWebLogic.sh

    On Windows:

    C:/path/to/MONITOR_DOMAIN>startWebLogic.cmd

    The server starts, with start-up information displayed on your screen,

    Note:

    Server startup can take a few minutes.

  2. When prompted for the Oracle WebLogic Server Administrator username and password, enter the credentials you created on the Administrative Account screen.

    Startup continues. When the server has started successfully, the server state will be RUNNING.

Update Oracle GoldenGate Monitor Server Credentials (Optional)

Note:

This section is optional. Do it only if you need to update your Oracle GoldenGate Monitor Server credentials. If you do not need to do so, proceed to Start the WebLogic Managed Server).

Use WLST to create or update your wallet's Oracle GoldenGate Monitor Server credentials:

  1. From $ORACLE_HOME/wlserver/common/bin (ORACLE_HOME\wlserver\common\bin on Windows), run WLST:

    On Linux:

    $ORACLE_HOME/wlserver/common/bin>./wlst.sh

    On Windows:

    C:\path\to\bin>wlst.cmd
  2. Then, do one of the following:
    To... Use this WLST Function...

    Create the new credentials

    createCred(); for example:

    wls:/test_domain/serverConfig>createCred(map="OGGMONITOR",key="WEB.JMX.PASSWORD",user="jmxuser",password="jmxuser1",desc="JMX Password")
wls:/test_domain/serverConfig>createCred(map="OGGMONITOR",key="MONITOR.KEYSTORE.PASSWORD",user="ksuser",password="ksuser1",desc="Keystore Password")
wls:/test_domain/serverConfig>createCred(map="OGGMONITOR",key="MONITOR.TRUSTSTORE.PASSWORD",user="tsuser",password="tsuser1",desc="Truststore Password")
wls:/test_domain/serverConfig>createCred(map="OGGMONITOR",key="WEB.SMTP.EMAIL.PASSWORD",user="smtpuser",password="smtpuser1",desc="SMTP Password")

    Update an existing key

    updateCred(); for example:

    wls:/test_domain/serverConfig>updateCred(map="OGGMONITOR",key="MONITOR.TRUSTSTORE.PASSWORD",user="tsuser",password="tsuser1",desc="Truststore Password")

    Delete an existing key

    deleteCred(); for example:

    wls:/test_domain/serverConfig>deleteCred(map="OGGMONITOR", key="MONITOR.TRUSTSTORE.PASSWORD")

    Note:

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

Start the WebLogic Managed Server

Finally, start the WebLogic Managed Server:

  1. Navigate to MONITOR_SERVER_DOMAIN\bin (MONITOR_SERVER_DOMAIN\bin on Windows) and enter:

    On Linux:

    $./startManagedWebLogic.sh MONITORSERVER_server1 http://hostname:7001

    On Windows:

    C:path\to\bin>startManagedWebLogic.cmd MONITORSERVER_server1 http://hostname:7001

    Where:

    • MONITORSERVER_server1 is the managed server name entered in the Configuration Wizard when that server was configurated.

    • hostname:7001 is your specific hostname and listening port.

  2. When prompted, enter the Oracle WebLogic Server Administrator username and password.

If the Oracle GoldenGate Monitor Server is deployed successfully, you should see the managed server state as RUNNING.