J-RAG, tool for automated batch-generation of Oracle Designer objects such as Forms and DDL-scripts
Frank Brink concluded the evening with the world-premier of J-RAG, a tool that enables Nightly Builds of Complete and Patch releases from Oracle Designer. J-RAG provides an extension of the popular Ant build tool that knows how to use the Oracle Designer Batch Generators to generate DDL-scripts, TAPIs, Forms and Menus in a batch job. J-RAG is run from a Configuration definition in Oracle SCM – a configuration is used to collect versions of objects that make up a release or patch. When you have defined a configuration that specifies a release or patch, J-RAG can generate all objects that are required in that release or patch. Frank’s presentation can be downloaded here.
For organizations that run all their development from Oracle Designer and Oracle SCM, J-RAG is a potentially very useful tool. Frank’s estimated time savings of 10% for release management and 20% for the creation of nightly builds. The crucial capability in J-RAG – next to the clever integration with Ant and the many filter options – is the fact that it can create the binary GBU files that drive the Oracle Designer Batch Generators. It does so from Configuration Definition, making it a very fitting piece in release management in Oracle SCM.
J-RAG will be made available in October 2004, via the Supplement Option that customers of the iDevelopment Accelerator Suite usually acquire. Shortly following the first J-RAG release, there will be an addition that supports full nightly build generation.
3 thoughts on “AMIS Query: The Future of Oracle Designer (and other tools)”
Did J-RAG ever get published? Is it available for download somewhere?
Iâ€™ll explain my doubt:
I have 2 workareas in RON (Repository Object Navigator).
I imported a container from workarea “A” to workarea “B”, using the import method “Import from an ORACLE database export fileâ€?.
After the import, I did a chek-in in the container I imported for workarea “Bâ€?.
I modified some containerâ€™s objects that are in the workarea “A”.
When I tried to import the container that I modified from worarea “A” to workarea “B”, I had no success, cause already exists a container with the same name in the workarea “Bâ€?.
I want to update the container of the workarea “B” with the modifications that I did in the container of the workarea “A”.
Could you help me, how can I do it?
[…] nt team. It sheds some more light on the issues we discussed just a few days ago. See also this post. John explained how within the Apps division, there is a strong drive towards a Single […]
Comments are closed.