Providers configuration table can be accessed via Edit Driver/Plugin Options action of Distributed Architecture plugin's global configuration context. Every provider has the following properties:
| • | Name. The unique name of provider. Name must follow context naming conventions. |
| • | Connection Type. For Incoming connection, this consumer awaits and accepts TCP connections from providers. For Outgoing connections, the consumer establishes its own TCP connection to provider. |
| • | Address. Address of provider server. Valid for Outgoing provider connections. |
| • | Port. Port number on provider server to connect to. Valid for Outgoing provider connections. |
| • | Username. Name of user account to use for authorization on provider server. |
| • | Password. Password for the above user account. |
| • | Mount Point. Path of context that will act as a "connection point" for contexts imported from the provider server. This is the path on local (consumer) server. |
| • | Remote Root Context Path. Path of root context of context sub-tree what will be imported from provider server. This is the path on remote (provider) server. |
Example
Imagine that provider server has the following contexts:
A
A.B
A.B.C1
A.B.C2
The consumer server wants to import context sub-tree rooted at A.B. The imported sub-tree should be connected at path X.Y of the provider context.
For the above setup, we can use the following provider configuration options:
| • | Name: P |
| • | Mount Point: X.Y |
| • | Remote Root Context Path: A.B |
Once the consumer-provider connection is established and import operation succeed, we'll get the following relations between paths of contexts:
Context Path on Provider Server |
Matching Context Path on Consumer Server |
A.B |
X.Y.P |
A.B.C1 |
X.Y.P.C1 |
A.B.C2 |
X.Y.P.C2 |
|
It may seem more logical that paths on consumer server should start from X.Y.B. However, the name of root imported context is substituted by provider name (i.e. B substituted by P). This is necessary to avoid name duplication. For example, the consumer server has "admin" context in "users", and we want to import "admin" context from provider server by using "users" as a mount point. We can name the provider "provider_admin" and, thus, the path of root imported context on consumer server will be "users.provider_admin". The root context name substitution also helps to import remote root context (those context path equals to empty string). |
