RPD Configuration File

You can either

  1. Save config file during build operation as artifact, or
    1. Use SCM operation to export configuration file and save it as artifacts. Artifacts are available at deployment time.
  2. Extract it from SCM during deploy workflow or
    1. Use SCM operation to export configuration file prior to running deploy operation.
  3. Use absolute path to location on server. (not recommended as it requires manual setup on server)

Configuration files details

  • Configuration file can use FlexDeploy variables. See Property Replacement Support. You can use any property available in FlexDeploy or configure user defined property on Workflow Properties section.
  • Configuration file is not considered java properties file, even if you use extension as .properties, which means that you do not need to escape space on left side of equals sign.
    • For example, connectionpool_ds:A B Pool=${{OBI_A_B_DSN}} is valid syntax.
  • Make sure that you do not put single quote around variable values in configuration file or when you configure Property value in FlexDeploy for variables. FlexDeploy will automatically enclose variable values in single quote(').
  • It is possible that you may be using variable for ds, user, password inside connection pool, in which case you just need variables replacement in your configuration file.

Understanding the RPD configuration file

The RPD configuration file consists of information to replace variables, connection pool users, datasources (DSN) and passwords within the RPD. An example file is shown below.

#Property Replacement File
# The format is
# What Type of Replacement:Name Key=Value

connectionpool_ds:BSC=${{OBI_BSC_DSN}}
connectionpool_user:BSC=${{OBI_BSC_USER}}
connectionpool_pass:BSC=${{OBI_BSC_PASSWORD}}

#You can also replace variable values like this:
#variable:variablename=value
variable:BI_EE_HOME=${{FD_ORACLE_BI_HOME}}