Thanks in advance,
rajesh

Much as I might like for my employer to ship me off to Edinburgh for the conference, I’m frankly stuck here in pergatory….. (errr – well Ottawa rather) … for the duration.

So will you be posting any documentation of that presentation either at the UKOUG site or here for us poor sods who won’t get to have a pint along the Royal Mile anytime soon? We’re just ramping up with OWB10R2, so I’m trying to read any real-world hints that I can get my grubby fingers on – especially as it relates to version control, deployment strategies, and (most critically) security issues.

Cheers,
Mike

An excellent point about multi-configurations, thank you for pointing this out. As you say, you can switch which control center the default configuration is associated with, and you can manually switch the module locations, which gives you the ability, without the Enterprise ETL Option, to run mappings on other databases.

This actually puts the multi-configuration feature in a different light – instead of it being essential and therefore something that would make you have to always license the Enterprise ETL Option, now it’s just something that makes life easer for you. You might still argue that multi-configuration support should be a free, built in feature, but given that the alternative, manual approach is what we’ve always had in the past, and that all the new functionality in 10gR2 has ended up in the pay-extra options anyway, it’s not as bad a situation as before. Thanks for pointing it out, that’s why I always like to publish this sort of stuff for review in the first place.

Also (and this is to Norbert as well) – yes, OMB*Plus scripting is the key to fast, efficient and error-free deployment across environments. It’s not something I’ve directly worked with myself, but I have colleagues that have scripted similar things in the past and I’ll try and get hold of some code examples in time for the presentation.

Thanks for the feedback

Mark

I’d like to add one more aspect of dealing with complex multi-stage development processes. It’s ’script based deployment’. In complex environments, where the operations guys are properly seprated from development, and where standard deployment procedures are in place, often enough direct tool access to the production system is forbidden. Therefore building, delivering, and deploying script based release packages is essential.

Fortunately, OWB provides the ability to do this, due to its OMB*Plus scripting interface. And that’s even free of charge, as long as you do not call Enterprise functionality of course. ;)

A note regarding deployment to multiple target systems and the use of configurations. You can target several (run-time) control centers i.e. target systems with one configuration. You just have to switch the configuration’s associated control center. The painful part, of course is, that you have to switch all the actual module locations everytime you want to deploy to another system too. However, you do not have to use Enterprise functionality this way.

Regards Holger

This was very timely as we are deploying to production shortly. I need to reconsider our infrastructure now that I see multiple configurations are an Enterprise option.

very interessting, cause we have the same to do with our customers. Good to read your opinions.
Even I like to hear your way for automating the whole way for code promotion between development, test and prod. May you will write a little bit about that?

For your next carrier step I wish you all the best.
Regards
Norbert