| ILOG JRules User Guide > Customizing JRules > Tasks > Customizing Rule Team Server > Implementing the Session Controller |
Implementing the Session Controller |
PREVIOUS NEXT |
Users can customize the behavior of Rule Team Server by implementing the controller interface: ilog.rule.teamserver.model.IlrSessionController.
The controller allows you to customize the permission management in Rule Team Server, implementing the methods:
It also allows you to report changes, through the methods:
Finally it allows the user to control the various aspects of an EMF attribute or reference through the methods:
Rule Team Server comes with a default implementation of the controller: ilog.rule.teamserver.model.IlrDefaultSessionController.
To keep the default Rule Team Server behavior while adding your own customizing, it is recommended that you subclass the default controller instead of rewriting a new one.
To set up your own controller, repackage the Rule Team Server EAR in order to integrate your new class (see Repackaging the Rule Team Server EAR), giving the JAR file containing your custom class. For example:
ant repackage-ear ... -DadditionalJars=c:/myfolder/mycustomcode.jar
| Note |
| See Working with the Rule Team Server Ant Tasks for help on setting up your environment to correctly execute the Rule Team Server Ant tasks. |
Then, to specify to Rule Team Server that it has to use your controller class instead of the default one, you have two options:
set-config-param Ant task in Adding or Removing Configuration Parameters):
preferences.properties file that you can put in your JAR file:
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |