![]() |
AMnet documentationContact: flexinet-support@ibr.cs.tu-bs.de |
With the tab pane Session Control Group all session present in the AMnet are displayed. Doing a right-click on a session reveals detailed information on a session. In order to join a session the user has to select the session and push the "Join Session" button.
After joining a session, all service announcements, that refer to this basic service, show up in the tab pane "Service Announcement Group". Again, doing a right-click reveals detailed information on the service. This is especially useful to obtain information about specific parameters of the service like e.g. quality and color of a MPEG stream. The current version does not group service announcements with respect to their session. This means that all service announcements are listed alphabetically. The joining of a service is not implemented yet.
The most interesting part is the placement of a deduced service. In order to do this, the user has to click the "New Service" button after he has selected a service. After that, the service repository is contacted and a description of all existing services is retrieved. This may take some seconds. If the error message "Unable to contact SMR" appears the LDAP server (6.1) is probably not running.
A short description on the existing services can be invoced with a right-click. After selecting a service, it has to be configured. A service consists of at least one service module whose behaviour can be controlled by parameters. All service modules can be selected and configured separately in the "Servicemodules" selector. The selector "Moduleparameter" then shows all the modules' parameters. If one of these is selected, the "Parametertype" and "Parametervalue" fields are set to default values. The user may now change these values in order to configure the module to suit the needs of the new service. Important: In order to save the updated values in the field "Parametervalue" the user has to press the enter key in that field.
After the configuration of the service, the user is asked how deep the search for the best matching AMnode has to go. This depth equals the maximum number of AMnodes between the AMnode that offers the new service and the receiver. After this configuration, the placing mechanism is started. Due to heavy communication with the LDAP server during this process, the placement may take some time. Once the selected AMnode is able to start the new service, it automatically sends out an service announcement.
The prior sections all referred to signalling and the configuration of the AMnet. The data transfer currently is not integrated into the signalling.In order to test modules in the current implementation, a test environment based on execution environments only has to be setup.