Managing System Configurations at Connectathon

Managing System Configurations at Connectathon

Table of Contents

• How do I transfer my System configuration from Gazelle to Toolkit?
• Why are there multiple Systems in Toolkit with my name and a suffix?
• What if my System configuration in Toolkit is wrong?
• How can I pull configuration updates from Gazelle into Toolkit?
• What if my configuration is corrupted when it’s transferred from Gazelle?
• Can I create private System configurations in Toolkit?
• Can I share a private System configuration with another vendor?
• Can I make a private System configuration public?
• How do I create and use Test Sessions?
• How can I tell who owns a System configuration?

How do I transfer my System configuration from Gazelle to Toolkit?

At the beginning of the event the Toolkit administrator will automatically pull all Document Sharing system configurations from Gazelle into Toolkit.

Why are there multiple Systems in Toolkit with my name and a suffix?

A single Gazelle system frequently maps to multiple Toolkit systems. See Managing-System-Configurations-at-Connectathon for why and what the names mean.

What if my System configuration in Toolkit is wrong?

First, is it correct in Gazelle? If not update it in Gazelle and then pull your updates to Toolkit. See below for how.

How can I pull configuration updates from Gazelle into Toolkit?

This is done by the user from the Toolkit UI

1. Open the System Configurations tool (left menu tray, third from the top)

2. Select your system name

3. Push the Reload from Gazelle button

4. Re-select your system name

5. Review the configuration to ensure it transferred correctly

What if my configuration is corrupted when it’s transferred from Gazelle?

This happens occasionally when Toolkit hasn’t been updated correctly to match Gazelle. If this happens we can tag your configuration in Toolkit so that it is no longer dependent on Gazelle. Stop by and talk to us if you think this is needed. Once we take control of your configuration in Toolkit it will no longer update from Gazelle.

If we give you control of your System configuration we will ask you to create a private Test Session. The using the admin console we will make that Test Session the owner of the System configuration. Once that is done you can edit it freely. Your edits will be public as soon as you save them.

Can I create private System configurations in Toolkit?

Yes.

1. Create a new private Test Session (top control bar)

2. In that Test Session create a new System configuration

That configuration will only be visible when you are in that Test Session. No one else can see or edit it. A Test Session can hold multiple System configurations.

Can I share a private System configuration with another vendor?

Yes. The Test Session ID is private. Another user can not get your ID from Toolkit. But, you can give the ID to them. Once they have the ID they can access the System configurations you built in that Test Session. Note that i they have the ID of your Test Session they can also edit the System configurations in that Test Session.

Can I make a private System configuration public?

Yes.

Select the configuration and press the Promote button. It is now visible to all participants.

How do I create and use Test Sessions?

See Managing-Test-Sessions-in-Multiuser-Toolkit for details.

How can I tell who owns a System configuration?

This is displayed in the System Configuration tool. With a system selected the top row of the display has System Name on the left and Owner on the right. You will see the following values:

default - Toolkit owns - it is part of the base operation of Toolkit

gazelle - Gazelle owns - it will be updated each time we reload all configurations from Gazelle

cat - Toolkit owns - a Connectathon support system. Examples are catred, catgreen, cat__blue which are simulator replacements for the old RED, GREEN, BLUE copies of the Public Registry (no longer used)

This Test Session - you are in a private Test Session and you own the configuration

***** - a private Test Session owns the configuration (not the current Test Session). Its name is hidden from view.