[lsc-changes] [Ldap Synchronization Connector (LSC)] page changed: documentation:2.0:execution:start
webmaster at lsc-project.org
webmaster at lsc-project.org
Fri Sep 30 00:22:05 CEST 2011
A page in your DokuWiki was added or changed. Here are the details:
Date : 2011/09/30 00:22
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.24 Safari/535.2
IP-Address : 126.96.36.199
Hostname : nsg93-4-82-235-239-71.fbx.proxad.net
Old Revision: http://lsc-project.org/wiki/documentation/2.0/execution/start?rev=1317334151
New Revision: http://lsc-project.org/wiki/documentation/2.0/execution/start
User : sbahloul
@@ -4,9 +4,9 @@
* **synchronous mode** : this is the simplest way to start LSC. Once the source service has been listed, objects are retrieved from the source and from the destination. New objects are created, existing are updated and at the end the LSC will stop (no more daemon or program running)
* **clean mode** : this mode is complementary to the first one for cleaning the destination service by retrieving objects and checking their existence inside the source service. If they exist nothing is done but if they don't they are deleted from the destination service.
* **asynchronous mode** : in this mode, LSC is started as a daemon. If the source service has something to synchronize, LSC will retrieve updated objects one by one and will synchronize it wich the destination service. If no update is provided, LSC will sleep for 5 seconds and try again. It will never stop until an explicit request is done.
- ==== Command line invocation ====
+ ==== Starting LSC ====
LSC can be start with either synchronous or asynchronous mode. In synchronous mode, LSC can also schedule a clean mode at the end of the synchronous mode.
=== Synchronous launch ===
@@ -27,6 +27,31 @@
When multiple asynchronous tasks are started, they are started as separate thread inside the same daemon.
- ==== Remote invocation ====
+ ==== Interaction with an already started instance ====
+ When LSC is started in asynchronous mode, it is still possible to request operations through the JMX protocol.
+ === LSC daemon required options for JMX remote invocation ===
+ To enable JMX, some Java Virtual Machine settings are required :
+ $ export JAVA_OPTS=-Dcom.sun.management.jmxremote \
+ -Dcom.sun.management.jmxremote.port=1099 \
+ -Dcom.sun.management.jmxremote.authenticate=false \
+ $ lsc -a <comma separated list of tasks' name|"all" keyword>
+ But doing such settings, please notice that anyone can send commands to your LSC instance listening on all your network interfaces on the 1099 TCP port ! (At this time this is not a simple task to bind JMX to the local interface only, RFU :)
+ === LSC remote invocation by lsc-agent command line tool ===
+ The lsc-agent command line tool is able to connect remotely to the LSC instance and to do some interesting things :
+ * **-a** gives the ability to start a task
+ * **-l** provides a list of asynchronous tasks
+ * **-s** gives the status (running or not) of an asynchronous task
+ When starting a task, if the id and pivot attributes are provided (**-i** and **-t** options), LSC will start the corresponding synchronous task. If not, LSC will start the corresponding asynchronous task.
+ Of course it is possible to specify an hostname and a port to connect to another host through **-h** and **-p** parameters.
This mail was generated by DokuWiki at
More information about the lsc-changes