Versions Compared

Old Version 11

changes.mady.by.user Chandresh Patel

Saved on

compared with

New Version Current

changes.mady.by.user Chandresh Patel

Saved on

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)
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.
Tip
titleConfiguration 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.

Code Blockinfo
languageiconjavafalse

#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:

variablename=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.

Property TypeDescription
variableIndicates this line is to replace an RPD variable value. Make sure to not put single quote around value in configuration file or when you configure property value in FlexDeploy. FlexDeploy will automatically wrap all variable values in single quote when RPD file is processed.
connectionpool_userIndicates this line is to replace a connection pool user.
connectionpool_dsIndicates this line is to replace a connection pool datasource.
connectionpool_passIndicates this line is to replace a connection pool password.

The Green text above is the property key.  In this case this will either be the variable name or the connection pool name which you want to edit. Note that it is OK to have spaces in this green text.

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 workflowduring deployment based on property values configured in FlexDeploy.