TIBCO LogLogic Unity Installation and Configuration...The following documents for this product can...

TIBCO LogLogic® UnityInstallation and ConfigurationSoftware Release 2.6June 2016

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 (ORPROVIDE 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, EITHER EXPRESSOR 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-2016 TIBCO Software Inc. All rights reserved.

TIBCO Software Inc. Confidential Information

2

TIBCO LogLogic® Unity Installation and Configuration

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

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

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring a Standalone System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Starting LogLogic Unity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Stopping LogLogic Unity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Restarting LogLogic Unity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Configuring a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Stopping a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Restarting a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring with Multiple Configuration Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Starting a System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Troubleshooting Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Collecting Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

LogLogic Unity Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Changing Default Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

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

Changing Standalone System Default Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Changing Distributed System Default Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Deploying LogLogic Unity Daemon (lld) in the Advanced Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Changing Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Changing Standalone System Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Changing Distributed System Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Exporting or Importing Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

3


Configuring Hawk Connector Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Setting the StorageZone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Setting the Ingest Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Backing up the Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Upgrading a Standalone System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Upgrading a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Uninstalling in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Uninstalling in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4


TIBCO Documentation and Support Services

Documentation for this and other TIBCO products is available on the TIBCO Documentation site. Thissite is updated more frequently than any documentation that might be included with the product. Toensure that you are accessing the latest available help topics, please visit:

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

where TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows,the default TIBCO_HOME is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco.The following documents for this product can be found in the TIBCO Documentation site:

● TIBCO LogLogic® Unity Installation and Configuration

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

● 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 the following web address:

https://www.tibcommunity.com

5


https://docs.tibco.com

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

https://support.tibco.com

https://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 GUI mode.

Supported PlatformsThe following platforms are supported by LogLogic® Unity.

● Apple Mac OS X 10.9.x, 10.10.x, 10.11.x 64-bit on x86-64

● CentOS 6.x, 7.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, 7.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.8.0 update 77.

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

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

● Google Chrome 50.0.x, 51.0.x

● Mozilla Firefox 45.0.x, 46.0.x,

● Microsoft Internet Explorer 10, 11

TIBCO Software Requirements

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

● TIBCO ActiveMatrix BusinessWorks™ 6.3.1● TIBCO Hawk® 4.9.1, 5.1, 5.1.1 or 5.2● TIBCO LogLogic® Log Management Intelligence (LMI) 5.5.1, 5.6.1 or 5.6.3● TIBCO LogLogic® Enterprise Virtual Appliance 5.5.1, 5.6.1 or 5.6.3

LogLogic Unity requires either of the following to generate reports for monitoring:

7


● TIBCO JasperReports® Server 6.2.0

● TIBCO JasperReports® Server Community Edition 6.2.0

TIBCO LogLogic Unity License Restrictions

The Unit for Licensor Software TIBCO LogLogic Unity is 20GB/day. If the average amount of raw dataindexed by the Licensor Software exceeds 20GB/day, then additional Units of TIBCO LogLogic Unitymust be purchased by Licensee. The Licensee will provide TIBCO access to usage data to determine theactual average per/day usage over a 6 month period. LogLogic Unity can be used with a TIBCOLogLogic Log Management Intelligence ST, MX or a LogLogic Enterprise Virtual Appliance.

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 want touse the existing location as the installation folder, create a new installation environment and choose thefolder where the other products exist.

Configure Firewall Settings

When installing on CentOS 6.x, disable the firewall rules to accommodate the LogLogic Unity ports forfull accessibility. The minimum requirement for access outside a firewall is port 9680 for access througha web browser, port 9681 for access to the REST API for queries, and ports 9610 and 9613 for ingestingdata from outside the firewall. As HTTPS is not currently supported, a proxying agent, such as NGINXcan be used.

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
















9





2. Run the following command to save the configuration:

service iptables save

10


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 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 GUI Mode.

Console Mode

In 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 Console Mode.

Silent Mode

In silent mode, the installer installs without prompting you for information. Silent mode either installsusing 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 Silent Mode.

Installing in GUI ModeWhen you run the installer in 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.

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.

11


● 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 thepath of an 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 the profilefeature settings, select the Customize Installation check box and use the feature tree on the right.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 GUI installation mode.

Prerequisites

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

Procedure

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

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 GUI mode instructions.

12


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 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 defaultlocation is: <entry key="installationRoot">/opt/tibco</entry>. The /opt/tibco becomesthe TIBCO_HOME path.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 thepath of an 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,provide the existing TIBCO_HOME installation path instead of /opt/tibco in the copy of theTIBCOUniversalInstaller_<product>_<version>.silent file .

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

13


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 Management 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 System

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

Prerequisites

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

● Install LogLogic Unity● Location of TIBCO_HOME

The TIBCO_HOME was created during installation. Refer to step 5a of Installing in GUIMode.

Starting LogLogic Unity

Complete the following steps to start your system.

Procedure

1. Change directory to:$TIBCO_HOME/logu/<version>/tools/bin

2. Run:./lld -p standalone

14


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 can see a message similar to the following:Running TIBCO LogLogic Unity Configurator (lld) ...TIBCO LogLogic Unity <version> DaemonConfiguration uploaded.Web Server url : http://102.168.200.208:9680Configuration uploaded.1 source config files uploaded.Machine started

At this point all nodes must have started.

3. Log into the Web Application using the URL http://<IP Address>:9680.IP Address is the IP Address of the machine where the Web Application is running and 9680 is thedefault port number.

Stopping LogLogic Unity

Complete the following steps to stop your system.

Procedure

1. If LogLogic Unity is running in foreground enter:CTRL-C

If you are using nohup go to:$TIBCO_HOME/logu/<version>/tools/bin

Run the command: ./lld stop

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

● node

● postgres

● llcn-<osplatform>

● lldn-<osplatform>

● lled-<osplatform>

● llqn-<osplatform>

● llzk-<osplatform>

● lluc-<osplatform>

● llhc-<osplatform>

● llan-<osplatform>

● llmn-<osplatform>

Restarting LogLogic Unity

Complete the following steps to restart your system.

15


Procedure


2. Run:./lld

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

Configuring a Distributed System

A 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, query node, eventdistributor node, web application, hawk connector node, aggregation node, management node, andcontrols member machines. There can only be one controller in each distributed system. A distributedsystem can have several member machines each running a data node.

Prerequisites

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

● Install LogLogic Unity● Location of TIBCO_HOME


● IP Address and port number of the machine which will be controlling your system● IP Address and port number of your member machines

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 specific mechanism such as nohup.

Procedure

1. On your controller machine change directory to:$TIBCO_HOME/logu/<version>/tools/bin

2. Enter:./llsetup controller

This will label this machine as the controller.

3. Enter:./lld


16


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

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

port>

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>:<configuration 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 LogLogicUnity and then reinstall it.

6. Enter:./lld


This will start the member server in the background.

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

1. If LogLogic Unity is running in foreground enter:CTRL-C

If you are using nohup go to:$TIBCO_HOME/logu/<version>/tools/bin

Run the command: ./lld stop

All member machines should be stopped before the controller.

2. Optional: To verify that everything has shutdown, check that the process names starting with thefollowing are not running:

● node

● postgres





17







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


Configuring with Multiple Configuration ServersIn the following distributed system scenario we are setting up one controller and two membermachines with each running a configuration server.

Prerequisites

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

● Install LogLogic Unity

● Location of TIBCO_HOME


● IP Address and port number of the machine which will be controlling your system

● IP Address and port number of your all member machines

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

In multiple configuration server system only 1, 3, or 5 configuration servers are supported.

Starting a System

In the following procedure, we will deploy 3 nodes each one hosting a configuration server.

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

18


Procedure

1. On your controller machine change directory to:$TIBCO_HOME/logu/<version>/tools/bin

2. On your controller machine run:./llsetup controller -c <connection string> —zkId <index in the connection string

for this host>

This will label the controller machine.

The connection string provided to the -c parameter of llsetup must be the same for allnodes and lists in order the IP and port for the configuration servers, separated withcommas. Every machine hosting a configuration server should use —zkId option inllsetup to specify the identification number (Id) corresponding to its position in theconnection string.

By default, the configuration server timeout is set to 60 seconds. If you want to change thetimeout setting, use --waitTime <seconds> option on all machines.

For example, ./llsetup controller -c 10.114.81.102:9600,10.114.80.129:9600,10.114.80.130:9600 —zkId 1

3. On your first member machine run:./llsetup member -c <connection string> —zkId <index in the connection string for

this host>

This will label the second machine as a member machine.

For example, ./llsetup member -c 10.114.81.102:9600,10.114.80.129:9600,10.114.80.130:9600 —zkId 2

4. On your second member machine run:./llsetup member -c <connection string> —zkId <index in the connection string for

this host>

This will label the third machine as a member machine.

For example, ./llsetup member -c 10.114.81.102:9600,10.114.80.129:9600,10.114.80.130:9600 —zkId 3

5. Run the following command on controller and machines that host configuration servers:./lld

On machines that do not host configuration servers, run the lld command after step 6.


This will start the member servers in the background.

6. On any one machine (controller or member), run the following command:./llconf -p distributed

The "Machine Started" status on each machine is displayed when the LogLogic Unity system startswith all configuration servers.

For any reasons, if any configuration server in a cluster goes down, the nodes that areconnected to that configuration server will be restarted automatically.

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

To check the configuation server cluster status, run the command for each configurationserver: telnet <configuration server IP address> <configuration server portnumber>. To get the status, once the telnet connection is successful, type stat.

19


Troubleshooting InstallationIf you encounter problems during installation, ensure that your system meets all prerequisites and thencheck 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 generated log files with locations are listed below:

● client/logs: <name of the imported file>.log

● correlationnode/logs: llcn.log, wrapper-llcn.log

● datanode/logs: lldn.log, wrapper-lldn.log

● eventdistributor/logs: lled.log, wrapper-lled.log

● querynode/logs: llqn.log, wrapper-llqn.log

● tools/logs: llconf.log, lldaemon.log, llunitymonitor.log

● webapp/logs: llweb-error.log, llweb-server.log, llweb.log

● zookeeper/logs: llzk.log, wrapper-llzk.log

● managementnode/logs: llmn.log, wrapper-llmn.log

● hawkconnector/logs: llhc.log, wrapper-llhc.log

● aggregationnode/logs: llan.log, wrapper-llan.log

LogLogic Unity Processes

LogLogic Unity runs the following processes:

Controller processes

● postgres



● Web Application






Member processes



20


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

Status

Use the following command on any machine that has LogLogic Unity installed, to get a summary ofLogLogic Unity currently running processes.llstatus

A sample output is shown below.=========================================================================CONFIGURATION STATUS=========================================================================Running TIBCO LogLogic Unity Configurator (llconf)...TIBCO LogLogic Unity v2.1.0 Configuration

System info: Profile: standalone Machine type: controller Machine nodes: database, datanode, querynode, managementnode, correlationnode, hawkconnector, aggregationnode, eventdistributor, webapp=========================================================================EXECUTION STATUS=========================================================================postgres is running (93575).zookeeper is running (93527).aggregationnode is running (94106).correlationnode is running (93960).datanode is running (93740).eventdistributor is running (94178).hawkconnector is running (94033).managementnode is running (93887).querynode is running (93815).ucnode is running (94328).webapp is running (94183).

Collecting Diagnostic InformationLogLogic Unity diagnostic information, from each node, can be gathered into a compressed file usingthe llconf command on each machine that has LogLogic Unity installed.

Run the following command from the logu/tools/bin folder:

./llconf ziplog

After you run this command, a compressed file is created with the timestamp. For example,Unity_Log_Thu_Dec_03_2015_15:52:46_GMT-0800_(PST).zip

For the collected log files with locations information, see Troubleshooting Installation.

21


If any node contains archived logs, those logs are also collected in each respective directory.

LogLogic Unity Port Numbers

The following tables provide a list of default port numbers. All LogLogic Unity ports are external andinbound ports. These ports must be visible to each other on the various machines used for properinteroperation of LogLogic Unity components. You must configure firewall rules to accommodate thedefault ports. For instructions, refer to the Configure Firewall Settings section in the InstallationPrerequisites.

Configuration Node (llzk)

Service Protocol Port Number

Config Configuration 9600

Config Replication 9601

Config Leader election 9602

Event Distributor (lled)


Ingest TCP 9610

Rest HTTP 9684

ULDP ULDP 9612

Ingest2 TCP 9613

IngestStore TCP 9614

Data Node (lldn)


Ingest TCP 9611

Rest HTTP 9683

Query TCP 9621

Streaming TCP 9622

Query Node (llqn)


Rest HTTP 9681

22



Query TCP 9620

Correlation Node (llcn)


Rest HTTP 9682

Web Node (llweb)


Web HTTP 9680

Postgres (postgres)


Query TCP 9630

Management Node (llmn)


Rest HTTP 9689

Hawk Connector Node (llhc)


Rest HTTP 9631

Aggregation Node (llan)


Rest HTTP 9685

Query TCP 9626

Changing Default Port NumbersYou can 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:

23


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 the standalone.profile file located in $TIBCO_HOME/logu/<version>/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.profile 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 the distributed.profile file located in $TIBCO_HOME/logu/<version>/tools/profile.

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.profile file.

Deploying LogLogic Unity Daemon (lld) in the Advanced NetworkConfiguration

In situations where IP address of the machine where LogLogic Unity is deployed is not the same as thepublic IP, when deployed behind Network Address Translation (NAT) or in virtual environment, it ispossible to override the IP address and port numbers that LogLogic Unity is using to communicatebetween nodes or accessed externally.

For example, if two virtual machines (or docker containers) with LogLogic Unity are running on thesame host and using a single host network interface to expose LogLogic Unity functionality, you cansetup the public IP address for the server using the --publicIp option. In addition, you can change theport number for network port mapping using the --portShift option.

Setting up the Public IP Address

Use the following commands to setup the IP address.

● In the Standalone system, run the following command:

./lld -p standalone --publicIp <new IP address>

24


● In the Distributed system without multiple configuration servers, run the following command on acontroller machine:

./llsetup controller -c <connection string> —zkId 1 --publicIp <new IP address>

● In the Distributed system without multiple configuration servers, run the following command on amember machine:

./llsetup member -c <connection string> —zkId 1 --publicIp <new IP address>

● In the Distributed system with multiple configuration servers, run the following command on acontroller machine:

./llsetup controller -c <connection string> —zkId <index in the connection string

for this host> --publicIp <new IP address>

The connection string provided to the -c parameter of llsetup must be the same for allnodes and lists in order the IP and port for the configuration servers, separated withcommas. Every machine hosting a configuration server should use —zkId option in llsetupto specify the identification number (Id) corresponding to its position in the connectionstring.

● In the Distributed system with multiple configuration servers, run the following command on everymember machine:


for this host> --publicIp <new IP address>

After you restart the system, the new configuration is displayed.

Changing the Port Mapping

LogLogic Unity uses the port numbers as specified in the profile file. If you want to expose default portnumbers as different port numbers, use the following commands. When you run the port mappingcommand, all LogLogic Unity port numbers are mapped to the new port numbers.

Make sure port forwarding is applied from all new port numbers to default port numbers on thesystem before changing the port mapping. You can only use the --portShift option with the --publicIp option.

For example, when the default port number is 9600 and if you want to expose as 9700; then the portoffset is 100.

● In the Standalone system, run the following command:

./lld -p standalone --publicIp <new IP address> --portShift <port offset>

● In the Distributed system without multiple configuration servers, run the following command on acontroller machine:

./llsetup controller -c <connection string> —zkId 1 --publicIp <new IP address>

--portShift <port offset>

The connection string provided to the -c parameter of llsetup must be the same for allnodes and lists in order the IP and port for the configuration servers, separated withcommas. Every machine hosting a configuration server should use —zkId option in llsetupto specify the identification number (Id) corresponding to its position in the connectionstring.

● In the Distributed system without multiple configuration servers, run the following command on amember machine:

./llsetup member -c <connection string> —zkId 1 --publicIp <new IP address> --

portShift <port offset>

25


● In the Distributed system with multiple configuration servers, run the following command on acontroller machine:


for this host> --publicIp <new IP address> --portShift <port offset>

● In the Distributed system with multiple configuration servers, run the following command on everymember machine:


for this host> --publicIp <new IP address> --portShift <port offset>

When using --portShift, make sure that the connect string is the same for all nodes with allpublic IP addresses, and the ports are shifted appropriately.

Changing Storage LocationsYou can change the data storage location for any node.

Changing Standalone System Storage Locations

Use the following steps to change the Standalone system storage locations.

Procedure

1. In edit mode, open the standalone.profile file located in $TIBCO_HOME/logu/<version>/tools/profile.

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

3. Locate the storage section and change it as required.Some types of node have more than one type of storage, for example, the data node stores eventsseparate from indexes. Steps 2 and 3 can be repeated for each node type you want to change.

4. Save the standalone.profile file.

Changing Distributed System Storage Locations

Use the following steps to change the distributed system storage locations.

Procedure

1. In edit mode, open the distributed.profile file located in $TIBCO_HOME/logu/<version>/tools/profile.

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

3. Locate the storage section and change it as required.Some types of node have more than one type of storage, for example, the data node stores eventsseparate from indexes. Steps 2 and 3 can be repeated for each node type you want to change.

4. Save the distributed.profile file.

26


Exporting or Importing ConfigurationsYou can export or import some configurations from one LogLogic Unity system to another. Only user-defined Sources, Bloks, Smartlist, and Dashboard configurations can be exported or imported.

Make sure that the LogLogic Unity system is running before you import or export any configurations.

Exporting Configurations

Use the following commands when exporting configurations.

● To export all configurations, run the following command:

./llconf export

After you run this command, the default unityconfig.json file is automatically created in thesame directory.

● To export configurations into a different file, run the following command:

./llconf export -f <path_to_file>

After you run this command, the file is saved at the defined location.

● To exclude samples from the exported source configuration, run the following command:

./llconf export --nosamples

● To export configuration into yaml format, run the following command:

./llconf export -y

After you run this command, the default unityconfig.yml file is automatically created in the samedirectory.

● To export configuration into a zip file, run the following command:

./llconf export -z

After you run this command, the default unityconfig.zip file is automatically created in the samedirectory.

● To export the selective configuration from the LogLogic Unity system, run the following command:

./llconf export --configlist <path_tofile>

The following expressions can be used in the configlist file.{ "sources" : [ "abc", "xyz" ], // This will export Sources configuration named "abc" and "xyz" only "bloks" : ["blok*"], // Export all Blok configurations with name starting "blok" "smartlists" : ["*"] // Export all Smartlist configurations "dashborads" : ["*"] // Export all Dashboard configurations }// To skip all Source Configurations "source": []

If you are using the above sample, make sure to remove the comments (shown by //) at theend of the line.

Importing Configurations

Use the following commands when importing configurations.

27


● To import all configurations, run the following command:

./llconf import

After you run this command, the system imports configurations from the default configuration fileunityconfig.json or unityconfig.yaml or unityconfig.zip.

● To import configurations from a specific file, run the following command:

./llconf import -f <path_to_file>

● To overwrite the existing configurations into the LogLogic Unity system, run the followingcommand:

./llconf import -o

Distributed System Configurations

On a controller machine, follow the same steps as explained above in a standalone system.

On a member machine, run the following commands:

● To export all configurations, run the command: ./llconf export -c <conf_server_url>● To import all configurations, run the command: ./llconf import -c <conf_server_url>

where, <conf_server_url> is a connect string to the Configuration server.

For example: ./llconf export -c 10.10.10.10:9600

All other options are also supported. Make sure you use the option -c<conf_server_url> when running on a member machine.

Configuring Hawk Connector NodeFor collecting real-time monitoring data from events generated within existing TIBCO Hawk®deployments - either local or distributed - into LogLogic Unity, you need to configure TIBCO Hawkmessage transport settings correctly.TIBCO Hawk provides the two message transport mechanisms via TIBCO Rendezvous® (RV) andTIBCO Enterprise Messaging Service™ (EMS). The location of the libraries for appropriately configuredtransport mechanism need to be set accurately in the $TIBCO_HOME>/logu/<version>/hawkconnector/conf/wrapper-llhc.conf file.

During the LogLogic Unity installation, if the TIBCO Universal Installer finds any existing installationsof RV, or EMS locally, it will automatically detect and set the correct locations. However, if there are nolocal installations of these TIBCO products or their respective client library sets, you must manually setthem in order to configure Hawk connector node as explained below.

Procedure

1. In the edit mode, open the wrapper-llhc.conf file located in the $TIBCO_HOME/logu/<version>/hawkconnector/conf folder.

2. Set the appropriate location of the product installation or client libraries by replacing theappropriate ${TIBCO_<transport-type>_HOME_ESC} entry in the following three lines:set.RV_HOME=${TIBCO_RV_HOME_ESC}

set.EMS_HOME=${TIBCO_EMS_HOME_ESC}

3. After the changes, save the wrapper-llhc.conf file.4. After making changes in the wrapper-llhc.conf file, you must stop the Hawk node and start it

again using the following commands:./llhc stop

28


./llhc start

5. Restart the LogLogic Unity system using the following command:./lld start

Setting the StorageZone ConfigurationThe StorageZone configuration helps you define how data is distributed among Event Distributor (ED)nodes and data nodes. Each domain is assigned to a StorageZone, each ED and data node are alsoassigned to a StorageZone.

By default, all domains are in the StorageZone named "all" and all EDs or data nodes are also in the"all" StorageZone, that means all events are distributed on all EDs or data nodes.

An ED and a data node store events belonging to a domain only if any of the following conditions aretrue:

● The domain of the events and the ED or data node belongs to the same StorageZone.● The domain of the events is set to "all" zone.● The domain of the ED or data node is set to "all" zone.

You can also setup the StorageZone configuration using the Web UI (Administration > Domains) for adomain.

Standalone System Configurations

● To get the current StorageZone configuration, run the following command:

./llconf getconfig --storagezone

● To update current StorageZone configuration, run the following command:

./llconf setconfig --storagezone -f <path_to_file>

where <path_to_file> contains the StorageZone configuration. This file must be in a valid JSONformat as shown in the following example:{ "configurations": [ { "name": "st1", "domains": [ "domain1" // This domain's StorageZone will change to 'st1' ], "eventdistributors":[ "eventdistributor-0000000001" // This eventdistributor's StorageZone will change to 'st1' ], "datanodes": [ "datanode-0000000001" // This datanode's StorageZone will change to 'st1' ] }, { "name": "st2", "domains": [ "domain2", "domain3" ], "eventdistributors":[ "eventdistributor-0000000002", "eventdistributor-0000000003" ], "datanodes": [ "datanode-0000000002", "datanode-0000000003" ]

29


} ] }

If you are using the above sample file, make sure to remove the comments (shown by //) at the end ofthe line.

When you run the ./llconf setconfig --storagezone -f <example_file> command, it makesthe following changes:

● Domain "domain1", EventDistributor "eventdistributor-0000000001", and DataNode"datanode-0000000001", will all belong to StorageZone "st1".

● Domains "domain2" and "domain3", EventDistributors "eventdistributor-0000000002", and"eventdistributor- 0000000003", and DataNode "datanode-0000000002", and "datanode-0000000003",will all belong to StorageZone "st2".

A warning may appear in the following cases:

● A StorageZone have domains but are not associated with any ED or data node.

● A StorageZone has no domain associated but it has either ED and/or data node associated.

If you want to overwrite StorageZone configuration even if warnings are displayed, run the followingcommand:

/llconf setconfig --storagezone -f <path_to_file> -o

or

./llconf setconfig --storagezone -f <path_to_file> --overwrite

Changing a StorageZone configuration of ED or data node will restart each respective nodes.




● To get the current Storagezone, run the command: ./llconf getconfig --storagezone -c<conf_server_url>

● To set the current Storagezone, run the command: ./llconf setconfig --storagezone -c<conf_server_url>


For example: ./llconf setconfig -c 10.10.10.10:9600


Setting the Ingest ConfigurationEach domain can be associated with an ingest configuration that defines how the ingestion buffer ismanaged on the Event Distributor (ED). By default, the configuration is defined in the "all" zone, thiscan be modified further by defining new values in the domain section with the relevant domain name,using the llconf command.The parameters that comprise the ingest configuration are:

● maxHours = 24

The minimum retention in hours for the ingest buffer.

30


● maxMB = 1024

The maximum retention size in MB for the ingest buffer.● replicationFactor = 1

The replication factor for the data of the ingest store. The value -1 means replicate the data on allEDs. The minimum value is 1 (which means data is not replicated). You can also setup thereplication factor configuration using the Web UI (Administration > Domains) for a domain.

After the first limit is reached, will trigger rotation of part of the buffer.

Standalone System Configurations

● To get the current ingest configuration, run the following command:

./llconf getconfig --ingest

● To update current ingest configuration, run the following command:

./llconf setconfig --ingest -f <path_to_file>

where <path_to_file> contains Ingest configuration. This file must be in a valid JSON format asshown in the following example:{ "all" : { "replicationFactor": 2 // This property's value will be updated to the new value "2" }, "domains": [ { "name": "domain1", // Ingest Configuration specific to domain "domain1" will be updated or created. "config": { "maxMB": 1024, // This property's value will be updated to the new value "1024" "maxHours" : 12 // This property's value will be updated to the new value "12" } } ] }

If you are using the above sample file, make sure to remove the comments (shown by //) atthe end of the line.

When you run the ./llconf setconfig --ingest -f <example_file> command, it makes thefollowing changes:

— a "replicationFactor" property will be updated to value "2". This property belongs to the defaultingest configurations.

— ingest configuration specific to domain "domain1" will be created if it does not exist, then"maxMB" value will be set to 1024, and "maxHours" value will be set to 12.

● To remove the current Ingest configurations, run the following command:

./llconf removeconfig --ingest -f <path_to_file>

where <path_to_file> contains Ingest configuration. This file must be in a valid JSON format asshown in the following example:{ "domains": [ { "name": "domain1", // Ingest Configuration for domain "domain1" will be removed if exists

31


"config": [ "maxMB", // This property will be removed "maxHours" // This property will be removed ] } ] }

If you are using the above sample file, make sure to remove the comments (shown by //) atthe end of the line.

When you run the ./llconf removeconfig --ingest -f <example_file> command, it willmake following change:

● the "maxMB" and "maxHours" properties of ingest configuration of domain "domain1" areremoved.




● To get the current ingest configuration, run the command: ./llconf getconfig --ingest -c<conf_server_url>

● To set the current ingest configuration, run the command: ./llconf setconfig --ingest -c<conf_server_url>

● To remove the current ingest configuration, run the command: ./llconf removeconfig --ingest-c <conf_server_url>


For example: ./llconf setconfig -c 10.10.10.10:9600


Backing up the Configuration DataIt is a good practice to back up LogLogic Unity configuration data.

The following files should be backed up:

● <type>/conf/logging-llxx.xml (if logging configuration has been modified)

● <type>/conf/server-llxx.conf (if optional parameters have been set)

● <type>/conf/wrapper-llxx.conf (if optional parameters, for example, VM parameters have been set)

● tools/conf/lld.conf

● tools/data/lld.id

● postgres/data/db

● zookeeper/data/zk

Since Kafka uses Zookeeper for its metadata storage, the backed up ZK data may not be usable withoutthe data directories from the ED and the DN.

32


Upgrade

You can upgrade LogLogic Unity from the previous version to the latest version on a Standalone orDistributed system.

During upgrade, the existing data and configurations are migrated from the previous version to thelatest version when the data folder is located in the default location.

Upgrading a Standalone SystemWhen LogLogic Unity components are installed on a single machine, follow the instructions describedbelow.

Procedure

1. Stop the LogLogic Unity system. For instructions, see the Stopping LogLogic Unity section describedin the Configuring a Standalone System.

2. Backup your data before starting the upgrade process.

3. Change directory to:$TIBCO_HOME/logu/<latest version>/tools/bin

4. Migrate the folders from the previous version to the latest version by running the llmigratecommand with the following options:./llmigrate <folder where previous version is installed>

For example, ./llmigrate $TIBCO_HOME/logu/2.0

5. Run the upgrade command:./llconf upgrade

6. Restart the LogLogic Unity system. For instructions, see the Restarting LogLogic Unity sectiondescribed in the Configuring a Standalone System.

Do NOT use the ./lld -p standalone command to start the LogLogic Unity systembecause that will overwrite the profile you have customized.

Upgrading a Distributed SystemWhen LogLogic Unity components are installed on several machines, comprised of a controller and oneor more member machines, follow the instructions described below.

Procedure

1. Stop the LogLogic Unity system on each machine, including the controller machine. Forinstructions, see the Stopping a Distributed System section described in the Configuring a DistributedSystem.

2. Backup your data before starting the upgrade process.

3. On each machine, change directory to:$TIBCO_HOME/logu/<latest version>/tools/bin

4. Migrate the folders from the previous version to the latest version by running the llmigratecommand with the following options:./llmigrate <folder where previous version is installed>

For example, ./llmigrate $TIBCO_HOME/logu/2.0

5. On the controller machine, run the upgrade command:./llconf upgrade

33


6. Restart the LogLogic Unity system. For instructions, see the Restarting a Distributed System sectiondescribed in the Configuring a Distributed System.

Do NOT use the ./lld -p distributed command to start the LogLogic Unity systembecause that will overwrite the profile you have customized.

34


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

35


TIBCO LogLogic Unity Installation and Configuration...The following documents for this product can...

Documents

Transcript of TIBCO LogLogic Unity Installation and Configuration...The following documents for this product can...