...
- 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 (DSN) and passwords within the RPD. An example file is shown below.
Code Blockinfo | ||
---|---|---|
| ||
#Property Replacement File
The format is
What Type of Replacement:Name Key :=Value connectionpool_ds:BSC=${{OBI_BSC_DSN}}
#You can also replace variable values like this:
variablename=value
|
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 Type | Description |
---|---|
variable | Indicates 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_user | Indicates this line is to replace a connection pool user. |
connectionpool_ds | Indicates this line is to replace a connection pool datasource. |
connectionpool_pass | Indicates 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. during deployment based on property values configured in FlexDeploy.