Harvest

Expand all | Collapse all

CA SCM Eclipse Plug-in: Can you keep your existing workspace projects when changing broker servers?

Jump to Best Answer
  • 1.  CA SCM Eclipse Plug-in: Can you keep your existing workspace projects when changing broker servers?

    Posted 07-23-2015 04:42 PM

    Our CA Harvest admin has created a new harvest server.  Currently both the old and new harvest servers are pointed to the same database repository.  This is just a lateral move to a new server OS.

     

    Our developers use the CA SCM Eclipse Plug-in to check out/check in code to their workspace.

    Currently they all have a broker connection pointing to the old harvest server.

    All of their eclipse workspace projects therefore point to that specific broker connection.

    Example:  my-project (my-broker-name:code-repository-name)

     

    Is there a way to change the broker connection within the CA SCM Eclipse Plug-in to point to the new harvest server name without requiring everyone to delete all of their projects, create a new broker connection for the new harvest server, then add all of the projects back to their workspace?

     

    We've tried right-clicking on Properties within the CA SCM view of Eclipse on the active broker, but the "Broker Connection Properties" tab only shows the user name and a button to "Clear Password".  Similarly other tabs do not allow for the changing of any connection settings.  We've tried this in versions 12.0 and 12.5 of the CA SCM Eclipse Plug-in.

     

    We've also tried editing the Windows hosts file to point the DNS name for the old server to the IP address of the new server, but this does not seem to work either.  An error pops up saying that the connection to broker, my-broker-name, is no longer valid.

     

    Doing a Team->Disconnect Project and then a Team->Reconnect Project only reconnects back to the old broker name.

     

    Surely there must be some way to modify the server address of an existing broker connection without requiring everyone to delete and re-add their entire workspace?

     

    Note:  Our harvest servers are also using Active Directory authentication.  I did see a note here: Change Broker Connection Properties

    Which said, "Note: When External Authentication is active, the Properties dialog will not have a Change Password button and passwords cannot be changed from the CA Harvest SCM Plug-In for Eclipse."

    That was on the help tab for "Change Broker Connection Properties".  So maybe for some reason since we have Active Directory authentication enabled, we cannot change the broker connection properties once the broker connection has been created within Eclipse?

     

    Message was edited by: Brad Fowler Added Note regarding Active Directory authentication setting.



  • 2.  Re: CA SCM Eclipse Plug-in: Can you keep your existing workspace projects when changing broker servers?
    Best Answer

    Posted 08-05-2015 01:55 AM

    Hello Brad,

     

    Actually there is no way this can be achieved as such because, harvest connection settings are stored in sync-info files of eclipse. Since they are managed by Eclipse Framework itself, we do not provide such change in broker. Because otherwise we will have to update all sync-info files.

     

    However, there is one way using RT_FORCE_NODE_NAME environment variable.

     

    • On Windows platforms, define the system variable, RT_FORCE_NODE_NAME, and assign it a node name. The value or node name assigned overrides the defaultnode name used by Enterprise Communicator.
    • On UNIX platforms, define an environment variable, $RT_FORCE_NODE_NAME, in the user shell. Set the value of this variable to override the default node name used by Enterprise Communicator.

    You must restart RTserver, the product broker and the product clients for the change to take effect.

     

    On the machine where broker is running define this variable with old name.
    Also ensure that old broker is not running any more.



  • 3.  Re: CA SCM Eclipse Plug-in: Can you keep your existing workspace projects when changing broker servers?

    Posted 08-05-2015 09:31 AM

    Could all of the .syncinfo files be manually edited to change broker names?  They don't appear to be normal text files, so possibly they could be edited in hex mode?



  • 4.  Re: CA SCM Eclipse Plug-in: Can you keep your existing workspace projects when changing broker servers?

    Posted 08-06-2015 03:53 AM

    We don't support nor recommend to alter syncinfo files.
    Best way to go forward is:

    1) Checkout the code fresh from new broker which you have configured and create workspace using that.

    2) Use RTFORCE_NODE_NAME variable to point towards old broker name and continue to use.



  • 5.  Re: CA SCM Eclipse Plug-in: Can you keep your existing workspace projects when changing broker servers?

    Posted 08-06-2015 12:23 PM

    I don't think we'll need to use RTFORCE_NODE_NAME as they've already created the new server.  It sounds like we'll just have to checkout the code from the new broker connection and create a new workspace using that broker connection.  It's unfortunate that there's no method to migrate to a new broker name, or rename a broker name. 

    I've marked your first answer as correct.

    Thanks for the information.