Installation and Configuration of IBM Watson Analytics and StoredIQ: Complete Administration Guide of IBM Watson, IBM Cloud, Red Hat OpenShift, Docker, and IBM StoredIQ (English Edition) [1 ed.] 9390684498, 9789390684496

Citation preview

Installation and Configuration of IBM Watson Analytics and StoredIQ

Complete Administration Guide of IBM Watson, IBM Cloud, Red Hat OpenShift, Docker, and IBM StoredIQ

Alan Bluck

www.bpbonline.com

FIRST EDITION 2021 Copyright © BPB Publications, India ISBN: 978-93-90684-49-6

All Rights Reserved. No part of this publication may be reproduced, distributed or transmitted in any form or by any means or stored in a database or retrieval system, without the prior written permission of the publisher with the exception to the program listings which may be entered, stored and executed in a computer system, but they can not be reproduced by the means of publication, photocopy, recording, or by any electronic and mechanical means.

LIMITS OF LIABILITY AND DISCLAIMER OF WARRANTY

The information contained in this book is true to correct and the best of author’s and publisher’s knowledge. The author has made every effort to ensure the accuracy of these publications, but publisher cannot be held responsible for any loss or damage arising from any information in this book.

All trademarks referred to in the book are acknowledged as properties of their respective owners but BPB Publications cannot guarantee the accuracy of this information.

Distributors:

BPB PUBLICATIONS

20, Ansari Road, Darya Ganj

New Delhi-110002

Ph: 23254990/23254991

MICRO MEDIA Shop No. 5, Mahendra Chambers,

150 DN Rd. Next to Capital Cinema, V.T. (C.S.T.) Station, MUMBAI-400 001

Ph: 22078296/22078297 DECCAN AGENCIES 4-3-329, Bank Street,

Hyderabad-500195 Ph: 24756967/24756400

BPB BOOK CENTRE

376 Old Lajpat Rai Market, Delhi-110006

Ph: 23861747

Published by Manish Jain for BPB Publications, 20 Ansari Road, Darya Ganj, New Delhi-110002 and Printed by him at Repro India Ltd, Mumbai

www.bpbonline.com

Dedicated to

My beloved Wife, Jennifer & My Children, Julie and Rosalie & Their Families

About the Author

Alan Bluck is a systems architect providing a broad range of services, with over 45 years of IT experience. He has been a Solutions Architect for IBM for over 10 years. His experience includes high-level technical design, through mentoring for code development, and installation and configuration of IBM’s core products. He is responsible for high-level analysis and configuration on existing and new IBM systems. He is also responsible for mentoring and troubleshooting high-level systems and issues, ensuring that scheduled timelines are maintained and deadlines are met.

He has over 45 years of Software Development experience in both Business and Scientific systems; 5 years of experience as a Project Manager/Analyst Developer, 11 years as a Software Development Manager for a team of 12 Software Engineers, 11 years as a Technical Consultant, 16 years as a Systems Architect and 3 years as the founding Director of ASB Software Development Limited.

He has two recent IBM Certifications for “The IBM DataFirst Method” and “Hybrid Cloud 2016” courses. He has a B.Sc. in Biochemistry from the University of Kent, Canterbury, United Kingdom. He is a Member of the British Computer Society (MBCS), and is a Chartered Information Technology Professional (CITP). He is also a British Computer Society (BCS), Digital IT Apprentice End Point Assessor (for Software Development).

About the Reviewer

Giles Metcalf has more than 30 years under his belt in the software arena, and he is an experienced software architect. He has a passion for robust and innovative software design, and has worked in a number of sectors, including financial services and banking, local and central government, logistics and distribution, pharma, telecoms and defense sectors. He has a deep knowledge of many software fields, including ECM, BPM, case management, UI design, ERM, document capture and processing, database design, security, cloud delivery, and integration. Giles has successfully delivered many solutions for a number of industries, often against very aggressive requirements and timescales, while still managing to go live on time and in budget!

He also has an experience in integrating many commercial products, recently delivering a complex AML investigation solution for a well-known high street bank.

He is a Certified FileNet Professional and IBM Datacap Designer, and is also an active member of both, the CITP (BCS) and the IASA. He was also qualified once, long ago, as a Certified PRINCE2 Practitioner. Giles lives near Cardiff in Wales, and when not frequenting the various watering holes in the area, he can be found in his man-

shed at the bottom of the garden, turning wooden ornaments or silversmithing items of jewelry.

Acknowledgements

There are a few people, whom I want to thank for their continued and ongoing support that they gave me, while I wrote this book. First and foremost, I would like to thank my wife, Jenny for continuously encouraging me to write the book—I could never have completed this book without her support.

I am grateful to the excellent online courses and materials provided by RedHat and IBM RedBooks I also extend my gratitude to the team at BPB Publication, for their support in allowing me to publish the book as a series in four parts, as IBM and RedHat Software installation covers a wide range of application products.

Preface

This series of books is a consolidation and rationalization of over 30 separate publications, describing the Installation and Configuration of IBM Software Products on RedHat Enterprise Linux 8.0, IBM Cloud, IBM Cloud Private (Community Edition), and the Windows 10 Operating System. To keep the volumes manageable, the book will be released as a series of four books.

This first book, in the series, is a consolidation and rationalization of 5 separate publications describing the Installation and Configuration of IBM Watson Analytics on RedHat Enterprise Linux 8.0, IBM Cloud, IBM Cloud Private (Community Edition), and the Windows 10 Operating System.

The book focuses on the initial preparation and configuration of the prerequisite requirements for each of the system platforms covered, and the initial installation and configuration of the supporting systems for the successful deployment of the IBM software products, which are listed as follows:

IBM Watson Explorer Foundational Components 12.x

IBM Watson Explorer oneWEX 12.x Docker Container IBM Cloud Private Installation

Installation of Eclipse Codewind and Docker Compose on RHEL 8 Linux with IBM Cloud Private CE (Community Edition)

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

Book-1

This book supplies useful guidance for installation and configuration, and provides trouble-shooting sections to improve the IT support productivity and fast resolution of the arising issues. It contains guidance on references available on-line, and the step-by-step procedures required for a successful installation of a broad range of IBM Data Analytics products.

The existing available documentation is often fragmented and focused on specific areas of support. This document provides a holistic in-depth resource for Software Architects, Installation specialists, and developers of Data Analysis software, and a handbook for the Data Analysts, who want a single source of information on IBM Data Analysis Software products. The rapid expansion of Technology, and the introduction of new Cloud Based systems provides an overwhelming information overload for hard-pressed IT technicians and Software Architects. This book supplies a single resource, which covers the latest available IBM Data Analysis software on the most recent RedHat Linux and IBM Cloud platforms.

This book is designed to provide a comprehensive introduction to enable an IT professional to gain an in-depth knowledge of the installation of a broad range of IBM Software products.

Book-2 This book is an expansion and rationalization of several separate publications describing the Installation and Configuration of the IBM Cognos Analytics software, and supporting systems on RedHat Enterprise Linux 8.0, IBM Cloud, IBM Cloud Private (Community Edition), and the Windows 10 Operating System. The book focuses on the initial preparation and configuration of the prerequisite requirements for each of the system platforms covered, and the initial installation and configuration of the supporting systems for successful deployment of the IBM software products, which are listed as follows:

Installation of IBM Cognos Analytics 11.1.0 Upgrade to IBM Cognos Analytics 11.1.4 Book-3 This book is a consolidation and rationalization over several publications describing the Installation and Configuration of IBM DB2 on RedHat Enterprise Linux 8.0, IBM Cloud, IBM Cloud

Private (Community Edition), and the Windows 10 Operating System. The book focuses on the initial preparation and configuration of the prerequisite requirements for each of the system platforms covered, and the initial installation and configuration of the supporting systems for successful deployment of the IBM software products, which are listed as follows: Jupyter notebook Installation on Linux RedHat RHEL 8 – Use with DB2 Graph 11.5 DB2 10.5 Installation DB2 11.5 Database on RedHat Linux RHEL 8.0 Database and Table creation using the Go Language Upgrade of IBM FileNet systems from DB2 10.5 FP 10 to latest DB2 11.5 version Book-4 This book is a consolidation and rationalization of more than a dozen separate publications describing the Installation and Configuration of IBM FileNet Software Products on RedHat Enterprise Linux 8.0, IBM Cloud, IBM Cloud Private (Community Edition), and the Windows 10 Operating System.

The book focuses on the initial preparation and configuration of the prerequisite requirements for each of the system platforms covered, and the initial installation and configuration of the supporting systems for successful deployment of the IBM software products, which are listed as follows: IBM BAW 18.0 - IBM Security Directory Suite 8.x

IBM FileNet P8 Java Development P8 Examples Supporting LibreOffice 6.3.x for IBM Content Navigator 3.x Client Document display and edit IBM CEBI Content Engine Bulk Import Document Batch Tool useage IBM Content Search Services 5.5.x Installation and Configuration IBM Case Manager Preparation of a new Target Object Store in a Filenet P8 Docker Container IBM BAW 18.0 - IBM Workflow Center 8.6.1.1900x

Case Manager 5.3.3 Installation with Content Navigator 3.0.x WebSphere 8.5.5.5 Installation and Configuration IBM Case Analyzer 5.5 Installation and Configuration

Case Monitor Dashboard 5.3.x plugin IBM Cloud Private and IBM FileNet P8 CPIT Installation IBM Content Navigator 3.0.x Installation IBM Content Foundation 5.5.x Installation

Oracle 12C on the Linux operating system Configuration for IBM Content Foundation 5.5.x IBM Security Directory Services 6.4 Importing Case Manager solution Auto Claims example into Case Manager 5.3.3

This is the first book of the series, and it will consist of the following fourteen chapters:

Chapter 1: This chapter covers the “Bill of Materials” for the IBM Information Management Products to be installed, with the download site URLs, Product Codes, Descriptions, and size and name of the download gzip tar files for each Software Package download.

Chapter 2: This chapter covers the references to IBM URLs, which can be used to generate tables listing the cross-compatibility

between the components of a system, which IBM have tested, and will support in a production environment. It includes descriptions for the interpretation of Product and Fix Pack online generation tool, and the downloadable supporting Excel spreadsheets, and their usage for the following products:

IBM Watson Explorer oneWEX 12.x Docker Container

IBM Watson Explorer Foundational Components 12.x IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

Chapter 3: This chapter describes the step-by-step download instructions, covering the list of products in Chapter 1 for the base Product and Fix Packs, and also covers the downloadable supporting systems for the products.

IBM StoredIQ can be downloaded as a VMware compatible .ova file. This includes its own CentOS 7 Operating System for direct loading to VMware, including VMware Workstation Pro 15.

Chapter 4: In this chapter, we will cover the installation of the Docker Container system, which is used, and describe the use and function of the main docker commands. We will introduce the chapter by creating a new Docker account, and then show how we can use this to install Docker on Linux RHEL 8.0, and on the Windows 10 Home edition operating systems. We will cover the creation of a Docker Compose file to enable the Build and run of

a new container app, and describe the use of a number of docker commands. Chapter 5: This chapter covers the IBM Fix Packs required for the upgrade of IBM Watson and StoredIQ software base installation versions targeted for installation. It describes the step-by-step procedures required to download the Fix Packs, and how to identify the correct version of a Fix Pack. Chapter 6: In this chapter, we will cover the setting up and installation of the prerequisites, and the download and installation of 3 different IBM Cloud Paks on a RedHat Linux RHEL 8.0 bare metal installation of Redhat OpenShift: IBM Cloud Pak for Data

IBM Cloud Pak for Multicloud Management IBM Cloud Pak for Security

Chapter 7: In this chapter, we will cover the installation procedure for a full OpenShift 4.5 cluster set-up and the installation of the Code Ready Container 4.5.9 system, and we will demonstrate the loading of the OpenShift administration console in a web browser. We will also cover the installation of a DNS server with the configuration required for the cluster, the supply of the required Nginx web server system, with installation and configuration of an HAproxy, Layer 4, load balancer.

Chapter 8: In this chapter, we will outline the procedure to create a server cluster, configure it with the required prerequisites for IBM Cloud Private installation and discuss the updates required to fix issues in the system.

The use of Docker pull to load the required containers for the system is described, with references to the description of the configuration of the config.yaml file needed for the installation. Chapter 9: In this chapter, we will cover the installation and upgrade of VMware Workstation Pro used to host virtual servers for Linux, Windows, and similar operating systems. The step-bystep procedures for configuring memory, disks and network cards are also covered, including the method required for modifying the BIOS boot order, used for the RedHat RHCOS operating system installation disk image.

Chapter 10: In this chapter, we will describe the procedure to create a server cluster, using CentOS 8.0 virtual servers, and configure it with the required prerequisites for IBM Cloud Private installation, updating to fix issues in the system.

The use of Docker pull to load the required containers for the system is described, with a complete description of the configuration of the config.yaml file needed for the installation. Chapter 11: In this chapter, we will cover the download and installation of IBM Watson Explorer Studio 11.0.1, and the creation of two examples of Custom Annotators using the java

programming language, including integration with an Oracle database table. The step-by-step procedure to deploy the resulting jar files as a UIMA pear file to an IBM Watson Content Analytics server are also covered.

Chapter 12: In this chapter, we will cover the download, installation, configuration, and some example usage of the IBM Watson Explorer Foundational Components V12.0.3.0 software. Chapter 13: In this chapter, we will cover the download, installation, configuration, and some example usage of the IBM Watson Explorer oneWEX container V12.0.3.0 software.

Chapter 14: In this chapter, we will cover the download and installation of the VM for IBM StoredIQ for legal 2.0.3.7. The integration of the role security using users searched from a separate LDAP Directory Server is demonstrated. The configuration for SMTP email communications to a gmail server is also covered, and the loading and activation of two sample Workflow definitions are described, and then the display of a workflow task step is shown.

Downloading the code bundle and coloured images:

Please follow the link to download the Code Bundle and the Coloured Images of the book:

https://rebrand.ly/998ca

Errata

We take immense pride in our work at BPB Publications and follow best practices to ensure the accuracy of our content to provide with an indulging reading experience to our subscribers. Our readers are our mirrors, and we use their inputs to reflect and improve upon human errors, if any, that may have occurred during the publishing processes involved. To let us maintain the quality and help us reach out to any readers who might be having difficulties due to any unforeseen errors, please write to us at :

[email protected]

Your support, suggestions and feedbacks are highly appreciated by the BPB Publications’ Family.

Did you know that BPB offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.bpbonline.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at [email protected] for more details.

At you can also read a collection of free technical articles, sign up for a range of free newsletters, and receive exclusive discounts and offers on BPB books and eBooks.

BPB is searching for authors like you

If you're interested in becoming an author for BPB, please visit www.bpbonline.com and apply today. We have worked with thousands of developers and tech professionals, just like you, to help them share their insight with the global tech community. You can make a general application, apply for a specific hot topic that we are recruiting an author for, or submit your own idea.

The code bundle for the book is also hosted on GitHub at In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available at Check them out!

PIRACY

If you come across any illegal copies of our works in any form on the internet, we would be grateful if you would provide us with the location address or website name. Please contact us at [email protected] with a link to the material. If you are interested in becoming an author

If there is a topic that you have expertise in, and you are interested in either writing or contributing to a book, please visit

REVIEWS

Please leave a review. Once you have read and used this book, why not leave a review on the site that you purchased it from? Potential readers can then see and use your unbiased opinion to make purchase decisions, we at BPB can understand what you think about our products, and our authors can see your feedback on their book. Thank you! For more information about BPB, please visit

Table of Contents

1. Getting started with IBM Resources for Analytics Introduction Structure: Objectives 1.1: Red Hat Linux RHEL 8.0 1.1.1: Download location, estimated download time, and version 1.1.2: License requirements UVU PVU 1.1.3: Fix pack location and versions 1.1.3.1: How to downgrade an installation for selected packages? 1.2: IBM Cloud 1.2.1: Download location, estimated download time, and version 1.2.2 License requirements UVU PVU 1.2.3 Fix pack location and versions 1.2.3.1: Lite 1.2.3.2: Standard v1 1.3: Red Hat OpenShift 4.5 1.3.1: Download location, estimated download time, and version 1.3.2: License requirements UVU PVU 1.3.2.1: License notice 1.3.2.2: Installation downloads for Red Hat OpenShift 4.5 1.3.3: Fix pack location and versions 1.4: IBM Watson 1.4.1: Download location, estimated download time, and versions 1.4.1.1: Downloads 1.4.1.2: If Download Director fails to run 1.4.1.3: IBM Watson Explorer Deep Analytics Edition Foundational Components Product details

1.4.1.4: IBM Watson Explorer Deep Analytics Edition oneWEX Product details 1.4.1.5: IBM Watson Explorer Deep Analytics Edition Analytical Components Product details 1.4.1.6: Copy the Watson Analytics, Foundation and oneWEX installation downloads 1.4.1.7: IBM Watson Explorer Analytical Component 1.4.1.8: Extraction of IBM Watson Explorer Foundational Components 1.4.1.9: Extraction of the IBM Watson Explorer Deep Analytics oneWEX Edition 1.4.2: License requirements UVU PVU 1.4.3: Fix Pack Location and versions 1.5 IBM Case Analyzer 5.5 1.5.1: Download location, estimated download time, and version 1.5.2: License requirements UVU PVU 1.5.3: Fix pack location and versions 1.6: IBM StoredIQ for Legal 2.0.3.7 1.6.1: Download location, estimated download time, and version 1.6.2: License requirements UVU PVU 1.6.3: Fix pack location and versions Conclusion Questions 2. IBM Component Software Compatibility Matrix Introduction Structure Objectives Compatibility matrix URLs 2.1: Fix Pack location and versions 2.1.1: Red Hat Linux upgrades

2.1.2: Version end of life support 2.2: IBM Watson Explorer oneWEX 12.x Docker Container 2.2.1: Compatibility issues and support limitations for the products listed in Chapter 1, Getting started with IBM Resources for Analytics 2.2.2: Supporting database, web applications, and operating system version limitations for the product 2.2.3: Component interactions with system architecture diagrams and performance issues 2.2.4: Upgrade paths and supported versions for upgrade 2.2.5: Version end-of-life and roadmaps 2.3: IBM Watson Explorer Foundational Components 12.x 2.3.1: Compatibility issues and support limitations for the products listed in Chapter 1, Getting started with IBM Resources for Analytics 2.3.2: Supporting database, web applications, and operating system version limitations for the products 2.3.3: Component interactions with system architecture diagrams and performance issues 2.3.4: Upgrade paths and supported versions for upgrade 2.3.5: Version end-of-life and roadmaps 2.4: IBM StoredIQ For Legal 2.0.3.7 2.4.1: Compatibility matrix URLs 2.4.2: Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics 2.4.3: Supporting database, web applications, and operating system version limitations for the products 2.4.4: Component interactions with system architecture diagrams and performance issues 2.4.5: Upgrade paths and supported versions for upgrade 2.4.6: End-of-life and roadmaps Conclusion

Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms 3. IBM Download Procedures Introduction Structure Objectives 3.1: IBM Watson Explorer Foundational Components 12.x 3.1.1: Downloading the IBM e-Assembly components for Linux 3.1.2: Product searching procedures 3.1.3: Product code lists - identifying the correct downloads 3.1.4: IBM Download Director installation and use 3.1.5: Red Hat and CentOS Linux download and use of subscription manager Install CENTOS Linux 8.2 on VMware 3.1.6: Use of FTP/SFTP, VMware mapped folders, and ssh/scp for file 3.2: IBM Watson Explorer oneWEX 12.x Docker Container 3.2.1: Downloading the IBM eAssembly components for Linux 3.2.2: Product code lists - identifying the correct downloads 3.2.3: Product searching procedures 3.2.4: IBM Download Director installation and use 3.2.5: Red Hat and CentOS Linux download 3.2.6: Use of FTP/SFTP, VMware mapped folders and ssh/scp for file 3.3: IBM StoredIQ for Legal VM 2.0.3.7 Server Installation 3.3.1: Downloading the IBM eAssembly components for Linux 3.3.2: Product code lists - identifying the correct downloads 3.3.3: Product searching procedures 3.3.4: IBM Download Director installation and use license restrictions

3.3.5: Red Hat Linux download 3.3.6: Use of FTP/SFTP, VMware mapped folders, and ssh/scp for file Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms

4. On-Premise Server Configurations and Prerequisites Introduction Structure Objectives 4.1: Docker account creation 4.2: Installing Docker 4.2.1: Installing Docker 18.09.2 on RHEL 8.0 4.2.2: Installing Docker Desktop 2.3.0.4 on Windows 10 Home Edition 4.2.2.1: Install the Linux kernel update package 4.2.2.2: Create an example Docker Container 4.2.2.3: Edit the Compose file to add a bind mount 4.3: Docker pull command 4.4: Docker exec command 4.5: Docker ps command 4.6 Docker run command 4.7: Experimenting with some other commands 4.8 Red Hat and CentOS 8.0 4.8.1: Use of Compatibility Matrix URLs 4.8.2: Use of Red Hat Linux upgrades 4.9: IBM Watson Explorer oneWEX 12.x Docker Container 4.9.1: Server(s) required for the installations 4.9.2: Red Hat Subscription Manager configurations

4.9.2.1: Enabling subscribe to the RHEL system 4.9.2.2: Change the host name to ecmukdemo10 4.9.2.3: Check available repositories 4.9.2.4: RHEL 8 system setup a remote repository 4.9.3: Memory and disk storage requirements and CPU cores required 4.9.4: Network card set-up and DNS configuration 4.9.4.1: VMware network card set-up for a static IP address 4.9.4.2: Install bind and configure to create a DNS server 4.9.5: GUI library installation requirements 4.9.5.1: X-Windows Terminal installation 4.9.6: Folder structures and user security 4.9.6.1: Preparation for IBM Security Directory Services 4.9.7: Shared folder access and Docker set up requirements 4.9.8: IBM Cloud Private Cluster set up and requirements 4.10: IBM Watson Explorer Foundational Components 12.x 4.10.1: Server(s) required for the installations 4.10.2: Red Hat Subscription Manager configurations 4.10.3: System requirements, CPU cores, DNS, and library installation requirements 4.10.4: Red Hat OpenShift server cluster requirements 4.11: IBM StoredIQ For Legal 2.0.3.7 4.11.1: Server(s) required for the installations 4.11.2: Red Hat Subscription Manager configurations 4.11.3: Memory and disk storage requirements and CPU cores required 4.11.4: Network card set-up and DNS configuration 4.11.5: GUI library installation requirements 4.11.6: Folder structures and user security 4.12: Compatibility Matrix URLs 4.13: IBM Watson Explorer Foundational Components 12.x 4.13.1: Compatibility issues and support limitations for the products listed in Chapter 1

4.13.1.1: For browsers 4.13.2: Server(s) required for the installations 4.13.3: Memory and disk storage requirements and CPU cores required 4.13.4: Folder structures and user security 4.13.5: Firewall – Windows Defender configuration 4.13.6: Supporting Java jdbc jar files and PATH environment set-up 4.13.7: Windows hosts file configuration for server network access 4.13.8: Stopping the running of windows services for install upgrades 4.13.9: Installation and configuration of IBM Watson Foundation Components 12.0.3.0 on Windows 10 Home Edition 4.13.9.1: Installing the other components 4.13.9.2: Procedure 4.13.9.3: Default login credentials

4.14: IBM Watson Explorer oneWEX 12.x Docker Container 4.14.1: Compatibility issues and support limitations for the products listed in Chapter 1 4.14.2: Server(s) required for the installations 4.14.3: Memory and disk storage requirements and CPU cores required 4.14.4: Folder structures and User security 4.14.5: Firewall – Windows Defender configuration 4.14.6: Supporting Java jdbc jar files and PATH environment set-up 4.14.7: Windows hosts file configuration for server network access 4.14.8: Stopping the running of Windows services for install upgrades 4.14.9: Installation and configuration of IBM Watson Explorer oneWEX 12.x on Windows Docker Container 4.15: Use of Compatibility Matrix URLs 4.16: Use of Red Hat Linux upgrades 4.17: RedHat OpenShift 4.x download and installation 4.17.1: Configuring the firewall 4.17.1.1: Installation Downloads 4.17.1.2: Prerequisites

4.17.1.3: Overview 4.17.2: Internet and telemetry access requirement 4.17.3: Server requirements for a cluster 4.17.4: Network connectivity requirements 4.17.4.1: Required servers Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms

5. IBM Fix Packs Introduction Structure Objectives 5.1: IBM Watson Explorer oneWEX 12.x Docker Container 5.1.1: Fix Pack product searching procedures 5.1.2: Downloading the Fix Pack components for Linux and Windows for correct upgrades 5.1.3: Fix Pack lists - identifying which fixes are cumulative 5.1.4: IBM Download Director installation and use for Fix Packs 5.1.5: License restrictions 5.1.6: Red Hat Linux Maintenance using Subscription Manager 5.2: IBM Watson Explorer Foundational Components 12.x 5.2.1: Fix Pack product searching procedures 5.2.2: Downloading the Fix Pack components for Linux and Windows for correct upgrades 5.2.3: Fix Pack lists - identifying which fixes are cumulative 5.2.4: License restrictions 5.3: IBM StoredIQ For Legal 2.0.3.7

5.3.1: Fix Pack product searching procedures 5.3.2: Downloading the Fix Pack components for Linux and Windows for correct upgrades 5.3.3: Fix Pack lists - identifying which fixes are cumulative 5.3.4: IBM Download Director installation and use for Fix Packs 5.3.5: License restrictions Conclusion Points to Remember Multiple Choice Questions

Multiple Choice Answers Questions Key terms 6. IBM Cloud PAK Systems Introduction Structure Objectives 6.1: Installation preparation 6.1.1: IBM Watson Explorer oneWEX 12.x Docker Container 6.1.2: Estimated download duration 6.2: IBM Cloud Pak for Data 6.2.1: Server(s) required for the installations 6.2.2: Installation procedure 6.2.3: IBM StoredIQ for Legal 2.0.3.7 6.2.3.1: Server(s) required for the Installations 6.3: IBM Cloud Pak for Multi-cloud Management 6.4: IBM Cloud Pak for Security Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers

Questions Key terms 7. Red Hat OpenShift 4.x Installations Introduction Structure Objectives 7.1: OpenShift 4.5 cluster installation 7.1.1: Overview 7.1.2: Set up each of the servers in the cluster with a static IP address 7.1.3: Prerequisites - required machines 7.1.3.1: Resolver configuration changes 7.1.3.2: Enabling the bind service at startup 7.1.4: Install bind and configure to create a DNS server 7.1.4.1: Enabling the bind service at startup 7.1.4.2: Configuration for a Single DNS server 7.1.5: Configuring the firewall 7.1.5.1: Edit for the subscription and the networks for other cluster servers 7.2: Installation Downloads 7.2.1: Load balancer HAProxy and NGINX web server installation 7.2.1.1: Layer 4 load balancing 7.2.1.2: Sticky Sessions 7.2.2: Update /etc/hosts file of the HAProxy server 7.2.3: Install NGINX and start its service 7.2.3.1: Test the HAProxy is working correctly 7.3: Bare metal installation 7.3.1: Generating an SSH private key and adding it to the agent 7.3.2: Obtaining the installation program 7.3.2.1: Installing the CLI by downloading the binary

7.3.2.2: Installing the CLI on Linux 7.3.2.3: Update the /etc/hosts file 7.4: Installation of the CodeReady Container for OpenShift 4.5.x Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms 8. IBM Cloud Private System Introduction Structure Objectives 8.1 IBM Cloud Private installation references and download 8.2: Installing a Linux DNS server on VMware 15.1 8.2.1: RHEL 8 download and install 8.2.2: Install Red Hat Linux 8.0 on VMware 8.3: Boot node requirements 8.3.1: RHEL 8 system registered through the Subscription Manager 8.3.2: Update of libraries and X-Window installs 8.4: Install bind and configure to create a DNS server 8.5: Installing Docker 18.09.2 on RHEL 8.0 8.6: Install IBM Private Cloud 8.6.1: System requirements 8.7: Master and Boot node requirements 8.7.1: Using docker pull on the MasterBoot node 8.8: Installation procedure Conclusion Points to Remember Multiple Choice Questions

Multiple Choice Answers Questions Key terms

9. Base VMware System Platform Introduction

Structure Objectives 9.1: Installing and upgrading of VMware Workstation Pro 15.1.0 9.2: Upgrading to VMware Workstation Pro 16.0 9.3: Installing an operating system from a disk .iso image 9.4: Setting VMware memory size 9.5: Setting VMware Disk Size and Types 9.6: Adding network cards 9.7: Adding mapped folders from the host system 9.8 Changing the boot options Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms 10. IBM Cloud Private Cluster on CentOS 8.0 Introduction Structure Objectives 10.1: IBM Cloud Private installation 10.1.1: Installing Linux DNS Server on VMware 15.1 10.1.1.1: CENTOS 8 download and install

10.2: VMWare 15.5 upgrade 10.2.1: Download CENTOS 8.0 iso image 10.2.1.1: Install CENTOS Linux 8.0 on VMware 10.3: Master and boot node requirements 10.3.1: CENTOS 8 system registered through the Subscription Manager 10.3.1.1: Change the host name to ecmukdemo20 10.4: Install bind and configure to create a DNS server 10.4.1: Configuring the firewall 10.4.1.1: Back up the main configuration files 10.4.1.2: Set up the DNS server with a static IP address 10.4.1.3: Resolver configuration changes 10.4.1.4: Enabling the bind service at startup 10.4.2: Reinstall VMware tools (if required) 10.4.3: Open firewall ports (for all three servers) 10.5: Installing Docker 18.09.2 on CENTOS 8.0 10.6: Install IBM Private Cloud 10.6.1: Master and Boot Node requirements 10.6.2: Create worker and proxy base systems 10.6.3: Open firewall ports (on all three servers) 10.6.4: Repeated sections for the proxy node 10.6.5: Using docker pull on the MasterBoot node 10.6.5.1: Master node requirements 10.6.6: Installation procedure 10.6.7: Repeated installation 10.6.8: Resolving the problem 10.6.8.1: Using FTP server – Procedure for Installation of FTP 10.6.9: Fix Pack 1907 for IBM Cloud Private 10.6.9.1: Fix Pack installation for IBM Cloud Private icp-3.2.0.1907 10.6.10: Fix Pack 3.2.1908 for IBM Cloud Private 10.6.10.1: Re-running the Fix Pack installation 10.6.10.2: Verify the installation

Conclusion Points to Remember

Multiple Choice Questions Multiple Choice Answers Questions Key terms

11. UIMA Pipeline and Java Code Extensions Introduction Structure Objectives 11.1: IBM Watson Content Analytics Studio Installation 11.1.1: Resolving the missing JVM problem 11.2: Incorporation of UIMA Apache Regular Expression Annotator 11.3: Transfer of a Custom Annotator to the ICA Server Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms 12. IBM Watson Explorer Foundational Components V12 Introduction Structure Objectives 12.1: Watson Foundational Component installation 12.1.1: Install Annotation Administration Console 12.1.2: Install Application Builder 12.1.3: Configuration of Application Builder

12.1.3.1: Default login credentials 12.1.4: Starting the services in order 12.2: Install the Results Module service 12.2.1: Check the status of the Results Module service 12.2.2: Install the AppBuilder service 12.2.2.1: Start the services in this order 12.2.2.2: Stopping Services 12.2.3: Open the ports on the firewall service 12.2.4: Add oneWEX datasource 12.2.5: Install Watson Explorer Engine 12.2.6: Installing the SIRE RPM file for Watson Explorer 12.3: Annotation Administration Console 12.4: Watson Explorer Engine administration tool installation 12.4.1: Encryption key generation 12.4.2: Checks on the system 12.4.2.1: Configure the Watson Explorer Engine embedded webserver (non-production use only) 12.4.2.2: Default login credentials 12.4.2.3: To unpack the repositories 12.4.2.4: Help About 12.5: Display creation tutorial Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms

13. IBM Watson Explorer oneWEX 12.0.3 Introduction Structure

Objectives 13.1: Downloads 13.1.1: IBM Watson Explorer Deep Analytics Edition oneWEX Product details 13.1.2: IBM Watson Explorer Deep Analytics Edition Analytical Components 13.1.3: Copy the Watson Analytics oneWEX installation downloads 13.1.4: IBM Watson Explorer Analytical 13.1.5: Extraction of the IBM Watson Explorer Deep Analytics oneWEX Edition 13.2: Installation of the IBM Watson Explorer Deep Analytics Edition 12.0.3 13.2.1: Installation of supporting Linux shared object libraries libXScrnSaver 13.2.2 Need to install the 64-bit version of the missing library shared object 13.3: Launch the IBM Watson Explorer GUI front end 13.3.1: Launch admin user interface 13.3.2: Add a collection for a file directory dataset 13.3.3: Download the Enron emails data to use as a dataset 13.3.4: CSV file example 13.4: Docker installed IBM Containers Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms

14. IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

Introduction Structure Objectives 14.1: IBM StoredIQ for Legal V 2.0.3.7 server installation steps for VMware Workstation Pro 15.5.6 14.1.1: Creating a test BPMN workflow 14.1.2: Adding an LDAP server 14.1.2.1: Assign roles 14.1.3: Configuring data requests 14.1.4: SMTP server gateway 14.1.4.1: SMTP server gateway for testing 14.1.4.2: Before you begin 14.1.4.3: Routing outbound mail using the SMTP relay service 14.1.4.4: Point the on-premise outbound server to Google 14.1.4.5: Additional configuration requirements 14.1.5: Adding roles to users 14.1.5.1: Add custom attributes 14.2: StoredIQ for Legal (VM): root certificate import 14.3: Approval process BPMN refined approval workflow 14.4: Backup of StoredIQ for Legal databases Conclusion Points to Remember Multiple Choice Questions Multiple Choice Answers Questions Key terms Appendix: References and End of Life Support Introduction Structure

Objectives IBM publication references Module overviews Supporting libraries and packages Application Builder and foundational components IBM Watson oneWEX links StoredIQ configuration Red Hat publication references ASB Software Development Ltd publication references End-of-Life support Red Hat Linux 8.0 End-of-Life support IBM Cloud End-of-Life support Red Hat OpenShift End-of-Life support IBM StoredIQ for Legal End-of-Life support IBM case analyser 5.5 End-of-Life support Index

CHAPTER 1 Getting started with IBM Resources for Analytics

Introduction

This book is a consolidation and rationalization of several separate publications describing the Installation and Configuration of IBM Watson Analytics on Red Hat Enterprise Linux 8.0, IBM Cloud, IBM Cloud Private (Community Edition), and the Windows 10 Operating System

The book focuses on the initial preparation and configuration of the prerequisite requirements for each of the system platforms covered, and the initial installation and configuration of the supporting systems for successful deployment of the IBM software products, which are listed as follows:

IBM Watson Explorer Foundational Components 12.x

IBM Watson Explorer oneWEX 12.x Docker Container

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

This chapter covers the Bill of Materials for the IBM Information Management System products to be installed, with the download site URLs, product codes, descriptions, and size and name of the download gzip, tar files for each software package download.

Structure:

In this chapter, we will discuss the following topics: Red Hat Linux RHEL 8.0

Download location, estimated download time, and version

License requirements User Value Unit Processor Value Unit Fix pack location and versions

IBM Cloud

Download location, estimated download time, and version

License requirements UVU PVU

Fix pack location and versions

Red Hat OpenShift 4.5 Download location, estimated download time, and version

License requirements UVU PVU

Fix pack location and versions

IBM Watson Explorer Foundational Components V12

Download location, estimated download time, and version

License requirements UVU PVU

Fix pack location and versions IBM Watson Explorer oneWEX 12.x Docker Container

Download location, estimated download time, and version License requirements UVU PVU

Fix pack location and versions IBM Case Analyzer 5.5

Download location, estimated download time, and version

License requirements UVU PVU Fix pack location and versions

IBM StoredIQ for Legal 2.0.3.7

Download location, estimated download time, and version License requirements UVU PVU

Fix pack location and versions

Objectives

After studying this unit, you should be able to: Locate and download the required software packages for installation.

Understand the prerequisite requirements for the target software to be installed, or know where to look for them.

1.1: Red Hat Linux RHEL 8.0

Red Hat has now been acquired by IBM, but has been given some independence (as of August 2020) in respect to its open source origins.

It has an open source Linux version called which is maintained in parallel with the commercial Red Hat Enterprise Linux versions.

1.1.1: Download location, estimated download time, and version

You can download RHEL 8.0 iso image file from the following URL location:

https://developers.redhat.com/products/rhel/download/

And then select the DVD iso file to download Red Hat Enterprise Linux 8.0 operating system, which is downloaded as an image file (with a file extension of This file can be loaded into VMware Workstation Pro version 15.1.0 virtual machine software or later versions, and holds a DVD disk image which can be booted to install the Linux Operating system.

The file, RHEL version 8.2 Linux DVD .iso file, can be selected; however this needs to be checked against IBM’s Compatibility Matrix for the IBM supported version with the target versions of the IBM Watson software, which are listed as follows:

IBM Watson Explorer Foundational Components 12.x

IBM Watson Explorer oneWEX 12.x Docker Container Click on the View Older Downloads link option to get a full list of available RHEL versions (I used RHEL Version 8.0).

The RHEL 8.0 OS is NOT needed for the IBM StoredIQ for Legal VM 2.0.3.7 server installation, as this is itself supplied as an installation, which is already a pre-built Virtual Machine .ova VMware file, based on CentOS 7. See Chapter 14, IBM StoredIQ for Legal VM 2.0.3.7 Server Installation for the full installation details.

1.1.2: License requirements UVU PVU

The Red Hat Linux RHEL 8.0 system can be loaded using a Developer License (FREE) for non-production purposes. This gives access to all the currently supported versions of Red Hat Linux (including versions 5 and 6 currently.)

See the following link: https://developers.redhat.com/products/rhel/download

The Red Hat Enterprise Linux 8.0 download is covered fully using the following URL:

https://doi.org/10.13140/RG.2.2.14590.95049

(Content Navigator 3.0.6 Installation on RHEL 8.0_V1.docx, on pages 15 – 20 of this word document, downloaded using the above DOI URL)

On the Download page, you will be able to download using the browser (I used AVG, version

Figure 1.1: The download progress of the DVD iso file shown in the browser, bottom left For RHEL 8.2, the download takes around 17 minutes for 7.9 GB.

You may find that the virus checker leaves the download unconfirmed if the space on the download drive is limited!

If so, and the size is as 7.9 GB, as above, just rename the file.

Figure 1.2: The highlighted link will give additional information and access to a number of Red Hat related eBooks

Figure 1.3: eBook free downloads (others are available!)

1.1.3: Fix pack location and versions

For Red Hat Linux RHEL 8.x, the subscription manager can be used together with the yum installer to upgrade packages (some examples are given in the preceding figure

1.1.3.1: How to downgrade an installation for selected packages?

The following is a real (and current) example of the use of yum downgrade to install the previous version of an installed package to effectively back out from an installed version on RHEL or CentOS.

Red Hat is currently advising users not to apply the GRUB2 security patches RHSA-2020:3216 or RHSA-2020:3217 until reboot failure issues have been resolved. If you administer a RHEL or CentOS system, and believe you may have installed these patches, do not reboot your Downgrade the affected packages using the following:

sudo yum downgrade shim\* grub2\* mokutil

and configure yum not to upgrade those packages by temporarily adding the following:

exclude=grub2* shim* mokutil to /etc/yum.conf. if so, in /etc/yum.conf append:

exclude=grub2* shim* mokutil

using vi/etc/yum.conf

Figure 1.4: Edit /etc/yum.conf as highlighted

1.2: IBM Cloud

IBM Cloud can be set up to use Red Hat (OpenShift based) systems remotely via the internet; this provides organisations a built and ready security system, full scalability, and flexible component installation to allow a fast route to a customised production environment for a large range of pre-built software container modules.

To create an IBM Cloud account, there is a free option for the trial of the software from the following link:

https://www.ibm.com/cloud

Figure 1.5: Select the Start for free link

See Chapter 10, IBM Cloud Private Cluster on CentOS for the full step by step details for installing and using this software.

1.2.1: Download location, estimated download time, and version

The following screen, Figure 1.6 below, shows the In screentext which is the initial home page you will see after logging into the IBM Cloud.

Figure 1.6: Logging into the IBM Cloud dashboard

The main download, initially required for using an IBM Cloud based system, is to install the IBM Cloud CLI client on an RHEL 8.0 server.

When you log into the installed IBM Cloud CLI using:

ibmcloud login -a cloud.ibm.com -sso

You are prompted from a launched browser to log into your IBM Cloud account and presented with a one-time pass code to copy

and use as a security token to allow access to retrieve a container using docker

This installs a local Docker container, which accesses other resources held in the IBM Cloud. (In my case, a local DB2 Graph container connecting to a remote Gremlin container on the IBM Cloud).

The container sizes are usually relatively small; for my example, it was less than 2 GB.

1.2.2 License requirements UVU PVU

This is the main browser page to the PDF downloads for the IBM SLA:

https://www-03.ibm.com/software/sla/sladb.nsf/sla/bm-7747-06

and links to the license agreements: https://www-03.ibm.com/software/sla/sladb.nsf/sla/home? OpenDocument

See the following link:

https://cloud.ibm.com/catalog

IBM Cloud catalog is used to find the components that can be used (there is a list of around 200 container packages, many of these are free to use).

Figure 1.7: The IBM Cloud software catalog browser page

1.2.3 Fix pack location and versions

See the following link: https://cloud.ibm.com/catalog/services/watson-studio

IBM Cloud fix packs are automatically applied by IBM, so there is no requirement to administer them (and, in fact, no need as these are regularly updated by IBM).

1.2.3.1: Lite

The Free Lite version of Watson Studio has the following resources allowed: 1 authorized user

50 capacity unit-hours monthly limit

Environment = # of capacity units required per hour 1 vCPU + 4 GB RAM = 0.5

2 vCPU + 8 GB RAM = 1

4 vCPU + 16 GB RAM = 2

Decision Optimization = Environment + 5

So, in the preceding resources mentioned, if a 4 virtual CPU system is selected with 16 GB of memory for Watson Studio, there will be around 7 hours available time per month. This can be calculated as follows: 50 units are available for a month, 2 units are required per hour for the environment, 5 additional units are required for the decision optimization per hour, so we need 7 units per hour.

50/(5 units for the Environment plus 2) = 50/7 hours = just over 7 hours

1.2.3.2: Standard v1

The next level is called this has the same unit allows unlimited viewer Processor Unit offering,

Standard v1 and it is a paid for service; capacity as the Lite (free) service but collaborators; it also has a Graphics unlike the Lite free version:

Price (as on 8th August 2020): $99.00 USD/instance

$0.50 USD/capacity unit-hour

$99.00 USD/authorized user

1 authorized user + unlimited viewer collaborators

50 capacity unit-hours included monthly (additional capacity available)

Unlimited elastic compute environments

Environment = # of capacity units required per hour 1 vCPU + 4 GB RAM = 0.5

2 vCPU + 8 GB RAM = 1

4 vCPU + 16 GB RAM = 2

8 vCPU + 32 GB RAM = 4

16 vCPU + 64 GB RAM = 8

4 vCPU + 24 GB RAM + 0.5 NVIDIA Tesla K80 (1 GPU) = 4

8 vCPU + 48 GB RAM + 1 NVIDIA Tesla K80 (2 GPU) = 8

16 vCPU + 96 GB RAM + 2 NVIDIA Tesla K80 (4 GPU) = 12 Decision Optimization = Environment + 5

NVIDIA K80 GPU environments available only in Dallas. The next level is called Enterprise V2 and the top level is applied for to IBM sales and is called SQO Enterprise See Cloud PAK For Data as a service documentation details: https://dataplatform.cloud.ibm.com/docs/content/wsj/gettingstarted/welcome-main.html?context=cpdaas

See Chapter 6, IBM Cloud PAK of this book for the full step by step details for installing and using this software. oneWEX for single container deployment does not support high availability (HA) and scale-out by adding additional containers.

1.3: Red Hat OpenShift 4.5

1.3.1: Download location, estimated download time, and version

https://cloud.redhat.com/openshift For the full access to the preceding URL, you need a Red Hat account.

See the following link: https://access.redhat.com/articles/4207611

For the full access to the preceding URL, you need a Red Hat account.

1.3.2: License requirements UVU PVU

Firstly, the installation guide is effectively governed by a creative commons attribution license:

1.3.2.1: License notice

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–ShareAlike 3.0 unported license. An explanation of CC-BY-SA is available at the following link:

http://creativecommons.org/licenses/by-sa/3.0/ In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.

See the following link:

https://access.redhat.com/documentation/enus/openshift_container_platform/4.5/html/installing_on_bare_metal/in dex

Deploying OpenShift 4.x on non-tested platforms using the bare metal install method (this is the method I have documented in Chapter 7, Red Hat OpenShift 4.x

1.3.2.2: Installation downloads for Red Hat OpenShift 4.5

https://cloud.redhat.com/openshift

Figure 1.8: Log in using a Red Hat account and select Create cluster

Figure 1.9: The bare metal option can be scrolled down to and selected

Figure 1.10: Select the Run on Bare Metal cluster option (highlighted)

Click on the OpenShift Installer Select OS drop-down. The downloaded file will be found in the browser downloads area and will need to be saved where required for loading. The downloaded openshift-install-linux.tar.gz file is copied to the bare metal Linux server, and will need to be unpacked using the tar -zxvf command for processing in the Linux environment.

Figure 1.11: Select the Download pull secret command button (highlighted)

The pull secret text file is a very small file with a code unique to your account and download session; it is required to be entered for a valid installation configuration.

Select the folder location for the pull secret file, See the following link:

https://docs.openshift.com/containerplatform/4.5/installing/installing_bare_metal/installing-baremetal.html#creating-machines-bare-metal See Chapter 7, On-premise server configurations and prerequisites – Red Hat OpenShift for the full download and installation of OpenShift 4.5. Also, note that IBM Cloud Pak for data will only function correctly up to OpenShift version 4.3, as of July 2020.

1.3.3: Fix pack location and versions

See the following link: https://docs.openshift.com/containerplatform/4.5/migration/migrating_4_2_4/migrating-applicationworkloads-4-2-4.html

Tools are provided for migration: The Cluster Application Migration tool is used to upgrade to newer versions of OpenShift.

The following URL lists the bug fix updates and provides links:

https://docs.openshift.com/container-platform/4.5/release_notes/ocp4-5-release-notes.html

1.4: IBM Watson

This section covers the download of both the Linux direct installation and container installation downloads of the following IBM Watson products:

IBM Watson Explorer Foundational Components V12, is the Linux direct installation (non-container) software. IBM Watson Explorer oneWEX 12.x Docker Container is the Docker container installation.

See the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/explorer_onewex.html

1.4.1: Download location, estimated download time, and versions

The full details of the download files can be found on page 4 of the following DOI URL document:

See the following link:

https://doi.org/10.13140/RG.2.2.12248.44803 IBM Watson Explorer oneWEX 12.0.3 Docker container installation on CentOS Linux 8.0.

1.4.1.1: Downloads

The product code, highlighted below, is specific to the version of IBM Watson Explorer Deep Analytics Edition to be downloaded:

Figure 1.12: The main IBM Watson Product code for searching CJ5DNML (highlighted)

The product code is useful to identify the specific IBM software product, as it can be used to search the software catalog to target the exact version required:

Figure 1.13: The product .package code, CC1G4EN for the Linux version of IBM Watson Explorer Deep Analytics software

To search and download the preceding installation, I logged into the IBM software catalog URL (google search “IBM Software Download Catalog”):

https://www.ibm.com/partnerworld/program/benefits/software-accesscatalog

Figure 1.14: Enter your IBM user ID and click Continue

Figure 1.15: Enter your IBM user password and click Continue

There is a link to create a new IBM id on the logon page, as shown in the preceding screenshot, which will allow a new user to apply for access (starting from July 2020, there is a new level of access to the IBM software value package, which provides an option for free access to download IBM software):

Figure 1.16: Scroll down to the bottom of the page Look carefully at the Software Access Catalog terms and conditions, as there are license limitations which restrict the number of downloads you can make, depending on the license level of your organization:

Figure 1.17: Review the terms of use and Click I agree (or cancel) The following page is shown for a specific agreement, which is recorded in a download history maintained by IBM:

Figure 1.18: Redirected to the Software Access Catalog Downloads page. Scroll down to search for the Software to download You can now search for an IBM software product, based either on a text search, as shown in the following screenshot, or the product code, as described earlier:

Figure 1.19: Enter the Product name or the Product code in the other search box The Screentext search text box has an active typeahead search, which attempts to give you a sub-set of matching products as you

type, but always use the product code if possible, as this should be an exact match:

Figure 1.20: Select the required IBM Watson installation tar (or .zip) files The two software packages, as shown in the preceding screenshot, are selected using tick boxes, for the Windows and Linux versions of IBM Watson Explorer Deep Analytics Edition, Foundational Components V12.0.3:

Figure 1.21: Select the I agree radio button to download The I agree radio button has to be selected for download to be initiated as shown in the preceding screenshot.

Figure 1.22: Click on Open IBM Download Director The Download Director option provides a streaming download of a Java-based program, which should prompt to be run, but recent changes to Windows 10 security updates can cause the launch of the program to fail, in which case you will get a pop-up window with a link, as shown in the following screenshot:

Figure 1.23: If the Download Director fails to start you may be prompted to install/re-install it

Figure 1.24: Follow the step-by-step instructions to install the Download Director

The preceding instructions are displayed, which you can follow to reload the Download Director .jnlp file.

Figure 1.25: Click on Install Download Director to complete the install

Figure 1.26: Save the downloaded Download Director .jnlp file to launch

The file IBM_install_DD.jnlp is downloaded and should be selected in the bottom left of the browser page, as shown in the following screenshot, so that it launches the Java program.

Figure 1.27: In the bottom left corner of the browser, double click on the .jnlp file

Figure 1.28: Click the Run command button to start the download of the selected software

1.4.1.2: If Download Director fails to run

There is a solution to this: using the HTTP option, as shown in the following screenshot:

Figure 1.29: At the top of the software selection page, change to using standard HTTP download (highlighted)

This change to HTTP loads a slightly different format of the software list on the page, such that you have to select using a single select radio-button interface shown as follows, rather than the tick-box multiple item select option available with Download Director:

Figure 1.30: On changing to this, you will see the selection change to radio button, so you can only select one download item at a time!

Figure 1.31: The HTTP file can be seen downloading in the bottom left browser page The preceding icon in the bottom left-hand corner of the browser page shows the progress of the download.

Figure 1.32: The HTTP downloaded file can be saved using the browser to the folder required

Figure 1.33: The details screen showing the date of download and size of two downloads

If you move a downloaded file to a different disk to make space (so effectively deleting it from the Download folder), then the file will still be displayed in the Download Director details list, but with a status of as shown in the preceding screenshot.

1.4.1.3: IBM Watson Explorer Deep Analytics Edition Foundational Components Product details File IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar Red Hat Entrprs Linx RHEL Base Srvr, Red Hat Entrprs Lnx RHEL Adv Pltfrm

English Related Estimated download duration

File 3,554,304,000 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

Figure 1.34: The download for IBM Watson oneWEX product code CC1GCML

In the preceding screenshot, the View details link will display the size and download speed text information, which can be cut and pasted for reference, as shown in the example shown at the start of this section, 1.4.1.3.

1.4.1.4: IBM Watson Explorer Deep Analytics Edition oneWEX Product details File IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar Red Hat Entrprs Linx RHEL Base Srvr, Red Hat Entrprs Lnx RHEL Adv Pltfrm

Chinese Simplified, Chinese Traditional, English, French, German, Italian, Japanese, Korean, Portuguese Brazilian, Spanish Related Estimated download duration

File 5,216,788,480 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

Figure 1.35: The download for IBM Watson Explorer Deep Analytics product code CC1G6ML

1.4.1.5: IBM Watson Explorer Deep Analytics Edition Analytical Components Product details OneWEX processes unstructured data (free text formatted files and text streams).

File IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar

Red Hat Entrprs Linx RHEL Base Srvr, Red Hat Entrprs Lnx RHEL Adv Pltfrm Chinese Simplified, Chinese Traditional, English, French, German, Italian, Japanese, Korean, Portuguese Brazilian, Spanish

Related Estimated download duration

File 4,830,801,920 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

Figure 1.36: Summary of the Downloads for IBM Watson products on Linux

Figure 1.37: The existing servers being targeted for IBM Cloud private installation of IBM Watson

See the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12.0. 0.html

Watson Explorer oneWEX now has a combination of exploration and content analytics components. The is a Docker container based, cloud ready solution.

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_install_docker.html

Create the installation directory on the Linux server: cd /opt mkdir watson cd watson Copy the oneWEX and other tar files downloaded to the /opt/watson directory.

1.4.1.6: Copy the Watson Analytics, Foundation and oneWEX installation downloads Copy from FTP transfer to /home/wasadm (using the VMware Master Boot Cloud Private server); the commands to enter in a Linux command window is shown as follows: (logged in as root)

[root@ecmukdemo20 tmp]# cd /opt/watson/

[root@ecmukdemo20 watson]# ls [root@ecmukdemo20 watson]# cp /home/wasadm/IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar .

[root@ecmukdemo20 watson]# cp /home/wasadm/IBM_WE*.tar .

[root@ecmukdemo20 watson]# ls

IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar

1.4.1.7: IBM Watson Explorer Analytical Component

The download of the components for IBM Watson oneWEX and IBM Watson Explorer Foundational Components is fully covered in the publication:

https://doi.org/10.13140/RG.2.2.12248.44803

IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, Pages 4 to 8.

1.4.1.8: Extraction of IBM Watson Explorer Foundational Components https://doi.org/10.13140/RG.2.2.12248.44803

IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, Page 9.

1.4.1.9: Extraction of the IBM Watson Explorer Deep Analytics oneWEX Edition https://doi.org/10.13140/RG.2.2.12248.44803

IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, Page

1.4.2: License requirements UVU PVU

See the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.uni.doc/slmtags.html

The IBM Watson Explorer installer adds a product-specific tag file. This tag file is located in the installation directory of each software component and is named in a specific format; for example,

There is a license metric tool to report the usage levels used.

See the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8JFY_9.2.0/com. ibm.lmt.doc/welcome/LMT_welcome.html

The following URL is the main link I use to licensing information and so on: https://www.ibm.com/software/passportadvantage/subcaplicensing.ht ml

This URL gives the link to PVU licensing:

https://www.ibm.com/software/passportadvantage/pvu_licensing_for_ customers.html

The download also has the full license information in a link called License

Figure 1.38: The full license agreement can be loaded using the link (highlighted)

1.4.3: Fix Pack Location and versions

The following URL describes the process required to upgrade from 12.0.3 base. The current version fix as of August 2020 is 12.0.3.4:

https://www.ibm.com/support/pages/watson-explorer-deep-analyticsedition-v12031-readme

Fix central URL is: https://www.ibm.com/support/fixcentral/

(This is not used for container versions)

1.5 IBM Case Analyzer 5.5

1.5.1: Download location, estimated download time, and version

Case Analyzer is a subcomponent of IBM Case Foundation for FileNet P8, and after creating a DB2 CASTORE database and adding XA and non-XA data sources in WebSphere, it is just activated, as described on pages 5 to 14 of the book accessed using the following DOI URL:

https://doi.org/10.13140/RG.2.2.11682.38089 IBM Case Analyzer 5.5 Installation and Configuration On RHEL 8.0 for Case Monitor Dashboard 5.3.3 plugin

1.5.2: License requirements UVU PVU

Licensing is based on the license for IBM Content Foundation, which uses the IBM FileNet Document Management Object Store engine since Case Analyser is a component of this system.

The following URL is the main link I use to licensing information and so on: https://www.ibm.com/software/passportadvantage/subcaplicensing.ht ml

This URL gives the link to PVU licensing:

https://www.ibm.com/software/passportadvantage/pvu_licensing_for_ customers.html

1.5.3: Fix pack location and versions

Fix pack details are covered in the BPB book: Installation and Configuration of IBM FileNet Information Management

1.6: IBM StoredIQ for Legal 2.0.3.7

1.6.1: Download location, estimated download time, and version

OVF format to VMware runtime format. You can import both .ovf and .ova files.

The full download and product details are covered on pages 5 to 10 of the following link downloaded as:

https://doi.org/10.13140/RG.2.2.12586.24008

(See Chapter 14, IBM StoredIQ for Legal VM 2.0.3.7 Server Installation for the full installation procedure.)

1.6.2: License requirements UVU PVU

The license information specific to IBM StoredIQ for Legal 2.0.3.x is found in the following URL:

https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.plan.doc/p_license.html

1.6.3: Fix pack location and versions

The support for IBM fix central downloads is described in the following URL:

https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.trouble.doc/ts_fixes_fc.html

For version 2.0.3.7 VM, the URL is as follows: https://www.ibm.com/support/fixcentral/options? selectionBean.selectedTab=find&selection=Enterprise+Content+Manage ment%3bibm%2fInformation+Management%2fStoredIQ+for+Legal

Select the required version in the drop-box.

Starting with version 2.0.3.10, you can deploy and configure StoredIQ for Legal in a Red Hat® OpenShift environment.

Conclusion

This chapter has covered the download procedures and system requirements to enable you to retrieve the base installation products, and fix pack updates of the following IBM IMS products covered by this book:

IBM Watson Explorer Foundational Components 12.x IBM Watson Explorer oneWEX 12.x Docker Container

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

It has also covered the download or access required for the supporting OS environments and platforms as follows:

IBM Cloud

Red Hat RHEL 8.0 Linux

In the next chapter, you will learn how to identify and retrieve the references to IBM URLs, which can be used to generate tables, listing the cross-compatibility between the components of a system, which IBM has tested, and will support in a production environment that will then help you successfully install and

configure the target software components to be installed, and know where to look for them.

Questions

Which version is the last supported version of Red Hat OpenShift for IBM Cloud Pak for data?

For how long are the releases of Red Hat OpenShift version 4 maintained after GA? (You will need to view the Appendix of this book to answer this question.) In what file format does IBM provide the downloadable compatibility matrix report? (You will need to view Chapter 2, IBM Component Software Compatibility Matrix of this book to answer this question.)

How can you customize the sections you want to print using the IBM compatibility matrix reporting tool? (You will need to view Chapter 4 of this book to answer this question.)

What is the file format for the IBM StoredIQ for Legal (VM) 2.0.3.7 download package?

From which version onwards of IBM StoredIQ for Legal is Red Hat OpenShift supported?

CHAPTER 2 IBM Component Software Compatibility Matrix

Introduction

This chapter covers the references to IBM URLs that can be used to generate tables listing the cross-compatibility between the components of a system, which IBM has tested, and will support in a production environment. It includes descriptions for the interpretation of product and Fix Pack online generation tool, and the downloadable supporting Excel spreadsheets and their usage for the following products: IBM Watson Explorer oneWEX 12.x Docker Container

IBM Watson Explorer Foundational Components 12.x

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

Structure

In this chapter, we will discuss the following topics: Compatibility matrix URLs

Fix Pack location and versions

Red Hat Linux upgrades Version end of life support

IBM Watson Explorer oneWEX 12.x Docker Container

Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics

Supporting database, web applications, and operating system version limitations for the products

Component interactions with system architecture diagrams and performance issues Upgrade paths and supported versions for upgrade

Version end-of-life and roadmaps

IBM Watson Explorer Foundational Components 12.x

Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics

Supporting database, web applications, and operating system version limitations for the products

Component interactions with system architecture diagrams and performance issues

Upgrade paths and supported versions for upgrade Version end-of-life and roadmaps

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation Compatibility matrix URLs Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics Supporting database, web applications, and operating system version limitations for the products

Component interactions with system architecture diagrams and performance issues Upgrade paths and supported versions for upgrade

Objectives

After studying this unit, you should be able to: Identify suitable versions of each of the system components, which will be required to support the IBM Watson and StoredIQ software versions targeted for installation.

Understand the prerequisite requirements for the target software components to be installed and know where to look for them.

Search, identify, and download the latest Fix Packs required to maintain a secure and robust system.

Compatibility matrix URLs

The following steps can be followed to retrieve the reports for a selected IBM Software package. In this chapter, we are interested in the compatibility matrices for IBM Watson Explorer products and IBM Stored IQ for Legal (VM) 2.0.3.7.

For IBM Watson versions, first check the release notes: Release Notes - IBM Watson Explorer Foundational Components, Version 12.0:

https://www.ibm.com/support/pages/release-notes-ibm-watsonexplorer-foundational-components-version-120#inst12034

The preceding link is useful, as it highlights changes in supported systems, over different versions; for example:

“Red Hat Enterprise Linux versions 6 are not supported in Version 12.0.3.3 or later.”

Compatibility reports can be obtained for IBM Software products at the following link:

https://www.ibm.com/support/pages/software-product-compatibilityreports

From the preceding link, enter the name of the product to list the compatibility matrix link.

Figure 2.1: To find an IBM Software Product, enter the text to search

The search box as shown in the preceding screenshot, is a typing event driven search box, which actively searches after every character entered and highlights the matched words entered in the result list. From this list, the required IBM Watson product can be clicked to load the corresponding IBM Software product support page. To find the actual compatibility matrix, the aforementioned page has the following URL:

page of the IBM Support http://ow.ly/cWfHz

This link, in step expands to the URL, as follows: https://www.ibm.com/software/reports/compatibility/clarity/index.html

Reference link is as follows:

https://www.ibm.com/support/pages/watson-explorer-version-120system-requirements#wex1203 The preceding URL lists the support for various operating systems (Linux, Windows, and AIX). This shows that IBM Watson oneWEX version 12.0.3 containers are supported both for IBM Cloud Private, and single container deployment up to RHEL 7.8 only!

Currently, IBM Watson Explorer oneWEX is not supported on OpenShift. IBM Watson Explorer oneWEX is a third-party product. Supportability and installation instructions have to be answered by IBM. URLs for minimum hardware requirements are as follows: For OpenShift 3.10 https://docs.openshift.com/containerplatform/3.10/install/prerequisites.html For OpenShift 2.5 https://docs.openshift.com/containerplatform/2.5/installing/installing_bare_metal/installing-bare-metalnetwork-customizations.html

Reference reports

https://www.ibm.com/software/reports/compatibility/clarityreports/report/html/hardwareReqsForProduct? deliverableId=EAAC8DD0522711E982882C5D069DA07A&osPlatforms= AIX|Linux|Windows&duComponentIds=S004

The preceding URL loads the IBM Software compatibility matrix. This shows that IBM support is currently only up to Red Hat Linux RHEL 7.9, but I will demonstrate how to install and use it for development at RHEL 8.0.

The IBM FileNet P8 compatibility matrix for version 5.5.3 of FileNet P8 is available as a downloadable Excel file 5.5.3 and later fix pack compatibility in the TechNote URL: https://www.ibm.com/support/pages/node/321543

The IBM StoredIQ compatibility matrix URL can be found at the following link: https://www.ibm.com/software/reports/compatibility/clarityreports/report/html/softwareReqsForProduct? deliverableId=8A0331A0C50D11E58D9C0D684F363D68 This link allows a customised PDF to be generated.

2.1: Fix Pack location and versions

The main IBM Fix Pack location to search is called Fix Central and has the following URL:

https://www.ibm.com/support/fixcentral/

Figure 2.2: The Select product option is preferable to target the required Fix Pack

Following these steps, you will be able to reach the pages showing the Fix Packs for the IBM Software products for IBM Watson:

From the URL browser page in the previous section, as shown in the preceding screenshot, I recommend you to select the Select product option as highlighted in the following screenshot:

Figure 2.3: Select the Watson Group option from the dropdown

Then, from the Product Group dropdown, scroll down and select the Watson Group option from the dropdown box, and then select from the IBM Watson software products listed:

Figure 2.4: Select the Watson Explorer (or other required product) from the group The Watson Group covers the products we are focussed on in this book. As an example, selecting the Watson Explorer option (highlighted in the preceding screenshot) then displays a prompt to scroll down for the required version, as shown in the following screenshot:

Figure 2.5: Scroll down to select the required Watson Explorer version, 12.0.3.4

The selection of the IBM Watson Version 12.0.3.4 in the preceding screenshot, next gives the option of the operating system platform to choose, as shown in the following screenshot:

Figure 2.6: Scroll down to select the required platform

AIX is the top option in the Platform selection box, but I chose so that I can select Linux and Windows on the results page.

After selecting from you can click on the Continue command button.

Figure 2.7: The radio button can be used to select from 4 search options to retrieve fixes

For the radio button selection, I recommend using the default, Browse for and click on the Continue button. If no results are found (quite possible, if 12.0.3.4 is the latest version), then the search results can be adjusted on the results page, and the Submit button clicked:

Figure 2.8: From the search results page, the search criteria can be adjusted

The results are shown with the Fix Packs which are available.

For IBM Watson Explorer, the Fix Central results are sub-divided into sections. The first section is called and if you hover the mouse on an item, it will show the details in a pop-up window, as shown in the following screenshot:

Figure 2.9: Shows the details of an interim fix for Watson WCM connector

When you scroll down, the next section of the browser page is labelled and the list of these are often interim fixes for JRE support packages for fixing security vulnerabilities, and so on.

The third section of the browser page shows the list of actual Fix Packs, and it should be noted that they are usually (but not always) platform specific and are also cumulative; so the latest Fix Pack will apply the fixes of earlier fix packs, so there is no need to apply the earlier (lower numbered) listed Fix Packs.

Figure 2.10: Shows the mouse-over detail for the Windows platform Fix Pack FP004 (12.0.1.4) for IBM Watson Explorer DAEoneWEX

2.1.1: Red Hat Linux upgrades

For Red Hat Linux RHEL 8.x, the subscription manager can be used together with the yum installer to upgrade packages.

Chapter 1, Getting Started with IBM Resources for shows the main location for download of RHEL 8.0, and the versions available for supporting a production system. In figure I have selected the Linux and Windows platform Fix Packs for IBM Watson Explorer, and the base installation 12.0.3.0.

IBM StoredIQ can be downloaded as a VMware compatible .ova file. This includes its own CentOS 7 operating system for direct loading to VMware, including VMware Workstation Pro 15.5, so that it does not have so many issues of compatibility, but it still requires supporting Windows hypervisor and VMware virtual machine host version recommendations for a production environment. For example, in this instance, the supported VM for production is supported with VMware vSphere 6.5 from StoredIQ for Legal (VM) version 2.0.3.9 onwards.

2.1.2: Version end of life support

The following URL gives IBM’s general guidance on end of life support:

https://www.ibm.com/software/passportadvantage/endofsupport_ov.ht ml

A csv product list can be downloaded from the following URL: https://www.ibm.com/support/pages/software-lifecycle-product-list

This list can be searched in Excel, and provides the following URL for support of IBM StoredIQ for the Information Lifecycle Governance products support as an example:

https://www.ibm.com/support/pages/node/563277

Version end-of-life and roadmaps.

2.2: IBM Watson Explorer oneWEX 12.x Docker Container

There is an overview of oneWEX on the following IBM support site browser page:

https://www.ibm.com/support/pages/watson-explorer-version-1203onewex

This link covers the 28 June, 2019 base release of oneWEX 12.0.3. This has separate links for hardware and operating system supported environments. Very helpfully, it also has a full list of the part numbers of the versions of oneWEX, which are supported on IBM Cloud Private, Linux, and Windows operating systems. On this browser page, find the section as follows:

Figure 2.11: To navigate to the oneWEX Sofware compatibility matrix, click the highlighted link A PDF file of the report can be generated after selecting the required components of interest, which is described in the following section, 2.2.1.

2.2.1: Compatibility issues and support limitations for the products listed in Chapter 1, Getting started with IBM Resources for Analytics The following are some example issues, which I have provided to illustrate the resolutions:

Issues are often resolved over time, so you need to follow the guidance described in the procedures for checking the compatibility matrix below and view the current pages provided. The following is applicable for oneWEX for a single container deployment.

With WEX V12.0.3, ICP Foundation is bundled as a supporting program for licensing and supported use. You can download ICP Foundation plus WEX V12.0.3.

Docker Community Edition used for loading the oneWEX container, is for developers only.

NOTE: Docker is licensed under the Apache license, version 2.0.

Reference link is as follows: https://github.com/moby/moby/blob/master/LICENSE

Also, note that Windows 2016 Server is not a certified operating system for Docker CE. For development, oneWEX can be deployed, and it can work on the Windows 2016 Server/Docker CE combination. Note that IBM support for a problem caused by this non-certified combination is limited.

For support from IBM, they recommended that the Docker Enterprise Edition (EE) is used with Windows Server 2016.

Production environments for oneWEX container installation should be on a certified combination of operating system and Docker editions, such as Red Hat Enterprise Linux and Docker Enterprise Edition. oneWEX can be deployed and work on Windows 10 with Docker CE for Windows. However, if Windows 10 is used for production, even for small scale use, note should be taken of the possible performance limitations in this system environment.

The following example procedure was used to generate a software compatibility matrix report:

https://www.ibm.com/software/reports/compatibility/clarity/index.html

Figure 2.12: This is the top-level page for the Software Product Compatibility Reports Click on the link below, to show the main IBM software compatibility web page, shown in Figure above. https://www.ibm.com/support/pages/software-product-compatibilityreports Click on the preceding URL to display the browser page, as shown in the preceding screenshot, and select from the in-depth reports bottom section, to follow the Create a report link.

This gives the URL as follows, which will display the page, as shown in the following screenshot:

https://www.ibm.com/software/reports/compatibility/clarity/softwareR eqsForProduct.html

Figure 2.13: Enter IBM Watson Explorer as the search string gives the options

Select the Watson Explorer Deep Analytics and then select 12.0.3 from the Version dropdown box, as highlighted in the preceding screenshot.

This title “Watson Explorer Deep analytics Edition” is actually synonymous with the title “IBM Watson Explorer oneWEX 12.x Docker Container” software component. You need to be aware that IBM software product names can change over time, but sometimes technical guides have the older name (or vice versa!).

Entering a tick in the Show fix packs checkbox, expands the Fix Pack versions for selection:

Figure 2.14: The Fix Pack versions can be displayed by ticking the Show fix packs checkbox

The Filters option allows the selection of just a sub-set of topics to be printed in the PDF report that is generated. The Filter option checkboxes are displayed by clicking the option section openers on the page:

Figure 2.15: The selected Capabilities for the Fix Pack Compatibility PDF Report

Tick or untick the options for information in each of the categories to customise the PDF generated report, then click on the Submit button.

(I just selected the Linux and Windows Operating system platform options.) This shows the results page as follows:

Figure 2.16: The resulting report of the Compatibility Matrix

In the preceding screenshot, we can see the compatible supported Hypervisors operating systems for Linux (you can scroll down on this browser page, if you wish to see the Windows section):

Figure 2.17: Click on the Download PDF link (highlighted) Select the Download PDF link, as shown in the preceding screenshot, then click on the Proceed command button, shown as follows, which gives you a further chance to select a sub-set of the report:

Figure 2.18: Select the compatibility options to publish and click Proceed

The file, FDSRPDF-2020-08-14.pdf is now downloaded.

Figure 2.19: The downloaded PDF is date-stamped with the current date

You may have noticed that the latest guest operating system that is supported for production use is only up to Red Hat Enterprise Linux RHEL Server 7 versions, and then only using VMWare ESXi up to 6.5, but I will demonstrate that this does not mean the product won’t work on a development platform with later versions, such as Red Hat Enterprise Linux RHEL 8.0 or CentOS 8.2, using other Hypervisor versions, such as VMware Workstation Pro 15.5.6. It is often possible to install and run on later versions, but not for a production environment (where you would not be entitled to IBM support). This is because IBM undertakes extensive testing of its software products before it validates a version for General Access (GA) release.

Figure 2.20: The guest operating system support for VMware ESXi 6.5

This procedure produces a downloadable PDF report, and you can see only RHEL 7.x is currently (as of August 2020) supported; so

you MUST use this for a production system, but I am going to show you how to install and run at RHEL 8.0, and fix the zlib issue which may be what was stopping IBM from validating the Red Hat RHEL 8.0 version.

2.2.2: Supporting database, web applications, and operating system version limitations for the product The IBM Cloud Client installation is a pre-requisite for any Cloud based version of the IBM Watson software, such as OneWEX, when you wish to provision a link to this from a private server system.

IBM Cloud To install the Cloud Client, which enables access of IBM Cloud based systems, you need to create an IBM Cloud account. (See Chapter 1, Getting Started with IBM Resources for

Reference link is as follows:

https://cloud.ibm.com/docs/cli?topic=cli-getting-started

Red Hat OpenShift 2.5

Reference link is as follows:

https://access.redhat.com/solutions/3781851 You need a RedHat Developer account to log into this URL.

Question issues asked are as follows:

Is IBM Watson Explorer oneWEX supported on OpenShift?

How to install IBM Watson Explorer oneWEX on OpenShift?

Note that you will need to have a Red Hat active subscription to see the results of the above support question.

2.2.3: Component interactions with system architecture diagrams and performance issues For the best overview of the architecture, download the IBM Redbook, Building 360-Degree Information sg248133 (where sg248133 is the IBM red Book unique reference) as a PDF and view page 7 onwards.

Reference link is as follows: http://www.redbooks.ibm.com/redbooks/pdfs/sg248133.pdf

See the diagram in this Redbook, Figure 1-3 Watson Explorer architecture.

2.2.4: Upgrade paths and supported versions for upgrade

To download the latest Fix Pack for the oneWEX components, you must log into IBM support; Fix Central to browse for all available downloads:

Reference link is as follows:

http://www.ibm.com/support/fixcentral/ In Product Watson Group

In Product: Watson Explorer

In Installed 12.0.3.0 (the base version)

In All

On the Identify Fixes page, keep Browse for fixes selected (the radio command button) and click

On the Select Fixes page, select the packages that you want to download, and click

A step-by-step procedure for the preceding outline procedure is covered for both IBM Watson oneWEX 12.x and IBM Watson Explorer Foundational Components in Section 2.3.4 below.

2.2.5: Version end-of-life and roadmaps

The excel spreadsheet, can be downloaded from the following URL:

https://www.ibm.com/support/pages/software-lifecycle-product-list

This spreadsheet can be searched in Excel for the string Watson in a cell, and this shows an entry, which is currently in row 7397 of the IBM excel spreadsheet.

This row has a column for the product name set as Watson Explorer Deep Analytics which is synonymous with IBM Watson Explorer oneWEX. From this, you will see a column with the GA Date of February, 2018; also, there is a blank cell for the EOS column, so there is no date set for End of Support currently.

2.3: IBM Watson Explorer Foundational Components 12.x

The Watson Explorer Foundational Components 12.0.3.0 consists of a set of Red Hat Package Manager installation files contained in a Linux tar file which, after download, can then be copied, unpacked with the tar command and installed with the yum install utility on the target Linux operating system platform.

2.3.1: Compatibility issues and support limitations for the products listed in Chapter 1, Getting started with IBM Resources for Analytics Using the URL reference link, as follows: https://www.ibm.com/support/pages/watson-explorer-version-12031foundational-components

Select the tab reference, as follows: https://www.ibm.com/support/pages/node/1073924

for Watson Explorer Version 12.0.3.1 Foundational Components Fix pack release notes.

Next, search the compatibility matrix, using the Section 2.2.1 stepby step procedure for accessing the IBM compatibility matrix, starting at the following URL:

https://www.ibm.com/software/reports/compatibility/clarity/index.html

Then, using this, the URL as follows, will display the page, as shown in Figure 2.13 in Section https://www.ibm.com/software/reports/compatibility/clarity/softwareR eqsForProduct.html

The only change to this procedure is to select the Watson Explorer option in the Results List in Figure (Note that this currently shows the latest version as 11.0.2.0, and latest release covered is Watson Explorer Foundational Components 11.0.2.8, but it will give you all the required pre-requisite Linux libraries required to be installed).

2.3.2: Supporting database, web applications, and operating system version limitations for the products When you use Annotation Administration Console the following 32bit libraries are required on Linux x86-64 systems:

- libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit) - libstdc++ (libstdc++.i686 / libstdc++6-32bit) - zlib (zlib.i686 / libz1-32bit / zlib-32bit) - libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit) - libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) - libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) - libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit) - libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit) "compat-libstdc++-33"

The package will be found in the optional packaging repository. You may need to configure the repository properly.

The following 32-bit libraries are required on Linux x86-64 systems:

-

libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit) libstdc++ (libstdc++.i686 / libstdc++6-32bit) zlib (zlib.i686 / libz1-32bit / zlib-32bit) libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit) libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit)

- libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit)

If you want to support the ability to generate thumbnails for certain types of documents in the search results, you must install the following libraries:

- libXm - libXt

The following 32-bit libraries are required on Linux x86-64 systems: - libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit) - libstdc++ (libstdc++.i686 / libstdc++6-32bit) - zlib (zlib.i686 / libz1-32bit / zlib-32bit) - libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit) - libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) - libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) - libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit) - libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit) If you want to support the ability to generate thumbnails for certain types of documents in the search results, you must install the following libraries: - libXm - libXt Support of Watson Explorer Analytical Components with Watson Knowledge Studio Annotator Support is available on RHEL 7.0, or

later fix packs only.

https://www.ibm.com/mysupport/s/topic/0TO500000002D9NGAU/w atson-explorer?language=en_US&productId=01t50000004XO7F

and, Release Notes - IBM Watson Explorer Foundational Components, Version 12.0. Reference link is as follows: https://www.ibm.com/support/pages/node/618669

2.3.3: Component interactions with system architecture diagrams and performance issues The URL for Watson Explorer Version 12.0.3.1 Foundational Components overview can be found in the following link:

https://www.ibm.com/support/pages/node/1073924

And the following URL has the main IBM support page: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.welcome.doc/doc/explorer_foundation. html

A component overview is available using the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.install.doc/c_module_oview.html

2.3.4: Upgrade paths and supported versions for upgrade

To download the latest Fix Pack for the foundational components, you must log in to IBM support, Fix Central to browse for all available downloads.

Reference link is as follows:

http://www.ibm.com/support/fixcentral/ In Product Watson Group

In Product: Watson Explorer

In Installed 12.0.3.0 base version)

In All

On the Identify Fixes page, keep Browse for fixes selected (radio command button) and click

On the Select Fixes page, select the packages that you want to download and click

The download terms have to be agreed – view and understand the IBM terms of the download, and click on I agree in the browser page, as shown in the following screenshots:

Figure 2.21: The Download terms have to be agreed

Figure 2.22: Click on Download now to start the Download Click on Download

Figure 2.23: You can select sftp file transfer for the Fix Pack download

Figure 2.24: The server, user, and password details, specific to you are displayed You need to run the sftp command in the form: sftp

For example, for me this was: sftp [email protected] (Limited time user name and password given.) (base) [root@ECMUKDEMO6 /opt

(base) [root@ECMUKDEMO6 (base) [root@ECMUKDEMO6 (base) [root@ECMUKDEMO6 [email protected] [email protected]'s password: Connected to [email protected]. readme.txtwex-aac-12.0.3.4-dae.tarwex-appbuilder-12.0.3.4dae_en.el6.rpm wex-bigindex-12.0.3.4-dae_en.el6.rpm wex-engine-12.0.3.4dae_en.el6.rpm wex-resultsmodule-12.0.3.4-dae_en.el6.rpm wex-zookeeper-12.0.3.4-dae_en.el6.rpm * Fetching /readme.txt to readme.txt /readme.txt 100% 239 3.1KB/s 00:00 Fetching /wex-aac-12.0.3.4-dae.tar to wex-aac-12.0.3.4-dae.tar /wex-aac-12.0.3.4-dae.tar 100% 1284MB 7.4MB/s 02:53 Fetching /wex-appbuilder-12.0.3.4-dae_en.el6.rpm to wex-appbuilder12.0.3.4-dae_en.el6.rpm /wex-appbuilder-12.0.3.4-dae_en.el6.rpm 100% 383MB 7.6MB/s 00:50 Fetching /wex-bigindex-12.0.3.4-dae_en.el6.rpm to wex-bigindex12.0.3.4-dae_en.el6.rpm /wex-bigindex-12.0.3.4-dae_en.el6.rpm 100% 55MB 7.8MB/s 00:07 Fetching /wex-engine-12.0.3.4-dae_en.el6.rpm to wex-engine-12.0.3.4dae_en.el6.rpm

/wex-engine-12.0.3.4-dae_en.el6.rpm 28% 367MB 7.6MB/s 02:01 E/we/wex-engine-12.0.3.4-dae_en.el6.rpm 100% 1288MB 7.3MB/s 02:56 Fetching /wex-resultsmodule-12.0.3.4-dae_en.el6.rpm to wexresultsmodule-12.0.3.4-dae_en.el6.rpm /wex-resultsmodule-12.0.3.4-dae_en.el6.rpm 100% 333MB 7.2MB/s 00:46 Fetching /wex-zookeeper-12.0.3.4-dae_en.el6.rpm to wex-zookeeper12.0.3.4-dae_en.el6.rpm /wex-zookeeper-12.0.3.4-dae_en.el6.rpm 100% 124MB 6.9MB/s 00:17 (base) [root@ECMUKDEMO6 WatsonFix]#

Figure 2.25: The downloaded files are now ready for installation From the readme.txt file:

For information about what is new or has changed in this release, see the Release Note section of the Knowledge Centre for this release, which is available at the following URL:

http://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0

2.3.5: Version end-of-life and roadmaps

The excel spreadsheet, can be downloaded from the following URL https://www.ibm.com/support/pages/software-lifecycle-product-list

This spreadsheet can be searched in Excel for the string product This is in a row of the IBM excel spreadsheet, named as Watson Explorer Deep Analytics Edition and GA Date was February, 2018. There are no dates set for EOS currently.

2.4: IBM StoredIQ For Legal 2.0.3.7

IBM StoredIQ for Legal VM 2.0.3.7 server is supplied as an installation, which is a ready-built virtual machine .ova VMware file, based on CentOS 7.

2.4.1: Compatibility matrix URLs

The reference link is as follows: https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_upgrade.html

IBM StoredIQ products - system requirements https://www.ibm.com/support/pages/ibm-storediq-products-systemrequirements

Select the preceding URL, then click for a one-time link:

Figure 2.26: The highlighted link leads to the compatibility matrix report

Starting with fix pack 12.0.3.10, StoredIQ for Legal is also delivered as a set of containers in addition to the OVA image.

DB2 Workgroup Server Edition 10.5.0.11

IBM Content Navigator 3.0.0

IBM Security Directory Server 6.4.0.20

WebSphere Application Server - Base 8.5.5.17

Figure 2.27: The requirements for the OVA VM version are viewed by selecting the Hardware Tab, then clicking on the Virtual Appliance option

2.4.2: Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics Please see the points as follows:

Fix pack 2.0.3.10 requires the Chrome 79 version of the browser.

Fix pack 2.0.3.10 requires the Browser Firefox ESR 72 version. Starting with Fix pack 2.0.3.4, the custodian portal can also be accessed from Apple iPad tablets (iPad mini 4 with IOS 9.3.5 and iPad Pro with IOS 11).

For the limitations, check the Knowledge Centre product for the required FixPack.

IBM StoredIQ products - system requirements

https://www.ibm.com/support/pages/ibm-storediq-products-systemrequirements (Also see above for the link to follow in figure

2.4.3: Supporting database, web applications, and operating system version limitations for the products The StoredIQ for IBM has the following links describing the supporting system requirements, although as this is a pre-built Vmware system, these are mainly shown with the list of preinstalled supporting software.

IBM StoredIQ products - system requirements main link. https://www.ibm.com/support/pages/ibm-storediq-products-systemrequirements

(Also see above for the link to follow in figure

The following supporting IBM system products are already installed as part of the delivered .ova file:

DB2 Workgroup Server Edition

IBM Content Navigator

IBM Security Directory Server 6.4.0.20 WebSphere Application Server 8.5.5.17

2.4.4: Component interactions with system architecture diagrams and performance issues IBM StoredIQ introduction and planning considerations

Reference link is as follows:

https://www.redbooks.ibm.com/redpapers/pdfs/redp5315.pdf See Figure 4 Sample architecture in the preceding Redbook link for an overview of the architecture components.

2.4.5: Upgrade paths and supported versions for upgrade

StoredIQ® for Legal provides a script for upgrading the Open Virtual Appliance to the latest version.

If you are upgrading to StoredIQ for Legal Version 2.0.3.10 from an earlier 2.0.3.x version, see the following link:

https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_upgrade_info.html

2.4.6: End-of-life and roadmaps

Reference link is as follows: https://www.ibm.com/software/passportadvantage/endofsupport_2H_ 2019.html

Product name VRM eGA End of Support date StoredIQ eDiscovery 7.5.x 11/8/2013 9/30/2019

Conclusion

This chapter covered the procedures to follow using IBM URLs, to generate tables listing the cross-compatibility between the components of a system, which IBM has tested and will support in a production environment. Descriptions were given to enable you to discover and interpret the information that IBM provides using its Product and Fix Pack online pdf generation tool. The steps required to search and download supporting Excel spreadsheets, and also their usage for EOL support searches for IBM Watson Explorer and IBM StoredIQ for Legal 2.0.3.7 (VM) were described.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software.

Generate a Cross tabulation of supported software and hardware components using the IBM compatibility matrix support tools.

Select the latest base product version supported for your target environment and download it from IBM Software Catalog.

Search and download the latest Fix Pack (this is usually cumulative) to apply fixes to the base product.

The Windows 2016 Server is not a certified operating system for Docker CE.

You can download IBM Cloud Private Foundation plus IBM oneWEX V12.0.3 as a supported and Licensed package.

Watson Explorer Deep analytics Edition is actually synonymous with the title IBM Watson Explorer For Docker Container IBM oneWEX 12.0.3, production use is only up to the Red Hat Enterprise Linux RHEL Server 7 version (as of August 2020)

Multiple Choice Questions

How is IBM Watson Explorer oneWEX 12.0.3 supported on Red Hat OpenShift?

IBM oneWEX12.0.3 is only supported on Red Hat OpenShift Version 3.1

IBM oneWEX 12.0.3 is only supported on Red Hat OpenShift Version 4.5

IBM oneWEX 12.0.3 is not yet supported on Red Hat OpenShift (up to Version 4.5)

IBM oneWEX 12.0.3 is supported on all versions of Red Hat OpenShift

Who supports the Installation of IBM oneWEX 12.0.3 on Red Hat OpenShift?

IBM supports the installation of oneWEX 12.0.3 on Red Hat OpenShift Red Hat supports the installation of oneWEX 12.0.3 on Red Hat OpenShift

Both IBM and Red Hat support the installation of IBM oneWEX 12.0.3 on OpenShift

oneWEX 12.0.3 installation is not supported on IBM OpenShift

IBM’s general guidance on EOL means:

IBM’s general guidance on extension of life

IBM’s general guidance on export of languages

IBM’s general guidance on end of life IBM’s general guidance on early offer licenses

The Docker CE used for loading the IBM Watson oneWEX 12.0.3 package Container is supported for:

Development and Production systems Only Production systems

Only Development systems

Neither Development or Production Systems

Multiple Choice Answers

c. IBM oneWEX 12.0.3 is not yet supported on OpenShift (up to version 4.5)

d. IBM oneWEX 12.0.3 installation is not supported on OpenShift

c. IBM’s general guidance on end of life c. Only development systems

Questions

Given the URLs for access to IBM Release Notes, the IBM compatibility matrix, IBM Fix Packs download page, and IBM Software Catalog downloads page, in what order would you review and use these pages to enable you to install the correct and latest IBM Watson oneWEX system, and why?

How would you provide a subset of IBM requirements for IBM Watson Explorer 12.0.3.0 in a printed PDF document? What procedures would you use to check for a potential solution to resolve an issue raised by a user of your IBM Watson Explorer installation to correct a software problem they raised?

If you wanted to support the ability to generate thumbnails for certain types of documents in the search results using IBM Watson Foundational Components 12.0.3 on a Linux server, what libraries would you have to install?

Key terms

End of Life Uniform Resource Locator

General Access

Community Edition Open Virtual Appliance file type

Virtual Machine

Fix Pack

Annotation Administration Console

End of Support

CHAPTER 3 IBM Download Procedures

Introduction

This chapter describes the step-by-step download instructions covering the list of products in Chapter 1, Getting Started with IBM Resources for Analytics for the base product and Fix Packs, and also covers the downloadable supporting systems for the following:

IBM Watson Explorer Foundational Components 12.x IBM Watson Explorer oneWEX 12.x Docker Container

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

IBM StoredIQ can be downloaded as a VMware compatible .ova file. This includes its own CentOS 7 operating system for direct loading to VMware, including VMware Workstation Pro 15.

For the full step by step procedure screenshots, for Vmware 15.1 installation see the ResearchGate publication, https://doi.org/10.13140/RG.2.2.27358.18246 IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux Pages to 19

Structure

In this chapter, we will discuss the following topics: IBM Watson Explorer Foundational Components 12.x

Downloading the IBM e-Assembly components for Linux

Product searching procedures Product code lists - identifying the correct downloads

IBM Download Director installation and use

License restrictions

Red Hat and Centos Linux download and use of subscription manager

Use of FTP/SFTP, VMware mapped folders and for file IBM Watson Explorer oneWEX 12.x Docker Container

Downloading the IBM e-Assembly components for Linux

Product searching procedures

Product code lists - identifying the correct downloads

IBM Download Director installation and use

License restrictions

Red Hat and CentOS Linux download

Use of FTP/SFTP, VMware mapped folders and for file

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation Downloading the IBM e-Assembly components for Linux

Product searching procedures

Product code lists - identifying the correct downloads IBM Download Director installation and use

License restrictions Red Hat and CentOS Linux download

Use of FTP/SFTP, VMware mapped folders and for file

Questions and Exercises

Objectives

After studying this unit, you should be able to: Identify suitable versions of each of the system components, which will be required to support the IBM Watson and StoredIQ software versions targeted for installation, and be able to use the tools and procedures to download them and copy them to the target host system. Understand the prerequisite requirements for the target software components to be installed, and know where to look for them and how to install them.

3.1: IBM Watson Explorer Foundational Components 12.x

The Watson Explorer Foundational Components 12.0.3.0 are broken down into the following installed components. See the following link:

https://www.ibm.com/support/pages/watson-explorer-version-12034foundational-components Application Builder

Used for developing information applications filtering data based on a user’s role or area of interest within the organization.

Example of the Fix Pack file available:

Watson Explorer Engine

A web-based development and deployment environment for searching and displaying an organizations information application.

Example of the Fix Pack file available: Annotation Administration Console

A web-based administration tool for configuring custom and domain specific text analytics, allowing additional Unstructured Information Management Architecture pipelines for Watson Explorer filters and views of the extracted data content for analysis applications.

Example of the Fix Pack file available: wex-aac-12.0.3.4-dae.tar.

BigIndex Java API

Deprecated module – This has been deprecated as of IBM Watson Explorer Version 12.0.0 (but still included in the Fix Pack at 12.0.3.4).

IBM Watson Explorer BigIndex is a component of Watson Explorer that provides a Java API.

This API is used for creating, configuring, and deploying information navigation applications. The BigIndex API includes functions that simplify large scale data application administration tasks, for tasks such as load balancing, mirroring, and replication. Example of the Fix Pack file available:

Draft PDF: Developing Applications Using the BigIndex API (Draft, December 9, 2014) PDF file download URL is as follows:

https://www.ibm.com/support/pages/sites/default/files/inlinefiles/$FILE/Watson%20Explorer%20BigIndex%20API%20draft%20doc umentation.pdf

Results Module Deprecated module, currently available for local administrators, to extend information mining applications using business-specific highlighting of selected query results, and allowing incorporation of domain-specific knowledge such as taxonomies. Example of the Fix Pack file available: ZooKeeper

A distributed coordination service and associated data repository for storing configuration information about distributed applications.

Example of the Fix Pack file available:

3.1.1: Downloading the IBM e-Assembly components for Linux

The files to download the base components are as follows:

follows: follows: follows: follows: follows: follows: follows: follows: follows:

Table 3.1: The available Watson Explorer foundational component modules

See the following link:

https://www.ibm.com/support/pages/node/6244508

3.1.2: Product searching procedures

Chapter 1, Getting Started with IBM Resources for of this book, section 1.4, IBM covers the step-by-step download of the IBM Watson Explorer Foundational components to a Windows 10 client machine.

The components can then be copied to a Linux Red Hat 8.x or CentOS 8.x server using FTP (see the last sub-section of this section of the chapter, Use of FTP/SFTP, VMware mapped folders and SSH/SCP for

3.1.3: Product code lists - identifying the correct downloads

The following URL is the main page for the following IBM Watson Software products:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12.0. 0.html

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com .ibm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12. 0.0.html https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com .ibm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12. 0.0.html https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com .ibm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12. 0.0.html https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com .ibm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12. 0.0.html https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com .ibm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12. 0.0.html https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com .ibm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12.

0.0.html

Table 3.2: The IBM Watson Software Products

Figure 3.1: The list of the packages downloaded for installation

In the preceding Download Director list, the Linux Watson Explorer Foundational Components, 12.0.3 are rpm Red Hat Package Manager based installation files compressed in the IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar file. The product codes to be searched in the IBM Software Access Catalog Downloads site are held at two levels. IBM has the concept of an eAssembly, which can be used with a single license. This usually contains multiple separate downloads, and these are split based on the installation operating system that they are targeted for. So, usually split for IBM AIX, IBM Power Linux, Linux (sometimes spilt into 32 bit or 64-bit systems) and for the Windows Server. Downloads The IBM Software Catalog Download page for IBM Watson is shown as follows. This eAssembly has thirteen separate downloadable software installation packages for deployment.

Figure 3.2: The main IBM Watson Explorer eAssembly product code (CJ5DNML)

Figure 3.3: Within the eAssembly, the IBM Watson Foundational Components can be selected for download using Download Director

Figure 3.4: Product code CC1G6ML for IBM Watson Explorer Deep Analytics Edition The table information below is displayed using View

Table 3.3: Download file details for IBM Watson Explorer Deep Analytics Related Estimated download duration

duration duration duration duration duration duration duration duration

3.1.4: IBM Download Director installation and use

The general initial installation of IBM Download Director and its use and the advantages of using it are covered in Chapter 1, Getting Started with IBM Resources for Analytics , section IBM subsection Downloads on pages 13 to

The download procedure is covered in the publication reference: https://doi.org/10.13140/RG.2.2.12248.44803

IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, pages

See the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.welcome.doc/doc/explorer_foundation. html

The preceding link displays the main browser page for the documentation on how to install, maintain, and use the components and features of IBM Watson Explorer Foundational Components, such as Watson Explorer Engine and Watson Explorer Application There is also documentation on how to install,

maintain, and use the components and features of IBM Watson Explorer Analytical Components, such as Watson Explorer Content Analytics and Content Analytics Studio.

The files required for IBM Watson Foundational components are:

IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar for Linux

IBM_WE_DEEP_ANALYTICS_EDITION_FOU.zip for Windows systems

You can install Watson Explorer Foundational Components Version 12.0.3.4 directly without installing Watson Explorer Foundational Components Version 12.0.3 To perform a fresh installation of Foundational Components Version 12.0.3.4, follow the steps, as described in Chapter 12, IBM Watson Explorer Foundational Components See the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.install.doc/c_install_wrapper.html

3.1.5: Red Hat and CentOS Linux download and use of subscription manager Red Hat RHEL 8.0 Linux download, installation, and subscription manager is covered fully in the publication:

https://doi.org/10.13140/RG.2.2.14590.95049

Content Navigator 3.0.6 Installation on RHEL 8.0_V1.docx, pages 1532. In this chapter, I have covered the CentOS 8.2 iso image download that I use for the VMWare MasterBoot server, which I used to install IBM Watson.

The publication described in pages

https://doi.org/10.13140/RG.2.2.20256.94729

IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux 8.0 describe the full CentOS 8.0 download and installation procedure. Note that for versioning, 2004 does not refer to the year of release, but an on-going independent release number, maintained by CentOS, in the form YYNN (last years, 2019 release of CentOS 8.0 was release number 1905).

The CentOS 8.2 Linux distribution is a stable operating system platform derived from the sources of Red Hat Enterprise Linux

The release notes for CentOS can be found at the following link:

https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2004

CentOS mainly changes packages to remove Red Hat’s branding and artwork.

At least 2 GB RAM is required to install and use CentOS-8.2 (2004). At least 4 GB RAM is recommended. I am using 32 GB RAM as I am following the IBM recommended sizes for the IBM Cloud Private MasterBoot server

See the following link: https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2004#Introdu ction

Figure 3.5: The browser download shows the estimated download time, 21 minutes for 7.7 GB on my broadband connection Before copying the image to your preferred installation media, you should check the sha256sum of the downloaded installation images. Please check the following link:

https://wiki.centos.org/TipsAndTricks/sha256sum On Use the sha256sum command:

Go to the directory where you downloaded the ISO file in a Command Prompt and type:

sha256sum .iso This returns the following:

CentOS-8.2.2004-x86_64-dvd1.iso: 8231321600 bytes SHA256 (CentOS-8.2.2004-x86_64-dvd1.iso) = c87a2d81d67bbaeaf646aea5bedd70990078ec252fc52f5a7d65ff609871e25 5 I have checked this as (8,231,321,600 bytes in size as expected)

Install CENTOS Linux 8.2 on VMware

See the following link (general networking information): https://linuxconfig.org/redhat

See the following link for installation steps:

https://linuxconfig.org/how-to-install-red-hat-linux-8-on-vmwareworkstation

CENTOS 8.2 is an open-source binary code equivalent of the Red Hat Enterprise Linux 8.2 Release. You have to create a bare metal system on VMware, and then set the boot option to boot from CD-ROM as described in the following section. It does not work if you let VMware try to use its own installer, so don’t use the Installer disc image file option on this screen! (VMware detects this as a pre-CentOS 5 O/S.)

Select Linux as the Guest Operating System type.

Name the virtual machine MasterBoot CentOS 82 and click Browse to identify the target drive and root folder for the VMware system (I have used G:\VMSC82 for the root folder). You need to have 500 GB free (or not expect to exceed the virtual disk actual size, see step 10, below).

Select the number of processors as 8 (you need to have a host VMware server with more than this number of core threads).

The number of virtual processors you select must be less than the number of CPU cores on your system!

Select the memory required for the CentOS 8.2 VM system.

The memory selected for the VMware system should be at least 9 GB less than the host VMware server’s memory. You can use the slide bar or type an exact allocation of memory in the highlighted text box. I have used the 32 GB of memory recommended for a MasterBoot server for IBM Cloud Private.

Select the network address card type for the virtual machines network. Additional cards and changes to the network type can be made later. The default NAT option is selected for the initial installation. Additional network cards can be added as required later. Select the recommended LSI Logic I/O controller option and click The default LSI Logic I/O controller should be selected for this system. Select the Create a new virtual disk and click

You can create a new virtual disk system or use an existing disk, but use the default for this system. Select the disk capacity required and the type of VMware disk files. The Disk capacity is selected as 500 GB as recommended by IBM for the IBM Cloud Private MasterBoot server of a small cluster. I have selected to split the virtual disk since this only uses the portion of the 500 GB that is occupied by files in the system, so the actual space used on the host server is usually a great deal less than 500 GB.

Use the default name provided for the vmdk disk files and click The summary of the VMware creation properties is displayed for review. Click Finish to begin the initial boot and system build process.

The VMware Workstation wizard displays the options you have selected before starting the build. You can check the options you selected and click on the button at this point, if you want to change anything. The VM Settings are selected, as shown earlier, to enable configuration so that we can use the CentOS 8.2 .iso file as the source for the boot CD-ROM.

We need to change the VMware default settings, so that the default CD-ROM is pointing at the installation CentOS 8.2 iso file. Browse to the location of the Centos-8.2.2004-x86_64-dvd1.iso file (click on the Use ISO image file radio button option)

The downloaded Centos-8.2.2004-x86_64-dvd1.iso file is a DVD image built to allow booting and installation for a full CentOS 8.2 Linux Operating System.

Figure 3.6: Select the option to change the boot order after the ‘Bare Metal’ build has completed using the VM-> Power -> Power On to Firmware

The preceding options must be selected to allow the VMware BIOS setup to be modified, so that the system will attempt a boot from the CentOS Linux DVD iso file (now selected as the CD drive).

The boot procedure for the new system is described fully in the following link: https://doi.org/10.13140/RG.2.2.20256.94729 CENTOS 8-0 Installation For IBM Cloud Private and IBM FileNet P8 CPIT Installation V2.docx Appendix J – Creation of the Base MasterBoot CENTOS 8 server on VMWare 15.5. For the setup of the DNS server with a static IP address:

https://doi.org/10.13140/RG.2.2.20256.94729

IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux 8.0, Pages 43-60. See also, Appendix B, Add a second NAT Network Card using VMware.

https://doi.org/10.13140/RG.2.2.21708.16001

Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator

3.1.6: Use of FTP/SFTP, VMware mapped folders, and ssh/scp for file Install ftp Using FTP server –procedure for installation of FTP:

https://doi.org/10.13140/RG.2.2.20256.94729

IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux 8.0, Pages 103-106.

FTP transfer

First load a windows command window, run as administrator.

In the windows command window:

C:\ASB_SOFTWARE_DEVELOPMENT ftp> open 192.168.50.138 Connected to 192.168.50.138. 220 (vsFTPd 3.0.3) 200 Always in UTF8 mode. ftp> user Username wasadm 331 Please specify the password. Password:

230 Login successful. ftp> mput *.tar mput IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar? y 200 PORT command successful. Consider using PASV. 150 Ok to send data. 226 Transfer complete.

ftp: 3554304000 bytes sent in 39.60Seconds 89757.42Kbytes/sec. ftp>

On the Linux system Copy the Watson Analytics, Foundation, and oneWEX Installation downloads. Copy from FTP transfer to /home/wasadm (using the VMware MasterBoot server): [root@localhost /]# cd /opt [root@localhost opt]# ls [root@localhost opt]# df -k /opt Filesystem          1K-blocks    Used Available Use% Mounted on /dev/mapper/cl-root  52403200 4645068  47758132   9% / [root@localhost opt]# mkdir installs [root@localhost opt]# cd installs/ [root@localhost installs]# pwd /opt/installs [root@localhost installs]# ls /home/wasadm IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar

[root@localhost installs]# cp /home/wasadm/IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar . [root@localhost installs]# tar -xvf IBM_WE_DEEP_ANALYTICS_EDITION_FOU.tar wex-appbuilder-12.0.3.0-dae_en.el6.rpm wex-bigindex-12.0.3.0-dae_en.el6.rpm wex-engine-12.0.3.0-dae_en.el6.rpm

wex-resultsmodule-12.0.3.0-dae_en.el6.rpm wex-zookeeper-12.0.3.0-dae_en.el6.rpm wex-aac-12.0.3.0-dae.tar [root@localhost installs]# After download, FTP or VMware mapped folder copy and tar -zxvf extraction, the .rpm packages required can be searched and listed ready for installation using the Linux find command:

[root@localhost installs]# cd /opt [root@localhost opt]# find . -name *.rpm ./installs/wex-appbuilder-12.0.3.0-dae_en.el6.rpm ./installs/wex-bigindex-12.0.3.0-dae_en.el6.rpm ./installs/wex-engine-12.0.3.0-dae_en.el6.rpm ./installs/wex-resultsmodule-12.0.3.0-dae_en.el6.rpm ./installs/wex-zookeeper-12.0.3.0-dae_en.el6.rpm [root@localhost opt]#

Figure 3.7: Results of the search listing the. rpm package files for installation

The micro-test utility (called micro-test.exe on a Microsoft Windows systems) is installed as part of the Watson Explorer Engine installation. It can be found in the bin sub-directory of the installation directory. The micro-test utility collects information about the performance of the target installation server. It also checks for the impact of anti-virus software, so that you can configure the anti-virus to exclude the IBM Watson folders and processes for the installed Watson Explorer components. IBM strongly recommends that you execute the micro-test utility on each host, where you have installed any Watson Explorer module BEFORE using the system! You need to archive the results of the tests for review. It is also recommended that you execute the Test All batch test, in order to collect data about all of the aspects of system performance and configuration that the micro-test utility can collect.

3.2: IBM Watson Explorer oneWEX 12.x Docker Container

The base Docker Container component for download is described as follows:

https://doi.org/10.13140/RG.2.2.12248.44803

(IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux 8.0)

3.2.1: Downloading the IBM eAssembly components for Linux

The following screen shows the web download page for the IBM Watson explorer Deep Analytics version 12.0.3 installation package:

Figure 3.8: The part number, CJ5DNML, for IBM Watson Explorer Deep Analytics

The download of the components for IBM Watson oneWEX and IBM Watson Explorer Foundational Components is fully covered in the publication:

https://doi.org/10.13140/RG.2.2.12248.44803

The preceding DOI URL allows download of the document, IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, on Pages 4 to 8.

Extraction of IBM Watson Explorer Foundational Components:

https://doi.org/10.13140/RG.2.2.12248.44803

The preceding DOI URL allows download of the document, IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, on Page

Extraction of the IBM Watson Explorer Deep Analytics oneWEX Edition:

https://doi.org/10.13140/RG.2.2.12248.44803 The preceding DOI URL allows download of the document, IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux October 2019, DOI: 10.13140/RG.2.2.12248.44803, Page

3.2.2: Product code lists - identifying the correct downloads

The two required packages for installation are contained in the following tar files:

IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar

IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar

3.2.3: Product searching procedures

Chapter 1, Getting Started with IBM Resources for section IBM Watson, pages 13 to covers the step-by-step download of the IBM Watson Explorer oneWEX docker container components to a Windows 10 client machine.

The components can then be copied to a Linux Red Hat 8.x or CentOS 8.x server using FTP (see the last sub-section of this section of the chapter, Use of FTP/SFTP, VMware mapped folders and ssh/scp for

3.2.4: IBM Download Director installation and use

The general initial installation of IBM Download Director and its use, and the advantages of using it are covered in Chapter 1, Getting Started with IBM Resources for section IBM sub-section Downloads on pages 13 to

3.2.5: Red Hat and CentOS Linux download

In this chapter, I have covered the CentOS 8.2 iso image download that I use for the VMWare MasterBoot server, which I used to install IBM Watson.

CentOS 8.2 conforms fully with Red Hat’s redistribution policy and aims to have full functional compatibility with the upstream product. The full step-by-step installation of the CentOS 8.2 O/S on the VMware Workstation Pro 15.5.6 based system is covered in Section earlier in this chapter.

3.2.6: Use of FTP/SFTP, VMware mapped folders and ssh/scp for file The following command installs the Linux FTP server: root@localhost ~]# dnf install vsftpd

The full step-by-step procedure for installing and using FTP on the Linux server is covered in Section earlier in this chapter. VMWare workstation upload

/mnt/hgfs is the VMware Workstation Pro 15.5.6 main mount-point set by VMware for any shared folders created

I have a shared folder called DB2_Graph (used for another IBM software component upload), see Chapter 21, IBM Workflow Centre 8.6 for IBM BAW 18.0 of the BPB Publication, Installation and Configuration of IBM Db2 I have copied the IBM Watson tar files to this shared folder for use, as follows:

(base) [root@ECMUKDEMO6 /opt/Watson12.0.3.0 (base) [root@ECMUKDEMO6 (base) [root@ECMUKDEMO6 (base) [root@ECMUKDEMO6 (base) [root@ECMUKDEMO6

Watson12.0.3.0]# pwd Watson12.0.3.0]# cd .. opt]# mkdir watson opt]# cd watson watson]# pwd

/opt/Watson

(base) [root@ECMUKDEMO6 watson]# ls /mnt/hgfs/ DB2_Graph (base) [root@ECMUKDEMO6 watson]# cp /mnt/hgfs/DB2_Graph/IBM_WE_DEEP_ANALYTICS_EDITION_ANA.ta r . (base) [root@ECMUKDEMO6 watson]# pwd /opt/watson (base) [root@ECMUKDEMO6 watson]# ls

IBM_WE_DEEP_ANALYTICS_EDITION_ANA.tar (base) [root@ECMUKDEMO6 watson]# tar -xvf IBM_WE_DEEP_ANALYTICS_EDITION_ANA.tar install.bin responseFiles/ responseFiles/LinuxAdditionalServer.properties responseFiles/LinuxMasterAllInOneServer.properties responseFiles/LinuxMasterDistributedServer.properties responseFiles/LinuxUpdateInstall.properties (base) [root@ECMUKDEMO6 watson]# cd .. (base) [root@ECMUKDEMO6 opt]# mkdir oneWEX (base) [root@ECMUKDEMO6 opt]# cd oneWEX/ (base) [root@ECMUKDEMO6 oneWEX]# pwd /opt/oneWEX (base) [root@ECMUKDEMO6 oneWEX]# cp /mnt/hgfs/DB2_Graph/IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.ta r . Unpack the downloaded oneWEX installation tar file

(base) [root@ECMUKDEMO6 oneWEX]# tar -xvf IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar one-wex-installer-linux.tar (base) [root@ECMUKDEMO6 oneWEX]# ls IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar  one-wex-installerlinux.tar Unpack the extracted one-wex-installer-linux.tar for installation (base) [root@ECMUKDEMO6 oneWEX]# tar -xvf one-wex-installerlinux.tar install.bin onewex.dat wksml.dat

(base) [root@ECMUKDEMO6 oneWEX]# ls IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar  install.bin  onewex.d at  one-wex-installer-linux.tar  wksml.dat (base) [root@ECMUKDEMO6 oneWEX]# ls -lsa total 14152720 0 drwxr-xr-x.  2 root  root  140 Aug 18 04:56 . 4 drwxr-xr-x.  22 root wasadm  4096 Aug 18 04:50 .. 4717580 -rwxr-xr-x.  1 root  root  4830801920 Aug 18 04:54 IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar 247124 -rwxr-xr-x. 1 root  root 253051900 Jun 22  2019 install.bin 3656756 -rw-r--r--. 1 root  root 3744516624 Jun 22  2019 onewex.dat 4717572 -rw-rw-r--. 1 idsldap idsldap 4830791680 Jun 23  2019 onewex-installer-linux.tar 813684 -rw-r--r--. 1 root  root  833212256 Jun 22  2019 wksml.dat

3.3: IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

For the OVF file format converted to a VMware runtime format, you can import both .ovf and .ova files. Using VMware Workstation Pro VMware, OVF is a platform-independent, efficient, extensible, and open packaging and distribution format for virtual machines. For example, you can import the OVF virtual machine files using the Vmware Workstation Pro 15.1 utility.

3.3.1: Downloading the IBM eAssembly components for Linux

From IBM Software Catalog, the search of the Product code CC15JEN shows the following:

Figure 3.9: The download file of the VM image for IBM StoredIQ for legal is over 6GB!

3.3.2: Product code lists - identifying the correct downloads

Product details File IBM_STOREDIQ_FOR_LEGAL_V2.0.3.7_V.OVA

VM

English Related Estimated download duration

File 6,396,541,952 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

3.3.3: Product searching procedures

Chapter 1, Getting Started with IBM Resources for section IBM Stored IQ For Legal 2.0.3.7, pages 27 to covers the step by step download of the IBM StoredIQ for Legal VM 2.0.3.7 virtual machine to a Windows 10 client machine.

The extracted OVF file is browsed to by the VMware Workstation Pro 15.5.6 host virtual machine system.

3.3.4: IBM Download Director installation and use license restrictions After download using Download Director, the first step is to recreate the package from the downloaded .ova file. For this, use 7zip utility (or a similar utility), and extract the files in the ova file/package into a new folder. For this use the 7zip utility (or a similar utility) and extract the files in the ova file/package into a new folder. After, the .ova file package is extracted into a new folder to its constituent files, vmdk files.

3.3.5: Red Hat Linux download

In this chapter, I have covered the CentOS 8.2 iso image download that I use for the VMWare MasterBoot server, which I used to install IBM Watson.

CentOS 8.2 conforms fully with Red Hat’s redistribution policy, and aims to have full functional compatibility with the upstream product. The full step-by-step installation of the CentOS 8.2 O/S on the VMware Workstation Pro 15.5.6 based system is covered in Section earlier in this chapter.

3.3.6: Use of FTP/SFTP, VMware mapped folders, and ssh/scp for file There is no requirement to use the FTP or a mapped folder for IBM StoredIQ for Legal VM 2.0.3.7, as it is a complete contained virtual machine image already.

Conclusion

This chapter covered the procedures to follow, and the search parameters required for displaying the latest products for download for:

IBM Watson Explorer oneWEX 12.x Docker Container

IBM Watson Explorer Foundational Components 12.x IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

The identification of product codes, speed of downloads and the interpretation of the downloaded file version information for the products required are described.

Points to Remember

Select the latest Base Product Version supported for your target environment and download it from IBM Software Catalog.

Search and download the latest Product version using the Product Code required for your server platform

It is always recommended to search for the latest compatible version for your server and then any intermediate fixes and Fix Packs, to ensure the completed installation is optimally installed.

Note that there are other later versions of IBM StoredIQ for Legal (VM) (2.0.3.10 and 2.0.3.11) which have to be installed specifically as base versions and cannot be created by upgrading version 2.0.3.7

Multiple Choice Questions

Which two components of the IBM Watson Foundation 12.0 version and above components are deprecated?

Results Module and Zookeeper.

Application Builder and Annotation Administration Console Application Builder and Zookeeper

Results Module and BigIndex Java API

Which one of the following copy mechanisms provides a secure transfer of files?

ftp

sftp

cp mv

IBM Download Director allows:

Just one IBM product to be downloaded

Only the latest IBM product to be downloaded

Only IBM products not ticked to be downloaded

All IBM products selected by a tick box to be downloaded

OVA file type means: Object Virtual Architecture file type

Open Virtual Appliance file type Open Version Archive file type

Open Version Appliance file type

Multiple Choice Answers

d. Results Module and BigIndex Java API b. sftp

d. All IBM products selected by a tick box to be downloaded

b. Open Virtual Appliance file type

Questions

If IBM Download Director could not be used, what alternative download mechanisms could you select for use, using the IBM product download page?

What network connection type would you select for the fastest download? What advantage does IBM Download Director provide that the https or sftp download options don’t provide?

In the Download Director status window after download is complete, what would you do to quickly view the individual files and how would you show the full folder path of the listed files?

Key terms

FTP: File Transfer Protocol. SFTP: Secure File Transfer Protocol

VM: Virtual Machine

OVA: Open Virtual Appliance file type JRE: Java Runtime Environment for a java system

AAC: Annotation Administration Console

BIOS: Basic Input/ Output System

CHAPTER 4 On-Premise Server Configurations and Prerequisites

Introduction

This chapter covers three separate platforms for the installation of the IBM products covered by the book.

First, the Red Hat 8.0 .iso disk image installation procedure on VMware Workstation Pro 15.5.x, for the disk resource and sizing requirements, network card(s) and mapping, and pip and conda installations, and Firewall port set-up for the IBM Software product prerequisites of the products covered in this Chapter. Secondly, it also covers the Windows 10.0 Server and client based installations of IBM oneWEX Docker Containers and IBM Watson Foundational Components 12.0.3.x software packages.

Thirdly, it defines the Red Hat Linux Red Hat Enterprise Linux CoreOS server cluster requirements for the OpenShift 4 onpremise cloud installation support for Kubernetes controlled containers. In support of containers, the installation of the Docker Container system, which is used in the first two sections, is described with the use and function of the main docker commands.

Every control plane server in an OpenShift Container Platform 4 cluster must use RHCOS, which includes a critical first-boot provisioning tool called Ignition. This tool enables the cluster to

configure the servers. Operating system updates are delivered as an atomic OSTree repository that is embedded in a container image, which is rolled out across the cluster by an operator. This chapter covers the prerequisites provided by Red Hat OpenShift for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics and in detail usage of the following products:

IBM Watson Explorer oneWEX 12.x Docker Container

IBM Watson Explorer Foundational Components 12.x IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

It also covers the installation of an IBM Cloud Private server cluster on the Linux CentOS 8.0 operating system, which is a 100% binary compatible, open source version of the Red Hat RHEL 8.0 server operating system.

Some sections of this chapter use procedures provided from the Red Hat URL:

Deploying OpenShift 4.x on non-tested platforms using the bare metal install method: https://access.redhat.com/articles/4207611

(For the full access to the preceding URL, you need a Red Hat account.) The preceding URLs used require the following license notice:

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license (“CC-BY-SA”). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. So, I have provided this in accordance with the CC-BY-SA license.

Figure 4.1: Legal Notice from the reference used For further There is a downloadable Redbook, which covers the open source version of Red Hat OpenShift, OpenShift OKD version 3.1.1 on LinuxOne, dated 2019: https://www.redbooks.ibm.com/redpapers/pdfs/redp5561.pdf

Structure

In this chapter, we will discuss the following topics: Docker account creation

Installing Docker

Installing Docker 18.09.2 on RHEL 8.0 Installing Docker Desktop 2.3.0.4 on Windows 10 Home Edition

Install the Linux kernel update package

Create an example Docker Container

Edit the Compose file to add a bind mount

Docker pull command

Docker exec command Docker ps command

Docker run command

Experimenting with some other commands

Red Hat and Centos 8.0

IBM Watson Explorer oneWEX 12.x Docker Container

Server(s) required for the installations

Red Hat Subscription Manager configurations Memory and disk storage requirements and CPU Cores required

Network card set-up and DNS configuration GUI library installation requirements

Folder structures and user security Shared folder access and Docker set up requirements IBM Cloud Private Cluster set up and requirements

IBM Watson Explorer Foundational Components 12.x Server(s) required for the installations

Red Hat Subscription Manager configurations

System requirements, CPU Cores, DNS, and library installation requirements Red Hat OpenShift server cluster requirements

IBM StoredIQ for Legal VM 2.0.3.7 Server installation Server(s) required for the installations Red Hat Subscription Manager configurations

Memory and disk storage requirements and CPU Cores required Network card set-up and DNS configuration

GUI library installation requirements Folder structures and User security

Compatibility Matrix URLs Installation and Configuration of IBM Watson Explorer Foundational Components 12.0.3.0 on Windows 10 Home Edition Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics

Server(s) required for the Installations Memory and disk storage requirements and CPU Cores required Folder structures and user security Firewall – Windows Defender configuration

Supporting files and PATH environment set-up Windows hosts file configuration for server network access Stopping running Windows services for install upgrades

Installation and configuration of IBM Watson Foundation Components 12.0.3.0 on Windows 10 Home Edition

Installing the other components Procedure Default login credentials IBM Watson Explorer oneWEX 12.x Docker Container

Compatibility issues and support limitations for the products listed in Chapter 1, Getting Started with IBM Resources for Analytics Server(s) required for the installations Memory and disk storage requirements and CPU Cores required

Folder structures and user security Firewall – Windows Defender configuration Supporting files and PATH environment set-up Windows hosts file configuration for server network access

Stopping running windows services for install upgrades Installation and configuration of IBM Watson Explorer oneWEX 12.x on Windows Docker Container Use of Compatibility Matrix URLs Use of Red Hat Linux upgrades

Red Hat OpenShift 4.x download and installation Configuring the firewall

Internet and telemetry access requirements Server requirements for a cluster

Network connectivity requirements

Objectives

After studying this unit, you should be able to: Follow the steps required to obtain a Docker login account and install the Docker system on Linux.

Follow the steps required to install the Docker system on Windows 10, Home edition. Understand how to create a Docker Container for deployment and test in the Docker system.

Be aware of the main Docker commands and how to use them.

Identify the prerequisite libraries required for each of the system components, which will be required to support the IBM Watson and StoredIQ software versions targeted for installation.

Understand the prerequisite disk, memory, and network requirements for the target software components to be installed, and know how to configure them. Search, identify, and download the latest Linux libraries, and configure the security required to maintain a secure and robust system.

Identify the prerequisites for Red Hat OpenShift required for each of the system components, which will be required to support the IBM Watson and StoredIQ software versions targeted for installation.

Understand the prerequisite Red Hat OpenShift disk, memory, and network requirements for the target software components to be installed, and know how to configure them.

Search, identify, and download the latest Linux Red Hat OpenShift versions, and configure the security required to maintain a secure and robust system.

4.1: Docker account creation

Docker is a container management system, which holds a repository of downloadable containers that can be pulled down, run, and managed, using a local server docker system.

The procedure described in the following publication, on pages 8 should be followed to create a Docker ID for logging in: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux

Docker is introducing a container image retention policy for inactive images, which will be enforced starting November 1, 2020.

The container inactive image retention policy will apply to the following plans:

Free plans will have a 6-month inactive image retention limit. Pro and Team plans will have unlimited image retention.

An inactive image is a container image that has not been either pushed or pulled from the Docker Hub image repository in 6 or more months.

4.2: Installing Docker

Docker can be installed on Red Hat Linux 8.0 (using the CentOS 7 repository).

4.2.1: Installing Docker 18.09.2 on RHEL 8.0

This section describes how to install and run the original Docker CE on RHEL 8 by using the official Docker repository for CentOS 7.

Docker version 18.09.2

The procedure described in the following publication, on pages should be followed to install Docker 18.09.2 on RHEL 8.0:

https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0.

4.2.2: Installing Docker Desktop 2.3.0.4 on Windows 10 Home Edition Although Docker installation Community Edition can be installed on Windows 10 Home edition, it requires a Linux shell to run in, and it uses the Microsoft WSL2 sub-system.

See the following link to download, and install the appropriate version of Docker. If you are downloading the Microsoft Windows installer, be sure to select the Docker CE for Windows: https://www.docker.com/community-edition

Sign in to the Docker Hub using the account we set up earlier in Section 4.1 of this chapter, Docker account

Then, check the Windows system specification. Run Speccy tool to get the windows specification:

See the following link:

https://www.ccleaner.com/speccy_idTextAnchor009/download/standar d Get Docker CE Desktop:

https://hub.docker.com/editions/community/docker-ce-desktopwindows

Figure 4.2: The page for downloading the free Windows Docker CE, click Get Stable The Docker Desktop CE for windows is available for free. Click on the Get Stable version:

Figure 4.3: The browser shows the Docker download progress in the bottom left corner This downloads as an install .exe program, as shown in the preceding screenshot.

Figure 4.4: The downloaded Docker Desktop CE installer can be run

Right-mouse click and Run as On launching the installer the first time, you may see an installation failure message, shown as follows in Figure The Docker Desktop installer program checks the current version of Microsoft Windows 10 that is installed, and requires a Windows 10 Home Edition Version 19018 or greater:

Figure 4.5: The Docker Desktop CE installer program should be run as administrator, right-mouse click and select Run as administrator to launch the installer The Docker Desktop installer should be launched with Windows administrator privileges:

Figure 4.6: The error is generated because our Windows system version needs to be greater than 19018

We need to upgrade the Windows 10 Home system to version 19018 or greater.

Figure 4.7: The Windows Update tool is run to Download the latest Windows version We need to upgrade to Windows 10, version 2004, released on May 27, 2020, as code name 20H1 (which is the latest available, as of September, 2020). Click on the Download button from the Windows Settings > Update & Security > Windows Update menu option screen. This version of Windows 10 Home Edition, is available from Microsoft as a free upgrade for existing users of Windows 7 or Windows 8.1. No product key is required, and the digital license says “you’re activated and ready to go”.

Figure 4.8: The Windows update status shows 100% ready for installation of Windows 2004 The status of the installation can be checked from the Windows Update tool. This download is around 7 GB in size.

Figure 4.9: After the download is complete, the windows must be rebooted to allow the Windows 2004 upgrade to be completed

Click the Restart now command button to complete the installation upgrade to Window 10 Home Edition, 2004:

Figure 4.10: The Update history confirms the Windows system has been upgraded to 2004 The Windows system can be seen to be updated now to version

Figure 4.11: We can now install the Docker Desktop CE 2.3.0.4 version on our Windows

Now, we can start the Docker Desktop installer program, Run as

Figure 4.12: The Configuration pane of the Docker installer gives us two options

Click Ok to continue, include the Enable WSL 2 Windows Features checkbox, and Add shortcut to desktop option. The status of the installation is shown in a window, as can be seen in the following screenshot:

Figure 4.13: The Close and restart command button is clicked to reboot the system

After the installation is completed, you have to restart the Windows system to allow the system installation to be registered:

Figure 4.14: The Microsoft WSL 2 kernel is installed by clicking on the link After the restart, we have a Docker Desktop installation notice to link to the following URL; follow the Microsoft instructions, and afterwards press Restart in order to restart the Docker environment again:

https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

Figure 4.15: The Download kernel update package is clicked to download WSL 2 In the browser page from the preceding URL, we must click on Download the Linux kernel update package to finalise the Docker Desktop system installation.

4.2.2.1: Install the Linux kernel update package

To install the Linux kernel update package, follow these steps: The update package downloaded in the previous step has to be run.

The Windows administrator permissions are required so, select Yes to approve this installation. Once the installation is complete, Docker Desktop will be able to use the WSL2 system.

If you repetitively get the message again that Windows subsystem for Linux, WSL2, requires another reboot in order to take effect, then WSL 2 may require an update to its kernel component; visit

It is possible that the kernel reference is missing in the registry key in which case you may see the preceding error.

The following are the possible ways to resolve it: Install the Linux kernel manually by following the instructions at the following link:

https://aka.ms/wsl2kernel

Uninstall the MSI from Add or Remove and install it again. See the following link:

https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

Figure 4.16: Click on the highlighted link to download the latest WSL 2 Linux kernel

Click on the download the latest WSL2 Linux Kernel link:

Figure 4.17: The wsl_update_x64.msi file is downloaded and can be clicked on to install it The wsl_update_x64.msi Windows program installer is downloaded and can be clicked on to start the upgrade:

Figure 4.18: Click next on the WSL2 update install setup Wizard window

The WSL install wizard is displayed as shown in the preceding screenshot, click

Figure 4.19: Click the Finish command button to complete the installation wizard Click Finish after the WSL 2 installation is completed. We now have to restart the Docker environment:

Figure 4.20: The Docker Desktop prompt for WSL 2 Installation Restart is clicked

This does not reboot the Windows system; it just restarts the Docker environment!

Figure 4.21: The first time launch of the Docker Desktop takes us to the start of the tutorial Start the tutorial:

Figure 4.22: The tutorial starts with the command to clone a repository

Click the Next Step button on the tutorial, notice that we can type freely in the command line window on the right-hand section of the split-window:

Figure 4.23: The command can be transferred to run, by pasting into the Terminal window

As shown in the tutorial window, expanded from figure the required statement is shown, which can be copied to the command window.

Figure 4.24: Click the Next Step after running the command

The download from GitHub can be seen in the command window; click Next Step for the next page of the tutorial:

Figure 4.25: The docker build command is shown in the next screen of the tutorial The Next Step option shows an example of the use of the docker build command:

Figure 4.26: The docker build example command

Now we have to just click on the window to paste the commands required. Change directory to the getting-started sub-folder:

cd getting-started and then use:

docker build -t docker101tutorial

After the Docker Build is completed, click Next Step to show the results:

Figure 4.27: The next screen shows the docker run container example The next tutorial step shows you how to run the Docker system command line to run a container after building it. So, we can run the following commands:

docker run -d -p 80:80 \ --name docker-tutorial docker101tutorial

Figure 4.28: The docker run command for the tutorial container example

The full command line can just be clicked in the box, as shown in the preceding screenshot.

Figure 4.29: Click Allow access to allow the docker service access, as prompted by the Windows defender virus checker

You need to click on the Allow access command button, in Windows Defender to allow this to run, as shown in the preceding screenshot.

Figure 4.30: The user is prompted to Sign in here to register with the Docker hub

Now we click on the Sign in here link as shown in the preceding screenshot.

Figure 4.31: The user is prompted to log into the Docker Hub

The Docker Hub log-on is shown, where we can enter the account ID and password, we set up in Section

Figure 4.32: The docker command to push the container built during the tutorial is displayed

The container we built can now be pushed to the Docker Hub, where it will be stored (for 6 months anyway, from when the new rules come in, in November So, to explain further, any images uploaded before November 2020 were always stored with no time limit, but after this date, the clock will start ticking down from November 2020 and any images not accessed for 6 months after this date will then be deleted!):

Figure 4.33: The command can be run by clicking to paste it to the Terminal window So, in the preceding push command, we give the container we built an identifier tag, which will allow us to pull it down and use the docker push to store it in the Docker Hub repository: docker tag docker1010tutorial alanbluck/docker101tutorial docker push alanbluck/docker101tutorial

Figure 4.34: The push results can be seen in the terminal window of the tutorial page

The repository is found in the following link: https://hub.docker.com/repositories

Figure 4.35: The Docker Hub shows the containers we have built and pushed

The existing containers, which you have pushed to the hub, can be viewed and their status can be seen. I have one public and one private container for download on this Docker account:

Figure 4.36: The tutorial can be closed by clicking on the Done command button

The tutorial is now completed, so we can click as shown in the preceding screenshot.

Figure 4.37: The docker-tutorial image can be launched to run this tutorial

http://localhost/tutorial/ The preceding link is the link to the local server Docker web URL address, where the tutorial is held:

Figure 4.38: The command is now displayed with a description of the parameters The preceding screenshot shows the details of the commands we have entered.

Figure 4.39: The docker-tutorial container is displayed in the Docker Desktop

The preceding desktop shows that Docker is running with one container in the list (the one we built). For a listed container, on mouse-over the Docker Desktop icons appear:

Figure 4.40: The mouse-over shows the icon commands and the function of each icon The last icon is the Delete icon, which will delete the container. If you click on the container, additional menu items are shown in the desktop, shown as follows. As shown, the first sub-menu shows

Figure 4.41: The Container Logs can be displayed The next menu item in the list is Inspect used to show the parameters of the container. The Inspect menu shows the path of the container, the version of the supporting web application server, NGINX. The NJS (JavaScript engine used by NGINX) version is also shown. The docker-tutorial container package release version is shown (set to 1 as we have just built and released it), and also the port details of the web access to the container. The Stats sub-menu shows the CPU usage (negligible) and the memory usage, just 8.2 MB. Also, the network I/O usage is shown, which is also very small, as you might expect.

4.2.2.2: Create an example Docker Container

The procedure in the publication, the following link shows the commands required to create a Docker Container using the docker-compose tool:

https://doi.org/10.13140/RG.2.2.36842.88007

Installation of Eclipse Codewind and Docker Compose on RHEL 8 Linux with IBM Cloud Private CE (Community Edition), pages 15-23.

4.2.2.3: Edit the Compose file to add a bind mount

Changes can be made for development simply by editing the docker-compose.yml in the project directory to add a bind mount for the web service. This is described in the publication, see the following link:

https://doi.org/10.13140/RG.2.2.36842.88007

Installation of Eclipse Codewind and Docker Compose on RHEL 8 Linux with IBM Cloud Private CE (Community Edition), pages

4.3: Docker pull command

The following commands show two examples of pulling a container from the Docker Hub. The first command can be used successfully without logging into the Docker Hub; the second example requires you to log in.

To load the image for the OpenLDAP container image, you can just run the docker pull command, shown as follows, without having to log into the Docker Hub: [root@ecmukdemo10 opt]# cd $Home [root@ecmukdemo10 ~]# docker pull osixia/openldap Using default tag: latest latest: Pulling from osixia/openldap 27833a3ba0a5: Pull complete e73966112593: Pull complete f68421a1195a: Pull complete 79357b03067c: Pull complete f2e418c55f56: Pull complete 6b46f2044202: Pull complete e48097182527: Pull complete fce70c83d920: Pull complete 35210aa1453c: Pull complete Digest: sha256:d556418a1f5845f30affabdb850e93402cba6483f6279be965560083 b65508da Status: Downloaded newer image for osixia/openldap:latest

docker.io/osixia/openldap:latest

For the IBM Container for DB2 version 11.1.4.4 for development, you need to use your Docker ID and password to log into the Docker Hub.

If you attempt to use docker pull without logging in, you get:

[root@ecmukdemo10 ~]# docker pull store/ibmcorp/db2_developer_c: 11.1.4.4-x86_64 Error response from daemon: pull access denied for store/ibmcorp/db2_developer_c, repository does not exist or may require 'docker login'

The docker login command must be used as follows: [root@ecmukdemo10 ~]# docker login

Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one. Username: alanbluck Password: WARNING! Your password will be stored unencrypted in /root/.docker/config.json.

Configure a credential helper to remove this warning. See the following link: https://docs.docker.com/engine/reference/commandline/login/#creden tials-store Login Succeeded

Now the failed pull for the IBM DB2 11.1.4.4 container image is successful: [root@ecmukdemo10 ~]#  docker pull store/ibmcorp/db2_developer_c:11.1.4.4-x86_64 11.1.4.4-x86_64: Pulling from store/ibmcorp/db2_developer_c 7dc0dca2b151: Pull complete baf90ce421c0: Pull complete 9044ef4b93fe: Pull complete 075362411155: Pull complete 1e526c4d4980: Pull complete 85e97a1c49f1: Pull complete 0b051b2dcf3e: Pull complete Digest: sha256:3e33958584ea7301d5791473fdbb37b2747963a83f8ef3258a7ab44a2 ea3868d Status: Downloaded newer image for store/ibmcorp/db2_developer_c: 11.1.4.4-x86_64 docker.io/store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

4.4: Docker exec command

The docker exec command allows access into a Docker Container. For example, for a new pre-release IBM Docker Container; I access this to edit a property file inside the actual container using the following command:

[root@ECMUKDEMO6 ~]# docker exec -it db2graph bash The flags -i and -t tell Docker that we want an interactive session with a tty attached. These flags/command line switches can be entered in any order; -it and -ti have exactly the same effect.

The preceding command loads the Bash shell from within the db2graph container; so, commands show the directory structure and files from within the container environment:

So, the ls command displays the files and folders within the container:

bash-4.2$ ls So, as can be seen in the output line from the ls command, shown below, you should see the following list, including the graphs folder we are require to change directory to:

bkup credentials graphs gremlin jdbc_license_jars keyStore logs ssl support

I change to the graphs directory:

bash-4.2$ cd graphs

Then I can access and edit a specific property file for use with

castore.properties gremlin.graph=com.ibm.db2graph.structure.DB2Graph db2graph.configfile=/db2graph/graphs/castore_CASTORE1.json

4.5: Docker ps command

The docker ps command shows the containers in the host server memory, giving the output as listed below:

(base) [root@ecmukdemo10 common-services]# docker ps CONTAINER ID    IMAGE    COMMAND CREATED         STATUS    PORTS   NAMES 43eee115ee40    103d5b1ea1a2  "sh -ec '/bin/mongod…" 47 hours ago    Up 47 hours k8s_metrics_icp-mongodb-0_kube-system_17caad93-c7d7-11e9-9cdb000c29fa0dd9_11 ffe0ae796c64   a3abd47e8d61 "mongod --config=/da…" 47 hours ago  Up 47 hours k8s_icp-mongodb_icp-mongodb-0_kube-system_17caad93-c7d7-11e99cdb-000c29fa0dd9_11 591c17f6930a   c90e4b49722e "start_runit"    47 hours ago  Up 47 hours k8s_calico-node_calico-node-v5glg_kube-system_f7f74df6-c7d6-11e99cdb-000c29fa0dd9_12 etc…. d98dad31b77c  ibmcorp/content_navigator:latest "/usr/bin/supervisor…"  12 months ago  Up 47 hours 0.0.0.0:9081->9080/tcp, 0.0.0.0:9444->9443/tcp icn 92705574df8c ibmcorp/filenet_content_platform_engine:latest "/usr/bin/supervisor…"  12 months ago  Up 47 hours

0.0.0.0:9080->9080/tcp, 0.0.0.0:9443->9443/tcp, 38241/tcp cpe a73ee96ff4d8  store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

"/var/db2_setup/lib/…"  12 months ago  Up 47 hours 22/tcp, 55000/tcp, 60006-60007/tcp, 0.0.0.0:50000->50000/tcp   db2 ddad9d71a503  osixia/openldap:latest "/container/tool/run…"  12 months ago  Up 47 hours 0.0.0.0:80->80/tcp, 0.0.0.0:389->389/tcp, 636/tcp ldap (base) [root@ecmukdemo10 common-services]#

4.6 Docker run command

The docker run command is used to run a stopped container. For example, for the Jupyter Notebook Docker Container.

In the following command, removes the container after it exits.

The -v points to a shared folder the container can use to transfer or load data to the external host server. The -p shows the port translation from the internal container network port to the externally visible network port on the host server:

[root@ecmukdemo10 db2script]# docker run --rm -it -p 8888:8888 v "$(pwd):/notebooks" jupyter/datascience-notebook Executing the command: jupyter notebook [I 07:09:37.595 NotebookApp] Writing notebook server cookie secret to /home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret [I 07:09:40.053 NotebookApp] JupyterLab extension loaded from /opt/conda/lib/python3.7/site-packages/jupyterlab [I 07:09:40.054 NotebookApp] JupyterLab application directory is /opt/conda/share/jupyter/lab [I 07:09:40.063 NotebookApp] Serving notebooks from local directory: /home/jovyan [I 07:09:40.063 NotebookApp] The Jupyter Notebook is running at: [I 07:09:40.064 NotebookApp] http://d321c2f4b88e:8888/? token=d16d2f8f8eadac32f3c19820f4484aad0e726d3d0c8efc94

[I 07:09:40.064 NotebookApp]  or http://127.0.0.1:8888/? token=d16d2f8f8eadac32f3c19820f4484aad0e726d3d0c8efc94

[I 07:09:40.064 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation). [C 07:09:40.081 NotebookApp]

To access the notebook, open this file in a browser:

file:///home/jovyan/.local/share/jupyter/runtime/nbserver-6-open.html Or copy and paste one of these URLs: http://d321c2f4b88e:8888/? token=d16d2f8f8eadac32f3c19820f4484aad0e726d3d0c8efc94 or http://127.0.0.1:8888/? token=d16d2f8f8eadac32f3c19820f4484aad0e726d3d0c8efc94 where is the unique Docker container ID for the Jupyter notebook container.

4.7: Experimenting with some other commands

Try some of the commands outlined as follows. Use docker ps to see the effect on the selected container.

Pause processes in a running container:

docker pause [CONTAINER] Unpause processes in a running container:

docker unpause [CONTAINER]

Block a container until others stop (after which it prints their exit codes):

docker wait [CONTAINER]

Kill a container by sending a SIGKILL command to a running container: docker kill [CONTAINER]

Attach local standard input, output, and error I/O streams to a running container:

docker attach [CONTAINER]

Start a container:

docker start [CONTAINER]

Stop a running container:

docker stop [CONTAINER] Stop a running container and start it up again:

docker restart [CONTAINER]

4.8 Red Hat and CentOS 8.0

The Red Hat Linux server Operating System, RHEL 8.0 has a fully binary compatible ‘free’ version called CentOS 8.0. So, the library requirements listed in this section for RedHat RHEL 8.0, apply equally to the CentOS 8.0 system.

4.8.1: Use of Compatibility Matrix URLs

IBM has the following URLs, to run the Compatibility Matrix reports. The following steps can be followed to retrieve the reports for a selected IBM Software package. In this chapter, we are interested in the Compatibility Matrices for IBM Watson Explorer products, and IBM Stored IQ for Legal (VM) 2.0.3.7 in order to identify the prerequisite libraries we require.

See Chapter 2, IBM Component Software Compatibility for the full step-by-step procedure to obtain the target URL for the Compatibility Matrix.

For IBM Watson versions, first check the Release Notes:

Release Notes - IBM Watson Explorer Foundational Components, Version 12.0:

https://www.ibm.com/support/pages/release-notes-ibm-watsonexplorer-foundational-components-version-120#inst12034

This state: “Red Hat Enterprise Linux versions 6 are not supported in Version 12.0.3.3 or later.” Compatibility reports can be procured for IBM Software products at the following link:

https://www.ibm.com/support/pages/software-product-compatibilityreports

From the preceding link, you will be able to enter the name of the product to list the Compatibility Matrix link.

This link, in Step expands to the URL, as follows:

https://www.ibm.com/software/reports/compatibility/clarity/index.html

To target the required compatibility report, select the search box and enter the string IBM Watson Then, select Watson Explorer Deep Analytics and then you can select version 12.0.3.0 base edition from the Version drop-down, or if you install from the Fix Packs, click on the Show fix packs checkbox first, and (currently at August 2020) this shows version 12.0.3.4.

Clicking the Submit command button will then render a report, which will show a number of tabs for selection. The first tab is called Operating Systems (providing you selected [ticked] an operating system in your search, such as If you scroll down on this tab, you will see a list of the recommended prerequisite libraries required for installation, currently for 12.0.3.4, these are as follows:

For RHEL 7 Linux,

Note 1 Supported for both oneWEX for ICP and oneWEX for single container deployment. oneWEX for single container deployment does not support high availability and scale-out by adding additional containers. Note 2 The following 32-bit libraries are required on Linux x86-64 systems:

- libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit) - libstdc++ (libstdc++.i686 / libstdc++6-32bit) - zlib (zlib.i686 / libz1-32bit / zlib-32bit) - libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit) - libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) - libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) - libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit) - libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit) and:

If you want to support the ability to generate thumbnails for certain types of documents in the search results, you must install the following libraries:

- libXm - libXt - bzip2-libs (both 32-bit and 64-bit) With the following paragraph, the Support of Watson Explorer Analytical Components with Watson Knowledge Studio Annotator Support is available on RHEL 7.0, or later fix packs only. Note 4 states: When you use Annotation Administration Console the following 32bit libraries are required on Linux x86-64 systems: -

libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit) libstdc++ (libstdc++.i686 / libstdc++6-32bit) zlib (zlib.i686 / libz1-32bit / zlib-32bit) libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit)

-

libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit) libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit)

compat-libstdc++-33 package will be found in the optional packaging repository. You may need to configure the repository properly.

4.8.2: Use of Red Hat Linux upgrades

For Red Hat Linux RHEL 8.x, the Subscription Manager can be used together with the yum installer to upgrade packages.

Chapter 1, Getting Started with IBM Resources for shows the main location for download of RHEL 8.0, and the versions available for supporting a production system. IBM StoredIQ can be downloaded as a VMware compatible .ova file. This includes its own CentOS 7 operating system for direct loading to VMware, including VMware Workstation Pro 15.5, so it does not have so many issues of compatibility, but does still require supporting Windows Hypervisor and VMware virtual machine host version recommendations for a production environment. So, for example, in this instance, the supported VM for production is supported with VMware vSphere 6.5 from StoredIQ for Legal (VM) version 2.0.3.9 onwards.

4.9: IBM Watson Explorer oneWEX 12.x Docker Container

The IBM Watson Explorer Discovery docker container can be installed with due regard to the prerequisite requirements covered in this section.

4.9.1: Server(s) required for the installations

The minimum hardware requirements for an IBM Cloud Private multi-node cluster of servers are shown in Table of Section

I have combined the Boot node and Master node servers and called this MasterBoot.

(I have not used a management node, VA node, or etcd node server as I have selected the minimum requirement for a development environment.) This minimum development cluster of three VMware servers can be created for an IBM Cloud Private installation.

4.9.2: Red Hat Subscription Manager configurations

The Red Hat RHEL 8.0 operating system is used for the IBM Watson oneWEX Docker container installation, which was set up with the Docker container system and an installation of IBM Cloud Private.

The VMware Workstation support for RHEL 8.0 (or CentOS 8.0) only starts with VMware Workstation Pro version 15.1.0; so this needs to be installed as an upgrade (or a new installation) first!

4.9.2.1: Enabling subscribe to the RHEL system

The following procedure is required to allow the download of additional packages and libraries for the prerequisites to run the IBM Software packages. This procedure is covered in full by the following link:

https://doi.org/10.13140/RG.2.2.27358.18246 IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Page 37 to 40.

4.9.2.2: Change the host name to ecmukdemo10

Log in as the root administration user: su - root

Choose the domain name. (I have used my company domain name, registered to ASB Software Development To set a Fully Qualified Domain Name use the Linux hostnamectl command:

hostnamectl set-hostname ecmukdemo10.asbsoftware.co.uk

4.9.2.3: Check available repositories

Once you have completed your subscription, you can review the enabled repositories by using the following command:

yum repolist

4.9.2.4: RHEL 8 system setup a remote repository

If you want to enable more repositories for your RHEL installation, you can edit the following file:

vi /etc/yum.repos.d/redhat.repo

You can also use the command: yum-config-manager --enable repositoryID

where repositoryID is the unique repository ID (use yum repolist all to list all the available repository IDs).

4.9.3: Memory and disk storage requirements and CPU cores required The following Table 4.1 lists the memory, and the minimum disk storage and CPU core requirements for the server cluster.

Requirement as

Table 4.1: The cluster server requirements used for IBM Cloud Private and the Docker installation I used 500 GB of disk space and 32 GB of memory, because the IBM CPIT shell script for installation of IBM FileNet Containers requires this. (See the BPB book, Installation and Configuration of IBM FileNet Information Management Software for reference.)

4.9.4: Network card set-up and DNS configuration

This section covers the required network and DNS server prerequisites required by the IBM Cloud private Cluster of servers that I used for the IBM Watson oneWEX Docker container installation.

This procedure is covered in full by the following link: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Page 46 to 60.

4.9.4.1: VMware network card set-up for a static IP address

The addresses in the two network cards originally set up in VMware use DHCP, so are allocated dynamically on system startup, and can change! Because we need to connect to other VMware servers (potentially), including a Tivoli Directory service server, I have allocated a fixed IP address, 10.10.10.70 to the ens33 card.

The IP address 10.10.10.70 is equivalently used as for the description of the IP address 10.10.10.130 used extensively in the full procedure covered in full by:

https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Page 46 to 60.

vi /etc/hosts

Edit the required IPs into the /etc/hosts file to resolve the static IP address. Append the following:

10.10.10.70 ecmukdemo2

10.10.10.10 P850

(The preceding P850 is an LDAP directory server).

(Assuming that you do not have a separate DNS server, of course).

Save the /etc/hosts file and reboot the server using the following:

shutdown -r now

Ensure the VMware Network Adaptor is set as

4.9.4.2: Install bind and configure to create a DNS server

We next have to install the Red Hat bind packages, using the following command:

dnf -y install bind*

Details of the configuration are in the procedure covered in the following link from pages 46 to https://doi.org/10.13140/RG.2.2.27358.18246

Configuring the firewall

The firewall has to be enabled for the Domain Name Service

firewall-cmd --permanent --zone=public --add-service=dns

and reload the configuration as follows:

firewall-cmd --reload I changed the second network card to be DHCP, giving “Host” VMware address of 192.169.50.140, since there is no access to the internet otherwise!

4.9.5: GUI library installation requirements

For the GUI, I installed the Linux X-Windows libraries, as follows, in the procedure. See the following link from Pages 40 to

https://doi.org/10.13140/RG.2.2.27358.18246

4.9.5.1: X-Windows Terminal installation

The yum installer command is used to install most Red Hat Linux packages and libraries at RHEL 8.0. (There are other installer utilities, such as conda [Anaconda] and

4.9.6: Folder structures and user security

IBM Watson oneWEX is configured for an LDAP server for validating user logons using a Liberty file, See the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/c_ee_adm_ldap_config.html

Upload a specific LDAP configuration file, using the /api/v1/usermgmt/config/file/{name} method in the Swagger UI (using

Upload the file custom_ldap_config.xml with a valid Liberty configuration.

The upload xml file MUST be called otherwise the configuration won’t be applied!

Example custom_ldap_config.xml set up as follows:

id="ldap" realm="asbsoftware.co.uk " host="ECMUKDEMO6.asbsoftware.co.uk" port="389" ignoreCase="true" baseDN="o=sample" bindDN="cn=root" bindPassword="filenet"

ldapType="IBM Tivoli Directory Server" sslEnabled="false" sslRef="">

userFilter="(&(mail=%v)(objectclass=ePerson))"

groupFilter="(&(cn=%v)(|(objectclass=groupOfNames) (objectclass=groupOfUniqueNames)))" userIdMap="*:mail" groupIdMap="*:cn" groupMemberIdMap="ibm-allGroups:member;ibmallGroups:uniqueMember" >

4.9.6.1: Preparation for IBM Security Directory Services

The following URL is a prerequisite for IBM Security Directory Services 6.4 installation of the Korn Shell and user creation, defined by the following link:

https://doi.org/10.13140/RG.2.2.33527.57761

IBM Security Directory Services 6.4-Installation on RHEL 8.0 Pages 37

4.9.7: Shared folder access and Docker set up requirements

IBM oneWEX explorer requires a mounted folder system access to enable it to use the File Crawler component for analysing text in files.

See the following link for more information:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/t_onewex_fs_access_docker.html

The following steps are required to connect IBM Watson Explorer oneWEX Docker Container to enable it to access files and any required Java libraries.

Navigate to the directory where IBM Watson Explorer oneWEX is installed, and run the following program:

./ibmwatsonexplorer

The details of the procedure are covered in the publication, in the following link: https://doi.org/10.13140/RG.2.2.12248.44803

IBM Watson Explorer oneWEX 12.0.3 Docker Container Installation on CENTOS Linux 8.0, October Pages

The folders should now be accessible within IBM Watson Explorer oneWEX.

The program will prompt you for security credentials, so that it can access the mounted folders. To access a folder from IBM Watson Explorer, you have to use the mount file path

For batch processes the configuration file can be edited to add the mount points in the mounts section of the file. An example is as follows:

"mounts": { "test-data": "/opt/data" } For another full list example of the config/wex.json file, see the IBM Knowledge Centre in the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/c_onewex_install_docker.html

The wex.json configuration file also allows the memory limits to be changed (which I had to change from the defaults):

Figure 4.42: Change to the /root/ibm/wex/config folder to edit the wex.json file Edit the wex.json Docker Container configuration file.

See the following link: https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_install_docker.html wex.json edited to increase the memory limits:

Figure 4.43: Default memory sizes set in the wex.json file are far too small! I changed the memory sizes to reflect a reasonable WebSphere Liberty working size as follows:

Figure 4.44: Updated memory sizes in the wex.json file

4.9.8: IBM Cloud Private Cluster set up and requirements

There is a good architecture overview Redbook available for download. See the following link:

IBM Cloud Private Application Developer’s Guide

http://www.redbooks.ibm.com/redbooks/pdfs/sg248441.pdf This does not cover any prerequisite set-up requirements, but focuses on the development of pods for use by the kubectl system.

The following reference from ASB Software Development covers the full installation of the IBM Cloud Private cluster, published on

https://doi.org/10.13140/RG.2.2.20256.94729

IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux

Chapter 10, IBM Cloud Private covers the installation of IBM Cloud Private 3.2.0 Community Edition It describes the download and installation using docker pull and the requirements of a single node cluster installation.

Sections 6.3.1 through in this chapter, covers the IBM Cloud Private system pre-requisites, since these are the same as for the Docker set up, as Docker is used to install the IBM Cloud Private CE as a number of docker container modules.

4.10: IBM Watson Explorer Foundational Components 12.x

The Watson Explorer Foundational Components 12.0.3.0 consists of a set of Red Hat Package Manager installation files contained in a Linux tar file which, after download, can then be copied, unpacked with the tar command, and installed with the yum install utility on the target Linux operating system platform.

4.10.1: Server(s) required for the installations

Since both, the IBM Watson Explorer oneWEX tar file and the IBM Watson Explorer Foundational Components tar file, were installed on the same IBM Cloud Private CentOS 8.0 cluster servers, sections 4.9.1 through in this chapter, covers the IBM Watson Explorer Foundational Components 12.x system prerequisites as these are the same as used for IBM Watson Explorer oneWEX.

4.10.2: Red Hat Subscription Manager configurations

The Red Hat RHEL 8.0 operating system used for the IBM Watson Explorer Foundational Components 12.x system installation was the same one that was set up with the Docker Container system, and an installation of IBM Cloud Private.

The VMware Workstation support for RHEL 8.0 only starts with VMware Workstation Pro version 15.1.0, so this needs to be installed as an upgrade (or a new installation) first! The Sections 4.9.2.1 through in this chapter, cover most of the configuration of the Red Hat Subscription Manager required for the Red Hat RHEL 8.0 operating system used.

There is an additional library required, for the Annotation Administration Console

The following fixed the missing library issue:

Figure 4.45: The CentOS rpm download site

From the preceding list, the following two rpm are required:

Figure 4.46: Highlighted libraries in the rpm packages are required Download and save the highlighted rpm packages. Change the security on the rpm files: [root@ecmukdemo20 Downloads]# chmod 775 *.rpm

[root@ecmukdemo20 Downloads]# ls compat-libstdc++-33-3.2.3-72.el7.i686.rpm  Container-PIT.zip ufone_tweets.csv compat-libstdc++-33-3.2.372.el7.x86_64.rpm  enron_mail_20150507.tar.gz

Install the 32-bit compat-libstdc++-33 library: [root@ecmukdemo20 Downloads]# yum install compat-libstdc++-333.2.3-72.el7.i686.rpm The summary of the preceding command log results is as follows: Installed: compat-libstdc++-33-3.2.3-72.el7.i686 Complete! [root@ecmukdemo20 Downloads]# ls compat-libstdc++-33-3.2.3-72.el7.i686.rpm  Container-PIT.zip ufone_tweets.csv compat-libstdc++-33-3.2.372.el7.x86_64.rpm  enron_mail_20150507.tar.gz Install the 64-bit compat-libstdc++-33 library:

[root@ecmukdemo20 Downloads]# yum install compat-libstdc++-333.2.3-72.el7.x86_64.rpm The summary of the above command log results is as follows: Installed: compat-libstdc++-33-3.2.3-72.el7.x86_64

Complete! [root@ecmukdemo20 Downloads] #

4.10.3: System requirements, CPU cores, DNS, and library installation requirements Since the same server was used for both IBM Watson Explorer oneWEX and the IBM Watson Explore Foundational Components 12.0X, the details of the memory and disk storage, the details of the network card set-up, the DNS, the GUI I installed, and the Linux X-Windows libraries are covered in Sections 4.9.3 to

The IBM Watson Explore Foundational Components 12.0X do not require a mounted folder system access to enable them to use the File Crawler component for analysing text in files, as they are not installed as Docker Container systems.

4.10.4: Red Hat OpenShift server cluster requirements

IBM Cloud Private 3.2.0 with OpenShift is newly supported at version 12.0.3.1 onwards of IBM Watson Explore Foundational Components.

The full requirements for this support are covered in Chapter 7, RedHat OpenShift 4.x Installations section, 7.1.2 Prerequisites Required

4.11: IBM StoredIQ For Legal 2.0.3.7

IBM StoredIQ for Legal VM 2.0.3.7 Server is supplied as an installation, which is a ready-built virtual machine .ova VMware file, based on CentOS 7.

There are some recent Fix Pack updates for IBM StoredIQ for Legal (VM) 2.0.3.7: Fix pack 2.0.3.10 requires the Chrome 79 version of the browser.

Fix pack 2.0.3.10 requires the Browser Firefox ESR 72 version.

Starting with Fix Pack 2.0.3.4, the custodian portal can also be accessed from Apple iPad tablets (iPad mini 4 with IOS 9.3.5 and iPad Pro with IOS 11).

However, there are certain limitations as described in the product Knowledge Centre. Please see the following link:

IBM StoredIQ products - system https://www.ibm.com/support/pages/ibm-storediq-products-systemrequirements

The following supporting IBM system products are already installed:

DB2 Workgroup Server Edition

IBM Content Navigator

IBM Security Directory Server 6.4.0.20

WebSphere Application Server 8.5.5.17

4.11.1: Server(s) required for the installations

The VMware virtual server, which is already supplied as a CentOS 7 virtual image OVF file, has 14 GB and 4 processors; so the host VMware system that we load it into must have at least 24 GB of memory and more than 4 cores for its CPU.

4.11.2: Red Hat Subscription Manager configurations

The IBM StoredIQ system comes ready-built with all the required sub-system components already installed.

4.11.3: Memory and disk storage requirements and CPU cores required The VMware virtual server is already supplied as a CentOS 7 virtual image OVF file, which has 14 GB and 4 processors.

The full details for this section are covered in the following link:

https://doi.org/10.13140/RG.2.2.12586.24008 IBM StoredIQ for Legal VM 2.0.3.7 Server Installation Steps for VMware Workstation Pro 15.5.6, Page 11

The IBM StoredIQ virtual machine is pre-built with two 97.7 GB SCSI hard disks. After installation, it takes up 44.9 GB of actual disk drive space.

4.11.4: Network card set-up and DNS configuration

The IBM StoredIQ VM has one network adapter card, but a number of virtual networks, which can be viewed using the ifconfig command.

This is a long list, because there are networks set up within the downloaded Virtual machine for separate preconfigured connectors. The /siq/bin/netcfg command can be run to manage the networks (see the other networks in the list).

4.11.5: GUI library installation requirements

IBM StoredIQ for Legal VM 2.0.3.7 Server is supplied as an installation, which is a ready-built virtual machine .ova VMware file; so the system is already set up, but only has a command line interface. It is accessed through web browser pages. For example, on my system:

https://ecmukdemo30.asbsoftware.co.uk:9443/navigator In general, the URL is the server fully qualified domain name followed by the HTTPS port number in the following form:

https://servername.domainname:9443/navigator

4.11.6: Folder structures and user security

You can set up user roles using the Web Administration tools, and the following security certificate procedure is followed:

StoredIQ for Legal (VM): root certificate import

The IBM StoredIQ root certificate is copied to the StoredIQ for Legal system: Log in as root to the IBM StoredIQ application server.

The /etc/siq/ssl/root.crt file must be copied to the root directory on the StoredIQ for Legal system.

Log in as root to the StoredIQ for Legal virtual machine.

Run the following command:

docker cp root.crt ilg_sol_plugin:/opt/IBM/WebSphere/AppServer/java_1.7.1_64/jre/bin The WebSphere Application Server container must be opened by running this command:

docker exec -it ilg_sol_plugin bash

Backup the certificates folder:

/opt/IBM/WebSphere/AppServer/java_1.7.1_64/jre/lib/security/cacerts.

cd down to the directory to which you copied the root.crt file:

cd /opt/IBM/WebSphere/AppServer/java_1.7.1_64/jre/bin

Run the keytool command to import the certificate:

./keytool -importcert -alias appstack -file root.crt -keystore /opt/IBM/WebSphere/AppServer/java_1.7.1_64/jre/lib/security/cacerts

Enter the password for the JRE keystore at the password prompt (the default password is

Enter y when asked whether to trust the certificate. User Roles are set up, as shown on pages 26 to 34 of the following link:

https://doi.org/10.13140/RG.2.2.12586.24008 IBM StoredIQ for Legal VM 2.0.3.7 Server Installation Steps for VMware Workstation Pro

I use the URL as follows:

https://ecmukdemo30.asbsoftware.co.uk:9443/navigator/ In general, the URL is the server fully qualified domain name followed by the HTTPS port number in the following form: https://servername.domainname:9443/navigator

4.12: Compatibility Matrix URLs

IBM have the following URL to a support knowledge base for IBM Watson Explorer Foundational Components 12.x.

For IBM Watson versions, first check the release notes:

https://www.ibm.com/support/pages/release-notes-ibm-watsonexplorer-foundational-components-version-120#inst12034 Compatibility reports can be procured for IBM Software products by following the links in the following page:

https://www.ibm.com/support/pages/node/598959

On this page, there is a table list that provides links to high-level or detailed system requirements that are sorted by type, operating system, and component.

Figure 4.47: Links to the Compatibility Matrix reports for IBM Watson on Windows

For example, the top link in the preceding screenshot gives the following:

Figure 4.48: The highlighted Download PDF link creates a downloadable PDF Report

4.13: IBM Watson Explorer Foundational Components 12.x

IBM Watson Explore Foundational Components 12.0.3.0 for Windows is downloaded as a .zip file:

IBM_WE_DEEP_ANALYTICS_EDITION_FOU.zip.

The download of this software .zip file is covered in detail, step by step in Chapter 1, Getting started with IBM Resources for Section 1.4.1.1 through to

It unpacks as the following, six ZIP and Windows MSI installer packages:

Figure 4.49: The contents of the IBM_WE_DEEP_ANALYTICS_EDITION_FOU.zip software package The first software component package wex-aac-12.0.3.0-dae.zip is the Annotation Administrator Console installation.

4.13.1: Compatibility issues and support limitations for the products listed in Chapter 1 To use the IBM Text Analytics features on Microsoft Windows platforms, the Microsoft Visual C Runtime version 10 or greater must be installed. (I am using Visual C Runtime version15.4).

Watson Explorer Engine is installed with an embedded Liberty web server (which is what I used), but IBM recommends that one of the following specified web servers is used, either Apache HTTP Server 2.0 and Fix Packs

Or

Microsoft Internet Information Services 6.0 and Fix Packs

4.13.1.1: For browsers

Microsoft Internet Explorer Version 11 is a supported browser; however, performance using this browser is slow and not recommended. Using other supported browsers is recommended, in preference.

For Google Chrome, Microsoft Edge, and Mozilla Firefox, it just states that use the latest version and Fix Packs. (I am using Google Chrome Version 84.0.4147.135 (Official Build) (64-bit). I also have Mozilla Firefox, version 80, both as of 25th August, 2020.).

4.13.2: Server(s) required for the installations

Only two Windows versions are listed for support, Windows Server 2012 Standard Edition x86-64 and Windows Server 2016 Standard Edition x86-64.

(I will demonstrate, later in this chapter, in Section 4.13.9, Installation and configuration of IBM Watson Foundation Components 12.0.3.0 on Windows that it can also be installed on Windows 10.0 Build 18363, Home Edition x86-64, with 16 GB memory and 1 TB Solid State Disk

4.13.3: Memory and disk storage requirements and CPU cores required The software package zipped takes 3.36 GB of disk space, unpacking it requires a further 4.45 GB. So, after extraction, there is a disk usage of 7.82 GB for version 12.0.3.0. The installed Foundation components take a further 6.04 GB of disk space, so you should allow for at least 14 GB of disk space in total.

For Windows, a minimum of 4 GB memory is recommended, plus 4 GB disk paging space. (This is also qualified as just suitable for a small, entry-level solution with a single document processor and up to 100MB of data.)

The CPU requirements, 64-bit (AMD64 or Intel 64) x86 system with 2 GHz, or higher processor, and 2 or more processor cores are required to run the AAC. This should be regarded as the minimum for the processing of one active collection.

4.13.4: Folder structures and user security

During configuration of the ZooKeeper configuration file, a prompt is raised to specify a working folder. This is created, by default as ZooKeeperData under the main installation folder

There are similar folders prompted for during the installation of the other components of the IBM Watson Explorer system, covered in Section

4.13.5: Firewall – Windows Defender configuration

There are a number of ports used, which can be configured during the Windows component-config.exe configuration after the initial set-up. See Section 4.13.9 for the figures showing the install defaults. (These ports can be modified during installation to prevent any conflict with your existing software. It is advisable to have a list of the existing network ports used on your Windows install environment to avoid any port conflicts.)

4.13.6: Supporting Java jdbc jar files and PATH environment set-up

The Java SDK, IBM Runtime Environment, Java Technology Edition 8.0.5.21 is required for compiling Java applications. This requirement also needs an installation and configuration of the Apache ANT (V1.7), the Apache Java-based build tool.

4.13.7: Windows hosts file configuration for server network access

The server name is used for the URLs established during the install configuration. (MSI in my installation example in Section

4.13.8: Stopping the running of windows services for install upgrades If you need to stop the services for upgrade, stop the Application Builder first, and ZooKeeper last.

The Windows service component list is shown in Table as follows:

follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows:

Table 4.2: The Windows Services which are installed (using a postinstall set-up)

4.13.9: Installation and configuration of IBM Watson Foundation Components 12.0.3.0 on Windows 10 Home Edition Unpack the IBM_WE_DEEP_ANALYTICS_EDITION_FOU.zip download (see Chapter 1, Getting Started with IBM Resources for Sections 1.4.1.1 to

Figure 4.50: Unpack the downloaded IBM_WE_DEEP_ANALYTICS_EDITION_FOU.zip

The extracted file is extracted to the installation folder of the target Windows 10 server.

As can be seen during the installation, this Windows 10 operating system is not on the list of supported environments, so cannot be used in a production environment, but it functions correctly and is useful for training purposes. 7-Zip can be obtained free from

Figure 4.51: The 7-zip open source utility is used to unpack the installation .msi files

The main .zip file contains the wex-aac-12.0.3.0-dae.zip file, which must itself be unpacked:

Figure 4.52: From Windows Explorer, right-mouse click and select 7-zip and the Extract the wex-aac-12.0.3.0-dae.zip to a wex-aac-12.0.3.0-dae subfolder

The wex-aac-12.0.3.0-dae.zip is extracted to a sub-folder of the same stem name, wex-aac-12.0.3.0-dae and the install.exe program is double-clicked (circled as follows in figure to start the AAC installation:

Figure 4.53: Double-click on the install.exe program to start the Installation of AAC

The InstallAnywhere Windows installer is launched to load the install files:

Figure 4.54: The InstallAnywhere windows installer is loaded

The IBM Watson Explorer Annotation Administration Console version 12.0.3 splash screen is launched next:

Figure 4.55: The splash screen verifies the install is as expected The installation version can be verified from the first splash screen, and the required language can be selected from the dropdown, as shown in the preceding screenshot. Click on the OK command button to start the installation validation.

Figure 4.56: The installer has detected that this is an unsupported operating system As expected, the installer validates the operating system and flags this as an unsupported Windows operating system version. The only two supported versions are Windows Server 2012 Standard Edition x86-64 and Windows Server 2016 Standard Edition x86-64 (as described in Section In the preceding screenshot, I clicked on the Ignore command button to continue the installation. I used the Windows Command Prompt to run the ipconfig /all command to display the Windows host name, as this is an entry in the install window.

Figure 4.57: The ipconfig /all command shows the Windows Host name is MSI The following screen gives you the opportunity of entering a new Windows user account name and password, which the installer will create for you as a separate user to log into your windows system:

Figure 4.58: The Host name, username and password of a new Windows user is entered; then click on the Advanced Options if you don’t want to install on the default C Drive In the preceding screenshot, I used Advanced since I have a small C disk, and I need to redirect the install area for the program to the D drive.

Figure 4.59: After selecting the required Installation and Data directories, note or change the port defaults and click Next I left the default ports after changing the drive letter for the installation and data directories to nd then clicked The default ports are set as:

Common Communication Layer (CCL) 6002 Data storage 1527

Search server port is set to: 8394

On the next screen, as shown in the following screenshot, the Windows Defender built-in virus/malware detector for Windows 10 is launched by the operating system to check if we wish to allow security access to the system, which the installer requires:

Figure 4.60: Click Allow access to proceed with the installation

The next screen gives you the opportunity of changing the default Administration Console web application port for the URL, which, it should be noted, can be accessed using the following link:

http://MSI:8390/ESAdmin (I left this default port as

The Text analytics API port defaults to 8393 in:

http://MSI:8393/api Where MSI in the preceding URLs is the Windows host server name.

Figure 4.61: Click Next after reviewing the port numbers

The next screen shows the required installation disk space required for the installation of the IBM Watson Explorer Annotation Administration Console:

Figure 4.62: Click Install to start the installation

The size of the installation is shown in the preceding screenshot as 1,699,367,943 Bytes (or 1.5827 GB). Click on the Install button to start the installation of the IBM Watson Explorer Annotation Administration Console:

Figure 4.63: The status and progress of the Installation

The completed installation gives you the opportunity of restarting the Windows operating system straight away, or allows you just to close the installer. But you will then need to reboot the system before using the installed software!

Figure 4.64: I selected Yes, to restart my system straight away, after clicking Done After restarting the Windows server, you must run the cmd.exe window as Run as

Figure 4.65: The system can be started with the use of two batch files

The startccl.bat file is used first to start the Common Communication Layer service required for the annotation communications. Or

The esadmin system startall command can be used to start all the services:

Figure 4.66: The system can be started with a single esadmin system startall command The status of the installation can be reviewed by opening the installation log, shown as follows:

Figure 4.67: The v12.0.3.0install.log

The log should contain the following installation summary, if all has been installed Summary ------Installation: Successful. 3049 Successes 0 Warnings 0 NonFatalErrors 0 FatalErrors Action Notes:

None Check Disk Space:  C:\Program Files (x86)\IBM\es Status: SUCCESSFUL Additional Notes: NOTE - Required Disk Space:1,326,838,414 Bytes Free Disk Space:7,335,628,800 Bytes

To start the server, the command cmd.exe must be run as the Windows Administrator. Run the cmd.exe command as administrator, and then run the following:

Figure 4.68: The start command esadmin system startall esadmin system startall from the install directory D:\Program files\IBM\es\bin directory

Now we can launch the IBM Watson Explorer Annotation Administration Console using the URL: http://localhost:8390/ESAdmin/

Figure 4.69: The Administration Console using the URL http://localhost:8390/ESAdmin/ The login user should be the new Windows user name and password that you entered earlier during the installation.

Figure 4.70: The esadmin user is used, set up in the installation plus the password entered

This user (default name is the administrator user for the IBM Watson Annotation Administration Console.

Figure 4.71: The Create Collection screen is loaded as expected ready to process After you login, you are now able to create a collection for analysis.

Figure 4.72: The Annotators can be administered from this console page And you can enable/disable the UIMA Annotators, as shown in the preceding screenshot.

4.13.9.1: Installing the other components

In turn, double click on the following .msi software installation components:

Figure 4.73: The highlighted components are installed

The preceding .msi files are double-clicked in turn to install the rest of the IBM Watson Foundational components, 12.0.3.0.

Install all the preceding highlighted five components before starting any of them, as they have to be started in a specific order!

Figure 4.74: The Application Builder install is loaded with double-click on wex-appbuilder-12.0.3.0-dae_en.msi

The Application Builder installer displays the license required for this component, which you have to review and agree to. It has a scroll bar which allows you to scroll down to see the text. You can also select the text with your mouse and use CTRL + A to select all the text, CTRL + C to copy the selected text, and CTRL + V in a notepad.exe window or in a new blank MS Word document to view and print the license information:

Figure 4.75: Tick I accept after viewing the User License and then click Next

The license lists the components covered by this installation.

Figure 4.76: The Change… command can be used to change the Drive and folder path The Destination Folder for the installation defaults to the C: Drive, but you can change this default, as shown in the following screenshot:

Figure 4.77: The default drive is set to D:\ from C:\ using the Change… command The Change… command was used to modify the folder path to D:\ as I only have limited space on the C:\ drive:

Figure 4.78: The Install command button starts the Application Builder installation On clicking the Install command button, the installer setup page is displayed with the status of the installation:

Figure 4.79: The installation status is displayed

You can monitor the status of the setup and the status bar will give you an idea of the progress of the installation, shown as follows:

Figure 4.80: The installer copies files for installation from the .msi compressed file

Click Finish after the install has completed:

Figure 4.81: Click Finish to close the installation window

4.13.9.2: Procedure

The following procedure steps should be followed to configure the initial Application Builder after installation:

Create a list of the user names and passwords that you wish to add as users for running Application Builder.

Stop the Application Builder service on the server, where Application Builder is installed. For more information about starting and stopping Application Builder, see the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_services.html#c_wex_native _services.dita

When starting the services, always:

Start ZooKeeper first (Application Builder relies on ZooKeeper for its configuration data).

Start all the other services except Application Builder. Then start Application Builder last.

If you need to stop the Services in the future, stop Application Builder first, and ZooKeeper last.

To add your list of users, find the server.xml file from within the AppBuilder/wlp/usr/servers/AppBuilder directory, and then open the file in a text editor:

In the basicRegistry node of the server.xml file, add the user names and passwords for the end users and administrators of the Application Builder application. The following example shows the default Application Builder administrator user, and sample user names and passwords:

id="basic" realm="customRealm"> name="data-explorer-admin" password="TH1nk1710" /> name="user-1" password="password-1" /> name="user-2" password="password-2" />

The next component to be installed is called It is more of a sample Java project with examples of using the API, than an actual working program. (Also, it is a deprecated component of the IBM Watson Foundational Components at 12.0.3.)

Figure 4.82: Double click on the wex-bigindex-12.0.3.0-dae_en.msi file and click Next

The End-User License Agreement text is shown in the next window, which you have to review and agree to:

Figure 4.83: View the license and tick the I accept box, then click Next

On clicking Next you get an opportunity of redirecting the installation from the default C: drive to a different installation drive and path:

Figure 4.84: Click on Change… to change the drive from C:\ Select Change… to select the D: drive:

Figure 4.85: The D:\ drive is entered, then click OK

After selecting the drive and path for the BigIndex API installation, click OK and then

Figure 4.86: Click Next to start the Install

The drive and path selected can be reviewed at this point, and you can use the Back command button, as shown in the preceding screenshot, to change the path if you spot an error or wish to change the path back again.

Figure 4.87: Click Install to start the installation of the BigIndex API component Clicking the Install command button will launch the installer status window:

Figure 4.88: Click Finish to close the completed installation of the BigIndex API

After the setup wizard has extracted the sample project, you can click on the Finish command button, as shown in the preceding screenshot, to complete the installation of BigIndex. The next component to be started is run by clicking on the which loads the splash screen as follows:

Figure 4.89: Double click on the wex-engine-12.0.3.0-dae_en.msi and click Next

Once again, the Engine component has its own separate license agreement, which you need to review:

Figure 4.90: View the License and tick the I accept box, then click Next After ticking the I accept the terms in License Agreement checkbox, you can print the license agreement and click on Next as shown in the preceding screenshot.

Figure 4.91: Click Change… to change the drive from C:\ to D:\

The C:\ drive default has to be changed on my system to D:\ to preserve the space on the limited space on

Figure 4.92: Click OK to start the installation of the Engine component

I have used the same root destination folder for all the components, so I have D:\Program Files\IBM\WEX as the target for the installation of the Watson Explorer Engine 12.0.3.0 component:

Figure 4.93: Click Next after changing the drive or folder path (if required) After clicking as shown in the preceding screenshot, you will see the install screen to allow you to begin the install:

Figure 4.94: Click Install to start the Watson Explorer Engine 12.0.3.0 installation

As can be seen in the following screenshot, the Windows Administrator security level access is required by the installer, since it has to update the Windows registry to register the environment variables:

Figure 4.95: The status shows the update of the registration of the Engine component

The successful installation displays the Finish command button:

Figure 4.96: The installer can be closed by clicking the Finish command button Click Double click on the wex-resultsmodule-12.0.3.0-dae_en.msi file.

Figure 4.97: The splash screen displays the Results Module 12.0.3.0 for install

Click Next and review the license details:

Figure 4.98: Select the I accept tick box and click Next to display the install path I changed the install path from a C:\ drive to D:\ drive:

Figure 4.99: Click the Change… to change the drive or install path as required The folder root is left as as shown in the preceding screenshot; I just changed the drive letter from C to

Figure 4.100: The Drive letter was changed to D; click OK to continue installing

Figure 4.101: The updated install path can be reviewed; click Next The next screen allows you to start the installation:

Figure 4.102: Click the Install command to start the installation of the Results Module

Figure 4.103: The status of the IBM Watson Explorer Results Module install is displayed If the installation of the IBM Watson Explorer Results Module is successful, the Finish command button can be clicked:

Figure 4.104: The IBM Watson Explorer Results Module 12.0.3.0 is installed Click on the wex-zookeeper-12.0.3.0-dae_en.msi install file to start the IBM Watson Explorer ZooKeeper 12.0.3.0 Setup as shown in the following screenshot:

Figure 4.105: The setupwWizard for Watson Explorer Zookeeper is displayed – click Next Review the IBM Watson ZooKeeper component license agreement and click I accept the terms in the License as shown in following screenshot:

Figure 4.106: Tick the I accept box and click Next to show the install path change screen I changed the installation location from the C: drive to the D: drive:

Figure 4.107: Click on Change… to change the installation path if required The changed drive path can be reviewed; then click OK to confirm, ready for installation of the IBM Watson Explorer ZooKeeper 12.0.3.0.

Figure 4.108: The install path is updated to D:\Program Files\IBM\WEX; click OK

Figure 4.109: Click Next to confirm the installation path

Figure 4.110: Click Install to start the installation of the ZooKeeper module After the installation of IBM Watson Zookeeper, reboot the Windows 10 system. For information about this release of IBM Watson Explorer Foundational Components, see the following documentation:

http://www.ibm.com/support/knowledgecenter/SS8NLW/SS8NLW_wel come.html

And the release notes as follows:

http://www.ibm.com/support/docview.wss?uid=swg27048565 This procedure requires changing the basic registry for Application Builder. First you will need to make a backup of the server.xml file from the AppBuilder/wlp/usr/servers/AppBuilder directory, and then open the file in a text editor.

Edit the first search for the basicRegistry node of the to add the user names and passwords for the end users and administrators of the Application Builder application. The following example shows the default Application Builder administrator user, and the placeholders for some sample user names and passwords (highlighted): id="basic" realm="customRealm"> name="data-explorer-admin" password="TH1nk1710" /> name="user1" password="password1" /> name="user2" password="password2" /> … name="usern" password="passwordn" /> When starting the services, always start ZooKeeper first (Application Builder requires ZooKeeper for its configuration data). Then start all the other services except Application Builder. Finally, start the Application Builder last. If you need to stop the services, stop Application Builder first, and ZooKeeper last.

We now need to run set-up configuration programs to enable windows services for the following installed programs:

programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs: programs:

programs: programs: programs: programs: programs: programs:

Table 4.3: The IBM Watson Explorer 12.0.3.0 components to be installed as services

Figure 4.111: In the command window, locate zookeeper-config.exe

The zookeeper-config.exe program is run from a Windows cmd.exe Command Prompt. This must be Run as as shown in the following screenshot:

Figure 4.112: Right-mouse click on the Command Prompt and then select More-> Run as administrator

The security access of Windows Administrator is required, because the windows registry is accessed to set the Windows services for each of the Watson components listed in Table following the procedure as:

Figure 4.113: Run zookeeper-config.exe to add the ZooKeeper as a Windows service I used the defaults for the ZooKeeper windows service as follows, when prompted by

Client listener port: The ZooKeeper data store folder is as follows: D:/ProgramFiles/IBM/WEX/ZooKeeperData Notice that the program expects the path in java format, using the forward slash, as shown earlier for the default! The ZooKeeper ID: The ZooKeeper’s cluster servers and ports The ZooKeeper additional configuration string required (semicolon separated): initLimit=1000;syncLimit=1000;tickTime=2000;autopurge.snapRetainC ount=3;autopurge.purgeInterval=1 (Additional configuration parameters required are semi-colon separated). Finally, confirm the service enablement by entering

Afterwards, in the windows Task Manager program, Services tab (after reloading it!), the following can be seen:

Figure 4.114: The windows Task Manager Services tab shows the zookeeper-service was successfully installed The resultsmodule-config.exe program should be located for running, in order to install the Results Module windows service:

Figure 4.115: The location of the resultsmodule-config.exe

The resultsmodule-config.exe program is run from a Windows cmd.exe Command Prompt. This must be Run as windows administrator, as shown in figure

Figure 4.116: The resultsmodule-config.exe prompts for configuration parameters I used the following default parameters (which you can change if required) for the resultsmodule-service windows service:

The language: en The Results Module listener port: 8081 The virtual directory name to be used: ResultsModule Finally, confirm the resultsmodule-service Windows service enablement by entering Afterwards, in the windows Task Manager program, Services tab (after reloading it!), the following can be seen:

Figure 4.117: The resultsmodule-Windows service is shown after running resultsmodule-config.exe Click on Description to sort the services and start the

The Description column can be selected for sorting the services, in the Windows Task Manager program, so the IBM Watson Explorer installed services appear together. Then, to start the services, starting with right-mouse click, as shown in following screenshot, and click on

Figure 4.118: The zookeeper-service is started first Repeat the start for the

Figure 4.119: The resultsmodule-service is started next

The engine-start.exe module is started, as shown in the following Figure

Figure 4.120: Start the IBM Watson Explorer engine component The program displays the following, as shown in the following screenshot on running:

Figure 4.121: The Date and time of starting is shown and shows the status The bigindex API is unpacked using as shown in the following screenshot:

Figure 4.122: The bigindex.zip is extracted to a subfolder with the same stem name

Extracts an example Java API Eclipse

Figure 4.123: The extracted sample Bigindex API project is available for review The appbuilder-config.exe service is used to install the Windows service,

Figure 4.124: Locate and run the appbuilder-config.exe to add the windows service Enter the default parameters following (or change as required) for the The virtual directory to use: AppBuilder

The port for the AppBuilder service to listen on: 8080

The instance of ZooKeeper defined by the server and port number: localhost:2181

The current namespace to use, default is I entered development, as shown in the following screenshot:

Figure 4.125: The appbuilder-config.exe program prompts for the parameters for the service

Figure 4.126: The Windows service, appbuilder-service, is installed in a Stopped status The services can be viewed by reloading the Windows Task as shown in the preceding screenshot. If you have Windows Task Manager program open during any of the aforementioned service config.exe program runs (for example, you have to restart the Windows Task Manager to see the new service in the Services tab list.

Figure 4.127: The Windows services required for IBM Watson Explorer 12.0.3.0 components All the Windows services are now running, as shown in the preceding screenshot. Next, we need to configure the IBM Watson Explorer 12.0.3.0 embedded IBM Liberty web server, using the embedded-webserverconfig.exe program:

Figure 4.128: The embedded-webserver-config.exe first prompts for the language to be entered The parameters following are prompted (some can be defaulted). The parameters to be entered are as follows: The language to be used by the configuration tool for prompts default: en The virtual directory for the embedded webserver default: vivisimo If debugging mode is required for the embedded webserver, choose from y or N (I selected

The hostname server that should be used (default is the current installation server): MSI The port that the embedded webserver will listen on: 9080 The registered background service name of the embedded webserver: EngineWebServer The user that the embedded webserver will run its worker services as: Administrator

Figure 4.129: The parameters prompted for the embedded webserver The program then prompts you to enter y for Yes or N for No to enable the web server process. The above response then triggers the creation of the embedded-webserver-config.json file:

Figure 4.130: The location of the embedded-webserver-config.json file The embedded webserver is started using the program command: embedded-webserver-config.exe start

Figure 4.131: The embedded-webserver.exe start program command is run to start the web application server At this point, you can run the engine-status.exe program to check the URL to use:

Figure 4.132: The URL to use is displayed using engine-status.exe This gives the following: http://MSI:9080/vivisimo/cgi-bin/admin.exe on my system, and then loads as follows:

Figure 4.133: The login is displayed on using the URL http://MSI:9080/vivisimo/cgi-bin/admin.exe

4.13.9.3: Default login credentials

The default login credentials are as follows: data-explorer-admin

TH1nk1710

The user and password are entered to log into the administrator console. The administrator console is displayed, as shown in the following screenshot:

Figure 4.134: The Administrator console is displayed as expected

To stop the command

embedded-webserver.exe stop is executed, as shown in the following screenshot:

Figure 4.135: The command used to stop the embedded EngineWebServer service

If you need to stop the services in the future, stop Application Builder first, and ZooKeeper last.

In Windows Task tab, select right-mouse click and stop the

Figure 4.136: The appbuilder-service is stopped first using Windows Task Manager

Repeat for the other services, as in the following

Remember to stop the ZooKeeper service last!

last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last! last!

Table 4.4: The windows services and names of IBM Watson services

4.14: IBM Watson Explorer oneWEX 12.x Docker Container

The following URL is the main support page for IBM Watson Explorer oneWEX 12.x:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/explorer_onewex.html

From this, the following URL can be derived to show the release notes:

https://www.ibm.com/support/pages/node/618667

This shows that the latest version is oneWEX 12.0.3.5, and it states the following:

You can install Watson Explorer oneWEX for single container deployment Version 12.0.3.5 directly, without installing an earlier version of Watson Explorer oneWEX for single container deployment.

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/c_onewex_install_docker.html To start the graphical installation program, run the install.exe program, see Section 4.14.9 of this chapter for the installation and

configuration procedure on Windows 10, Home Edition, Build 2004.

See the following:

8/27/2020 2020-08: Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004 for x64 (KB4569745)

8/27/2020 2020-06: Security Update for Adobe Flash Player for Windows 10 Version 2004 for x64-based Systems (KB4561600) 8/27/2020: Feature update to Windows 10, version 2004

The readme.txt file downloaded just has the URL to the current IBM Knowledge Centre information:

http://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0

4.14.1: Compatibility issues and support limitations for the products listed in Chapter 1 The prerequisite Docker installation uses WS2 Linux containers for the Microsoft Windows installation.

To download the Fix Pack 12.0.3.4, browse to IBM Fix Central website at the URL:

https://www.ibm.com/support/fixcentral/ This shows the page displayed, as shown in the following screenshot:

Figure 4.137: The search parameters required in Fix Central for listing oneWEX Fix Packs

The Continue command button displays the next browser page for selecting the type of fixes required:

Figure 4.138: The default Browse for Fixes

The Continue command is clicked to show the available Fix Packs and interim fixes for the JREs, and the main Fix Pack sections. Scroll down through the Fix Pack sections and select the following:

Figure 4.139: The Fix Pack 12.0.3.4 for the Windows version of oneWEX can be selected See the following link:

https://www.ibm.com/support/pages/node/6244508 The preceding URL is in a pop-up window on clicking on the Readme link in the preceding screenshot.

Figure 4.140: Click on the Continue command button

Scroll down and select then select Download options (the Download using Download Director option was selected):

Figure 4.141: The Fix Central Download option can be selected from FTPS/SFTP, HTTPS or Download Director

After selecting the download option, Download using Download Director radio button option, if you want to include the fixes related to supporting IBM component fixes tick the checkbox, Include prerequisites and co-requisite fixes, then click

Figure 4.142: The Tick box shows related fixes for supporting IBM product software

IBM Watson Explore oneWEX Docker container 12.0.3.4 for Windows is downloaded as a .zip file, 12.0.3.4-WS-WatsonExplorerDAEoneWEX-Windows-FP004.zip containing the one-wex-installer, Windows installer.

The download, license agreement is reviewed; then click on I

Figure 4.143: Click on I agree after reviewing the license

The Fix Pack section can be seen by scrolling down, and then ticking on the box, as shown in the following screenshot:

Figure 4.144: The links relate to the following URLs

https://www.ibm.com/support/pages/node/6244508 Release notes

https://www.ibm.com/support/pages/node/618667 Security bulletin 1

https://www.ibm.com/support/pages/node/6250345

Security bulletin 2 https://www.ibm.com/support/pages/node/6250347

Security bulletin 3 https://www.ibm.com/support/pages/node/6250343

Figure 4.145: The Download now command button is selected

Click on the Download now button to start the Fix Pack download. This shows the following pop-up window, to load Download Director Java-based program, click Open IBM Download as shown in the following screenshot:

Figure 4.146: The IBM Download Director can be selected to start the launch

The IBM Download Director Java program has to be started by clicking the Run button on the following launched application:

Figure 4.147: Click on the Run command button to start

The status of the downloading Fix Pack is shown in the pop-up window, as follows:

Figure 4.148: The Details button shows the list of files to be downloaded for the Fix Pack The Details command button is clicked to open the following window to give the status of each file in progress of download:

Figure 4.149: The details of the downloading Fix Pack files are displayed The size, date and download status is shown in the following screenshot for each file to be downloaded.

Figure 4.150: The download status shows 100%, so it is complete

4.14.2: Server(s) required for the installations

The Docker Container installation for IBM Watson Explorer oneWEX 12.0.3.4 requires 538,533,232 Bytes (0.5385 GB) of disk space, just for the installation.

The supporting Windows Docker Desktop 2.3.0.4 (Community Edition) system (Docker service version requires Windows 10 Home Build version 19018 or above. Sections 4.2 through 4.7, Installing Docker describes the full installation procedure for the Docker system on Windows 10, Home Edition.

This version of Docker has a back-end service version, which can be verified using docker version from a Windows Command Prompt:

Figure 4.151: The docker version command is used to verify the version used

The feature upgrade of Windows to Build version 2004 (which satisfies the Docker install checks) also requires around 7 GB free disk space on the O/S disk (the C:\ drive usually).

The Windows WSL2 Linux kernel features of the Windows system (the Windows subsystem for Linux) must also be enabled for Docker Desktop. See the following link:

https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

4.14.3: Memory and disk storage requirements and CPU cores required The installation of oneWEX needs 4 CPUs and at least 8.5 GB of RAM for the virtual machine, from the IBM recommendations.

The Fix Pack also requires around 5 GB of disk space.

I discovered in practice, with Windows, the Windows Linux 2 subsystem, required for Docker and the two Docker Containers required for IBM Watson Explorer 12.0.3.4 oneWEX, that it was consuming 15 GB of the 16 GB of memory on my system, just running with no data processing load. Also, the 4-core CPU I have, was running at 40%.

The full CPU specification I used is as follows:

follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows: follows:

I therefore recommend at least 32 GB of memory and an 8 Core CPU running at least at 2.6 GHz.

4.14.4: Folder structures and User security

The Docker image build adds containers, where all the files and directories that are added to the build context will have permissions of -rwxr-xr-x (Linux: chmod Docker recommend checking and resetting permissions for sensitive files and directories on the Windows environment on the C:\ drive for limited security access.

For IBM Watson oneWEX LDAP configuration, the uploaded xml file MUST be called otherwise the configuration won’t be applied.

The following URL describes the procedure to load users in detail. See the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_ee_adm_ldap_config.html

4.14.5: Firewall – Windows Defender configuration

The ports required are translated from internal Docker Container port numbers, 443 is translated to 60443 and the service uses ports 9080 and

4.14.6: Supporting Java jdbc jar files and PATH environment set-up

The Docker Container oneWEX 12.0.3.4 install includes IBM Java to 8.0.6.10, and includes the latest Product Security Incident Response Team fixes.

4.14.7: Windows hosts file configuration for server network access

The installation I completed was self-contained on a single machine.

The Docker installation added the following to the Windows hosts file

# Added by Docker Desktop 192.168.1.66 host.docker.internal 192.168.1.66 gateway.docker.internal # To allow the same kube context to work on the host and the container: 127.0.0.1 kubernetes.docker.internal # End of section

4.14.8: Stopping the running of Windows services for install upgrades The Docker service starts automatically on reboot of the Windows host machine. This has to be running for the installation of oneWEX to proceed (see the following Section

4.14.9: Installation and configuration of IBM Watson Explorer oneWEX 12.x on Windows Docker Container

Figure 4.152: The 7-Zip utility program is used to unpack the Fix Pack zip file Extract the downloaded

Now double click on the extracted install.exe program.

You will be prompted by Windows to allow this to Run as

Figure 4.153: The InstallAnywhere status bar shows the progress of the installation

If you get the following pop-up window at this point in the installation, then the Docker service will need to be started. This should automatically start on a reboot of the system, but can be manually be started with a batch job:

Figure 4.154: The Docker service was found to be required running for the installation

The following screen is shown if the Docker service is running:

Figure 4.155: The Language can be selected, and then click OK Select the language and click

Figure 4.156: The two license texts should be reviewed, and then click I accept radio button Click Read Non-IBM

Figure 4.157: The Installation location is selected

In figure you can select the Windows drive letter and path required to install the oneWEX system.

Figure 4.158: Enter the Windows administrator’s password in the prompted text box In the preceding screenshot, the password required is for the Windows admin user.

Figure 4.159: The Disk space sizes are displayed. Click Install to start the installation

The screen shown in the preceding screenshot shows the available space on the chosen drive and the required space to install the oneWEX container system.

Figure 4.160: The status of the installation is displayed together with some advertising! The status bar shows the installation progress and the text above this bar shows what is being installed or configured. The uses that can be made of IBM Watson Explorer are also displayed during the installation.

Figure 4.161: The Install completed successfully and shows the screen Click Done and check the log:

C:\IBM\WEX\Install\Watson_Explorer_Deep_Analytics_Edition_Install_ 08_28_2020_14_29_04.log

Figure 4.162: Scrolling down the log shows the Summary of the Install. There should be no errors

Watson Explorer Admin Console and Watson Explorer Content Miner can be launched from the graphical user interface with the following command:

C:\IBM\wex\bin\IBM Watson Explorer.exe.

Figure 4.163: The main Administration launch window is shown after launch using IBM Watson Explorer.exe You can also restart the Watson Explorer oneWEX docker container from the command line with the following command:

C:\IBM\wex\bin/wexdocker.bat

Watson Explorer oneWEX can then be invoked in a web browser using the following URL: https://MSI:/miner/ for Watson Explorer Content Miner

and https://MSI:/admin/ for Watson Explorer Admin Console,

where MSI is the server name (I used localhost). https://MSI:60443/admin

Clicking on the relevant launch icon in figure 4.163 launches the web browser with the correct URLs.

The Watson configuration parameters can be modified in the wex.json file: {

"env" : { "SOLR_MAX_HEAP" : "4g", "DOCPROC_WORKER_NUM" : "2", "SOLR_PER_NODE" : "1", "DOCPROC_MAX_MEMORY" : "2g", "WKSML_HOST" : "wksml-service", "ZK_MAX_HEAPSIZE" : "1g", "ZK_MIN_HEAPSIZE" : "512m", "WLP_JVM_MAX_MEMORY" : "1g" }, "port" : 8443, "name" : "wex12dae", "wexDataVolume" : "wex12dae", "dockerImage" : "ibm-wex-ee:12.0.3.2116", "wksmlImage" : "ibm-wex-wksml:12.0.3.2116", "wexCPULimit" : 0.0, "wksmlCPULimit" : 0.0, "wksmlContainerName" : "wksml-service", "restart" : "unless-stopped" }

Using the Windows Command Prompt:

Figure 4.164: Running docker ps from the command window shows the two installed containers for IBM Watson Explorer oneWEX

For custom Watson convertors See the following URL: https://github.com/Watson-Explorer/onewex-custom-converters

This content is covered by the Apache 2.0 license.

See the following link: http://www.apache.org/licenses/LICENSE-2.0

4.15: Use of Compatibility Matrix URLs

IBM has the following URL to run the Compatibility Matrix reports. The following steps can be followed to retrieve the reports for a selected IBM Software package. In this chapter, we are interested in the Compatibility Matrices for IBM Watson Explorer products and IBM Stored IQ for Legal (VM) 2.0.3.7 to identify the prerequisites for Red Hat OpenShift installation that we require.

See Chapter 2, Component Software Compatibility for the full stepby-step procedure to obtain the target URL for the Compatibility Matrix:

For IBM Watson versions, first check the Release Notes:

Release Notes - IBM Watson Explorer Foundational Components, Version

https://www.ibm.com/support/pages/release-notes-ibm-watsonexplorer-foundational-components-version-120#inst12034

These state: Red Hat Enterprise Linux versions 6 are not supported in Version 12.0.3.3 or later. Compatibility reports can be procured for IBM Software products at the following link:

https://www.ibm.com/support/pages/software-product-compatibilityreports

From the preceding link, you will be able to enter the name of the product to list the Compatibility Matrix link. For OpenShift, there is a link derived from the preceding URL:

https://www.ibm.com/support/pages/node/880807

This shows that the IBM Watson oneWEX container is supported indirectly on OpenShift through the IBM Cloud Private 3.2 version running on the Red Hat OpenShift system, as highlighted in the following product code tables (product code

Figure 4.165: The product code part numbers for IBM Watson Explorer oneWEX for ICP This link, in Step expands to the URL as follows:

https://www.ibm.com/software/reports/compatibility/clarity/index.html

To target the required compatibility report, select the search box and enter the string IBM Watson Then select Watson Explorer Deep Analytics Edition and then you can select version 12.0.3.0 base edition from the Version drop-down, or if you install from

the Fix Packs, click on the Show fix packs checkbox first, and (currently at August 2020) this shows version Clicking the Submit command button will then render a report, which will show a number of tabs for selection.

The first tab is called Operating Systems (providing you selected [ticked] an operating system in your search, such as If you scroll down on this tab, you will see a list of the recommended prerequisite libraries required for installation, currently for 12.0.3.4 these are as follows: For RHEL 7 Note 1 Supported for both oneWEX for ICP and oneWEX for single container deployment. oneWEX for single container deployment does not support high availability and scale-out by adding additional containers. Note 2 states: The following 32-bit libraries are required on Linux x86-64 systems:

- libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit) - libstdc++ (libstdc++.i686 / libstdc++6-32bit) - zlib (zlib.i686 / libz1-32bit / zlib-32bit)

-

libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit) libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit)

- libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit) and:

If you want to support the ability to generate thumbnails for certain types of documents in the search results, you must install the following libraries: - libXm - libXt - bzip2-libs (both 32-bit and 64-bit)

With the following Support of Watson Explorer Analytical Components with Watson Knowledge Studio Annotator Support is available on RHEL 7.0, or later Fix Packs only. Note 4

When you use Annotation Administration Console the following 32bit libraries are required on Linux x86-64 systems: - libstdc++33 (compat-libstdc++-33.i686 / libstdc++33-32bit)

- libstdc++ (libstdc++.i686 / libstdc++6-32bit) - zlib (zlib.i686 / libz1-32bit / zlib-32bit) - libXext (libXext.i686 / libXext6-32bit / xorg-x11-libXext-32bit) -

libXft (libXft.i686 / libXft2-32bit / xorg-x11-libs-32bit) libXi (libXi.i686 / libXi6-32bit / xorg-x11-libs-32bit) libXp (libXp.i686 / libXp6-32bit / xorg-x11-libXp-32bit) libXtst (libXtst.i686 / libXtst6-32bit / xorg-x11-libs-32bit)

compat-libstdc++-33 package will be found in the optional packaging repository. You may need to configure the repository properly

4.16: Use of Red Hat Linux upgrades

For Red Hat Linux RHEL 8.x, the Subscription Manager can be used together with the yum installer to upgrade packages.

Chapter 1, Getting Started with IBM Resources for shows the main location for download of RHEL 8.0, and the versions available for supporting a production system. IBM StoredIQ can be downloaded as a VMware compatible .ova file. This includes its own CentOS 7 operating system for direct loading to VMware, including VMware Workstation Pro 15.5, so it does not have so many issues of compatibility, but does still require supporting Windows Hypervisor and VMware VM (virtual server) host version recommendations for a production environment. So, for example, in this instance, the supported VM for production is supported with VMware vSphere 6.5 from StoredIQ for Legal (VM) version 2.0.3.9 onwards.

4.17: RedHat OpenShift 4.x download and installation

The OpenShift system provided by Red Hat supplies a container management wrapper, which forms a logical layer above the Kubernetes system used for the direct container management.

4.17.1: Configuring the firewall

The following URL provides the OpenShift 4.5 procedure for adding the necessary ports to the firewall service across the server clusters required by OpenShift.

See the following link:

https://access.redhat.com/documentation/enus/openshift_container_platform/4.5/htmlsingle/installing/index#configuring-firewall

4.17.1.1: Installation Downloads

The following URL is the first browser page entry-point you have, to generate the required subscriptions on Red Hat to allow you to create a download for the bare-metal installation of OpenShift 4.5, so that you can create an on-premise Red Hat OpenShift 4.5 cluster.

https://cloud.redhat.com/openshift The Create cluster link and download procedure screens are shown in Chapter 1, Getting started with IBM Resources for Section 1.3.3.2 Installation Downloads for RedHat OpenShift

We have to follow the specific procedure as documented by Red Hat, step by step, as any deviation from the very specific steps described will cause the installation to fail!

So, in the preceding step, we select the operating system from the drop-down, and we will also need to download a text file which contains a long unique key which is required to complete the installation. We select Linux from the two available installation platforms for a bare-metal installation.

The openshift-install-linux.tar.gz file is downloaded and saved. Remember that this is just the installation utility program, which is run on the master node server after you have configured the basic set of servers in the cluster to at least the minimum specifications required (see the details for these later in this chapter).

Next, we must download the pull which is manifested by a text file, which contains a key to allow the installation utility program to pull down the full Red Hat OpenShift 4.5 installation system onto the pre-created server cluster.

After clicking on Download pull you will almost immediately be prompted for a folder to save it to, since the text file with the key is very small. The pull-secret.txt file is saved for use during the installation procedure. In OpenShift Container Platform version 4.5, you can install a cluster on bare metal infrastructure that you provision. See the following link: https://docs.openshift.com/containerplatform/4.5/installing/installing_bare_metal/installing-baremetal.html#creating-machines-bare-metal

4.17.1.2: Prerequisites

See the following link: https://docs.openshift.com/containerplatform/4.5/architecture/architecture-installation.html#architectureinstallation

Figure 4.166: The architecture overview for the OpenShift 4.5 installation

The architecture overview of the targets and dependencies is shown in the preceding screenshot.

4.17.1.3: Overview

Every control plane server in an OpenShift Container Platform 4.5 cluster must use which includes a critical first-boot provisioning tool called Ignition. This tool enables the cluster to configure the servers. Operating system updates are delivered as an atomic OSTree repository that is embedded in a container image that is rolled out across the cluster by an operator. Actual operating system changes are made in-place on each server as an atomic operation by using Together, these technologies enable OpenShift Container Platform to manage the operating system, like it manages any other application on the cluster, through in-place upgrades that keep the entire platform up-to-date. These in-place updates can reduce the burden on operations teams.

If you use RHCOS as the operating system for all cluster servers, the cluster manages all aspects of its components and servers, including the operating system. Because of this, only the installation program and the Machine Config Operator can change servers. The installation program uses Ignition configuration files to set the exact state of each and the Machine Config Operator completes more changes to the servers, such as the application of new certificates or keys, after installation.

4.17.2: Internet and telemetry access requirement

In OpenShift Container Platform 4.5, you require access to the internet to install your cluster. The Telemetry service, which runs by default to provide metrics about cluster health and the success of updates, also requires internet access. If your cluster is connected to the internet, Telemetry runs automatically, and your cluster is registered to the OpenShift Cluster Manager

See the following link: https://cloud.redhat.com/openshift

Once you confirm that your Red Hat OCM inventory is correct, either maintained automatically by telemetry or manually using OCM, use subscription watch to track your OpenShift Container Platform subscriptions at the account or multi-cluster level.

You must have internet access to:

Access the Red Hat OpenShift Cluster Manager page to download the installation program and perform subscription management. If the cluster has internet access and you do not disable telemetry, that service automatically entitles your cluster:

https://cloud.redhat.com/openshift

Access Quay.io to obtain the packages that are required to install your cluster.

Obtain the packages that are required to perform cluster updates.

If your cluster cannot have direct internet access, you can perform a restricted network installation on some types of infrastructure that you provision. During that process, you download the content that is required and use it to populate a mirror registry with the packages, which you need to install a cluster, and generate the installation program. With some installation types, the environment that you install your cluster in will not require internet access. Before you update the cluster, you update the content of the mirror registry.

4.17.3: Server requirements for a cluster

The following section covers the prerequisites for the cluster of servers you have to prepare before installing Red Hat OpenShift 4.5.

For a cluster that contains user-provisioned infrastructure, you must deploy all of the required servers first.

4.17.4: Network connectivity requirements

All the Red Hat Enterprise Linux CoreOS servers require network in initramfs during boot to fetch Ignition configuration files from the Machine Config Server. During the initial boot, the servers require either a DHCP server or static IP addresses be set in order to establish a network connection to download their Ignition configuration files.

4.17.4.1: Required servers

The smallest OpenShift Container Platform clusters require the following hosts:

One temporary bootstrap server

Three control plane, or master, servers At least two compute servers, which are also known as worker servers

The cluster requires the bootstrap server to deploy the OpenShift Container Platform cluster on the three control plane servers. You can remove the bootstrap server after you install the cluster.

For a cluster that contains user-provisioned infrastructure, you must deploy all of the required servers.

To maintain high availability of your cluster, use separate physical hosts for these cluster servers. The bootstrap, control plane, and compute servers must use the Red Hat Enterprise Linux CoreOS as the operating system.

Note that RHCOS is based on Red Hat Enterprise Linux 8 and inherits all of its hardware certifications and requirements. See Red

Hat Enterprise Linux technology capabilities and limits.

See the following link:

https://docs.openshift.com/containerplatform/4.5/installing/installing_bare_metal/installing-baremetal.html#creating-machines-bare-metal

The detailed requirements for an installation are covered in the blog: https://www.openshift.com/blog/openshift-4-bare-metal-installquickstart

and Section 4.17, Red Hat OpenShift 4.x Download and

Conclusion

In this chapter, we covered the installation of the Docker Container system, which is used in Sections 4.9, and and described the use and function of the main docker commands. We introduced the chapter by creating a new Docker account, and then showed how we could us this to install Docker on Linux RHEL 8.0 and on the Windows 10 Home Edition operating systems. We covered the creation of a Docker Compose file to enable the build and run of a new container app and we described the use of a number of Docker commands.

This chapter covered the procedures to follow, to install, and initially configure:

IBM Watson Explorer Foundational Components 12.x for Windows 10

IBM Watson Explorer oneWEX 12.x Docker Container for Windows 10

IBM StoredIQ for Legal (VM). RedHat OpenShift 4.5 installer program and RHCOS installation binaries and the supporting pull secret file download

It also described the prerequisites required for the provision and networking for the cluster servers, which are necessary for a bare metal install of the Red Hat OpenShift 4.5 system.

The next Chapter 5, IBM Fix covers Fix Packs required for the following products:

IBM Watson Explorer oneWEX 12.x Docker Container

IBM Watson Explorer Foundational Components 12.x IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

The following points should be noted.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software shared object library prerequisites.

Docker is introducing a container image retention policy for inactive images which will be enforced starting November 1, 2020. The container inactive image retention policy will apply to the following plans: Free plans will have a 6-month inactive image retention limit

Pro and Team plans will have unlimited image retention

An inactive image is a container image that has not been either pushed or pulled from the Docker Hub image repository in 6 or more months.

Docker Desktop requires the installation of the Microsoft Windows Linux sub-system, WSL2.

Docker Desktop also requires that the Windows 10 Home Edition operating system must be at version 19018 or greater.

Windows 10 Home Edition is available from Microsoft as a free upgrade for existing users of Windows 7 or Windows 8.1

The VMware Workstation support for RHEL 8.0 (or CentOS 8.0) only starts with VMware Workstation Pro version 15.1.0, so this needs to be installed as an upgrade (or a new installation) first!

To login as you have to select and click on the Not listed? option in the initial Linux start-up screen.

Red Hat Subscription Manager must be used initially to register your installed RHEL 8.0 system, for which you must have set up a Red Hat Developer account (free at the time of writing!).

Check and compare the SHA fingerprint with what you expected (see the download site for the expected GPG keys) when you were installing yum packages. For IBM Watson oneWEX LDAP configuration, the uploaded XML file MUST be called otherwise the configuration won’t be applied! The Docker Desktop support for oneWEX requires a minimum installation of Windows version 19018. For IBM Watson oneWEX LDAP configuration, the uploaded XML file MUST be called otherwise the configuration won’t be applied!

See the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_ee_adm_ldap_config.html The Windows system for IBM Watson oneWEX should have at least 8.5 GB free memory and must have 4 CPU cores available. (But for a working system, I recommend 32 GB and 8 cores.)

RHCOS is based on RHEL 8 and inherits all of its hardware certifications and requirements. Use the image versions that match the OpenShift Container Platform version if they are available. Only use ISO images for this procedure. The version of RHCOS supported must be equal to or less than the OpenShift version installed.

OpenShift Container Platform requires all nodes to have internet access to pull images for platform containers and provide telemetry data to Red Hat load balancers.

Before you install the OpenShift Container Platform, you must provision two layer-4 load balancers. The install of the OpenShift CLI is completed in order to interact with OpenShift Container Platform from a command-line interface. oc can be installed on Linux, Windows, or macOS.

Multiple Choice Questions

For which system is a DNS server prerequisite required? Red Hat Enterprise Linux 8.0 servers

CentOS Linux 8.0 servers

IBM Cloud private server clusters Red Hat RHEL 8.0 and CentOS 8.0 servers

It isn’t required as a prerequisite.

What is the yum command used for?

Installation of IBM StoredIQ for Legal on Red Hat

Update of Microsoft Windows Servers

Configuration of Red Hat Linux network cards Installation of Linux Software Library packages on Red Hat and CentOS servers

Ordering a takeaway

What is the program ./ibmwatsonexplorer used for?

Setting up shared folder mount points for IBM Watson explorer Foundational Components

Setting up shared folder mount points for IBM oneWEX

Viewing analysis results of the File Crawler

Checking who is logged into the system What is the Korn shell a prerequisite for?

IBM Watson oneWEX Watson Explorer 12.0.3.4 IBM Security Directory Services 6.4

Red Hat Linux RHEL 8.0 Operating system IBM Cloud Private version 3.2 Making popcorn

What command is used to change the server name on Linux systems?

hostnamectl

subscription-manager systemctl

rename What are the minimum number of CPU cores required as a prerequisite for installation of IBM Watson oneWEX containers?

2 CPU cores 4 CPU cores

8 CPU cores 16 CPU cores

It isn’t required as a prerequisite. What is the minimum version of Windows 10, Home Edition required to install Desktop Docker CE version 2.3.0.4? Version 2004

Version 19018

Version 19000 You can’t install Desktop Docker on Windows 10, Home edition What is the program C:\IBM\wex\bin\IBM Watson Explorer.exe used for?

Setting up shared folder mount points for IBM Watson explorer Foundational Components Setting up shared folder mount points for IBM oneWEX Viewing analysis results of the File Crawler Checking who is logged into the system

What is the Windows WSL 2 a prerequisite for? IBM Watson Foundational Components 12.0.3.4 IBM Security Directory Services 6.4

Docker Desktop 2.3.0.4 (Community Edition)

Windows 10 Home Edition version 19018

What installation changes the Windows hosts file content? IBM Watson Foundational Components 12.0.3.4 installation The Docker installation The Windows 10 Home Edition Version 2004 upgrade

The Windows host file content is not changed What are the minimum number of CPU cores required for the Bootstrap server as a prerequisite for installation of Red Hat OpenShift 4.5?

2 CPU cores 4 CPU cores c) CPU cores 16 CPU cores It isn’t required as a prerequisite

What version of RHCOS is supplied for use with Red Hat OpenShift 4.5? Version 6.0

Version 7.0 Version 8.0 You can’t install RHCOS for use with Red Hat OpenShift 4.5 What is the openshift-install-linux.tar.gz file used for?

Installing the RHCOS core Linux Operating System Installing the HAProxy Load Balancer system Installing the OpenShift 4.5 system Checking who is logged into the system

What does the OpenShift 4.5 installation program use to set the exact state of each server?

The startup program

The fireup program The Ignition program

The installation program sets the exact state itself

What must you do so that the installation program generated certificates don’t affect the use of the system? Keep the system running for 12 hours

Keep the system running for 24 hours Keep the system running for 48 hours

Keep the system running for 24 minutes

Docker is a container management system, which only runs on: A Linux environment on Red Hat Enterprise Linux

A WSL 2 environment on Windows 10 Home Edition Both native Windows and native Linux operating systems

A WSL2 environment on Windows systems and on native Linux systems

To run a docker pull command: You always have to log into Docker to pull container images

You have to log into Docker just for the open-source LDAP container You have to log into Docker for the IBM DB2 development containers

You never have to log into Docker to pull containers

The docker exec -it command: Pulls containers from the Docker Hub

Shows the status of a list of Docker Containers in memory

Runs a command from within the container to a tty terminal for I/O from the container process which is selected

Builds a new Docker container The Docker CE, used for loading the IBM DB2 container image is supported for:

Development and production systems

Only production systems Only development systems

Neither development, nor production systems

Multiple Choice Answers

c. IBM Cloud private server clusters d. Installation of Linux Software Library packages on Red Hat and CentOS servers

a. Setting up shared folder mount points for IBM Watson explorer b. IBM Security Directory Services 6.4

a. hostnamectl

b. 4 CPU cores

b. Version 19018

a. Setting up shared folder mount points for IBM Watson explorer Foundational Components

c. Docker Desktop 2.3.0.4 (Community Edition) b. The Docker installation

b. 4 CPU cores

c. Version 8.0

c. Installing the OpenShift 4.5 system

c. The Ignition program

b. Keep the system running for 24 hours

d. A WSL2 environment on Windows systems and on native Linux systems

c. You have to log into Docker for the IBM DB2 development containers

c. Runs a command from within the container to a tty terminal for I/O from the container process which is selected.

c. Only development systems

Questions

What is the essential configuration step for loading the installer for IBM Security Directory services to create the default instance?

What type of file are the components of the Watson Explorer Foundational Components 12.0.3.0?

How can you enable more repositories for your Red Hat RHEL or CentOS Linux installation? (There are two methods for this.)

Name three installer commands (besides that can be used in a Red Hat or CentOS Linux system.

What is the package called that is required to support the DNS server named service installation?

What software component is used to download the IBM Cloud Private containers?

What documentation would you review first before starting the IBM Watson Explorer oneWEX 12.0.3.4 installation? Where would you look for the IBM Watson Explorer oneWEX 12.0.3.4 installation file?

What service must be running before the IBM Watson Explorer oneWEX system can be installed?

What is the Desktop Docker system used for?

Is a Java component required for IBM Watson Explorer Foundational Components 12.0.3.4?

What other software component is required, apart from the IBM JDK for IBM Watson Explorer Foundational Components 12.0.3.4?

What main function does the Red Hat OpenShift 4.5 cluster system provide? What operating systems are supported for a bare metal installation of the Red Hat OpenShift 4.5 cluster? What are the main prerequisites, which are required before the Red Hat OpenShift 4.5 system can be installed? What is Kubernetes used for? What is the install-config.yaml file used for?

Why do you have to configure ports for the FireWallD service? What two software/operating system component prerequisites would you need before installing the docker system on a Windows

environment?

What online user account do you need before you start installing Docker?

What procedures would you use to check for a potential solution to resolve an issue raised by a user of your IBM Watson Explorer installation to correct a software problem they raised? What Linux command line commands could you use to show that the Docker Container system is running?

Key terms

DHCP: Dynamic Host Configuration Protocol is a network management protocol used to automate the process of configuring devices on IP networks. This means that the IP address of a network card set for DHCP is provided by a DHCP server. In this case, the user cannot provide a manual IP address.

DNS: Domain Name Server sudo Some guides state this means superuser do, and others that it stands for switch user do or substitute user do but essentially, it gives an ordinary Linux user root command privilege (but can give the user the privilege of another specific Linux user).

I have always used the root user to login, in my examples in this chapter, but on most production, installation sites, you will never get root login access, but be given access to use so I have included this, so that when you see a command like

yum repolist

for example, you should know that you should be able to use sudo yum repolist

The following Linux commands all relate to adding or displaying users and groups:

Add a Linux security group:

groupadd groupname

Add a user name with a group name of idsldap and with a default home directory of /home/idsldap means, create it if it doesn’t exist) using the Korn shell as a default command shell useradd -g idsldap -d /home/idsldap -m -s /bin/ksh idsldap

Set the ldsldap user password: passwd idsldap

Modify the ldsldap as a group ID for the root user usermod -a -G idsldap root List the groups belonging to the root user:

groups root WSL 2: Windows subsystem for Linux release 2, used by Docker Desktop and the Docker service.

Apache An open source Java program used to compile, assemble, test, and run Java applications. Java The software development kit for Java consisting of the Java compiler and Java program to run compiled jar files, plus an extensive library of precompiled utility modules used by Java programs for I/O and language and mathematical functions. Docker: The container management system, which builds and encapsulates a complete independent software installation application container containing all the dependent systems the container application needs, which can be embedded in a host operating system that the docker then manages access msi Windows installer files used to install programs.

(Specifically for this chapter, for installing the component programs used by IBM Watson Explore Foundational Components 12.0.3.4.)

MITM CA certificate

Mitmproxy Certificate Authority certificate. The CA certificate utility instructions can be viewed using: https://docs.mitmproxy.org/stable/concepts-certificates/

The mitmproxy CA cert is generated on the first start of mitmproxy and is located in ~/.mitmproxy MITM Proxy mitmproxy is a free and open source interactive HTTPS. It allows intercepting HTTP and HTTPS connections between any HTTP(S) client (Man In The Middle). Lights Out Management interface is for remote access management of a server RHCOS: Red Hat Enterprise Linux CoreOS created by Red Hat specifically for use as a single-purpose container operating system, that is, for Red Hat OpenShift. ISO A binary file which can be used to emulate a CD or DVD disk format. PXE or iPXE booting: The Preboot Execution Environment is an industry standard client/server interface which can be used remotely by an administrator over a network for an initial boot for computers that are not yet configured with an operating system. iPXE is an updated version of the PXE system, which can use HTTP protocol for improved network performance (which is not used by PXE). The open-source version of Red Hat RHEL 7. Dandified yum is the next-generation version of the Linux yum installer, which was named based on Yellowdog So, DNF could be expanded to Dandified Yellowdog Updater, Modified!

Community Edition. This CE abbreviation appears appended to many software packages and the Community part usually indicates an Open-Source edition, that is, Free! Hence Docker CE, Community Enterprise Operating System IBM Cloud Private CE (Community Edition), which we will cover in-depth in Chapter 10, IBM Cloud Private Cluster on CentOS Is a Linux software teletype terminal emulation for standard I/O, so it allows you to interact with the system by typing characters into it, and displays the characters output by the system. It originated from the teletype hardware, originally used by very early operating systems, which you will probably only have used if you have been in IT for over 40 years. (I have one in my garage, carefully guarded from museums and my wife’s attempts to scrap it!)

CHAPTER 5 IBM Fix Packs

Introduction

This chapter covers Fix Packs required for the following products: IBM Watson Explorer oneWEX 12.x Docker Container

IBM Watson Explorer Foundational Components 12.x

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation The main IBM Fix Pack location to search is called Fix Central, and it has the following URL:

https://www.ibm.com/support/fixcentral/

Structure

In this chapter, we will discuss the following topics: IBM Watson Explorer oneWEX 12.x Docker Container

Fix Pack Product searching procedures

Downloading the Fix Pack components for Linux and Windows for correct upgrades

Fix Pack lists - identifying which fixes are cumulative

IBM Download Director installation and use for Fix Packs

License restrictions

Red Hat Linux maintenance using subscription manager

IBM Watson Explorer Foundational Components 12.x Fix Pack Product searching procedures

Downloading the Fix Pack components for Linux for correct upgrades

Fix Pack lists - identifying which fixes are cumulative

License restrictions

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

Fix Pack Product searching procedures

Downloading the Fix Pack components for Linux for correct upgrades

Fix Pack lists - identifying which fixes are cumulative IBM Download Director installation and use for Fix Packs

License restrictions

Objectives

After studying this unit, you should be able to: Identify the prerequisite Fix Packs required for each of the system components, which will be required to support the upgrade of IBM Watson and StoredIQ software base installation versions targeted for installation. Understand the reasons for upgrading to the latest supported Fix Pack releases, and be able to identify the Fix Packs, which provide cumulative fixes for the target software components to be installed and know how to download them.

Search, identify, and download the latest Fix Packs and configure the intermediate Fix Pack plug-ins and security related interim fixes required to maintain a secure and robust system.

5.1: IBM Watson Explorer oneWEX 12.x Docker Container

The assumption, in this chapter, for IBM Watson Explorer oneWEX is that the base install is set at version 12.0.3.0. The following procedure is used to search and select the correct/latest Fix Pack to upgrade to (available, at the time of writing, September 2020).

Whenever an installation of IBM software is completed from the IBM Software Catalog, it is always recommended to search for the latest compatible Fix Pack and any intermediate Fix Packs, to ensure the completed installation is optimally installed with any software issues and all possible security fixes, in the base system, resolved as far as possible.

5.1.1: Fix Pack product searching procedures

As is usual, we start from the following URL: https://www.ibm.com/support/fixcentral/

Further details of this section can be found in Chapter 2, IBM Component Software Compatibility Section 2.1, Fix Pack location and versions, pages 7 to The wcm connector is for IBM Web Content Manager/P V8.5. The URL for install information is available at: https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.connector.wcm-portal-server.doc/c_wcm-portalserver-connector-doc.html

The Details: Download Director command window shows the size, download date and the name of the file(s) selected for download:

Figure 5.1: The details window of Download Director

IBM Web Content Manager/Portal V8.5 connector installation

The downloaded connector can be installed by extracting it into the root directory of the Watson Explorer Engine installation:

On /opt/ibm/WEX/Engine/

On …\Program Files\IBM\WEX\Engine\

The archive file contains the JAR files and so on, used by the WCM connector.

Details of the procedure to install the connector can be found at the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.connector.wcm-portal-server.doc/t_wcm-portalserver-connector-install-auto.html

5.1.2: Downloading the Fix Pack components for Linux and Windows for correct upgrades The next section of the Fix Pack list contains the Others section, which has interim fixes for Java packages (usually security fixes):

Figure 5.2: The Required Fix Pack(s) can be selected by ticking a box(es)

5.1.3: Fix Pack lists - identifying which fixes are cumulative

In the Fix Pack list, if the fix is labelled as interim, then it is not usually a cumulative such as the Fix Pack shown as follows, where the mouse-over shows the detail, and that it is targeted specifically for the windows 12.0.3.0 JRE install:

Figure 5.3: The mouse-over pop-up window shows the applicable versions this Fix Pack applies to

It can be seen from the mouse-over below that the Fix Pack 12.0.3.4 is cumulative, because the Applies to versions: label shows all the previous Fix Packs, but critically shows that the base version, 12.0.3.0 is listed too:

Figure 5.4: The mouse-over shows that the Fix Pack 12.0.3.4 is cumulative

Additionally, in the README link browser page, it states the following:

You can install Watson Explorer oneWEX for single container deployment Version 12.0.3.4 directly without installing an earlier version of Watson Explorer oneWEX for single container deployment. Reference link is as follows: https://www.ibm.com/support/pages/node/6244508

The readme.txt file contains the following knowledge centre link:

http://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0

which is the top-level link to the IBM Watson Explorer products covered by this book. The completed IBM Download Director status window shows the bytes downloaded.

5.1.4: IBM Download Director installation and use for Fix Packs

Chapter 1, Getting Started with IBM Resources for sections 1.4.1.1 to 1.4.1.2 describe the procedures required to install the IBM Download Director and the work arounds available if it fails to install correctly.

5.1.5: License restrictions

Chapter 1, Getting Started with IBM Resources for section 1.4.2 contains the full links to the license requirements User Value Unit Processor Value Unit for the IBM Watson software.

5.1.6: Red Hat Linux Maintenance using Subscription Manager

For Red Hat Linux RHEL 8.x, the Subscription Manager can be used together with the yum installer to upgrade packages.

Chapter 1, Getting Started with IBM Resources for shows the main location for download of RHEL 8.0 and the versions available for supporting a production system.

5.2: IBM Watson Explorer Foundational Components 12.x

The Watson Explorer Foundational Components 12.0.3.0 consists of a set of Red Hat Package Manager installation files which, after download, can then be copied, and installed with the yum install utility on the target Linux operating system platform.

There are an equivalent set of installation files for the Windows operating system, which have the .msi extension, which are downloaded as a set of separate Fix Pack files. The only compressed download files are for the IBM Watson Annotation Administrator Console component, which is downloaded as a compressed .tar file for Linux and a compressed .zip file for the Windows version, and the IBM Watson Explorer-DAE Analytical, Linux, and Windows system files for Fix Pack 4.

5.2.1: Fix Pack product searching procedures

As shown in the previous section, you get to the browser page, using the following URL:

https://www.ibm.com/support/fixcentral/

Using exactly the same search parameters, as shown in section for IBM Watson Explorer oneWEX 12.x, we can scroll down and select the Windows and Linux Fix Packs for IBM Watson Explorer Foundation Components as follows:

Figure 5.5: The two Fix Packs for IBM Watson Explorer Foundational Components for Windows and Linux are selected

The same Download Director procedure is the used as for the section.

5.2.2: Downloading the Fix Pack components for Linux and Windows for correct upgrades Because we are using IBM Download Director, rather than HTTPS/SFTP, we have the option to select multiple components for download, so I can tick the required Fix Packs, and any additional Fix packs required:

Figure 5.6: The selected Fix Packs are ready to be downloaded

The download procedure can now be followed exactly as shown in section 5.1.2 of this chapter.

5.2.3: Fix Pack lists - identifying which fixes are cumulative

The mouse-over facility shows the Fix pack details as also covered in detail in section

Figure 5.7: The mouse-over shows the Fix Pack is cumulative

So, it can be seen that this Fix Pack 4 can be applied directly to the base version 12.0.3.0 of the IBM Watson Explorer Foundational Components (Windows) System:

Figure 5.8: The list of Fix Packs to be downloaded can be reviewed with the download terms After clicking the Continue command button at the foot of the browser page, View and accept terms are shown with the list of selected Fix Packs, as highlighted in the preceding screenshot.

Then, scroll down to click the I agree command button. And to start the actual download, click the Download now command button.

The Download now command button is clicked to start the IBM Download Director download of the five Fix Pack items we selected earlier:

Figure 5.9: The prompt window can appear to download a newer version of the IBM Download Director Java application You might see the preceding pop-up window; click

(Usually if there is a new version of IBM Download Director available).

Figure 5.10: The IBM_Download Director.jnlp file is downloaded for launching with Java Then, click to launch the .jnlp download:

Figure 5.11: The bottom left-hand corner of the Chrome browser window shows the downloaded File IBM_DownloadDirector.jnlp file which is clicked to install it

The new installed application, IBM Download Director, is prompted to Run and connect to the IBM Fix Pack central server site to download the Fix Packs we selected:

Figure 5.12: The IBM Download Director Java application program is loaded, click Run to start the application Then, this launches the application as shown in the preceding screenshot; click

Figure 5.13: The IBM Download Director status bar window shows the download progress

You should see the download shown in figure Sometimes the IBM server is very busy, and it is possible that Download Director will have an issue connecting at first. If so, the Pause command button will be renamed Retry to allow you to retry the server connection.

On completion, you will see the status window at 100%:

Figure 5.14: The completed download shows 16 files downloaded with a total size of 12 GB

And clicking on the Details command button will show the status of each downloaded file in the selected list:

Figure 5.15: The full list of downloaded files for the Fix Packs is displayed

To see the full download path, tick the Show full path checkbox to see the following:

Figure 5.16: The full file path can be viewed by ticking the Show full path tick box

The downloads can then be transferred by copying as required for an upgrade installation:

Figure 5.17: The copied Fix Pack files for the Linux and Windows system

5.2.4: License restrictions

Chapter 1, Getting Started with IBM Resources for section 1.4.2 contains the full links to the license requirements UVU/PVU for the IBM Watson software.

5.3: IBM StoredIQ For Legal 2.0.3.7

IBM StoredIQ for Legal VM 2.0.3.7 Server is supplied as an installation, which is a ready-built virtual machine .ova VMware file, based on CentOS 7.

There are some recent Fix pack updates for IBM StoredIQ for Legal (VM) 2.0.3.7: Fix pack 2.0.3.10 requires the Chrome 79 version of the browser.

Fix pack 2.0.3.10 requires the Browser Firefox ESR 72 version.

Starting with Fix pack 2.0.3.4, the custodian portal can also be accessed from Apple iPad tablets (iPad mini 4 with IOS 9.3.5 and iPad Pro with IOS 11).

5.3.1: Fix Pack product searching procedures

As shown in section go to the Browser page, using the following URL:

https://www.ibm.com/support/fixcentral/

Then, select the search parameters, as shown in the following screenshot:

Figure 5.18: The parameters for searching for the IBM StoredIQ For Legal (VM) Fix Packs

Click the Continue command button to initiate the Fix Pack search:

Figure 5.19: The default for Browse for all fixes The search options are now available, as shown in the preceding screenshot; just use the default Browse for fixes and click on the Continue button. The APAR or SPR is a known software issue assigned an ID, which the IBM support maintains, and so can be entered to search for a specific fix for that issue. There are sometimes special one-off fixes supplied to a small number of customers, or even uniquely to a single customer, which can be entered in the Individual fix IDs text box.

If you have a more specific issue, which may have a fix, then it is also possible to perform a text search and enter free text to try to locate the required Fix Pack.

5.3.2: Downloading the Fix Pack components for Linux and Windows for correct upgrades It is important to select the correct Fix Packs for an upgrade. In a new base installation, a search should be made for the latest appropriate Fix Pack to reduce the possibility of security issues and functional failures.

Figure 5.20: The Fix Pack Component list shows an upgrade tool and Fix Packs

In the results in figure we can see that we can apply a Fix Pack 8 which is item 2 on the list, and we can then apply an upgrade tool, which is the first item 1 on the list. Applying this upgrade tool then takes the release to 2.0.3.9.

5.3.3: Fix Pack lists - identifying which fixes are cumulative

The mouse-over shows the tool information:

Figure 5.21: The mouse-over shows the tool is cumulative as it includes the base version

The preceding screenshot shows that the tool is cumulative and can be applied right back to the base 2.0.3.0 version.

The mouse-over on the second item in the list, Fix Pack 8 shows that the Fix Pack only applies to version 2.0.3.7 (and the base 2.0.3.8):

Figure 5.22: The Fix Pack is specific to 2.0.3.7 for upgrade to 2.0.3.8

So, the best strategy to get the latest version requires us to select items 1 and which will get us to 2.0.3.9. It should be noted here, that there are other later versions of IBM StoredIQ for Legal (VM). If we select the drop-down on the right-hand side of the result list, we can see that there is a 2.0.3.11 version, (and also a 2.0.3.10 version), but there is no direct upgrade path from 2.0.3.7 to this version:

Figure 5.23: The right-hand side of the Fix Pack results page shows that other versions are available

So, selecting items 1 and 2 and clicking on I get the following screenshot:

Figure 5.24: The list of Fix Pack components selected is displayed for agreement

Click I then the Fix Packs listed can be reviewed and downloaded:

Figure 5.25: The Fix packs required for download are selected using the tick boxes Click Download now to start the download for the select items:

Figure 5.26: The Download now command button is clicked to start the Download

Click Open IBM Download Director to start the download:

Figure 5.27: Click on the Run command to initiate the downloads

Now click Run to allow the IBM Download Director to connect to the IBM Fix Pack server and start the download, with the status shown in IBM Download Director

Figure 5.28: The status of the download is displayed

The completed download shows that 12 GB of Fix Pack files have been downloaded:

Figure 5.29: The status window shows the completed download The Details command button gives the status of each file downloaded:

Figure 5.30: The list of each file downloaded can be seen in the Details window

5.3.4: IBM Download Director installation and use for Fix Packs

Chapter 1, Getting Started with IBM Resources for sections 1.4.1.1 to 1.4.1.2 describe the procedures required to install the IBM Download Director, and the work arounds available if it fails to install correctly.

5.3.5: License restrictions

Chapter 1, Getting started with IBM Resources for section 1.6.2 contains the full links to the License requirements UVU/PVU for the IBM StoredIQ for Legal (VM) 2.0.3.7 software.

Conclusion

This chapter covered the IBM Fix Packs required for the upgrade of IBM Watson and StoredIQ software base installation versions targeted for installation. It described the step-by-step procedures required to download the Fix Packs and how to identify the correct version of a Fix Pack.

The next chapter, Chapter 6, IBM Cloud PAK describes the architecture and implementation of IBM’s Cloud PAK systems. The IBM Cloud PAK offerings are hosted on Red Hat Openshift clusters with the IBM Kubernetes container management layer.

Points to Remember

Select the latest base product version supported for your target environment and download it from IBM Software Catalog.

Search and download the latest Fix Pack (this is usually cumulative) to apply fixes to the base product.

It is always recommended to search for the latest compatible Fix Pack and any intermediate Fix Packs, to ensure the completed installation is optimally installed.

Note that there are other later versions of IBM StoredIQ for Legal (VM) (2.0.3.10 and 2.0.3.11), which have to be installed specifically as base versions and cannot be created by upgrading version 2.0.3.7.

Multiple Choice Questions

How is IBM Watson Explorer oneWEX 12.0.3.0 upgraded? IBM oneWEX12.0.3.0 is upgraded using Windows system update

IBM oneWEX 12.0.3.0 is upgraded from IBM Fix Central web site downloads IBM oneWEX 12.0.3.0 can’t be upgraded

IBM oneWEX 12.0.3.0 is upgraded using yum installer

A cumulative Fix Pack can be identified by:

Looking at its version

Using mouse-over to see the list applies to versions

Downloading the base version Downloading the latest version

IBM Download Director allows:

Just one Fix Pack to be downloaded

Only the latest Fix Pack to be downloaded

Only Fix Packs not ticked to be downloaded

All Fix Packs selected by a tick box to be downloaded

UV License means:

Under Valued User License

User Value Unit License User Version Upgrade License

Upgraded Version User License

Multiple Choice Answers

b. IBM oneWEX 12.0.3.0 is upgraded from IBM Fix Central web site downloads

b. Using mouse-over to see the list applies to versions

d. All Fix Packs selected by a tick box to be downloaded b. User Value Unit License

Questions

If IBM Download Director could not be used, what alternative download mechanisms could you select for use, using the IBM Fix Pack download page?

How would you identify that a Fix Pack was cumulative and what does that mean with regards to upgrading from the Base version of the installation? What advantage does IBM Download Director provide that the HTTPS or SFTP download options don’t provide?

In the Download Director status window after download is complete, what would you do to quickly view the individual files and how would you show the full folder path of the listed files?

Key terms

User value unit measure of a license for a Fix Pack product Processor value unit of a license for a Fix Pack product

Virtual machine

Open virtual appliance file type Java runtime environment for a Java system

Annotation Administration Console

iPhone operating system

CHAPTER 6 IBM Cloud PAK Systems

Introduction

This chapter describes the architecture and implementation of IBM Cloud PAK systems. All the containers in Cloud Pak use Certified Red Hat Universal Base Images

The IBM Cloud PAK offerings are hosted on Red Hat OpenShift clusters with the IBM Kubernetes container management layer. I have also emphasized the dependency and limitations of some Cloud PAKs on the OpenShift version; for example, IBM Cloud Pak for Data will only function correctly up to OpenShift version 4.3 as at July, 2020. IBM Cloud Pak For Data is currently at version 3.0.1

Structure

In this chapter, we will discuss the following topics: Installation preparation

IBM Watson Explorer oneWEX 12.x Docker Container

Estimated download duration Server(s) required for the installations

IBM Cloud Pak for Data

Installation procedure

IBM StoredIQ for Legal 2.0.3.7

IBM Cloud Pak for multi-cloud management

IBM Cloud Pak for Security

Objectives

After studying this unit, you should be able to: Identify the prerequisite system versions required for each of the system components, which will be required to support the IBM Watson and StoredIQ software versions targeted for installation.

Understand the prerequisite disk, memory, and network requirements for the target software components to be installed, and know how to configure them.

Search, identify, and download the latest supported versions, and configure the security required to maintain a secure and robust system.

6.1: Installation preparation

IBM has the following URL, which specifies the requirements for IBM Cloud Pak for Data:

https://www.ibm.com/support/producthub/icpdata/docs/content/SSQ NUZ_current/cpd/plan/rhos-reqs.html

The Cloud Pak for Data license gives access to both, the Red Hat OpenShift Container Platform and Red Hat Enterprise Linux operating system. These can be downloaded, for the Red Hat OpenShift system, either from IBM Passport Advantage or directly from the Red Hat Customer Portal. There are two levels of licensed installation available, Standard and Enterprise.

Cloud Pak for Data Enterprise Edition, has the part number

Cloud Pak for Data Standard Edition, has the part number CC62VEN.

The following URL lists all the supported versions for IBM Cloud Pack for Data 3.0.1: https://www.ibm.com/support/producthub/icpdata/docs/content/SSQ NUZ_current/sys-reqs/services_prereqs.html

The download URL for the Software Access Catalog overview is as follows:

https://www.ibm.com/partnerworld/program/benefits/software-accesscatalog

Using the Firefox browser (or the Chrome Browser, Version 88.0.4324.190) you can find and then click on the “Access the catalog” command button which loads the URL as follows:

https://www356.ibm.com/partnerworld/partnertools/eorderweb/ordersw.do It should be noted that login as an IBM PartnerWorld Business partner or a customer with “passport advantage” is required. Search for CC62VEN, as shown in the following screenshot:

Figure 6.1: Search box for finding IBM software systems by part number Enter the preceding part number in the Find by part number field and then click the search magnifying glass to display the results.

Figure 6.2: Select the Download Director and click on View details to see the file details

Clicking on View details gives the following details: Product details

File CP4D_STE_Readme.docx RHEL 7, Red Hat Entrprs Lnx RHEL Adv Pltfrm

English Related information

File 91,596 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

Table 6.1: The relative download speeds for different network types

Figure 6.3: Double-click on the IBM Download Director listed application Double-click on the IBM Download highlighted in blue in the preceding screenshot, in the Firefox bowser pop-up window to launch the IBM Download Director Java application.

Figure 6.4: Launch the IBM Download Director Java application by clicking Run Then, click Run as shown in the preceding screenshot.

Figure 6.5: The status of the IBM Download Director indicates 100% when completed

The preceding document contains two sections for installation guidance: Installing Red Hat OpenShift Container Platform 3.11

Installing Red Hat OpenShift Container Platform 4.3

6.1.1: IBM Watson Explorer oneWEX 12.x Docker Container

Search as follows to go directly to the IBM Cloud Private version:

Figure 6.6: Enter the search text to select the highlighted download

6.1.2: Estimated download duration

File ibm-cloud-private-3.2.1-qsg.zip Linux for System p, Linux for System x 86Series, Linux for System z, Red Hat Entrprs Lnx RHEL Adv Pltfrm, SLES 12, Ubuntu

Language(s) English File 2,902 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

File ibm-cloud-private-x86_64-3.2.1.tar.gz

Linux for System x 86Series, Red Hat Entrprs Lnx RHEL Adv Pltfrm, SLES 12, Ubuntu

English Related Estimated download duration

File 16,379,420,011 bytes

bytes bytes bytes bytes bytes bytes bytes bytes

File ibm-cloud-private-rhos-3.2.1.tar.gz Red Hat Entrprs Lnx RHEL Adv Pltfrm

English Related Estimated download duration

File 14,004,382,150 bytes

bytes bytes

bytes bytes bytes bytes bytes bytes

Table 6.2: The relative download times for the installation file with different networks

Figure 6.7: Click on the I agree radio button, then click Download now The following 6 steps cover the use of IBM Download Director to download the IBM Cloud Private installation file, ibm-cloud-private3.2.1-qsg.zip

Select IBM Download Director and click Choose… as shown in the following screenshot:

Figure 6.8: Double-click on the IBM Download Director application listed to launch it

Double-click on IBM Download Director and then click

Figure 6.9: Click Run to start the download application This will download around 30 GB of installation files:

Figure 6.10: The download status of the file is shown on the status bar The details can be found in the IBM Cloud Private Quick Start Guide:

Figure 6.11: The quick start guide is shown zipped (unzipped as an HTML file)

The Quick Start Guide can be extracted to an HTML file,

Figure 6.12: The downloaded files are shown, completed, taking 30 GB disk space

On completion, check the details for the status, as shown in the following screenshot:

Figure 6.13: The Details button shows the status and size of each downloaded file

Copy the downloads to the installation area:

Figure 6.14: The downloaded ibm-cloud-private-x86_64-3.2.1.tar.gz file is copied for installation

6.2: IBM Cloud Pak for Data

The Hub URL for IBM Cloud Pak for Data is as follows: https://www.ibm.com/support/producthub/icpdata/docs/content/SSQ NUZ_current/cpd/install/installation-files.html

There is a very useful URL, which will also provide the most recent news on this Cloud Pak: https://www.ibm.com/support/knowledgecenter/SSQNUZ_3.0.1/cpd/o verview/whats-new.html?view=embed#whats-new__sept-2020

After you order IBM Cloud Pak for an entitlement key for the software is associated with your My IBM account. To get the entitlement key:

Figure 6.15: Copy the unique entitlement key for IBM Cloud Pak Log into the following link with the IBM ID and password that are associated with the entitled software:

https://myibm.ibm.com/products-services/containerlibrary

Figure View library to see the list of the entitled Container software you have See the access list by clicking on View I have everything!

On the Entitlement key tab, select Copy key to copy the entitlement key to the clipboard:

Figure 6.17: Click on the Copy key command button to copy the API key to the clipboard Save the API key in a text file.

With the download that we have selected, we use a Linux workstation to run the installation from. The workstation does not

have to be a node of the cluster, but must have internet access and be able to connect to the Red Hat OpenShift cluster.

6.2.1: Server(s) required for the installations

The following platforms are selected for installation:

Figure 6.18: The highlighted components are selected for download

The details of the download times and so on are given in Section

6.2.2: Installation procedure

Obtain the installation files. On a Linux workstation, we download the Standard Edition file from the following link:

https://github.com/IBM/cpd-cli

Log into GitHub:

Figure 6.19: The two-factor authentication for GitHub prompts for an SMS text code GitHub now uses two-factor authentication with a one-time code, so after the normal prompt for user name and login, an SMS text with the code is sent to your mobile phone to enable you to enter this code for completion of the login.

Figure 6.20: The IBM Cloud Pak for Data Installer links to the download Click on the README.md file:

https://github.com/IBM/cpd-cli/blob/master/README.md

Figure 6.21: The table of Installer names for each platform is displayed

Please see the reference link as follows:

https://www.ibm.com/support/producthub/icpdata/docs/content/SSQ NUZ_current/cpd/install/install.html Check the oc installed version:

Figure 6.22: The oc version command shows the OpenShift version status

Please see the reference link as follows: https://github.com/IBM/cpd-cli/releases

Figure 6.23: The Standard Edition install program is selected for download

The highlighted Standard Edition compressed tar file is downloaded:

downloaded: downloaded: downloaded:

downloaded:

Table 6.3: The file names for installation for different levels of entitlement In Firefox browser, on the RHEL Linux 8.0 server, we save the file cloudpak4data-ste-3.0.1.tgz to the /root Downloads area:

Figure 6.24: The cloudpak4data-ste-3.0.1.tgz file is saved to the Downloads area Extract the contents of the TAR file:

tar -zxvf cloudpak4data-ste-3.0.1.tgz

(base) [root@ecmukdemo10 ~]# cd /opt/IBM/ (base) [root@ecmukdemo10 IBM]# ls

DS4.1.3 InstallationManager SDPShared

(base) [root@ecmukdemo10 IBM]# mkdir cloudpak4data

(base) [root@ecmukdemo10 IBM]# pwd

/opt/IBM (base) [root@ecmukdemo10 IBM]# cd

(base) [root@ecmukdemo10 cloudpak4data]# pwd

/opt/IBM/cloudpak4data (base) [root@ecmukdemo10 cloudpak4data]# cp /home/wasadm/Downloads/cloudpak4data-ste-3.0.1.tgz .

(base) [root@ecmukdemo10 cloudpak4data]# ls

cloudpak4data-ste-3.0.1.tgz (base) [root@ecmukdemo10 cloudpak4data]# tar -zxvf cloudpak4data-ste-3.0.1.tgz

LICENSES/

LICENSES/LA_cs

LICENSES/LA_de

LICENSES/LA_el LICENSES/LA_en

Etc…

LICENSES/LI_zh_TW LICENSES/non_ibm_license

LICENSES/notices bin/

bin/cpd-chain0.pem

bin/cpd-darwin bin/cpd-darwin.sig

bin/cpd-linux bin/cpd-linux.sig

bin/cpd-ppc64le

bin/cpd-ppc64le.sig bin/cpd-public.key

bin/cpd-s390x

bin/cpd-s390x.sig

bin/cpd-signcert.pem bin/cpd-windows.exe

bin/cpd-windows.signed.exe bin/deploy.sh

bin/utils/

bin/utils/deploy-utils/ bin/utils/deploy-utils/README.md

bin/utils/deploy-utils/global.yaml bin/utils/deploy-utils/install.yaml

bin/utils/deploy-utils/installChart.sh

bin/utils/deploy-utils/installutil bin/utils/deploy-utils/loadimages.sh

bin/utils/helm bin/utils/installutil

bin/utils/process-bootstrap-images.sh

repo.yaml (base) [root@ecmukdemo10 cloudpak4data]#

A bin folder is created in the current directory with the cpd command binaries and a After you extract the contents of the gzipped tar file, you can delete the tar from your file system to save space. Set up the requirements for the cpd command:

Figure 6.25: The cpdtool.tgz file is downloaded for use during the installation

Save the file, and copy and unpack it:

Figure 6.26: The gzipped tar file, cpdtool.tgz, is unpacked

On the same workstation, download and extract the Linux oc CLI from the website:

https://docs.openshift.com/containerplatform/4.5/cli_reference/openshift_cli/getting-started-cli.html

is required for to succeed. Details of the use of are covered in the following sections. Edit the repo.yaml server definition file that you downloaded. This file specifies the repositories for the cpd command to download the installation files from. Make the following changes to the file:

file: file: file: file: file: file: file: file: file: file: file: file: file: file:

Table 6.4: The parameters to be added to the repo.yaml file for logon Some services are hosted in separate repositories. If you plan to install any of the services listed in the following table, add the appropriate entries to the repo.yaml file:

file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file:

file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file:

file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file:

file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file: file:

Table 6.5: The namespace parameters for each IBM Watson subsystem Save the file. We will be using Watson Discovery from the preceding table:

Edit the repo.yaml file using

Figure 6.27: The repo.yaml file is configured for IBM Watson Discovery installation Backup the repo.yaml file:

cp repo.yaml repo.yaml_Bck Follow the installation procedure from the following URL:

https://www.ibm.com/support/producthub/icpdata/docs/content/SSQ NUZ_current/cpd/install/rhos-install.html You can run the following command to find the route to the registry: oc get routes --all-namespaces

Figure 6.28: The list of existing OpenShift namespaces is listed Then run the command:

oc get route/default-route -n openshift-image-registry -template='{{.spec.host}}' On the server,

[wasadm@ecmukdemo10 Downloads]$ oc get route/default-route -n openshift-image-registry --template='{{.spec.host}}'

Returns:

default-route-openshift-image-registry.apps-crc.testing

So, we need to use

(where the project we have is Run the following command to get the internal name of the Red Hat OpenShift registry service: oc registry info This gives:

default-route-openshift-image-registry.apps-crc.testing (As we also found earlier) Login as an administrator. Run this command to configure your shell:

eval $(crc oc-env) oc login -u kubeadmin -p ILWgF-VfgcQ-p6mJ4-Jztez https://api.crc.testing:6443

Figure 6.29: The OpenShift login is run to prepare for the IBM Cloud Pak install cpdtool –help gives the following:

[wasadm@ecmukdemo10 cloudpak4data]$ ./cpdtool --help CPD Command Line Tool:

cpdtool [flags] cpdtool [command] Available export           Work with CPD exports help             Help about any command import           Work with CPD imports init             initialize cpdtool list             List CPD resources reset            reset cpdtool schedule-export  Work with CPD schedule export version          print the version information

--arch string  Provide the architecture (default "x86_64")

--config string config file (default is ./cpdtool.yaml) -h, --help  help for cpdtool --log-level string   command log level: debug, info, warn, error, panic (default "info") -n, --namespace string  The namespace in which cpdtool should operate (default "zen") --verbose  Logs will include more detailed messages

Use "cpdtool [command] --help" for more information about a command. [wasadm@ecmukdemo10 cloudpak4data]$ Using the following: ./cpdtool --config ./repo.yaml --namespace openshift-image-registry

In the cpdtool.log we get: time="2020-09-08T14:00:42-07:00" level=info msg="CliContext.Complete(): namespace set to 'cp/watsondiscovery'" time="2020-09-08T14:13:49-07:00" level=info msg="CliContext.Complete(): namespace set to 'openshift-imageregistry'" There is a an almost instantaneous response from the cpdtool used to register a project; so check that there are no errors in the cpdtool.log file. This step is just to set the registry, but doesn’t pull the actual software.

Figure 6.30: The oc project default is selected

The documented status command does not work with the available

Figure 6.31: The status command as documented gives an error

Common services IAM can be installed if Please see the reference link as follows:

https://www.ibm.com/support/producthub/icpdata/docs/content/SSQ NUZ_latest/cpd/install/common-svcs.html

6.2.3: IBM StoredIQ for Legal 2.0.3.7

IBM StoredIQ for Legal VM 2.0.3.7 Server is supplied as an installation, which is a ready-built Virtual Machine .ova VMware file, based on CentOS 7. There are some recent Fix pack updates for IBM StoredIQ for Legal (VM) 2.0.3.7:

Fix pack 2.0.3.10 requires the Chrome 79 version of the browser. Fix pack 2.0.3.10 requires the Browser Firefox ESR 72 version.

Starting with Fix pack 2.0.3.4, the custodian portal can also be accessed from Apple iPad tablets (iPad mini 4 with IOS 9.3.5 and iPad Pro with IOS 11).

However, there are certain limitations, as described in the product Knowledge Centre.

IBM StoredIQ products - system requirements:

https://www.ibm.com/support/pages/ibm-storediq-products-systemrequirements The following supporting IBM system products are already installed:

DB2 Workgroup Server Edition

IBM Content Navigator

IBM Security Directory Server 6.4.0.20

WebSphere Application Server -8.5.5.17

6.2.3.1: Server(s) required for the Installations

StoredIQ for legal can be migrated from a VM to a Red Hat OpenShift environment. The reference link is as follows:

https://www.ibm.com/support/knowledgecenter/en/SSZL2P_2.0.3/com .ibm.biq.deploy.doc/d_migate_vm2container.html

6.3: IBM Cloud Pak for Multi-cloud Management

The download for this is shown as follows, for IBM Cloud Automation Manager 4.2 for IBM Cloud Pak for Multicloud Management v1.3 English Multiplatform eAssembly.

The product code to search for the multiplatform eAssembly on the IBM Software catalog is The Linux version of the product code, for download is shown as follows. IBM Cloud Automation Manager 4.2 for Linux (x86_64) English

Figure 6.32: The IBM Cloud Automation Manager 4.2 with code CC5QFEN, is selected

The following 5 steps describe the download and copying of the installation file, IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz file, for the IBM Cloud Pak for Multi-cloud Management v1.3

On search for this, it is recommended to use the IBM Download Director Java application, shown as follows, because the size of the zipped tar file for download is around 10 GB:

Figure 6.33: The IBM Download Director is launched to download the IBM Cloud Pak

Click Run to start the download:

Figure 6.34: The status of the download for IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz is displayed

The IBM Download Director Java application status window shows the progress of the downloading installation file,

Figure 6.35: The completed download showing nearly 11 GB of downloads

On completion, the downloaded file can be copied from the Download Director folder area to the installation folder:

Figure 6.36: The downloaded installation file is copied to the install folder Copy up to the main server. The reference link is as follows: https://github.com/icp4a/cert-kubernetes

IBM Cloud Pak for Automation 20.0.1 on Certified Kubernetes This repository includes folders and resources to help you install the Cloud Pak for Automation software. Installation of the software components is done with the Cloud Pak operator. For demonstration purposes, or to get started with the Cloud Pak, you can install a single component of Digital Business Automation For

enterprise purposes, you must enable one or more components in a custom resource file, and install them in a specified namespace. This README is divided into the following sections:

https://github.com/icp4a/certkubernetes/blob/master/README.md#install-the-cloud-pak-fordemonstration-purposes IBM Cloud Pak for Automation 20.0.1 for demonstration purposes This repository includes the folders and resources for installing the Cloud Pak for Automation software for demonstration purposes on Red Hat OpenShift Cloud Platform 3.11.

Cloud Pak for Automation can be installed on OCP by running the deployment script, and selecting the required deployment pattern. A deployment pattern includes a single Cloud Pak option, and also includes containers for Db2 and OpenLDAP, when required.

In version 20.0.1, patterns cannot be used to install the Cloud Pak for enterprise purposes. In addition to the patterns, it is possible to install Business Automation Insights and Automation Digital Worker for demonstration purposes. These containers use a ‘pattern deployment’.

Business Automation Insights and Automation Digital Worker, both require other Cloud Pak functions. To use more than one function in an OCP cluster, a single deployment pattern must be installed by using the Cloud Pak operator. The README.md text file can be viewed here (this has links to IBM’s Knowledge Centre, which has the actual Installation details.)

https://github.com/icp4a/certkubernetes/blob/master/README.md#install-the-cloud-pak-forenterprise-purposes Giving the IBM URL:

https://www.ibm.com/support/knowledgecenter/SSYHZ8_20.0.x/com.i bm.dba.install/topics/con_installing.html

Reference license information is as follows: https://github.com/icp4a/certkubernetes/blob/master/README.md#legal-notice https://github.com/icp4a/cert-kubernetes/blob/master/legal-notice.md

Install the Cloud Pak for demonstration purposes

The Cloud Pak functions are presented as patterns. A single pattern is installed in a specified namespace. It is not possible to install more than one pattern in a single namespace. In version 20.0.1, patterns can only be used to install the Cloud Pak for demonstration purposes.

The demo deployment type reduces the number of steps required as Ansible procedure is used to create persistent storage that is allocated to a server node. If you want to install the Cloud Pak components into a cluster with external storage, the following URL describes how to do this:

https://github.com/icp4a/certkubernetes/blob/master/README.md#install-the-cloud-pak-forenterprise-purposes

I have also found the demo instructions at the following URL: https://www.ibm.com/support/knowledgecenter/SSYHZ8_20.0.x/com.i bm.dba.install/op_topics/tsk_deploy_demo.html

The Boot Master and Infrastructure nodes can be located on the same host, as long as it has enough resources. Boot Masters with a co-located etcd (etcd is a control plane node, see the Red Hat URL https://access.redhat.com/solutions/4422511 for details) these need a minimum of 4 cores. The cluster setup script creates an OpenShift project applies the custom resource definitions adds the specified user to the ibm-

cp4a-operator role, and then binds the role to the service account, applying a security context constraint for the Cloud Pak.

The script also requests that the administrator takes note of the cluster host name and a dynamic storage class on the cluster. These names are provided to the user, who runs the deployment script.

Use the following steps to complete the preparation: Step 1 -Check the docker version and the environment are set up correctly:

Figure 6.37: The docker Client and Server versions are displayed

Figure 6.38: The Red Hat Subscription manager is run on the Target server, ecmukdemo10, to register the system for updates

Update the subscription status on Red Hat.

Reference link is as follows: https://access.redhat.com/management/products

Run the update as root: dnf update

Download the GitHub repository onto the local server and cd to the

$ git clone [email protected]:icp4a/cert-kubernetes.git $ cd cert-kubernetes

Login to the target cluster as the cluster administration user: crc oc-env

oc login -u kubeadmin -p ILWgF-VfgcQ-p6mJ4-Jztez https://api.crc.testing:6443

Figure 6.39: The OpenShift client, oc, the Command Line Interface is used to log in

Run the cluster setup script from where the GitHub repository was downloaded, following the prompts:

cd scripts ./cp4a-clusteradmin-setup.sh Enter the name for a new project or an existing project (namespace); for example,

Enter an existing non-administrator user name in your cluster to run the deployment script; for example, The available storage class names and the infrastructure node name are displayed after the install script completes. The class name to use for the installation, and the host name are needed for the deployment script. Step 2: Container images are given access to an installer To get access to the Cloud Pak container images, you need an IBM Entitlement Registry key to pull the images from the IBM docker registry, and download the Cloud Pak package file) downloaded from the IBM PartnerWorld Software Access Catalog, and push these images to the local server docker registry. For the demo 20.0.2 version, you can use the following link: https://github.com/icp4a/cert-kubernetes/archive/20.0.2.tar.gz

Figure 6.40: The cert-kubernetes-20.0.2.tar.gz demo version of the IBM Cloud Pak is saved Click OK and unpack the certificate and scripts.

The deployment script asks for the entitlement key or user credentials for the local registry.

Using a non-root user, you also need the container images for Db2 and OpenLDAP: Download or clone the GitHub repository on the local server and cd to the cert-kubernetes directory:

cd cert-kubernetes-20.0.2/ yum install git git config --global user.name alan-bluck git config --global

Go to the scripts sub-folder: eval $(crc oc-env) oc get is cd scripts The CR files are configured by the deployment script. It is possible to copy these templates, configure them by hand, and apply the file from line, if it is required to run the steps manually. The deployment script makes use of these custom resource (CR) template files for each pattern. The template names include demo and are found in The following documented process was followed first:

Figure 6.41: The scripts folder is navigated for running the installation script Navigate using cd to the cert-kubernetes-20.0.2 subfolder, then cd to the scripts subfolder under this:

Figure 6.42: The script displays the URL for the License information Run the following shell script from the scripts folder: ./cp4a-deployment.sh

Figure 6.43: The script prompts for acceptance of the IBM License conditions Type Yes to accept the license:

Figure 6.44: The script prompts for the installation type, for New enter 1

Figure 6.45: The script prompts for the installation type, enter 1 for OCP The preceding option 1 did not work, so I tried The logs can be viewed to see the reasons for any failures using the URL:

https://access.redhat.com/documentation/enus/openshift_container_platform/4.3/html-single/installing/index

Figure 6.46: The is selected to install to Kubernetes Entering the Kubernetes option

Figure 6.47: The script prompts for Demo or Enterprise level installation

Enter 1 for

Figure 6.48: The script prompts for the ‘pattern’ to be installed

Enter Yes to install Business Automation workflow or services:

Figure 6.49: The script prompts for entry to select the ‘pattern(s)’; there is only one! 1 is the only option, but you still have to enter it to select the option to install!

Figure 6.50: The list of available patterns is shown, there is just one available

1 is the only option, but you still have to enter it to select Business Automation

Figure 6.51: The option(s) can be selected for installation; only one available

Just click the Enter (return) key to complete the selection: https://github.com/icp4a/cert-kubernetes

Here I had issues finding the certificate, so I used the Docker installation ref. https://www.ibm.com/support/knowledgecenter/SSYHZ8_20.0.x/com.i bm.dba.install/op_topics/tsk_images_demo.html This state, Get your entitlement key for the IBM Cloud® Entitled

Log in to the My IBM Container Software library with the IBMid and password that is associated with the entitled software: https://myibm.ibm.com/products-services/containerlibrary

Figure 6.52: The docker pull is used to load The prerequisite containers need to be loaded first, if using Docker, with the shell script command line: ./loadPrereqImages.sh -r docker_registry

Figure 6.53: The list of docker images pushed to the system registry are listed

Now we have the prerequisite container images installed, as listed in the preceding screenshot.

Figure 6.54: The entitlement key is copied for use in the config.yaml file The preceding key is required, and is obtained from the URL:

https://myibm.ibm.com/products-services/containerlibrary You need an IBM user ID and password to launch the entitlement key browser page, similar to the one in the preceding screenshot.

Figure 6.55: The OpenShift registry detail is listed for use Enter the OpenShift command, as shown in the preceding screenshot, to view the registry and port to use. oc registry info --internal

Figure 6.56: The Kubernetes system status is checked using kubectl cluster-info com

Ensure there is access to Kubernetes, using the command, as shown in the preceding screenshot. kubectl cluster-info

Copy the installation Cloud PAK downloaded earlier:

Figure 6.57: Copy the gzipped tar for the Cloud Pak install file to the scripts folder

[wasadm@ecmukdemo10 scripts]$ pwd /home/wasadm/Downloads/cert-kubernetes-20.0.2/scripts [wasadm@ecmukdemo10 scripts]$ ls cp4a-clusteradmin-setup.sh cp4a-post-deployment.sh deploy_CS3.3.sh deployOperator.sh helper  loadimages.sh pull-eventstreams-connection-info.sh cp4a-deployment.sh deleteOperator.sh deploy_CS3.4.sh generated-cr jdbc loadPrereqImages.sh upgradeOperator.sh [wasadm@ecmukdemo10 scripts]$ cp /mnt/hgfs/IBMCloudPrivate/IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz . Run the script with the following commands:

docker login [wasadm@ecmukdemo10 scripts]$ ./loadimages.sh -p IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz -r image-registry.openshiftimage-registry.svc:5000/default

You must login to the target Docker registry before running the script. Also, the load image demo script is for x86_64, amd64, or i386 platforms only: Supported arch: x86_64 Use podman command to load images. ppa_path: IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz arr_ppa_archive: IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz target_docker_repo: image-registry.openshift-imageregistry.svc:5000/default Check image archives in the PPA package: IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz manifest.json Image archives list in IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz: charts/ibm-cam-4.2.0.tgz, mages/3c021fac72ddf9bea73b54f615e72b7a09dbed834a39386d981cd4ba 0965b6f3.tar.gz Image archives in IBM_CLOUD_AUTO_MGR_4.2_Lnx.tar.gz count: 22 etc … list of 22 image ids …etc Load docker images from image archives into local registry. Loading image file: images/da82ebb6ffb261ef67123c161363a7373295c1c07cfa719be8c549785 eba3365.tar.gz Check whether the images are installed:

Figure 6.58: The install log shows the list of containers in the registry The OpenShift command line can be used to display the loaded images: oc get is

6.4: IBM Cloud Pak for Security

IBM Cloud Pak for Security requires OpenShift Container Platform 4.3 as a platform to install on.

This can be downloaded and installed by using the following URL:

https://cloud.redhat.com/openshift/install and selecting Red Hat OpenShift Cluster Manager, for which you need to use a Red Hat account.

This account can be created for free, without paying for a Red Hat subscription, by browsing through the following link:

https://www.redhat.com/wapps/ugc/register.html

After you have created a Red Hat account, browse through the following URL:

https://cloud.redhat.com/openshift/install You will then be prompted for the Red Hat account login and password that you created for free earlier.

IBM Cloud Pak for Security supplies security tools to search and report on network threats across hybrid cloud and cloud environments.

The software system consists of containerized systems, which are pre-installed into the Red Hat OpenShift system.

The IBM Cloud Pak for Security connects to data sources, to search for threats, without changing any of the data which it processes.

The IBM Cloud Pak for Security packages the following subsystems:

IBM Threat Intelligence Analyses threats.

IBM Security Data Performs a federated search and investigation across a hybrid or cloud environment using a standard GUI and workflow.

IBM Case Provides workflows and case monitoring to track and fix network security incidents. IBM Orchestration and It is an additional component which requires a license and is available, stand-alone or integrated in IBM Cloud Pak for Security.

It can be used to create response plans to manage the responses to events and incidents. Search in the IBM Software catalog, using the Firefox browser (Chrome is not currently working for IBM software download access).

On the main IBM PartnerWorld Software, access catalog page: https://www.ibm.com/partnerworld/program/benefits/software-accesscatalog\

Log into the page using your IBM ID (IBM Partner supplied account).

Then, click on the Access the catalog command button link: https://www.ibm.com/partnerworld/partnertools/eorderweb/ordersw.do

Then, you can accept the General License Agreement page and search as follows:

Figure 6.59: The search for IBM Cloud Pak for Security is entered to retrieve the list This will show the search results as you type:

Figure 6.60: The highlighted latest version of IBM Cloud Pak for Security is selected Select the highlighted 1.3.0.1 version (latest version as of September 2020): The next page shows the available downloads and the product codes assigned to them:

Figure 6.61: The IBM Cloud Pak for Security quick start guide and the OpenShift install are selected

Download the eAssembly components, as shown in the following screenshot, by ticking the boxes. It is recommended to use the IBM Download Director for this, since the main IBM Cloud Pak for Security component is nearly 30 GB in size.

Figure 6.62: The I agree radio button is selected and the Download now command button is used to start the download of the selected files Select the I agree radio button and click on the Download now command button.

Figure 6.63: The IBM Download Director is double-clicked to launch the application Double click on the IBM Download Director application link (shown highlighted) in the Firefox browser pop-up window. You should see the following pop-up window after a couple of seconds; to launch the application to start the download, click the Run command button:

Figure 6.64: The Run button is clicked to start the IBM Cloud Pak for Security download The download status window should appear:

Figure 6.65: The status bar shows the progress of the CPS_RHOS_EN.tgz download On completion, we see the status bar as 100%, shown as follows:

Figure 6.66: The completed download shows the status at 100% On clicking CPS_RHOS_EN.tgz download status detail is shown:

Figure 6.67: The Details button shows the status and size of the downloaded files The download list shows the Quick Start guide, CPS_QSG_EN.pdf and the install file,

This status window shows that we are downloading nearly 30 GB of a file called which is the IBM Cloud Pak for security file. The estimated time for download is around 1 hour 29 minutes, assuming we can maintain the download speed, which is currently around 5 MB/second. You will notice that the number of connections is shown as This is because IBM Download Director will attempt to establish multiple connections, provided there is capacity on the IBM server, which can increase the overall speed of download and shorten the actual time taken, so it is often showing a status with Connections=2 or even especially if there are a number of large files to be downloaded in the list. In this case, the status bar will split horizontally to show the progress for each separate connection.

For an online installation of IBM Cloud Platform Common complete the following procedure, by using the entitled registry: Install Docker on the Boot Node:

See Chapter 4, On-Premise Server configurations and Sections 4.1 and

For the Docker installation, see the following link: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on Red Hat Enterprise Linux 8.0, pages 63 - 64 Verify that the Docker Engine is installed successfully by running the hello-world image: docker run hello-world

Figure 6.68: The docker system is re-run and checked using the helloworld container If Docker fails to start after it is installed on the boot node, complete the following 1.1. Create a group account: groupadd docker

Modify the user account: usermod -aG docker $(whoami)

Modify the Docker configuration in /etc/sysconfig/docker and set OPTIONS to: OPTIONS='--selinux-enabled=false --log-driver=journald  --signatureverification=false' Restart the Docker service to use the updated configuration:

systemctl restart docker Install the IBM Cloud Platform Common Services

IBM Cloud Platform Common Services cannot install directly on the OpenShift Container Platform, these services must be installed before other Cloud Pak modules. Obtain the entitlement key that you are licensed for with your IBM ID Login to the system after browsing through the following URL, using the IBM ID and password that are associated with the entitled software: https://myibm.ibm.com/products-services/containerlibrary

In the Entitlement keys section, select Copy key to copy the entitlement key to the clipboard.

Download the OpenShift Container Platform CLI tools onto the Boot Node, extract them using the tar command, and install the OpenShift Container Platform CLI tool, sudo docker login cp.icr.io --username cp --password For example, on the Linux system:

[wasadm@ecmukdemo10 scripts]$ sudo docker login cp.icr.io -username cp --password eyJhbSSSSSSSSSSSSSJ9.eyJpc3MiOiJJQk0gTWFya2V0cGxhY2UiLCJpYX QiOjE1OTk1Njg1MzgsImp0aSI6Ijk2YzgzYjlmOTA5NTRmZTZhZWFmO WUzMGRiZmI3YWNlIn0.PkEOIvdkSFDKKD_Eu6uIEGQQ52_sG5MQZlaGtEUKr8

The preceding very long password is shown as an example of and form. You have to get your own from IBM (I have made changes to invalidate my example)! [sudo] password for wasadm: WARNING! Using --password via the CLI is insecure. Use -password-stdin. WARNING! Your password will be stored unencrypted in /root/.docker/config.json. Configure a credential helper to remove this warning. See https://docs.docker.com/engine/reference/commandline/login/#creden tials-store

Login succeeded Create the secret by using the username and entitlement key you retrieved earlier. The docker-email is the email that you used to login to the Container Software Library URL to retrieve your entitlement key: oc create secret docker-registry entitled-registry --dockerserver=cp.icr.io --docker-username=cp --docker-password= --dockeremail= [wasadm@ecmukdemo10 scripts]$ oc create secret docker-registry entitled-registry --docker-server=cp.icr.io --docker-username=cp -dockerpassword=eyJhbSSSSSSSSSSSSSJ9.eyJpc3MiOiJJQk0gTWFya2V0cGxhY2 UiLCJpYXQiOjE1OTk1Njg1MzgsImp0aSI6Ijk2YzgzYjlmOTA5NTRmZTZh ZWFmOWUzMGRiZmI3YWNlIn0.PkEOIvdkSFDKKD_Eu6uIEGQQ52_sG5MQZlaGtEUKr8 [email protected] secret/entitled-registry created

Pull the installer image from the entitled registry by running the following command: sudo docker pull cp.icr.io/cp/icp-foundation/icp-inception:3.2.4

Figure 6.69: The download using docker pull for ICP 3.2.4 is completed

Create an installation directory on the boot node and change directory to it:

mkdir ~/common-services cd ~/common-services Extract the cluster directory:

sudo docker run --rm -v $(pwd):/data:z -e LICENSE=accept -security-opt label:disable cp.icr.io/cp/icp-foundation/icpinception:3.2.4 cp -r cluster /data

Create the cluster configuration or kubeconfig file for the cluster.

Generally, you can populate the kubeconfig file by running the following commands:

Set KUBECONFIG: export KUBECONFIG=cluster/kubeconfig Ensure the user has access (base) [root@ecmukdemo10 common-services]# chown wasadm:wasadm cluster -R I found that the preceding step was important (and missing from IBM’s documentation) because structure generated earlier is owned by root. (base) [root@ecmukdemo10 common-services]# pwd /home/wasadm/common-services To log in to your cluster, use the oc login command, and a new kubeconfig file is populated: oc login -u -p oc login -u kubeadmin -p ILWinvalidpass-Jztez https://api.crc.testing:6443 [wasadm@ecmukdemo10 common-services]$ export KUBECONFIG=cluster/kubeconfig [wasadm@ecmukdemo10 common-services]$ oc login -u kubeadmin -p ILWinvalidpass-Jztez https://api.crc.testing:6443 Login successful. You have access to 57 projects, the list has been suppressed. You can list all projects with 'oc projects'

Using project "default".

Unset the KUBECONFIG environment variable: unset KUBECONFIG If you use a token to log in to the cluster, your kubeconfig file is only valid for 24 hours. The config.yaml file within the extracted cluster directory must be updated before you deploy the services. For Red Hat OpenShift on an IBM Cloud, there is only the OpenShift Container Platform worker nodes visible in an IBM Cloud Kubernetes Service managed cluster. The server node names are the same as the private IP address of their hosting virtual machines. Update the cluster_nodes section of the config.yaml to identify the OpenShift Container Platform worker nodes. Set worker node as master, proxy, and worker node.

Add the OpenShift Container Platform worker node on the cluster that you want to deploy services upon, to the config.yaml file.

Collect information for the config.yaml file. Run the following command to get all the cluster node name(s):

oc get nodes

Figure 6.70: The KUBECONFIG environment variable is unset and the oc nodes listed

The config.yaml file has to be edited. This file is in the cluster sub-folder:

Figure 6.71: The config.yaml file is identified for editing config.yaml section:

Figure 6.72: The server node reference, obtained with oc get nodes, is entered for all three sections of the config.yaml file Identify an OpenShift Container Platform dynamic block storage class that can be used to run the following command. The chosen storage class is used by the common services pods that require persistent storage. oc get storageclass

Select the storage class to use and set it as the value of the storage_class parameter in the config.yaml file.

The default password for the admin user should be changed. This password is then the Common Services login password for the admin user. This login should not be an OpenShift Container Platform account.

Set up a default password in the config.yaml file that must meet the default password regular expression as follows:

^([a-zA-Z0-9\-]{32,} '.)$ The explanation of the regular expression meaning is at: It is possible to define a custom set of password rules. Open the //cluster/config.yaml file, and set the The password must satisfy all regular expressions that are specified in This needs to be added as follows (that is, on two lines): default_admin_password: filenet

Optional password regular expressions It is possible to define one or more rules as regular expressions in an array list that the password must pass. The rules should be created as regular expressions, which are supported by the Go programming language. For this, add the following parameter and values to the config.yaml file:

password_rules: - '^.{10,}' - '.*[!@#\$%\^&\*].*' Disabling the password rule

You have to add (.*) as follows

password_rules: - '(.*)'

See the following link: https://www.ibm.com/support/pages/how-deploy-ibm-cloud-privatev312-using-pureapplication-pattern-type-v1012

Effectively this means accept any characters (I used this!) The default_admin_password must match all rules that are defined. If the password_rules keyword is not defined, the default_admin_password must meet the default enforcement regular expression rule Add the following block into the config.yaml file to set the image registry to the entitled registry. This step is for the installer to pull images from the entitled registry: image_repo: cp.icr.io/cp/icp-foundation private_registry_enabled: true docker_username: cp docker_password: eyJhbSSSSSSSSSSSSSJ9.eyJpc3MiOiJJQk0gTWFya2V0cGxhY2UiLCJpYX QiOjE1OTk1Njg1MzgsImp0aSI6Ijk2YzgzYjlmOTA5NTRmZTZhZWFmO WUzMGRiZmI3YWNlIn0.PkEOIvdkSFDKKD_Eu6uIEGQQ52_sG5MQZlaGtEUKr8

Check the management_services section in the config.yaml file. The following default configuration of the management services is recommended as it installs only the required services for Cloud Pak for Security:

management_services: iam-policy-controller: enabled metering: enabled licensing: disabled monitoring: enabled nginx-ingress: enabled common-web-ui: enabled catalog-ui: enabled mcm-kui: enabled logging: disabled audit-logging: disabled system-healthcheck-service: disabled multitenancy-enforcement: disabled This is created by default anyway on the initial install. Deploying IBM Cloud Platform Common Services Deploy by using the addon command. sudo docker run -t --net=host -e LICENSE=accept -v $(pwd)/cluster:/installer/cluster:z -v /var/run:/var/run:z -v

/etc/docker:/etc/docker:z --security-opt label:disable cp.icr.io/cp/icpfoundation/icp-inception:3.2.4 addon -v The preceding should be run from: /home/wasadm/common-services (on our system deployment).

Verify the installation If the installation succeeded, the access information for the cluster is displayed. The displayed URL to connect to the console can then be used.

Check that the installation is successful by checking the state of the pods under the kube-system namespace. All the pods must be in either the Running or Completed state.

Display the route for the Common Services console to prove it exists by using the following command:

oc get route -n kube-system | grep console

Figure 6.73: The OpenShift command line lists the console service

Apply DNS lookup timeout resolution to Common Services The DNS lookup timeout resolution must be applied to all the pods in the namespace, where IBM Cloud Platform Common Services is deployed. The kube-system namespace needs to be configured as soon as the IBM Cloud Platform Common Services 3.2.4 installation is completed. (Use the script and instructions in the Fix for Common Services download from IBM Fix Central.) The script patches single-request-reopen dnsConfig to all the pods in the cluster.

Conclusion

In this chapter, we covered the setting up and installation of the prerequisites, and the download and installation of three different IBM Cloud Paks on a Red Hat Linux RHEL 8.0 bare metal installation of Red Hat OpenShift:

IBM Cloud Pak for Data IBM Cloud Pak for Multi-cloud Management

IBM Cloud Pak for Security

In Chapter 4, On-Premise Server configurations and Sections 4.1 and we have described the installation of the Docker Container system, and the use and function of the main docker commands.

In Chapter 7, Red Hat OpenShift 4.x Red Hat OpenShift is described. This forms a front-end for container management of a Cloud cluster of load-balanced control plane and worker servers.

Points to Remember

If the IBM Download Director or the access to the IBM Software Catalog fails to function, try using a different browser.

For example, the IBM Software Catalog access is currently only working from Firefox, 80.0.1 (64-bit) as at September 2020.

The Cloud Pak for Data License gives access to both, the Red Hat OpenShift Container Platform and Red Hat Enterprise Linux operating system. These can be downloaded, for the Red Hat OpenShift system, either from IBM Passport Advantage or directly from the Red Hat Customer Portal.

In version 20.0.1, patterns cannot be used to install the Cloud Pak for enterprise purposes. In version 20.0.2, which we used in this chapter, this does not appear to be the case, as there is a valid Enterprise installation option.

The Cloud Pak functions are presented as patterns. A single pattern is installed in a specified RedHat OpenShift It is not possible to install more than one pattern in a single namespace.

Multiple Choice Questions

What access do you need to download IBM Cloud Pak for Data standard edition and the entitlement key?

Logon access to GitHub

Logon access as an IBM PartnerWorld Business partner or a customer with passport advantage Logon access to a Red Hat account

Logon access to a Docker account

Both logon access as an IBM PartnerWorld Business partner or a customer with passport advantage and logon access to GitHub

What is the approximate download size of the IBM Cloud Pak for Security Linux installation gzipped tar file?

10 GBytes 20 GBytes

30 GBytes

40 GBytes

What is the repo.yaml file used for?

Configuration of the installation parameters for IBM Cloud Pak for Security

Configuration of the installation parameters for IBM Cloud Pak for Data

Configuration of the installation parameters for IBM Cloud Pak for Multi-cloud Management

It isn’t used for installation parameters What is the config.yaml file used for?

Configuration of the installation parameters for IBM Cloud Pak for Security Configuration of the installation parameters for IBM Cloud Pak for Data

Configuration of the installation parameters for IBM Cloud Pak for Multi-cloud Management

It isn’t used for installation parameters

Multiple Choice Answers

e. Both logon access as an IBM PartnerWorld Business partner or a customer with “passport advantage” and logon access to GitHub.

c. 30 GBytes.

b. Configuration of the installation parameters for IBM Cloud Pak for Data.

a. Configuration of the installation parameters for IBM Cloud Pak for Security.

Questions

If you wanted to install IBM Business Automation workflow, which IBM Cloud Pak would you download?

If you wanted to install IBM Watson systems, which IBM Cloud Pak would you download?

If you wanted to install IBM Threat Intelligence Insights, which IBM Cloud Pak would you download?

What major system components are commonly required as prerequisites for installing the IBM Cloud Paks?

Key terms

Red Hat Universal Base Images used by all IBM Cloud Paks SLES Suse Linux Enterprise Server 12

API A unique identifier used to authenticate a calling program using an Application Programmer Interface. OpenShift Linux command

Command Line Interface used by the oc command

Open Virtual Appliance file type

Virtual Machine

YAML is a recursive acronym for YAML Ain’t Markup Language, a plain text data-serialization language used for configuration and installation. It is used in this chapter for the config.yaml and repo.yaml files used for the installation configuration.

CHAPTER 7 Red Hat OpenShift 4.x Installations

Introduction

In this chapter, Red Hat OpenShift is described. This forms a front-end for container management of a Cloud cluster of loadbalanced control plane and worker servers.

Every control plane machine in an OpenShift Container Platform 4.5 cluster must use Red Hat Enterprise Linux CoreOS or be updated with the required kernel if RHEL 8.0 is used. This is because RHCOS includes an essential first-boot provisioning tool called This tool enables the cluster to configure the machines. Operating system updates are delivered as an atomic OSTree repository that is embedded in a container image, which is rolled out across the cluster by an operator.

While RHCOS is the default operating system for all cluster machines, you can create compute machines, which are also known as worker machines, that use RHEL as their operating system.

Actual operating system changes are made in-place on each machine using OpenShift Container Platform manages the operating system like it manages any other container application on the cluster, using network upgrades that keep the operating system servers up-to-date.

Structure

In this chapter, we will discuss the following topics: OpenShift 4.5 Cluster installation

Overview

Set up each of the servers in the cluster with a static IP address Pre-requisites - required machines

Install bind and configure to create a DNS server

Configuring the firewall

Installation downloads

Load balancer HAProxy and NGINX web server installation

Update /etc/hosts file of the HAProxy server Install NGINX and start its service

Bare metal installation

Generating an SSH private key and adding it to the agent

Obtaining the installation program

Installation of the CodeReady Container for OpenShift 4.5.x

Objectives

After studying this unit, you should be able to: Identify the resources required for Red Hat OpenShift 4.5 for a bare metal installation.

Understand the prerequisite disk, memory and network requirements for the CodeReady Container for OpenShift 4.5. Install and configure a layer 4 HAProxy software load balancer and configure it for Load balancing a cluster of web servers.

Install and configure the NGINX Linux web server and configure it for the Ignition and raw boot installation files for OpenShift 4.5.

Search, identify and download the versions of OpenShift 4.x components and understand how to extract and deploy them.

Prepare and install OpenShift 4.5 for a bare metal cluster.

Prepare and install OpenShift 4.5 for the CodeReady container, and have an overview of the OpenShift web administration console.

7.1: OpenShift 4.5 cluster installation

OpenShift 4.5 installation - installing a cluster on vSphere In OpenShift Container Platform version 4.5, you can install a cluster on VMware vSphere infrastructure that you provision. I will use a bare metal installation, which is just the server hardware in most systems, but I have been making use of VMware Workstation Pro 16.0, which has just been released (as of September 2020).

7.1.1: Overview

As a reference video, you should see the Red Hat OpenShift YouTube, which is as follows:

https://www.youtube.com/watch?v=wZYx4_xBSUQ

Also, there is an OpenShift URL blog for a quick start. Reference is as follows:

https://www.openshift.com/blog/openshift-4-bare-metal-installquickstart

7.1.2: Set up each of the servers in the cluster with a static IP address I will set up the static addresses as follows:

follows: follows: follows: follows: follows: follows: follows: follows: follows: follows:

Table 7.1: The list of the servers initially set up for the supporting server cluster

The addresses in the two network cards originally set up in VMware use DHCP, so are allocated dynamically on system startup and can change. Because we need to connect to other VMware servers, I have allocated a fixed IP address, 10.10.10.210 to the second, ens192 card.

For the full procedure for setting up the static address, see the procedure described in Appendix of the publication with the following URL:

https://doi.org/10.13140/RG.2.2.21708.16001

Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator 3.0.6

Disabling the Network Manager DNS auto-configuration

We don’t want the network manager to change the resolv.conf file. To do that, we simply add the following line:

dns=none in the following file:

/etc/NetworkManager/NetworkManager.conf, vi /etc/NetworkManager/NetworkManager.conf

Figure 7.1: The NetworkManager.conf file is edited to set the dns flag

Append

Figure 7.2: The dns=none line is appended as highlighted to the NetworkManager.conf file

And we reload the service as follows: systemctl reload NetworkManager

Figure 7.3: The NetworkManager service is reloaded to establish the configuration change

7.1.3: Prerequisites - required machines

Each cluster machine must meet the following minimum requirements:

requirements: requirements: requirements: requirements: requirements: requirements: requirements: requirements: requirements: requirements: requirements: requirements:

Table 7.2: The size of memory, disk capacity and location, and the CPU processor count

I run VMware Workstation Pro 16.0, on a Windows 10 Pro for Workstations, version 2004 latest version operating system, as the windows administrator, using a server with 64 GB memory, a 1 TB C Drive, and three high speed magnetic drives of 1.8 TB. The CPU is a Xeon 1.8 GHz processer with 8 cores and 16 logical processors.

Figure 7.4: The VMware Workstation Pro 16.0 virtual server application is launched

Accept the pop-up window prompt to run as administrator, and then select the New Virtual Machine… option in the VMware menu item, as shown in the following screenshot:

Figure 7.5: The VMware Workstation menu item is selected for a new virtual server The New Virtual Machine Wizard will be launched.

For the full RHEL 8.0 installation procedure, see the ResearchGate publication, as follows: https://doi.org/10.13140/RG.2.2.21708.16001

Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator 3.0., Pages 15 to 24.

Figure 7.6: The summary list of selected parameters to build the server are displayed

Review the selected parameters, as shown in the preceding screenshot, and click Finish to start the virtual server machine build.

Figure 7.7: The server is booted from the iso file for RHEL 8.0, within the VMware system The build boots the asbbootstrap server for further configuration.

Figure 7.8: The summary of the Red Hat RHEL 8.0 Linux operating system install is shown The installation summary allows some configuration changes to be selected, if required:

Figure 7.9: During the progress of the full installation, the first user can be created

During the install, you can click on the User Creation icon to add one or more users to be created:

Figure 7.10: The wasadm user and password are entered and the Advanced button is clicked

The wasadm user is created and a password set:

Figure 7.11: The wasgrp is added to the wasadm user’s groups in the Advanced User Configuration window

The Advanced… button is used to add a group,

Figure 7.12: The status of the new user can be seen during the installation

The user icon shows that the user wasadm will be created.

Figure 7.13: The Not listed? Option is clicked to allow logon as root

The login page is displayed, I log in using by selecting the Not listed? option. Repeat the preceding steps for the other five VMware servers, asbmaster0 details are shown as follows:

Figure 7.14: The summary of the machine build for the asbmaster0 web server is shown The screen, on boot up, shows the user created for the web server:

Figure 7.15: The logon screen for the first web application server The asbmaster0 server machine is used as a web application cluster server, installed with NGINX:

Figure 7.16: The build parameters for the second Web Application Server in the cluster

The preceding details are part of the web application server cluster, which I am going to configure as a high availability cluster using HAProxy layer 4 load-balancing.

Figure 7.17: The build parameters for the third web application server in the cluster The asbmaster2 server is the third web application server in the HA cluster:

Figure 7.18: The build parameters for the first of the two compute layer servers

The asbworker0 and asbworker1 compute servers are created for the worker cluster:

Figure 7.19: The build parameters for the second of the two compute layer servers You can change the machine name in the Virtual Machine Settings tab after-installation:

Figure 7.20: The second compute server is renamed to asbworker1 To

Figure 7.21: The Virtual machine name can be changed in VMware settings

And then click

Figure 7.22: The six machines are created for building the cluster We have the basic six machines running, ready to build the cluster. Create the static addresses and the DNS server. First, we need to add a second network card to each server listed earlier. The second network card has to be DHCP, giving a “Host” VMware address of since there is no access to the internet otherwise.

Figure 7.23: The VM > Settings menu item is selected to add a second network card Select the VMware machine tab to be updated, and select VM > Settings… from the menu:

Figure 7.24: The Network Adapter hardware is updated using the Add command button Select the Network Adapter device, review the first network card setting, as shown, and click the Add… command button.

Figure 7.25: The Network Adapter option is selected in the Add Hardware Wizard Select Network Adapter in the Add Hardware Wizard pop-up window and click

Figure 7.26: The Host-only option is selected for the second card type

Change the NAT default setting for the Network Adapter 2 card to as highlighted in the preceding screenshot, and click

VMware will reset the machine to incorporate the additional network card. The following command shows the VMware DHCP provides IP address settings for the two cards: ifconfig

Figure 7.27: The ifconfig command shows the highlighted IP addresses set before any changes Repeat the preceding steps, network card addition, for each server machine in the cluster.

7.1.3.1: Resolver configuration changes

The domain I am using is my company domain,

Figure 7.28: The domain, asbsoftware.co.uk, is pinged to give the IP address

To configure the resolv.conf file, the first lines must be:

search asbsoftware.co.uk nameserver 10.10.10.210 nameserver 216.239.38.21 nameserver 192.168.50.2

Figure 7.29: The resolv.conf file is edited using vi to start the DNS server configuration

The resolv.conf file is edited with the following nameserver list:

Figure 7.30: The nameserver list is set up in the resolv.conf file for DNS

This is both in the server and in any client querying this DNS. You need to add a second name server to resolve internet sites or any other domain:

7.1.3.2: Enabling the bind service at startup

Change the host name to the following: su – root

Give our server a name using

Choose the domain name (I have used my company domain name,

(Registered to ASB Software Development

To set a Fully Qualified Domain Name

hostnamectl set-hostname asbbootstrap.asbsoftware.co.uk

Run the Subscription Manager for Red Hat RHEL 8.0.

The reference link is as follows: https://doi.org/10.13140/RG.2.2.21708.16001

Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator 3.0.6, Pages 31 to 35, Installation of RHEL 8.0 on VMware

Workstation Pro

Once the base OS is installed, install Extra Packages for Enterprise Linux

yum -y install https://dl.fedoraproject.org/pub/epel/epel-releaselatest-$(rpm -E %rhel).noarch.rpm

Figure 7.31: The log output from the installation of the EPEL package

7.1.4: Install bind and configure to create a DNS server

The full procedure is described in the following link: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Pages 46 to 60, Install bind and configure to create a DNS Server. This section is only applied to the Bootstrap server using the following command:

dnf install bind bind-utils

The bind and bind-utils packages for DNS are installed for the asbbootstrap server.

7.1.4.1: Enabling the bind service at startup

Make sure the DNS service is started with the system: systemctl enable named

7.1.4.2: Configuration for a Single DNS server

A primary or single DNS server is authoritative for a domain, but we have no high availability, and therefore if it is down or unreachable, no DNS query for the domain will work, unless cached or duplicated in the static file

Edit the file vi /etc/named.conf

Change the named.conf file to the following:

listen-on port 53 {127.0.0.1;

port 53 {::1;};

allow-query {localhost; recursion no;

Don’t forget to comment out the line //listen-on-v6 port 53 {::1;};

Figure 7.32: The line has been commented out (second line down from the options tag)

The recursion no; option makes sure the DNS will not always give an answer to a particular query, but will delegate to the root servers if necessary, for any unknown names or IP addresses. So, an authoritative server must not be recursive.

Afterwards we have to specify the zone files.

For this, we will configure a forward zone (to resolve to an IP from a name) and a reverse zone (to resolve to a name given an IP address) each in its specific file, by appending lines to the file

Next, we need to create the files forward.zone and The .zone files are inside the directory

Our /var/named/forward.zone file will contain: $TTL  1D @   IN SOA asbbootstrap.asbsoftware.co.uk. root.asbsoftware.co.uk. ( 2020091500 ; serial 3h         ; refresh 15         ; retry 1w         ; expire 3h         ; minimum )

IN  NS asbbootstrap.asbsoftware.co.uk. asbbootstrap  IN  A  10.10.10.210 And the reverse.zone file:

$TTL  1D @   IN  SOA asbbootstrap.asbsoftware.co.uk. root.asbsoftware.co.uk. ( 2020091500 ; serial 3h         ; refresh 15         ; retry 1w         ; expire 3h         ; minimum ) IN  NS  asbbootstrap.asbsoftware.co.uk. 210   IN  PTR  asbbootstrap.asbsoftware.co.uk

So, to summarize, we have created the two zone files, shown as follows, for the DNS system to work correctly:

Figure 7.33: The list of the two zone files we have now created using the vi editor Here root.asbsoftware.co.uk is the e-mail address and 2020091500 is a serial field for tracking any change in the zone file and, by

convention, is in the form where ss is a two-digit number. In the reverse file, the last line is different. PTR defines a reverse lookup, which will resolve to it is only required for the last digit 210 to be entered, which identifies the host (for Class C address, /24 that is, the netmask is Now, we make sure we have the correct file permissions: chgrp named /var/named/reverse.zone chgrp named /var/named/forward.zone

To check that the zone files are correctly configured, you can issue the following commands: named-checkzone asbsoftware.co.uk /var/named/forward.zone Also, we check the reverse.zone file: named-checkzone 10.10.10.210 /var/named/reverse.zone

And to verify the overall configuration: named-checkconf -v If everything’s fine, we can start the service:

systemctl start named The preceding command starts the service, and the following command checks the status of the running DNS service:

systemctl status named.service

Figure 7.34: The status running the systemctl status named.service command

Next, we edit the /etc/hosts file (as a backup for IP resolution!):

Figure 7.35: The /etc/hosts file, edited with our cluster of servers

Edit the /etc/hosts file, as shown in the preceding screenshot, for each server. The settings for the network card, ens192 are changed to set the DNS IP to the server static IP: reboot

7.1.5: Configuring the firewall

The firewall has to be enabled for the DNS service: firewall-cmd --permanent --zone=public --add-service=dns firewall-cmd –reload

7.1.5.1: Edit for the subscription and the networks for other cluster servers Next, we create the Red Hat subscriptions using subscription manager, and edit the network settings for static addresses for each of the other 5 VMware servers, as follows (I have used asbmaster0.asbsoftware.co.uk as an example server):

server): server): server): server): server): server): server): server):

Table 7.3: The list of servers we are using to test the cluster

To set a FQDN:

hostnamectl set-hostname asbmaster0.asbsoftware.co.uk hostnamectl

Figure 7.36: The server host name is updated using the hostnamectl command Run the Subscription Manager for Red Hat RHEL 8.0:

The full procedure is shown in the publication in the following link:

https://doi.org/10.13140/RG.2.2.27358.18246 IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Pages 67 to 72, Subscription Manager

We have to register the system to continue the RHEL 8 installation, we do it now by applying the following command as the root user. This can be completed in one step by using the following command:

subscription-manager register --username --password --auto-attach

Once the base OS is installed, install EPEL: yum -y install https://dl.fedoraproject.org/pub/epel/epel-releaselatest-$(rpm -E %rhel).noarch.rpm Change the configuration file for the ens192 card to set BOOTPROTO=static and the Edit the /etc/hosts file. Append the following: 10.10.10.210 asbbootstrap asbbootstrap.asbsoftware.co.uk 10.10.10.215 asbmaster0 asbmaster0.asbsoftware.co.uk 10.10.10.220 asbmaster1 asbmaster1.asbsoftware.co.uk 10.10.10.225 asbmaster2 asbmaster2.asbsoftware.co.uk 10.10.10.230 asbworker0 asbworker0.asbsoftware.co.uk 10.10.10.235 asbworker1 asbworker1.asbsoftware.co.uk These are my examples; you need to substitute your own server names and IP addresses. Reboot the system. Repeat section 7.1.5 for each server in the table at the beginning of this section, using the appropriate server name and IP address.

The hostnamectl and Subscription Manager commands are run for the second, asbmaster1 server. The hostnamectl and Subscription Manager commands are used to set the name of the third web application server in the cluster,

The hostnamectl and Subscription Manager commands are used to set the server’s name and register it with the online RedHat subscription database. The hostnamectl and Subscription Manager commands are run for the asbworker1 server. Backup the six virtual servers in the VMware system. Shutdown now.

7.2: Installation Downloads

Next, install ansible and then clone the following repository: yum -y install ansible git

You should get a log similar to the following in the command window response (I have truncated the output to show the summary of the installation expected): Transaction Summary Install 41 Packages Total download size: 33 M Installed size: 173 M Downloading Packages: (1/41): python3-bcrypt-3.1.6-2.el8.1.x86_64.rpm 376 kB/s | 44 kB  00:00 …etc (41/41): perl-Pod-Usage-1.69-395.el8.noarch.rpm 222 kB/s | 34 kB  00:00 -------------------------------------------------------------------------------Total                                           5.1 MB/s | 33 MB  00:06 warning: /var/cache/dnf/epel-fafd94c310c51e1e/packages/ansible2.9.13-1.el8.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID 2f86d6a1: NOKEY

Extra Packages for Enterprise Linux 8 - x86_64  1.6 MB/s | 1.6 kB  00:00 Importing GPG key 0x2F86D6A1: Userid     : "Fedora EPEL (8) " etc Installed: ansible-2.9.13-1.el8.noarch

… ETC…. perl-Term-Cap-1.17-395.el8.noarch perl-Pod-Usage-4:1.69-395.el8.noarch

Complete! [root@asbbootstrap ~]#

7.2.1: Load balancer HAProxy and NGINX web server installation

In order to load the files for installation, it is required that there is a web browser and a front-end, layer 4, load balancer. The installation of which stands for High Availability is described. This is a free and open-source load balancer tool, which allows the distribution of the incoming traffic and across the backend servers based on a configuration file.

HAProxy can be run on Linux and is usually used to improve the performance and reliability of a server environment by distributing the workload across multiple servers (for example, web, application, database). It is used in many high-profile environments, such as GitHub, Instagram, and Twitter.

In this chapter, we will cover the overview of what HAProxy is, the load-balancing terminology, and an installation example.

7.2.1.1: Layer 4 load balancing

The easiest way for load balancing the network traffic to multiple web application servers is to use layer 4 (transport layer) load balancing. Load balancing, using this method, uses the configuration of the IP range and port (that is, if a request comes in for an http web address, the traffic will be forwarded to the backend that handles all the requests for the domain on my system] on port The user accesses the load balancer, which forwards the user’s request to the web application group of backend servers servers). Whichever backend server is selected, will respond directly to the user’s request. All of the servers in the back-end should be serving identical content, otherwise the user might receive inconsistent content (unless sticky sessions are selected, which then locks an http session to one server; for details, see section

So, HAProxy is used to provide fault tolerance and high availability in the case, where one node is getting too many concurrent requests. It is used (using the Layer 7 option) by very large web sites like GitHub and Twitter. Layer 4 load balancing is suitable for small web site load balancing.

7.2.1.2: Sticky Sessions

Some applications require a user to stay connected to the same backend server. This persistence is achieved through sticky sessions, using the appsession parameter in the backend that requires it.

In this section, we describe the installation and configuration of HAProxy on a RHEL 8 server for forwarding to Nginx backend web servers. Following are the details for the HAproxy development environment:

HAProxy Server – 10.10.10.210 server)

Nginx Server 1 – 10.10.10.215

Nginx Server 2 – 10.10.10.220

Nginx Server 3 – 10.10.10.225

The following procedure, described in section 7.2.2 below, covers the installation and configuration steps of the HAProxy server on RHEL 8.

7.2.2: Update /etc/hosts file of the HAProxy server

The following are example cluster server names and IP addresses which you should substitute with your own configuration.

Login to the asbbootstrap RHEL 8 system to install HAproxy, and check that the following lines are in the /etc/hosts file (they should already be configured): 10.10.10.210 asbbootstrap asbbootstrap.asbsoftware.co.uk 10.10.10.215 asbmaster0 asbmaster0.asbsoftware.co.uk 10.10.10.220 asbmaster1 asbmaster1.asbsoftware.co.uk 10.10.10.225 asbmaster2 asbmaster2.asbsoftware.co.uk 10.10.10.230 asbworker0 asbworker0.asbsoftware.co.uk 10.10.10.235 asbworker1 asbworker1.asbsoftware.co.uk

The following sub-set of the preceding cluster is used for the configuration example:

10.10.10.210    asbbootstrap 10.10.10.215    asbmaster0 10.10.10.220    asbmaster1 10.10.10.225    asbmaster2 HAproxy package is available in the default package repositories of RHEL 8, so it can be easily installed with the dnf command. But

it is recommended to update the system before installing HAproxy. So, execute the following command:

dnf update -y

This may take some time, I had 1498 items to be updated!

Figure 7.37: The updated RHEL 8.0 system with the installed packages after applying the dnf update -y command

reboot

After rebooting, the HAproxy software system can be installed:

dnf install haproxy

Figure 7.38: The install log showing the install of the HAproxy load balancer software

Once the HAproxy is installed successfully, configure it by editing its configuration file Before editing the file, it is always a good practice to make a backup of original file; run the following command:

[root@asbbootstrap ~]# cd /etc/haproxy/ [root@asbbootstrap haproxy]# cp haproxy.cfg haproxy.cfg_bck [root@asbbootstrap haproxy]# Reference link is as follows:

https://www.haproxy.org/download/1.8/doc/configuration.txt

In the configuration file, we will modify two sections frontend and In the frontend section, we define the HAproxy IP and its port, the static URL, and the backend name. In the backend section, we define the type of load balance algorithm that we will use, like round robin and least connection, and so on, and backend server’s name, IPs and port; the example is shown as follows: [root@asbbootstrap haproxy]# vi haproxy.cfg ………………… frontend http_balancer bind 10.10.10.210:80, 10.10.10.210:443 option http-server-close option forwardfor stats uri /haproxy?stats

#  acl url_static  path_beg  -i /static /images /javascript /stylesheets #  acl url_static  path_end  -i .jpg .gif .png .css .js #  use_backend static  if url_static

backend nginx_webservers mode  http balance roundrobin option httpchk HEAD / HTTP/1.1\r\nHost:\ localhost server  asbmaster0  10.10.10.215:80  check server  asbmaster1  10.10.10.220:80  check server  asbmaster2  10.10.10.225:80  check Configure rsyslog so that it stores all HAProxy statistics, edit rsyslog config file "/etc/rsyslog.conf" and uncomment line 19 and 20, [root@asbbootstrap ~]# vi /etc/rsyslog.conf …… module(load="imudp") input(type="imudp" port="514") …… Now create haproxy.conf file for paste the following lines: [root@asbbootstrap ~]# vi /etc/rsyslog.d/haproxy.conf local2.=info  /var/log/haproxy-access.log local2.notice  /var/log/haproxy-info.log Save and exit the file.

Restart and enable rsyslog service, so that it will be available across the reboots: [root@asbbootstrap ~]# systemctl restart rsyslog [root@asbbootstrap ~]# systemctl enable rsyslog Now, finally start haproxy service, but before starting the service, set the following selinux rule: [root@asbbootstrap ~]# setsebool -P haproxy_connect_any 1 Start and enable the HAproxy service, using the following systemctl commands: [root@asbbootstrap ~]# systemctl start haproxy [root@asbbootstrap ~]# systemctl enable haproxy

Allow the HAproxy ports (in our case it is 80 and in the OS firewall, execute the firewall-cmd command: [root@asbbootstrap ~]# firewall-cmd --permanent --add-port=443/tcp [root@asbbootstrap ~]# firewall-cmd --permanent --add-port=80/tcp [root@asbbootstrap ~]# firewall-cmd --reload

HAProxy installation and configuration is now complete, now the Nginx web application nodes need to be configured.

7.2.3: Install NGINX and start its service

Login to all three nginx nodes, install nginx and start the nginx service, using the following commands:

# dnf install nginx -y # systemctl start nginx # systemctl enable nginx

Figure 7.39: The install log showing the install of the Nginx web application software

The preceding screenshot shows the list of Nginx packages that are installed.

Figure 7.40: The start and enable commands of systemctl to start the nginx web application

The preceding screenshot shows the commands used to automatically start and enable (for reboot) the nginx web application service on the first server of the three server cluster,

The nginx service is next installed on the second server,

Figure 7.41: The installed packages of the nginx service

The next step on the asbmaster1 server shows the commands used to automatically start and enable (for reboot) the nginx web application service on the second server of the three server cluster,

Figure 7.42: The second server’s Nginx web application service is started

The preceding step is next repeated on the third web application server, shown as follows:

Figure 7.43: The Nginx web application service is installed on the third server of the cluster

The final step on the asbmaster2 server shows the commands used to automatically start and enable (for reboot) the nginx web application service on the third server of the three-server cluster,

Figure 7.44: The third server’s Nginx web application service is started Allow Nginx port and in the OS firewall in all the master servers using the following commands: firewall-cmd --permanent --add-service=http

firewall-cmd --permanent --add-service=https firewall-cmd --reload

7.2.3.1: Test the HAProxy is working correctly

Login to HAproxy server and run the curl command to see whether traffic is distributed in a round-robin way, which can be verified by viewing the log file

[root@asbbootstrap ~]# curl 10.10.10.210

Figure 7.45: The curl command returns the http index.html expected from the asbmastern servers Returns the default index.html page from a master server. Also, we can verify the output from the web browser too:

http://10.10.10.210

Figure 7.46: The browser url returns the http index.html expected from the asbmastern servers

The preceding screenshot confirms that the HAProxy has been configured successfully on the RHEL 8 servers. You can view the status of the HAProxy server through a web browser, type url : In our case, the URL will be

Figure 7.47: The HAProxy load balancer statistics for the web cluster can be loaded in a browser

We can also view the HAProxy statistics from log file tail -f /var/log/haproxy-access.log

Figure 7.48: Shows the haproxy-Load balancer access.log for the web application cluster of servers The highlighted server names in the preceding screenshot show that the HAProxy front end is applying the round-robin to each backend Nginx web application server in turn.

7.3: Bare metal installation

The full procedure to follow for a Red Hat OpenShift 4.5 Bare Metal installation is covered using the URL:

https://access.redhat.com/documentation/enus/openshift_container_platform/4.5/html/installing_on_bare_metal/in stalling-on-bare-metal

7.3.1: Generating an SSH private key and adding it to the agent

If you want to perform installation debugging or disaster recovery on a cluster, you must provide an SSH key to both the ssh-agent and to the installation program. In a production environment, you require disaster recovery and debugging.

You can use the key to SSH into the master nodes as the user core. When you deploy the cluster, the key is added to the core user’s ~/.ssh/authorized_keys list. You must use a local key: Procedure

If you do not have an SSH key that is configured for passwordless authentication on your computer, create one. For example, on a computer that uses a Linux operating system, run the following command:

ssh-keygen -t rsa -b 4096 -N '' \ -f /

Specify the path and file name, such as of the SSH key. Do not specify an existing SSH key, as it will be overwritten. ssh-keygen -t rsa -b 4096 -N '' \ -f ~/.ssh/id_rsa

Figure 7.49: Shows the generation of the ssh key we need to install the bare metal installation of OpenShift 4.5 Running this command generates an SSH key that does not require a password in the location that you specified. Start the ssh-agent process as a background task: $ eval "$(ssh-agent -s)"

This gives the example output below: Agent pid 10359

Add your SSH private key to the ssh-agent that we started in Step

ssh-add ~/.ssh/id_rsa

Specify the path and file name for your SSH private key, such as This gives similar output in outline, as follows:

Identity added: /home/// ()

Figure 7.50: The ssh key is added to the ssh agent process

When you install OpenShift Container Platform, provide the SSH public key to the installation program. If you install a cluster on infrastructure that you supply, you must provide this key to the cluster’s servers.

7.3.2: Obtaining the installation program

Before you install OpenShift Container Platform on the RHEL 8.0 Linux system, download the installation file on a local computer.

Prerequisites

You need 500 MB of local disk space to download the installation program. Procedure

Access the following URL on the Red Hat OpenShift Cluster Manager site:

https://cloud.redhat.com/openshift/install

This will prompt you to log into RedHat with your account.

(Also scroll down and select the Run it yourself section

Run OpenShift clusters on your own by installing from another cloud provider.

and then select

Platform stack automation and pre-existing infrastructure link option)

See Chapter 4, On-Premise Server Configurations and Section 4.17, RedHat OpenShift 4.x Download and

Figure 7.51: The downloaded files for installation of the OpenShift 4.5 Client and server The downloaded OpenShift4.5 Client and Install files that are stored with the pull-secret.txt file, which we need in order to configure the install_config.yaml file. To copy these files, we need to set up a VMware shared folder.

The Add Shared Folder wizard is invoked.

Figure 7.52: The browse button is used to navigate to the Installs folder for sharing

Select the Installs folder, where we will place all the required installation files we downloaded.

The wizard process is followed; click Finish to complete the shared folder mapping to the VMware Linux device,

Then we click OK and the shared folder is now accessible to the root user for copying. As can be seen in the following screenshot, this folder is added dynamically, so we don’t need to log out (or reboot):

Figure 7.53: The new shared Installs folder is found on the VMware mount /mnt/hgfs

Figure 7.54: The openshift installation software is copied from the shared folder The OpenShift 4.5 installation for bare metal can now be copied to our asbbootstrap server in the installation path created as follows: cd /opt ls mkdir installs cd installs mkdir openshift4.5

cd openshift4.5 cp /mnt/hgfs/Installs/openshift-install-linux.tar.gz . tar -zxvf openshift-install-linux.tar.gz

Figure 7.55: The installation file is copied and unpacked to give the files listed From the following URL:

https://cloud.redhat.com/openshift/install/pull-secret We can get the download page on the Red Hat OpenShift Cluster Manager site, and we can download the installation pull secret as a .txt file. This pull secret allows authentication with the services that are required, with the included authorities, including which serves the container images for OpenShift Container Platform components. See Chapter 4, On-Premise Server Configurations and Section 4.17, RedHat OpenShift 4.x Download and

7.3.2.1: Installing the CLI by downloading the binary

Now, the OpenShift CLI must be installed in order to interact with OpenShift Container Platform from a command-line interface. This client can be installed on Linux, Windows, or macOS.

7.3.2.2: Installing the CLI on Linux

The following procedure can be used to install the OpenShift CLI binary on our Linux, asbbootstrap server. See Chapter 4, OnPremise Server Configurations and

Also, the full procedure on:

https://access.redhat.com/documentation/enus/openshift_container_platform/4.5/html/installing_on_bare_metal/in stalling-on-bare-metal

Reference: 1.1.7. Installing the CLI by downloading the binary.

Place the oc binary in a directory that is on your PATH environment variable folder path list:

Figure 7.56: The oc binary is copied into the /usr/local/bin folder

To check your execute the following command:

echo $PATH

After you install the CLI, it is available using the oc command:

oc

Repeat for

Figure 7.57: The kubectl binary is copied to the /usr/local/bin folder

7.3.2.3: Update the /etc/hosts file

[root@asbbootstrap ocp-install]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.10.10.214 bootstrap.ocp4.asbsoftware.co.uk 10.10.10.210 asbbootstrap asbbootstrap.asbsoftware.co.uk asbbootstrap.ocp4.asbsoftware.co.uk 10.10.10.216 master0.ocp4.asbsoftware.co.uk 10.10.10.215 asbmaster0 asbmaster0.asbsoftware.co.uk 10.10.10.218 master1.ocp4.asbsoftware.co.uk 10.10.10.222 master2.ocp4.asbsoftware.co.uk 10.10.10.224 worker0.ocp4.asbsoftware.co.uk 10.10.10.226 worker1.ocp4.asbsoftware.co.uk 10.10.10.220 asbmaster1 asbmaster1.asbsoftware.co.uk 10.10.10.225 asbmaster2 asbmaster2.asbsoftware.co.uk 10.10.10.230 asbworker0 asbworker0.asbsoftware.co.uk 10.10.10.235 asbworker1 asbworker1.asbsoftware.co.uk

Run the GitHub clone to download the Red Hat OpenShift 4 helper repository: git clone https://github.com/RedHatOfficial/ocp4-helpernode cd ocp4-helpernode

Figure 7.58: The Redhat OpenShift 4 helper repository is downloaded from GitHub

cd /root mkdir ocp-install cd ocp-install

Generate SSH private key and add it to the agent. Create an SSH private key, which will be used to SSH into the master and bootstrap nodes as the user core. The key is added to the core users’ ~/.ssh/authorized_keys list through the ignition files.

ssh-keygen -t rsa -b 4096 -N '' -f installer Verify if ssh-agent is running, or otherwise start the ssh-agent as a background task: eval "$(ssh-agent -s)"

The following results show the rsa key’s randomart image:

Figure 7.59: The ssh-keygen command is run to create a public/private rsa key pair Add the SSH private key to the ssh-agent using: ssh-add installer

Figure 7.60: The SSH private key is added to the installer Generate ignition configuration files Ignition is a tool for configuring the system, during the start of the boot process, before the operating system starts. This includes writing files (files, systemd components, networkd services, and so

on) and user configuration. It only runs once (during the first boot). OpenShift 4 installer generates three ignition config files to prepare the node as an OpenShift for bootstrap, master, and worker nodes. From within the working directory (in this example, it’s generate the ignition configurations. Full details of the procedure are in the following link: https://access.redhat.com/documentation/enus/openshift_container_platform/4.5/html/installing_on_bare_metal/in stalling-on-bare-metal Reference: 1.2.11. Creating the ignition config files Run the following command to create the install-config.yaml file, as shown below:

cat install-config.yaml apiVersion: v1 baseDomain: asbsoftware.co.uk compute: - hyperthreading: Enabled name: worker replicas: 0 controlPlane: hyperthreading: Enabled name: master replicas: 3

metadata: name: ocp4 networking: clusterNetworks: - cidr: 10.254.0.0/16 hostPrefix: 24 networkType: OpenShiftSDN serviceNetwork: - 172.30.0.0/16 platform: none: {} pullSecret: '$(< /root/ocp-install/pull-secret.txt)' sshKey: '$(< /root/ocp-install/installer.pub)' EOF

The following command is used to generate the ignition configuration files: ./openshift-install create ignition-configs -dir=/opt/installs/openshift4.5/asbClusterInstall Creating ignition config will result in the removal of the installconfig.yaml file. Make a backup of install-config.yaml before creating ignition configs. You may have to recreate a new one if you need to re-create the ignition config files. Copy the .ign file to the Nginx webservers we created earlier. From the bootstrap: cp *.ign /mnt/hgfs/Installs

Figure 7.61: The ignition files are copied to the shared Installs folder for install on the web application server and from the web server:

cp /mnt/hgfs/Installs/*.ign /var/www/html/ignition-install/

Figure 7.62: On the web application server, copy the ignition files from the shared Installs Give required permissions as follows, otherwise, it will not work:

Figure 7.63: The uploaded ignition files are moved to a new web ignition-install folder

chmod o+r /usr/share/nginx/html/ignition-install/*.ign

Figure 7.64: The ignition file permissions are updated using the chmod command Before we begin installing RHCOS in bootstrap and master nodes, make sure the following files are available in the webserver: bootstrap.ign master.ign rhcos.-metal.x86_64.raw.gz

worker.ign

These are shown in the following screenshot:

Figure 7.65: The installation files must be present on the web application server

Download the RHCOS iso file.

Download the RHCOS 4.5.2 iso from the following link: https://mirror.openshift.com/pub/openshiftv4/x86_64/dependencies/rhcos/4.5/latest/

Install the RHCOS machines:

bootstrap master0

master1 master2

worker0

worker1 Detailed VMware creation screen examples can be found at Appendix B of

https://doi.org/10.13140/RG.2.2.21708.16001

Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator 3.0.6, Pages 15 to 24, Installation of RHEL 8.0 on VMware Workstation Pro.

Figure 7.66: The build parameters for the master1 server can be reviewed, then click Finish The build parameters for the bare metal server are reviewed and Finish is clicked:

Figure 7.67: The master1 VMware machine is built but not yet powered on

The VMware master1 machine has not been started yet; we need it to boot from the CDROM device we pointed to for the installer operating system for Red Hat OpenShift 4.5.6. Set BIOS to point to the CDROM on boot.

Figure 7.68: The VMware Power On to Firmware is required to configure the BIOS for boot

Select the VM > Power > Power On to so that we can change the BIOS boot order:

Figure 7.69: The Select Menu right-arrow key is used to move to the Boot tab

Use the Select Menu option to move from Main to the Boot tab:

Figure 7.70: The down-arrow key is used to select CD-ROM drive as the boot device Select the CD-ROM Drive to boot from:

Figure 7.71: The F10 Key is used to save the changes, and the Enter key starts the boot Click the F10 key, and then the Enter key to run the VMware boot:

Figure 7.72: The RHEL CoreOS Installer screen appears, click the Tab key to enter the Ignition Commands. Click the Tab key to show the screen, where we enter the ignition commands. At the prompt leave a single space and enter the highlighted text as follows: For

coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http:// 192.168.50.144/ignition-install/rhcosmetal.x86_64.raw.gz coreos.inst.ignition_url=http://192.168.50.144/ignitioninstall/bootstrap.ign ip= 10.10.10.214::10.10.10.210:255.255.255.0:bootstrap.ocp4.asbsoftware.co.u k:enp63s0:none nameserver=10.10.10.210 nameserver=216.239.38.21 Unfortunately, this has to be manually typed into the VMware prompt (and with no carriage returns)! For master (0,1 and 2) 10.10.10.216 master0.ocp4.asbsoftware.co.uk 10.10.10.218 master1.ocp4.asbsoftware.co.uk 10.10.10.222 master2.ocp4.asbsoftware.co.uk

Change the IP 10.10.10.NNN and master number from the preceding list: coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http://192.168.50.144/ignition-install/rhcosmetal.x86_64.raw.gz coreos.inst.ignition_url=http://192.168.50.144/ignition-install/master.ign nameserver=10.10.10.210 nameserver=216.239.38.21

For worker (0 and 1) 10.10.10.224 worker0.ocp4.asbsoftware.co.uk 10.10.10.226 worker1.ocp4.asbsoftware.co.uk

Change the IP 10.10.10.NNN and workern from the preceding list: coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http://192.168.50.144/ignition-install/rhcosmetal.x86_64.raw.gz coreos.inst.ignition_url=http://192.168.50.144/ignition-install/worker.ign nameserver=10.10.10.210 nameserver=216.239.38.21

Figure 7.73: The Ignition commands are typed into the boot screen

If you make a mistake, as I did here, then the prompt will come back again on reboot.

Figure 7.74: The bootstrap.ign Ignition file is found on the web server and is processed The second time was and the preceding screenshot shows the download of the main images.

Figure 7.75: The internet IP addresses created are shown after boot

Repeat the preceding installation steps for worker0 and

7.4: Installation of the CodeReady Container for OpenShift 4.5.x

As you will have seen in the previous sections, the installation of OpenShift 4.5 on a bare metal, on-premise system, involves quite a few separate installation procedures, and for VMware, a manual keyed entry for each server machine in the cluster, which can easily introduce installation failures.

I wanted a fast installation, so I could investigate and test the features available in OpenShift without having to spend several days preparing, installing, and configuring the system!

This section covers a procedure, which can be used to get a single virtual Linux server installation up and running with a functional Red Hat OpenShift 4.5 system in less than a day.

Red Hat CodeReady Containers allow a minimal OpenShift 4 cluster to be very quickly installed on a single Linux server.

This cluster provides a single server environment for development and testing purposes only.

Reference link is as follows: https://access.redhat.com/documentation/enus/red_hat_codeready_containers/1.16/html/getting_started_guide/inst

allation_gsg

You need to download the Linux version (used in our procedure) using the link as follows:

https://cloud.redhat.com/openshift/install/crc/installer-provisioned

The preceding link requires a Red Hat account to log in.

Figure 7.76: The browser page from Red Hat showing the download links highlighted for CRC CodeReady Containers

Clicking on the Linux qualified, Download Code-Ready Containers causes the following file to be downloaded:

Figure 7.77: The zipped CRC installation file is downloaded from the browser

Reference link is as follows: https://access.redhat.com/documentation/enus/red_hat_codeready_containers/1.16/html/getting_started_guide/ind ex CodeReady Containers includes the crc command-line interface to interact with the CodeReady Containers and requires the following system resources:

4 virtual CPUs

9 GB of free memory

35 GB of storage space I found that the aforementioned minimums did not support the web server access to display the Administration Console, so I have used the following:

10 virtual CPUs 20 GB of free memory 500 GB of storage space

Figure 7.78: The New Virtual single server required for the OpenShift 4.5.9 Code Ready Container system hostnamectl set-hostname crc_openshift.asbsoftware.co.uk hostnamectl

Figure 7.79: The hostnamectl command is used to name the server as crc_openshift

The preceding screenshot shows the hostname that I have set as crc_openshift for this Linux install server.

Figure 7.80: The Red Hat subscription-manager command is used to register the server

The system has to be registered using Subscription Manager, shown as follows:

Figure 7.81: The crc-linux-amd64.tar.xz file is copied from the downloaded file in the Installs shared folder into the Linux server install directory.

The server is mapped with a shared Installs folder, and the crc install software is copied from the Installs shared folder to the Linux server:

Figure 7.82: The CodeReady Container installation file is unpacked

The compressed tar file is extracted to unpack the crc software:

Delete any existing CodeReady Containers virtual machine:

crc delete can result in the data loss in the existing CRC containers, so remember to save any required data stored in the virtual machines before running the command.

Replace the earlier crc binary with the latest release version. Verify that the new crc binary is in use by checking its version:

crc version Set up the new CodeReady Containers release:

Figure 7.83: The ./crc version command is run to display the versions of CRC and OpenShift, and then the ./crc setup command is run to start the unpacking for the installation

The unpack takes a while to complete:

Figure 7.84: The message requires us to run as a non-root user

First, I tried to run as but the preceding error states step has to be run as a non-root user.

Figure 7.85: The install is copied to /home/wasadm and unpacked to run as non-root user wasadm

The preceding install was extracted and run as but this also had an issue.

Figure 7.86: The Virtual server BIOS virtualization setting has to be set

The virtualization has to be set in the BIOS, which can be done from VMware settings, but you have to stop the server first and then set, as shown in the following screenshot:

Figure 7.87: The Virtualize Intel VT-x/EPT or AMD-V/RV1 VMware flag is ticked in the Settings window for the Linux server we are using

The server can then be restarted, and then you can use the following command:

./crc setup

Figure 7.88: The Installation of CRC now runs after the check, we are now prompted to enter the sudo password for wasadm The password for wasadm is then entered, as shown in the preceding screenshot.

Figure 7.89: The CRC setup completes, so we can now start the OpenShift virtual cluster created

The preceding screenshot shows that the setup program ran without any errors. We can now use the following command to start the system:

./crc start

Start the new CodeReady Containers virtual machine:

Figure 7.90: The Image pull secret text has to be cut and paste into the window, so that the full installation can be completed We then cut and paste the pull secret, as shown in the preceding screenshot, from the pull-secret.txt file and press

Figure 7.91: The process starts the download of 9.86 GB of container files The installation process pulls 9.86 GB of containers down for installation. This may take a few minutes (even on a fiber broadband):

Figure 7.92: The crcqcow2 software download shows the percentage completed of the 9.86 GB The bundle is pulled from the network using the pull secret pasted in the preceding screenshot, copied from the text file:

Figure 7.93: The next step of the process creates the CodeReady Containers VM

The next step creates the CodeReady containers for OpenShift 4.5.9.

Figure 7.94: The Cluster is now ready to start and can be tested on completion The screen displays the following information; I have highlighted the URLs and login information, which is required to be recorded for later use:

INFO Starting OpenShift cluster … [waiting 3m] INFO Updating kubeconfig

WARN The cluster might report a degraded or error state. This is expected since several operators have been disabled to lower the resource usage. For more information, please consult the documentation. Started the OpenShift cluster To access the cluster, first set up your environment by following 'crc oc-env' instructions.

Then you can access it by running oc login -u developer -p developer

To login as an admin, run oc login -u kubeadmin -p duduwyPT9Z-hsUpq-f3pre

To access the cluster, first set up your environment by following crc oc-env instructions. The preceding system specific output should be noted for use of the OpenShift 4.5.9 system as highlighted.

You can now run crc console and use these credentials to access the OpenShift web console:

Figure 7.95: The ./crc oc-env command is run to set the environment variables

[wasadm@crc_openshift crc-linux-1.16.0-amd64]$ ./crc oc-env export PATH="/home/wasadm/.crc/bin/oc:$PATH" Run the following command to configure the shell:

eval $(./crc oc-env) [wasadm@crc_openshift crc-linux-1.16.0-amd64]$

oc login -u kubeadmin -p duduw-yPT9Z-hsUpq-f3pre https://api.crc.testing:6443

Figure 7.96: The command eval $(./crc oc-env) is run (not as documented, without the ./ which fails)

The environment is set up using the preceding command.

Figure 7.97: The OpenShift oc command can now be used to log in Then, as shown in the preceding screenshot, the oc command is used, which shows that we have access to 57 projects for testing:

Figure 7.98: The web browser can now be used to log into the OpenShift Container Platform administrator console

The admin user command loads the browser login, as shown in the preceding screenshot. (The system specific password on our sandboxed system is duduw-yPT9Z-hsUpq-f3pre taken from the output displayed in Figure 7.97: The OpenShift oc command can now be used to log

Figure 7.99: The OC Administrator console is running as expected The administration console is now available for use:

Figure 7.100: The OC Administrator console shows the Active projects available

Conclusion

In this chapter, we covered the installation procedure for a full OpenShift 4.5 cluster set-up, the installation of the CodeReady Container 4.5.9 system, and we demonstrated the loading of the OpenShift administration console in a web browser. We also covered the installation of a DNS server with configuration for the cluster, the supply of the required Nginx web server system, with installation and configuration of an HAProxy, layer 4, load balancer. In Chapter 8, IBM Cloud Private we will describe the step-by-step installation of IBM Cloud Private, including the set-up of the supporting RHEL 8.0 Linux Operating system and the Docker sub system.

Points to Remember

Ensure you have a current Red Hat developer user account to log into for the download of the OpenShift 4.x installation files, and the pull-secret.txt file, required for installation.

When you install OpenShift Container Platform, provide the SSH public key to the installation program. If you install a cluster on infrastructure that you supply, you must provide this key to the cluster’s servers. The CRC, CodeReady Container system must be installed as a non-root user.

The CRC, CodeReady Container system, must be run using the BIOS virtualization setting on the VMware server host.

Select the latest base product version supported for your target environment and download it from the Red Hat OpenShift mirror site nearest to you.

Search and download the latest OpenShift 4.5.x images via FTP/HTTP download (this is usually cumulative) to ensure the maximum stability of the deployment.

Ensure there is a local system, functional web application server, such as Nginx, to allow RHCOS first boot deployment to pull the ignition configuration files you generate and the required install file.

Ensure all the required network service ports are opened through for access by the servers you supply.

Multiple Choice Questions

Which layer of an OpenShift 4.x cluster can’t make use of RHEL 8.0 installed servers?

The control layer

The compute layer The bootstrap layer

The worker layer

Which of the following ignition file names is required to configure the compute layer?

bootstrap.ign

master.ign

worker.ign compute.ign

What prerequisite software service application systems are required before installing an OpenShift 4.5 cluster?

Just a Nginx web application server

Just a HAProxy layer 4 load balancer

Nginx and HAProxy load balancer

Nginx, DNS server, and an HAProxy load balancer

The CodeReady Container OpenShift 4.5.9 system requires: At least 6 Servers, Bootstrap x 1, Control Layer x3 Compute layer x 2 At least 2 servers, Bootstrap x 1, and Control Layer x 1

One Server set with a standard Operating system One server set with the virtualization BIOS flag

Multiple Choice Answers

a. The control layer c. worker.ign

d. Nginx, DNS server, and an HAProxy load balancer

d. One server set with the virtualization BIOS flag

Questions

Which of the two installation options, OpenShift 4.5 or CodeReady Container OpenShift 4.5, would you install if you were asked to provision a production ready system of OpenShift?

Which of the two installation options, OpenShift 4.5 or CodeReady Container OpenShift 4.5, would you install if you had to provide a training course the next day for an overview of the OpenShift administration console using a single 32 GB laptop? What are sticky sessions, and why might you need to set these up on a load balancer?

What minimum prerequisites would you request for a basic development OpenShift 4.5 server cluster (not CRC)?

Key terms

CodeReady Container – The version of OpenShift, which will install on a single virtualised operating system server. Can also be found, in other IT areas, used for Cyclic Redundancy Check.

Dynamic Host Configuration Protocol is a network management protocol used to automate the process of configuring devices on IP networks; it supplies the IP addresses to a network card. Domain Name Server required to resolve the IP addresses and names of servers in a defined network domain.

Extra Packages for Enterprise Linux – Open-source packages including the Nginx web service.

Usually stated as Red Hat Enterprise Linux CoreOS, but also Red Hat centre for Open Source.

High availability proxy the Linux sub-system, which runs as a software load balancer supporting layer 4 and layer 7 protocols. Secure Shell is a cryptographic network protocol for operating network services securely over an unsecured network. The standard TCP port for SSH is 22.

Transmission Control Protocol (TCP) is a connection communications protocol between server systems. Usually combined with IP Internet protocol, as they form a functional system for communication, so we refer to this as TCP/IP.

The imudp module accepts UDP datagrams on the configured address and port. UDP is the transport protocol of the legacy BSD Syslog as described in RFC 3164 (currently RFC 5424). UDP is an acronym for User Datagram Protocol and is used for transmission of messages. It is different from the TCP protocol, because it doesn’t establish a connection before transmitting a message. BSD is an acronym for Berkeley Software which is the name of the Berkeley Computer Systems Research Group One of the first versions of the Unix operating system, released in 1977, initially called Berkeley Unix, because it was based on the source code of the original Unix operating system developed at Bell labs, between 1969 and 1973.

CHAPTER 8 IBM Cloud Private System

Introduction

In Chapter 7, RedHat OpenShift 4.x we covered the installation and configuration of a cluster of servers for the OpenShift 4.5.x system. The IBM Cloud Private system is based on a similar system using Docker and Kubernetes logical layers, in a cluster of servers, to provide an on-premise cloud environment. This chapter describes the outline installation of IBM Cloud Private, including the set-up of the supporting RHEL 8.0 Linux operating system and Docker system on a cluster of servers.

Structure

In this chapter, we will discuss the following topics: IBM Cloud Private Installation references and Download

Installing a Linux DNS Server on VMware 15.1

RHEL 8 download and install Install Red Hat Linux 8.0 on VMware

Boot node requirements

RHEL 8 system registered through the Subscription Manager

Update of libraries and X-Window installs

Install bind and configure to create a DNS Server

Installing Docker 18.09.2 on RHEL 8.0 Install IBM Private Cloud

System requirements

Master and Boot node requirements

Using docker pull on the MasterBoot Node

Installation procedure

Objectives

After studying this unit, you should be able to: Identify the prerequisite libraries required for the installation and configuration of IBM Cloud Private on the Red Hat RHEL 8.0 Linux operating system.

Understand the prerequisite disk, memory, network, and cluster server requirements for the target software components to be installed, and know how to configure them.

Search, identify, and download the latest Linux libraries, and configure the security required to maintain a secure and robust system.

8.1 IBM Cloud Private installation references and download

See the IBM Cloud Private Application Developer’s Guide in the following link:

http://www.redbooks.ibm.com/redbooks/pdfs/sg248441.pdf

IBM Cloud Private is an application platform for developing and managing on-premises, containerized applications. It is an integrated environment that includes the container management layer, Kubernetes, a private image registry, a management console, and monitoring systems.

IBM Cloud Private provides an on-premise-managed container solution for large organizations. It is also in a community edition, IBM Cloud Private-CE, which provides a restricted system that is available at no charge, and is available mainly for test environments.

IBM Cloud Private Community Edition is available for free from Docker Hub for a Linux 64-bit environment:

See the following link for reference: https://hub.docker.com/r/ibmcom/icp-inception/

Create a Docker ID account.

For details, see Chapter 4, On Premise Server configurations and Section 4.1, Docker account

See the Installing Docker on RHEL 8.0 section later in this chapter

8.2: Installing a Linux DNS server on VMware 15.1

The following prerequisite systems have to be present:

8.2.1: RHEL 8 download and install

Install VMware Workstation Pro 15.1.0 (minimum version): The VMware Workstation support for RHEL 8.0 only starts with VMware Workstation Pro version so this needs to be installed as an upgrade (or a new installation) first.

See the next chapter, Chapter 9, Base VMWare System for the details of this installation and configuration.

Download RHEL 8.0 ISO image from the following link:

https://developers.redhat.com/products/rhel/download/

See Chapter 1, Getting Started with IBM Resources for Section 1.1 Red Hat Linux RHEL for full details for setting up the Red Hat user account, and downloading the installation disk image for RHEL 8.0.

8.2.2: Install Red Hat Linux 8.0 on VMware

Select the menu item File > New Virtual Machine and in the first window, select the second option

For the full installation details, see the publication in the following link: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on Red Hat Enterprise Linux 8.0, Pages 24

8.3: Boot node requirements

I am supplying 8 cores, 20 GB of memory, and 300 GB drive. For full details, see the publication in the following link:

https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on Red Hat Enterprise Linux 8.0, Pages 25 -37.

Figure 8.1: The MasterBoot server parameters can be reviewed before starting the build The parameters for building the MasterBoot server are displayed by the New Virtual Machine and can be modified by clicking on the button or by using the Customize Hardware… command button; otherwise click

8.3.1: RHEL 8 system registered through the Subscription Manager

Enable subscribe to the RHEL system. Change the host name to su - root

Choose the domain name. (I have used my company domain name, registered to ASB Software Development To set a Fully Qualified Domain Name

hostnamectl set-hostname ecmukdemo10.asbsoftware.co.uk

For full details, see the publication in the following link from Pages 38 to

https://doi.org/10.13140/RG.2.2.27358.18246

8.3.2: Update of libraries and X-Window installs

For details, see Chapter 4, On-Premise Server Configurations and Section 4.9.5, GUI library installation

8.4: Install bind and configure to create a DNS server

For details of the set-up and configuration, see Chapter 4, OnPremise Server Configurations and Section 4.9.4, Network card set-up and DNS

8.5: Installing Docker 18.09.2 on RHEL 8.0

For the GUI, I installed the Linux X-Windows libraries, as follows, in the procedure. See the following link from Pages 40 to

https://doi.org/10.13140/RG.2.2.27358.18246

Install Docker for all three servers, MasterBoot, WorkerNode, and ProxyNode.

8.6: Install IBM Private Cloud

See the following link: https://ibm-cloud-architecture.github.io/refarchintegration/icp/troubleshooting/

8.6.1: System requirements

For detailed system requirements for IBM Cloud Private 3.2.0, see the IBM Knowledge Centre in the following link:

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/support ed_system_config/system_reqs.html

Figure 8.2: The recommended minimum hardware requirements for a Single node server

8.7: Master and Boot node requirements

Figure 8.3: The Master and Boot node recommended server requirements

Create worker and proxy node systems, as shown in the preceding screenshot, but without DNS and with Docker installed. For the worker node server:

Each 8 GB memory

2 processors

150 GB disks

For full details, see the publication in the following link:

https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Pages 66 to

The server name is set as follows:

hostnamectl set-hostname ecmukdemo11.asbsoftware.co.uk

IP for the worker node set to

The Red Hat Subscription Manager is run to enable the main repositories.

subscription-manager register --username usernamehere --password passwordhere --auto-attach

For the proxy node server (IP for the server is set to hostnamectl set-hostname ecmukdemo12.asbsoftware.co.uk subscription-manager register --username usernamehere --password passwordhere --auto-attach

8.7.1: Using docker pull on the MasterBoot node

The following docker command is used to pull down the IBM Cloud Private container system:

docker pull ibmcom/icp-inception

For full details, see the publication in the following link: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Pages 72 to 75.

The docker pull returns the latest version of the IBM Cloud private container system.

8.8: Installation procedure

For information about installing an IBM Cloud Private 3.2.0 cluster, see Installing IBM Cloud Private-CE in the IBM Knowledge

And for the installation on RHEL 8.0, install IBM Private Cloud. In this document:

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html

Table 8.1: Minimum storage requirements for installation

Installation-time disk space requirements are required for successful installation. In installing IBM Cloud Private, by normal Unix convention, the directory for placing offline images is and

directory for loading offline images is the directory in which you place the installation file. mkdir /opt/ibm-cloud-private-3.2.0

Installation can be completed in six main steps: Install Docker for your boot node only Complete Docker installation first, see Section, Installing Docker 18.09.2 on RHEL

Set up the installation environment

Log in to the boot node as a user with full root permissions. Download the installation file or image.

For IBM Cloud Private Native or Enterprise installation, download the correct file or files. For the Linux x86_64 cluster, download the ibm-cloud-private-x86_64-3.2.0.tar.gz file.

For full details, see the publication in the following link: https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Pages 75 to 98 and https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/inst alling/install_containers.html docker pull ibmcom/icp-inception:3.2.0 The installer image supports Linux on x86_64 systems, Linux on IBM Power 64-bit LE systems, and Linux on IBM Z and LinuxONE systems. docker run -e LICENSE=accept \ -v "$(pwd)":/data ibmcom/icp-inception:3.2.0 cp -r cluster /data The Cluster is created in the installation directory. Verify that the installation has completed successfully. The procedure is described in the following URL reference: https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html#verify

Conclusion

In this chapter, we outlined the procedure to create a server cluster, configure it with the required prerequisites for IBM Cloud Private installation and updating to fix issues in the system.

The use of Docker pull to load the required containers for the system was covered, with references to the description of the configuration of the config.yaml file needed for the installation. The config.yaml file needs at least a 32-character password!

In the next chapter, we describe the minimum required version of VMware Workplace Pro to support the Red Hat RHEL 8.0 operating system, the procedures for adding memory, CPU virtual cores, the creation and configuration of network cards, and types of network to enable access to the internet.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software.

Search and download the latest Fix Pack (this is usually cumulative) to apply fixes to the base product.

You will need a GitHub login to access the IBM Cloud Private Community Edition.

You will need an IBM user account to download the required Fix Packs.

You will need a Red Hat user account to download the Red Hat Enterprise Linux RHEL 8.0 and run Subscription Manager.

You will need a Docker log on user account to allow download and install the Docker subsystem.

Docker must be installed in all three servers in the cluster. Remember that //cluster/hosts file just has an IP address for each server (no host name).

The config.yaml file needs at least a 32-character password.

Multiple Choice Questions

Which one of the following logons do you need to download the IBM Cloud Private Fix Pack?

The Docker logon to pull the Fix Pack

The Red Hat logon to ftp down the Fix Pack The GitHub logon to download the repository for the Fix Pack

The IBM user logon to log in to Fix Central to download the Fix Pack

Which of the following lists of server nodes are the three essential server nodes for IBM Cloud Private installation?

Master (boot) node, Worker node, Management node

Master (boot) node, Proxy Node, VA node

Master (boot) node, Worker node, Proxy Node Master (boot) node, VA node, Management Node

The VMware Workstation support for RHEL 8.0 only starts with VMware Workstation Pro Version:

15.5.6

16.1.0

15.0.0

15.1.0

The IBM Cloud Private Community Edition (CE) used for the IBM FileNet Content Engine and IBM Content Navigator Containers is supported for: Development and production systems

Only production systems Only development systems Neither development or production systems

Multiple Choice Answers

d. The IBM user logon to log in to Fix Central to download the Fix Pack

c. Master (boot) node, Worker node, Proxy Node

d. 15.1.0 c. Only development systems

Questions

(You will find some of these answers in the ResearchGate publication I referenced earlier:

What prerequisite systems have to be present before the IBM Cloud Private installation can be started?

What two functions are described for docker during the installation procedure for IBM Cloud Private

What command can be used for you to review the enabled repositories in RHEL 8.0?

What is the minimum size of the password which has to be edited into the config.yaml file, and what does the installer use to validate it?

Describe the changes which have to be made to the /etc/hosts file to support the installation of IBM Cloud Private.

Key terms

Domain Name Server resolves IP address and the server Host names for a network domain

Uniform Resource Locator

Community Edition Virtual Machine

Fix Pack

CHAPTER 9 Base VMware System Platform

Introduction

In Chapter 8, IBM Cloud Private the outline procedure was covered to build a cluster of RHEL 8.0 Linux servers based on VMware, using Docker and Kubernetes logical layers to provide an onpremise cloud environment. This chapter describes the minimum required version of VMware Workplace Pro to support the Red Hat RHEL 8.0 operating system. It also describes procedures for adding memory, CPU virtual cores, the creation and configuration of network cards, and types of network to enable access to the internet. The mapping of host folders and access to load installation gzipped tar files is outlined, and the setting of hardware boot options.

Structure

In this chapter, we will discuss the following topics: Installing and upgrading of VMware Workstation Pro 15.1.0

Upgrading to VMware Workstation Pro 16.0

Installing an operating system from a disk .iso image Setting VMware memory size

Setting VMware disk size and types

Adding network cards

Adding mapped folders from the host system

Changing the boot options

Objectives

After studying this unit, you should be able to: Set up a VMware installation at 15.1 and an upgrade to 16.0.

Create a Linux operating system-based virtual server, selecting the disk, memory, and CPU processor sizes. Add and configure additional network cards

Add and configure additional virtual drives.

Add mapped folders from the host system and understand how to copy installation files and backup data to and from the established shared folder system.

Change the power-on BIOS boot options to install .iso disk images mapped to the VMware virtual CD/DVD drive.

9.1: Installing and upgrading of VMware Workstation Pro 15.1.0

If you wish to use the Red Hat Enterprise Linux RHEL 8.0 version and install it as a virtual system on VMware Workstation Pro, then you need to upgrade VMware to at least version as I show in the following procedure.

The VMware Workstation support for RHEL 8.0 only starts with VMware Workstation Pro version so this needs to be installed as an upgrade (or a new installation) first! For the full step-by-step procedure screenshots, see the ResearchGate publication in the following link:

https://doi.org/10.13140/RG.2.2.27358.18246

IBM Cloud Private P8 Container CPIT Installation on RedHat Enterprise Linux 8.0, Pages 12 to 19.

It is recommended to tick the option box to receive any upgrade information on the start-up of VMware Workstation; you will then get a windows pop-up, which can be useful for developers to be up-to-date with the latest versions of operating systems. Even more generous of VMware, as they provided this as a free update for existing VMware Workstation Pro 15.0 Licensed users.

Remember to note down your existing license key, displayed using the Help > About menu item.

The option to Download and Install this upgrade is clicked.

When the upgrade download is completed, the VMware Workstation Pro Setup wizard is launched to start the installation:

Figure 9.1: The warning pop-up appears as we still have the old version of VMware loaded

The Wizard detects we have a version of Workstation 15.0 loaded (since we discovered the 15.1 upgrade was available, from the popup reminder, while launching VMware workstation!), but we now need to close it to allow the newer version to be installed correctly. Any running versions of VMware should be stopped before upgrading. So select the File > Exit menu option on Workstation

Pro 15.0 before running the upgrade wizard.

9.2: Upgrading to VMware Workstation Pro 16.0

If you have set up your original VMware options to do so (see Section VMware will check for upgrades and display the option to upgrade on starting the VMware Workstation program. This reminder option allows you to go directly to the VMware site and order the upgrade, usually at a good discount on the full new license copy:

Figure 9.2: The Upgrade option takes you to VMware order site. After payment, you can note the license key and click on the go to download link

From the Invoice browser page, you will be able to copy the license key, and click on the download link, as shown in the preceding screenshot, to load the workstation installer.

Figure 9.3: The Go To Downloads page (highlighted) is clicked The release date for VMware Workstation Pro 16.0 can be seen as September, 2020. I selected the version for working on the Windows operating system (there is also a version of VMware Workstation Pro 16.0, which will work on a Linux operating system). Whichever version you select, it can still run a guest operating system, which is Linux-based (and a large number of other virtual operating systems are also supported). The download page is next opened with the details, as follows, for the installation download:

Figure 9.4: The details of the Download is shown on the Download browser page

Next, click the DOWNLOAD NOW button to download the installation:

Figure 9.5: The DOWNLOAD NOW command button is clicked The VMware file, VMware-workstation-full-16.0.0-16894299.exe install is downloaded:

Figure 9.6: The download installation file status can be seen in the bottom left corner using the AVG browser Click on the downloaded VMware workstation program, This file is named, based on the version, 16.0.0 and the build number,

The VMware Help > About menu item also shows the same version information after installation:

Figure 9.7: The Help-> About menu shows the VMware version 16.0 and build The installer prompts for the Windows administrator permissions:

Figure 9.8: The next prompt from the VMware 16.0 upgrade install requires access as the Windows administrator

Click Yes to continue the VMware Workstation Pro 16.0 installation:

Figure 9.9: The VMware Workstation Pro version 16 splash screen The splash screen is then shown, as shown in the preceding screenshot, followed by the following installation window, where you can either click Next for the installation or cancel out:

Figure 9.10: The Installation Next command button is clicked to continue the install upgrade

The installation license is displayed for review:

Figure 9.11: The End User License is reviewed and the I accept tick box selected; click Next The License Agreement is shown for review, tick the I accept the terms in the License Agreement checkbox option, and click

Figure 9.12: The options for the Enhanced keyboard Driver and the Workstation console tools are ticked; click Next

The enhanced keyboard and workstation console tools options are selected, as shown in the preceding screenshot. The Enhanced Keyboard Driver option is available (I have always used this since it provides better handling of international keyboards and keyboards that have extra keys), and the option to add VMware Workstation console tools into the system PATH environment variable to simplify launching the tools.

Figure 9.13: The Check for product updates on startup and the Join the VMware Customer Experience Improvement Program options are selected and the Next command button clicked Next, there is an option to Check for product updates on which I described at the beginning of this section; I recommend that this is ticked as it prompts for free minor upgrades, as well as discounted major upgrades. Also, I have selected (and recommend) that you tick the Join the VMware Customer Experience Improvement Program checkbox, as this will provide benefits for VMware users by providing some data to VMware, for improving future releases, many of which are

incorporated in the free minor version upgrades (One of which was the free 15.1 upgrade for support of RHEL Linux Version 8.0):

Figure 9.14: The options for creating icons for shortcuts are selected

The options on providing the desktop and start menu icons are shown next:

Figure 9.15: The Upgrade command button starts the installation upgrade The final installation screen either shows install or, because I am upgrading from version 15.6, the Upgrade command button to start the installation:

Figure 9.16: The Upgrade installation status is shown The installer setup wizard will then proceed with the installation of VMware Workstation Pro 16.0:

Figure 9.17: The License command button is selected to enter the key copied from the invoice You can then either click if this is an evaluation install, or click the License command button, as shown in the preceding screenshot, to add the new license that you copied in the Invoice area of the browser.

Figure 9.18: The Finish command button is clicked to complete the installation After entering the license key, click Finish as shown in the preceding screenshot.

Figure 9.19: The Yes command button is selected to reboot the Windows operating system

Because I added the VMware enhanced keyboard driver, I need to reboot the windows system to complete my VMware upgrade installation, so I selected Yes (ensure any open documents are saved first).

Figure 9.20: The Help > About menu item shows the version of VMware installed The VMware Help > About menu item confirms the installation is completed.

9.3: Installing an operating system from a disk .iso image

Install VMware Workstation Pro 15.1.0 (minimum version). Download RHEL 8.0 iso image from the following link:

https://developers.redhat.com/products/rhel/download/

See Chapter 1, Getting Started with IBM Resources for Section 1.1 RedHat Linux RHEL for full details for setting up the Red Hat user account, and downloading the installation disk image for RHEL 8.0.

This section is covered in Chapter 8, IBM Cloud Private Section 8.2.2: Install Red Hat Linux 8.0 on VMware.

For installation of RHEL 8.0 for Workstation Pro 16.0, see Chapter 7, Red Hat OpenShift 4.x Section 7.1.2: Prerequisites - Required machines.

For installation of RHCOS using the BIOS boot order see Chapter 7, RedHat OpenShift 4.x Section: 7.3.2.3, Update the /etc/hosts file, Figure 7.68 The VMware Power On to Firmware is required to configure the BIOS for

9.4: Setting VMware memory size

On VMware Workstation Pro to allocate 20 GB, you need a larger amount of physical host memory available.

With 64 GB of host server memory, the memory is set to 20 GB for the MasterBoot node server. This is fine, because the maximum recommended memory is 55.7 GB. With 16 GB of host server memory, this is not recommended!

Figure 9.21: The memory allocated can be selected up to the recommended maximum

The maximum is just 13.4

It is possible, with the virtual machine powered off, to adjust the amount of memory allocated, as long as this does not exceed the

maximum recommended memory.

9.5: Setting VMware Disk Size and Types

The following example selects 300 GB of SCSI disk space, allocated in separate files of 2 GB size, as the disk space grows, subsequent disk files are automatically created by VMware.

The virtual machine wizard is used to select the disk controller type. The SCSI disk type is selected, then the Next> command button is clicked. The default option to create a new virtual disk is selected for the MasterBoot server, this is split, as the disk space increases, in a series of 2 GB files. The 300 GB disk size is selected with the option to be split into multiple files for the MasterBoot server.

See Chapter 7, Red Hat OpenShift 4.x 7.1.2 Prerequisites - Required machines for a full example disk set-up:

Figure 9.22: The disk name is left as the default, set based on the server name, select Next> The default names for the VMware disks are set, by New Virtual Machine based on the server name given earlier.

9.6: Adding network cards

The network card is set up as a NAT card. Additional network cards can be added at any time.

The Host-only option is selected for a second network card to be used with a static IP address card.

On the main Virtual Machine Settings window on the virtual machine, the Add button is clicked, then on the Hardware Type window, the Network Adapter option is selected, and the Finish command button is clicked. The host only option allows the machine to access the DHCP network.

For some installations, three network cards are mandated, VMware supports this too. For example, IBM Directory Service 8.0 requires three network cards to be provisioned. The reference link is as follows:

https://www.ibm.com/support/knowledgecenter/SS3Q78_8.0.0/com.ib m.IBMDS.doc_8.0.0/ds_ig_va_settingup_the_VM.html

9.7: Adding mapped folders from the host system

For ease of installation, VMware can be set up to map a shared drive, which can be used for copying in installation files.

These are mounted at the /mnt/hgfs mount point on a Linux server system. An example of this can be seen as used in Chapter 7, Red Hat OpenShift 4.x Section 7.3.2, Obtaining the installation program. On a Windows server, the mapping is a network, as in the example as follows:

Figure 9.23: The Installs folder in a window environment as a shared vmware-host\Shared Folders The VMware tools must be installed on the virtual server first.

9.8 Changing the boot options

The boot options For some installations, the virtual machine BIOS has to be changed, as in the following example, to alter the boot order.

See Chapter 7, Red Hat OpenShift 4.x Figure 7.68 The VMware Power On to Firmware is required to configure the BIOS for boot for the full step by step screenshots.

The VMware master1 machine has not been started yet; we need it to boot from the CDROM device that we pointed to for the installer operating system for Red Hat OpenShift 4.5.6.

Set BIOS to point to the CDROM on boot.

Select the VM > Power > Power On to so we can change the BIOS boot order.

Use the Select Menu to move from Main to the Boot tab. Select the CD-ROM Drive to boot from, and click the F10 key and then the Enter key to run the VMware boot.

The Virtualisation Flag (Virtualize Intel VT-x/EPT or AMD-V/RV1)

The virtualisation has to be set in the VMware BIOS, in the situation where there is a Linux virtual server running inside a VMware Linux operating system, which can be done from VMware settings, but you have to stop the Linux server first and then set, as shown in the following screenshot:

Figure 9.24: The Virtualize Intel VT-x/EPT or AMD-V/RV1 VMware flag is ticked in the Settings window for the Linux server we are using This flag is required, for example, for the Red Hat CodeReady Container single Linux server version 4.5.9 of OpenShift, which is covered in Section 7.4: Installation of the Code Ready Container for OpenShift 4.5.x of Chapter 7, Red Hat OpenShift 4.x

For details on the virtualization engine flags, see the following link:

https://docs.vmware.com/en/VMware-WorkstationPro/16.0/com.vmware.ws.using.doc/GUID-3140DF1F-A105-4EED-B9E8D99B3D3F0447.html

Conclusion

In this chapter, we have covered the installation and upgrade of VMware Workstation Pro used to host virtual servers for Linux, Windows, and similar operating systems. The step-by-step procedures for configuring memory, disks, and network cards were also covered, including the method of modifying the BIOS boot order used for the Red Hat RHCOS operating system installation disk image.

Points to Remember

15.1 is the first version of VMware Workstation Pro for support of the Red Hat RHEL 8.0 Linux version

The BIOS boot order has to be changed for the installation, where the virtual CD Disk Drive is used to load a disk image for installing an operating system. For Code Ready Containers Red Hat OpenShift 4.5.9 with a virtual Linux server install, the BIOS virtualization flag has to be set in VMware Workstation Pro 16.0, for the host virtual Linux server.

The maximum virtual memory settings should reflect the maximum recommended setting defined by VMware.

For implementing a static IP address, whilst maintaining internet access, the option for a second network card can be applied with the host-only option.

Multiple Choice Questions

How can you set the functional maximum memory allowed for a Virtual server in VMware?

Set the pointer to the top of the slide bar when following the VMware Wizard parameter setting window for memory allocation.

Set the pointer to the green pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation.

Set the pointer to the blue pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation.

Set the pointer to the yellow pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation.

How can you set the functional minimum memory allowed for a virtual server in VMware? Set the pointer to the bottom of the slide bar when following the VMware Wizard parameter setting window for memory allocation.

Set the pointer to the green pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation.

Set the pointer to the blue pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation.

Set the pointer to the yellow pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation.

The splitting of a virtual disk is in a set of files, which are each limited to: 8 GBytes

4 GBytes 2 GBytes 1 GByte

The virtualisation flag has to be set in the BIOS to: Increase the memory size

To support a Linux virtual server running inside a VMware Linux operating system To change the BIOS boot order

To change the disk size and type

Multiple Choice Answers

c. Set the pointer to the blue pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation

d. Set the pointer to the yellow pointer mark icon on the slide bar when following the VMware Wizard parameter setting window for memory allocation c. 2 GBytes

b. To support a Linux virtual server running inside a VMware Linux operating system

Questions

Why might you want to tick the box for the Check for product updates on startup option on installing VMware Workstation Pro?

What advantages do you think you would have by selecting the virtual disk split into multiple files option, and are there any disadvantages? Why would you want to add a second network card to a VMware server, and when can this card be added?

What would you do to back up a Virtual server, and when might this be useful?

Key terms

RHCOS: Red Hat Core Operating based on RHEL 8.0 but maintained like a container with automatic updates. Can also be the acronym for Red Hat Centre for Open Source.

BIOS: Basic Input/Output System usually held in a ROM chip, a very basic minimal operating system to load the main Linux or Windows operating system. Open Virtual Appliance file type.

Virtual

– defines the electrical, data, and software standards and protocols for transferring data from a disk to be processed.

Network Address

Dynamic Host Configuration Protocol is a TCP/IP network management protocol used to allocate IP addresses.

CHAPTER 10 IBM Cloud Private Cluster on CentOS 8.0

Introduction

Chapter 9, Red Hat Linux covered the prerequisite requirements for download installation, upgrade, and configuration for Red Hat Linux RHEL 8.0.

This chapter covers the installation of IBM Cloud Private 3.2.0 (Community Edition) on CENTOS 8.0. See ResearchGate document, CENTOS8-0 Installation For IBM Cloud Private and IBM FileNet P8 CPIT Installation V2.docx, entitled, IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux 8.0, Pages 21 to

This describes the download and installation using docker and the requirements of a single node cluster installation on CENTOS 8.0.

For the full procedure with all screenshots, see the following:

https://doi.org/10.13140/RG.2.2.20256.94729

Structure

In this chapter, we will discuss the following topics: IBM Cloud Private installation

Installing Linux DNS Server on VMware 15.1

VMware 15.5 upgrade Download CENTOS 8.0 iso image

Master and boot node requirements

CENTOS 8 system registered through the subscription-manager

Install bind and configure to create a DNS server

Configuring the firewall

Reinstall VMware tools (if required) Open firewall ports (for all three servers)

Installing Docker 18.09.2 on CENTOS 8.0

Install IBM Private Cloud

Master and boot node requirements

Create worker and proxy base systems

Open firewall ports (on all three servers)

Repeated sections for the proxy node Using docker pull on the MasterBoot node

Installation procedure Repeated installation

Resolving the problem Fix Pack 1907 for IBM Cloud Private FIX Pack 3.2.1908 for IBM Cloud Private

Objectives

After studying this unit, you should be able to: Identify the prerequisite libraries required for the installation and configuration of IBM Cloud Private on the CentOS 8.0 Linux operating system.

Understand the prerequisite disk, memory, network, and cluster server requirements for the target software components to be installed, and know how to configure them.

Search, identify, and download the latest Linux libraries, and configure the security required to maintain a secure and robust system.

10.1: IBM Cloud Private installation

See IBM Cloud Private Application Developer’s Guide in the following link:

http://www.redbooks.ibm.com/redbooks/pdfs/sg248441.pdf

See the following link, for the Installation Workflow overview: https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/inst alling/install.html

IBM Cloud Private is an application platform for developing and managing on-premises, containerized applications. It is an integrated environment that includes the container management layer, Kubernetes, a private image registry, a management console, and monitoring systems.

IBM Cloud Private provides an on-premise-managed container solution for large organizations. It is available as a community edition, IBM Cloud Private-CE, which provides a restricted system that is available at no charge, and is mainly for test environments. IBM Cloud Private Community Edition is available for free from Docker Hub for a Linux 64-bit environment.

For details of setting up a Docker account, see Chapter 4, Docker Container Section 4.1 Docker account creation.

IBM Cloud Private CE can be downloaded for free from Docker Hub, Linux 64-bit. See the link as follows:

https://hub.docker.com/r/ibmcom/icp-inception/

Figure 10.1: Sign into the Docker web site

See the section, Installing Docker 18.09.2 on CENTOS 8.0, later in this document for the full procedure.

10.1.1: Installing Linux DNS Server on VMware 15.1

Several VMware upgrades are included in this section, since additional features were made available which are also outlined.

10.1.1.1: CENTOS 8 download and install

CENTOS Linux 8.0 Installation on VMWare Install VMware Workstation Pro 15.1.0 (minimum version)

The VMware Workstation support for CENTOS 8.0 only starts with VMware Workstation Pro version so this needs to be installed as an upgrade (or a new installation) first! This is through the VMware support for the Red Hat Enterprise Linux 8.0 option, as CENTOS 8.0 is 100 % binary compatible.

See Chapter 9, Red Hat Linux 8.0, Base VMWare System for details of this installation and configuration.

10.2: VMWare 15.5 upgrade

There are a number of (free) additional features in this version of VMWare.

Support for new guest operating systems are as follows:

Windows 10 19H2 Debian 10.0/10.1

Debian 9.11

Oracle Linux 8.0

SLE 15 SP1

FreeBSD 12.0

PhotonOS 3.0 New features have been added to Vmware 15.1 as follows:…

Jumbo frame Virtual networks can now be configured with MTU size of up to 9000 bytes.

Preserve network Network settings are now preserved after upgrades. You can also import and export your network configurations.

Multiple display shortcut You can now quickly adjust the VM display layout with a new keyboard shortcut.

PVSCSI device PVSCSI adapter is now officially supported by Workstation, which enhances the compatibility for VMs migration between Workstation and vSphere.

Open VM Tools is the default VMware Tools for applicable Linux virtual machine, and click on the download and install command button to start the upgrade installation.

10.2.1: Download CENTOS 8.0 iso image

https://wiki.centos.org/Download The download page shows that the end-of life date for CentOS 8.0 is 31st December, 2021 and for CentOS 7 is 31st May,

The mirror sites for download can be used to select a network web site local to your location:

Figure 10.2: The DVD image file is selected, for download, dated 24/09/2019 for CentOS 8.0

See the following link:

https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.1905? action=show&redirect=Manuals%2FReleaseNotes%2FCentOSLinux8 The notes reference this as the first CentOS 8 release. The CentOS Linux distribution is described as a stable platform derived from the Red Hat Enterprise Linux release.

It states that:

CentOS conforms fully with Red Hat’s redistribution policy and aims to have full functional compatibility with the upstream product.

The main difference is that CentOS mainly changes packages to remove Red Hat’s branding and artwork.

(Though sometimes there are some remaining references which have been missed!)

It is recommended that at least 2 GB RAM is required to install and use CentOS 8 (1905). And at least 4 GB RAM is recommended for a working minimum. See the following links:

https://docs.centos.org/en-US/docs/

https://docs.centos.org/en-US/8-docs/standard-install/ The CentOS-8-x86_64-1905-dvd1.iso is uploaded to the host server.

10.2.1.1: Install CENTOS Linux 8.0 on VMware

CENTOS 8 is a binary code equivalent of the Red Hat Enterprise Linux 8.0 Release

Select the menu item File > New Virtual

The disk, CPU, and memory requirements are shown in Section 10.3 as follows.

10.3: Master and boot node requirements

I am supplying 8 cores, 32 GB of memory, and 500 GB drive The disk size is selected as a single expandable file and the memory size is set to 32 GB.

The MasterBoot parameters are displayed as follows; note that although the operating system is shown as CentOS 7.0, it is actually loading a CentOS 8.0 .iso disk image system.

Figure 10.3: The MasterBoot virtual machine build parameters are displayed

The boot option to boot from the CD-ROM drive must be configured in the BIOS. The BIOS setup screen is navigated by using the select right-arrow key to move the Menu tab to the Boot tab.

The right-arrow, Select Item key is clicked to move the tab to the Boot tab from then highlight the CD-ROM drive as the first bootable device, enter to select it, then select the F10 key to save and exit. The CentOS 8.0.1905 disk image installation disk is run to display the Install screen. The mount points are set up, shown as follows, recommended for validation by the IBM Cloud Private installation:

Figure 10.4: The mount points are set up with the split of the 500 GB

A static IP address of 10.10.10.200 is set, with a DNS server of 10.10.10.170 and a domain of The power on reboot option to BIOS is used again to reset the boot option to hard drive again.

The command window can now be opened to check that the mount points we created earlier have been set with the sizes we need:

Figure 10.5: The disk space allocation and mount points are checked

Add VMware tools: [root@localhost ~]# mkdir /mnt/cdrom [root@localhost ~]# mount [root@localhost ~]# mount /dev/sr0 /mnt/cdrom mount: /mnt/cdrom: WARNING: device write-protected, mounted read-only. [root@localhost ~]#

The VMWare tools are now installed as follows: mount /dev/sr0 /mnt/cdrom mkdir /root/vmware cp /mnt/cdrom/VMwareTools-10.3.10-13959562.tar.gz /root/vmware cd /root/vmware tar -zxvf VMwareTools-10.3.10-13959562.tar.gz The VMware tools installer is launched. The VMware Display settings are set for Auto and the option is set for Stretch The number of processors is set to 8 The disk and memory sizes are checked using df -k and free.

The logon for the root is used at reboot. Click Not Listed? (to logon as root)

(The password must then be entered to login as Login as the wasadm user to initialize the user desktop preferences.

Review the Getting Started videos.

10.3.1: CENTOS 8 system registered through the Subscription Manager Enabling Subscribe to the CENTOS system

10.3.1.1: Change the host name to ecmukdemo20

su - root Choose the domain name.

(I have used my company domain name,

(Registered to ASB Software Development To set a Fully Qualified Domain Name

hostnamectl set-hostname ecmukdemo20.asbsoftware.co.uk

Check available repositories

You can review the enabled repositories by using the following command:

yum repolist

10.4: Install bind and configure to create a DNS server

This section is only applied to the MasterBoot server. The DNS service package is installed as follows:

dnf -y install bind*

10.4.1: Configuring the firewall

The firewall has to be enabled for the DNS service: firewall-cmd --permanent --zone=public --add-service=dns

and reload the configuration:

firewall-cmd --reload

10.4.1.1: Back up the main configuration files

Make an initial backup copy of the main bind configuration files: cp /etc/named.conf /etc/named.conf_bck cp /etc/named.rfc1912.zones /etc/named.rfc1912.zones_bck

10.4.1.2: Set up the DNS server with a static IP address

See the Appendix B of the following link: https://doi.org/10.13140/RG.2.2.21708.16001

Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator 3.0.6. Add a second NAT Network Card using VMware:

reboot

The ens192 MAC address is selected for configuration.

The static IP address, 10.10.10.170 is added to the IPv4 address tab:

cat /etc/sysconfig/network-scripts/ifcfg-ens160|egrep -i "boot|ipaddr|mask|gateway" vi /etc/sysconfig/network-scripts/ifcfg-ens160 to change the bootproto flag to static. reboot cat /etc/sysconfig/network-scripts/ifcfg-ens160|egrep -i "boot|ipaddr|mask|gateway"

Figure 10.6: The filtered parameters of the ifcfg-ens160 file are displayed

The Displays setting needs to be changed to match the host display resolution:

Figure 10.7: The display resolution is changed to match the screen display Disabling the Network Manager DNS auto-configuration

We don’t want the Network Manager to change the resolv.conf file. To do that, we simply add the following line, dns=none in the file:

/etc/NetworkManager/NetworkManager.conf, vi /etc/NetworkManager/NetworkManager.conf Add dns=none at the end of the file, save, and then reload the service: systemctl reload NetworkManager

10.4.1.3: Resolver configuration changes

To configure the resolv.conf file. The first lines must be the following:

search asbsoftware.co.uk nameserver 10.10.10.200 nameserver 216.239.34.21 nameserver 192.168.50.2 This is both in the server and in any client querying this DNS.

The nameserver 216.239.34.21 IP address is just a Google DNS server used for internet resolution.

You need to add a second name server to resolve internet sites or any other domain.

Configuration for a single DNS server.

See the reference link pages 49 to 57 for the full procedure: https://doi.org/10.13140/RG.2.2.20256.94729

10.4.1.4: Enabling the bind service at startup

Make sure the DNS service is started with the system: systemctl enable named

The named.conf file has to be edited to add the IP address of the server acting as a DNS server: Reboot

I changed the second network card to be DHCP, giving the “Host” VMware address of 192.168.50.128, since there is no access to the internet otherwise!

10.4.2: Reinstall VMware tools (if required)

On the host, from the Workstation Pro menu bar, select VM > Install VMware

If an earlier version of VMware Tools is installed, the menu item is Update VMware

If the VMware Tools virtual CD-ROM image is not mounted, mount the CD-ROM drive.

10.4.3: Open firewall ports ( for all three servers)

For FileNet ports: firewall-cmd --zone=public --permanent --add-port 2809/tcp firewall-cmd --zone=public --permanent --add-port 9080/tcp firewall-cmd --zone=public --permanent --add-port 9081/tcp

firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd

--reload --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public

--permanent --permanent --permanent --permanent --permanent --permanent --permanent

--add-port 389/tcp --add-port 636/tcp --add-port=8001/tcp --add-port 10248-10252/tcp --add-port 30000-32767/tcp --add-port 30000-32767/udp --add-port=5601/tcp

firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd

--zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public

--permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent

--add-port=8001/tcp --add-port=5044/tcp --add-port=8080/tcp --add-port=8443/tcp --add-port=3306/tcp --add-port=4567/tcp --add-port=4568/tcp --add-port=4444/tcp --add-port=31443/tcp --add-port=9443/tcp --add-port=9083/tcp --add-port=27017/tcp

firewall-cmd --zone=public --permanent --add-port=8445/tcp

firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd firewall-cmd

--zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public --zone=public

--permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent --permanent

--add-port=9100/tcp --add-port=6969/tcp --add-port=3100/tcp --add-port=9100/tcp --add-port=3000/tcp --add-port=9090/tcp --add-port=44134/tcp --add-port=9093/tcp --add-port=179/tcp --add-port=9099/tcp --add-port=9103/tcp

firewall-cmd --zone=public --permanent --add-port=9200/tcp firewall-cmd --zone=public --permanent --add-port=9300/tcp firewall-cmd --zone=public --permanent --add-port=9108/tcp firewall-cmd --zone=public --permanent --add-port=2380/tcp firewall-cmd --zone=public --permanent --add-port=4001/tcp firewall-cmd --zone=public --permanent --add-port=24007/tcp firewall-cmd --zone=public --permanent --add-port=24008/tcp firewall-cmd --zone=public --permanent --add-port=2222/tcp firewall-cmd --zone=public --permanent --add-port 49152-49251/tcp firewall-cmd --zone=public --permanent --add-port=3000/tcp firewall-cmd --zone=public --permanent --add-port=31031/tcp firewall-cmd --zone=public --permanent --add-port=31030/tcp firewall-cmd --zone=public --permanent --add-port=8500/tcp firewall-cmd --zone=public --permanent --add-port=8600/tcp firewall-cmd --zone=public --permanent --add-port=80/tcp firewall-cmd --zone=public --permanent --add-port=443/tcp firewall-cmd --zone=public --permanent --add-port=500/tcp

firewall-cmd --zone=public --permanent --add-port=500/udp

firewall-cmd --zone=public --permanent --add-port=4500/tcp firewall-cmd --zone=public --permanent --add-port=31380/tcp firewall-cmd --zone=public --permanent --add-port=31390/tcp firewall-cmd --reload

10.5: Installing Docker 18.09.2 on CENTOS 8.0

See Chapter 4, Docker Container Section 4.2.1 Installing Docker 18.09.2 on RHEL for details of the procedure for this.

Install Docker for all three servers: MasterBoot, WorkerNode, and ProxyNode.

10.6: Install IBM Private Cloud

See the following links: https://ibm-cloud-architecture.github.io/refarchintegration/icp/troubleshooting/

and https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/inst alling/install.html

System requirements

For detailed system requirements for IBM Cloud Private 3.2.0, see the System Requirements in the IBM Knowledge

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/support ed_system_config/system_reqs.html

Figure 10.8: The Single node, IBM Cloud Private requirements

10.6.1: Master and Boot Node requirements

The Master and Boot requirements are shown split, in the following screenshot, but usually the boot server is combined with the master server for installation of IBM Cloud Private.

Figure 10.9: The Master Boot server requirements

10.6.2: Create worker and proxy base systems

Create worker and proxy node systems, as shown in the preceding Figure but without DNS and with Docker installed. /etc/hosts file set is shown in the following screenshot with cluster server IP addresses:

Figure 10.10: The /etc/hosts file is set with the cluster server IP addresses

Repeat base install for the worker node server

Repeated the procedure, as given in the preceding screenshot, for the worker and proxy nodes, as for the master but no DNS install. For the worker node server:

Each 8 GB memory, 2 processors and 150 GB disks.

The worker node server disk capacity is set to 150 GB, split into a 2 GB set of files. The command is run, as follows, to change the server name for the worker node:

hostnamectl set-hostname ecmukdemo21.asbsoftware.co.uk

The IP for the worker node is set to

Repeated sections for the worker node:

Repeat sections from CENTOS 8 system to setup a remote repository down to (but not including) install bind, and configure to create a DNS Server.

Run the section, reinstall VMware Tools. Run the section, installing Docker 18.09.2 on CENTOS 8.0.

Repeat base install for the proxy node server.

The disk size is set at 150 GB, split into multiple files, which are limited to 2 GB each. The BIOS for the server is modified using the Power On > Power On to Firmware option to modify the boot order for use of the CDROM for booting. The hostnamectl command is used to change the server Fully Qualified Domain Name

hostnamectl set-hostname ecmukdemo22.asbsoftware.co.uk

The /etc/hosts file is listed to ensure the configuration includes all the cluster node servers.

Network settings The proxy server network card is set with a static IP address and reference to the DNS server IP. /etc/hosts file:

Figure 10.11: The /etc/hosts file is listed using cat, to show the mycluster.icp IP address

10.6.3: Open firewall ports (on all three servers)

The firewall-cmd command is run to open all the required port numbers for the required IBM Software containers (see Section

The proxy node server system is then rebooted:

reboot

10.6.4: Repeated sections for the proxy node

Repeat sections from CENTOS 8 system setup a remote repository down to (but not including) install bind, and configure to create a DNS server.

Run the section, reinstall VMware Tools.

Run the section, installing Docker 18.09.2 on CENTOS 8.0.

10.6.5: Using docker pull on the MasterBoot node

docker pull ibmcom/icp-inception The completed Docker download of IBM Cloud Private 3.2.0 base installation is shown as follows:

Figure 10.12: The completed docker pull of container images of IBM Cloud Private 3.2.0

Changed the config.yaml file:

Figure 10.13: The container image config.yaml file is edited

From:

Figure 10.14: The cluster_lb_address is changed from ecmukdemo9.asbsoftware.co.uk To the following:

Figure 10.15: The cluster_lb_address is changed to none Also, on the master node:

Figure 10.16: The /etc/hosts file is set on the master node, 10.10.10.200 Added the ecmukdemo21.asbsoftware.co.uk and ecmukdemo22.asbsoftware.co.uk to the /etc/hosts file in each server. IBM Cloud Private workload services – load balancer set to none.

10.6.5.1: Master node requirements

Installed Docker directly on the master node, as for the worker node and proxy node. Following the document section: Installing Docker 18.09.2 on

Figure 10.17: The master node requirements

Updated the base cluster server

The master node server is set with 32 GB of memory.

10.6.6: Installation procedure

yum install iptables-services systemctl start firewalld systemctl enable firewalld

For information about installing an IBM Cloud Private 3.2.0 cluster, see Installing IBM Cloud Private-CE in the IBM Knowledge And for the installation on CENTOS 8.0:

Install IBM Private Cloud

In this document:

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html

Installation-time disk space requirements are required for successful installation in

The directory for placing offline images is and the directory for loading offline images is the directory in which you place the installation file. mkdir /opt/ibm-cloud-private-3.2.0 See the following link:

https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html?view=kc#prep_boot

For completion of this installation, see section,10.5 Installing Docker 18.09.2 on CENTOS

See the following link: https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html?view=kc#setup

Log in to the boot node as a user with full root permissions. Download the installation file or image.

For IBM Cloud private native or enterprise installation: download the correct file or files for the type of nodes in your cluster from the website: https://www-01.ibm.com/software/passportadvantage/

For a Linux x86_64 cluster, download the ibm-cloud-private-x86_643.2.0.tar.gz file. See the following link: https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/inst alling/install_containers.html

(Search of the preceding link only finds version 3.1.0 on the IBM PartnerWorld Software Advantage web site) For IBM Cloud Private-CE Download the CE image from Docker Hub by running the following commands:

cd /opt/ibm-cloud-private-3.2.0 docker pull ibmcom/icp-inception:3.2.0 This installer image supports Linux on x86_64 systems, Linux on Power 64-bit LE systems, and Linux on IBM Z and LinuxONE systems. cd cluster

docker run -e LICENSE=accept \ -v "$(pwd)":/data ibmcom/icp-inception:3.2.0 cp -r cluster /data Cluster is created in the installation directory. Change directory using the Unix command:

cd cluster and create a secure connection from the boot node to all other nodes in the cluster. I chose password authentication. Set up password authentication in the cluster. See configuring password authentication for cluster nodes. See the following link: https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/password_auth.html Configuring password authentication by using the config.yaml file.

The config.yaml file can be used to set password authentication for nodes that have the same password only. If each node has a different password, set the password authentication by using the hosts file.

View the license as follows: [root@ECMUKDEMO9 cluster]# docker run -e LICENSE=view -e LANG=$LANG ibmcom/icp-inception:3.2.0 LICENSE INFORMATION The following programs listed here are licensed under the license Information terms and conditions in addition to the program license terms previously agreed to by client and IBM. If client does not have previously agreed to license terms in effect for the program, the international license agreement for non-warranted programs (Z125-5589-05) applies. Etc…etc…. Add the configuration parameters for your use case to the //cluster/config.yaml file:

Add the IP address of each node in the cluster to the //cluster/hosts file. See setting the node roles in the hosts file.

The hosts file contains the IP address of the master, worker, proxy, and optional management and Vulnerability Advisor nodes in your cluster. Do not add host names to this file!

Figure 10.18: The hosts file (highlighted) is edited

Open the //cluster/hosts file.

Add the IP addresses for the different node types to the different sections of the file. The following points should be noted:

For a standard or Community Edition environment, you can have only one node in the master section.

You can enable the optional management node. If you use a single computer as multiple nodes in your cluster, you must specify its IP address in each applicable node section. For example, if you use the same node as a master and proxy, enter its IP address in both the master and proxy sections. You can enable the optional etcd node. If you add an etcd node, etcd is installed on this node. Else, etcd is installed on the master node.

See the following link:

https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/inst alling/config_yaml.html

is the directory to hold the temporary installation files during installation. This location must have at least 50 GB of available disk space.

If your /tmp directory has less than 50 GB of space, you must set this parameter to a location that has the available disk space requirement. Set to

ansible_python_interpreter Set this parameter to /usr/bin/python3 if you use python3 in your cluster nodes.

The cfdisk command is used to show the breakdown of the /dev/sda disk space sectors: https://access.redhat.com/documentation/enus/red_hat_enterprise_linux/6/html/storage_administration_guide/xfs grow

In the config.yaml file ref:

ansible_user: root ansible_ssh_pass: SHARED_PASSWORD ansible_ssh_common_args: "-oPubkeyAuthentication=no"

Changed to the following:

Figure 10.19: The updated config.yaml file used for the installation Get regular expression rule (see tested in the following screenshot), and I found I need at least a 32-character password!

So, I used a > 32-character password:

FileNetTheQuickBrownFoxJumpsOver

Figure 10.20: The hosts file after update

Can add the following (if required): [etcd]

Customize your cluster You can complete most of the cluster customization in the //cluster/config.yaml file. These customizations must be done during the installation of your cluster.

For IBM Cloud Private-CE installation: cluster_lb_address: IP address

The address> value is the IP address, fully qualified domain name, or OpenStack floating IP address that manages communication to external services.

The cluster_domain parameter is uncommented in the config.yaml file.

Set up Docker for your cluster nodes If you do not have a supported version of Docker that is installed on your cluster nodes, IBM Cloud Private can automatically install Docker on your cluster nodes during the installation.

The preceding does not work on the proxy server! I had to install Docker on it manually!

See the following link: https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.1.0/inst alling/prep_cluster.html For Python 3.x appended to the config.yaml file.

Append ansible_python_interpreter: /usr/bin/python3 Deploy the environment.

Change to the cluster folder in your installation directory by running the following command: cd /opt/ibm-cloud-private-3.2.0/cluster

For IBM Cloud Private-CE (The first attempt failed… so the additional configuration was used, as shown in the following section, after this first attempt, which was caused by using a short password!) docker run --net=host -t -e LICENSE=accept \ -v "$(pwd)":/installer/cluster ibmcom/icp-inception:3.2.0 install

Changed to

This is described in the IBM knowledge base technote as follows:

https://www-01.ibm.com/support/docview.wss?uid=ibm10875466 ICP V3.1.2 password rules have changed. Ensure that you set the system administrator password parameter according to ICP V3.1.2 rules, else the deployment fails. The rules are enforced as per this aspect: regex – "^([a-zA-Z0-9\-]{32,})$" This Regular Expression is described in the following URL reference (cut and paste into the Regular Expression box). It describes each character’s meaning as you move across with the mouseover. Tested using the following link:

https://www.regexpal.com/ Edited The password validation error is shown which indicates that the password should be created with 32 characters:

I had the regular expression rule displayed as shown below, so I tested this and found I need at least a 32-character password!

The Regular Expression was tested from the error message: ^([a-zA-Z0-9\-]{32,})$ So I used a password:

FileNetTheQuickBrownFoxJumpsOver Open the ports on each server (See Section Enable sshd service on the master node: systemctl enable --now sshd systemctl reload sshd service sshd status Generate an SSH key: ssh-keygen -b 4096 -t rsa -f ~/.ssh/master.id_rsa -N "" [root@ecmukdemo10 cluster]# Add the SSH key to the list of authorized keys: cat ~/.ssh/master.id_rsa.pub | tee -a ~/.ssh/authorized_keys

Apply the port 22 open below to all nodes: firewall-cmd --zone=public --permanent --add-port=22/tcp firewall-cmd --reload ssh-copy-id -i ~/.ssh/master.id_rsa.pub ecmukdemo21; ssh 'ecmukdemo21' systemctl enable --now cockpit.socket ssh-copy-id -i ~/.ssh/master.id_rsa.pub ecmukdemo22; systemctl enable --now cockpit.socket Exit the ssh connection on each node server: systemctl restart sshd On the boot node server:

cp ~/.ssh/master.id_rsa ./ssh_key

10.6.7: Repeated installation

docker run --net=host -t -e LICENSE=accept -v "$(pwd)":/installer/cluster ibmcom/icp-inception:3.2.0 install kubectl -n kube-system get pods

Deployments are managed by the Kubernetes Deployment controller. They represent a set of identical Pods with no unique identities. A Deployment can run multiple replicas of a container pod application and automatically replaces any instances that fail. The following kubectl command is used to list the container deployments:

kubectl -n kube-system get deployments

From the preceding command, the MongoDB container can be seen to be in the init status (so, not started into the Running status after the installation).

Found a fix for that; see the following link: https://www.ibm.com/support/pages/node/739405

10.6.8: Resolving the problem

This will be fixed in a future release; however, there is a workaround:

The /cluster/config.yaml file line 18 is modified by commenting out the cluster_domain line, so that it can use the default value given, Here the value used internally, so generally you don’t have to customize it.

Uninstall (if required)

docker run --net=host -t -e LICENSE=accept \ -v "$(pwd)":/installer/cluster ibmcom/icp-inception:3.2.0 uninstall

and then re-install IBM Cloud Private.

docker run --net=host -t -e LICENSE=accept \ -v "$(pwd)":/installer/cluster ibmcom/icp-inception:3.2.0 install

10.6.8.1: Using FTP server – Procedure for Installation of FTP

Signed in as root to use: dnf install vsftpd [root@ecmukdemo20 ~]# dnf install vsftpd

Make a backup copy of the FTP configuration file: mv /etc/vsftpd/vsftpd.conf /etc/vsftpd/vsftpd.conf_orig

Start with a clean configuration file:

grep -v ^# /etc/vsftpd/vsftpd.conf_orig > /etc/vsftpd/vsftpd.conf cat /etc/vsftpd/vsftpd.conf systemctl start vsftpd systemctl enable vsftpd

Open firewall FTP port 21 incoming connections:

firewall-cmd --zone=public --permanent --add-service=ftp firewall-cmd --reload Test FTP connection from the remote host using the ftp command. Use your regular user credentials to login. For example, create an FTP connection to the host IP:

chown root:wasadm -R /opt

Using binary mode to transfer files.

Enter ftp from the windows command line:

ftp>open 192.168.50.128

(Or whatever the host IP or DNS host CentOS 8.0 server name is set to.)

Figure 10.21: The ftp server can be connected to using the open command

The mput *.* command can then be used to transfer files from a windows host server to the Linux virtual server.

The mput *.* will transfer all the files from the current local directory to the Linux server /home/wasadm remote directory user’s folder with each file prompted for transfer affirmation, shown as follows: cd /opt/dockeFP mv /home/wasadm/docker-3.2.0-26053-20190808.patch /opt/dockeFP/

Add the executable permission: chmod +x docker-3.2.0-26053-20190808.patch Get the Docker installation binary:

./docker-3.2.0-26053-20190808.patch --noexec --keep cd docker-3.2.0-26053-20190808

Change to the //cluster/ directory: vi /opt/ibm-cloud-private-3.2.0/cluster/config.yaml

Edit the config.yaml file to set the Docker version to docker_version: 18.09.7 The installation directory for the runtime-engine is created: mkdir -p /opt/ibm-cloud-private-3.2.0/cluster/runtime-engine

The docker binary file is then renamed to the runtime-engine directory that we created: mv icp-docker-18.09.7_x86_64.bin /opt/ibm-cloud-private3.2.0/cluster/runtime-engine

As the boot node is one of the cluster nodes, I manually upgraded Docker on the boot node: kubectl cordon 10.10.10.200 kubectl drain 10.10.10.200 --ignore-daemonsets --delete-local-data -force --timeout=600s ./runtime-engine/icp-docker-18.09.7_x86_64.bin --upgrade kubectl uncordon There are several kubectl commands we have used in the preceding section to control the deployed container pods. Using the cordon command causes the node server to be marked unschedulable to prevent new pods from arriving. (The uncordon command reverses this status flag allowing the pod to be schedulable again.)

The drain command evicts the pods or deletes all pods, except mirror pods.

If there are daemondet-managed pods, drain will not proceed without --force will allow deletion to proceed if the managing resource of one or more pods is missing.

drain waits for graceful termination. For upgrade, we need to wait until the command completes, and then run the command: ./runtime-engine/icp-docker-18.09.7__x86_64.bin –upgrade kubectl uncordon 10.10.10.200

The preceding command is used to upgrade Docker on the other nodes.

Add the executable permission. chmod +x docker-3.2.0-26053-20190808.patch Get the Docker installation binary:

./docker-3.2.0-26053-20190808.patch --noexec --keep

10.6.9: Fix Pack 1907 for IBM Cloud Private

Uploaded using the windows FTP client to the master boot server: Check the Docker version:

kubectl get nodes -o yaml | grep containerRuntimeVersion

The Docker version must be containerRuntimeVersion: docker://18.9.7

Or, run the following commands on the cluster nodes to verify the Docker version:

docker version docker info

10.6.9.1: Fix Pack installation for IBM Cloud Private icp-3.2.0.1907

See the following link: https://github.com/kubernetes/ingress-nginx/pull/3038

Looked for fixes.

See the following link: https://www.ibm.com/support/fixcentral/swg/identifyFixes? query.parent=ibm~WebSphere&query.product=ibm~WebSphere~IBM%2 0Cloud%20Private&query.release=3.2.0&query.platform=Linux%2064bit,x86_64

Figure 10.22: The highlighted links are used to download the Fix Packs

See the following link: https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/manag e_cluster/patching_cluster.html#apply

Apply the fix pack first.

Copy the downloads to the boot node (Master) server VMware server host.

mkdir /opt/installFP1907 FTP or VMware copy the installation fix pack. The VMware server shared folder for the master server node is set to the installation folder path. Map to the installs directory using the VMware shared folders option: cd /opt/installFP1907

Figure 10.23: The downloaded install for IBM Cloud Private Fix Pack is shared cp /mnt/hgfs/Installs/IBMCloudPrivate/IBM_Cloud_Private3.2.0.1907/ibm -cloud-private-x86_64-3.2.0.1907.tar.gz .

Extract the images from the fix pack and load the images into Docker. tar xf ibm-cloud-private-x86_64-3.2.0.1907.tar.gz -O | docker load [root@ecmukdemo20 installFP1907]# cp /mnt/hgfs/Installs/IBMCloudPrivate/IBM_Cloud_Private3.2.0.1907/ibm -cloud-private-x86_64-3.2.0.1907.tar.gz . [root@ecmukdemo20 installFP1907]# ls ibm-cloud-private-x86_64-3.2.0.1907.tar.gz [root@ecmukdemo20 installFP1907]# tar xf ibm-cloud-privatex86_64-3.2.0.1907.tar.gz -O | docker load Move the fix pack file to the cluster, //cluster/images folder: mkdir /opt/ibm-cloud-private-3.2.0/cluster/images mv /opt/installFP1907/ibm-cloud-private-x86_64-3.2.0.1907.tar.gz /opt/ibm-cloud-private-3.2.0/cluster/images cd /opt/ibm-cloud-private-3.2.0/cluster Apply the fix pack images to the

docker run -e LICENSE=accept --net=host --rm -t -v "$(pwd)":/installer/cluster \ ibmcom/icp-inception-amd64:3.2.0.1907-ee apply-fixpack

Disk space usage peaks at 32% of a 300 GB disk!

10.6.10: Fix Pack 3.2.1908 for IBM Cloud Private

The Fix pack 3.2.1908 is now downloaded and installed. Download the fix pack file.

For a Linux x86_64 cluster, run the following commands:

mkdir /opt/installFP1908 cd /opt/installFP1908 cp /home/wasadm/ibm-cloud-private-x86_64-3.2.0.1908.tar.gz . tar xf ibm-cloud-private-x86_64-3.2.0.1908.tar.gz -O | docker load

Figure 10.24: The docker load command is used to install the Fix Pack

Move the fix pack file to your cluster.

For a Linux x86_64 cluster, run the following command: mv /opt/installFP1908/ibm-cloud-private-x86_64-3.2.0.1908.tar.gz /opt/ibm-cloud-private-3.2.0/cluster/images

cd /opt/ibm-cloud-private-3.2.0/cluster

Apply the fix pack images to the

docker run -e LICENSE=accept --net=host --rm -t -v "$(pwd)":/installer/cluster \ ibmcom/icp-inception-amd64:3.2.0.1908-ee apply-fixpack reboot kubectl -n kube-system get nodes -o yaml | grep containerRuntimeVersion kubectl get nodes -o yaml | grep containerRuntimeVersion docker version

Figure 10.25: The docker version command is run to show the server and client versions

10.6.10.1: Re-running the Fix Pack installation

See the following link: https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/inst alling/install_containers.html

No errors but still no completion message last entry in the log is: TASK [Building multiarch images] *********************************************** kubectl -n kube-system get nodes

Figure 10.26: The list of server cluster nodes is listed using kubectl

10.6.10.2: Verify the installation

See the following link: https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html#verify

kubectl -n kube-system get statefulset

Figure 10.27: The state of the docker containers is listed using the kubectl command

docker version

Figure 10.28: The docker version of the Master server is displayed

kubectl -n kube-system get pods

Figure 10.29: The kubectl -n kube-system get pods command lists container pods The list of pods is shown in the preceding screenshot, and in a second page, Verify the See the following link (version [as of August, 2020]): https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/installi ng/install_containers.html#verify

Conclusion

In this chapter, we described the procedure to create a server cluster using CentOS 8.0 virtual servers, and configure it with the required prerequisites for IBM Cloud Private installation, updating to fix issues in the system.

The use of Docker pull to load the required containers for the system was covered, with a complete description of the configuration of the config.yaml file needed for the installation. In the next chapter, we will cover the customisation of IBM Watson Content Analytics Studio (IBM Watson Explorer Content Analytics Studio V11.0.1) with a Custom Java based Unstructured Information Management pipeline.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software.

Search and download the latest Fix Pack (this is usually cumulative) to apply fixes to the base product.

You will need a GitHub logon to access the IBM Cloud Private Community Edition.

You will need an IBM user account to download the required Fix Packs.

You will need a Docker log on user account to allow download and install of the Docker subsystem.

Docker must be installed in all three servers in the cluster.

Remember that //cluster/hosts file just has an IP address for each server (no host name). The config.yaml file needs at least a 32-character password!

Multiple Choice Questions

Which one of the following logons do you need to download the IBM Cloud Private Fix Pack?

The Docker logon to pull the Fix Pack

The Red Hat logon to FTP down the Fix Pack The GitHub logon to download the repository for the Fix Pack

The IBM user logon to log into Fix Central to download the Fix Pack

Which of the following lists of server nodes are the three essential server nodes for IBM Cloud Private installation?

Master (boot) node, Worker node, Management node

Master (boot) node, Proxy Node, VA node

Master (boot) node, Worker node, Proxy Node Master (boot) node, VA node, Management Node

The VMware Workstation support for CentOS 8.0 only starts with VMware Workstation Pro Version:

15.5.6

16.1.0

15.0.0

15.1.0

The IBM Cloud Private Community Edition used for the IBM FileNet Content Engine and IBM Content Navigator Containers is supported for: Development and production systems

Only production systems Only development systems Neither development or production systems

Multiple Choice Answers

d. The IBM user logon to log into Fix Central to download the Fix Pack

c. Master (boot) node, Worker node, Proxy Node

d. 15.1.0 c. Only development systems

Questions

What prerequisite systems have to be present before the IBM Cloud Private installation can be started?

What two functions are described for docker during the installation procedure for IBM Cloud Private?

What command can be used for you to review the enabled repositories in RHEL 8.0?

What is the minimum size of the password that has to be edited into the config.yaml file, and what does the installer use to validate it?

Describe the changes that have to be made to the /etc/hosts file to support the installation of IBM Cloud Private?

Key terms

Domain Name Server resolves IP address, and the server host names for a network domain

Uniform Resource Locator

Community Edition Virtual Machine

Fix Pack

CHAPTER 11 UIMA Pipeline and Java Code Extensions

Introduction

This chapter covers the installation and customization of IBM Watson Content Analytics Studio (IBM Watson Explorer Content Analytics Studio V11.0.1) with a custom Java based Unstructured Information Management Architecture pipeline.

Reference link is as follows: https://www.ibm.com/support/pages/release-notes-ibm-watsonexplorer-analytical-components-version-1101

Structure

In this chapter, we will discuss the following topics: IBM Watson Content Analytics Studio installation

Resolving the missing JVM problem

Incorporation of UIMA Apache Regular Expression Annotator Transfer of a Custom Annotator to the ICA Server

Objectives

After studying this unit, you should be able to: Identify the prerequisites required for each of the system components, which will be required to support the IBM Watson Explorer Studio versions targeted for installation.

Understand the prerequisite requirements for the target software component to be installed, and know how to configure it.

Search, identify, and download the latest Java JVM supporting the installation, and configure the Watson Studio Explorer to export a .pear file, for use as a Custom Annotator (the UIMA standard extension, is the Processing Engine Archive

11.1: IBM Watson Content Analytics Studio Installation

IBM Watson Explorer Content Analytics Studio V11.0.1 The Download Reference link is as follows:

https://www.ibm.com/support/pages/watson-explorer-version-1101analytical-components

Figure 11.1: The product code CNAW3EN can be found by scrolling down

Product code CNAW3EN is used as the search for download. See the link as follows:

https://www356.ibm.com/partnerworld/partnertools/eorderweb/ordersw.do

Figure 11.2: The Find by part number section is searched using the CNAW3EN code

The download windows .zip file for the IBM Watson Explorer Content Analytics studio V11.0.1:

Figure 11.3: The Find by part number results show the IBM Watson Explorer Content Analytics studio for download The I agree radio button has to be selected to enable the Download now command button:

Figure 11.4: The download status window is displayed to show the progress of the download After downloading the windows .zip file, the setup file, ContentAnalyticsStudio-install.exe is extracted from the file: WATSON_EXPLR_CAS_V11.0.1_WIN_EN.zip

Figure 11.5: The downloaded zip file is available to extract the installation program

Extract the installation program from the .zip file and Run as

Figure 11.6: The installation program is run as administrator

The program must be run as administrator as it requires full security access to the system:

Figure 11.7: The first install run failed with a Windows error 2

The first time I ran the install program, I got a pop-up window with the preceding shown message, “Windows error 2 occurred while loading the Java VM”.

A search on Google gave the following URLs which helped to resolve the issue: https://www.ibm.com/support/pages/cannot-run-watson-contentanalytics-studio-installer

A search for the IBM Watson Explorer Studio 11.0.1 requirements, showed that the Java JVM version IBM Java 8.0 SR3 was required. https://www.ibm.com/support/pages/node/607443#requirements The following IBM URL has a link to download the Java SDK required, which is bundled with IBM’s release of Eclipse, Version: 2020-06 (4.16) Build ID: as highlighted in the following screenshot: https://www.ibm.com/support/pages/java-sdk-downloads

Figure 11.8: The 64-bit version of the IBM JVM 8.0 SR3 is downloaded as part of the IBM Eclipse package Reference link is as follows:

https://www.ibm.com/support/pages/java-sdk-downloads-eclipse leading to:

https://www.ibm.com/marketing/iwm/platform/mrs/assets? source=idpe&lang=en_US&S_PKG=win64-6.6.15

This downloads as a .zip file, which is as follows: IBM_DevelopmentPackage_for_Eclipse_Win_X86_64_6.6.15.zip On unpacking this IBM eclipse package, the ibm_sdk80 sub-folder should be copied to the required Java system directory (I used So, the ibm_sdk80 subfolder must be copied to the existing Java standard windows java folder, as a subfolder, as highlighted.

11.1.1: Resolving the missing JVM problem

To resolve the issue: Make sure that a 64-bit JRE is installed.

Run ContentAnalyticsStudio-install.exe LAX_VM as a Windows administrator. where the LAX_VM switch parameter is used to boot the installer from the Java virtual machine, which is installed on the system. You need to specify the absolute path of the Java executable file that resides in the Java bin directory.

should be replaced with the concrete full path of the folder having java.exe. I used the unpacked and copied folder ibm_sdk80:

ContentAnalyticsStudio-install.exe LAX_VM C:\PROGRA~1\java\ibm_sdk80\bin\java.exe

Figure 11.9: Running the install program with the LAX_VM switch from a command window fixes the issue

The license agreement is displayed after clicking the Next command button:

Figure 11.10: The License is displayed, to accept, click the I accept radio button and click Next

The options can be selected, as shown in the following screenshot, for the installation:

Figure 11.11: The install options can be ticked; then click Next

The installation destination drive and folder path can be selected, as shown in the following screenshot:

Figure 11.12: The Install path is selected as required and the Next command button is clicked The installation path drive was updated from C: to as shown highlighted in the preceding screenshot. This needs to be a fast read/write SSD, or magnetic hard drive can be any valid drive in the range D: to Z: (not a CDROM optical DVD drive).

Figure 11.13: The Installation details are displayed for review and the Install command clicked The installation status is displayed in the next window, as shown in the following screenshot, showing the progress of the installation:

Figure 11.14: The installation is displayed with the status bar showing % completed The installation is shown as Install Complete in the following screenshot, and the Done command button can be clicked:

Figure 11.15: The installation is displayed as successfully completed; click the Done command

The Windows Start command shows the program has been added to the system:

Figure 11.16: The icons for the IBM Watson Explorer Content Analytics Studio are displayed

The IBM Watson Explorer Content Analytics Studio 11.0.1 program is launched by using the Windows Start command, and clicking on the icon highlighted in the preceding screenshot.

Figure 11.17: The default studioworkspace folder can be modified or used by clicking OK

The default studioworkspace folder contains an example IBM project, which can be used for testing or as a tutorial. If the folder is modified, this project is not loaded. On loading for the first time, the following screen is shown:

Figure 11.18: The Welcome splash screen, with URL links are displayed

On loading for the first time, with a different folder path from the default for the studioworkplace folder, the following screen is then shown, as shown in the following screenshot; there are no existing projects in this case:

Figure 11.19: The Help > About command shows the version as 11.0.1.0 A new project can be created, as shown in the following screenshot:

Figure 11.20: The File > New > Content Analytics Studio Project menu item is selected

The new project name can be entered, as shown in the following screenshot, and the default UIMA type prefix entered as where the com.asb prefix is a Java standard package naming convention; for example, for IBM software, it is usually

Package naming conventions are as defined at: https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html

Figure 11.21: The Project Name and UIMA Type prefix is entered, and Next> is clicked The next screen, as shown in the following screenshot, shows the default folders which can be automatically created for the project by clicking a tick box:

Figure 11.22: The Create folders for the new project tick box and Finish command are selected

The next screen shows the default IBM project and the fields entered to create a connection to the Linux ecmukdemo20 server.

The windows hosts file requires an entry for the ecmukdemo20 IP address, and the 8393 and 8390 ports need to be open on the Linux server by running the firewall commands as follows:

firewall-cmd --zone=public --permanent --add-port=8390/tcp firewall-cmd --zone=public --permanent --add-port=8393/tcp firewall-cmd –reload

Figure 11.23: Create a Content Analytics Server connection to ecmukdemo20

The existing collections and on the IBM Watson Content Analytics server are displayed after the connection is successfully created for the ecmukdemo20 server, as shown in the preceding screenshot. The administrator user, esadmin and the user’s password must be entered to make the connection. The IBM project example is installed automatically with the installation of IBM Watson Explorer Studio 11.0.1.

11.2: Incorporation of UIMA Apache Regular Expression Annotator

The simplest custom annotator for the UIMA pipeline is as follows, using a Java eclipse implementation:

Figure 11.24: The java code is the simplest example of a custom java annotator This requires the supporting .jar file, in the build path (from the regex annotator lib folder).

The full path of the Regex Annotator lib folder is {path to the

The validator simply returns false if the text in the pipeline matches the email address,

This can be extended to use a list of text values held in a database; the following example is an extension of the above, which searches for email addresses and URLs using an Oracle database.

This requires the supporting .jar file, in the build path (from the Regex Annotator lib folder) and the JDBC jar file from Oracle,

Add the resulting SimpleValidator.jar and the ojdbc6.jar to the lib folder of the Regex Annotator.

Figure 11.25: The jar files highlighted in the Class Path window are added Added the path to the SimpleValidator.jar to the classpath of the custom stage in the pipeline. We also have to edit the concepts.xml to include the new validator for email addresses:

id="urlAnnot" type="org.apache.uima.URLAddress" validate="org.apache.uima.annotator.regex.extension.SimpleValidator">

group="0" /> group="0" />

Figure 11.26: The section of the concepts.xml file with the reference to the custom annotator A table to hold White List data was created as follows:

Create a database schema user:

Oracle Create User - LINUX -------------------------------------------Create WHITELIST Database User, ICAUSER --------------------------------------------[wasadm@ecmukdemo20 ~]$ su - oracle

Password: filenet [oracle@ecmukdemo20 ~]$ sqlplus sys/filenet as sysdba CREATE USER ICAUSER IDENTIFIED BY filenet; GRANT SELECT on pending_trans$ TO ICAUSER; GRANT SELECT on dba_2pc_pending TO ICAUSER; GRANT SELECT on dba_pending_transactions TO ICAUSER; GRANT SELECT on DUAL TO ICAUSER; GRANT SELECT on product_component_version TO ICAUSER; GRANT SELECT on USER_INDEXES TO ICAUSER;

GRANT EXECUTE ON SYS.DBMS_SYSTEM TO ICAUSER; GRANT EXECUTE ON SYS.DBMS_XA TO ICAUSER; ALTER USER ICAUSER QUOTA UNLIMITED ON USERS; GRANT CREATE TYPE TO ICAUSER; GRANT GRANT GRANT GRANT

CREATE CREATE CREATE CREATE

VIEW TO ICAUSER; TABLE TO ICAUSER; CLUSTER TO ICAUSER; SESSION TO ICAUSER;

GRANT GRANT GRANT GRANT

CREATE CREATE CREATE CREATE

TRIGGER TO ICAUSER; SEQUENCE TO ICAUSER; DIMENSION TO ICAUSER; INDEXTYPE TO ICAUSER;

GRANT CREATE PROCEDURE TO ICAUSER; GRANT CREATE MATERIALIZED VIEW TO ICAUSER; alter user ICAUSER account unlock;

Create Database Tablespaces and Table --- ICA White List Oracle SQL Script -- Create tablespaces

CREATE TABLESPACE ICATableSpace DATAFILE 'ICATableSpace' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ONLINE PERMANENT ; CREATE TEMPORARY TABLESPACE ICATableSpaceTEMP TEMPFILE 'ICATableSpaceTEMP' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M EXTENT MANAGEMENT LOCAL ; -- Alter existing schema ALTER USER ICAUSER DEFAULT TABLESPACE ICATableSpace TEMPORARY TABLESPACE ICATableSpaceTEMP; GRANT CONNECT, RESOURCE to ICAUSER; GRANT UNLIMITED TABLESPACE TO ICAUSER; -- Drop table -- ALTER SESSION SET CURRENT_SCHEMA = ICAUSER; -- DROP TABLE ICAUSER.WHITELIST; -- Create table ALTER SESSION SET CURRENT_SCHEMA = ICAUSER; CREATE TABLE ICAUSER.WHITELIST ( LISTID VARCHAR(64) NOT NULL,

LISTTYPE VARCHAR(40) NOT NULL, LISTPOSITION VARCHAR(10) NOT NULL, LISTVALUE VARCHAR(512) NOT NULL ); -- Create grant ALTER SESSION SET CURRENT_SCHEMA = ICAUSER; GRANT INSERT,UPDATE,SELECT,DELETE ON WHITELIST TO ICAUSER;--- COMMIT; Create Oracle DBEXECUTE Procedure CREATE OR REPLACE PROCEDURE ICAUSER.UPDATE_WHITELIST ( LISTID IN VARCHAR2, LISTTYPE IN VARCHAR2, LISTPOSITION IN VARCHAR2, LISTVALUE IN VARCHAR2, LISTSTATUS OUT INT ) IS v_STATUS  INT; BEGIN LISTSTATUS := 0; INSERT INTO ICAUSER.WHITELIST (LISTID, LISTTYPE, LISTPOSITION, LISTVALUE ) VALUES (LISTID, LISTTYPE, LISTPOSITION, LISTVALUE ); SELECT COUNT(*) INTO v_STATUS FROM ICAUSER.WHITELIST WHERE LISTID = LISTID; LISTSTATUS := v_STATUS; END;

/

Test the stored procedure on Oracle SQL> variable CALLSTATUS NUMBER; SQL> execute ICAUSER.UPDATE_WHITELIST ('ICA1_CaseInvestigation_000000280005','ICA1_URLAddresses','13',' http://alan-bluck.simplesite.com/442375815',:CALLSTATUS); PL/SQL procedure successfully completed. SQL> print CALLSTATUS;

CALLSTATUS ---------1

SQL> select * from ICAUSER.WHITELIST; LISTID ---------------------------------------------------------------LISTTYPE     LISTPOSITI ---------------------------------------- ---------LISTVALUE -------------------------------------------------------------------------------ICA1_CaseInvestigation_000000180004 ICA1_URLAddresses    13

http://alan-bluck.simplesite.com/442375815 The following Java code uses the preceding Oracle table:

/** * */ /** * @author Alan S. Bluck * */ package org.apache.uima.annotator.regex.extension; import java.sql.Connection; import java.sql.DriverManager; import java.sql.PreparedStatement; import java.sql.ResultSet; //import org.apache.uima.annotator.regex.extension.Configuration; public class WhiteListValidator implements org.apache.uima.annotator.regex.extension.Validation{ private String WhiteList = //ASB make this available for multiple calls private static boolean connect = private static Connection connection = private static ResultSet resultRows = private static PreparedStatement pstmt = private static final String jdbcDriverClass = "oracle.jdbc.driver.OracleDriver"; public boolean validate(String coveredText, String Exception{ //Retrieve rows for testing from the Whitelist Database //Load class into memory //Establish connection != connection = "ICAUSER", "filenet"); }

!= pstmt = Distinct LISTVALUE FROM ICAUSER.WHITELIST"); } resultRows = while WhiteList = return } return else return sqle){ return != { // connection.close(); } != // resultRows.close(); } } The preceding code is optimised, so that the connection is left open between calls, by checking the connection object, so that only one connection call is made during the processing. Since hundreds of calls to the routine are made during the analysis of even one file, this optimisation is very significant!

11.3: Transfer of a Custom Annotator to the ICA Server

Deployment of the Custom Annotator from IBM Watson Content Analytics Studio.

The Oracle ojdbc6.jar file deployed with the .pear file is compatible across all platforms (Windows and Linux).

Select the Project Configurators Annotator node, right mouse-click and select Export… as shown in the following screenshot:

Figure 11.27: Select the required annotator to be exported as a pear file

Select UIMA Pipeline to Watson Content Analytics Server and click

Figure 11.28: The UIMA Pipeline to Content Analytics Server is selected

Set the PEAR output file name and Custom Annotator component name, and click

Figure 11.29: The Export Pear file to local file is ticked and Next> command button clicked Select the Watson Content Analytics Server, ecmukdemo20, and click

Figure 11.30: The server, ecmukdemo20, configuration is selected

Select the collection required:

Figure 11.31: Select the ecmukdemo20 server Enron Mail collection Select and update the Facets required and click

See the following link for a full description of the Faceted search in content analytics collections:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.discovery.es.ad.doc/iiysafacetsta.html Described in brief, as follows:

In a content analytics collection, you select facets to explore analyzed content and discover patterns, trends, and deviations in data over time. Determining which facets are displayed to analysts, and what data contributes to each facet is a critical design task for successful content mining.

Figure 11.32: The required Facets are added

The facets are edited and additional facets can be selected using the Add command button:

Figure 11.33: The Text Analysis Engine is named ICA1 Update the Text Analysis Engine Name field name and click

Figure 11.34: The progress of the ICA1 pear file is displayed in the status bar

PEAR file is built, exported, and then imported to the Watson Content Analytics Server specified: Reference is as follows:

For details of the installation of the server see the following link:

https://doi.org/10.13140/RG.2.2.11327.66721 IBM Watson Explorer Foundational Components 12.0.3.0 Installation and Configuration on CentOS Linux

The download of the components for IBM Watson oneWEX and IBM Watson Explorer Foundational Components is fully covered in

the publication: https://doi.org/10.13140/RG.2.2.12248.44803

Figure 11.35: The Enron Collection, ICA1 System Text Analysis Engine is viewed The IBM Watson Explorer Annotation Administration Console is used to view the transferred System Text Analysis named ICA1 in

the Enron collection:

Figure 11.36: The Details of the ICA1 engine can be viewed

For another full step-by-step Custom Java Annotator example, see the following tutorial: Reference link is as follows: https://uima.apache.org/d/uimaj3.0.0/tutorials_and_users_guides.html#ugr.tug.application

Conclusion

In this chapter, we covered the download and installation of IBM Watson Explorer Studio 11.0.1, and the creation of two examples of Custom Annotators using the Java programming language, including integration with an Oracle database table. The step-bystep procedure to deploy the resulting jar files as a UIMA .pear file to an IBM Watson Content Analytics server are also covered.

In Chapter 12, IBM Watson Explorer Foundational Components we will cover the step-by-step installation of IBM Watson Explorer Foundational Components 12.0.3 together with example use on the CENTOS 8.0 Linux Operating system.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software.

The IBM JVM version IBM Java 8.0 folder is an essential software prerequisite for the installation to load correctly.

The sub-folder ibm_sdk80 must be unpacked and copied to the Windows Java folder as a sub-folder.

For the IBM project example to be installed automatically, the default studioworkspace folder path has to be used during the installation.

The supporting Oracle ojdbc6.jar (if required) and the Custom Annotator jar file deployed with the .pear file must be added to the custom classpath for the engine.

Multiple Choice Questions

What must be installed before the installation of the IBM Watson Explorer Studio 11.0.1 can be loaded?

The Oracle ojdbc6.jar file

The Apache uima-an-regex.jar file The IBM Java 8.0 SR JVM folder, ibm_sdk80

The custom java annotator SimpleValidator.jar file

What file must be edited with the custom annotator package name for the Custom Annotation Engine to process the text in a collection?

The pear file

The concepts.xml file

The WATSON_EXPLR_CAS_V11.0.1_WIN_EN.zip file The uima-an-regex.jar file

Which software is used to view the transferred pear file containing the Custom Annotator?

The IBM Watson Explorer Content Analytics Studio

The IBM Watson Explorer Foundational Components 12.0.3.0 installer

The IBM Watson Annotation Administration Console

The IBM Development Package for Eclipse UIMA stands for:

Universal Information Management Analysis Unstructured Information Management Architecture

Unlimited Information Machine Analysis Unstructured Information Management Application

Multiple Choice Answers

c. The IBM Java 8.0 SR JVM folder, ibm_sdk80 b. The concepts.xml file

c. The IBM Watson Annotation Administration Console

b. Unstructured Information Management Architecture

Questions

After downloading the windows .zip file for the IBM Watson Explorer Studio 11.0.1, what steps would you use before running the installation program?

Where would you find the concepts.xml file, and what would you do to incorporate a Custom Annotator package reference in this file? What procedures would you use to check that a server collection had the Custom Annotator text analysis engine?

If you saw a pop-up window with the message shown as, Windows error 2 occurred while loading the Java what procedure would you follow to fix this?

Key terms

Unstructured Information Management Architecture Software Development Kit

Java Virtual Machine

Java Runtime Environment IBM Content Analytics

Annotation Administration Console

Processing Engine Archive file is the UIMA standard packaging format for UIMA components

CHAPTER 12 IBM Watson Explorer Foundational Components V12

Introduction

This chapter describes the step-by-step installation of IBM Watson Explorer Foundational Components 12.0.3, together with example use on the CENTOS 8.0 Linux operating system created as described in earlier chapters.

The full screenshots for the procedures discussed in this chapter can be found in my publications on ResearchGate with the URLs, as follows: https://doi.org/10.13140/RG.2.2.11327.66721

IBM Watson Explorer Foundational Components 12.0.3 Installation and Configuration on CentOS Linux

https://doi.org/10.13140/RG.2.2.12248.44803

Watson Explorer 12.0.3 oneWEX Installation on IBM Cloud CENTOS 8.0 Linux with Docker

(The preceding URLs covers the download and initial installation of rpm packages used in this document.)

https://doi.org/10.13140/RG.2.2.20256.94729

IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux 8.0.

The preceding URL describes the installation of the base CENTOS 8.0 Linux system for this document.

Structure

In this chapter, we will discuss the following topics: Watson Foundational Component Installation

Install Annotation Administration Console

Install Application Builder Configuration of Application Builder

Starting the services in order

Install the ZooKeeper service

Install the Results Module service

Install the AppBuilder Service

Stopping services Open the ports on the firewall service

Add oneWEX Datasource

Install Watson Explorer Engine

Installing the SIRE RPM file for Watson Explorer

Annotation Administration Console

Watson Explorer Engine administration tool installation

Encryption key generation Checks on the system

Display creation tutorial

Objectives

After studying this unit, you should be able to: Identify the prerequisite libraries required for each of the system components, which will be required to support the IBM Watson software versions targeted for installation.

Understand the prerequisite disk, memory, and network requirements for the target software components to be installed, and know how to configure them.

Search, identify, and download the latest Linux libraries, and configure the security required to maintain a secure and robust system.

12.1: Watson Foundational Component installation

Refer to the following links: http://www.redbooks.ibm.com/abstracts/sg247877.html

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.swg.im.infosphere.dataexpl.install.doc/c_module_oview.html The Watson Explorer foundational components are comprised of the following installable modules:

Application Builder

Used for developing the 360-degree information applications that filter data that is most relevant to users.

Watson Explorer Engine

This is a web-based development and deployment environment for internet navigation applications. Annotation Administration Console

This is a web-based administration tool for configuring custom annotators (see the examples in Chapter 11, UIMA Pipeline and Java Code for text analytics that provide additional filters for Watson Explorer content mining applications.

IBM Knowledge Center

This is a web site provided as help for IBM Watson Explorer Foundational Components.

Results Module

Enables administrators to easily extend applications with the capability of highlighting selected query results, and by incorporating their-specific knowledge such as taxonomies. ZooKeeper

Allows the load balancing of the services and associated data repository for storing configuration information across distributed applications. The available Watson Explorer foundational component modules are as follows:

follows: follows: follows: follows:

follows: follows: follows: follows:

Table 12.1: The list of modules supplied with IBM Watson Explorer Foundational Components V12.0.3

12.1.1: Install Annotation Administration Console

Run the following command: ./install.bin

The output message in a pop-up window will read as follows:

A library that is required for Linux operating systems is missing. You must install 'compat-libstdc++-33-3.2.3-61' before you run the installation program.

Additionally, if required, the packages from the Fedora project can also be accessed:

https://fedoraproject.org/wiki/EPEL

yum install -y epel-release yum-utils yum-config-manager --enable epel yum clean all && sudo yum update -y yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest8.noarch.rpm Refer to the following link:

http://mirror.centos.org/centos/7/os/x86_64/Packages/

The following fixed the missing library issue:

Figure 12.1: The two missing library install rpm packages are highlighted

Download and save the rpm packages: compat-libstdc++-33-3.2.3-72.el7.i686.rpm

and compat-libstdc++-33-3.2.3-72.el7.x86_64.rpm

Change the security on the rpm files: [root@ecmukdemo20 Downloads]# chmod 775 *.rpm [root@ecmukdemo20 Downloads]# ls compat-libstdc++-33-3.2.3-72.el7.i686.rpm  Container-PIT.zip ufone_tweets.csv compat-libstdc++-33-3.2.372.el7.x86_64.rpm  enron_mail_20150507.tar.gz

Install the 32-bit compat-libstdc++-33 library, as follows:

[root@ecmukdemo20 Downloads]# yum install compat-libstdc++-333.2.3-72.el7.i686.rpm CentOS-8 - AppStream  1.7 kB/s | 4.3 kB     00:02    …etc.. Installed: compat-libstdc++-33-3.2.3-72.el7.i686 Complete! [root@ecmukdemo20 Downloads]# ls compat-libstdc++-33-3.2.3-72.el7.i686.rpm  ContainerPIT.zip           ufone_tweets.csv compat-libstdc++-33-3.2.372.el7.x86_64.rpm  enron_mail_20150507.tar.gz Install the 64-bit compat-libstdc++-33 library:

[root@ecmukdemo20 Downloads]# yum install compat-libstdc++-333.2.3-72.el7.x86_64.rpm cd /opt/watson/wex-aac-1515-dae/

Figure 12.2: The folder path to the installation program binary

./install.bin Although the default font-size was impossibly small to read, it is possible to use cut and paste to view and modify each of the

fields (if the defaults are not required).

Figure 12.3: The User and password are entered (cut and paste to view and modify) The following bullet points list the Fields entered in boxes in Figure which were verified using cut and paste: Host ecmukdemo20.asbsoftware.co.uk User esadmin

filenet

Click on Advanced Options On the next screen, the fields were entered as follows: Installation /opt/IBM/es Data /home/esadmin/esdata

Common communication layer (CCL) 6002

Data storage 1527 Search server 8394

Figure 12.4: The installer detects an existing file in the folder path This can happen if a previous release is already installed, and may need to be maintained for the preservation of analytical data.

Change to the following: Installation /opt/IBM/es2 On the next screen, the default options, as follows, are set, which can be changed if required:

Administration console 390 Text analytics API 8393

Figure 12.5: The installed programs are started using ./startall.sh

The following examples demonstrate how to stop and start the system and administer the crawler server, using the esadmin command:

Example 1: To start the

cd /opt/IBM/es2/bin ./esadmin system start Example 2: To view a report of all running sessions in the

esadmin report sessions -pid

Example 3: To add a crawler server to the

esadmin session configmanager addNode -nid node2 destination tango.svl.ibm.com -port $CCL_PORT -nodeRoot ~/test_es/node -role crawler

Use esadmin COMMAND help for more usage information on the command: [root@ecmukdemo20 bin]# ./esservice.sh Error:  Cannot locate a JAVA JRE to execute esservice.sh.  Terminating. [root@ecmukdemo20 bin]# yum install java Installed: java-1.8.0-openjdk-1:1.8.0.222.b10-0.el8_0.x86_64 copy-jdk-configs-3.7-1.el8.noarch java-1.8.0-openjdk-headless-1:1.8.0.222.b10-0.el8_0.x86_64 javapackages-filesystem-5.3.0-1.module_el8.0.0+11+5b8c10bd.noarch tzdata-java-2019a-1.el8.noarch lksctp-tools-1.0.18-3.el8.x86_64

12.1.2: Install Application Builder

The following Unix, yum installer command lines, are used to install the Application Builder component of the IBM Watson Foundational Components, version 12.0.3.0:

[root@ecmukdemo20 watson]# yum install wex-appbuilder-12.0.3.0dae_en.el6.rpm Installed: wex-appbuilder-12.0.3.0-2487.x86_64 Complete! [root@ecmukdemo20 watson]# yum install wex-bigindex-12.0.3.0dae_en.el6.rpm Installed: wex-bigindex-12.0.3.0-2487.x86_64 Complete! [root@ecmukdemo20 watson]#

12.1.3: Configuration of Application Builder

Refer to the following link: https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.swg.im.infosphere.dataexpl.install.doc/r_ab-config-ab.html

12.1.3.1: Default login credentials

User data-explorer-admin TH1nk1710

Refer to the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/t_de-ab-devappentities-user.html

Stop services

Make a backup of the server.xml file from the AppBuilder/wlp/usr/servers/AppBuilder directory, and then open the file in a text editor.

The following example shows the default Application Builder administrator user, data-explorer-admin, and sample user names and passwords: id="basic" realm="customRealm"> name="data-explorer-admin" password="TH1nk1710" /> name="user-1" password="password-1" /> name="user-2" password="password-2" />

12.1.4: Starting the services in order

Refer to the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_services.html#c_wex_native _services.dita

When starting the services, always: Start ZooKeeper first (Application Builder relies on ZooKeeper for configuration data).

Start all other services except Application Builder.

Start Application Builder last.

Refer to the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.fc.install.doc/c_wex_native_config_zk.html cd /opt/ibm/WEX/ZooKeeper [root@ecmukdemo20 ZooKeeper]# ./zookeeper-config Which language do you want to use for the configuration tool? The current language is ['en']. Other available languages are: ['en']:

Which port do you want ZooKeeper to listen on for clients? The port is currently Specify the directory to store ZooKeeper's data in. The current directory is Specify the ZooKeeper ID. It is currently Specify the servers and ports ZooKeeper's cluster will use. The current list is Provide any additional zookeeper configuration as a semicolonseparated list. The configuration is currently:

Do you want to install ZooKeeper's service? [y/N]: y [root@ecmukdemo20 ZooKeeper]# pwd /opt/ibm/WEX/ZooKeeper The ZooKeeper service will automatically start ZooKeeper whenever you restart a system on which it is installed. Installing the service is recommended.

[root@ecmukdemo20 ZooKeeper]# systemctl start zookeeper.service

12.2: Install the Results Module service

The Results Module updates the report query layout. This module is deprecated as of Watson Explorer 12.0.x.

https://www.ibm.com/support/pages/release-notes-ibm-watsonexplorer-foundational-components-version-120#new12031 Refer to Appendix C of the following link for details of the deprecated 12.0.x features:

https://doi.org/10.13140/RG.2.2.11327.66721

[root@ecmukdemo20 WEX]# cd /opt/ibm/WEX/ResultsModule [root@ecmukdemo20 ResultsModule]# ls daemon  intl  java  license  README.txt  resultsmoduleconfig  resultsmodule.properties  swidtag  wlp [root@ecmukdemo20 ResultsModule]# ./resultsmodule-config Which language do you want to use for the configuration tool? The current language is ['en']. Other available languages are: ['en']: Which port do you want Results Module to listen on? The port is currently [8081]: What virtual directory should Results Module use? It is currently [ResultsModule]: Do you want to install the service for Results Module? [y/N]: y

[root@ecmukdemo20 ResultsModule]# pwd /opt/ibm/WEX/ResultsModule [root@ecmukdemo20 ResultsModule]# systemctl start resultsmodule.service

12.2.1: Check the status of the Results Module service

Refer to the command, as follows: cd /opt/ibm/WEX/ResultsModule/wlp/bin/ ./server status ResultsModule

12.2.2: Install the AppBuilder service

Refer to the command, as follows: cd /opt/ibm/WEX/AppBuilder [root@ecmukdemo20 AppBuilder]# ./appbuilder-config Which language do you want to use for the configuration tool? The current language is ['en']. Other available languages are: ['en']: What virtual directory should Application Builder use? The name is currently [AppBuilder]: Which port do you want Application Builder to listen on? The port is currently [8080]: Which ZooKeeper instance or instances do you want to use with Application Builder? The currently used instance or instances are [localhost:2181]: Which namespace do you want to use for this instance of Application Builder? The currently used namespace is [production]: Do you want to install the service for Application Builder? [y/N]: y systemctl start appbuilder.service cd /opt/ibm/WEX/AppBuilder/daemon ./appbuilder.sysvinit

12.2.2.1: Start the services in this order

Refer to the command, as follows: systemctl start zookeeper.service systemctl start resultsmodule.service systemctl start appbuilder.service

systemctl enable zookeeper.service systemctl enable resultsmodule.service systemctl enable appbuilder.service

12.2.2.2: Stopping Services

Refer to the command, as follows: You must stop the services in this order. systemctl stop appbuilder.service systemctl stop resultsmodule.service systemctl stop zookeeper.service

12.2.3: Open the ports on the firewall service

Refer to the command, as follows: systemctl start firewalld systemctl enable firewalld firewall-cmd --zone=public firewall-cmd --zone=public firewall-cmd --zone=public firewall-cmd --zone=public firewall-cmd --zone=public firewall-cmd --zone=public firewall-cmd --reload

--permanent --permanent --permanent --permanent --permanent --permanent

--add-port --add-port --add-port --add-port --add-port --add-port

2181/tcp 43981/tcp 8080/tcp 8081/tcp 16777/tcp 16888/tcp

You can adjust the configuration of the application server by editing the server.xml file in the AppBuilder/wlp/usr/servers/AppBuilder directory of the installation, that is,

vi /opt/ibm/WEX/AppBuilder/wlp/usr/servers/AppBuilder/server.xml

Refer to the server.xml file. Refer to Appendix A – server.xml of the Application Builder web app for the full server.xml OOTB, in the document downloaded from the following link:

https://doi.org/10.13140/RG.2.2.11327.66721

Also, for the embedded IBM WebSphere Liberty server configuration the following link describes the server.xml file used by the deployed AppBuilder:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.appbuilder.doc/c_de-ab-systemwlp.html

12.2.4: Add oneWEX datasource

For a oneWEX data source, enter the fully qualified URL of the oneWEX instance. The URL takes the following form:

http://hostname:port/

https://localhost/admin/main/#/admin/datasets The process to use oneWEX as a data source for Application Builder is the same as for a Watson Explorer Engine backend:

Index the For oneWEX, that means that you upload data to the oneWEX instance.

Add the data source in Application In this case, the data source is oneWEX.

Create entity For you connect the entity types to an instance and collection.

Use the entity type as you develop your entity model and application.

Refer to the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.appbuilder.doc/c_onewex_ab_ds.html

12.2.5: Install Watson Explorer Engine

Refer to the command, as follows: [root@ecmukdemo20 watson]# yum install wex-engine-12.0.3.0dae_en.el6.rpm Installed: wex-engine-12.0.3.0-2487.x86_64 Complete! Install Results Module

[root@ecmukdemo20 watson]# yum install wex-resultsmodule12.0.3.0-dae_en.el6.rpm Installed: wex-resultsmodule-12.0.3.0-2487.x86_64 Complete!

Install ZooKeeper

[root@ecmukdemo20 watson]# yum install wex-zookeeper-12.0.3.0dae_en.el6.rpm Installed: wex-zookeeper-12.0.3.0-2487.x86_64 Complete!

Refer to the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.wks.integration.doc/anno-machine-export-upload.html

In the field for the path to the file, enter the path, including the name of the file, and click For example,

Refer to the following link for post-installation of the supporting Statistical Information and Relation Extraction (SIRE) RPM file and the required libraries:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.wks.integration.doc/anno-machine-sire.html

Figure 12.6: The Desktop shows the installed Watson Explorer Deep Analytics Edition icon The URL link below provides a set of links to video tutorials on the use of the IBM Watson Content Analytics miner software: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.discovery.es.tm.doc/iiyscviewlet.html (Note, that although there is a broken link issue with the first “Getting Started…” video link, the other 10 videos are a very useful introduction to the software)

12.2.6: Installing the SIRE RPM file for Watson Explorer

The procedure is as follows: Install the required libraries, by running the following command:

[root@ecmukdemo20 watson]# yum -y install apr apr-util boostfilesystem boost-iostreams boost-program-options boost-regex boostserialization Installed:

apr-1.6.3-9.el8.x86_64     apr-util-1.6.1-6.el8.x86_64

boost-filesystem-1.66.0-6.el8.x86_64 boost-serialization-1.66.06.el8.x86_64

apr-util-bdb-1.6.1-6.el8.x86_64   apr-util-openssl-1.6.1-6.el8.x86_64

Complete!

Install the SIRE ES_INSTALL_ROOT/bin/sire/sire-201604292.x86_64.rpm file by running the following command:

rpm -ivh sire-20160429-2.x86_64.rpm

Log in as the default content analytics administrator. The default user ID is

To set the SIRE environment variables, enter the following commands to restart the system:

esadmin system stopall esadmin system startall

12.3: Annotation Administration Console

Refer to the following link: http://ecmukdemo20:8390/ESAdmin/loginForm.jsp

Figure 12.7: The logon page for the IBM Watson Explorer Annotation Administration Console

To access the IBM Watson Explorer Annotation Administration Console, Login using the username and the password that was established during installation in Figure as shown in Figure above:

Using the esadmin user name, with the password filenet

Figure 12.8: The Create Collection command button is clicked

The preceding screen shows the Create Collection command button, which is used to create a collection source of files for analysis.

Figure 12.9: The Collection Name and path to the files to be analyzed is entered

The Custom location option is selected and a UNIX folder path entered for searching the collection of files to be analyzed. The Collection ID option is left with the default, and the analysis language is set as

Figure 12.10: The required annotators are selected for the UIMA pipeline by ticking the required boxes The required annotators are selected for the UIMA pipeline by ticking the required boxes. The last box shown is for a Custom Annotator, which we covered in Chapter 11, UIMA Pipeline and Java code

Figure 12.11: The deploy analytic resources icon is clicked (set to 100% stopped) The Collections tab, shown in the preceding screenshot, can now be selected to process the collection.

12.4: Watson Explorer Engine administration tool installation

Refer to the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_config_engine.html

12.4.1: Encryption key generation

A default encryption key is included when you install Watson Explorer Engine. To change this, follow:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_config_engine_enc.html

This change is recommended by IBM.

12.4.2: Checks on the system

Refer to the following command: mkdir /opt/tests

Use the following command to test the installed system:

/opt/ibm/WEX/Engine/bin/micro-test --all /opt/tests Requires at least 40 GB of free disk space.

Check log results, as follows:

[root@ecmukdemo20 bin]# mkdir /opt/tests [root@ecmukdemo20 bin]# /opt/ibm/WEX/Engine/bin/micro-test -all /opt/tests System micro-test tool. Run with --help for information about individual tests. Starting full run. Starting mktemp test: 20000 reps, P=0.00, dir=/opt/tests/microtest-temp. 20000  20000 0.06 ms/temp Starting buffered write 42949672960 bytes in /opt/tests/micro-testtemp 40900  40960 110.76 MB/secc

Waiting for I/O to be flushed to disk. 40960  40960 103.44 MB/sec Starting buffered read test : /opt/tests/micro-test-temp 40960 94.51 MB/sec Starting seek test: /opt/tests/micro-test-temp, nthreads=16, block_size=8192, n_blocks=976562, ms=30000 228.63 seeks/sec Starting unbuffered write test: 1073741824 bytes in /opt/tests/micro-test-temp 1024   1024 509.71 MB/sec

Starting unbuffered read /opt/tests/micro-test-temp 1024 665.80 MB/sec Starting sqlite-insert 5000 inserts 5000 527.26 inserts/sec Starting sqlite-insert-transaction test: 5000 inserts 5000 90909.09 inserts/sec Starting sqlite-insert-indexed 5000 inserts 5000 79365.08 inserts/sec Starting sqlite-select 5000 selects 5000 1613.42 selects/sec Starting sqlite-select-indexed 5000 selects 5000 3516.17 selects/sec Starting sqlite-update 5000 updates 5000 2777.78 updates/sec Starting sqlite-update-indexed 5000 updates 5000 31446.54 updates/sec Starting sqlite-update-text-indexed test: 5000 updates 5000 61728.39 updates/sec Starting sqlite-delete 5000 deletes 5000 570.78 deletes/sec Starting sqlite-delete-transaction 5000 deletes

5000 5347.59 deletes/sec Starting sqlite-delete-indexed test: 5000 deletes 5000 83333.34 deletes/sec Starting the xsl test. 100 iterations xslt result 15 ms Starting virus scanner test: 5 reps 6 sleep /opt/tests/micro-testtemp virus scanner not detected Checking ability to create core dumps: Overall, the check(s) passed with warnings. The "system-wide core dump handler" check passed with warnings (reason: core dumps will be captured by a non-kernel process: /usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e ). The "value of RLIMIT_CORE" check passed (reason: core dumps are enabled and there is no restriction on core dump size). Results: Temporary file creation: 0.06 ms Buffered Write speed:    103.44 MB/sec Buffered Read speed:     94.51 MB/sec Unbuffered Write speed:  509.71 MB/sec Unbuffered Read speed:   665.80 MB/sec Unbuffered Seek rate:    228.63 seeks/sec Virus scanner detected:  no sqlite-insert time:              527.26 inserts/sec sqlite-insert-transaction time:  90909.09 inserts/sec sqlite-insert-indexed time:      79365.08 inserts/sec sqlite-select time:              1613.42 selects/sec sqlite-select-indexed time:      3516.17 selects/sec sqlite-update time:              2777.78 updates/sec

sqlite-update-indexed time:      31446.54 updates/sec sqlite-update-text-indexed time: 61728.39 updates/sec sqlite-delete time:              570.78 deletes/sec sqlite-delete-transaction time:  5347.59 deletes/sec sqlite-delete-indexed time:      83333.34 deletes/sec Runtime environment’s ability to create core dumps: passed with warnings Consult the documentation to properly understand and interpret your system’s ability or inability to create core dumps: xsl time:    15.39 ms [root@ecmukdemo20 bin]#

12.4.2.1: Configure the Watson Explorer Engine embedded webserver (non-production use only) Refer to the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.install.doc/c_velocity-web-serverconfiguration.html

Running embedded-webserver-config This command can also be rerun to change the parameters after stopping the engine, using the following command:

./engine-shutdown

The port 9080 is already used by the acce tool on the FileNet P8 container, so I am using 19080:

netstat -nlp 9080|grep 9080

Figure 12.12: The netstat tool shows the status of a network port, 9080 is already used by docker-proxy as a listen port

cd /opt/ibm/WEX/Engine/bin ./embedded-webserver-config Which language do you want to use for the configuration tool? The current language is ['en']. Other available languages are: ['en']: Specify the virtual directory for the embedded webserver to place Engine in. It is currently [vivisimo]: Do you wish to enable debugging mode for the embedded webserver? [y/N]:

y

Use N for production deployments!

Specify the group that the embedded webserver's workers will run in. It is currently Specify the hostname that the embedded webserver should use. It is currently Specify the port the embedded webserver will listen on. It is currently using [9080]: 19080 (The port was changed to avoid a clash with existing installed systems) Specify the user that the embedded webserver will run its workers as. It is currently [apache]: Do you want to enable the embedded webserver? [y/N]: y [root@ecmukdemo20 bin]# Once the Watson Explorer Engine embedded webserver is started, the Watson Explorer Engine installation can be completed by

accessing the Watson Explorer Engine administration tool through the IBM WebSphere embedded web server. The URL for the Watson Explorer Engine embedded web server can be obtained using the ./engine-status command. This is stated in the IBM documentation as embedded-webserver but this just gives the following:

Figure 12.13: The command ./embedded-webserver is-running is used

http://ecmukdemo20.asbsoftware.co.uk:19080/vivisimo/cgi-bin/admin

Open the port 19080 on the firewall: firewall-cmd --zone=public --permanent --add-port 19080/tcp firewall-cmd --reload cd /opt/ibm/WEX/Engine/bin ./embedded-webserver start ./engine-status

Figure 12.14: The ./engine-status command is used to display the URL we need to use

Refer to the following link: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_accessing.html Using the URL, as follows, the IBM Watson Explorer is loaded: http://ecmukdemo20.asbsoftware.co.uk:19080/vivisimo/cgi-bin/admin

Figure 12.15: The URL returned in figure 12.14 is used to load the IBM Watson Explorer administration tool (highlighted states Successfully unpacked repository files) The login page is then loaded:

Figure 12.16: The logon page is shown to enable the logging onto the administration tool

12.4.2.2: Default login credentials

The credentials are as follows: data-explorer-admin TH1nk1710

Figure 12.17: The main IBM Watson Explorer administration Configuration Tab is displayed

The Zoom option of the web browser may be required to view some of the display parameters, as shown in the following screenshot:

Figure 12.18: The Simple tab can be seen more clearly using the Zoom option highlighted Zoom in to see the options more clearly!

12.4.2.3: To unpack the repositories

Select the main Configuration tab, then select example-sourcebundle from the Components tab on the Sources (default) line.

From this, select the Example News Sources link. This will show the Overview tab which has the BBC news link, which can then be selected. This then shows the four tabs below; the Testing tab can be selected, followed by the Execution tab.

The Custom Test opener will then show the test results run, as shown in the following screenshot:

Figure 12.19: The available internet resources (e.g. BBC News) can be viewed and processed

12.4.2.4: Help About

Pursue the following steps: Click on Help >

Figure 12.20: The Help About menu shows the version details

Click on the unpack option:

Figure 12.21: The Configuration files are shown unpacked and initialized

12.5: Display creation tutorial

Refer to the following links: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.engine.tut.display.doc/c_graphicaldisplays.html

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.engine.tut.display.doc/t_display-tutcreate-display.html

Figure 12.22: The New Project, “display-tutorial” project name is entered

Click on + on and enter display-tutorial based on the core project and

Figure 12.23: The Components tab is shown for the new project to allow for editing The preceding Components tab is displayed and the Displays component can now be edited, as shown in the following screenshot:

Figure 12.24: The display name (display-tutorial-display) is entered in the New Display

Click then enter the display name required; click on

Figure 12.25: The details of the Simple Theme display are shown in the administrator tool

The Display component is edited to select the required theme:

Figure 12.26: The edit option is clicked for the Display Click on edit on the project display-tutorial-display line:

Figure 12.27: The display-tutorial-display [xml] can be clicked to show the details Click on

Figure 12.28: The Project “display-tutorial” link is clicked as highlighted Click on display-tutorial beside the Project: label in the left-hand Watson Explorer Engine administration tool navigation menu. Enter testing as a search string and click on

Figure 12.29: The text testing is entered in the search box for analysis The following screen is then displayed:

Figure 12.30: The top 130 results of the search string are displayed from the BBC News Enter Jockey to see a subset (as in the IBM Tutorial!):

Figure 12.31: The search string is changed to ‘Jockey’ to show the top 123 results

My URL is as follows:

http://ecmukdemo20.asbsoftware.co.uk:19080/vivisimo/cgi-bin/querymeta?v%3Aproject=display-tutorial&query=Jockey Refer to the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.engine.tut.display.doc/c_display-tutcustomizing.html

Conclusion

In this chapter, we covered the download, installation, configuration, and some example usage of the IBM Watson Explorer Foundational Components V12.0.3.0 software. In the next chapter, we will describe the step-by-step installation of IBM Watson Explorer 12.0.3 oneWEX, together with example use on the CENTOS 8.0 Linux Operating system and the Cloud Private Docker system.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software.

Select the latest Base Product Version supported for your target environment and download it from IBM Software Catalog.

Search and download the latest Fix Pack (this is usually cumulative) to apply fixes to the base product.

When starting the services, always start ZooKeeper first, and the Application Builder component last.

When stopping the services, always stop the Application Builder first, and the ZooKeeper component last.

Multiple Choice Questions

Which module is deprecated as of Watson Explorer 12.0.x? Application Builder

Zookeeper

ResultsModule Annotation Administration Console

In what order must you stop the IBM Watson services?

zookeeper.service then

resultsmodule.service

zookeeper.service then

appbuilder.service resultsmodule.service then

zookeeper.service

resultsmodule.service then

appbuilder.service

In what order must you start the IBM Watson services?

zookeeper.service then

resultsmodule.service zookeeper.service then

appbuilder.service resultsmodule.service then

zookeeper.service resultsmodule.service then appbuilder.service

Which module is a web-based administration tool for configuring custom annotators?

Application Builder

Zookeeper

ResultsModule Annotation Administration Console

Multiple Choice Answers

c. ResultsModule c. resultsmodule.service then zookeeper.service

d. resultsmodule.service then appbuilder.service

d. Annotation Administration Console

Questions

What library, that is required for Linux operating systems, is missing, and what procedure would you follow to install it, before you run the installation program?

How would you provide a subset of IBM Requirements for IBM Watson Explorer 12.0.3.0 in a printed PDF document? What would you do to check the status of the Results Module service?

If you wanted to support the ability to generate thumbnails for certain types of documents in the search results using IBM Watson Foundational Components 12.0.3 on a Linux server, what libraries would you have to install?

How can you adjust the configuration of the embedded web application server used by IBM Watson Explorer?

Key terms

Statistical Information and Relation Extraction Libraries required for IBM Watson components

Uniform Resource Locator

Annotation Administration Console Extra Packages for Enterprise Linux, a group, providing additional rpm packages from the Fedora Project

OOTB: Out of the meaning, installed from the original software package without any changes or updates

CCL: Common Communication the prerequisite services used for intercommunication between the Watson

UIMA: Unstructured Information Management Architecture.

CHAPTER 13 IBM Watson Explorer oneWEX 12.0.3

Introduction

This chapter describes the step-by-step installation of IBM Watson Explorer 12.0.3 oneWEX, together with an example use on the CENTOS 8.0 Linux operating system, and the Cloud Private Docker system created as described in Chapter 10, IBM Cloud Private

The full step-by-step procedure screenshots are displayed in the Research Gate publications: https://doi.org/10.13140/RG.2.2.11327.66721

IBM Watson Explorer Foundational Components 12.0.3 Installation and Configuration on CentOS Linux

and

https://doi.org/10.13140/RG.2.2.20256.94729

IBM Cloud Private P8 Container CPIT Installation on CENTOS Linux The preceding link describes the installation of the base CENTOS 8.0 Linux system for this chapter.

Structure

In this chapter, we will discuss the following topics: Downloads

IBM Watson Explorer Deep Analytics Edition oneWEX Product details IBM Watson Explorer Deep Analytics Edition Analytical Components

Copy the Watson Analytics oneWEX installation downloads

IBM Watson Explorer Analytical Components

Extraction of the IBM Watson Explorer Deep Analytics oneWEX Edition

Installation of the IBM Watson Explorer Deep Analytics Edition 12.0.3

Installation of supporting Linux shared object libraries libXScrnSaver

Need to install the 64-bit version of the missing library shared object

Launch the IBM Watson Explorer GUI front end

Launch admin user interface

Add a collection for a file directory dataset

Download the Enron emails data to use as a dataset

CSV file example Docker installed IBM Containers

Objectives

After studying this unit, you should be able to: Identify suitable versions of each of the system components, which will be required to support the IBM Watson Explorer oneWEX 12.0.3 software versions targeted for installation.

Understand the prerequisite requirements for the target software components to be installed, and know where to look for them.

Give examples of the download of data for configuration of Collections, and the procedure to configure the IBM Watson Crawlers used to analyze a Dataset defined in a Collection.

13.1: Downloads

Refer to Chapter 1, IBM Section 1.4.1, Download estimated download time and versions for details of the product codes and files to be downloaded:

Figure 13.1: The product code, CJ5DNML is available to search downloads

13.1.1: IBM Watson Explorer Deep Analytics Edition oneWEX Product details For installation, after download of IBM Watson Explorer oneWEX docker container, the file name is as follows:

IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar

Figure 13.2: The product code, CC1G6ML is displayed for the oneWEX installation

13.1.2: IBM Watson Explorer Deep Analytics Edition Analytical Components For installation, after download of IBM Watson Explorer Analytical Components, the file name is as follows:

IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12.0. 0.html

Watson Explorer now includes oneWEX, a container-based component. OneWEX processes unstructured data. The IBM Watson Explorer Foundational Components include Watson Explorer Engine and Watson Explorer Application Builder; also, the IBM Watson Explorer Analytical Components, such as Watson Explorer Content Analytics and Content Analytics Studio:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_install_docker.html

Copy the oneWEX and other .tar files downloaded to the /opt/watson directory. Unpack the following downloaded .tar file:

IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar cd /opt mkdir watson cd watson

13.1.3: Copy the Watson Analytics oneWEX installation downloads

Copy from FTP transfer to /home/wasadm (using the VMware MasterBoot Cloud Private server):

[root@ecmukdemo20 tmp]# cd /opt/watson/ [root@ecmukdemo20 watson]# ls [root@ecmukdemo20 watson]# cp /home/wasadm/IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar . [root@ecmukdemo20 watson]# cp /home/wasadm/IBM_WE*.tar . [root@ecmukdemo20 watson]# ls IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar  IBM_WE_DEEP_ANA LYTICS_EDITION_EMB.tar

[root@ecmukdemo20 watson]# ls -lsa total 13283100 0 drwxr-xr-x.  2 root root          141 Sep 30 14:09 . 0 drwxr-xr-x. 10 root wasadm        148 Sep 30 07:06 .. 4717580 -rw-r--r--.  1 root root   4830801920 Sep 30 14:06 IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar 5094520 -rw-r--r--.  1 root root   5216788480 Sep 30 14:09 IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar

13.1.4: IBM Watson Explorer Analytical

Unpack the downloaded .tar file, and then the embedded .tar.gz zipped installation file for IBM Watson Explorer:

[root@ecmukdemo20 watson]# tar -xvf IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar ibm-wex-prod-12.0.3.935.tar.gz [root@ecmukdemo20 watson]# ls IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar  ibm-wex-prod12.0.3.935.tar.gz [root@ecmukdemo20 watson]# tar -zxvf ibm-wex-prod12.0.3.935.tar.gz charts/ charts/ibm-wex-prod-1.4.0.tgz images/ images/ibm-wex-ee_12.0.3.935-linux-amd64.tar.gz images/ibm-wex-hdp_12.0.3.935-linux-amd64.tar.gz images/ibm-wex-wksml_12.0.3.935-linux-amd64.tar.gz manifest.json manifest.yaml

Delete the unpacked .tar file to save disk space: [root@ecmukdemo20 watson]# rm IBM_WE_DEEP_ANALYTICS_EDITION_EMB.tar -rf

13.1.5: Extraction of the IBM Watson Explorer Deep Analytics oneWEX Edition The following Unix commands are required to extract the installer files for the IBM Watson Explorer oneWEX docker container:

[root@ecmukdemo20 watson]# tar -xvf IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar one-wex-installer-linux.tar Delete the unpacked tar file to save disk space:

[root@ecmukdemo20 watson]# rm IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar rm: remove regular file 'IBM_WAT_EXPLORER_DEEP_ANALYTICS_E.tar'? y [root@ecmukdemo20 watson]# tar -xvf one-wex-installer-linux.tar install.bin onewex.dat wksml.dat

13.2: Installation of the IBM Watson Explorer Deep Analytics Edition 12.0.3 The following command is run from a Unix command window to start the installation of the IBM Watson Explorer Analytics Edition:

[root@ecmukdemo20 watson]# ./install.bin

Accept the license to continue the installation. Then select the installation path, as shown in the following screenshot:

Figure 13.3: Enter the folder path for the IBM Watson Explorer installation

The path for installation and the disk space required (369 MB) for the Watson Explorer installation:

Figure 13.4: Review the installation parameters are displayed, and then click Install Edit the wex.json Docker Container configuration file. The Watson Explorer oneWEX configuration file is under the folder path An example is as follows:

{ "env" : { "SOLR_MAX_HEAP" : "8g", "DOCPROC_WORKER_NUM" : "2", "SQLR_PER_NODE" : "1", "DOCPROC_MAX_MEMORY" : "4g", "ZK_MAX_HEAPSIZE" : "2g", "ZK_MIN_HEAPSIZE" : "1024m", "WLP_JVM_MAX_MEMORY" : "2g" }, "port" : 443, "name" : "wex12dae", "wexDataVolume" : "wex12dae", "dockerImage" : "ibm-wex-ee:12.0.3.935", "wksmlImage" : "ibm-wex-wksml:12.0.3.935", "wksmlContainerName" : "wksml-service", "restart" : "unless-stopped" }

Refer to the following link: https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_install_docker.html

wex.json edited to increase the memory limits and changed to the following:

Figure 13.5: The wex.json file is edited to the highlighted parameters

13.2.1: Installation of supporting Linux shared object libraries libXScrnSaver Use ./wexdocker.sh to stop and restart the system. The shared library for X-Windows is required to be installed first:

yum install libXss.so.1

First time using the following command: ./ibmwatsonexplorer

It may give an error message, as the following:

wrong ELF class ELFCLASS32

Refer to Section 13.2.2 to correct this.

13.2.2 Need to install the 64-bit version of the missing library shared object Check if you do get the following message:

yum install libXScrnSaver [root@ecmukdemo20 bin]# cp /usr/lib/libXss.so.1 .

13.3: Launch the IBM Watson Explorer GUI front end

Execute the following command to launch the IBM Watson Explorer oneWEX login splash screen to select either the IBM Watson Miner web user interface (the left-hand panel), or the Administration user interface (the right-hand panel):

[root@ecmukdemo20 bin]# ./ibmwatsonexplorer

Figure 13.6: The IBM Watson Explorer program is launched for logon

Login as admin with password as

13.3.1: Launch admin user interface

Refer to the following screenshot:

Figure 13.7: The browser flags that the https security certificate is required

The HTTPS certificate is missing, so click on

Figure 13.8: The Browser security certificate exception option Add Exception is selected

Click on Add Exception… as highlighted in the preceding screenshot:

Figure 13.9: The Confirm Security Exception command is selected Click on Confirm Security

Figure 13.10: The logon page for IBM Watson Explorer is displayed

Log into the IBM Watson Explorer web application:

Figure 13.11: Click on the Add collection command button Click on Add collection to create a new collection.

13.3.2: Add a collection for a file directory dataset

The collection for analysis, can be created by crawling a file directory and its subdirectories and is established using the following screenshot as a starting point:

Figure 13.12: The Next command button is selected

Click on

The Collection Template options are as follows:

Content Mining (selected with a tick, as shown in the preceding screenshot) for general content mining

Sentiment Analysis (for sentiment analysis, determines if the text from a writer is positive, negative, or neutral)

Search (for a text search, using a search text string to locate all the occurrences.)

Figure 13.13: The collection name and description are entered, then Next is clicked

Enter the collection details, and click on

Figure 13.14: The File system tab is selected to load a file from a folder path mount point

Select the File system option for the dataset to be selected from a folder path.

13.3.3: Download the Enron emails data to use as a dataset

The description of this test email dataset is shown in the following link:

https://www.cs.cmu.edu/~enron/

(The above URL was searched for, using the Google search text: Enron emails data to use as a dataset

currently the top URL link result returned, is as shown above.)

The .zip file download link is as follows:

https://www.cs.cmu.edu/~enron/enron_mail_20150507.tar.gz

There are around 0.5 million email messages obtainable from this link, as a downloadable .zip file:

Figure 13.15: The Enron zip file is downloaded and saved mkdir /var/enron chmod 777 /var/enron

cp enron_mail_20150507.tar.gz /var/enron cd /var/enron tar -zxvf enron_mail_20150507.tar.gz The preceding gzipped .tar file was unpacked to view the folder structure, and the actual data was able to be extracted by IBM Watson Explorer directly from the gzip file.

Refer to the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/t_onewex_fs_access_docker.html The local file system can be used by the Watson crawler, using the following procedure: cd to the directory where IBM Watson Explorer oneWEX is installed, and this using the program ./ibmwatsonexplorer on Linux. On the results screen of Watson™ Explorer oneWEX, click on >

Figure 13.16: The icon which is used for accessing the Mount option in a dropdown menu

Select a source folder to mount:

Figure 13.17: The Mount menu item is clicked

Enter the path to be used to access the source folder after /mnt/ in the Mount location option:

Figure 13.18: The + icon is selected to add the entered Source folder with mount point /mnt/maildr Refer to the following link:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/t_onewex_fs_access_docker.html Click on the + icon to add to a list of mount points for folder structure access:

Figure 13.19: The Apply and Restart command button is selected to complete the config

Click on Apply & Restart after adding the list of folders to be crawled:

Figure 13.20: The Dataset Name and Description are entered and the Create command clicked Enter the dataset name and description, as shown in the preceding screenshot, and click on the Create command button:

Figure 13.21: Click the Add crawler link, highlighted

Click on the Add crawler option with a + sign:

Figure 13.22: The File system Crawler type is selected from the dropdown list

Select the File system crawler from the Crawler type list, as shown in the preceding screenshot.

Figure 13.23: The Advanced options are selected for the File system Crawler properties I changed the Time to wait interval from 0 to 1 millisecond. This is between retrieval requests, so I changed this to reduce the CPU

and I/O loading.

Change the security recursively on the maildir folder: chown root:root -R maildir

This is required to allow the crawler engine process access to read the file system (it can process directories and content files recursively):

Figure 13.24: The highlighted Find and Add Action command button link is clicked

Find and add the file crawler details:

Figure 13.25: The crawl space root mount point is selected and Add is clicked Select the crawler root folder required for the collection:

Figure 13.26: The crawl space root child folders are clicked to add The Crawl space root option is opened to show the sub-folders to be added:

Figure 13.27: The Crawl space is saved The next screen shows the status of the Crawler after clicking on the Start crawling button:

Figure 13.28: The status of the Enron Mail Crawler is displayed

The status of the Enron Mail Crawler is shown, as Starting after the Start crawling command button is clicked in the Crawler control panel:

Figure 13.29: The document process count status is shown

Refresh shows 7,375 emails found so far. After several hours, 308,434 emails found -- ~ 200,000 to go:

Figure 13.30: The Crawler process Ingestion status is shown as Completed

The crawler completed with 517,402 emails discovered:

Figure 13.31: The Create a collection for importing a csv file - see section 13.3.4 The Content Mining option is selected and the Next command button is clicked:

Figure 13.32: The Content Mining option is selected for the Collection Template The name and description of the collection are prompted for entry:

Figure 13.33: The name and description for the collection are entered and Next is clicked

The dataset is added to the collection, as shown in the following screenshot:

Figure 13.34: The Enron Emails Dataset is added to the new collection

The sample document and field mappings screen is shown next:

Figure 13.35: The sample document and field mapping screen is shown The Enrichment step allows a selection of UIMA annotators to be chosen:

Figure 13.36: The Annotators are selected from a tick box list and Next is clicked The annotator types for selection are as follows: Parts of Extracts words and phrases from unstructured content.

Sentiment Extracts phrases and expressions for positive, neutral, or negative sentiment.

Named Entity Extracts person names, locations, organizations. Personal Identification Information Extracts personal identification information.

Figure 13.37: The facets are selected by scrolling and updating as required The Watson Explorer Content Miner Facet Editing is shown in the following link : https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_miner_dac.html The Facet types are also outlined in the following link:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.discovery.es.ad.doc/iiysafacetsta.html The screen shown below shows the collection saved for further analysis and

Figure 13.38: The collection is saved for processing The next screen shows the collection is in the process of indexing:

Figure 13.39: The status of the collection is shown as indexing The following links provide further detailed IBM Watson Explorer procedures: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/c_ee_miner_home.html https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.discovery.es.ta.doc/iiysspipelinetestdoc.html The following link has details for loading a CSV file into Excel:

https://support.video.ibm.com/hc/en-us/articles/207851757-How-toload-CSV-files-into-Excel

13.3.4: CSV file example

Refer to the following link: https://developer.ibm.com/tutorials/build-a-predictive-model-usingtweets/

The CSV data example downloaded from the link in the preceding tutorial, is as follows:

Figure 13.40: The CSV ufone_tweets.csv examples are downloaded for processing

The following window in figure 13.41 is used to drag and drop the downloaded CSV file for a collection dataset.

The CSV contains the facet data to be analysed, parsing options such as delimiters and headers (if any), data types of files, and field mappings are configured automatically. If the data type is the date format will be detected.

Refer to the following URL:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_ee_adm_quick_add_coll_with_csv.html

Figure 13.41: This window area is used to drag and drop a CSV file

Click on + and browse to the CSV file example (downloaded):

Figure 13.42: The sample document and field mapping screen is shown for ufone_tweets.csv

The two created collections are displayed, as shown in the following screenshot:

Figure 13.43: The ufone_tweets.csv collection is shown in the process of indexing The screen above shows the ufone_tweets.csv tutorial example file collection, which we downloaded and the status shows that the crawler engine is in the process of importing and indexing the csv file. On completion of this Import and Index process, the icon status is shown in the next screen with a 100% Indexed status inside the red circle:

Figure 13.44: The status of the CSV collection, ufone_tweets.csv is shown as Ready to Analyze

The ufone_tweets.csv file indexing is completed, ready for analysis, as shown in the following screenshot:

Figure 13.45: The ufone_tweets.csv is clicked as highlighted

Click on

Figure 13.46: The count of the occurrences of each of the facets is displayed for selecting

The magnifying glass can be clicked, as shown in the preceding screenshot.

Figure 13.47: The required Facet Analysis or display types can be selected

The Show Analysis Dashboard option is selected:

Figure 13.48: The target facets are displayed in a scrollable histogram with counts I selected the Target Facets highlighted on the right panel, as shown in the preceding screenshot.

13.4: Docker installed IBM Containers

The following command can be used to display the supporting containers used for IBM Watson Explorer oneWEX:

docker ps

Figure 13.49: The docker ps command is used to show the highlighted containers for IBM Watson oneWEX

Conclusion

In this chapter, we covered the download, installation, configuration, and some example usage of the IBM Watson Explorer oneWEX container V12.0.3.0 software. In the next chapter, we will describe the step-by-step installation of IBM StoredIQ for Legal VM 2.0.3.7 Server Installation, together with an example use.

Points to Remember

First search for and check the contents on the IBM Release Notes for the software.

Select the latest base product version supported for your target environment and download it from IBM Software Catalog.

Search and download the latest Fix Pack (this is usually cumulative) to apply fixes to the base product.

The actual crawler dataset can be extracted by IBM Watson Explorer directly from a gzip file.

Change the security recursively on the File system crawler folder using chown root:root -R filesystemrootpathfolder.

Multiple Choice Questions

Which file can be edited to modify memory, ports, mount points, and other properties for Watson Explorer oneWEX configuration?

wex.json

ufone_tweets.csv wexdocker.sh

onewex.dat

The Crawler Type list includes which one of the following?

Access

Excel

File system Mount points

In what order are collection steps used to process a collection?

Dataset, Fields, Enrichment, Facet, Create

Create, Dataset, Fields, Enrichment, Facet

Fields, Enrichment, Facet, Create, Dataset

Enrichment, Facet, Create, Dataset, Fields

What would you do if you got the following message?

libXss.so.1: wrong ELF class ELFCLASS32

Use yum to install Gnome GUI packages Use yum to install libXss.so.1

Use yum to install libXScrnSaver Use yum to install yum-utils

Multiple Choice Answers

a. wex.json c. File system

b. Create, Dataset, Fields, Enrichment, Facet

c. Use yum to install libXScrnSaver

Questions

What library, that is required for Watson oneWEX, gives the message, wrong ELF class and what procedure would you follow to install it, before you run the installation program?

Name three of the available Watson oneWEX statuses and describe what they mean. What does the Linux rm command do, and why would you use it?

Outline the procedural steps to use to create a collection dataset for analyzing a .csv file of tweets?

Key terms

ELF: Executable and Linking Format binary files. These files include executable .bin files and shared object library files. A full description can be found in the following link:

https://man7.org/linux/man-pages/man5/elf.5.html

Graphical User Comma Separated A format used for spreadsheets and columnbased field data.

CHAPTER 14 IBM StoredIQ for Legal VM 2.0.3.7 Server Installation

Introduction

This chapter describes the step-by-step installation of the StoredIQ for Legal VM 2.0.3.7 Docker Container VM system for VMware and initial testing using example workflows, and backup on the CentOS 7 Linux system.

Structure

In this chapter, we will discuss the following topics: IBM StoredIQ for Legal V 2.0.3.7 server installation steps for VMware Workstation Pro 15.5.6

Creating a test Business Process Modeling Notation workflow Adding an Lightweight Directory Access Protocol server

Configuring data requests

SMTP server gateway

Adding roles to users

StoredIQ for Legal (VM): Root certificate import

Approval process BPMN refined approval workflow Backup of StoredIQ for Legal databases

Objectives

After studying this unit, you should be able to: Locate and download the required software packages for installation.

Understand the prerequisite requirements for the target software to be installed, or know where to look for them. Identify suitable versions of each of the system components, which will be required to support the IBM StoredIQ software versions targeted for installation.

Search, identify, and download the latest Fix Packs required to maintain a secure and robust system.

14.1: IBM StoredIQ for Legal V 2.0.3.7 server installation steps for VMware Workstation Pro 15.5.6 For the OVF format to VMware runtime format, you can import both, .ovf and .ova files. Using VMware Workstation Pro VMware, Inc. 68 OVF is a platform-independent, open source packaging and distribution format for virtual machines. For example, you can import OVF virtual machines.

On IBM’s download site, you can select from the available versions of the virtual machine OVF file. For details of the download, refer to pages 5 to 10 of the following link:

https://doi.org/10.13140/RG.2.2.12586.24008

This is downloaded as the following file:

IBMStoredIQforLegalVM2.0.3.7Installation.docx

The Virtual Machine OVF file is copied to the 64 GB memory server, F:\ drive (this has an 8 Core Xeon Silver 4108 processor) on my test server. The first step is to recreate the package from the downloaded .ova file. For this, the 7zip utility (or a similar utility) was used to extract the files in the .ova file/package into a new folder. Using

this, the .ova file package is extracted into a new folder into its constituent and vmdk files:

Figure 14.1: The downloaded OVA file is extracted using 7-zip

I used 7-zip to extract the OVA file, as shown in the preceding screenshot.

I first tried to use the VMware Workstation Pro File > Open on the .ova file, but got the following error message:

Figure 14.2: The Error message obtained trying to load the OVA file in VMware

Then, in Workstation Pro 15.5.6, use File > Open on the .ovf file; and get the following:

Figure 14.3: The storage folder path for the virtual machine is selected using the Browse… command button Browse to the G:\ drive (or any read/write drive with space) and create a sub folder:

Figure 14.4: The Make New Folder command is used to create the StoredIQ folder 1The Import Virtual Machine step is shown in the following screenshot:

Figure 14.5: The Import command is clicked to import the OVF file to VMware The status bar shows the progress of the import of the StoredIQ VM server:

Figure 14.6: The status bar shows the progress of the VM import to VMware

This VMware virtual server has 14 GB and 4 processors and can now be started. It is based on CentOS 7. Refer to the following links:

https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_va_configure.html

https://www.ibm.com/support/knowledgecenter/SSSHEC_7.6.0/deploy /tsk/tsk_install_dataservers.html Please check the PDF in the following link:

https://www.ibm.com/support/pages/sites/default/files/inlinefiles/$FILE/IBMSIQDeploymentConfigGuide76020_0.pdf

Once the license details are displayed, select I

Figure 14.7: The Keyboard keys used to navigate and enter the configuration options I hit to give:

Figure 14.8: The I agree option is selected after reviewing the license details Then click on the Repeat using Tab to get the following:

Figure 14.9: The I agree option is selected again after clicking the space bar and Tab key

Then, click on the Enter key (I had to do this twice). Enter the password required:

Figure 14.10: The Unix password for root is created

Characters are not echoed; if you make a mistake, you can keep re-entering the password and eventually it prompts for the first password entry again!

Figure 14.11: The administrator user, ilgadmin, password is entered and recorded for use later

Record this password for future reference. However, this password can be changed later by running the /siq/bin/change_ilgadmin_password.sh script. The script requests the old and the new password as input, and must be run as root user.

You are now prompted for the machine name and the domain I used:

Figure 14.12: The Fully Qualified Domain machine server host name is entered for the VM

Tab to OK and press Return:

Figure 14.13: The hostname is set after clicking the OK button Press Return to OK the update.

Tab as required, and enter connection requirements and press Return on (Note that the defaults are already filled and can be used as shown):

Figure 14.14: The ethernet network card MAC address and MTU is entered as required The system reboots. Enter the password that we set earlier for

Figure 14.15: The root password is entered to log in as the root user The StoredIQ server is now up and running in VMware Pro 15.5.6.

Use the following command:

ifconfig|more

Figure 14.16: The IP address for the ens32 network card is displayed Find the ens32 network card (which we first used to set the server host name), and note the IP address 192.168.50.128 on our system.

Ping the IP address from the host windows server cmd.exe command window, in order to confirm the connectivity. Edit the Windows hosts file using Notepad launched as a Windows Administrator, and enter the ecmukdemo30 IP address to allow the StoredIQ server installation to be accessed from the VMware host. (Using the right-mouse, click on the Notepad icon):

Figure 14.17: The notepad.exe program, run as administrator to allow editing of the host’s file

Click on Navigate to the C:\Windows\System32\drivers\etc\hosts to load the file:

Figure 14.18: The Windows hosts file with the highlighted additional VM IP address Enter the IP address, as shown in the preceding screenshot. Save the hosts file:

Figure 14.19: The pop-up asks for confirmation that the existing hosts file is to be updated Test in the Command Prompt:

Figure 14.20: The VM host name is tested using the ping command In a browser, use the URL as follows:

https://siqserver/navigator

Where siqserver stands for the fully qualified host name, or the IP address of the StoredIQ for Legal server.

I used the following link: https://ecmukdemo30.asbdoftware.co.uk:9443/navigator

Figure 14.21: The security certificate is flagged as not in the list of trusted certificates

Click on then proceed as highlighted:

Figure 14.22: The logon page for the StoredIQ for Legal web client system is displayed

Log into the StoredIQ for Legal web client, using the administrative user name and password.

The default login ID of the administrative user, is used with the password that was entered during installation of the VM. After a successful logon, the administration page is displayed as follows:

Figure 14.23: The Role assignments administration page is displayed

To reconfigure the VM, you can run the following applications from the console window:

window: window:

window: window: window: window: window: window: window:

Table 14.1: The available administration commands are listed Refer to the following link: https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_va_configure.html

14.1.1: Creating a test BPMN workflow

For the full detailed screenshot procedure, see the following link: https://doi.org/10.13140/RG.2.2.12586.24008

This is downloaded as follows:

IBMStoredIQforLegalVM2.0.3.7Installation.docx The reference link is as follows:

https://www.ibm.com/support/pages/node/711333

Figure 14.24: The BPMN Workflow review process page is displayed

The loaded BPMN file is as follows:

Figure 14.25: The BPMN file header and first part

Figure 14.26: The BPMN file second part

14.1.2: Adding an LDAP server

See the reference link as follows: https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_connection_directory.html

The Windows hosts file entry is set as follows, for an LDAP server: 192.168.50.129 ECMUKDEMO6 ecmukdemo6.asbsoftware.co.uk

User filter

Log into the administration web browser application:

https://ecmukdemo30.asbsoftware.co.uk:9443/navigator/

Figure 14.27: The StoredIQ for Legal login is displayed for Sign In

Click on the Admin tab, and select External as shown in the following screenshot:

Figure 14.28: The ecmukdemo6 directory server parameters are entered for user validation

Click on the Preview button: I mapped all attributes to cn as no other attributes were set up on the LDAP server for users at the time.

Figure 14.29: The StoredIQ for Legal is restarted to update for the directory service config Reboot the server, ecmukdemo30 with the root command

Figure 14.30: The Role Assignments administration page is displayed Select Catalog and the External Persons item, and then click Sync to list the LDAP server entries:

Figure 14.31: The list of users for role selection (using tick boxes) is displayed

The synchronisation status of the users held in the LDAP directory service is displayed in a pop-up window:

Figure 14.32: The Sync status is shown in a pop-up window The People page allows the following reference:

Figure 14.33: The users for the roles are selected by ticking the boxes Select users, the Profile option shows multiple users are selected and the list can be saved.

14.1.2.1: Assign roles

The Assign Roles window is shown as follows:

Figure 14.34: The user sue is selected for the required role

Select Role Assignments in the Admin tab, and select a user from the list of LDAP users, and click on

Click on Add to add the user (roles are selected in the base screen). Use the drop-down in the main screen to add the user role:

Figure 14.35: The users are added to the Roles by checking the dropdown list box of roles

If the user is selected already, they no longer appear in the available user list for Assigning Roles.

One or more roles can be assigned to a user; users are selected from a list using a check box, and the Next command button is clicked to show the selected users for the role assignment:

Figure 14.36: The Save command is used to update the configured user roles On moving to the next menu item, you can save or discard the user role assignments. Click on the Save button.

14.1.3: Configuring data requests

Follow the tutorial given in the following URL: https://www.ibm.com/support/pages/node/570599

This introduces you to setting up data requests in IBM StoredIQ for Legal, and describes the steps which are required for creating a data request. Download the asset files for this at the end of the tutorial:

Figure 14.37: The example Sample.json file link is saved for download

Not all browsers allow the .json downloads (I used Firefox).

Right mouse click on the Sample.json files and save using Save link

14.1.4: SMTP server gateway

The Google SMTP email server is covered in the following configuration example.

14.1.4.1: SMTP server gateway for testing

The reference link is as follows: https://support.google.com/a/answer/178333?hl=en

14.1.4.2: Before you begin

Follow these steps: Turn on comprehensive mail storage.

Comprehensive mail storage applies only to core Google Workspace service. See the following link for reference: https://support.google.com/a/answer/3547347

Review sending limits for the SMTP relay service.

14.1.4.3: Routing outbound mail using the SMTP relay service

After entering and saving an IP address or range, you can enable or disable it by checking or unchecking the box to the left of the entry.

Follow these steps:

Sign in to the Google Admin console. Sign in using an administrator account (not a current account

From the Admin console home page, go to Apps > G-Suite > Gmail > Advanced

To see Advanced settings, scroll to the bottom of the Gmail page.

On the left, select the top-level organization. See tailor advanced settings for Gmail for more details:

https://support.google.com/a/answer/2786758 The SMTP relay service setting can be configured for the top-level organization only. Although the settings can be viewed from the sub-organization level when it’s added, at this level, it is not

possible to add, edit, or delete the setting from the suborganization level.

Scroll to the SMTP relay service setting in the Routing section, hover the mouse over the setting, and click on If the setting is already configured, hover the mouse over the setting and click on Edit or Add

For a new setting, enter a unique description. In the Allowed senders section, select the users who are allowed to send messages through the SMTP relay service: Only registered Apps users in my The sender must be a registered user in one of the domains. Only addresses in my The sender doesn’t have to be a recognized G Suite user, but must be in one of the registered domains. This can be useful for a third-party or for custom applications that need to send messages. Any addresses (not The sender address can be anything, even an address outside of the local domain:

Figure 14.38: The Google SMTP relay settings are selected and saved

The Any addresses option is vulnerable to abuse, either through malware on a user’s machine or by misconfiguration of the SMTP system. Therefore, Google doesn’t recommend this option.

For the Any address option to work properly, the email server must be configured to use SMTP AUTH or to present one of the domain names in the HELO or EHLO command. In the Authentication section, check one or both boxes to set an authentication method:

Only accept mail from the specified IP The system only accepts mail sent from these IP addresses as coming from your domains. Require SMTP Enforces the use of SMTP authentication to identify the sending domain. Using this option requires the clients to connect via TLS. If accepting messages from specified IP addresses is required, enter the IP addresses: Click on Add IP

Enter a description for the IP address or range. Enter the IP address or range.

Use the Classless Inter-Domain Routing format to enter an IP range; for example, Use the public IP address required. The maximum number of IP addresses that you can specify in the range is 65,536. Google recommends that the allowed IP range is kept as narrow as possible for security reasons. IPv6 address formats can also be specified for the IP address; for example:

1050:0000:0000:0000:0005:0600:300c:326b or 1050:0:0:0:5:600:300c:326b or

1050::5:600:300c:326b Check the Enabled box to enable (or uncheck to disable) this IP address or range, and then click on After an IP address or range is saved, it can be enabled or disabled in the future by checking the box to the left of the entry. In the Encryption section, check the Require TLS encryption box to require that the communication between the server and Google’s server is TLS encrypted.

If the email server doesn’t support TLS, don’t check this box. (If checked, the Google email server rejects messages that are not encrypted.) Click on Add setting or Any new settings are added to the Advanced settings page. At the bottom, click on It can take up to an hour for changes to propagate to the user accounts. Track any prior changes using the Admin console audit log.

14.1.4.4: Point the on-premise outbound server to Google

Configure your on-premise outbound email server to point to Click on the following server for instructions:

Figure 14.39: The SMTP options for the SMTP relay service

As an example, my GSUITE account is set, as shown in the preceding screenshot.

Configuration notes

Please see the following points:

If the box to require TLS encryption in step 1, mentioned earlier, is checked, configure the on-premise mail server to point to smtprelay.gmail.com on port

If TLS encryption is not required, the on-premise mail server can be configured to point to smtp-relay.gmail.com on port port or port

Without TLS encryption, SMTP authentication cannot be configured, and the IP address authentication has to be used.

Google recommend that the mail server is configured to present a unique identifier (such as the domain name or the name of the host mail server) in the HELO or EHLO command in the SMTP relay connections that the server makes to Google. Avoid using generic names such as localhost or which can result in issues with DoS limits.

The SMTP relay service doesn’t support multiple envelope recipients when specifying a null envelope sender FROM:

14.1.4.5: Additional configuration requirements

In addition to the server configuration steps listed earlier, the server must be further configured if either of the following is true:

The Any address option in the Allowed senders setting is selected, and email is sent from a domain you don’t own, such as

You send email without a From address, such as non-delivery reports or vacation out of office notifications.

In these cases, the local email server must be configured to either ensure that the server is using SMTP AUTH to authenticate as a registered G Suite user or present one of the local domain names in the HELO or EHLO command. See the instruction as follows:

https://docs.microsoft.com/en-us/previous-versions/office/exchangeserver-2010/bb629503(v=exchg.141)

Open port 587 on the server.

Enable or disable ports or services on the IBM StoredIQ data server

To manage ports, you can use the /usr/local/storediq/bin/util/port_handler.pyc script with

the appropriate

python /usr/local/storediq/bin/util/port_handler.pyc

The parameters are as

To list the current rules in iptables:

-s To list the supported services:

-l

To delete a port or a range of port numbers from iptables:

-d port_number|'port_range'

Figure 14.40: The Email Server configuration is updated for SMTP communications The SMTP logon and email settings are entered, as shown in the preceding screenshot. vi /etc/services Add the SMTP TLS port 587 for TCP and UDP and save the /etc/services file. Get the TLS certificate from Google SMTP Relay:

openssl s_client -starttls smtp -connect smtp-relay.gmail.com:25 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'l Give all roles to an LDAP administrator. Log in as an administrator as set up earlier in figure 14.34 (user

Tick all the role boxes, then log out and back in again.

14.1.5: Adding roles to users

See the Roles and Privileges screenshot, as follows:

Figure 14.41: The New Role command button is selected to add the Email roles

Add the following roles for the demo request:

Email Fulfillment Fulfills data requests for email servers.

Home Drive Fulfillment Fulfills data requests for home drives.

To add new roles to the system:

Go to Admin > Users and Roles > Role

Click on New Role and provide the following information for Email Fulfillment Technician role:

Figure 14.42: For the Email Fulfillment Technician role, the Work packages View and Manage privileges are selected Go to Admin > Attributes > Work Packages Click the wrench icon for the Fulfillment Team entry and add Email Fulfillment Technician and Home Drive Fulfillment as shown in the preceding screenshot. Make sure to save the change:

Figure 14.43: For the Home Drive Fulfillment Technician role, the Work packages View and Manage privileges are selected The saved roles from figure 14.41 and figure 14.42 are listed on the Roles and Privileges page as new available roles. The Work packages attributes are selected to add the Fulfillment Team values, as shown in the following screenshot:

Figure 14.44: The Fulfillment Team value is selected to add the new role items

Figure 14.45: The Email and Drive Fulfillment Technician roles are selected Click on New item after entering the first Email Fullfillment Technician text, and save the changes. Go to Admin > Attributes > Data Request Click on the wrench icon for the Data Source Category entry and add Email and Home Drive, as shown in the following screenshot:

Figure 14.46: The Data Source Category entry is edited using the wrench icon

The Data Request Attributes can now be edited from this page as follows.

Figure 14.47: The drop-down list is used to configure the Data Source Category

Click on New

Figure 14.48: The Email and New Drive options are selected

Click on

Still on the Data Attributes page, we can now add custom attributes, as described in section 14.1.5.1 below.

14.1.5.1: Add custom attributes

In the demo workflow, the Allow Unmapped flag in a workflow allows data requests to proceed even if a workflow custodian does not have a mapped data source.

Click on the New button:

Figure 14.49: Create a new Data Request Attribute for the Workflow, then click New

The attribute Allow Unmapped of Data Request Attributes is set as a Boolean or as shown in the following screenshot:

Figure 14.50: Select the attribute type from the drop-down Click on Save after setting the attribute type, and copy up the workflow definitions and JSON files to the VMware Workstation Pro Host Windows 10 server:

Figure 14.51: The StoredIQ Workflow definitions and JSON files

Deploy the definitions Download the workflow definitions attached to the examples’ web page and StoredIQ_for Go to Admin > Workflows > Workflow Definitions and click on Add Workflow

Figure 14.52: The Workflow Definitions page is selected to load the BPMN example files The Add Workflow Definition command button is clicked to open up the Browse… command button pop-up window, as shown in the following screenshot:

Figure 14.53: The Add Workflow Definition Browse button is clicked to add the XML example BPMN workflow definition files

Figure 14.54: The StoredIQ_for_Legal_Data_Request_Process.bpmn file is selected

The StoredIQ_for_Legal_Data_Request_Process.bpmn file is added to the IBM StoredIQ system using the Add Workflow Definition then Browse… and the Add command buttons:

Figure 14.55: The sample data request workflow is loaded and displayed Activate the workflow in the details view using the Activate command button, as shown in the following screenshot:

Figure 14.56: The Activate workflow command button is clicked

Figure 14.57: The radio button option to activate immediately (Now) is selected Repeat for the second BPMN file: StoredIQ_for_Legal_Fulfillment_Process.bpmn

Figure 14.58: The second Sample Fulfillment Workflow is loaded from the BPMN file

Activate the second workflow:

Figure 14.59: The two imported workflows can now be seen to have Active status

The two new, imported, and activated workflows, now have the status as highlighted in the preceding screenshot:

Figure 14.60: The Workflow Tasks page shows the task step details

The screen shown in Figure 14.60 above, shows the StoredIQ workflow Task in progress.

14.2: StoredIQ for Legal (VM): root certificate import

Copy the IBM StoredIQ root certificate to the StoredIQ for Legal system:

Sign in to the IBM StoredIQ application stack as

Copy the /etc/siq/ssl/root.crt file to the root directory on the StoredIQ for Legal system. Use a secure copy tool such as scp for this.

Sign in to the StoredIQ for Legal virtual machine as the root user, and follow the procedure in the following link:

https://www.ibm.com/support/knowledgecenter/en/SSZL2P_2.0.3/com .ibm.biq.deploy.doc/d_connection_siq_certificate.html

14.3: Approval process BPMN refined approval workflow

The reference link is as follows: https://www.ibm.com/support/pages/node/711335

(Scroll down to the bottom of this web page to download the two example BPMN workflow files: StoredIQ_for_Legal_Review_Process.bpmn StoredIQ_for_Legal_Approval_Process.bpmn)

14.4: Backup of StoredIQ for Legal databases

To manage backup and restore of the StoredIQ for Legal databases, refer to the following:

To back up the StoredIQ for Legal database information, use the /siq/bin/backup create command.

When you run the command without any options, a backup file is created in the /root/backup folder and is named in the format for example However, you can specify a file name of your choice, and use the -folder option to specify the location of the backup file.

To list your available backups, use the /siq/bin/backup list command.

If your backup files are not stored in the default backup folder use the -folder option to specify the respective folder.

To restore your StoredIQ for Legal database information:

Run the /siq/bin/backup restore command. For full details of the backup and restore procedure, see the following link:

https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_backup.htm

Conclusion

In this chapter, we covered the download and installation of the VM for IBM StoredIQ for Legal 2.0.3.7. The integration of the role security using users searched from a separate LDAP directory server was demonstrated. The configuration for SMTP email communications to a gmail server was also covered, and twosample workflow definitions were loaded and activated, and then the display of a workflow task step was shown.

Points to Remember

During the installation of the IBM StoredIQ VM, the ilgadmin administrator user password is entered; you will need to remember this for future reference. Note that this password can be changed later by running the /siq/bin/change_ilgadmin_password.sh shell script logged in as but you still need to enter the original password you configured.

You may have to extract the .ovf file from the downloaded IBM StoredIQ OVA file, using 7-zip or WinZip extraction, to load it into the VMware Workstation Pro program.

The SMTP Relay service setting can be configured for the top-level organization only. Although the settings can be viewed from the sub-organization level when it’s added, at this level, it is not possible to add, edit, or delete the setting from the suborganization level.

Not all browsers allow the .json file downloads for the example Workflows (I used Firefox).

Multiple Choice Questions

Which file do you have to edit to enable the IBM StoredIQ VM to be accessed from the VMware host Windows system by a browser?

change_ilgadmin_password.sh

/etc/services hosts

StoredIQ_for_Legal_Fulfillment_Process.bpmn

Which script would you use to process the backup of the StoredIQ for Legal databases?

/siq/bin/backup restore

/siq/bin/backup list

/siq/bin/backup create /root/backup

Which script would you use to change the main ilgadmin administrator password?

/usr/local/sbin/create_ilgadmin

/siq/bin/change_reportadmin_password

/siq/bin/change_ilgadmin_password

/siq/bin/netcfg

How many roles are assigned to a user? Only one role must be assigned

One or more roles must be assigned More than one role must be assigned

One or more roles can be assigned

Multiple Choice Answers

c. hosts c. /siq/bin/backup create

c. /siq/bin/change_ilgadmin_password

d. One or more roles can be assigned

Questions

For what reason would you navigate to and edit C:\Windows\System32\drivers\etc\hosts file?

Describe, in outline, the procedure steps for setting up data requests in IBM StoredIQ for Legal.

What procedure would you use to add the parameters for an LDAP Directory server to use this for user validation?

What command would you use to restore the databases for the IBM StoredIQ for Legal server, and how would you know when the backup was made?

Key terms

Uniform Resource Locator. Open Virtual Appliance file type, the .tar version of an OVF file, and its component files.

Open Virtualisation a standard format with complete specification of the virtual machine, including the full list of required virtual disks used by the virtual hardware configuration.

Virtual machine.

Business Process Model and Notation is a standard file format for business process workflow diagrams and step configuration.

Lightweight Directory Access Protocol is an open standard for accessing users for authenticating sign on.

Simple Mail Transfer Protocol is a standard for sending and receiving emails. A container file representing a VMware virtual hard disk.

APPENDIX References and End of Life Support

Introduction

This Appendix lists the publication references for the supporting software and platform operating systems for the set-up and use of the IBM products covered in the book, including the products End-of-Life support.

Structure

In this Appendix, we will provide the following sections: IBM publication references

Module overviews

Supporting libraries and packages Application Builder and foundation components

IBM Watson oneWEX links

StoredIQ configuration

Red Hat publication references

ASB Software Development Ltd publication references

End-of-Life support Red Hat Linux 8.0 End-of-Life support

IBM Cloud End-of-Life support

Red Hat OpenShift End-of-Life support

IBM StoredIQ for Legal End-of-Life support

IBM Case Analyser 5.5 End-of-Life support

Objectives

After studying this unit, you should be able to: Identify and locate the relevant publication references for the installation of the IBM products.

Be aware of the EOL support required to ensure the maintenance and security of the installed system.

IBM publication references

Provides details of the Watson Explorer foundational components, which are to be installed: Application Watson Explorer Annotation Administration Console IBM Knowledge Results

Module overviews

See the following link for reference: https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.swg.im.infosphere.dataexpl.install.doc/c_module_oview.html

The terms of use of the IBM knowledge base content is as follows: https://www.ibm.com/legal?lnk=flg-tous-usen

Supporting libraries and packages

Describes the commands required to install Extra Packages for Enterprise Linux

https://fedoraproject.org/wiki/EPEL

The terms of use of the content are covered in the following URL: https://fedoraproject.org/wiki/Legal

The main content is available under Attribution-Share Alike 3.0 Unported

https://creativecommons.org/licenses/by-sa/3.0/

Current CentOS Linux and stream releases of a number of rpm packages:

http://mirror.centos.org/centos/7/os/x86_64/Packages/

The terms of use of the content are covered in the following URL: https://www.centos.org/legal/

Application Builder and foundational components

Please refer to the links as follows: Application Builder user name and default password:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.swg.im.infosphere.dataexpl.appbuilder.doc/t_ab-config-userentity.html Linux commands to correctly start each of the component modules, which make up the IBM Watson Foundational Component 12.0.x system:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_services.html#c_wex_native _services.dita

Configuring ZooKeeper:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.fc.install.doc/c_wex_native_config_zk.html Configuration of the Application Builder Liberty web server by editing of the server.xml file:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.appbuilder.doc/c_de-ab-systemwlp.html

IBM Watson oneWEX links

Please refer to the following links: Describes the advantages and limitations of using IBM Watson oneWEX as a data source in Application Builder:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.appbuilder.doc/c_onewex_ab_ds.html The procedure required to upload an exported annotator; for example,

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.wks.integration.doc/anno-machine-export-upload.html

Procedure to install the Statistical Information and Relation Extraction RPM file and the required libraries:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.wks.integration.doc/anno-machine-sire.html This URL contains the links to the post-installation configuration steps to configure Watson Explorer Engine for generating a new encryption key, running the micro-test utility, and configuring the embedded Liberty web server:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_config_engine.html

Procedure to generate a new key using the AES-128-GCM encryption algorithm, (which uses 128-bit keys, and OpenSSL):

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_config_engine_enc.html

Procedure to start and configure an embedded web server that can be used to isolate Watson Explorer Engine. This embedded web server cannot be used in a production environment: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.install.doc/c_velocity-web-serverconfiguration.html

Links to describe access to the following Watson Explorer Engine modules from a web browser: Watson Explorer Engine, Application Builder, the Results Module: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.fc.install.doc/c_wex_native_accessing.html

Links to show how to associate a new display with a project and customizing a standard display and advanced display editing:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.engine.tut.display.doc/c_graphicaldisplays.html

Provides details of creating a new display based on an existing one:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.engine.tut.display.doc/t_display-tutcreate-display.html

Provides links to the following customization procedures: Changing logos, changing colors, changing fonts, modifying headers and footers, changing navigation, customizing clusters, disabling navigation, customizing results:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.engine.tut.display.doc/c_display-tutcustomizing.html Procedure for start-up/shutdown integration on Linux systems: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.install.doc/c_de-init.html Introduces the container-based architecture of the software and supplies the main links to the IBM Watson Explorer oneWEX

container documentation: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/explorer_onewex.html Main links to the IBM Watson Explorer and IBM Watson Explorer oneWEX container documentation: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.swg.im.infosphere.dataexpl.welcome.doc/doc/watsonexplorer_12.0. 0.html

Procedure for the installation of IBM Watson® Explorer oneWEX as a container on the Docker system on both Windows and Linux platforms: https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_install_docker.html

Procedure to give access to a local file system, so that the IBM Watson file system crawler can crawl local files, and for other crawlers to have access to required Java libraries: https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/t_onewex_fs_access_docker.html Procedure to create new facets from a collection, so that the new facets can be used for analysis:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.watson.wex.ee.doc/c_onewex_miner_dac.html Describes the use of the Watson™ Explorer Content Miner to create and analyse a collection:

https://www.ibm.com/support/knowledgecenter/SS8NLW_12.0.0/com.i bm.watson.wex.ee.doc/c_ee_miner_home.html Describes the procedure to be used to analyze a single document in order to test the annotators in a UIMA pipeline:

https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/co m.ibm.discovery.es.ta.doc/iiysspipelinetestdoc.html Provides details of the procedure to use to load CSV files for analysis:

https://support.video.ibm.com/hc/en-us/articles/207851757-How-toload-CSV-files-into-Excel Link to the example ufone_tweets.csv sample dataset file, which can be downloaded for use as a tutorial example: https://developer.ibm.com/tutorials/build-a-predictive-model-usingtweets/

Lists the scripts required for changing the system administrator password (required for the first-time use); changing the report administrator password, and where to find the log files. It also describes how to reset the security domain: https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_va_configure.html

StoredIQ configuration

Please refer to the following links: Gives a step-by-step procedure for configuring the IBM StoredIQ VM data server system settings:

https://www.ibm.com/support/knowledgecenter/SSSHEC_7.6.0/deploy /tsk/tsk_install_dataservers.html Provided for further reading in Chapter 14 of this book:

https://www.ibm.com/support/pages/sites/default/files/inlinefiles/$FILE/IBMSIQDeploymentConfigGuide76020_0.pdf

A step-by-step example for creating a StoredIQ workflow:

https://www.ibm.com/support/pages/node/711333

Outline procedure to configure IBM StoredIQ for integration with an LDAP server: https://www.ibm.com/support/knowledgecenter/SSZL2P_2.0.3/com.ib m.biq.deploy.doc/d_connection_directory.html

Outline procedure to configure IBM StoredIQ for integration with an SMTP server connection:

https://support.google.com/a/answer/178333?hl=en

The reference is provided for further reading in Chapter 14 of this book:

https://www.ibm.com/support/pages/sites/default/files/inlinefiles/$FILE/IBMSIQDeploymentConfigGuide76017_1.pdf

Further reading in Chapter 14 of this book, describes further workflow development and has downloadable BPMN workflow examples:

https://www.ibm.com/support/pages/node/711335 Workflows in IBM StoredIQ for Legal: part 3 - introducing process variables to the part 3 tutorial guidance with access for download of two further BPMN workflows: https://www.ibm.com/support/pages/node/711337

Red Hat publication references

Please refer to the following links: IBM Red Book series Building Cognitive Applications with IBM Watson Services is in the following link:

http://www.redbooks.ibm.com/redbooks/pdfs/sg248387.pdf This is split into the following seven volumes:

Volume 1 Getting Started, SG24-8387 (June,2017)

Volume 2 Conversation, SG24-8394 (May, 2017)

Volume 3 Visual Recognition, SG24-8393 (May, 2017)

Volume 4 Natural Language Classifier, SG24-8391 (May, 2017)

Volume 5 Language Translator, SG24-8392 (May, 2017) Volume 6 Speech to Text and Text to Speech, SG24-8388 (May, 2017)

Volume 7 Natural Language Understanding, SG24-8398

These volumes are all accessible using the URL, starting with the following link:

http://www.redbooks.ibm.com/redbooks/pdfs/sg

It is followed by the numbers, as specified for each volume, (removing the hyphen) and adding the .pdf extension:

https://www.redbooks.ibm.com/technotes/tips1208.pdf

IBM Watson Explorer 9.0.0.3 and integration with Infosphere Master Data Management V11.3:

https://www.redbooks.ibm.com/redbooks/pdfs/sg248133.pdf

Building 360-degree information applications. IBM StoredIQ data sources and volumes: http://www.redbooks.ibm.com/redpapers/pdfs/redp5316.pdf Check the following website for the latest list of data sources:

http://www.ibm.com/support/knowledgecenter/SSSHEC_7.6.0/admin/r ef/ref_supportedserverplatformsandprotocols.dita

IBM StoredIQ introduction and planning considerations:

http://www.redbooks.ibm.com/redpapers/pdfs/redp5315.pdf

http://www.redbooks.ibm.com/abstracts/redp5507.html IBM Spectrum Scale Security, REDP-5426:

http://www.redbooks.ibm.com/abstracts/redp5426.html IBM Spectrum Scale Functionality to support GDPR requirements, REDP-5489:

http://www.redbooks.ibm.com/abstracts/redp5489.html IBM StoredIQ introduction and planning considerations, REDP-5315:

http://www.redbooks.ibm.com/abstracts/redp5315.html IBM Cloud private system administrator’s guide:

http://www.redbooks.ibm.com/redbooks/pdfs/sg248440.pdf IBM Cloud private application developer’s guide, SG24-8441: http://www.redbooks.ibm.com/redbooks/pdfs/sg248441.pdf

Red Hat OpenShift and IBM Cloud Paks on IBM Power Systems Volume 1:

http://www.redbooks.ibm.com/redbooks/pdfs/sg248459.pdf https://www.ibm.com/support/pages/product-documentation-ibm-casefoundation-case-analyzer The preceding link is not a Redbook URL, but does have two more recent access links for documentation: http://www.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ib m.p8.pe.taskmgrui.doc/pa.htm http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss? CTY=US&FNC=SRX&PBL=GC19-3915-02

ASB Software Development Ltd publication references

This Appendix covers the references to Uniform Resource Locators for the installation preprint publications that I have on Research Gate in the following link:

https://www.researchgate.net/profile/Alan_Bluck

The preceding link is for the products covered in this book. IBM Watson Explorer Foundational Components 12.0.3 Installation and Configuration on CentOS Linux

https://doi.org/10.13140/RG.2.2.11327.66721

Watson Explorer 12.0.3 oneWEX Installation on IBM Cloud CENTOS 8.0 Linux with Docker

https://doi.org/10.13140/RG.2.2.12248.44803

IBM StoredIQ for Legal VM 2.0.3.7 Server Installation Steps for VMware Workstation Pro https://doi.org/10.13140/RG.2.2.12586.24008

End-of-Life support

This section covers the End-of-Life support for Red Hat Linux 8.0, IBM Cloud products, Red Hat OpenShift v4 and IBM StoredIQ for Legal.

After the End-of-Life support date is reached, it is usually possible to obtain an extended support contract (but usually not as a “free” option.)

Red Hat Linux 8.0 End-of-Life support

The life-cycle support is covered by Red Hat at the following URL: https://access.redhat.com/support/policy/updates/errata/

In summary, RHEL versions 5, 6, and 7, each have ten years of support from their General Availability date, refer to the following URL. https://access.redhat.com/support/policy/updates/errata/#Maintenanc e_Support_2_Phase

In general, this is split into 5 years of full support and 5 years of support.

There are two types of purchased support for RHEL, as the following description attempts to clarify.

Extended Update Support for RHEL allows you to receive bugfix and security updates to a minor release of RHEL. For example, the x is the minor version in RHEL 8.x for an extended time. There is now a beta of RHEL 8.3 available for developers and 2 GA minor releases for RHEL 8.0 since May 2019; that is, a minor release around every 6 months. Extended Lifetime Support (ELS)

can be purchased from Red Hat for an RHEL version, if the IBM certified software only runs on this version.

(Refer to Chapter 4 on the IBM Software Compatibility Matrix for examples of these version limits.)

Red Hat GA release dates can be viewed using the following URL:

https://access.redhat.com/articles/3078

EUS is intended to be used for Red Hat customers who have a longer software lifecycle, and require bug/security updates, but don’t need to update to each minor release. (These updates come out every 6 months – for example, since RHEL 8.0 was GA in May 2019, we now [August 2020] have a Beta release of 8.3.) EUS is not needed, but it means that you will always update to the current minor release of RHEL and the latest patch level of the rpm you update.

For example, if you do not buy EUS today, you will not be able to connect to RHEL 6.6 EUS channel’s the yum package installer command:

yum -y update This command will cause a full update to RHEL 6.9 with patches up to the last available patch.

End of support for Red Hat is a little confusing! For example, Red Hat stopped making updates to RHEL 6.6 on October 31 2016, but continued updating packages for minor releases.

In fact, support for configuration and usage questions are still provided on all RHEL 6 until at least November 30th, 2020 (and you can still download RHEL Version 5 as a Red Hat Developer). One of the many advantages of Linux is its flexibility; for example, if an RHEL 6.6 issue is found, it is possible to update to a package from a later minor release in the main RHEL 6 channel, or Red Hat can deliver the fix from a later major release, such as RHEL 7. The main RHEL 6 channel stops getting updates on November 2020, but all is not lost! You can purchase the RHEL 6 Extended Lifecycle Support to get any critical bug fixes delivered during the ELS phase.

You need to add the ELS channel to the installed operating systems. This purchase of ELS would not be required after 2020, since by then you won’t get any more package updates, so there’s no need to change channel. ELS is only needed if the applications running on the server are not certified for a higher major release.

So clearly, if you can migrate dependent applications before November 2020 to RHEL 7.x or RHEL 8.x, there is no need to buy ELS.

IBM Cloud End-of-Life support

See the reference link as follows: https://www.ibm.com/cloud/cloud-prod-life

There is usually a 90-day warning for End of Support or End of Marketing The preceding URL provides the actual dates for various cloud services.

Red Hat OpenShift End-of-Life support

See the reference link as follows: https://access.redhat.com/support/policy/updates/openshift/

You will need to log in with a Red Hat account to view the preceding URL pages. Red Hat OpenShift Container platform v4: The time period of support is determined by the future release schedule. Red Hat aims to forecast these at three-month intervals. With the introduction of Red Hat OpenShift Container Platform v4, the major version of a release (for example, 4.x) is available for a minimum of three years from the initial GA; this three-year period is split into two phases; GA phase 1 and GA phase Full details can be obtained from the preceding URL.

IBM StoredIQ for Legal End-of-Life support

The following URL gives IBM’s general guidance on EOL support: https://www.ibm.com/software/passportadvantage/endofsupport_ov.ht ml

A CSV product list can be downloaded from the following URL: https://www.ibm.com/support/pages/software-lifecycle-product-list

This list can be searched in Excel and it provides the following URL for support:

https://www.ibm.com/support/pages/node/563277

Figure 15.1: The highlighted shows the on-going ILG support provided by IBM

IBM case analyser 5.5 End-of-Life support

End-of-life support details are covered in the following BPB book: Installation and Configuration of IBM FileNet Information Management

Index

A Annotation Administration Console (AAC) about installing Watson Explorer Engine administration tool installation 515 Apache ANT 232 APAR 250 API key 315 AppBuilder service installing 506 starting, in order 507 stopping 507 Application Builder about 497 configuration 503 default login credentials 503 installing 502 approval process BPMN refined approval workflow 606 ASB Software Development Ltd publication references 619 atomic OSTree repository 94

B bare metal installation. See Red Hat OpenShift 4.5 Bare Metal installation bind installation, for DNS about 430

bind, configuring 337 bind service, enabling at startup 337

firewall ports 433 single DNS server, configuring VMware tools, reinstalling 433 boot node requirements about 390 libraries and X-Window installs, update 391 RHEL 8 system, registering through Subcription Manager 391 boot options changing 416 C

Case Analyzer 29 CC1W3EN, product code 216 CC-BY-SA reference link 11 CC-BY-SA license 94 CentOS about 3 release notes 77 CentOS7 233 CentOS 8.0 about 127 Compatibility Matrix reports 127 Compatibility Matrix URLs, obtaining Red Hat Linux upgrades 129 CentOS 8.2 Linux distribution 77 CENTOS Linux 8.2

installing, on VMware Classless Inter-Domain Routing (CIDR) format 592 CLI 315

Cloud Pak installing for demonstration 289 Cloud PAK For Data 11 Cluster Application Migration (CAM) tool 14 cluster customization 445 cluster_domain parameter 446 CodeReady Container installation, for OpenShift 4.5.x Community Edition (CE) 233 compatibility matrix URLs about 145 using 215 compatibility reports procuring 216 targeting 217 Connectors 41 container inactive image retention policy 99 CSV data example 562 Custom Annotator transferring, to ICA Server custom resource definitions (CRD) 288 D Dandified Yellowdog Updater, Modified 233 Dandified yum 233 demo deployment type 288

Digital Business Automation (DBA) 287 display tutorial creating DNS service package

firewall, configuring 430 installing 430 Docker about 232 account, creating 99 setting up, for cluster nodes 446 Docker 18.09.2 installation, on RHEL 8.0 391 Docker 18.09.2 installation, on CENTOS 8.0 435 Docker Community Edition (CE) 45 Docker Desktop 2.3.0.4 installation, on Windows 10 Home Edition about 100 compose file, editing 121 container logs 120 docker-tutorial container display 119 docker-tutorial image, launching for tutorial 118 example Docker Container, creating 120 Linux kernel update package, installing tutorial, running WSL 2 installation 109 Docker Installation about 99 Docker docker Docker docker

18.09.2, installing on RHEL 8.0 99 attach command 127 Desktop 2.3.0.4, installing on Windows 10 Home Edition exec command 124

docker kill command 127 docker pause command 126

docker ps command docker pull command 122 docker restart command 127 docker docker docker docker

run command 126 start command 127 stop command 127 unpause command 126

docker wait command 127 Docker installation Community Edition (CE) 100 Docker installed IBM containers 567 Domain Name Server (DNS) 231 Download Director option about 19 troubleshooting downloads IBM Watson Explorer Analytical 537 IBM Watson Explorer Deep Analytics Edition Analytical Components 535 IBM Watson Explorer Deep Analytics Edition oneWEX Product details 535 IBM Watson Explorer Deep Analytics oneWEX Edition, extraction 537 Watson Analytics oneWEX installation downloads 536 Dynamic Host Configuration Protocol (DHCP) 231

E End-of-Life (EOL) support about 620 IBM case analyser 5.5 End-of-Life support 623 IBM StoredIQ for Legal End-of-Life support 622

Red Hat Linux 8.0 End-of-Life support 620 Red Hat OpenShift End-of-Life support 622 reference links 44 Enhanced Keyboard Driver option 408 ens192 MAC address 431 Extra Packages for Enterprise Linux (EPEL) 336 F Faceted search reference link 487 File Crawler component 141 firewall configuration, DNS service about 430 bind service, enabling at startup 432 DNS server, setting up with static IP address 431 main configuration files, backing up 430 Network Manager DNS auto-configuration, disabling 432 resolver configuration changes 432 firewall configuration, OpenShift 4.5 cluster installation about 340 network settings, editing 342 subscription, editing 342 Fix Central 38 Fix Central Download option 199 Fix Pack downloading 203 Fix Pack 12.0.3.4 download link 197 Fix Pack 1907, for IBM Cloud Private

about 452

Fix Pack icp-3.2.0.1907 Fix Pack sections Fix Packs for IBM Software products FTP installing 81 installing, on Linux system 82 using, for IBM Watson Explorer Foundational Components 12.x 81 Fully Qualified Domain Name (FQDN) 437

G

Graphics Processor Unit (GPU) 10 Gremlin container 8 H

HAProxy installation 344 layer 4 load balancing 344 sticky sessions 345 testing 353 high availability (HA) 128 hostnamectl command 437 I

IBM case analyser 5.5 End-of-Life support 623 IBM Case Analyzer 5.5

download location 29 fix pack location 30 license requirements UVU PVU 30 version 29 IBM Cloud

about 7 account, creating 7 download location 7 fix pack location 9 license requirements UVU PVU 8 Lite version 10 Standard v1 10 version 8 IBM Cloud catalog 8 IBM Cloud End-of-Life support reference link 622 IBM Cloud Pak for Automation 20.0.1 for demonstration purposes 287 IBM Cloud Pak, for Automation 20.0.1 on Certified Kubernetes 287 IBM Cloud Pak, for Data about 272 download URL 270 IBM StoredIQ for legal 2.0.3.7 284 installation procedure server requirements 284 IBM Cloud Pak, for Multicloud Management download 284 installing IBM Cloud Pak for Security about 299 cluster configuration 309

DNS lookup timeout resolution, applying to common services 312

IBM Cloud Platform Common Services, deploying 312 IBM Cloud Platform Common Services, installing 306 installation, verifying 312 installing logging in 307 optional password regular expressions sub-systems 299 IBM Cloud PAK systems about 261 installation preparation 262 IBM Cloud Private about 423 references 389 IBM Cloud Private 3.2.0 cluster, installing 394 IBM Cloud Private-CE installation 442 IBM Cloud Private Community Edition (CE) 423 IBM Cloud Private installation about 423 CENTOS Linux 8.0, installing 424 Linux DNS Server, installing on VMware 15.1 424 IBM Download Director App installing IBM FileNet P8 compatibility matrix 37 IBM Fix Pack location 38 IBM Information Management System (IMS) products 1 IBM Knowledge Center 497 IBM Private Cloud Docker installation 395

installation environment, setting up 394 installing 394 IBM Private Cloud installation about 435 docker pull, using on MasterBoot node firewall ports 438 Fix Pack 3.2.1908 455 Fix Pack 1907 452 Fix Pack installation, re-running 456 FTP server, using installation procedure Master and Boot Node requirements 436 problem, resolving 449 reference link 392 repeated installation 448 repeated sections, for proxy node 438 system requirements 435 verifying 458 worker and proxy base systems, creating 438 IBM publication references about 612 application builder and foundational components 613 IBM Watson oneWEX links module overviews 612 StoredIQ configuration 617 supporting libraries and packages 613 IBM StoredIQ for Legal 2.0.3.7 about 249 compatibility matrix URLs 62 component interactions with system architecture diagrams and performance issues 64

CPU core requirements 143 cumulative fixes, identifying DNS configuration 143 download location 31 End of Support 65 Fix Pack components, downloading for Linux and Windows 251 Fix Pack lists 252 Fix Pack product searching procedures 250 folder structures 144 GUI library installation requirements 144 IBM Download Director installation, for Fix Packs 257 license requirements UVU PVU 31 license restrictions 258 memory and disk storage requirements 143 network card set-up 143 prerequisites, for installations 142 Red Hat Subscription Manager configurations 143 software compatibility report 63 supported versions for upgrade 65 supporting system requirements 64 upgrade paths 64 user roles, setting up 145 version 31 IBM StoredIQ for Legal End-of-Life support 622 IBM StoredIQ for Legal V 2.0.3.7 server installation, for VMware Workstation Pro 15.5.6 data requests, configuring 589

installation steps LDAP server, adding roles, assigning to users 588 SMTP server gateway 589

test BPMN workflow, creating 583 IBM StoredIQ for Legal VM 2.0.3.7 Server Installation 88 FTP/SFTP, using 90 IBM Download Director installation 89 IBM eAssembly components, downloading for Linux 88 license restrictions, using 90 product code lists, identifying 89 product searching procedures 89 Red Hat Linux download 90 VMware mapped folders 90 IBM StoredIQ root certificate copying, to StoredIQ for Legal system 605 IBM Watson about 15 CJ5DNML 15 download location 15 IBM Watson Explorer Foundational Components V12 15 IBM Watson Explorer oneWEX 12.x Docker Container 15 IBM Watson Annotation Administrator Console (AAC) component 241 IBM Watson Content Analytics Studio installation about missing JVM problem, resolving reference link 462 IBM Watson Explorer 12.0.3.0 embedded IBM Liberty web server, configuring IBM Watson Explorer Analytical Component 28 IBM Watson Explorer Deep Analytics Edition Analytical Components Product details 27 downloading fix pack location 29

Foundational Components Product details 25 foundation, copying 27 installing license requirements UVU PVU 29 oneWEX installation downloads, copying 27 oneWEX Product details 25 versions 29 Watson Analytics, copying 27 IBM Watson Explorer Deep Analytics Edition 12.0.3 installation 64-bit version of missing library shared object, installing 541 about supporting Linux shared object libraries libXScrnSaver, installing 541 IBM Watson Explorer Deep Analytics oneWEX Edition extraction 28 IBM Watson Explorer Foundational Components extraction 28 IBM Watson Explorer Foundational Components 12.x about 241 compatibility reports 148 component interactions with system architecture diagrams and performance issues 56 CPU core requirements 149 cumulative fixes, identifying default login credentials 195 DNS and library installation requirements 141 Fix Pack components, downloading for Linux and Windows 242 Fix Pack lists 243 Fix Pack Product searching procedures 241 folder structures 149 FTP/SFTP, using 81 IBM Download Director installation 76

IBM e-Assembly components, downloading for Linux 73 initial Application Builder, configuring 169 installed components 71 Java jdbc jar files, supporting 150 license restrictions 249 memory and disk storage requirements 149 .msi software installation components, installing 164 PATH environment set-up 150 prerequisites, for installation 149 product code lists download, identifying product searching procedures 73 Red Hat OpenShift server cluster requirements 142 Red Hat RHEL 8.0 Linux download 76 Red Hat RHEL 8.0 Linux installation 76 Red Hat Subscription Manager configurations services for upgrade, stopping 150 software compatibility report 54 subscription manager 76 supported browser 148 supported versions for upgrade supporting system requirements system requirements 141 upgrade paths 56 user security 149 version end-of-life and roadmaps 61 VMware mapped folders, using 82 Windows Defender configuration 150 Windows hosts file configuration, for server network access 150 Windows services, enabling IBM Watson Explorer GUI front end admin user interface, launching

collection for file directory dataset, adding 546 CSV file example Enron emails data, downloading launching 542 IBM Watson Explorer oneWEX 12.x installing, on Windows Docker Container IBM Watson Explorer oneWEX 12.x Docker Container about 237 bind, configuring 133 bind, installing 133 CentOS download 86 compatibility report 196 component interactions with system architecture diagrams and performance issues 52 CPU core requirements 206 cumulative fixes, identifying Docker set up requisites firewall, configuring for DNS 133 Fix Pack components, downloading for Linux and Windows 238 Fix Pack lists 238 Fix Pack product searching procedures 237 folder structures 206 FTP/SFTP, using 86 GUI library installation requirements 134 IBM Cloud Private Cluster set up 139 IBM Download Director installation 240 IBM eAssembly components, downloading for Linux 85 Java jdbc jar files, supporting 207 license restrictions 240 memory and disk storage requirements 206 network and DNS configuration 132

PATH environment set-up 207 prerequisite, for IBM Security Directory Services 135 prerequisites 130 prerequisites, for installations 205 product code lists, identifying 85 product searching procedures 85 Red Hat download 85 Red Hat Linux maintenance, Subscription Manager used 240 Red Hat Subscription Manager configurations 130 shared folder access, enabling 136 software compatibility matrix report, generating supported versions for upgrade 53 supporting system requirements 52 upgrade paths 52 user security 206

version end-of-life and roadmaps 53 VMware mapped folders, using 86 VMware network card set-up, for static IP address 133 VMware workstation upload 86 Windows Defender configuration 207 Windows hosts file configuration, for server network access 207 Windows services, stopping for installing upgrades 207 X-Windows Terminal installation 134 IBM Watson Explorer oneWEX for ICP product code 216 IBM Watson Foundation Components 12.0.3.0 installing, on Windows 10 Home Edition IBM Web Content Manager/Portal V8.5 connector installation 237 Ignition tool 361 inactive image 99 Information Lifecycle Governance (ILG) 44

installable modules, Watson foundation components Annotation Administration Console 497 Application Builder 497 IBM Knowledge Center 497 Results Module 497 Watson Explorer Engine 497 ZooKeeper 497 installation downloads about 343 /etc/hosts file of HAProxy, updating load balancer HAProxy installation 344 NGINX installation 350 NGINX web server installation 344 installation preparation, IBM Cloud Pak about 262 estimated download duration 267 IBM Watson Explorer oneWEX 12.x Docker Container 266 supported versions 262 installation program, bare metal installation CLI, installing 358 CLI, installing on Linux 359 /etc/hosts file, updating ignition configuration files, generating 361 obtaining 356 installed components, IBM Watson Explorer Foundational Components 12.x Annotation Administration Console 71 Application Builder 71 BigIndex Java API 72 Results Module 72 Watson Explorer Engine 71

ZooKeeper 72 IOS 260 iPXE 232 ISO image 232 J Java SDK 232 JRE 260 K kubectl command 448

L

Lights Out Management interface (LOM) 232 Linux DNS server installation, on VMware 15.1 prerequisites 389 Red Hat Linux 8.0, installing on VMware 389 RHEL 8, downloading 389 RHEL 8, installing 389 M mapped folders adding, from host system 415 Master and Boot node requirements

CENTOS 8 system, registering through Subscription Manager 429 docker pull, using 393 host name, changing to ecmukdemo20 430 Master node requirements about 440 base cluster server, updating 440 MITM CA certificate 232 mitmproxy CA cert 232 MITM Proxy Network 232 msi files 232

N network cards adding 415 NGINX HAProxy, testing 352 installing 350 nginx service starting 351 O

oneWEX reference link 44 OpenShift 4.5 cluster installation about 319 bind, configuring for DNS 337 bind, installing 337 bind service, enabling at startup 336

firewall, configuring 340 overview 319 prerequisites resolver configuration changes 335 static IP address, setting up OpenShift 4.x deploying, on non-tested platforms 94 OpenShift Cluster Manager (OCM) 221 OpenShift Container Platform 317 Open Virtual Appliance (OVA) 64 OVA 315 P

Preboot Execution Environment (PXE) 232 proxy node server base install, repeating 437 pull secret text file 14 PVU 260 Q

Quay.io URL 222 R Red Hat Enterprise Linux CoreOS (RHCOS) 317 Red Hat Enterprise Linux (RHEL) versions 3

Red Hat Linux 8.0 End-of-Life support 621 Red Hat Linux RHEL 8.0 about 3 download link 3 fix pack location 5 installation, downgrading 6 license requirements UVU PVU 4 versions 5 Red Hat Linux upgrades about 43 using 218 Red Hat OpenShift reference link 95 Red Hat OpenShift 4.5 bug fix updates 15 download location 11 fix pack location 14 installation, downloading license notice 12 license requirements UVU PVU 11 version 14 Red Hat OpenShift 4.5 Bare Metal installation about 354 installation program, obtaining SSH private key, generating 355 RedHat OpenShift 4.x installation about 219 downloading 220 firewall, configuring 219 internet and telemetry access requirement 222 network connectivity requirements 222

overview 221 prerequisites 220 server requirements 223 Red Hat OpenShift Cloud Platform (OCP) 3.11 287 Red Hat OpenShift End-of-Life support reference link 622 Red Hat publication references Red Hat Subscription Manager configurations, IBM Watson Explorer oneWEX Docker Container about 130 available repositories, checking 131 host name, changing to ecmukdemo10 131 remote repository, enabling for RHEL 8 system 131 subscribe, enabling to RHEL system 131 Results Module service installation about 505 AppBuilder service, installing 506 oneWEX datasource, adding 508 ports, opening on firewall service 508 SIRE RPM file, installing for Watson Explorer 511 status, checking 506 Watson Explorer Engine, installing 509 RHEL 6 Extended Lifecycle Support (ELS) 621 RHEL 8.0 CentOS 8.0 127 RHEL version 8.2 Linux DVD .iso file 3 rpm-ostree 317

S

security context constraint (SCC) 288 sha256sum 77 SLES 12 315 SMTP server gateway about 589 additional configuration requirements configuration notes 593 custom attributes, adding for testing 589 on-premise outbound server, pointing to Google 592 roles, adding to users using, for routing outbound mail workflow definitions, deploying Software Access Catalog overview download URL 263 Speccy tool 100 SPR 250 SQO Enterprise v2 11 Standard v1, IBM Cloud 10 StoredIQ for Legal databases backup and restore, managing 606 sub-systems, IBM Cloud Pak for Security IBM Case Management 299 IBM Orchestration and Automation 299 IBM Security Data Explorer 299 IBM Threat Intelligence Insights 299 sudo 231 T

Tty 233 two-factor authentication (2FA) 273 U UBI 315 ufone_tweets.csv tutorial example file collection 564 UIMA Apache Regular Expression Annotator incorporating Unstructured Information Management Architecture (UIMA) pipeline 461 UVU 260 V virtualisation flag 417 virtualization engine flags reference link 417 Virtual Machine 260 VMWare upgrade about 425 CENTOS 8.0 iso image, downloading 426 CENTOS Linux 8.0, installing 426 jumbo frame support 425 multiple display shortcut key 425 preserve network configuration 425 PVSCSI device support 425 VMware disk size and types setting 414 VMware memory size

setting 414 VMware virtual machine (VM) 130 VMware Workstation Pro 15.1.0 installing 400 installing, from disk .iso image 413 upgrading 401 VMware Workstation Pro 16.0 upgrading to W Watson Explorer Applicaton Builder 12.0.3.0 installing Watson Explorer BigIndex 12.0.3.0 installing Watson Explorer Engine about 497 installing 509 Results Module, installing 509 ZooKeeper, installing 509 Watson Explorer Engine 12.0.3.0 installing Watson Explorer Engine administration tool installation about 515 default login credentials 522 encryption key generation 515 Help About menu 524 repositories, unpacking 523 system check Watson Explorer Engine embedded webserver, configuring

Watson Explorer Results Module 12.0.3.0 installing Watson Explorer ZooKeeper 12.0.3.0 installing Watson foundational component installation about 497 available component modules 498 installable modules 497 Results Module service, installing 505 services, starting in order 504 WebSphere 30 Windows subsystem for Linux release 2 (WSL 2) 231 worker node server base install, repeating 437 WS2 Linux containers 196

Y YAML 315 yum downgrade 6 yum installer 43 Z

ZooKeeper 497