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 DataModel configuration file
The datamodel configuration file consists of information to replace the datasources of all datamodels within an OBIEE WebCatalog. An example snippet of a file is below
...
The Purple text above is the value to be replaced as the datasource reference on deployment.
Using FlexDeploy properties in the configuration file
FlexDeploy properties can also be used in the configuration file as data source values. An example is seen below.
Above, you can see the property used in the configuration file. Below, you can see the property defined on the FlexDeploy workflow used for deploying WebCatalog objects.
And lastly, you can see it configured below on the environment instance. For more information on using FlexDeploy workflow properties, see Defining Workflow Properties.
Using property replacement in a workflow
In order for the deployWebCatalog plugin operation to make use of a configuration file, the buildWebCatalog operation must first export the config file from some form of source control management system. In the example below, we are going to bring in a config file from an SVN repository, in addition to exporting our WebCatalog objects, during our build workflow.
After performing the build with the above workflow and project configuration, we should see the Datamodel.properties config file in our artifacts repository in FlexDeploy. Note that because we did not specify a checkout folder in the project configuration or a target subfolder in the SaveArtifacts workflow step the config file is checked out directly under the artifacts with no parent folder.
Due to the fact there is no parent folder, we only need to specify the config file name to the deploy workflow. Had we set a checkout folder or target subfolder, we would need to put the parent folder in the deploy workflow input, such as %PARENTFOLDER%/Datamodel.properties
