At this time we migrate the dsx code from one environment to another by exporting and importing dsx code and compiling them manually. The dsx is first sent to ACCUREV for version control and then migrator will pick up the dsx and move to newer environment.
My question is "Do we have ANY tool outside of Datastage that can be used to automatically pick up dsx from one place/environment, deploy the code to another environment and compile them, all 100% AUTOMATED?"
Any suggestions will be welcome.
Automatic deployment of DSX from one environment to another
Moderators: chulett, rschirm, roy
Automatic deployment of DSX from one environment to another
Datawarehouse Consultant
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You need DataStage to produce the DSX file.
That having been done, it's just a text file - you can use any tool you like to check it in to a version control system.
At the other end, once it's checked out and deployed to the new system, you need DataStage to effect a full or partial import.
The same considerations obtain if you use the istool command (which produces and consumes "isx" format files). However, with this tool (or its GUI equivalent Information Server Manager) you can use an Eclipse plug-in to communicate directly with source code control systems.
That having been done, it's just a text file - you can use any tool you like to check it in to a version control system.
At the other end, once it's checked out and deployed to the new system, you need DataStage to effect a full or partial import.
The same considerations obtain if you use the istool command (which produces and consumes "isx" format files). However, with this tool (or its GUI equivalent Information Server Manager) you can use an Eclipse plug-in to communicate directly with source code control systems.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.