TBC EDG 7.0 vs 6.4: Teamwork Platform Parameters

23 views
Skip to first unread message

Tim Smith

unread,
Mar 3, 2021, 1:34:01 PM3/3/21
to topbrai...@googlegroups.com
Hi,

In TBC/EDG 6.4, I had the option of how my asset collection instances were stored per the options below:

image.png

Does this option exist in 7.0?  I did not see it in any of the configuration screens.  7.0 is defaulting to placing everything in the Repositories project as XDB files.  This makes migrating workspaces difficult since the Repositories project is automatically created in a new workspace.  i.e. It is not exclusively user-created content and thus is not importable into a new workspace.  I had always configure EDG to keep my content separate from TBC provided content.  

This brings me to a slightly larger question, what is the proper process to migrate Teamwork managed projects across workspaces?

Thanks,

Tim

Irene Polikoff

unread,
Mar 3, 2021, 2:30:17 PM3/3/21
to topbrai...@googlegroups.com
Hi Tim,

These options are still available, but they are no longer set in the UI. They are moved to the setup file used to deploy EDG on the server. It's all described in the upgrade and migration instructions. See  https://www.topquadrant.com/release-notes-topbraid-7-0/.

In general, EDG from TBC meant for testing customizations and sandbox work. Thus, we don't believe you would need to have these options configurable for TBC. In TBC, you will automatically get XDB and Repositories as the project when running  EDG in TBC. For server-based EDG you specify the database in the setup file but you automatically get Repositories as the project that contains asset collections. 

Regards,

Irene

On Mar 3, 2021, at 1:33 PM, Tim Smith <smith...@gmail.com> wrote:

Hi,

In TBC/EDG 6.4, I had the option of how my asset collection instances were stored per the options below:

<image.png>

Does this option exist in 7.0?  I did not see it in any of the configuration screens.  7.0 is defaulting to placing everything in the Repositories project as XDB files.  This makes migrating workspaces difficult since the Repositories project is automatically created in a new workspace.  i.e. It is not exclusively user-created content and thus is not importable into a new workspace.  I had always configure EDG to keep my content separate from TBC provided content.  

This brings me to a slightly larger question, what is the proper process to migrate Teamwork managed projects across workspaces?

Thanks,

Tim


--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAF0WbnJKYAGXVSnCZowtkzrrUT1Hp5JBObgKo-KrcHbH1Z92Vw%40mail.gmail.com.

Reply all
Reply to author
Forward
0 new messages