Oracle® GoldenGate

Installing and Configuring Oracle GoldenGate Monitor

12c (12.1.3)

E50582-05

April 2015

This document describes how to install and configure Oracle GoldenGate Monitor Server.

Oracle GoldenGate Installing and Configuring Oracle GoldenGate Monitor, 12c (12.1.3)

E50582-05

Copyright © 2011, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- 1.1 Platform Support

- 1.2 About Oracle GoldenGate Monitor

- 1.3 Oracle GoldenGate Monitor Architecture

- 1.3.1 Oracle GoldenGate

- 1.3.2 Oracle GoldenGate Agent

- 1.3.3 Oracle GoldenGate Monitor Server

- 1.3.4 Oracle GoldenGate Monitor Repository

- 1.4 Installation and Configuration Roadmap

- 1.5 Using Oracle GoldenGate Monitor with Non-Oracle Databases

2 Preparing to Install

- 2.1 Install JDK 1.7 on the Target Machine

- 2.2 Install WebLogic Server 12c (12.1.3)

- 2.3 Install the Database Software

- 2.3.1 Setting the nls_length_semantics Parameter in your Database

- 2.4 Next Step: Install Oracle GoldenGate Monitor

3 Installing Oracle GoldenGate Monitor

- 3.1 Installing Oracle GoldenGate Monitor

- 3.1.1 Obtain the Installer

- 3.1.2 Start the Installation Program

- 3.1.3 Install the Product

- 3.2 Creating a Repository

- 3.2.1 Before You begin

- 3.2.2 Create the Repository

- 3.3 Next Step: Configure the Domain

4 Configuring and Starting Monitor Server

- 4.1 Configuring Oracle GoldenGate Monitor Server for Oracle Databases

- 4.1.1 The Configuration Wizard

- 4.1.2 Launching the Configuration Wizard

- 4.1.3 Creating the Domain

- 4.2 Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases

- 4.2.1 Configuring a Domain for MySQL

- 4.2.1.1 Before You Begin

- 4.2.1.2 Create the MySQL Repository

- 4.2.1.3 Create a Compact WebLogic Server Domain

- 4.2.2 Configuring a Domain for Microsoft SQL Server

- 4.2.2.1 Before You Begin

- 4.2.2.2 Create the SQL Server Repository

- 4.2.2.3 Create a Compact WebLogic Server Domain

- 4.3 Completing Monitor Server Configuration

- 4.3.1 Edit Monitor Properties

- 4.3.2 Complete the SNMP Alerts Configuration

- 4.3.2.1 Importing the MIB File

- 4.3.2.2 Configuring SNMP Alerts

- 4.3.2.3 Setting the SNMP Version

- 4.3.2.4 Setting the SNMP Targets

- 4.3.3 Complete the CLI Configuration

- 4.3.3.1 Setting Up Command-Line Handlers

- 4.3.3.2 Sample Command-Line Handlers

- 4.4 Starting Oracle GoldenGate Monitor Server

- 4.4.1 Start the WebLogic Administration Server

- 4.4.2 Update Oracle GoldenGate Monitor Server Credentials (Optional)

- 4.4.3 Start the WebLogic Managed Server

5 Managing Users from the WebLogic Administration Console

- 5.1 Log-in to Oracle WebLogic Server Administration Console

- 5.2 Create a User

- 5.3 Add the User to a Group

- 5.4 Start the Oracle GoldenGate Monitor Console

6 Deinstalling Monitor Server

- 6.1 Stop the Servers

- 6.2 Drop the Repositories

- 6.3 Delete the WebLogic Domain

- 6.4 Deinstall Oracle GoldenGate Monitor Server

7 Moving from a Test to a Production Environment

- 7.1 Prerequisites

- 7.2 Preparing the Test Environment

- 7.3 Preparing the Production Environment

- 7.3.1 Before You Begin

- 7.3.2 Preparing the Environment

- 7.4 Verifying the Move

- 7.5 Additional Information

A Installation and Configuration Screens

- A.1 Installation Screens for Oracle GoldenGate Monitor

- A.1.1 Welcome

- A.1.2 Installation Location

- A.1.3 Installation Type

- A.1.4 Prerequisite Checks

- A.1.5 Installation Summary

- A.1.6 Installation Progress

- A.1.7 Installation Complete

- A.2 Repository Creation Utility (RCU) Screens for Oracle GoldenGate Monitor

- A.2.1 Welcome

- A.2.2 Create Repository

- A.2.3 Database Connection Details

- A.2.4 Select Components

- A.2.5 Schema Passwords

- A.2.6 Map Tablespaces

- A.2.7 Summary

- A.2.8 Completion Summary

- A.3 Configuration Wizard Screens for Oracle GoldenGate Monitor

- A.3.1 Configuration Type

- A.3.2 Templates

- A.3.3 Administrative Account

- A.3.4 Domain Mode and JDK

- A.3.5 Database Configuration Type

- A.3.6 JDBC Component Schema

- A.3.7 JDBC Component Schema Test

- A.3.8 Credentials

- A.3.9 Advanced Configuration

- A.3.10 Administration Server

- A.3.11 Managed Servers

- A.3.12 Clusters

- A.3.13 Coherence Cluster

- A.3.14 Machines

- A.3.15 Configuration Summary

- A.3.16 Configuration Progress

- A.3.17 Configuration Success

Preface

This document describes how to install and configure an Oracle GoldenGate Monitor.

Audience

This document is intended for system administrators or application developers who are installing the Oracle GoldenGate Monitor Server. It is assumed that readers are familiar with Web technologies and have a general understanding of Windows and UNIX platforms.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle GoldenGate Monitor documentation set:

- Administering Oracle GoldenGate Monitor

- Oracle GoldenGate Monitor Console Online Help

- Upgrading to Oracle GoldenGate Monitor Server 12.1.3

- Installing and Configuring Oracle GoldenGate Monitor Agent

- Release Notes for Oracle GoldenGate Monitor

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

This chapter is an introduction to the installation and configuration procedures for Oracle GoldenGate Monitor. It is comprised of the following sections:

- Section 1.1, "Platform Support"

- Section 1.2, "About Oracle GoldenGate Monitor"

- Section 1.3, "Oracle GoldenGate Monitor Architecture"

- Section 1.4, "Installation and Configuration Roadmap"

- Section 1.5, "Using Oracle GoldenGate Monitor with Non-Oracle Databases"

1.1 Platform Support

To see current platform support information for Oracle GoldenGate Monitor 12c (12.1.3), do the following

1. Log in to Oracle Support, at:
http://support.oracle.com

and click the Certifications tab.

The Certification page appears.

2. Open the Search tab and, in the Product field, type GoldenGate to open the product list.

3. From the Product list, select Oracle GoldenGate (OGG, FMW, Oracle GoldenGate Suite).

4. Click the Release edit box to open the release list and select 12.1.3.0.0.

5. Click Search.
The Search Results page for the selected product and release will appear, showing the operating systems, databases, application, browsers, and clients with which the selected Oracle GoldenGate version is certified. You can see details about each platform by clicking the text in the Number of Releases/Versions column.

1.2 About Oracle GoldenGate Monitor

Oracle GoldenGate Monitor is a real-time, web-based monitoring console for the Oracle GoldenGate replication solution. Oracle GoldenGate Monitor delivers an at-a-glance, graphical view of all of the Oracle GoldenGate instances and their associated databases within your enterprise. Instantly, you can view statistics, targeted views, and alerts that will help you to monitor the performance of all of the objects in the Oracle GoldenGate configuration and detect problems, such as lag or abended processes, the moment that they occur. Oracle GoldenGate Monitor can send alert messages to its own console workspaces, as well as to e-mail, SNMP, and CLI clients.

1.3 Oracle GoldenGate Monitor Architecture

Oracle GoldenGate Monitor uses a browser-based graphical user interface to monitor Oracle GoldenGate instances remotely. It includes the components shown in the diagram.

1.3.1 Oracle GoldenGate

An Oracle GoldenGate Monitor Server communicates with one or more Oracle GoldenGate instances using Java Management Extensions (JMX). The Manager process for each Oracle GoldenGate instance is associated with an Oracle GoldenGate Agent that supplies information about the instance to the Oracle GoldenGate Monitor Server.

1.3.2 Oracle GoldenGate Agent

An Oracle GoldenGate Agent is installed with each Oracle GoldenGate instance. It collects information about the instance and sends it to the Oracle GoldenGate Monitor Server. Oracle GoldenGate agent is installed separately from Oracle GoldenGate Monitor. For those installation and configuration procedures, see Oracle® GoldenGate Installing and Configuring Oracle GoldenGate Monitor Agent.

1.3.3 Oracle GoldenGate Monitor Server

The Oracle GoldenGate Monitor Server coordinates the monitoring of multiple Oracle GoldenGate instances. The Oracle GoldenGate Monitor Server is a Java application that:

- processes information from Oracle GoldenGate Agents and communicates it to the web browser and

- manages users, history, the display of information, and notifications triggered by events.

1.3.4 Oracle GoldenGate Monitor Repository

The Oracle GoldenGate Monitor Server uses a database as a central repository to store information about users and groups, process status, events, and other information.

1.4 Installation and Configuration Roadmap

Installing and configuring Oracle GoldenGate Monitor Server comprises these steps:

1. Meet prerequisites described in Chapter 2, "Preparing to Install".

2. Run the Oracle Universal Installer (OUI) to install Oracle GoldenGate Monitor Server. For instructions, see Section 3.1, "Installing Oracle GoldenGate Monitor".

3. Run the Repository Configuration Utility (RCU) to create Oracle GoldenGate Monitor-specific repository. For instructions, see Section 3.2, "Creating a Repository".

4. Run the Configuration Wizard to create Oracle WebLogic Server domain for Oracle databases. For instructions, see Section 4.1, "Configuring Oracle GoldenGate Monitor Server for Oracle Databases".
If you are using a non-Oracle database, follow the additional instructions in Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases". See also Section 1.5, "Using Oracle GoldenGate Monitor with Non-Oracle Databases"

5. Perform the manual configuration steps to finish creating your domain. For instructions, see Section 4.3, "Completing Monitor Server Configuration".

6. Start Oracle GoldenGate Monitor Server, For instructions, see Section 4.4, "Starting Oracle GoldenGate Monitor Server".

7. Add and/or update users from the Oracle WebLogic Server Administration console, as described in Chapter 5, "Managing Users from the WebLogic Administration Console".

1.5 Using Oracle GoldenGate Monitor with Non-Oracle Databases

In addition to Oracle databases specified in Section 2.3, "Install the Database Software", Oracle GoldenGate Monitor Server 12c (12.1.3) also supports databases provided by MySQL and Microsoft SQL Server. Because these non-Oracle databases do not support the Oracle Platform Security Service (OPSS) configuring them requires a few different steps than do Oracle databases. If you are installing either of these non-Oracle databases, you should familiarize yourself with these additional steps. For more information, see Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases".

2 Preparing to Install

This is a chapter describes the prerequisites you must meet before you can successfully install and configure Oracle GoldenGate Monitor. It is comprised of these sections

- Section 2.1, "Install JDK 1.7 on the Target Machine"

- Section 2.2, "Install WebLogic Server 12c (12.1.3)"

- Section 2.3, "Install the Database Software"

- Section 2.4, "Next Step: Install Oracle GoldenGate Monitor"

Note:
If your machine configuration already meets the criteria specified in this chapter, proceed to Chapter 3, "Installing Oracle GoldenGate Monitor".

2.1 Install JDK 1.7 on the Target Machine

The target machine is that computer on which you are running the Oracle GoldenGate Monitor instance. Install JDK 7.1 on this machine and set JAVA_HOME and PATH environment variables with JDK 1.7 path.

For more information on installing JDK 1.7, see the "JDK 7 and JRE 7 Installation Guide" at:

http://docs.oracle.com/javase/7/docs/webnotes/install/index.html

2.2 Install WebLogic Server 12c (12.1.3)

After installing the certified JDK (JDK 1.7.0_15 or higher), use the Oracle Fusion Middleware 12c (12.1.3) Infrastructure installer to install Oracle WebLogic Server and the Oracle Java Required Files (JRF) Infrastructure services. Download the installer fmw_WLS_version_infrastructure.jar (where WLS_version represents the supported WebLogic Server version; for example, 12.1.3.0.0), which you can obtain from:

http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html

or from the Oracle Software Delivery Cloud, at:

https://edelivery.oracle.com/

For more details on obtaining Oracle Fusion Middleware Infrastructure installer, see "Understanding and Obtaining the Oracle Fusion Middleware Infrastructure Distribution" in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

For details on installing Oracle WebLogic Server and JRF, see "Installing the Oracle Fusion Middleware Infrastructure Software" in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

2.3 Install the Database Software

Oracle GoldenGate Monitor supports these databases:

Database

Version

Documentation

Oracle

11gR2, 12c

http://www.oracle.com/technetwork/indexes/documentation/index.html#database

MySQL

5.5

http://www.oracle.com/technetwork/indexes/documentation/index.html#database

SQL Server

2008, 2012

2008: http://www.microsoft.com/en-us/download/details.aspx?id=30437
2012: http://msdn.microsoft.com/en-us/library/cc281837%28v=sql.110%29.aspx

The MySQL and Microsoft SQL Server databases do not support the Oracle Platform Security Service (OPSS) so configuring them requires different steps than the Oracle database. If you are installing either of these non-Oracle databases, you should familiarize yourself with these additional steps, see Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases".

2.3.1 Setting the nls_length_semantics Parameter in your Database

Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter on the database where the schemas reside must be set to BYTE; setting this parameter to CHAR is not supported.

To check the values of this parameter using SQL*Plus, you can use the show parameters command:

prompt> sqlplus "sys/password as sysdba"SQL> show parameters nls_length_semantics

Replace password with the actual password for the SYS user.

Alternatively, you can check the values by querying the V$PARAMETER view:

prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;

2.4 Next Step: Install Oracle GoldenGate Monitor

With the prerequisites met, you will now install Oracle GoldenGate Monitor. For instructions, see Section 3, "Installing Oracle GoldenGate Monitor"

3 Installing Oracle GoldenGate Monitor

This chapters contains the steps necessary to install Oracle GoldenGate Monitor on your computer. It also provides additional details for using the Repository Configuration Utility (RCU) to create a repository for your Oracle GoldenGate Monitor implementation. This chapter is comprised of the following sections:

- Section 3.1, "Installing Oracle GoldenGate Monitor"

- Section 3.2, "Creating a Repository"

3.1 Installing Oracle GoldenGate Monitor

You install Oracle GoldenGate Monitor by using the Oracle Universal Installer (OUI), a seven-step, screen-driven tool used to install this and other Oracle products. This section describes how to launch and navigate the OUI. To install Oracle GoldenGate Monitor, you need to:

1. Obtain the Installer

2. Start the Installation Program

3. Install the Product

Note:
For more detailed information on OUI, see Installing with the Oracle Universal Installer.

3.1.1 Obtain the Installer

OUI for all Oracle GoldenGate components is available from the product distribution, which you can obtained from either the Oracle Software Delivery Cloud, MyOracle Support, or the Oracle Technology Network. For more information, contact your Release team.

3.1.2 Start the Installation Program

To start the installation program, perform the following steps.

1. Log in to the target 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 O/S

Use this command

Unix

$ java -jar -Xmx1024m /path/to/jar/file/fmw_12.1.3.0.0_ogg.jar

Windows

C:\ java -jar -Xmx1024m  fmw_12.1.3.0.0_ogg.jar

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

3.1.3 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.

Screen

Description

Installation Action

Welcome

This screen introduces you to the product installer.

Click Next.

Installation Location

On this screen, specify the location of your Oracle home directory.

1. Type or browse and select the Oracle Home location (that is, the path where you have installed WebLogic Server+JRF) and

2. Click View to see the products installed under the selected Oracle Home.

3. Click Next.

Installation Type

On this screen, specify the type of installation you want to perform and thus, which products and features are installed.

1. Select Oracle Golden Gate Monitor Server.

2. Click Next.

Prerequisite Checks

This screen analyzes the host computer to ensure that specific operating system prerequisites have been met.

Click Next.

Installation Summary

This screen contains a list of the feature sets you selected for installation, along with the approximate amount of disk space to be used by the feature sets once installation is complete.
Note: To display an individual component's approximate installed size, click its name.

Click Install.

Installation Progress

This screen shows the progress of the installation. When the progress bar reaches 100%, the installation is complete. Be aware that the Generating Libraries process can take up to 70% of the total installation time on some systems.

When the installation progress is 100%, click Next.

Installation Complete

This screen appears at the conclusion of the installation and provides a summary of the products and features that were installed. Click Finish to dismiss the installer.

Click Finish.

3.2 Creating a Repository

Note:
These procedures describe how to create a repository for an Oracle database, only. If you are creating an repository for a non-Oracle database (that is, MySQL and SQL Server), see Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases"

Next, use the Repository Creation Utility (RCU) to create an Oracle GoldenGate Monitor-specific repository.

Note:
For more information on creating a repository with RCU, see Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

3.2.1 Before You begin

Before creating the repository for an Oracle database, be aware of the following:

- The character set must be AL32UTF8 because the default character set is not supported by RCU.

- RCU supports only plug-able databases; it does not support container database. This is because by default container database will enable in Oracle 12c (12.1.3).

3.2.2 Create the Repository

To create the repository use this procedure:

1. Start RCU by doing the following:

1. Change directory to ORACLE_HOME/oracle_common/bin/ (ORACLE_HOME\oracle_common\bin\ on Windows).

2. Launch RCU by entering:
On Linux:

$ ./rcu

On Windows:

C:/path/to/bin>rcu.bat

The RCU Welcome screen appears.

2. Navigate through the RCU 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

Repository Creation Action

Welcome

Click Next.

Create Repository

1. Ensure Create Repository and System Load and Product Load are selected.

2. Click Next.

Database Connection Details

1. Enter Database Connection details with the appropriate information.

2. Click Next.
A confirmation window opens, verifying that the Global Prerequisites are implemented.

3. Click OK.

Select Components

1. If it is not already selected, select Create new prefix and, in the edit box, enter the prefix by which you want to identify that the schema was created for Oracle GoldenGate Monitor Server (for example, DEV1). This schema prefix is automatically appended with _STB, which you will use when configuring your Oracle WebLogic Server domain.

2. Select the following components:

- AS Common Schemas

- Metadata Services

- Audit Services

- Audit Services Append

- Audit Services Viewer

- Oracle Platform Security Services

- User Messaging Services

- WebLogic Services

- Call COntrol

- Oracle GoldenGate

- Monitor Server

Note: The preceding component list is for Oracle databases, only. Components selected for non-Oracle databases will differ. For more information, see Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases"

3. Click Next.
A confirmation window opens, verifying that the prerequisites are implemented.

4. Click OK.

Schema Passwords

1. Ensure that Use same password for all schemas is selected.

2. Enter and confirm a new password.

3. Click Next.

Map Tablespaces

1. Click Next.
A confirmation window opens, advising that tablespaces that do not already exist will be created.

2. Click OK to create the new tablespaces or Cancel to return to the wizard (this procedure assumes you clicked OK).
A confirmation window opens, tracking the progress of the tablespace creation.

3. Click OK.

Summary

Review the repository creation summary and click Create.

Completion Summary

Click Close. This will end the repository creation process.

3.3 Next Step: Configure the Domain

With Oracle GoldenGate Monitor Server installed and a repository created, you need to create the domain for the database type you are using. For instructions, see Chapter 4, "Configuring and Starting Monitor Server".

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 MySQL and SQL Server). It also includes instructions for starting the server once these domains have been created.

This chapter contains these sections:

- Section 4.1, "Configuring Oracle GoldenGate Monitor Server for Oracle Databases"

- Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases"

- Section 4.3, "Completing Monitor Server Configuration"

- Section 4.4, "Starting Oracle GoldenGate Monitor Server"

4.1 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 MySQL or SQL Server database, see Section 4.2, "Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases".

4.1.1 The Configuration Wizard

You will use the Configuration Wizard to create the domain. 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 datasources 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 Creating WebLogic Domains Using the Configuration Wizard.

4.1.2 Launching the Configuration Wizard

Assuming WebLogic Server is installed properly (see Section 2.2, "Install WebLogic Server 12c (12.1.3)"), launch the Configuration Wizard by doing the following:

On Linux:

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

On Windows:

C:\ORACLE_HOME\wlserver\common\bin>config.cmd

The Configuration Wizard starts and the Configuration Type screen appears.

4.1.3 Creating the Domain

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/oggmon1213_domain

- Click Next.

Templates

1. Select Oracle GoldenGate Monitor Server Domain-12.1.3 (oggmon)

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.7.0_45/ade_autofs/gd29_3rdparty/nfsdo_generic/JDL7/MAIN/LINUX.X64/

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.

Note:
This completes the first steps of configuring Oracle GoldenGate Monitor Server for Oracle databases. The next section contains procedures pertaining only to non-Oracle databases (that is, MySQL or Microsoft SQL Server). Unless you are also configuring the server for one of these databases, you can skip this section and proceed to Section 4.3, "Completing Monitor Server Configuration".

4.2 Configuring Oracle GoldenGate Monitor Server for Non-Oracle Databases

In addition to Oracle databases, Oracle GoldenGate Monitor also supports databases provided by MySQL and Microsoft SQL Server. The configuration instructions covered in Section 4.1, "Configuring Oracle GoldenGate Monitor Server for Oracle Databases" applies only to that database provider. For these non-Oracle databases, you need to use the same tools but follow somewhat different procedures. Those procedures are explained in the following sections:

- Section 4.2.1, "Configuring a Domain for MySQL"

- Section 4.2.2, "Configuring a Domain for Microsoft SQL Server"

4.2.1 Configuring a Domain for MySQL

Configuring a domain for MySQL is a two-stage process:

1. Create the MySQL Repository

2. Create a Compact WebLogic Server Domain

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

Note:
When using a MySQL database, you can only create a compact domain. This is because the Oracle Platform Security Service and Auditing frameworks does not support maintaining the security artifacts and audit management data when using Weblogic Server 12c (12.1.3) on non-Oracle databases.

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.

Note:
When using a MySQL database, you can only create a compact domain. This is because, when using Weblogic Server 12c (12.1.3) on non-Oracle databases, the Oracle Platform Security Service and Auditing frameworks do not support maintaining the security artifacts and audit management data.

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 Configuring a Domain for Microsoft SQL Server

Configuring a domain for SQL Server is a two-stage process:

1. Create the SQL Server Repository

2. Create a Compact WebLogic Server Domain

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.

Note:
When using a SQL Server database, you can only create a compact domain. This is because, when using Weblogic Server 12c (12.1.3) on non-Oracle databases, the Oracle Platform Security Service and Auditing frameworks does not support maintaining the security artifacts and audit management data.

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 Completing Monitor Server Configuration

The final steps in configuring Oracle GoldenGate Monitor Server are manual and comprise the following steps:

- Edit Monitor Properties

- Complete the SNMP Alerts Configuration

- Complete the CLI Configuration

4.3.1 Edit Monitor Properties

The monitor.properties file resides in ../wlsdomains/oggmon_domain/config/monitorserver/cfg. To continue configuring the monitor server, open this file and edit it by doing the following:

- Configure the JMX Server Properties

- Configure SMTP Alert Properties

- Configure SNMP Alert Properties

- Configure Command Line Interface (CLI) Alert Properties

Configure the JMX Server Properties

Configure the JMX server by setting these properties:

- monitor.jmx.server.host=hostname

- monitor.jmx.server.port=portNumber

Where hostname is the name of the host on which you are running the product (for example, localhost) and portNumber is number of the host's listening port (for example, 5502).

Configure Target Database Properties

Uncomment one of the lines below that applies to the database you are configuring for Oracle GoldenGate Monitor Server.

For Oracle:

#eclipselink.target-database=org.eclipse.persistence.platform.database.OraclePlatform

For SQL Server:

#eclipselink.target-database=org.eclipse.persistence.platform.database.SQLServerPlatform

For MySQL:

#eclipselink.target-database=org.eclipse.persistence.platform.database.MySQLPlatform

Configure SMTP Alert Properties

Set monitor.smtp.alerts.enabled property to true to enable SMTP alerts. Set the remaining properties as necessary to enable receipt of SMTP alerts; for example:

monitor.smtp.alerts.enabled=true
monitor.smtp.secure=false
monitor.smtp.host
monitor.smtp.port
monitor.smtp.from
monitor.smtp.user

Configure SNMP Alert Properties

Set monitor.snmp.alerts.enabled to true to enable SNMP alerts; for example:

monitor.snmp.alerts.enabled=true

Configure Command Line Interface (CLI) Alert Properties

Set monitor.cli.alerts.enabled to true to enable CLI alerts; for example:

monitor.cli.alerts.enabled=true

4.3.2 Complete the SNMP Alerts Configuration

The Oracle GoldenGate Monitor Simple Network Management Protocol (SNMP) interface sends alerts in the form of datagrams. These are picked up by an SNMP trap recipient listening on a specified port.

To use this feature you must enable SNMP alerts during installation or later set the monitor.snmp.alerts.enabled property equal to true in the monitor.properties file.

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 Complete the CLI Configuration

The Oracle GoldenGate Monitor Command-Line Integration (CLI) allows you to run a script or object file on the Oracle GoldenGate Monitor Server when an alert is triggered.

To use this feature you must enable CLI alerts by checking the CLI alerts box during installation or later setting the monitor.cli.alerts.enabled property equal to true in the monitor.properties file.

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.

4.3.3.1.1 Command-Line Handler Arguments

The example UNIX configuration below illustrates the structure and arguments of the XML configuration file. The header values should not be changed. These values specify the version and coding of the XML.

Arguments are specified by entering a value within quotation marks after the equal sign (=) as shown in the example. In this illustration namespace and schema information has been omitted as indicated by the ellipses (. . .).

<?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 is the parent tag for the CLI alert handler. This is specified within the CommandLineHandlers tags.

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

The CommandLineHandler tag includes the following arguments:

- dateTimeFormat
This is the standard Java format argument described in Java documentation.

- executeIn
The executeIn argument triggers the processing to move into the specified directory before running the external script or object file. The default is to use the current run directory of the virtual machine (VM); the directory in which the script or command was started.

A RunTimeException is generated when the alert is triggered if the specified directory does not exist or if the executeIn attribute is empty or not present.

- name
This will always be "CMDLINE".

The following example illustrates the tags that can be nested within the CommandLineHandler tags:

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

- externalCommand
The value in externalCommand specifies the absolute path to the script or object file. If the system path environment variable points to the directory of the file to be run, you can specify the script or object file name without the path.

- arguments
The arguments tag specifies one or more values that are appended to the directory value specified in the externalCommand tag.

For each argument the following attributes can be specified:

argText - Specifies a literal text argument that is sent with the externalCommand tag.

name - Can be a name or it can work with alertMappings to find a name as explained below.

presentIfEmpty - Works with the alertMappings tag to add selected information associated with the alert definition to the externalCommand tag. See alertMappings below for more detail.

quoted - Specifies whether quotation marks should be added.

- alertMappings
The alertMappings tag appends the value extracted from the alert definition information to the value specified in the externalCommand tag.

<alertMappings>
<alertMapping alertField="host" name="hostname"/>
</alertMappings>

The alertField can be one of the following values associated with the alert definition:

alertName - The name of an alert definition.

host - The host of the Oracle GoldenGate object whose monitoring point triggers the alert.

alertObjectName - The name associated with the object whose monitoring point triggers the alert, such as an Extract process named EXACCT.

alertTime - The time that the alert was triggered.

alertSeverity - The severity level defined for the alert; either Warning or Error.

alertMessage - The message generated by the alert. This is a combination of the condition defined for the alert, the value of the monitoring point, and literal text.

changedValue - The new monitoring point value that triggered the alert. For example, you create an alert that is triggered when lag is greater than 5 seconds. The lag is 4 seconds and then it goes to 7 seconds. This triggers the alert and the changedValue is 7.

In the following example, the name attributes in the argument and the alertMapping tags are matched to extract the value from the alertField attribute. The argument name "hostname" is matched to the alertMapping name "hostname" to find the value of alertField, which is "host". This tells the system to append the host of the Oracle GoldenGate object that triggered the alert to the value specified in the externalCommand tag.

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

The presentIfEmpty attribute works with the alertMappings tag to determine what to do if the alertField is not valid or the name attributes do not match:

- presentIfEmpty="true"
The value in the argText attribute is used in the external command.

- presentIfEmpty="false"
The entire argument is omitted.

4.3.3.2 Sample Command-Line Handlers

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

4.3.3.2.1 Running on a Windows Server

The following example runs the batch script sample_cli.bat on a Windows server hosting the Oracle GoldenGate Monitor Server. The server of the Oracle GoldenGate instance ("host") that triggered the alert is appended to the name of the batch script specified in the externalCommand.

<?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>

4.3.3.2.2 Running on a UNIX Host

The following example runs the sample_cli.sh script on the UNIX server hosting the Oracle GoldenGate Monitor Server. The server of the Oracle GoldenGate instance ("host") that triggered the alert is appended to the name of the batch script specified in the externalCommand.

<?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>

4.4 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:

- Start the WebLogic Administration Server

- Update Oracle GoldenGate Monitor Server Credentials (Optional)

- Start the WebLogic Managed Server

4.4.1 Start the WebLogic Administration Server

To start the Administration server, do the following:

1. Navigate to the MONITOR_DOMAIN folder (for example, /apps/oggmon_domain�; apps\oggmon_domain in 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.

4.4.2 Update Oracle GoldenGate Monitor Server Credentials (Optional)

Note:
This step 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 Understanding the WebLogic Scripting Tool

4.4.3 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.

5 Managing Users from the WebLogic Administration Console

With Oracle GoldenGate Monitor Server installed and configured, you can now use the WebLogic Server Administration Console to manage your users. You can then launch the Oracle GoldenGate Monitor console and start monitoring. These procedures are described in the following sections:

- Section 5.1, "Log-in to Oracle WebLogic Server Administration Console"

- Section 5.2, "Create a User"

- Section 5.3, "Add the User to a Group"

- Section 5.4, "Start the Oracle GoldenGate Monitor Console"

Note:
Before attempting any of the tasks in this chapter, ensure that both the WebLogic administration server is running. You can find server start-up instructions in Section 4.4.1, "Start the WebLogic Administration Server".

5.1 Log-in to Oracle WebLogic Server Administration Console

To log in to the Oracle WebLogic Server Administration Console, do the following:

1. Open a Web browser and navigate to your administration server by entering the administration machine name and port in the navigation bar; for example:

The Console Welcome page appears. This page contains a form where you can enter your log-in credentials.

2. Enter a Username and Password and click Login:

The Oracle WebLogic Server Administration Console appears, with the home page displayed in the main panel. To the left of the main panel are links that will help you navigate the console. For more information on the Oracle WebLogic Server Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.

5.2 Create a User

You begin user creation from the Oracle WebLogic Server Administration Console home page. Use this procedure:

1. Left of the main panel, locate the Domain Structure panel for your domain:

2. From the Domain Structure tree, select Security Realms.
The Summary of Security Realms page appears in the main panel.

3. In the Realms table, select myrealms.
The Settings for myrealm page appears in the main panel.

4. Click Users and Groups.
The Users tab opens.

5. Click Add.
The Create a New User page appears.

6. Add the new users details:

- User name; this name will be used to log in to the Oracle GoldenGate Monitor console.

- A brief freeform description of the user.

- The user provider, selected from the dropdown list.

- A password for the user (with confirmation entry). This password will be used with the user name to log in to the Oracle GoldenGate Monitor console. It must be at least eight characters long

- Click OK.
The User tab reappears with the new user added.

5.3 Add the User to a Group

Next, you need to add the user you created in Section 5.2, "Create a User" to a group. To do so, use this procedure.

1. On the Settings for myrealms' User tab, click the name of the user you just added.
The Settings for username page appears.

2. Click Groups.
The Groups tab opens, displaying a list of parent groups to which the user can belong.

3. Select the parent groups to which you want the user to belong and click the right arrow ( ).
The selected groups will move to the Chosen list.

If you want to make the user a member of all groups, rather than select each group, just click the double right arrow ( ). All groups will move to the Chosen list. If you accidently add a group you did not intend, select it and click the left arrow. To remove all groups from the Chosen list, click the double left arrow.

4. Click Save.

5.4 Start the Oracle GoldenGate Monitor Console

Finally, you are ready to launch the Oracle GoldenGate Monitor Server console. To do so, use this procedure.

1. In the Web browser navigation bar, the Oracle GoldenGate Monitor Server URL in this format:

http://hostname:portNumber/monitor/faces/loginPage.jspx

Where hostname is the system on which WebLogic Server is installed and the portnumber is 7003, which is the managed server port number (because the application is being deployed on a managed server, MONITOR_server1); for example

http://slc03abc:7003/monitor/faces/loginPage.jspx

The Oracle GoldenGate Monitor Server log-in screen appears.

2. Provide the log-in credentials entered for the user in step 6 of Section 5.2, "Create a User"and click Submit.
The Oracle GoldenGate Monitor Server console opens. You can now start administering Oracle GoldenGate Monitor.

6 Deinstalling Monitor Server

This chapter describes how to deinstall Oracle GoldenGate Monitor Server. It contains these sections:

- Section 6.1, "Stop the Servers"

- Section 6.2, "Drop the Repositories"

- Section 6.3, "Delete the WebLogic Domain"

- Section 6.4, "Deinstall Oracle GoldenGate Monitor Server"

6.1 Stop the Servers

First, stop any running Oracle GoldenGate Monitor managed servers. and, if necessary, the WebLogic administration server.

To stop the Managed Server(s):

To stop the managed server, navigate to OGGMON_DOMAIN/bin (OGGMON_DOMAIN\bin on Windows) and enter the following command:

On Linux:

$ ./stopManagedWebLogic.sh MONITORSERVER_server1

On Windows:

C:\path\to\bin> stopManagedWebLogic.cmd

Note:
If you are stopping a managed server after stopping the administration server, you need to specify the managed server's URL in the stop script; for example (on Linux):

$ ./stopManagedWebLogic.sh MONITORSERVER_server1 t3://hostname:ManagedServerPort"

To stop the Administration Server:

You only need to stop the WebLogic administration server if your domain contains only the Oracle GoldenGate Monitor application and you plan to delete the domain.

To stop an Administration Server, navigate to DOMAIN_HOME/bin (DOMAIN_HOME\bin on Windows) and enter:

On Linux:

$ ./stopWebLogic.sh username password [admin_url]

On Windows

C:\path\to\bin>stopWebLogic.cmd username password [admin_url]

6.2 Drop the Repositories

Next, you must run the Repository Creation Unit (RCU) to drop the repositories you created during the repository creation stage described in Section 3.2, "Creating a Repository".

To drop repositories:

1. Navigate to ORACLE_HOME/oracle_common/bin/ (ORACLE_HOME\oracle_common\bin\ on Windows) and enter:
On Linux:

$ ./rcu.sh

On Windows:"

C:\path\to\bin> rcu.cmd

The RCU Welcome screen appears.

2. Click Next.
The Create Repository screen appears.

3. Select Drop Repository and click Next.
The Database Connection Details appears.

4. Enter the connection details for the database you are dropping and click Next.
A confirmation window opens, verifying that the Global Prerequisites are implemented.

5. Click OK.
The Select Components screen appears.

6. Click Next and continue through the RCU process, as described in Section 3.2, "Creating a Repository".
After you click Close on the Completion Summary screen, the repository will be dropped.

6.3 Delete the WebLogic Domain

Next, you need to delete the WebLogic domain you created in Section 4.1, "Configuring Oracle GoldenGate Monitor Server for Oracle Databases". To do this, simply delete the domain folder from your file system.

6.4 Deinstall Oracle GoldenGate Monitor Server

Finally, to complete the deinstall process, you need to deinstall Oracle GoldenGate Monitor Server.

To deinstall Oracle GoldenGate Monitor Server:

1. Navigate to ORACLE_HOME/oui/bin (ORACLE_HOME\oui\bin on Windows) and enter
On Linux:

$./deinstall.sh

On Windows:

C:\path\to\bin>deinstall.cmd

The deinstallation program launches and the Welcome screen appears.

2. Navigate through the deinstallation screens as described in the following table. For additional information on any of the deinstallation screens, click the screen name.

Screen

Description/Action

Welcome

This screen introduces you to the product deinstaller.

Deinstallation Summary

This screen shows the Oracle home directory and its contents that will be deinstalled. Verify that this is the correct directory.
Click Deinstall to begin removing the software.

Deinstallation Progress

This screen shows the progress of the deinstallation.

Deinstallation Complete

This screen appears when the deinstallation is complete. Review the information on this screen then click Finish to dismiss the deinstaller.

Oracle GoldenGate Monitor Server is successfully removed from your system.

7 Moving from a Test to a Production Environment

This chapter describes the procedures for moving Oracle GoldenGate Monitor Server from a test environment to a production environment ("T2P"). It contains the following sections:

- Section 7.1, "Prerequisites"

- Section 7.2, "Preparing the Test Environment"

- Section 7.3, "Preparing the Production Environment"

- Section 7.4, "Verifying the Move"

- Section 7.5, "Additional Information"

Note:
Oracle GoldenGate Monitor does not support test-to-production for compact domains because these types of domains are not intended for production environments. Expanded Domains are used for Oracle databases; compact domains are used for non-oracle databases; for example, MySQL and SQL Server.

7.1 Prerequisites

Before moving Oracle GoldenGate Monitor Server from a test to a production environment, ensure that Oracle GoldenGate is installed and is configured on both the source and target environments for enabling Oracle GoldenGate monitoring using Oracle GoldenGate agent.

7.2 Preparing the Test Environment

To prepare the test environment, install the Oracle WebLogic Server infrastructure and then do the following:

1. Create a database instance by using the Repository Creation Utility (RCU). For instructions, see Section 3.2, "Creating a Repository".

2. Install and configure Oracle GoldenGate Monitor 12c (12.1.3), in this order:

1. Oracle GoldenGate Monitor Server

2. Oracle GoldenGate agent

7.3 Preparing the Production Environment

This section contains information on how to prepare the production, or "target" environment.

7.3.1 Before You Begin

Your target environment must meet the following prerequisites:

- You must use the cloningclient.jar file and the pasteBinary script file that are compatible with the version of the ORACLE_HOME and components that you want to copy. The procedures in this chapter presume that you are using the current version of the cloningclient.jar file and movement scripts.

- The target environment must be on the same operating system as the source environment. Also, the operating system architecture must be the same in both environments. For example, both environments must be running 32-bit operating systems or 64-bit operating systems.

- The host must have JDK 1.6.04 or higher installed. In addition, ensure that the PATH, CLASSPATH, and JAVA_HOME environment variables point to the JDK. When you execute the scripts, you must specify a matching Java home. That is, if the Oracle homes are 64 bit, you must specify a 64-bit Java home. If the Oracle homes are 32 bit, you must specify a 32-bit Java home.

- The target environment must have the same superuser or administrative user as the user at the source environment. After you complete the movement of the installation, you can modify the user on the target environment.

7.3.2 Preparing the Environment

To prepare the production environment for an Oracle Database, do the following:

1. Create new database Instance using by RCU, as described in Section 3.2, "Creating a Repository".
Note that the database in the target environment must be the same type and version of database as in the source environment; for example, if the database in the source environment is an Oracle database, the database in the target environment must also be an Oracle database.

2. Copy and paste WLS_JRF binary files to the target environment by using the T2P scripts copyBinary.sh (.cmd on Windows) and pasteBinary.sh; (.cmd) for example:

Note:
The scripts used in the following examples—called movement scripts—are located in ORACLE_HOME/oracle_common/bin/ (ORACLE_HOME\oracle_common\bin\ on Windows). For more information on the Move scripts, see "Movement Scripts and Move Plans" in Administering Oracle Fusion Middleware.

To copy:

On Linux:

./copyBinary.sh -javaHome /usr/local/packages/jdk7
-archiveLoc /scratch/myuser/T2P/oh_copy.jar
-sourceOracleHomeLoc /scratch/myuser/WLS_12.1.3_HOME

On Windows:

>copyBinary.cmd -javaHome C:\Program Files\Java\jdk1.7.0_51
-archiveLoc userhome\T2P\oh_copy.jar
-sourceOracleHomeLoc userhome\WLS_12.1.3_HOME

To paste:

First, copy the pasteBinary script and the cloningclient.jar file to the target system and ensure that they have execute permission. cloningClient.jar is located in ORACLE_COMMON_HOME/jlib/cloningclient.jar (Linux) or ORACLE_COMMON_HOME\jlib\cloningclient.jar (Windows).

Then, depending on your O/S, do one of the following:

On Linux:

./pasteBinary.sh -javaHome /usr/local/packages/jdk7
-archiveLoc  /scratch/myuser/T2P/oh_copy.jar
-targetOracleHomeLoc /scratch/myuser/WLS_1213_COPY_HOME
-targetOracleHomeName WLS_1213_COPY_HOME_1

On Windows:

>pasteBinary.cmd -javaHome C:\Program Files\Java\jdk1.7.0_51
-archiveLoc  userhome\T2P\oh_copy.jar
-targetOracleHomeLoc userhome\WLS_1213_COPY_HOME
-targetOracleHomeName WLS_1213_COPY_HOME_1

3. Using any text editor, create a new text file called adminuser_password.txt and enter a password for the Oracle WebLogic Server administrative user (for example, weblogic) in the file and save it. This file will be used in next step.

4. Use the copyConfig script to copy the Oracle GoldenGate Monitor Weblogic domain configuration to the target environment; for example:

Note:
Before you execute the copyConfig.sh script in a WebLogic Server domain, make sure that the Administration Server and Managed Servers are running.

On Linux:

./copyConfig.sh -javaHome /usr/local/packages/jdk7
-archiveLoc /scratch/myuser/T2P/oggmon_domain.jar
-sourceDomainLoc /scratch/myuser/OGGMON_INSTALLS/oggmon_domain
-sourceOracleHomeLoc /scratch/myuser/WLS_12.1.3_HOME
-domainHostName myhost.example.com
-domainPortNum 7001
-domainAdminUserName weblogic
-domainAdminPasswordFile /scratch/myuser/T2P/adminuser_password.txt

On Windows:

>copyConfig.cmd -javaHome C:\Program Files\Java\jdk1.7.0_51
-archiveLoc userhome\T2P/oggmon_domain.jar
-sourceDomainLoc userhome\OGGMON_INSTALLS\oggmon_domain
-sourceOracleHomeLoc userhome\WLS_12.1.3_HOME -domainHostName myhost.example.com
-domainPortNum 7001 -domainAdminUserName weblogic
-domainAdminPasswordFile userhome\T2P\adminuser_password.txt

5. Use the extractMovePlan. script to extract the move plan from the domain configuration jar file (oggmon_domain.jar) so you can make required updates to the target environment; for example:
On Linux:

./extractMovePlan.sh -javaHome /usr/local/packages/jdk7
-archiveLoc /scratch/myuser/T2P/oggmon_domain.jar
-planDirLoc /scratch/myuser/T2P/extract_plans

On Windows:

>extractMovePlan.cmd -javaHome C:\Program Files\Java\jdk1.7.0_51
-archiveLoc userhome\T2P\oggmon_domain.jar
-planDirLoc userhome/T2P\extract_plans

For information about the properties in the move plans, and which properties you should edit, see "Modifying Move Plans" in Administering Oracle Fusion Middleware.

6. Use the pasteConfig script to paste the generated configuration into the target environment; for example:
On Linux:

./pasteConfig.sh -javaHome /usr/local/packages/jdk7
-archiveLoc /scratch/myuser/T2P/oggmon_domain.jar
-targetDomainLoc /scratch/myuser/OGGMON_INSTALLS/oggmon_domain_copy
-targetOracleHomeLoc /scratch/myuser/WLS_1213_COPY_HOME
-movePlanLoc /scratch/myuser/T2P/extract_plans/moveplan.xml
-domainAdminPasswordFile /scratch/myuser/T2P/adminuser_password.txt
-logDirLoc /scratch/myuser/T2P/log

On Windows:

>pasteConfig.cmd -javaHome C:\Program Files\Java\jdk1.7.0_51
-archiveLoc userhome\T2P\oggmon_domain.jar
-targetDomainLoc userhome\OGGMON_INSTALLS\oggmon_domain_copy
-targetOracleHomeLoc userhome\WLS_1213_COPY_HOME
-movePlanLoc userhome\T2P\extract_plans\moveplan.xml
-domainAdminPasswordFile userhome\T2P\adminuser_password.txt
-logDirLoc userhome\T2P\log

7. Update the Oracle GoldenGate Monitor Server configuration by doing the following:

- Update these Oracle GoldenGate Monitor Server configuration files:

- monitor.properties

- SNMPJMXMapping.xml

- CommandLineHandlers.xml

- Move the SSL certificates manually to the target environment. For information about using SSL with Oracle GoldenGate Monitor, see "Using SSL Communication" in Administering Oracle GoldenGate Monitor.

- Using the WebLogic Scripting Tool (WLST), update Oracle GoldenGate Monitor Server-related passwords for target environment. For more information on using WLST, see Understanding the WebLogic Scripting Tool.

8. Install and configure Oracle GoldenGate agent software on the target machine. For instructions, see Installing and Configuring Oracle GoldenGate Monitor Agent.

Note:
T2P scripts are not available for standalone products, like Oracle GoldenGate agent.

7.4 Verifying the Move

Verify that the T2P move was successful by doing the following:

1. Start the administration server, as described in Section 4.4.1, "Start the WebLogic Administration Server" and managed server, as described in Section 4.4.3, "Start the WebLogic Managed Server".

2. Go to Oracle GoldenGate Core GGSCI terminal and start Oracle GoldenGate Monitor Agent by executing the start jagent command:

GGSCI>start jagent

If everything starts successfully, the T2P process is complete.

7.5 Additional Information

For more information on moving from a test to a production environment, see the following chapters in Administering Oracle Fusion Middleware:

- "Moving from a Test to a Production Environment"

- "Movement Scripts and Move Plans"

A Installation and Configuration Screens

This appendix contains images and descriptions of the Oracle GoldenGate-specific screens used by the Oracle Universal Installer (OUI). This information is contained in the following sections:

- Section A.1, "Installation Screens for Oracle GoldenGate Monitor"

- Section A.2, "Repository Creation Utility (RCU) Screens for Oracle GoldenGate Monitor"

- Section A.3, "Configuration Wizard Screens for Oracle GoldenGate Monitor"

A.1 Installation Screens for Oracle GoldenGate Monitor

This section shows examples of the Oracle Universal Installer screens for Oracle GoldenGate Monitor. These screens are:

- Welcome

- Installation Location

- Installation Type

- Prerequisite Checks

- Installation Summary

- Installation Progress

- Installation Complete

A.1.1 Welcome

This screen introduces you to the product installer.

This page provides two important pieces of information:

- A navigation pane on the left that summarizes the tasks the installer will help you complete. Each item in the navigation pane represents a specific installer screen that will prompt you for information required to install the software.

- Information about any prerequisites you might need to perform before continuing with the installation.

Review the information on this screen carefully to be sure you have performed all the necessary prerequisites.

A.1.2 Installation Location

Use this screen to specify the location of your Oracle home directory.

If you have an existing directory into which one or more Oracle products have already been installed, that directory can be viewed in the drop-down list. You can see which products are installed in that particular directory by clicking View next to "Features Sets Installed at Selected Oracle Home."

If you want your product to be installed in a new directory, type the full path of your new directory in the Oracle Home field; the installer will create the specified directory for you.

If you are installing Oracle Fusion Middleware Infrastructure, then the Oracle Common home (oracle_common) directory will be created inside the specified Oracle home directory. The Oracle Common home contains services that are shared across all Oracle Fusion Middleware products.

A.1.3 Installation Type

Use this screen to specify the installation type, which defines which products and features are installed.

The options you see on this screen will differ depending on the product you are installing. Refer to Section 3.1.3, "Install the Product" for specific details.

A.1.4 Prerequisite Checks

This screen analyzes the host computer to ensure that specific operating system prerequisites have been met.

The following table describes the options on this screen:

Button

Description

Stop

Click this button to stop prerequisite checking for all components.

Rerun

Click this button if you have encountered any warning or error messages, addressed them appropriately, and want to try the prerequisite checking again.

Skip

Click this button to ignore any error or warning messages and continue with the installation.

View Successful Tasks

This check box is selected by default, and shows the list of tasks in the main part of the screen as they are completed.
De-select this check box if you do not want to see the list of tasks.

View Log

Click this button to open a separate window containing a detailed log file of the prerequisite checking.

A.1.5 Installation Summary

This screen contains a list of the feature sets you selected for installation, along with the approximate amount of disk space to be used by the feature sets once installation is complete.

You can click an individual component to display its approximate installed size.

Click Save Response File to save this configuration to a response file, which can be used later in a silent install situation. See Chapter 2, "Using the Oracle Universal Installer in Silent Mode" in Installing with the Oracle Universal Installer for more information about response file and silent installation.

A.1.6 Installation Progress

This screen shows the progress of the installation. When the progress bar reaches 100%, the installation is complete.

The following table describes the options on this screen.

Button

Description

View Messages

Click View Messages to see the installer messages at the bottom of the screen, where the billboard is located. Click the button again to return to the billboard.

View Successful Tasks

This check box is selected by default, and shows the list of tasks in the main part of the screen as they are completed.
De-select this check box if you do not want to see the list of tasks.

View Log

Click View Log to see the installer log; the log will be displayed in a separate window.

A.1.7 Installation Complete

This screen appears at the conclusion of the installation and provides a summary of the products and features that were installed.

A.2 Repository Creation Utility (RCU) Screens for Oracle GoldenGate Monitor

This section provides sample images of the screens used to create a data repository for Oracle GoldenGate Monitor Server. These screens are:

- Welcome

- Create Repository

- Database Connection Details

- Select Components

- Schema Passwords

- Map Tablespaces

- Summary

- Completion Summary

The following examples comprise an overview of the RCU screens that apply to Oracle GoldenGate Monitor. For more detailed information on these screen and repository creation in general, see Creating Schemas with the Repository Creation Utility, particularly "Understanding Repository Creation Utility Screens".

A.2.1 Welcome

This screen introduces you to the product installer.

A.2.2 Create Repository

Use this screen to select the action you want to perform.

A.2.3 Database Connection Details

Use this screen to specify the connection credentials to the database in which you will be creating or dropping your schemata.

A.2.4 Select Components

Use this screen to select the components for the database you are creating. Components will vary depending upon which database you will be running.

A.2.5 Schema Passwords

Use this screen to define the passwords for the main and auxiliary scheme users.

A.2.6 Map Tablespaces

This screen lists the tablespaces for the selected components.

A.2.7 Summary

This screen summarizes the details of the repository you are creating.

A.2.8 Completion Summary

This screen contains information about the log files that were created from this RCU operation. You can click on the name of a particular log file to view the contents of that file.

If there were any problems encountered during schema creation, you can troubleshoot the issue by using the log files.

If errors are encountered during a Create operation, or if a Create operation fails for any component, the Cleanup for failed components check box appears on this page and is selected by default. If selected, RCU will perform cleanup operations for the component that failed during the Create operation. If you choose not to select this check box, you can cleanup the failed component at a later time by performing a Drop operation for the failed component(s).

A.3 Configuration Wizard Screens for Oracle GoldenGate Monitor

This section provides samples of the screens used to configure a Oracle WebLogic Server domain for Oracle GoldenGate Monitor Server. These screens are:

- Configuration Type

- Templates

- Administrative Account

- Domain Mode and JDK

- Database Configuration Type

- JDBC Component Schema

- JDBC Component Schema Test

- Credentials

- Advanced Configuration

- Administration Server

- Managed Servers

- Clusters

- Coherence Cluster

- Machines

- Configuration Summary

- Configuration Progress

- Configuration Success

The following examples comprise an overview of the Configuration Wizard screens that apply to Oracle GoldenGate Monitor. For more detailed information on these screens and domain configuration in general, see Creating WebLogic Domains Using the Configuration Wizard.

A.3.1 Configuration Type

Use this screen to define why you are using the Configuration Wizard: to create a new domain or update an existing domain.

A.3.2 Templates

Use this screen to choose whether to create or extend a domain that is configured automatically to support selected products, or to create or extend a domain based on an existing domain or application template. Each template in the displayed list is associated with a single product template (a JAR file) which configures the required domain resources for the product. If the selected template has dependencies on other templates, the dependency templates are automatically selected or included in the domain.

A.3.3 Administrative Account

Use this screen to define the default WebLogic Administrator account for the domain. This account is used to boot and connect to the domain's Administration Server.

A.3.4 Domain Mode and JDK

Use this section to specify whether you want to run Oracle GoldenGate Monitor in Production mode or Development mode.

A.3.5 Database Configuration Type

Use this screen to specify the information for connecting to the database to retrieve schema information that will be used to populate the schema fields on subsequent component schema screens.

A.3.6 JDBC Component Schema

Use this screen to configure the JDBC component schema settings, such as database driver, schema owner, password, and so on.

A.3.7 JDBC Component Schema Test

Use this screen to test the configurations that you specified for the data sources in the previous screen. Note that:

- If the JDBC driver JAR file for a data source is not in the classpath, the data source is not selectable for testing.

- If you are updating a domain, all data sources that exist in the original domain are not selected by default. Only new data sources are selected and tested by default.

A.3.8 Credentials

Use this screen to provide credentials for each key in the domain.

A.3.9 Advanced Configuration

Use this screen to select the categories (if any) for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration. If you do not select any items on this screen, the Configuration Summary screen is displayed next.

Note:
The categories that are listed on this screen depend on the resources defined in the templates you selected for the domain.

A.3.10 Administration Server

Use this screen to configure or change the following Administration Server settings.

- Server

- Listen address

- Listen port

- Enable SSL

- SSL listen port

- Server Groups

A.3.11 Managed Servers

Use this screen to add, delete, or clone Managed Servers, and assign a user-expandable server group (if available) to a Managed Server. You can also change the settings for an existing Managed Server.

A.3.12 Clusters

Use this screen to add or delete clusters. You can also change the Cluster Name and Cluster Address settings for an existing cluster.

A.3.13 Coherence Cluster

This screen is displayed only if you included Coherence in the WebLogic Server installation.

A.3.14 Machines

Use this screen to add or delete machines, or to modify the settings for an existing machine.

A.3.15 Configuration Summary

Use this screen to review the detailed configuration settings of your domain before continuing.

A.3.16 Configuration Progress

This screen uses a progress bar and message panel to indicate the progress of your domain configuration process.

A.3.17 Configuration Success

This screen appears when domain creation has successfully completed.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.