TIBCO LogLogic LMI - EMS Collector Libraries supporting TLS encryption are not packaged with LSP

TIBCO LogLogic LMI - EMS Collector Libraries supporting TLS encryption are not packaged with LSP

book

Article ID: KB0080401

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Log Management Intelligence 6.1.0 and higher
TIBCO LogLogic Log Source Packages 34 and higher

Description

The LSP starting from version 34 has added the ability to establish connection to TIBCO EMS server via TLS1.2. However, LMI administrators need to install the proper client libraries prior to configuring the EMS collector.

Issue/Introduction

Starting from LSP34 the EMS collector libraries enabling TLS encryption will not be packaged with the LSP installer. They need to be separately downloaded and transferred to the LogLogic LMI appliance. This article describes the procedure and lists the specific required libraries.

Resolution

LMI now supports TLS encryption with TIBCO EMS server via the LSP. Successful connectivity with TLS1.2 is made through newer TIBCO EMS client v8.3 and higher. However, by default, LSP34 and higher will not install the libraries needed to establish TLS1.2 connections to an EMS server. The LSP will continue being packaged with only the library tibjms-6.3.0.jar which does not support secure connection with EMS. 

Administrators will need to grab libraries jms-2.0.jar, tibcrypt.jar, and tibjms.jar from the lib directory of their EMS installation folder at $EMS_HOME/<version>/lib
and copy them to the LMI host under the proper collectors library folder at /loglogic/logsource/collector/endorsed.

At this point, administrators can proceed configuring the new TIBCO EMSC device source. There is no need to restart LLCollectors.