Hi All,
V8.7 on Windows.
When we want to move jobs between Env, say Dev to UAT, is exporting the Job designs with Executables and the Parameter Sets enough, or do we also need to export the Table Definitions?
Can we use the Information Server Manager (will create .isx ??) for this by creating a package or should this be done via the Datastage Client Import/Export interface (.dsx)
Thanks
Datastaje Jobs Deploy between Env
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Information Server Manager is to be preferred, because it gives you the ability to create versioned "deployment packages" and to interact with source code control systems if that is your wish.
Table definitions do not need to be promoted (though it's not wrong to do so); when you load a table definition into a job design a copy of the table definition (rather than a reference to the table definition in the Repository) is made.
Table definitions do not need to be promoted (though it's not wrong to do so); when you load a table definition into a job design a copy of the table definition (rather than a reference to the table definition in the Repository) is made.
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.
-
- Participant
- Posts: 134
- Joined: Tue Jun 15, 2010 2:10 am
- Location: Bangalore
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Provided that identical hardware and identical versions of software are involved, deploying executables means that you do not require a compiler on the target environment.
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.