Integration server configuration type

setdbparms.txt type

Use the setdbparms.txt type to create configurations that contain mqsisetdbparms commands to run when the integration server is deployed.

Summary of key details for the configuration type

File name or type Contains secrets Path extracted/imported to Maximum allowed per integration server
TXT Yes N/A (mqsisetdbparms commands in the file will be executed) Multiple

Creating the file for a configuration object of type setdbparms.txt

The setdbparms.txt type requires a TXT file that lists one or more mqsisetdbparms commands to run. For information about this command, see mqsisetdbparms command.

To create a TXT file that lists one or more mqsisetdbparms commands, complete the following steps:

  1. Create a text file named setdbparms.txt or use another name with a .txt extension. (In this topic, setdbparms.txt is used as the file name.)
  2. Include one or more mqsisetdbparms commands in the file by using either of the following formats:
    • Add one or more lines to the file, where each line contains three space-separated values that identify a resource, a user name, and a password, specified in this form:

      resource username password

      For each line, these three values will be used to run an mqsisetdbparms command with the -n, -u, and -p settings. For example, if you add an mq::user1 app1 topSecret line to your setdbparms.txt file, the following command will be executed:

      mqsisetdbparms -n mq::user1 -u app1 -p topSecret

    • Specify the entire mqsisetdbparms command in the file. The entry must start with mqsisetdbparms, and the command will be executed as specified.
    Note: For both formats, when the command is executed, all arguments are enclosed within single quotation marks, and any single quotation marks within the values are escaped. As a result, you must not include quotation marks on the parameters within the file.
  3. Save and close the file.

If you want to use cloud-managed connectors to run the actions or operations for a Designer integration that is deployed to the integration server, you must provide your IBM® Cloud API key details in a setdbparms.txt file.
Note: Cloud-managed connectors are available only if the Channel or version value (that is, spec.version) of the integration server resolves to 12.0.3.0-r1 or earlier.
  1. Add a line in this format to the empty file:
    flow_name apikey IBMCloud_APIkey

    Where:

    • flow_name is the file name stem of the BAR file.
    • IBMCloud_APIkey is the "apiKey" value in the apiKey.json file that contains details of the IBM Cloud API key.
      Contents of a setdbparms.txt file for cloud-managed connectors
  2. Save and close the file.

After you create the file, you can use it to create a configuration object as described in Configuration reference: Creating an instance from the Red Hat OpenShift web console and Creating an instance from the Red Hat OpenShift CLI.

For examples of how to use the setdbparms.txt configuration type, see Tutorials and examples.