Running configuration scripts

Before you can configure the WebSphere® Application Server, you need to configure the installation.

Before you begin

You must run configureEnv.sh script after a change is made to the env_settings.ini file or the addition of any JAR file to the jar directory in an enterprise installation.

About this task

The configureEnv.sh script does the following tasks,
  • Validates the env_settings.ini file and notifies if there are any errors.
  • Generates the configuration for IBM® Product Master services.
  • Generates following Persona-based UI settings files:
    File name Used for... File Location
    application.properties pimcollector and indexer $TOP/mdmui/dynamic/indexer$TOP/mdmui/dynamic/pimcollector
    config.json User interface configuration $TOP/mdmui/dynamic/MDMUI
    dam.properties Digital Asset Management $TOP/etc/default/dam/config
    damConfig.properties Digital Asset Management $TOP/mdmui/dynamic/mdmrest
    dashboards_config.ini Dashboards $TOP/mdmui/dashboards/tnpmoed/conf
    ml_configuration.ini Machine learning services $TOP/mdmui/machinelearning/config
    restConfig.properties REST APIs $TOP/mdmui/dynamic/mdmrest
  • Generates a <install dir>/build/build.properties file for Apache Ant.
  • Generates the common.properties file.
    Note:
    • Comments inside the common.properties file are deleted after you run the configureEnv.sh script. If you want the descriptions for each property, refer the common.properties.default file.
    • If the common.properties file exists, a warning message is reported and displays the missing properties, which exist in the common.properties.template file.
    • If the common.properties file does not exist, you can either copy the properties from the common.properties.default file or delete the common.properties file and run the configureEnv.sh script to generate a new file.
    • If the configureEnv.sh script is run with an overwrite (-ov) option, then the script does not overwrite all the existing properties and appends only the newly added properties in the property file.
Following are the parameters for the configureEnv.sh script.
--ov
Overwrites all the existing generated files, thus you might lose your custom configurations in such files.
--dbpassword
=<database password>
Disables the Db2 password that is stored in the plain text. For more information, see Storing database passwords in an encrypted format.
--mqpassword
=<MQ password>
Disables the IBM MQ password that is stored in the plain text. Parameter to be passed if the value is removed from the env_settings.ini file.
--mongodbpassword
=<MongoDB password>
Disables the MongoDB password that is stored in the plain text. The value of the mongodb_encrypt_password parameter should be set to yes and the password value should be removed from the env_settings.ini file.
--smtppassword
=<SMTP password>
Disables the SMTP password that is stored in the plain text. The value of the smtp_encrypt_password parameter should be set to yes and the password value should be removed from the env_settings.ini file.
--espassword
=<Elastic Search password>
Disables the Elastic Search password that is stored in the plain text. The value of the elastic_encrypt_password parameter should be set to yes and the password value should be removed from the env_settings.ini file.

Procedure

  1. Go to the <install dir>/bin directory.
    Note: Use a short folder name for the <install dir> to avoid "java.lang.IllegalArgumentException: Value too long" error message during installation.

    Example

    Use /opt/MDM instead of opt/IBM/MDM/MDMv12.

  2. Run the <install dir>/bin/configureEnv.sh script.