Reconnect MD to Doors via DataHub when moving to new servers

Discussions about data interchange products Cameo DataHub and Magic RQ functionalities

Moderator: Moderators

Reconnect MD to Doors via DataHub when moving to new servers

Postby davidsontw » Fri Nov 30, 2018 2:54 pm

Hi all:

We moved our MD/Doors installation to a new server environment.

We have everything purring nicely including the DataHub plugin and link to Doors.

However, some of our MD projects already had links to Doors db, that connection is now broken. This is probably due to a new host name for the Doors server, or different id strings for the databases. We don't have any trouble establishing a new Data Source connection, but the old is broken. When trying to connect, we get the following message:

Cannot connect to database 0.0.0.0........ Please login to DOORS.

(and yes we are logged in to Doors)

So the old connection is referencing the old Doors server and not finding it. Is there a way to recover the data source relationship? All the data has been migrated to the new Doors server, naturally.

Thanks very much for any assistance you can provide.

-td
davidsontw
Forum Newbie
Forum Newbie
 
Posts: 6
Posts Rating:0
Joined: Thu May 17, 2018 10:00 am

Re: Reconnect MD to Doors via DataHub when moving to new servers

Postby patrick.d.dees@boeing.com » Tue Sep 17, 2019 1:34 pm

Did you ever come to a solution for this?
patrick.d.dees@boeing.com
Forum Newbie
Forum Newbie
 
Posts: 4
Posts Rating:0
Joined: Wed Sep 11, 2019 1:42 pm

Re: Reconnect MD to Doors via DataHub when moving to new servers

Postby davidsontw » Tue Sep 17, 2019 1:46 pm

Patrick:

Below is the suggested procedure from NM. The initial error we made was exporting the project in Doors and importing on the new server. This resulted in new ids. Instead, do a filesystem copy, or rsync or something similar, and move the data directory to the new server(s).

To migrate DOORS database, you may copy the database folder and paste into the new server. So the ID information will not change.
To migrate DOORS database by copying file:
1. With older server, browse into <DOORS>/<version>/data/. (you may replace 'data' with the folder that keep database.
2. Copy folder 'v6data' and paste into the new server.
Next we will rename the old DOORS server name to new one.
But first, from your information above, looks like you already have the another Data Source of new DOORS server added. You may need to remove it because after the renaming, 2 Data source will refer to the same server and cause error.
To replace the existing server name that DataHub kept for all reference with the new name.
1. Open the MD project that you work with DataHub. DO NOT call up DataHub Explorer yet. If DataHub Explorer is already called, you may reopen the project again.
2. Click menu Edit> Find and Replace...
3. In case DOORS server change from ‘oldserver.com’ to ‘newsserver.com’, you may find all entry of ‘@oldserver.com:36677' and replace with ‘@newserver.com:36677'. (you should see the server information in DOORS login dialog).
4. Save and reopen the project.
Now all DataHub reference should be back. Please let us know if you need more assistance.
davidsontw
Forum Newbie
Forum Newbie
 
Posts: 6
Posts Rating:0
Joined: Thu May 17, 2018 10:00 am

Re: Reconnect MD to Doors via DataHub when moving to new servers

Postby patrick.d.dees@boeing.com » Tue Sep 17, 2019 3:24 pm

davidsontw wrote:Patrick:

Below is the suggested procedure from NM. The initial error we made was exporting the project in Doors and importing on the new server. This resulted in new ids. Instead, do a filesystem copy, or rsync or something similar, and move the data directory to the new server(s).

To migrate DOORS database, you may copy the database folder and paste into the new server. So the ID information will not change.
To migrate DOORS database by copying file:
1. With older server, browse into <DOORS>/<version>/data/. (you may replace 'data' with the folder that keep database.
2. Copy folder 'v6data' and paste into the new server.
Next we will rename the old DOORS server name to new one.
But first, from your information above, looks like you already have the another Data Source of new DOORS server added. You may need to remove it because after the renaming, 2 Data source will refer to the same server and cause error.
To replace the existing server name that DataHub kept for all reference with the new name.
1. Open the MD project that you work with DataHub. DO NOT call up DataHub Explorer yet. If DataHub Explorer is already called, you may reopen the project again.
2. Click menu Edit> Find and Replace...
3. In case DOORS server change from ‘oldserver.com’ to ‘newsserver.com’, you may find all entry of ‘@oldserver.com:36677' and replace with ‘@newserver.com:36677'. (you should see the server information in DOORS login dialog).
4. Save and reopen the project.
Now all DataHub reference should be back. Please let us know if you need more assistance.


Thank you! Have you ever tried to see if this method works for changing the sync location from within a single DOORS database?
patrick.d.dees@boeing.com
Forum Newbie
Forum Newbie
 
Posts: 4
Posts Rating:0
Joined: Wed Sep 11, 2019 1:42 pm

Re: Reconnect MD to Doors via DataHub when moving to new servers

Postby davidsontw » Tue Sep 24, 2019 9:01 am

No, we haven't, but if I understand your question correctly I don't see why it would not.

-td
davidsontw
Forum Newbie
Forum Newbie
 
Posts: 6
Posts Rating:0
Joined: Thu May 17, 2018 10:00 am


Return to Cameo DataHub, Magic RQ

Who is online

Users browsing this forum: No registered users and 0 guests