...
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
...
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
...
an OBIEE configuration file in a workflow
Include Page Using an OBIEE config file in a workflow Using an OBIEE config file in a workflow