Tag: connected workgroups
-
Replication – Common Workflows
Here are some code snippets to help you out when dealing with replicated environments. Finding out your local workgroup One of the first things you will probably want to do is figure out which workgroup you are connected to. This one is pretty easy, just call GetLocalWorkgroup() in the ReplicationService. If you want to get…
-
Replication – The Vault Mirror Bug
Replication is one of those "game changer" features. It's a very powerful feature, but it has the potential to impact any customizations you write. Code that works perfectly well in a single workgroup environment may behave incorrectly in a multi-workgroup environment. Even worse, the incorrect behavior may be intermittent, making it hard to isolate what…
-
Replication – Testing on a Single Server
The recommended way to test your applications with the connected workgroups feature is to use 2 computers for testing. If you only have 1 computer you can easily fix the problem by conjuring another one with your magic wand. What's that you say? You don't have a magic wand? No problem. Just go to your…
-
Replication – Introduction
Replication. Replication. Also known as Connected Workgroups, Replication is the feature where you can create multiple, working copies of the Vault database. The main reason you would want to do this is if you have multiple locations working on the same vault where your network latency is too large between locations. Replication speeds things up…
You must be logged in to post a comment.