![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: SYNERGY/CM client for several servers Topic Summary: Multiple server acces configuration Created On: 16-Mar-2007 08:00 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thank you Tony. Do you know if this files are the only ones that MUST be touched before launching the client? I understand that there is no difference between doing it on Windows or UNIX platform. I'll see bot config files and prepare a Java simple standalone app in order to change these parameters. What you say about having test environment in different patch or version than production one is true... That's another obstacle. Wonder if there could be in the future the possibility of having several client version installations simultaneously as it can be done with Telelogic DOORS. Many thanks and best regards. | |
![]() |
|
Hello:
Does anyone know about the exact reference of how configuring a SYNERGY/CM windows client in order to "attack" SYNERGY/CM different servers. When I say different I mean that each server has it's own router, obje_registrar and rest of daemon/processes. This is, I do want to have two independent SYNERGY/CM domains: one for management, new meta-model and scripting testing and user kind testing and the real one for production. What I would like is not to have distinct SYNERGY/CM client installations, but, as far as the installer asks for the port and machine name of the router daemon it looks like if the client could only be attached to one. And I wouldn't like to have the production server router daemon attending to testing processes. Many thanks in advance. Best regards. |
|
![]() |
|
![]() |
|
We have our own tool for managing that, it redefines the $CCM_HOME\etc\_router.adr content, and additionally modifies the ccm.ini files (both $CCM_HOME\etc\ccm.ini and %USERPROFILE%\ccm.ini) to set correct database paths and engine hosts.
Another complication on Synergy/CM 6.4 (and newer) is that it requires the Windows client to have the same patch level as the server. So it might be difficult to test out new patches in test environment and use the same client installation to connect to the production system as well. |
|
![]() |
|
![]() |
|
Thank you Tony.
Do you know if this files are the only ones that MUST be touched before launching the client? I understand that there is no difference between doing it on Windows or UNIX platform. I'll see bot config files and prepare a Java simple standalone app in order to change these parameters. What you say about having test environment in different patch or version than production one is true... That's another obstacle. Wonder if there could be in the future the possibility of having several client version installations simultaneously as it can be done with Telelogic DOORS. Many thanks and best regards. |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
SYNERGY/CM client for several servers
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.