knakkarit1 Absent Member.
Absent Member.
530 views

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 😄
Labels (1)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: Start and Stop driver from User application

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.


0 Likes
knakkarit1 Absent Member.
Absent Member.

Re: Start and Stop driver from User application

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.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Start and Stop driver from User application

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 & forget or have to poll a status attribute your NULL driver has to
maintain.

--
http://www.is4it.de/en/solution/identity-access-management/
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.