Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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)
Tip
  • Make sure to remove any spaces from the strings or use environment instance property overrides like the example below as spaces will break the property file reader.
  • Configuration files 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.

...

Code Block
languagejava
#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:name:value
variable:BI_EE_HOME=${{FD_ORACLE_BI_HOME}}


Image RemovedImage Added

The Red text above is the property type.  The property types in the table below are the available options to replace in the RPD.

...

The Purple text above is the value to be replaced as the datasource reference on deployment.  

Using FlexDeploy properties in the configuration file

...

Using an OBIEE configuration file in a workflow

Include PageUsing an OBIEE config file in a workflowUsing an OBIEE config file in a workflow