Update the inow.ini file - Perceptive Content Server Install Guide - Foundation 24.1 - Foundation 24.1 - Ready - Perceptive Content - external - Perceptive-Content/Perceptive-Content-Server-Install-Guide/Foundation-24.1/Perceptive-Content-Server-Install-Guide/Install-Perceptive-Content/Install-Perceptive-Content-Server-on-Linux/Update-the-inow.ini-file - 2024-04-02

Perceptive Content Server Install Guide
Platform
Perceptive Content
Product
Perceptive Content Server Install Guide
Release
Foundation 24.1
License

You must update the inow.ini file manually when installing Perceptive Content Server on Linux.

  1. Navigate to the shared /inserver/etc directory and then open the inow.ini file with a text editor.
  2. In the odbc.dbms setting, enter the appropriate database.
    Note: The database type is case sensitive and should be entered asSQLServer, Oracle, or PostgreSQL. The default is SQLServer.
  3. Change the odbc.dsnto the name of your DataSource (DSN), for example INOW. Ensure the section name is defined in the odbc.ini file.
  4. Update odbc.user.id and odbc.user.password to your user id and password.
    Note: The password supplied in the odbc.user.password setting is consumed by the application for encryption in the odbc.user.password.encrypted setting. This value is removed from the setting after encryption.
  5. To update the message queuing server settings, complete the following substeps.
    1. Update mq.host to specify the hostname or IP address of the node running the message queuing broker.
    2. Update mq.port to specify the port the message queuing broker uses.
      Note: The commonly used message queuing port for RabbitMQ is 5672.
    3. Update the mq.vhost with the name of the virtual host (optional).
    4. Update mq.username and mq.password to the user name and password used when connecting to the message queuing broker.
      Note: The password supplied in the mq.password setting is consumed for encryption in the mq.password.encrypted setting. This value is encrypted and removed from the mq.password setting after running the inserver -encrypt-config command. Do not manually update the mq.password.encrypted setting value.
    5. Update mq.secure.enable to TRUE to use SSL/TLS (optional).
      Note: The SSL_CERT_DIR or SSL_CERT_FILE environment variables must be set to the location of the CA.pem file. See Configure OpenSSL trust stores for SSL/TLS on Linux and Windows for more information.
  6. To update the message queuing client settings, complete the following substeps.
    Note: If any of the following settings are incorrectly specified in the inow.ini file, Perceptive Content Client cannot connect to the message queuing broker. If this occurs, a message is logged in Message Center.
    1. Update mq.client.reconnect.interval to specify, in seconds, how longPerceptive Content Client waits before reattempting to connect to the message queuing broker (optional).
    2. Update mq.client.host to specify the hostname or IP address of the node running the message queuing broker.
    3. Update mq.client.username and mq.client.password to the user name and password used when connecting to the message queuing broker.
      Note: The password supplied in the mq.client.password setting is consumed for encryption in the mq.client.password.encrypted setting. This value is encrypted and removed from the mq.password setting after running the inserver -encrypt-config command. Do not manually update the mq.client.password.encrypted setting value.
    4. Update mq.client.secure.enable to TRUE to use SSL/TLS (optional).
  7. Save and close the inow.ini file.
  8. Source the setenv.sh file to set up your environment variables. For example, if you are using /bin/bash, the command to source the file is: . ./setenv.sh.