...
You can either
- Save config file during build operation as artifact, or
- Use SCM operation to export configuration file and save it as artifacts. Artifacts are available at deployment time.
- Extract it from SCM during deploy workflow or
- Use SCM operation to export configuration file prior to running deploy operation.
- Use absolute path to location on server. (not recommended as it requires manual setup on server)
Tip |
---|
|
Understanding the RPD configuration file
The RPD configuration file consists of information to replace variables, connection pool users, datasources and passwords within the RPD. An An example snippet of a file is shown below.
Code Block | ||
---|---|---|
| ||
#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}}
|
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 Page