Start and Stop driver from User application

Hi All,

I'm just wondering if we can start and stop the driver from User Application. I have a request to create a workflow request to allow user to start and stop a single driver. Do you guys have any idea how this can be done?

Cheers :D
  • On 2/2/2016 6:46 PM, knakkarit wrote:
    >
    > Hi All,
    >
    > I'm just wondering if we can start and stop the driver from User
    > Application. I have a request to create a workflow request to allow user
    > to start and stop a single driver. Do you guys have any idea how this
    > can be done?


    The workflow engine can call ECMA which executes in the web app server
    context, that could call the dxcmd functions via the Java class direct,
    or a Java/ECMA execute command.

    Not sure this is a great idea, but should work. Would require that the
    jars for the engine needed by dxcmd be on the UA server. I once tried to
    figure out all the dependent jars without complete success. Be nice to
    know the answer if you bother to figure it out.


  • Thanks for the quick reply. It sounds doable. I will try it and let you know the outcome.

    geoffc;2418679 wrote:
    On 2/2/2016 6:46 PM, knakkarit wrote:
    >
    > Hi All,
    >
    > I'm just wondering if we can start and stop the driver from User
    > Application. I have a request to create a workflow request to allow user
    > to start and stop a single driver. Do you guys have any idea how this
    > can be done?


    The workflow engine can call ECMA which executes in the web app server
    context, that could call the dxcmd functions via the Java class direct,
    or a Java/ECMA execute command.

    Not sure this is a great idea, but should work. Would require that the
    jars for the engine needed by dxcmd be on the UA server. I once tried to
    figure out all the dependent jars without complete success. Be nice to
    know the answer if you bother to figure it out.
  • knakkarit wrote:

    > Do you guys have any idea how this can be done?


    An alternative to Geoffreys approach would be set a trigger attribute on the
    driver object and have a (different) NULL driver stop the target driver when it
    sees the event.

    The advantage of this is that NULL drivers run in the engine server, which
    always has the dxcmd libs needed installed. You can see such a helper driver as
    an engine service to start/stop/restart drivers via LDAP, basically, which
    allows all kind of client apps to perform driver operations. Make sure to limit
    write access to the trigger attibute :-)

    One disadvantage over calling dxcmd directly from UA is status handling,
    though. When you call com.novell.nds.dirxml.util.DxCommand directly, you get a
    return code and know immediately about success/error. Via LDAP you would either
    firs