Anonymous_User Absent Member.
Absent Member.
382 views

scripting driver: heartbeat - shouldn't it return the result back to the engine?

I've added logic to the Heartbeat.ps1 script to return success, error or warning depending on the application specific check.

I can see this written to a WSDXXXX.tmp.OUT file:

For example:

IDMSETVAR: COMMAND=status
IDMSETVAR: STATUS_LEVEL=error
IDMSETVAR: STATUS_MESSAGE=heartbeat error
IDMSETVAR: STATUS_TYPE=heartbeat

The driver shim trace shows that the heartbeat script executed successfully, but it doesn't seem to send this back to the engine.

(trace): --->DriverShim publisher channel: polling...
(trace): --->DriverShim publisher channel: executing heartbeat
(trace): --->WindowsScript Driver publisher channel: executing heartbeat script
(trace): WindowsScript_executeCommand: Executing command bin\scriptclient.exe "scripts\powershell\Heartbeat.ps1" "C:\Windows\TEMP\WSD54A5.tmp" "C:\Windows\TEMP\WSD112F.tmp"
(trace): WindowsScript_executeCommand: command exited with code 0
(trace): Received document from publicationShim:
(trace): <nds dtdversion="1.1" ndsversion="8.6">
(trace): <source>
(trace): <product version="4.0.2" build="Apr 22 2014 15:39:53" />
(trace): <contact />
(trace): </source>
(trace): <input />
(trace): </nds>
(drv_driver): Driver_registerObjectDn: starting
(drv_driver): Driver_registerObjectDn: ending
(trace): Document consists only of a state; not sending to the remote side
(trace): Returning to publisher.
(trace): <nds dtdversion="2.0" ndsversion="8.x">
(trace): <output />
(trace): <status level="success" />
(trace): </nds>

I have the following config:

DRIVER_INIT_PARAM_auto-loopback-detection=true
DRIVER_INIT_PARAM_script-command=bin\scriptclient.exe
DRIVER_INIT_PARAM_script-trace-file=logs\script-trace.log
DRIVER_INIT_PARAM_script-timeout=120
DRIVER_INIT_PARAM_use-windows-efs=false
DRIVER_INIT_PARAM_script-trace-output=true
DRIVER_INIT_PARAM_name-mapping=LogonNameMap
AUTH_ID=<omitted>
AUTH_CONTEXT=<omitted>
APPLICATION_PASSWORD=<omitted>
windows-service=true
SUBSCRIBER_INIT_PARAM_subscriber-script=scripts\powershell\Subscriber.ps1
INSTALL_PATH=C:\PROGRA~1\Novell\WSDriver\
PUBLISHER_INIT_PARAM_polling-script=scripts\powershell\Poll.ps1
PUBLISHER_INIT_PARAM_heartbeat-script=scripts\powershell\Heartbeat.ps1
PUBLISHER_INIT_PARAM_pub-polling-interval=60
PUBLISHER_INIT_PARAM_pub-heartbeat-interval=30
PUBLISHER_INIT_PARAM_pub-disabled=false
Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: scripting driver: heartbeat - shouldn't it return the result back to the engine?


I'll look into this, Alex.

-- Sam


--
Zygomax
------------------------------------------------------------------------
Zygomax's Profile: https://forums.netiq.com/member.php?userid=215
View this thread: https://forums.netiq.com/showthread.php?t=52147

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: scripting driver: heartbeat - shouldn't it return the result back to the engine?


I reproduced this. It will require a code change, so we'll release a
hotfix. Hopefully I can get you a beta fix by the end of the week.


--
Zygomax
------------------------------------------------------------------------
Zygomax's Profile: https://forums.netiq.com/member.php?userid=215
View this thread: https://forums.netiq.com/showthread.php?t=52147

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: scripting driver: heartbeat - shouldn't it return the result back to the engine?


Here is the Bugzilla bug for this:
https://bugzilla.novell.com/show_bug.cgi?id=905134.

I have added a beta hotfix (64-bit) for this. It is private on the bug
however, so contact your NetIQ rep if you need it.

Sam


--
Zygomax
------------------------------------------------------------------------
Zygomax's Profile: https://forums.netiq.com/member.php?userid=215
View this thread: https://forums.netiq.com/showthread.php?t=52147

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.