next up previous contents
Next: Search examples Up: Multi-MA extension Previous: Function of the Multi-MA   Contents

Deployment example

The instructions about how to compile DIET with the multi-MA extension are available in Section 2.2.5 and the configuration instructions are available in Section 10.1.2.

The example described here is about four organizations which want to share there resources. The first organization, named alpha, have ten SeD s which give access to the service a. The second organization, named beta, have eight SeD s with the service a and three with the service b. The third one, named gamma, have two SeD s with the service c. The last one, named delta, have one SeD with the service a, but the server crash and the SeD is unavailable.

Each organization has it's own DIET hierarchy. All MAs (one for each organization) are connected with the multi-MA extension as shown in Figure 12.2

Figure 12.1: Example of a multi-MA deployment
Image multima

The following lines appear in the MA configuration file of alpha. They tell that the multi-MA extension should listen for incoming connection at port 2001. They also tell that the MA should create a link toward the MA of the organization gamma and toward the MA of the organization beta. (The description of each configuration parameter are available in Section 10.1.2.)

agentType = DIET_MASTER_AGENT
dietHostname = diet.alpha.com
bindServicePort = 2001
neighbours = diet.beta.com:2001,ma.gamma.com:6000

The following lines appear in the MA configuration file of beta:

agentType = DIET_MASTER_AGENT
dietHostname = diet.beta.com
bindServicePort = 2001
neighbours = diet.alpha.com:2001,ma.gamma.com:6000

The following lines appear in the MA configuration file of gamma. The neighbours value is empty. This means that the gamma's MA will not try to connect itself to other MA. However, the three others are configured to be connected to gamma. So, after all, the gamma MA is connected to the other three.

agentType = DIET_MASTER_AGENT
dietHostname = ma.gamma.com
bindServicePort = 6000
neighbours =

Finally the following lines appear in the MA configuration file of delta:

agentType = DIET_MASTER_AGENT
dietHostname = ma.delta.com
bindServicePort = 2001
neighbours = ma.gamma.com:6000


next up previous contents
Next: Search examples Up: Multi-MA extension Previous: Function of the Multi-MA   Contents
The DIET Team - Ven 18 nov 2011 18:13:39 PST