Installing OpenSearch and OpenSearch Dashboards on Linux in Silent Mode

Encrypting the OpenSearch Passwords on Linux

You can use the setup script to install OpenSearch and OpenSearch Dashboards in silent mode by preparing a text file that includes installation details.

The passwords that you include in the silent mode text file must be encrypted using the PSCipher utility. You must use the pscipher.jar and psvault files that are part of the OSK DPK. The psvault that is delivered with PeopleSoft PeopleTools will not work for OpenSearch.

  1. Open a terminal window, and change directory to OSK_INSTALL. 

    cd OSK_INSTALL

  2. Extract the entire contents of OSK_FILENAME.zip in the same directory, OSK_INSTALL. 

    unzip OSK_FILENAME.zip

    Note:

    It is a good idea to extract into the same directory where you downloaded the zip files, and to extract into an empty directory for each new installation.

    The extraction creates the following directories in OSK_INSTALL:

    • setup directory — includes the setup script and a sample configuration file.

    • archives directory — includes archives for deployment

    • readme.txt file

    • opensearch-manifest — lists the version information for OpenSearch and JDK included in the DPK

  3. Change directory to OSK_INSTALL/archives, and extract pt-jdk21.0.yy.tgz into a temporary directory, or a directory with a different name.

    It may be necessary to extract the file twice. The sample uses pt-jdk-temp as the directory name

  4. Change directory to OSK_INSTALL/archives and extract pt-opensearch-3.2.0.tgz into a temporary directory, or a directory with a different name.

    It may be necessary to extract the file twice. The sample uses pt-opensearch-temp as the directory name.

    • bin

    • config

    • lib

    • logs

    • modules

    • plugins

  5. Copy psvault from the directory OSK_INSTALL/pt-opensearch-temp/plugins/orcl-security-plugin/config/properties to OSK_INSTALL/pt-opensearch-temp/plugins/orcl-security-plugin.

  6. Run the following command, specifying the user names and passwords for the OpenSearch administrator and proxy user.

    <path_to_java>/java -Dpscipher.path=<path_to_which_files_are_extracted> -cp <path_to_which_files_are_extracted>/pscipher.jar com.peoplesoft.pt.opensearch.pscipher.PSESEncrypt <administrative_user> <password> <proxy_user> 
<password> <output_path>/<outputfile>

    This example uses the default administrative user, osadmin, and proxy user, people:

    /home/OSK_INSTALL/archives/pt-jdk-temp/bin/java -Dpscipher.path=/home/OSK_INSTALL/archives/pt-opensearch-temp/plugins/orcl-security-plugin -cp /home/OSK_INSTALL/archives/pt-opensearch-temp/plugins/orcl-security-plugin/pscipher.jar com.peoplesoft.pt.opensearch.pscipher.PSESEncrypt osadmin password1 people password2 /home/OSK_INSTALL/os_output.txt

  7. Copy the encrypted text from the output file, os_output.txt in this example, without adding line feeds or spaces. Paste the encrypted passwords into the silentinstall.config file for the osadmin.password and people.password parameters.

Creating a Configuration File and Running the Silent Mode Installation on Linux

To install in silent mode:

  1. Create a configuration file.

    The OSK_INSTALL/setup directory includes a sample configuration file, silentinstall.config. If you want to use this file, it is a good idea to make a backup copy of the original file before you continue.

    Edit the configuration file with the required values. See the section Installing OpenSearch and OpenSearch Dashboards on Linux Interactively for guidance on specifying the values.

  2. Enter y (yes) if you want to install OpenSearch, or n (no) if you want to skip the OpenSearch installation.

    You must enter a value for this field. If you enter yes, you must specify values for the items labelled mandatory. If you enter no, you can leave them blank. Enter encrypted text for the passwords as described in the previous section.

    #Silent Install Configuration Values for installing opensearch 
and opensearch-dashboards

#Install opensearch Y/N is mandatory field
Install opensearch?[Y/N]= 

#Opensearch cluster name (mandatory)
cluster.name= OSCLUSTER

#Opensearch host name (mandatory)
network.host=

#Opensearch port number (optional-default 9200)
#If its upgrade from ES to Opensearch and if you want to use the 
same port number as ES. Please make sure ES is down else please 
enter a different port number for OS.

http.port=

#Opensearch data directory (optional-default OS_HOME/data)
#If its upgrade from ES to Opensearch and if you want to use the 
same data path as ES. Please make sure ES is down else please 
enter a different data path for OS.
path.data= 

#Opensearch log directory (optional-default OS_HOME/logs)
path.logs= 

#Opensearch discovery hosts (optional)
discovery.hosts= 

#Master eligible nodes (optional)
master_eligible.hosts=

#Opensearch heap size (optional-default 2)
OS_HEAP_SIZE= 

#Opensearch admin username (optional - default osadmin)
admin.user= 

#Opnesearch encrypted password for osadmin (mandatory)
admin.password=encrypted password

#Opensearch proxy username (optional - default people)
people.user= proxy

#Opensearch encrypted password for people (mandatory)
people.password=encrypted password

  3. Specify N (no) to skip the Logstash installation.

    When you enter N (no) for this field, you can leave the other parameters in the Logstash section blank. 

    Install Logstash?[Y/N]=N

    #Install Logstash Y/N is mandatory field
Install Logstash?[Y/N]=

#Logstash port number (optional-default 9800)
LS_port= 

#Logstash host name (mandatory)
LS_host = 

#The Opensearch username (mandatory)
OS_user = 

#The encrypted Opensearch password [encrypted using PSLSCipher.bat/PSLSCipher.sh] (mandatory)
OS_pwd = 

#Configure Logstash Y/N (for PeopleSoft Health Centre) is mandatory field 
Configure Logstash(for PHC)?[Y/N]= 

#IB REST service URL (mandatory)
IB_REST_URL= 

#Enter the encrypted IB user [encrypted using PSLSCipher.bat/PSLSCipher.sh] (mandatory)
IB_USER= 

#Enter the encrypted IB password [encrypted using PSLSCipher.bat/PSLSCipher.sh](mandatory) 
IB_PWD=

#location where JSON files need to be created(optional-default LS_HOME/pt/jmxmonitor)
JSON_LOC= 

#The polling frequency for JMX metrics (mandatory)
polling_freq = 

#The number of threads (mandatory)
no_of_threads =

#The Opensearch host name (mandatory)
OS_host =

#The Opensearch port (mandatory)
OS_port = 

#Do you want to create JSON files(Y/N) (mandatory)
JSON_files?[Y/N] =

#To fetch the alert configuration, alerts must be configured in 
Peopletools>Health Centre>Alert Configuration. Do you want to 
fetch the alert configuration parameters?(Y/N) (mandatory)
alert_conf?[Y/N] =

  4. Specify y if you want to install OpenSearch Dashboards, or n if you do not.

    You must enter a value for this field. If you enter yes, you must specify values for the items labelled mandatory in this section. If you enter no, you can leave them blank. 

    #Install Opensearch-dashboards Y/N is mandatory field
Install opensearch-dashboards?[Y/N]= 

#Opensearch-dashboards host name (mandatory)
opensearch-dashboards.host= 

#Opensearch-dashboards port number (optional-default 5601)
opensearch-dashboards.port=

  5. If you want to install OpenSearch Dashboards and connect to the currently-installed OpenSearch server, specify y (yes) for the following.

    If you want to install OpenSearch Dashboards and connect to a previously-installed OpenSearch server, specify n (no). 

    #Set the value to Y if Install Opensearch(Y) and Install 
Opensearch-dashboards(Y)
Use same OS?[Y/N]= n

  6. Specify the host name, port, OpenSearch administrative user, and encrypted password for the OpenSearch server.

    #Provide the Opensearch instance details mapped to Opensearch-dashboards
OS.host[http(s)://hostname]= 
OS.port= 
OS.user=
OS.password=

  7. If the OpenSearch is SSL enabled, enter the path to the certificate.

    #Provide SSL certificate path if Opensearch is SSL enabled.
OS.cacert.path=
  8. If OpenSearch is SSL enabled, provide SSL values for OpenSearch Dashboards.
    #Provide SSL required values for OSD if Opensearch is SSL enabled.
#Provide the absolute signed certificate path (Ex: /dir1/pt/osd_home/config/****.cer)
OSD.cert.path=
#Provide the absolute key file path(Ex: /dir1/pt/osd_home/config/****.key)
OSD.cert.key=
#Provide the absolute pem file path(Ex: /dir1/pt/osd_home/config/****.pem)
OSD.cert.pem=
  9. If you want to install Data Prepper, enter Y, and provide the full path to the configuration file.

    The installation is optional, and the default is n. 

    #Install data-prepper Y/N is optional field ( N - by default)

Install data-prepper?[Y/N]= 
#Provide the configuration files path for data-prepper
dp_config_path=
  10. If you want to install Fluent Bit, enter Y, and provide the full path to the configuration file.

    The installation is optional, and the default is n. 

    #Install fluent-bit Y/N is optional field (N - by default)

Install fluent-bit?[Y/N]= 
#Provide the configuration files path for fluent-bit
fb_config_path=

  11. In a terminal window, run the DPK setup script from OSK_INSTALL/setup as follows:

    Note:

    The command includes line feeds for readability. Do not include the line feeds when you run.

    ./psft-dpk-setup.sh –-install_silent 
--install_base_dir BASE_DIR
--config full_path_configuration_file

    • Use double-dashes when specifying the script options; for example, --install_silent.

    • For the install_base_dir option, specify the full path where you want OpenSearch and OpenSearch Dashboards installed. The installation directory is referred to in this documentation as BASE_DIR.

    • For the config option, specify the full path to the prepared configuration file. For example:

      Note:

      The command includes line feeds for readability. Do not include the line feeds when you run.

      ./psft-dpk-setup.sh –-install_silent
--install_base_dir /home/opensearch
--config /home/temp_install/silentinstall.config

  12. When the script completes, you see messages such as: 

    OpenSearch Installation Completed.
....
OpenSearch-dashboards installation is completed.

  13. After you complete the OpenSearch and OpenSearch Dashboards installation, you must configure the integration with the PeopleSoft environment.

    See "Integrating OpenSearch with the PeopleSoft Environment."

  14. To use OpenSearch Dashboards, see the Search Technology product documentation.

    See PeopleTools: Search Technology, "Working with Insights Dashboards for PeopleSoft Application Data."