TIBCO LogLogic Unity Installation and …...TIBCO LogLogic® Unity Installation and Configuration...

TIBCO LogLogic® Unity Installation andConfiguration GuideSoftware Release 1.0.0November 2014 Document Update: January 2015

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, LogLogic, and Two-Second Advantage are either registered trademarks or trademarks ofTIBCO Software Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE 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 ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2014-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO LogLogic® Unity Installation and Configuration Guide

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

TIBCO Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

TIBCO LogLogic Unity License Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring a Standalone System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Starting LogLogic Unity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Stopping LogLogic Unity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Restarting LogLogic Unity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Distributed System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Stopping a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Restarting a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Troubleshooting Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

LogLogic Unity Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Changing Default Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Changing the Configuration Node Default Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Changing Standalone System Default Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Changing Distributed System Default Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Uninstalling in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Uninstalling in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Manage Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Viewing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Adding a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Editing User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Disabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Deleting User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Manage Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3


Viewing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Adding a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Editing a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Disabling a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4


TIBCO Documentation and Support Services

All TIBCO documentation is available in the TIBCO Documentation Library, which can be found here:

https://docs.tibco.com

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on theTIBCO Documentation site. To directly access documentation for this product, double-click thefollowing file:

TIBCO_HOME/release_notes/TIB_logu_version_docinfo.html

The following documents for this product can be found in the TIBCO Documentation site:

● TIBCO LogLogic® Unity Installation and Configuration Guide

● TIBCO LogLogic® Unity User's Guide

● TIBCO LogLogic® Unity Developer's Guide

● TIBCO LogLogic® Unity Tutorials

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support asfollows:

● 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 canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to:

http://www.tibcommunity.com

5


https://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

http://www.tibcommunity.com

Installation Requirements

Before you can run the installer on your Linux system, you must log in as a user with appropriatepermissions, and your system must meet the hardware and software requirements.

If you plan on installing in an existing installation environment, stop all processes that are using Javafrom TIBCO_HOME.

Installation Account Requirements

A regular (non-root) login must be used to install the product (it cannot be run as "root").

A graphic environment such as CDE or X Windows is required to run the installer in the GUI mode.

Supported PlatformsThe following platforms are supported by LogLogic® Unity.

● Apple Mac OS X 10.9.x 64-bit on x86-64● CentOS 6.x 64-bit on x86-64

When installing on CentOS 6.x, disable the firewall rules to accommodate the LogLogicUnity ports. For instructions, refer to the Configure Firewall Settings section in the Installation Prerequisites.

● Red Hat Enterprise Linux Server 6.x 64-bit on x86-64

Hardware RequirementsInstallation requires a substantial amount of system memory and disk space. Review the systemmemory and disk space requirements before you start installation.

Development/TestEnvironments

(Minimum Requirements)

Production Environments

(RecommendedRequirements)

CPU 8 cores 16 cores

System Memory 16GB RAM 64GB RAM

Hard Drive 1x1 TB (10,000 RPM) 9 x 1 TB (10,000 RPM)

1 x 400 GB SSD (Optional)

Disk Space

The installer requires space in the temporary directory before installation, and additional space in thetemporary directory for running the installer. You must also make sure that the directory you want touse as the installation environment (TIBCO_HOME) directory has sufficient space.

While installing, avoid running other processes that consume disk space in the installation environmentdirectory. If another process consumes disk space while the installer is copying the files, the installermight fail and display a failure message.

6


Directory Disk Space Requirement

Temporary directorybefore installation

Before you start the installation process, extract the contents of theinstallation archive to a temporary directory. The installer filesconsume up to 200 MB of disk space.

Temporary directoryduring installation

The installer requires at least 100 MB of free space in the temporarydirectory.

If your system does not have sufficient free disk space in the defaulttemporary directory, you can use the is:tempdir option to run theinstaller with a different temporary directory. For example:

TIBCOUniversalInstallerPlatform -is:tempdir /new_tmp

where /new_tmp has sufficient free disk space.

Installation environmentdirectory

The installer calculates the disk space required in the installationenvironment directory for the selected components. The calculation isdone before the actual installation (copying of files to system) begins.The installer proceeds only if sufficient free disk space is available inthe installation environment directory. LogLogic Unity might consume700 MB of free space under TIBCO_HOME.

Software RequirementsYour system must meet the software requirements before you run the installer.

Software Description

Java Required (bundled with the installer). If not using the Oracle Java RuntimeEnvironment that is bundled with the installer, you must use Oracle Java RuntimeEnvironment 1.7.0 update 72 or higher.

Please check for additional patches for the supported OS platforms forJava 1.7 certification.

Web Browser Required to run the LogLogic Unity GUI. The supported browsers are:

● Google Chrome 33.0.x, 34.0.x● Mozilla Firefox 27.0.x, 28.0.x

TIBCO Software Requirements

LogLogic® Unity requires either of the following for log collection and storage:

● TIBCO LogLogic® Log Managment Intelligence (LMI) 5.5.1 — ST Appliance required

● TIBCO LogLogic® Enterprise Virtual Appliance 5.5.1

TIBCO LogLogic Unity License Restrictions

The Unit for Licensor Software TIBCO LogLogic Unity is 20GB/day. If the amount of raw data indexedby the Licensor Software exceeds 20GB/day, then additional Units of TIBCO LogLogic Unity must bepurchased by Licensee. The Licensee will provide TIBCO access to usage data to determine the actual

7


average per/day usage over a 6 month period. LogLogic Unity must be used with a TIBCO LogLogicLog Management Intelligence ST, MX or a LogLogic Enterprise Virtual Appliance. You must eitherhave an existing instance of one of these products or will need to purchase one.

8


Installation Prerequisites

Before downloading and extracting the installation package, ensure that the system meets all theprerequisites and decide on the installation environment and folder.

● TIBCO_HOME is the top-level installation directory for TIBCO products.● TIBCO_HOME is referred to as the installation environment.

If the TIBCO_HOME directory is created under a folder which has spaces in its name, LogLogic Unitywill not start up.

Installation environments isolate software installations; a product installed into an installationenvironment does not automatically access components in other environments. An installationenvironment consists of:

● A name that identifies the environment.● A directory that contains the installed software. When you install, you can choose a new installation

environment or an existing installation environment.

If a previous installation of a TIBCO product did not use the TIBCO Universal Installer, the TIBCOUniversal Installer does not detect the folder it uses as an installation environment folder. If you wantto use the existing location as the installation folder, create a new installation environment and choosethe folder where the other products exist.

Configure Firewall Settings

When installing on CentOS 6.x, disable the firewall rules to accommodate the LogLogic Unity ports.

1. Run the following commands to configure firewall rules (iptables):

iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9600 -j ACCEPT












2. Run the following command to save the configuration:

service iptables save

9


Installation

TIBCO provides downloadable product archive files and the products can be installed using TIBCOUniversal Installer.

Extract the product archive file to a temporary directory and then run the TIBCO Universal Installerexecutable from that directory.

The installer allows you to run in one of the following modes: GUI, console, or silent, which areavailable on all platforms.

Once you launch the installer, you must specify the installation directory. If installing for the first time,create a new installation directory. For subsequent installations, you can choose to either use an existinginstallation directory or create a new one.

Installation ModesThe installer allows you to install in one of the following modes: GUI, console, or silent. Each mode issupported on all platforms.

GUI Mode

In the GUI (graphical user interface) mode, the installer presents windows that allow you to select theproduct components.

For more information about installing in GUI mode, see Installing in the GUI Mode.

Console Mode

In the console mode, you invoke the installer from a command prompt or a terminal window and theinstaller prompts for values on the console. You can move through the installation process byresponding to the prompts. This mode is useful if your machine does not have a Windowsenvironment.

Use this method for Linux installations.

For more information about installing in Console mode, see Installing in the Console Mode.

Silent Mode

In the silent mode, the installer installs without prompting you for information. Silent mode eitherinstalls using the default settings or uses a response file that was saved during an earlier installation.

For more information about installing in Silent mode, see Installing in the Silent Mode.

Installing in GUI ModeWhen you run the installer in the GUI mode, the installer prompts you for information about theinstallation environment, and allows other customizations.

Procedure

1. Open the physical media or download the product package. Perform the following steps:a) Extract the contents of the package to a temporary directory.b) Navigate to the temporary directory.

10


2. Run TIBCOUniversalInstaller. You can do so in one of the following ways:

● Double-click on the installer icon.

Not supported on Red Hat Enterprise Linux.

● On the command prompt, provide the absolute path of the installer file without specifying anyoptions. The installer defaults to the GUI mode.

3. In the Welcome window, click Next.

4. Read through the license text when the License Agreement window appears, select the I accept theterms of the license agreement radio button and then click Next.

5. In the TIBCO Installation Home window, select an installation environment.An installation environment isolates product installations. A product installed into an installationenvironment does not access components in other installation environments. An installationenvironment consists of a name and path. You can specify a new environment or an existingenvironment.a) Create a new TIBCO_HOME: To install the product into a new installation environment,

specify the following properties:

● Directory: The directory into which the product is installed. Type a path or click Browse tospecify the path or accept the default location. The path cannot contain special characterssuch as "*", "#", "?", ">", "<", "%", "&", "$", "`", or "|". The path cannot be the same as the path ofan existing environment.

● Name: Identifies the installation environment. The name cannot contain special characterssuch as "*", "?", ">", "<", ":", "|", "/", "\", or quotation marks(").

b) Use an existing TIBCO_HOME: To install the product into an existing installation environment,select the environment from the drop-down list. In this case, select Use an existingTIBCO_HOME to install this product into the TIBCO_HOME directory where the TIBCOproducts are installed.

c) Click Next to continue.

6. By default, TIBCO Universal Installer selects the Typical installation profile. To customize theprofile feature settings, select the Customize Installation check box and use the feature tree on theright. Click Next to continue.

7. Point to the existing location of the Java directory and click Next.

8. Verify the list of products selected to install in the Pre-Install Summary window and click Install tostart the installation process.

9. Review the information listed in the Post-Install Summary window and click Finish to complete theinstallation process and exit the universal installer.

Installing in Console ModeConsole mode allows you to install TIBCO LogLogic Unity from a non-Windows environment. Thismode presents a series of prompts that request the same information that you would enter on thedialogs presented in the GUI installation mode.

Prerequisites

Prepare your system and the installation media before running the installer in the console mode.

Procedure

1. Open a console window and navigate to the temporary directory where you extracted the productarchive file.

11


2. Run TIBCOUniversalInstaller -console.The installer launches a second console window.

3. Complete the installation by responding to the console window prompts, which are similar to thosedescribed in the GUI mode instructions.

4. When the installation completes, press Enter to exit the installer.

Installing in Silent ModeIn silent mode, you can run the installer without the user input by pointing the installer to a responsefile. A default pre-configured response file exists.In the silent mode, the installer does not prompt for inputs during the installation, but reads the inputsfrom a response file. By default, the installer uses theTIBCOUniversalInstaller_<product>_<version>.silent file that is included in the directory thatcontains the universal installer.

You can customize the silent installer as follows:

● Make a backup copy of the TIBCOUniversalInstaller_<product>_<version>.silent file andedit the file itself. You can then run the silent installer with or without the response file argument.

● Make a copy of the TIBCOUniversalInstaller_<product>_<version>.silent file and name thecopy. You can then run the silent installer, passing in your custom response file.

Procedure

1. Open the physical media or download the product package.

2. Extract the contents of the package to a temporary directory.

3. Using a console window, navigate to the temporary directory.

4. Make a copy of the TIBCOUniversalInstaller_<product>_<version>.silent file and renamethe file.

5. Using a text editor, open the copied file. You may need to update the install location.The default location is: <entry key="installationRoot">/opt/tibco</entry>

6. Run the silent installer with or without the optional response file using the command line:TIBCOUniversalInstaller.bin -silent [-V responseFile='myfile.silent']

12


Configuration

After installing TIBCO LogLogic Unity you can configure and start it. TIBCO LogLogic Unity comeswith the following two default configuration profiles:

● standalone — this profile configures all LogLogic Unity components on a single machine.● distributed — this profile configures LogLogic Unity components on multiple machines.

In the following steps the lld command will run in the foreground.

Refer to LogLogic Unity Port Numbers for details regarding the LogLogic Unity port numbers. Allport numbers can be changed.

Warning: After starting up LogLogic Unity, if the system it is running on changes its IP address (forexample, if running on a laptop that moves to another network), LogLogic Unity must be stoppedand restarted. Until the system is restarted, logins for valid users will fail with the error "Sorry, theinfo you entered didn't match any account. Please try again.", and queries will fail with the error"Problem with connection to datanode".

The Event Distributor Client (EDC) which runs on the TIBCO LogLogic Managment Intelligence (LMI)ST platform is responsible for forwarding events collected by a LogLogic appliance to a LogLogic Unitysystem. The EDC must be configured by using the lmiedc command which has options to start, stopand configure the EDC service.

For instructions on how to configure the EDC using the lmiedc command refer to Appendix A CommandLine Interface (CLI) of the LMI Administration Guide.

By default the retention period is 90 days for all events.

Configuring a Standalone SystemA Standalone profile allows you to configure LogLogic Unity components on a single machine.

Prerequisites

You will need the following information in order to configure your system:

● Install LogLogic Unity● Location of TIBCO_HOME — Note the TIBCO_HOME was created during installation. Refer to step

5a of Installing in the GUI Mode.

Starting LogLogic Unity

Complete the following steps to start your system.

Procedure

1. CD to:$TIBCO_HOME/logu/1.0/tools/bin

13


2. Run:./lld -p standalone

If you want to start your system in the background use an operating specific mechanism such asnohup. For example:nohup ./lld -p standalone > ../logs/lld.out 2>&1 & echo $! > ../logs/lld.pid

Once the system has started you will see the following message:Running TIBCO LogLogic Unity Configurator (lld) ...TIBCO LogLogic Unity v1.0 DaemonConfiguration uploaded.Web Server url : http://102.168.200.208:9680Configuration uploaded.1 source config files uploaded.Machine started

At this point all nodes will have started.

3. You can now log into the Web Application.http://<IP Address>:<9680> (IP Address is the IP Address of the machine where the WebApplication is running and 9680 is the default port number.)

Stopping LogLogic Unity

Complete the following steps to stop your system.

Procedure


2. Enter:CTRL-C

If you are using nohup enter:cat ../logs/lld.pid

kill <id-in-lld.pid>

3. Optional: To verify that everything has shutdown, check that the following processes are notrunning:

● node

● postgres

● tibco-correlationnode-<osplatform>

● tibco-datanode-<osplatform>

● tibco-eventdistributor-<osplatform>

● tibco-querynode-<osplatform>

● configuration node-<osplatform>

Restarting LogLogic Unity

Complete the following steps to restart your system.

Procedure


14


2. Run:./lld

If you are using nohup enter:nohup ./lld > ../logs/lld.out 2>&1 & echo $! > ../logs/lld.pid

Distributed System ConfigurationA Distributed profile allows you to configure LogLogic Unity components on several machines, eachhosting different LogLogic Unity nodes. A distributed system is comprised of a controller and one ormore member machines. A controller machine runs the configuration server and controls membermachines. There can only be one controller in each distributed system. A distributed system can haveseveral member machines each running; a data node, query node, event distributor node, and webapplication.

Prerequisites

You will need the following information in order to configure your system:

● Install LogLogic Unity● Location of TIBCO_HOME — Note the TIBCO_HOME was created during installation. Refer to step

5a of Installing in the GUI Mode.● IP Address and port number of the machine which will be controlling your system● IP Address and port number of your member machine(s)

Refer to LogLogic Unity Port Numbers on how to change your port numbers.

Configuring a Distributed System

Complete the following steps to configure your distributed system.

This will start the configuration server in the foreground. If you want to start the configuration in thebackground use an operating specfic mechanism such as noHub.

Procedure

1. On your controller machine CD to:$TIBCO_HOME/logu/1.0/tools/bin

2. Enter:./llsetup controller

This will label this machine as the controller.

3. Enter:./lld


The configuration server will wait for the configuration to be uploaded.

15


4. In a new window run:./llconf -p <IP Address of controller machine>:<port> distributed -c

This step can be run from any machine. It does not necessarily need to be run from one ofthe LogLogic Unity machines. However if you are running this step on the same machineused in step 3 you will need to run this step in a new window otherwise step 3 will notcomplete.

5. On your member machine run:./llsetup member -c <IP Address of controller machine>:<port>

This will label the second machine as a member machine.

./llsetup can only be used once. If you use it again you will need to uninstall Unity andthen reinstall it.

6. Enter:./lld


This will start the member server in the foreground.

7. Repeat steps 5 through 6 on all your member machines.

8. You can now log into the Web Application.http://<IP Address>:<port number> (IP Address is the IP Address of the machine where the WebApplication is running and 9680 is the default port number.)

Stopping a Distributed System

Complete the following steps on each machine to stop your system.

Procedure


2. Enter:CTRL-C

If you are using nohup enter:cat ../logs/lld.pid

kill <id-in-lld.pid>

All member machines should be stopped before the controller.

16


3. Optional: To confirm that everything has shutdown, check that the following processes are notrunning:

● node

● postgres

● tibco-correlationnode-<osplatform>

● tibco-datanode-<osplatform>

● tibco-querynode-<osplatform>

● tibco-eventdistributor-<osplatform>

● configuration node-<osplatform>

Restarting a Distributed System

Complete the following steps to restart your system.

Procedure


Run the following command first on your controller and then on your member machines

2. Run:./lld


Troubleshooting InstallationIf you encounter problems during installation, ensure that your system meets all prerequisities andthen check the installer log for potential problems.

Installer Log File

The installer log file captures information such as:

● Installation environment details such as the user that invoked the installer, hostname,JAVA_HOME, operating system details, and so on.

● List of installed processes.

LogLogic Unity Log Files

The following log files are created during installation:

● lld.out — this file contains all command logs● lldaemon.log — this file displays the running system information to help users detect errors and

troubleshoot before they actually take place● llconfig.log — this file

LogLogic Unity Processes

LogLogic Unity runs the following processes:

17


Controller proccesses

● postgres● tibco-correlation-<osplatform>● configuration node-<osplatform>

Member processes

● tibco-datanode-<osplatform>● tibco-querynode-<osplatform>● tibco-eventdistributor-<osplatform>● Web Application

ll Commands

Info

This can be used to see what profile and machine types have been configured, and what nodes havebeen enabled to run (based on the profile and machine type). Before running this command ensure thatconfiguration node is running.

This does NOT show the actual status of any of the nodes (running, not running/connected), just theconfiguration../llconf info

Help

To see help for each of the commands use:./llsetup --help./lld --help./llconf --help

LogLogic Unity Port Numbers

The following tables provide a list of default port numbers. All LogLogic Unity ports are external andinbound ports. You must configure firewall rules to accommodate the default ports. For instructions,refer to the Configure Firewall Settings section in the Installation Prerequisites.

Configuration Node

Service Protocol Port Number

Config Configuration 9600

Event Distributor


Ingest TCP 9610

Rest HTTP 9684

Data Node

18



Ingest TCP 9611

Rest HTTP 9683

Query TCP 9621

Streaming TCP 9622

Query Node


Rest HTTP 9681

Query TCP 9620

Correlation node


Rest HTTP 9682

Web node


Web HTTP 9680

Postgres


Query TCP 9630

Additional Ports

The following additional ports must be opened by LogLogic Unity. All additional ports are internal andinbound ports.

These ports do not need to be accessed remotely and should not be configured in the firewall.

Component Port Number Description

Correlation node 9010 JMX Remote port.

Random RMI random port.

Event Distributor 9012 JMX Remote port.

19


Component Port Number Description


Event Distributor Client 9013 JMX Remote port.


Query node 9014 JMX Remote port.


Zookeeper 9015 JMX Remote port.


Java service wrapper port range 32000 - 32999 will be bound to localhost only.

Changing Default Port NumbersThe following procedures can be used to change the LogLogic Unity default port numbers.

Changing the Configuration Node Default Port Number

Use the following command to change the configuration node port number:

Procedure

● ./lld -p standalone -c localhost:<new port number>

Changing Standalone System Default Port Numbers

Use the following steps to change the standalone system default port numbers.

Procedure

1. In edit mode open standalone.conf located in $TIBCO_HOME/logu/1.0/tools/profile.

2. Under the node type section locate the node you want to change, for example Event distributor.

3. Locate the default port number and change it as required.Steps 2 and 3 can be repeated for each node port number you want to change.

4. Save the standalone.conf file.

Changing Distributed System Default Port Numbers

Use the following steps to change the distributed system default port numbers.

Procedure

1. In edit mode open distributed.conf located in $TIBCO_HOME/logu/1.0/tools/profile.

20


2. Under the node type section locate the node you want to change, for example Correlation node.

3. Locate the default port number and change it as required.Steps 2 and 3 can be repeated for each node port number you want to change.

4. Save the distributed.conf file.

21


Uninstallation

TIBCO Universal Installer can be used to uninstall the software. Using the Universal Installer, you canchoose to uninstall products installed in the TIBCO_HOME directory.

Uninstalling in GUI ModeYou can uninstall the product in the GUI mode.

Procedure

1. Shut down all running TIBCO applications.

2. Navigate to <TIBCO_HOME>/tools/universal_installer and run the TIBCOUniversalInstallerexecutable.

3. In the TIBCO Installation Manager window:a) Select the Uninstall Products from a TIBCO Home Location radio button.b) Select the TIBCO_HOME location from the TIBCO Home Location drop-down list.c) Click Next.

4. In the Welcome window, click Next.

5. Select an uninstallation option radio button. The wizard provides two uninstallation options:a) Custom Uninstall: You can select the products to be removed.b) Typical Uninstall: The universal uninstaller removes all the products from the TIBCO_HOME.

6. Click Next.If you selected the Custom Uninstall (select the products to be removed) radio button, select thecheck boxes for products to uninstall, and then click Next.

7. Verify the list of products selected to uninstall in the Pre-Uninstall Summary window and clickUninstall to start the uninstallation process.

8. Specify the /tools directory cleanup option.a) Yes, clean it up: To delete the directory after uninstallation.b) No, do not clean it up: The directory will not be removed after uninstallation.

9. Review the information listed in the Post-Uninstall Summary window and click Finish to exit theuninstall wizard.

Uninstalling in Console ModeTo uninstall this product in Console mode, complete the following steps:

Procedure

1. Using a console window, navigate to the <TIBCO_HOME>/tools/universal_installer directory.

2. Type the following command at the command prompt:TIBCOUniversalInstaller-<platform> -console

3. Complete the uninstallation by responding to the console window prompts.

The silent mode is not available for uninstallation.

22


Manage Users

Using the User Management menu, an admin can manage users, groups, roles, and permissions.

Users are entities that need access to the system. User roles determine the permissions the user has forperforming system operation tasks. By default TIBCO LogLogic Unity comes with the following rolespredefined:

● admin: this role has the most capabilities assigned to it and is intended for administrators who willmanage all or most of the users and groups. This role will also be able to run searches, managetriggers, Bloks, or sources.

Your system must have at least one enabled user with the admin role.

● user: this role can run searches, manage triggers, Bloks, or sources.

When a user is selected the users information is displayed in a User Card on the right.

Click located on the right corner to select the columns you wish to display. You can add columnsfor the User Management view panel by simply selecting the check box next to the column name.Uncheck the check box to remove the column. The column pane is refreshed based on your selections.

Viewing UsersAn admin can manage the users authorized to use LogLogic Unity. An admin can add new users,disable user accounts, delete users from the system, or edit user information.

The User management page User tab information is described below:

Field Description

Enable Indicates if the user is enabled or disabled.

User name Mandatory field — A unique identifier for each user.

First name The user's first name.

Last name The user's last name.

Status Indicates if the user is online or offline.

Role The assigned role of the user. It can be either User or Admin. This fieldwill be empty if the user is not assigned to a role. A user who is notassigned a role will not be able to login to LogLogic Unity.

Last sign in The time the user last signed in.

Adding a UserOnly an admin can add new users.

Procedure

1. From the Admin menu, select Users and groups.

23


2. From the User management page, click to add a new user.

3. In the Add User page enter the following:

● User name — enter a user name● Email — Optional, enter users email address● First name — Optional, enter users first name● Last name — Optional, enter users last name● Phone — Optional, enter users phone number● Password — Enter user password. It is reccommended that users change their passwords the

first time they login.● Verify password — Re-enter the user password● Group — Optional, from the drop-down menu select a group. users can be assigned to multiple

groups.● Role — From the drop-down menu select a role.● Enable — Slide the Enable slide to ON to enable the user. If this is not selected the user will not

be able to login.

Disabled users or users who have not been assigned a role will not be able to login.

4. Click Save to add the new user in the system.The newly added user is listed in the User management page.

Editing User InformationAn admin can edit all user information, but users can only edit their own information via Edit Profile.

Procedure


2. From the User management page, click on a user name.The users details are displayed on the right.

3. Select Edit from the User card located on the right.

4. In the Edit User Info page edit the fields you want to update.

5. Click Save to save the updated information.

Disabling a UserOnly an admin can disable a user.

Procedure


2. From the User management page, click on a user name.The users details are displayed on the right.

3. Select Edit from the user card located on the right.

24


4. In the Edit User Info page slide the Enable slider to OFF.


Disabled users are not able to login to the system.

A user can also be disabled via the user management page by deselecting the Enabledslider next to the users name.

Deleting UserOnly an admin can delete a user.

In order for LogLogic Unity to work, your system must contain at least one admin user.

Procedure


2. From the User management page, select the checkbox next to the user that you want to delete and

click .

3. In the confirmation window, click OK to delete the user from the system.The User management page will be updated.

Once users are deleted their information cannot be recovered.

25


Manage Groups

Using the User Management menu, an admin can create groups to manage a collection of users.

A user group is a collection of user accounts and can have multiple roles assigned to it. When a user isassigned to a group, the group's roles are automatically assigned to the user. Users can be associatedwith multiple groups.

Viewing GroupsAn admin can create groups to manage a collection of users. Add a new group, disable a group, deletea group from the system, or edit group information.

The User management page Group tab information is described below:

Field Description

Active Indicates if the group is is active or inactive. Note: Users can be assigned togroups that are not active.

Group The unique identifier for each group.

Description Provides a description of the group.

Role The role assigned to all users within the group.

Adding a GroupOnly an admin can add new groups.

Procedure


2. Group account page, click to add a new group.

3. From the User management page select Groups.

4. In the Add Group page enter the following information:

● Group name — Enter a name for the group.● Description — Optional, enter a description of the group.● Role — Optional, enter the role that will be assigned to all users in this group.● Add users — Optional, enter the names of all the users that will be connected to this group.

Names should be separated by a comma.● Enable — Slide the Enable slide to ON to enable the group.

5. Click Save to add the new group in the system.The newly added group is listed in the Group account page.

26


Editing a GroupAn admin can edit all group information.

Procedure



3. From the Group account page, click on a group.The group details are displayed on the right.

4. Select Edit from the Group card located on the right.

5. In the Edit Group Info page edit the fields you want to update.


Disabling a GroupOnly an admin can disable a user.

Procedure



3. From the Group account page, click on a group.The group details are displayed on the right.

4. Select Edit from the Group card located on the right.

5. In the Edit Group Info page slide the Enable slider to OFF.


Users can be assigned to inactive groups.

A group can also be disabled via the group account page by deselecting the Enabled slidernext to the groups name.

Deleting a GroupOnly an admin can delete a group.

Procedure



3. From the Group account page, select the group that you want to delete and click .

27


4. In the confirmation window, click OK to delete the group from the system.The Group account page will be updated.

Once a group is deleted its information cannot be recovered.

28


TIBCO LogLogic Unity Installation and …...TIBCO LogLogic® Unity Installation and Configuration...

Documents

Transcript of TIBCO LogLogic Unity Installation and …...TIBCO LogLogic® Unity Installation and Configuration...