Installation and Configuration

Transcription

TIBCO® MDM Administration
Agent
Installation and Configuration
Software Release 1.0
November 2013
Two-Second Advantage®
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, Two-Second Advantage, TIBCO Hawk, TIBCO Rendezvous, TIBCO Runtime Agent, TIBCO
ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer, TIBCO ActiveMatrix Service Gateway,
TIBCO BusinessEvents, TIBCO BusinessConnect, and TIBCO BusinessConnect Trading Community
Management are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or
other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition
(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation
in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
This Product is covered by U.S. Patent No. 7,472,101
Copyright © 1999-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
|3
Contents
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
TIBCO MDM Administration Agent Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
TIBCO MDM Administration Agent Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
TIBCO MDM Administration Agent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
TEA Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Chapter 2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Installation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Installing TIBCO MDM Administration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Installing in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Installing in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Installation File System Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Installer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Chapter 3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Setting Java Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
WebSphere and IBM JDK Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
TIBCO MDM Administration Agent Installation and Configuration
4
| Contents
Configuring Agent Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Example Agent Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuring MDM Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Preparing Startup and Shutdown Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Example Cluster Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Starting TIBCO MDM Administration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Verifying TIBCO MDM Administration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 4 MDM Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Managing MDM Instances with TIBCO MDM Administration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Accessing the MDM Product View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Accessing the MDM Instance View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Accessing the MDM Components View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Accessing the MDM Solutions View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solutions View: Critical Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solutions View: Cache Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solutions View: Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
47
48
50
Chapter 5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Troubleshooting Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent Does Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent Unable to Connect to MDM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent Unable to Connect to TEA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MDM Instance Status Is Inconsistent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
No MDM Instances Are Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
54
54
54
55
56
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Tables 5
|
Tables
Table 1
General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 2
Syntax Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 3
Agent Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4
Cluster Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 5
Cluster Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 6
Instance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 7
Instance View Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 8
Critical Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 9
Cache Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 10
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6
| Tables
|7
Preface
This software may be available on multiple operating systems. However, not
all operating system platforms for a specific software version are released at the
same time. Please see the readme file for the availability of this software
version on a specific operating system platform.
TIBCO MDM Administration Agent is a web application that implements an
interface to TEA servers. TIBCO MDM Administration Agent links MDM with
TIBCO Enterprise Administrator (TEA), allowing users to manage MDM
instances through the TEA interface.
Topics
•
Related Documentation, page 8
•
Typographical Conventions, page 10
•
Connecting with TIBCO Resources, page 13
8
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO MDM Administration Agent Documentation
The following documents form the TIBCO MDM Administration Agent
documentation set:
•
TIBCO MDM Administration Agent Installation and Configuration Read this
manual for information about preparing, installing, configuring, and
managing TIBCO MDM Administration Agent.
•
TIBCO MDM Administration Agent Release Notes Read the release notes for a
list of new and changed features. This document also contains lists of known
issues and closed issues for this release.
Other TIBCO Product Documentation
You may find it useful to read the documentation for the following TIBCO
products:
•
TIBCO MDM Installation and Configuration Read this manual for instructions
on site preparation and installation.
•
TIBCO MDM User’s Guide This manual explains features and benefits of
TIBCO MDM from the business user’s viewpoint. It describes the manual and
functionality as well as all the screens.
•
TIBCO MDM System Administration This manual explains features relevant to
the system administrator.
•
TIBCO MDM Customization Read this manual to how the application can be
customized to your enterprise needs.
•
TIBCO MDM Workflow Reference This manual is a reference for automation of
business processes.
•
TIBCO MDM Web Services This manual is a reference for using web services.
•
TIBCO MDM Release Notes Read the release notes for a list of new and
changed features. This document also contains lists of known issues and
closed issues for this release.
You may also find it useful to read the documentation for the following TIBCO
products:
Preface 9
|
•
TIBCO TEA™ software: TIBCO TEA provides a single point of entry for
multi-product enterprise deployments. This increases ease of use for the
management and monitoring of runtime artifacts, and simplifies
deployments, provisioning, and upgrading.
10
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
ENV_NAME
TIBCO products are installed into an installation environment. A product
installed into an installation environment does not access components in other
installation environments. Incompatible products and multiple instances of the
same product must be installed into different installation environments.
TIBCO_HOME
MDM-AGENT_
HOME
An installation environment consists of the following properties:
•
Name Identifies the installation environment. This name is referenced in
documentation as ENV_NAME. On Microsoft Windows, the name is
appended to the name of Windows services created by the installer and is a
component of the path to the product shortcut in the Windows Start > All
Programs menu.
•
Path The folder into which the product is installed. This folder is referenced
in documentation as TIBCO_HOME.
TIBCO MDM Administration Agent installs into a directory within a
TIBCO_HOME. This directory is referenced in documentation as
MDM-AGENT_HOME. The default value of MDM-AGENT_HOME depends on the
operating system. For example on Windows systems, the default value is
C:\tibco\mdm-agent\1.0
code font
Code font identifies commands, code examples, filenames, pathnames, and
output displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code
font
Bold code font is used in the following ways:
•
In procedures, to indicate what a user types. For example: Type admin.
•
In large code samples, to indicate the parts of the sample that are of
particular interest.
•
In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
Preface 11
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
italic font
Italic font is used in the following ways:
Key
combinations
•
To indicate a document title. For example: See TIBCO ActiveMatrix
BusinessWorks Concepts.
•
To introduce new terms For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
•
To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName
Key name separated by a plus sign indicate keys pressed simultaneously. For
example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply
the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example,
data loss or corruption if certain steps are taken or not taken.
Table 2 Syntax Typographical Conventions
Convention
Use
[ ]
An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
|
A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
12
| Typographical Conventions
Table 2 Syntax Typographical Conventions
Convention
Use
{ }
A logical group of items in a command. Other syntax notations may appear
within each logical group.
For example, the following command requires two parameters, which can be
either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter
can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters.
The first parameter must be param1. You can optionally include param2 as the
second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
Preface 13
|
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts. It is a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access TIBCO Documentation
You can access TIBCO documentation here:
http://docs.tibco.com
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact
TIBCO Support as follows:
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
14
| Connecting with TIBCO Resources
| 15
Chapter 1
Introduction
TIBCO MDM Administration Agent is a web application that implements an
interface to TEA servers. TIBCO MDM Administration Agent links MDM with
TEA, allowing users to manage MDM instances through the TEA interface.
Topics
•
TIBCO MDM Administration Agent Overview, page 16
•
TIBCO MDM Administration Agent Communication, page 17
•
TEA Terminology, page 18
16
| Chapter 1
Introduction
TIBCO MDM Administration Agent Overview
TIBCO® Enterprise Administrator (TEA) is a unified administrative interface
through which users can manage and monitor multiple TIBCO enterprise assets.
TEA provides an extensible administration platform to centralize the
management of various TIBCO® and non-TIBCO® products. TEA provides a
graphical user interface as well as a shell interface to view and administer your
enterprise assets. You can access the shell interface via SSH.
TIBCO® MDM is a tool to manage the master data of organizations by providing a
framework for governance, rules, and processes. TIBCO MDM ensures accuracy
and efficiency both inside the enterprise and throughout the value chain so that
multiple processes are optimally coordinated. TIBCO MDM delivers a
multi-domain horizontal platform to manage all types of information including
products, customers, vendors, reference data, backend systems.
TIBCO MDM Administration Agent is a standalone application that implements
an interface to TEA that allows users to stop, start, suspend, resume, and monitor
multiple instances of TIBCO MDM application servers.
TIBCO MDM Administration Agent Communication 17
|
TIBCO MDM Administration Agent Communication
TIBCO MDM Administration Agent communicates with TIBCO MDM
application servers via Java Management Extensions (JMX). The
mdm-agent.properties file facilitates communication with TIBCO MDM
instances. See Configuring Agent Properties File on page 29 for more details.
TIBCO MDM Administration Agent finds and connects the Java Virtual Machine
(JVM) of each MDM instance to the agent. One agent is installed on each MDM
server, and manages all MDM instances on that server. TIBCO MDM
Administration Agent manages the instances by handling all JVMs local to the
machine on which it’s installed.
If
If you are using IBM’s implementation of JDK 7, some additional configuration is
required. See WebSphere and IBM JDK Configuration on page 28 for more
information.
18
| Chapter 1
Introduction
TEA Terminology
Both TIBCO TEA and TIBCO MDM Administration Agent assign a unique
definition to concepts such as agent, server, solution, and cluster. These terms are
defined below as they are used by TEA and MDM Administration Agent.
Term
Definition
TEA Server
Server hosting TEA.
MDM Agent
TEA agent that manages MDM instances.
Solution
A collection of assets that provide a business function. Typically, multiple
products' application assets (such as applications, processes, resources, and
endpoints) together provide a Solution.
Cluster
A group of MDM instances in an application server.
Instance
An MDM application running in an application server.
| 19
Chapter 2
Installation
This chapter explains how to install TIBCO MDM Administration Agent.
Topics
•
Installation Overview, page 20
•
Installation Requirements, page 21
•
Installing TIBCO MDM Administration Agent, page 22
•
Verifying the Installation, page 25
20
| Chapter 2
Installation
Installation Overview
TIBCO MDM Administration Agent is a standalone Jetty-based web application
that communicates with TIBCO MDM via JMX and with TEA Servers via HTTP. It
is installed using the TIBCO Universal Installer.
Installation Modes
Three installation modes are available: GUI, console, and silent.
Installation Requirements 21
|
Installation Requirements
This section provides general information about TIBCO MDM Administration
Agent’s installation requirements. For complete installation requirement details,
see TIB_mdm-agent_1.0.0_readme.txt.
Required Software
TIBCO MDM Administration Agent requires an agent library with which it is
packaged. No other software is required for installation.
The functionality of TIBCO MDM Administration Agent depends on the
following TIBCO software:
•
TIBCO TEA version 1.0.0
•
TIBCO MDM version 8.3.1_HF-001 and above
TIBCO MDM Administration Agent also requires Java SE Development Kit (JDK)
7.
Disk Space Requirements
TIBCO MDM Administration Agent requires 10 MB of free disk space for logging
purposes.
Supported Platforms
TIBCO MDM Administration Agent supports the following platforms:
•
HP HP-UX
— 11i v3 (B.11.31) 64-bit on Itanium
•
Microsoft Windows Server
— 2008 R2 64-bit on x86-64
•
Red Hat Enterprise Linux Server
— 5.x, 6.x 64-bit on x86-64
•
Sun Solaris
— 10 64-bit on SPARC
22
| Chapter 2
Installation
Installing TIBCO MDM Administration Agent
TIBCO MDM Administration Agent is installed using the TIBCO Universal
Installer. Run the TIBCO Universal Installer executable to install the agent.
TIBCO MDM Administration Agent does not need to be installed in a
TIBCO_HOME. TIBCO MDM Administration Agent can be installed in any
directory of the machine hosting the MDM instances that you want the agent to
monitor and manage. Only one MDM Administration Agent should be
configured per machine. TIBCO MDM Administration Agent handles the Java
Virtual Machine (JVM) of each MDM instance.
You can install TIBCO MDM Administration Agent using one of the following
modes:
•
Installing in GUI Mode, page 22
•
Installing in Console Mode, page 23
•
Installing in Silent Mode, page 24
Installing in GUI Mode
In GUI mode, the TIBCO Universal Installer presents panels that allow you to
make choices about product selection, product location, and so on. GUI mode is
the installer's default mode.
To install in GUI mode:
1. Open the physical media or download the installation package.
2. Extract the TIBCO MDM Administration Agent archive file to a temporary
directory.
3. Navigate to the temporary directory.
4. Run TIBCOUniversalInstaller. The Welcome screen displays. Click Next.
5. The License Agreement screen appears. After reading through the license text,
click I accept the terms of the license agreement and then click Next.
6. The TIBCO Installation Home screen displays.
An installation environment isolates product installations; a product installed
into an installation environment does not access components in other
installation environments. An installation environment consists of a name,
and path. You can choose a new environment or an existing environment.
Installing TIBCO MDM Administration Agent 23
|
•
Create a new TIBCO_HOME To install the product into a new installation
environment, specify the following properties:
— Name Identifies the installation environment. The name cannot contain
special characters such as * ? > < : | / \ or ".
— Path The directory into which the product is installed. Type a path or click
Browse to specify the path or accept the default location.
The path cannot contain special characters such as * # ? > < % & $ ` or |. The
path cannot be the same as the path of an existing environment.
•
Use an existing TIBCO_HOME To install the product into an existing
installation environment, select the environment from the Environment
drop-down list.
7. The Installation Profile Selection screen displays.
Start by selecting one of the installation profiles in the left pane. If you select
Customize Installation (optional), you may then select or unselect individual
components in the right pane. Click Next.
8. The Pre-Install summary screen displays. Verify the list of products selected
for install and then click Install.
9. The Post-Install Summary screen appears. This screen summarizes the
installation process. Click Finish to complete the installation process and close
the installer window.
Installing in Console Mode
Console mode allows you to run the installer from the command line. This is
useful if your machine does not have a window environment.
To install in console mode:
1. Open the physical media or download the installation package.
2. Extract the TIBCO MDM Administration Agent archive file to a temporary
directory.
3. Using a console window, navigate to the temporary directory.
4. Run the platform-specific installer executable in console mode:
TIBCOUniversalInstaller -console
5. Complete the installation by responding to the console window prompts.
24
| Chapter 2
Installation
Installing in Silent Mode
In silent mode, the universal installer does not prompt for any inputs during
installation. Instead, the inputs are read from a response file that can be provided
as a command-line parameter. If no value is specified, the installer uses the
default TIBCOUniversalInstaller.silent file.
The following procedure explains how to install TIBCO MDM Administration
Agent in silent mode. If errors occur during installation, they will be listed in the
installation log file contained in the directory USER_HOME/username.TIBCO, as
explained in Installer Log File on page 25.
1. Open the physical media or download the TIBCO MDM Administration
Agent package.
2. Extract the contents of the package to a temporary directory.
3. Using a console window, navigate to the temporary directory.
4. Copy the file TIBCOUniversalInstaller.silent, rename the copy as
myfilename.silent. (If you use the default file name for your copy, you may
omit the responseFile parameter in step 6.)
5. Using a text editor, open the copied file and update the install location and
features to install.
6. Run the installer. To do this on Linux, execute:
TIBCOUniversalInstaller-lnx-x86.bin -silent -V
responseFile="myfilename.silent"
Installation File System Details
TIBCO MDM Administration Agent creates the following directories and files:
•
MDM-AGENT_HOME/config — Contains configuration files.
•
MDM-AGENT_HOME/lib — Contains library files required by the agent.
•
MDM-AGENT_HOME/samples/application_server — Contains sample scripts for
the following application servers: JBoss, WebLogic, WebSphere. Use the script
appropriate to your application server.
•
MDM-AGENT_HOME/config/mdm-agent.properties — The properties file
for the agent. See Configuring Agent Properties File on page 29 for more
information about configuring this file.
Installing TIBCO MDM Administration Agent 25
|
•
MDM-AGENT_HOME/StartMDMAgent.sh (StartMDMAgent.bat for Windows)
— The startup script for the agent. See Starting TIBCO MDM Administration
Agent on page 36 for more information about starting the agent.
B
You must set the JAVA_HOME environment variable in the following locations:
•
The file StartMdmAgent.sh (StartMdmAgent.bat for Windows)
•
Environment
•
TEA Server
See Setting Java Environment Variables on page 28 for more information about
setting environment variables.
Installer Log File
TIBCO MDM Administration Agentd does not create a dedicated log directory. If
you want to debug the StartMDMAgent.sh (StartMDMAgent.bat for Windows)
command, you can redirect the logs to directory of your choice.
The TIBCO Universal Installer automatically generates the following log files:
•
USER_HOME/username.TIBCO/install_currentyear-currentmonth-currentdate.uniqueI
D — This log file allows you to troubleshoot for any errors that might have
occurred during the installation process.
•
USER_HOME/tibco_universal_installer.username_install — This file
contains installer-related logs.
Verifying the Installation
After installing TIBCO MDM Administration Agent, verify that the file
MDM-AGENT_HOME/StartMDMAgent.sh (StartMDMAgent.bat for Windows) is
present.
See Chapter 5, Troubleshooting, on page 53 for general troubleshooting
information.
26
| Chapter 2
Installation
| 27
Chapter 3
Configuration
This chapter explains how to configure TIBCO MDM Administration Agent.
Topics
•
Setting Java Environment Variables, page 28
•
Configuring Agent Properties File, page 29
•
Configuring MDM Clusters, page 33
•
Starting TIBCO MDM Administration Agent, page 36
•
Verifying TIBCO MDM Administration Agent, page 37
28
| Chapter 3
Configuration
Setting Java Environment Variables
TIBCO MDM Administration Agent requires Java SE Development Kit (JDK) 7.
You must set a JAVA_HOME environment variable to point to the JDK in the
following locations:
•
MDM-AGENT_HOME/startMDMAgent.sh (startMDMAgent.bat on Windows)
•
Environment
•
TEA Server
WebSphere and IBM JDK Configuration
If you use WebSphere as an application server and IBM’s implementation of Java
Development Kit (JDK) 7, additional configuration is required.
To enable communication via JMX for each MDM instance, set the following
properties on the MDM Server as arguments for the Java command line:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port= 9010
-Dcom.sun.management.jmxremote.local.only=true
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
(For security reasons,
set this to true so that the remote method invocation (RMI) port cannot be
accessed from outside.)
-Dcom.sun.management.jmxremote.local.only=true
Configuring Agent Properties File 29
|
Configuring Agent Properties File
TIBCO MDM Administration Agent’s properties file, mdm-agent.properties,
must be configured to communicate with TIBCO MDM. The required and
optional properties are described in the table below.
Table 3 Agent Properties
Properties
Description
Required Properties
agent.description
Brief description of the agent. For example, Agent
agent.server.port
Port used by TEA Server to connect to agent. For example, 1242
for MDM
QA cluster
Optional Properties
tea.server.url
URL the agent uses to connect to TEA Server. For example,
http://localhost:8777/tea
If no URL is specified the agent will not automatically register with TEA
Server. You can manually register the agent using TEA Server UI.
ssl.enabled
Boolean property to enable SSL.
tea.agent.http.ke
ystore
File path to or URL of the SSL key store.
tea.agent.http.ke
ystore.password
Password for the key store.
tea.agent.http.ce
rt.alias
Alias of SSL certificate.
tea.agent.http.ke
ymanager.password
Password for specific key within the key store.
tea.agent.http.tr
uststore
File path to or URL of the trust store.
tea.agent.http.tr
uststore.password
Password for the trust store.
tea.agent.http.id
letimeout
The maximum idle time to set. Translates to the
Socket.setSoTimeout(int) call.
tea.agent.http.th
readpool.acceptor
s
Number of acceptor threads to set.
30
| Chapter 3
Configuration
Properties
Description
agent.managed.mdm
server.url
The URL of the managed MDM server. For example,
http://localhost:8080
If used, this URL should be mentioned in the file cluster-config.xml.
See Configuring Agent Properties File on page 29 for more information
about MDM cluster configuration.
agent.version
Version of the agent.
mdmserver.polling
_interval
Polling interval for agent to poll MDM, specified in milliseconds.
Recommended value is 5000 ms (5 s). Values lower than 1000 ms (1 s)
should not be specified.
product.type.name
Product name for MDM. Not recommended to change.
product.type.desc
Description of MDM product. Not recommended to change.
agent.server.name
Name of agent.
agent.server.desc
ription
Brief description of agent.
agent.server.vers
ion
Version of server hosting agent.
agent.server.cont
extPat
Context path used by TEA Server to execute Rest API. Not modified in
most cases.
mdmserver.mqhome
This property is optional. However, if you want to start MDM Servers for
the first time by using the agent’s Bootup function, you must specify this
property. If this property is specified, the agent reads
cluster-config.xml and lists the MDM Servers defined there.
Specify this property with the path to the MQ_HOME. Be sure that this
path conforms to your operating system’s syntax. For example:
LINUX
mdmserver.mqhome=/home/user1/mdm/83
WINDOWS
agent.managed.mdm
server.url
mdmserver.mqhome=C:\\tibco\\mdm\\8.3
The URL and credentials of an MDM Server. For example,
http://localhost:8080
If a URL is provided, the agent connects to the MDM instance at startup.
agent.info
Brief description of agent. For example, agent1
Configuring Agent Properties File 31
|
Example Agent Properties File
Here is an example of a configured mdm-agent.properties file, located at
MDM-AGENT_HOME/config:
##--- Start of Mandatory properties
agent.description=MDM
QA cluster
agent.server.port=1242
##--- End of Mandatory properties
# URL to connect with Tea Server. if URL is not specified, agent
will not automatically register to Tea Server. You can register the
agent using Tea Server
tea.server.url=http://localhost:8777/tea
##--- SSL properties
ssl.enabled=false
#- The file or URL of the SSL Key store location.
tea.agent.http.keystore=
#- The password for the key store.
tea.agent.http.keystore.password=
#- Alias of SSL certificate.
tea.agent.http.cert.alias=
#- The password for the specific key within the key store.
tea.agent.http.keymanager.password=
#- The file name or URL of the trust store location
tea.agent.http.truststore=
#- The password for the trust store.
tea.agent.http.truststore.password=
#--" - The maxIdleTime to set, which translates to the
Socket.setSoTimeout(int) call.
tea.agent.http.idletimeout=
#- The number of acceptor threads to set.
tea.agent.http.threadpool.acceptors=
##- SSL properties
#enable jmx password
jmx.password=false
32
| Chapter 3
Configuration
# Optional. if MQ_HOME is specified, it is used to read
Cluster-info for MDM solution. If not specified, MQ_HOME
environment var is looked up.
# if environemnt variable is not setup, solution is not published.
#mdmserver.mqhome=/Users/jsmith/dev/mdm/dest
#mdmserver.mqhome=/home/apatil/mdm/v_dist/cim_jboss/eCM83
## Please do not modify the below properties
#agent.info=agent1 info
agent.version=8.3.1
# Polling interval for agent to poll MDM. Specified in Mill
Seconds. Recomemnded value is 5000 (5s). Value lower than 1000
should not be specified.
mdmserver.polling_interval=10000
product.type.name=TIBCO MDM
product.type.desc=TIBCO MDM helps you to ensure that your master
data is consistent\, complete\, and accurate throughout your
organization\, enterprise systems and partners.
agent.name=TIBCOMDMAgent
agent.server.name=TIBCOMDMAgent
agent.server.description=TIBCO MDM Agent to monitor MDM instances
and cluster
agent.server.version=8.3.1
# Context Path is used by Tea Server to execute Rest API. Normally
not changed.
agent.server.contextPath=MDMAgent
# Optional This url should be mentioned in the cluster-config.xml
#agent.managed.mdmserver.url=http://localhost:8080
Configuring MDM Clusters 33
|
Configuring MDM Clusters
MDM clusters are groups of MDM instances. In the TEA Server UI, such groups
are referred to as MDM solutions. These clusters are defined for MDM in a
configuration file called cluster-config.xml, which is located at
MQ_HOME/config. TIBCO MDM Administration Agent queries
cluster-config.xml for the values displayed in the TEA Server UI.
The cluster and cluster member properties specified in this file are described in
the tables below:
•
Table 4, Cluster Properties describes the properties that define a cluster.
•
Table 5, Cluster Member Properties describes the properties that define
members of the cluster.
Table 4 Cluster Properties
Properties
Description
name
Name of the cluster. For example, Cluster1
The TEA UI displays this as MDM Solution.
description
Short description of the cluster. For example, Test
Cluster
Table 5 Cluster Member Properties
Properties
Description
name
Name of the MDM instance member in the cluster.
This must be the same as the NODE_ID environment variable set for the MDM
Server. See Chapter 1, Configurator, in TIBCO MDM System Administration for
more information about clusters in TIBCO MDM.
description
Brief description of the instance.
serverURL
URL of the machine hosting the MDM instance. This must be a hostname and
not an IP address. For example, http://localhost:8080
The serverURL should be unique in a cluster definition. TIBCO MDM
Administration Agent uses the serverURL to determine whether the MDM
instance is local to that machine.
34
| Chapter 3
Configuration
Properties
Description
startCmd
Start command for the application server. The exact command depends on the
type of web application server you are using. For example, a JBoss server start
command would resemble the following example:
$JBOSS_HOME/bin/standalone.sh -b 0.0.0
See Preparing Startup and Shutdown Commands on page 34 for more
information about startup commands.
shutdownCmd
Shutdown command for the application server. The exact command depends
on the type of web application server you are using. For example, a JBoss
server stop command would resemble the following example: ./jboss-cli.sh
--controller=localhost:9999 --connect command=:shutdown
See Preparing Startup and Shutdown Commands on page 34 for more
information about shutdown commands.
Preparing Startup and Shutdown Commands
TIBCO MDM Administration Agent installs three directories that provide sample
startup and shutdown commands for three different types of application servers:
•
MDM-AGENT_HOME/Samples/scripts/JBoss
•
MDM-AGENT_HOME/Samples/scripts/WebLogic
•
MDM-AGENT_HOME/Samples/scripts/WebSphere
The shutdown script for a JBoss application server would resemble the following
example:
export JAVA_HOME=/home/mdm/jdk1.7.0_40
export EMS_HOME=/home/mdm/tibco/ems/8.0
export AS_HOME=/home/mdm/MDM831/mdm/8.3/bin/as/2.0
export PATH=$AS_HOME/bin:$JAVA_HOME/bin:$PATH:
export LD_LIBRARY_PATH=$AS_HOME/lib:$LD_LIBRARY_PATH:
export JBOSS_HOME=/home/mdm/jboss-as-7.1.1.Final
rm -rf "${JBOSS_HOME}/standalone/tmp"
rm -rf "${JBOSS_HOME}/standalone/data"
rm -rf "${JBOSS_HOME}/standalone/log"
rm server1.log
./standalone.sh -b 0.0.0.0 > server1.log 2>&1 &
Create Shutdown Script
Configuring MDM Clusters 35
|
/jboss-cli.sh --controller=localhost:9999 --connect
command=:shutdown
Example Cluster Configuration File
This section provides an example of a complete cluster-config.xml file. If you
want to add more members to the cluster, copy the member fragment.
<cluster>
<name>MDMCluster</name>
<description>MDMCluster view</description>
<members>

<member>
<name>Member1</name>
<description>Member1</description>
<serverUrl>http://localhost:8080</serverUrl>
<startCmd>/home/mdm/jboss/bin/startMdmServer.sh
</startCmd>
<shutdownCmd>/home/mdm/jboss/bin/shutdownMdmServer.sh
</shutdownCmd>
</member>
<member>
<name>Member2</name>
<description>Member2</description>
<serverUrl>http://localhost:8081</serverUrl>
<startCmd>/home/mdm/jboss/bin/startMdmServer.sh
</startCmd>
<shutdownCmd>/home/mdm/jboss/bin/shutdownMdmServer.sh
</shutdownCmd>
</member>
</members>
</cluster>
36
| Chapter 3
Configuration
Starting TIBCO MDM Administration Agent
Before starting TIBCO MDM Administration Agent, ensure that:
•
The MDM Server is started.
•
You have set the following:
— JAVA_HOME as an environment variable, as explained in Setting Java
Environment Variables on page 28.
— MQ_HOME as an environment variable or as the property
mdmserver.mqhome in the file mdm-agent.properties. Setting the
MQ_HOME is optional. but if you want to start the server using agent then
it should be mentioned in mdm-agent.properties. See Configuring Agent
Properties File on page 29 for more information about configuring agent
properties. The property mdmserver.mqhome helps the agent read the file
cluster-config.xml. The agent is initialized with cluster-config.xml
using this property. This property is useful if you want to start the MDM
Server for the first time using the Bootup function.
To start TIBCO MDM Administration Agent, execute the following from the
command line:
./startMDMAgent.sh (startMDMAgent.bat for Windows)
This file is located at MDM-AGENT_HOME.
TIBCO MDM Administration Agent checks for the MDM Server’s environment
properties to verify the MDM Server’s Java Virtual Machine (JVM) and connects
automatically to the MDM Server’s JVM.
Verifying TIBCO MDM Administration Agent 37
|
Verifying TIBCO MDM Administration Agent
Once you have started the agent, verify that the following elements are displayed
correctly in the TEA UI:
•
Agent listed in the Agent Management page, as illustrated in Figure 1.
•
MDM Server and MDM Instances managed by the agent, as illustrated by
Figure 2.
See Chapter 5, Troubleshooting if any of these elements are not displayed
properly.
Figure 1 TEA Start Page > Agent Management
38
| Chapter 3
Configuration
Figure 2 TEA Start Page > MDM Product Page
| 39
Chapter 4
MDM Management
This chapter explains how to manage MDM instances using TIBCO MDM
Administration Agent and how to access the different views for TIBCO MDM in
the TEA UI.
Topics
•
Managing MDM Instances with TIBCO MDM Administration Agent on
page 40
•
Accessing the MDM Product View, page 41
•
Accessing the MDM Instance View, page 42
•
Accessing the MDM Components View, page 44
•
Accessing the MDM Solutions View, page 45
40
| Chapter 4
MDM Management
Managing MDM Instances with TIBCO MDM Administration Agent
You can manage connected instances of MDM from the instance view using the
Bootup, Shutdown, Suspend, and Resume functions. See Accessing the MDM
Instance View on page 42 for more information. Each function requires you to
confirm the action. The details of each action are described in Table 6 on page 40.
Table 6 Instance Management
Action
Description
Bootup
Starts a new application instance. When this button is clicked, TIBCO MDM
Administration Agent queries the MQ_HOME of the instance via JMX and
executes a script to start the instance.
Shutdown
Stops the application instance and the application server. TIBCO MDM
Administration Agent queries the MQ_HOME of the instance via JMX and
executes a script to stop the instance.
Suspend
Suspends inputs to the application server. It does not affect the application server
itself or the application instance. When suspended, no input channel (such as the
UI, web services, or JMS) will accept any new work. Any current work in progress
is completed. This service can take few seconds to execute.
Resume
Resumes a suspended application server.
Accessing the MDM Product View 41
|
Accessing the MDM Product View
The product view displays high-level information about the product, including a
brief description and a list of connected instances of the product. To access the
MDM Product view in the TEA UI start page, click on the MDM product icon. The
following screenshot shows the view from the UI pathTEA Start Page > TIBCO
MDM Product View.
The MDM Instances table lists all connected MDM instances and provides a
description and status for each instance. Click on an instance name to see more
information about that instance. See Accessing the MDM Instance View on
page 42 for more information about the drilled-down instance view.
42
| Chapter 4
MDM Management
Accessing the MDM Instance View
The instance view displays information about connected instances of MDM. The
following screenshot shows the view from the UI pathTEA Start Page > TIBCO
MDM Product View > MDM Instance View.
The instance view provides the information listed in Table 7 on page 42:
Table 7 Instance View Fields
Field
Description
Name
Name of the instance.
Status
Status of the instance. Either Running, Stopped, or Unreachable.
Accessing the MDM Instance View 43
|
Table 7 Instance View Fields
Field
Description
Type
Product type.
Description
Brief description of the instance.
Application
Name
Name of the application running the instance.
Application
Server Name
Name of the server hosting the application.
Build Number
Version of the build.
Common
Directory
Common directory for the application. For example,
Config File
Location of the application’s configuration file. For example,
/TIBCO_HOME/MDM831/mdm/8.3/common
/TIBCO_HOME/MDM831/mdm/8.3/config/ConfigValues.xml
Home
Directory
Home directory of the application. For example, /TIBCO_HOME/MDM831/mdm/8.3
Hot
deployment
port
Hot deployment port. Default: 57571
Log Directory
Location of the log directory. For example,
/TIBCO_HOME/MDM831/mdm/8.3/log/Inst01
Started On
Timestamp of when application was started. For example, 1382654324978
Uptime
Total uptime of application. For example, 22
Version
Version of the application. For example, 8.3.1
Hours,6 Minutes,52 Seconds
44
| Chapter 4
MDM Management
Accessing the MDM Components View
The Components section lists any components (such as Patterns and JMS servers)
to which TIBCO MDM is connected. This section provides the name of the
component, a brief description of the component, and the status of most
components (for example, Running or Stopped). Click on the name of a
component to see more detailed information about it. The following screenshot
shows the view from the UI path TEA Start Page > TIBCO MDM Product View
> MDM Instance View.
When you click on the component’s name, you see additional, detailed
information about the component. For example, clicking on JMS Server in the
above example displays the following detailed information about that Patterns
Server instance:
The type of information provided varies depending on the type of component.
Accessing the MDM Solutions View 45
|
Accessing the MDM Solutions View
The Solutions view displays an overview of all of a server’s assets. You can click
on any asset to see more detailed information about most of the assets associated
with the selected MDM Server. This section provides detailed information
provided for each solution.
You can access the Solutions view from the TEA start page using the view icon in
the upper right corner of the page:
46
| Chapter 4
MDM Management
Select the server for which you want to see more detailed information. The
Solutions view displays all the assets associated with that server.
|
Solutions View: Critical Statistics
The Critical Statistics section provides information about the application server.
Table 8 Critical Statistics
Field
Description
Active HTTP
Requests
Number of active HTTP requests received by the application server.
Active
Webservice
Requests
Number of active web services requests received by the application server.
Active
Workflow
Threads
Number of active workflow threads in application server.
Logged in
Users
Number of users logged into application server.
Maximum
HTTP
Requests
Allowed
Maximum number of HTTP requests allowed by the application server.
Maximum
Users
Allowed
Maximum number of users allowed to concurrently log into the application
server.
48
| Chapter 4
MDM Management
Table 8 Critical Statistics
Field
Description
Maximum
Webservice
Requests
Allowed
Maximum number of web services the application server is allowed to receive.
Total HTTP
Requests
Served
Total number of HTTP requests that the application server has served since the
server was started or this count was restarted using JMX.
Total
Webservice
Requests
Served
Total number of web services requests the application server has served since the
Workflow
Activities
Executed
Total number of workflow activities the application server has executed since the
Workflows
Executed
Total number of workflows the application server has executed.
Solutions View: Cache Details
The Cache Details section provides information about the cache.
|
Table 9 Cache Details
Best Cache
Best cache. For example, ENTERPRISE
Best Hit Ratio
Best hit ratio. For example, 99
Caches
Total number of caches.
Distribution
Role
Distribution role of cache. For example, LEECH
Hits
Total number of hits.
Listen URL
URL cache is listening on. For example, tcp://mdminstance1:50012
Metaspace
Name
Metaspace name of cache. For example, cim831ms
Misses
Total number of misses.
Multicast URL
URL cache uses for multicasting. For example, tibpgm://12345
Requests
Total number of requests.
Unicast URL
URL cache uses for unicasting. For example, tcp:////
Weakest
Cache
Name of weakest cache. For example, SECURITYPERMISSIONS
Weakest Hit
Ratio
Ratio of weakest hits.
50
| Chapter 4
MDM Management
Solutions View: Database
The Database section provides information about the database.
Table 10 Database
Field
Description
Acquired
Connections
Number of acquired connections.
Active
Connections
Number of active connections.
Connection
URL
URL to connect to database. For example,
DatabaseConfig
Database configuration. For example, POSTGRES
Driver
Database drive. For example, PostgreSQL
Driver Version
Version of database driver. For example, PostgreSQL
JDBC Major
Version
Major version of database driver.
JDBC Minor
Version
Minor version of database driver.
Major Version
Major version of database configuration.
Minor Version
Minor version of database configuration.
jdbc:postgresql://localhost:5432/velodb
Native Driver
9.1 JDBC4 (build 901)
|
Table 10 Database
Field
Description
Product Name
Name of database product. For example, PostgreSQL
Product Version
Version of database product.
Released
Connections
Connections to database released.
SQLs Executed
Number of SQL queries executed.
User ID
User ID for database. For example, mdmuser
52
| Chapter 4
MDM Management
| 53
Chapter 5
Troubleshooting
This chapter provides some guidance for common troubleshooting scenarios.
Topics
•
Agent Does Not Start, page 54
•
Agent Unable to Connect to MDM Server, page 54
•
Agent Unable to Connect to TEA Server, page 54
•
MDM Instance Status Is Inconsistent, page 55
•
No MDM Instances Are Displayed, page 56
54
| Chapter 5
Troubleshooting
Troubleshooting Scenarios
This section describes procedures that may be useful in common troubleshooting
scenarios.
Agent Does Not Start
If TIBCO MDM Administration Agent fails to start, reload the agent and
reconnect to it in the TEA Start page.
If TIBCO MDM Administration Agent fails to start, ensure that the JAVA_HOME
environment variable has been set correctly. See Setting Java Environment
Variables on page 28 for more information.
Agent Unable to Connect to MDM Server
In general, MDM Servers should be accessible via the hostname; IP addresses
should not be used. Confirm that the MDM Server is accessible from the agent
and the TEA Server using the hostname.
If TIBCO MDM Administration Agent and TIBCO MDM are not communicating,
it is likely because there is a problem with the JMX configuration. If you are using
IBM’s implementation of the Java Development Kit (JDK) 7, some additional
configuration is required. See WebSphere and IBM JDK Configuration on page 28
for more details.
Ensure that the application server URL in the file cluster-config.xml is
correct. If it is not correct, you will see an error.
If the application server doesn’t start, verify that the server-related information in
the file cluster-config.xml is correct.
Agent Unable to Connect to TEA Server
If TIBCO MDM Administration Agent cannot connect to the TEA Server, make
sure that the agent port and the TEA Server port are accessible from their
respective machines.
If the TEA Server displays an error indicating a connection problem, reload the
agent from the TEA Server UI.
Troubleshooting Scenarios 55
|
After starting the TEA Server, check the Agent Management page to determine
whether the agent is registered. Access the Agent Management page from the
TEA Start page by clicking on the Agents icon:
If the agent is not registered, you can register it by specifying the agent name,
URL, and description from the Agent Management page:
MDM Instance Status Is Inconsistent
If the status of an MDM instance is inconsistent (for example, Running for some
time, then Stopped, then Running), the problem may be that the MDM instance
name does not match the NODE_ID environment variable. Make sure that the
cluster member name of the MDM instance in cluster-config.xml is the same
as the NODE_ID environment variable set for the MDM Server.
56
| Chapter 5
Troubleshooting
No MDM Instances Are Displayed
If no MDM instances are displayed in the Product view, check to if any of the
agents are unreachable. All instances may fail to display if one agent becomes
unreachable and multiple agents are registered on the TEA Server.
Unregister the unreachable agent if this occurs. After unregistering the
unreachable agent, all instances should display correctly.
| 57
Index
A
H
application servers 17, 24
HTTP 20
B
I
Bootup 36, 40
Installation 21, 24
Installing 22
Instance View 42
instances 15
interface 15, 16, 16, 16, 16, 16
C
cluster 33
cluster member properties 33
clusters 33
command line 36
communicate 29
communicates 17, 20
Communication 17
communication 17
component 44
Components View 44
Configuration File 35
customer support 13
J
JAVA_HOME 25, 28, 54
JBoss 24
JDK 21, 28, 28
Jetty 20
JMX 17, 20, 28, 54
JVM 17, 22, 36, 36
JVMs 17
L
E
logging 21
environment properties 36
environment variable 25, 25, 36, 36
esume 16
M
Managing Instances 40
MDM Instances 41
monitor 16
58
| Index
P
W
Product View 41
Properties File 31
properties file 29
web application 15, 20
WebLogic 24
WebSphere 24
R
Resume 40
Running 42
S
Shutdown 34, 40
shutdown 34
start 16
start page 41
Starting 36
Startup 34
startup 34
Status 42
stop 16
Stopped 42
support, contacting 13
Suspend 40
suspend 16
T
technical support 13
TIBCO Univeral Installer 22
TIBCO_HOME 10
Troubleshooting 54
U
Unreachable 42

Installation and Configuration

Transcription

Similar documents

DOWNLOAD: "Pharma-Industry"

Jaeckle Distributors Uses Spotfire to Differentiate in a

A 3-STEP PLAN FOR MOBILE SECURITY

G azzette - CHIJ Our Lady Queen of Peace

P1 Orientation Slides - Gongshang Primary School

Consistency and efficiency with Master Data

EnWin Utilities - Rogers Enterprise Business Solutions

Atlantis Energy Systems Inc.