Readme file for IBM® Spectrum Conductor with Spark 2.2.1 Interim Fix 528061  

Readme file for: IBM Spectrum Conductor
Product/Component Release: 2.2.1
Fix ID: sc-2.2.1.0-build528061

Publication date: August 19, 2019

This interim fix upgrades the Search Guard plug-in for Elasticsearch in IBM Spectrum Conductor with Spark 2.2.1 with a cache token implementation. 

Contents

1.      List of fixes

2.      Download location 

3.      Products or components affected

4.      Installation and configuration

5.      Uninstallation

6.      List of files

7.      Product notifications 

8.      Copyright and trademark information

1.    List of fixes

APAR: P103164

2.    Download location

Download interim fix 528061 from the following location: http://www.ibm.com/eserver/support/fixes/.

3.    Products or components affected

Component Name, Platform, Fix ID:

conductorspark_core, elk, sc-2.2.1.0-build528061

4.    Installation and configuration

Follow the instructions in this section to download and install this interim fix on all hosts in your cluster.

Prerequisite

Interim fix 514129 must be applied in your cluster.

Installation

a.      Create a backup directory and back up the following files:

$EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/plugins/search-guard-5/search-guard-5-5.4.2-12.jar

$ELK_CONFDIR/elasticsearch/elasticsearch.yml

b.      Log on to the management host as CLUSTERADMIN and source the environment.

c.      Stop the ascd, plc, and Elastic services:

$ egosh service stop ascd

$ egosh service stop plc

$ egosh service stop elk-shipper

$ egosh service stop elk-indexer

$ egosh service stop elk-elasticsearch-master elk-elasticsearch elk-elasticsearch-data

$ egosh service stop elk-manager

d.      Extract the contents of the sc-2.2.1.0_build528061.tgz package to the backup directory:

$ tar zoxf sc-2.2.1.0_build528061.tgz

e.      Replace files extracted from step d:

$ cp -f search-guard-5-5.4.2-12.jar $EGO_TOP/integration/elk/1.4/logstash-5.6.6/logstash-core/lib/com/floragunn/searchguard/search-guard/5-5.4.2-12/search-guard-5-5.4.2-12.jar

$ cp -f search-guard-5-5.4.2-12.jar $EGO_TOP/integration/elk/1.4/logstash-5.6.6/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.4.2-java/vendor/jar-dependencies/com/floragunn/searchguard/search-guard/5-5.4.2-12/search-guard-5-5.4.2-12.jar

$ cp -f search-guard-5-5.4.2-12.jar $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/plugins/search-guard-5/search-guard-5-5.4.2-12.jar

$ cp -f search-guard-5-5.4.2-12.jar $EGO_TOP/perf/cs/2.2.1/lib/search-guard-5-5.4.2-12.jar

$ cp -f search-guard-5-5.4.2-12.jar $EGO_TOP/ascd/2.2.1/lib/search-guard-5-5.4.2-12.jar

f.       [Optional] Modify $ELK_CONFDIR/elasticsearch/elasticsearch.yml to append the searchguard.egotoken.cache_timeout_min parameter, which defines the time (in minutes)  before the cached token expires (default is 30 minutes; 0 disables the cache implementation):

searchguard.egotoken.cache_timeout_min: 30

g.      Start the ascd, plc, and Elastic services:

$ egosh service start elk-manager

$ egosh service start elk-elasticsearch-master elk-elasticsearch elk-elasticsearch-data

$ egosh service start elk-indexer

$ egosh service start elk-shipper

$ egosh service start ascd

$ egosh service start plc

h.      Clear your browser cache and log in to the cluster management console as usual.

5.    Uninstallation

If required, follow the instructions in this section to uninstall this interim fix on hosts in your cluster.

a.      Log in to the management host as CLUSTERADMIN and source the environment.

b.      Stop the ascd, plc, and Elastic services:

$ egosh service stop ascd

$ egosh service stop plc

$ egosh service stop elk-shipper

$ egosh service stop elk-indexer

$ egosh service stop elk-elasticsearch-master elk-elasticsearch elk-elasticsearch-data

$ egosh service stop elk-manager

c.      Restore $ELK_CONFDIR/elasticsearch/elasticsearch.yml and all instances of the search-guard-5-5.4.2-12.jar file with your backup of the elasticsearch.yml and search-guard-5-5.4.2-12.jar file.

d.      Start the ascd, plc, and Elastic services:

$ egosh service start elk-manager

$ egosh service start elk-elasticsearch-master elk-elasticsearch elk-elasticsearch-data

$ egosh service start elk-indexer

$ egosh service start elk-shipper

$ egosh service start ascd

$ egosh service start plc

e.      Clear your browser cache and log in to the cluster management console.

6.    List of files 

$ELK_CONFDIR/elasticsearch/elasticsearch.yml

$EGO_TOP/integration/elk/1.4/logstash-5.6.6/logstash-core/lib/com/floragunn/searchguard/search-guard/5-5.4.2-12/search-guard-5-5.4.2-12.jar

$EGO_TOP/integration/elk/1.4/logstash-5.6.6/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.4.2-java/vendor/jar-dependencies/com/floragunn/searchguard/search-guard/5-5.4.2-12/search-guard-5-5.4.2-12.jar

$EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/plugins/search-guard-5/search-guard-5-5.4.2-12.jar

$EGO_TOP/perf/cs/2.2.1/lib/search-guard-5-5.4.2-12.jar

$EGO_TOP/ascd/2.2.1/lib/search-guard-5-5.4.2-12.jar

7.    Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes. 

8.    Copyright and trademark information 

© Copyright IBM Corporation 2019

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml