Latest Release
- Release candidate 2.0rc2 (07/03/12)
- Release candidate 2.0rc1 (23/12/11)
- Stable version 1.2.2 (09/02/12)
- Nightly builds available to test
Events
- 10/10/2011 - LDAPCon 2011 (Heidelberg, Germany)
- 13/06/2011 - RMLL (Strasbourg, France)
- 9/07/2010 - RMLL (Bordeaux, France)
Community
Get help, contribute or find professional services ...
Find out more!
Search
Download | Read more... | Get started!
Server control
LSC 1.3+ can be launched as a server which pull updates. You can control this server and request some operation through a JMX agent.
Activating JMX on LSC startup
To be able to use this client, you need to launch LSC with the following JVM arguments :
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
But take care that this installation is highly unsecured ! Please look at the “Securing JMX Access” section to implement a correct security configuration.
Control LSC
Then you need to launch org.lsc.jmx.LscAgent with the following parameters :
- -h <hostname> : hostname to connect to, localhost if you launch LSC and its agent on the same computer
- -p <tcp> : tcp port to connect to, here 1099
You can get the list of available tasks through :
- -l : List the available tasks
Or get an asynchronous task status :
- -s <taskname> : Get a task status
Then you can add the following parameters to launch start an asynchronous task :
- -a <taskname> : start the taskname
Or stop it :
- -o <taskname> : stop the taskname
If you want to force a object synchronization for a synchronous task, add :
- -a <taskname> : start the taskname
- -i <id> : specify the main object identifier
- -t <name=value,name2=value2,…> : Specify the attributes pivot to synchronize
Securing JMX access
To be completed by implemeting following advice : http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#remote


