OWB 11gR2 – Getting to grips with configurations
By David Allan-Oracle on Apr 13, 2011
The 11gR2 release has a useful feature for altering the shipped configuration property values – you can set default property values for all sorts of information, from code generation modes to analyze table settings and many more. The default values are captured in a template – a template for a configuration. So you can have different default settings per configuration, see the OBE here. Objects will use these default settings rather than those shipped with the product. In the past users have done this kind of thing by setting properties via script after they have been created.
The ‘Globals’ panel has the configuration templates node, new templates can be created here;
When the template editor is launched you will see all of the object types that OWB let’s you set default configuration properties for – you will see the object types listed in a tree with properties as children in the tree and the OWB seeded property values listed, a column with the new template name is available to change the values. Below I have changed the generation mode property to ‘Set based’ in my MY_CONFIG_TEMPLATE, I could have changed the analyze table statements property to true for example also or any other.
This is a sparse matrix, so if no value is specified for your template the seeded default is used. You can look for yourself, but there are lots and lots of properties that you can tweak the defaults for.
After I have finished with defining my template, how do I use it? It is a configuration template, so I can set the template to use in my configuration. below I am changing my default configuration to use the newly created template (if you leave the value to Unspecified the OWB seeded value is used).
Then when I create new mappings, by default the default properties are the ones defined in the template, see below my mapping AMAP has the generation mode set to ‘Set based’.
I have shown just mappings above, but the configuration model is exposed such that you can change the defaults for all objects. So when you find yourself changing en-masse configuration property values for your objects and wishing the defaults were different, now you know what to do.