Versions Compared

Old Version 2

changes.mady.by.user Joel Wenzel

Saved on

compared with

New Version Current

changes.mady.by.user Tristan Butzine (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can either

  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)

Tip

  • Configuration files 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.

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.

Image Removed

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.

Image Removed

And lastly, you can see it configured below on the environment instance.  For more information on using FlexDeploy workflow properties, see Defining Workflow Properties.

Image Removed