Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

First, ask your hub admin for the base url for your hub. That admin will ask you for your public IP address so that the hub can open an inbound firewall hole for your system. "Inbound" access is from the perspective of the hub.   In most cases,  Generally if a downstream site can reach the Internet without restrictions, then no firewall configuration is necessary on the downstream side.

Second, ensure that you can reach the hub's tomcat service from your shrine host with this curl command. (Substitute the right DNS name for the hub.) In the example below, if your command executes successfully, you will receive a "pong 200" response:

...

  1. Once you select your node key value, it cannot be changed in the hub. Please select a value unique for your site. It is never displayed in the UI so should be insulated from branding considerations.
  2. Please keep your preferred node name descriptive and concise.  This is the value that will be displayed in query result outputs, so consider branding carefully. It is easy to change.
  3. Please use an i2b2 domain that reasonably reflects your site. Please do not use the default value.
  4. For your sys admin email address, consider using an alias email for your team to simplify your vacation plans.

--

TODO start here

The hub admin will run this curl command to add your node to the network.

...