All,
I need to work two different versions of DS Servers,for this i installed these two different version clients in different locations on my PC and also installed multi client manager utility.
Everything installed well but multi client manager is not showing in program files..how to invoke/work with multi client manager.
Please advise.
Thanks in advance..
Multi Client Manager
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Check if you have "MultiClientManager.exe" in the path . If it exists, create a shortcut to your Desktop. Viola!
Code: Select all
C:\Program Files\Ascential\DataStage Multi-Client Manager
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Code: Select all
Start Menu ---> Right Click on "My Computer" -----> Click on "Manage" (This opens 'Computer Management' window)-----> Double click on "Services and Applications" ----> Double click on "Services" (This will open up the Services list).
Also, bear in mind that MCM ( Multi-Client Manager) will not work properly if you have 'Version Control' installed. You can have any one of them, not both.
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
I know there's something to that effect in the MCM readme, and it's been awhile since I've had a need for the MCM but I think that's a little too literal of a reading.I_Server_Whale wrote:Also, bear in mind that MCM ( Multi-Client Manager) will not work properly if you have 'Version Control' installed. You can have any one of them, not both.
I've had both installed. I've used both at the same time - but only when 'switched' to the primary client version - the one that matches the VC client. When you switch out to the other client, don't use Version Control. I don't think they can't co-exist but more to the point that it can't switch VC for some reason.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Craig,
Gotcha! Does that mean that, say if I have DS Server 7.5.1.A and DSEE 7.5x2 installed, then should I be installing Version Control twice respective to the client version.
And after this, using MCM, I would be able to use only ONE version of the 'Version Control' but not the other. Am I in the right path here?
Thanks,
Whale.
Gotcha! Does that mean that, say if I have DS Server 7.5.1.A and DSEE 7.5x2 installed, then should I be installing Version Control twice respective to the client version.
And after this, using MCM, I would be able to use only ONE version of the 'Version Control' but not the other. Am I in the right path here?
Thanks,
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Not sure, as I've never installed two different versions of Version Control, let alone mixed Windows and UNIX flavors. It will depend on how it handles the registry, I would think, more than likely only the second (most recent) install would function correctly.
Why would you need to do that? Typically, the MCM is meant to help when you are testing or in the process of migrating to a new version. You don't need both once things are settled down and would only be 'versioning' jobs in the 'old' release. At some point everything would get blessed and transferred to the 'new' release and then you'd install the new Version Control.
Or do you actually need to support two versions from the same PC for an extended period of time? If that's the case, I'd check with Support to get an official ruling on the subject...
Why would you need to do that? Typically, the MCM is meant to help when you are testing or in the process of migrating to a new version. You don't need both once things are settled down and would only be 'versioning' jobs in the 'old' release. At some point everything would get blessed and transferred to the 'new' release and then you'd install the new Version Control.
Or do you actually need to support two versions from the same PC for an extended period of time? If that's the case, I'd check with Support to get an official ruling on the subject...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers