Promoting jobs across partitions

[DKostelnik]

Hi,
Factoids: We have had 1 DataStage (7.5.1a) server environment setup that contains production, qa, version control, and development projects. This DataStage environment is on an AIX machine (5.3) and runs on one of the four partitions defined on the machine. I administer the "Ascential" toolset and do all promotions to qa and production from the development projects.

Issue: Due to new requirements, the production environment is being moved to a different partition than all the other projects. I have to promote jobs into the new production environment. I am looking for "the best practice" to do this.

I can think of several "off the cuff possibilities"
1) Sharing the production project across partitions via NFS - I don't know the impact (ie: leaving it in the development partition, but access it from the production partition via nfs)
2) Having 2 version control databases and exporting from one environment and importing into another
3) Some built-in internal DataStage/Version Control method.

I need "real life" solutions that would give me the best reliability. I would also like to hear about ways that are easy to implement as well.

The base problem is that I need to either:
1) Keep two version control projects in synchronization across partitions
2) Somehow share one version control project across partitions.

Does anyone have this same situation?

[chulett]

This change shouldn't change your process at all, other than the fact that when you promote to Production, you'll point to the new 'partition'.

[DKostelnik]

This change shouldn't change your process at all, other than the fact that when you promote to Production, you'll point to the new 'partition'. ...

Even though my Production project is in a different instantiation of DataStage that is essentially on a different machine?

I must appologize because I am really a database architect and do the Ascential administration on the side. Normally I have time to research questions such as this, but I am under a tremendous time-crunch.

How do I get Version Control on my "development server" to point to my Production Project on my "production Server"?

[chulett]

Since it's client based, it doesn't matter where any given project is located. Connect to the Version Control repository on your original server like normal, then when you promote change the 'Host system' value in the 'Attach to project' dialogue box. The first time you'll need to actually type the new value, but after that it will be available in the drop-down list.

That's really all there is to that.

[DKostelnik]

Since it's client based, it doesn't matter where any given project is located. Connect to the Version Control repository on your original server like normal, then when you promote change the 'Host system' value in the 'Attach to project' dialogue box. The first time you'll need to actually type the new value, but after that it will be available in the drop-down list.

That's really all there is to that.

OMG - I am such a moron. I look at that darn panel all day and NEVER payed any attention to the system. Yes, that works perfectly. Sorry for wasting your time, but I appreciate your help.

The funny thing is that I was looking at it from a client perspective and was wondering about configuration files or something. It was right in front of me. I have been brilliant in several things all week so I thought I got over being an idiot - apparently not!

[chulett]

No problem, glad I could help stop you from building some large, elaborate 'version control for multiple partitions' system.

Please mark the topic as Resolved using the button at the top of the screen!

[DKostelnik]

Done, now I can get back to my overly complex data warehouse modeling project. :D