@Username (OpenInsight 32-bit Specific)
At 07 JUN 2007 09:15:49AM Simon G Wilmot wrote:
Hi all,
Not sure if this is at all possible, but … is it possible to hoodwink the system to change the @username setting on the fly ??
Reason is that we are doing a background processor to run various reports / processes etc and would like the 'process' to take on the characteristics of the user for Audit purposes. Obviously having to use a different variable will mean a lot more coding changes within the system !!!
TIA … and hope,
Simon
At 08 JUN 2007 04:32AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
That security hole would be so big, you know that guy who couldn't hit the broadside of a barn? He'd hit that.
World leaders in all things RevSoft
Revelation Conference 2007, London - Wednesday 27th June Click here to register for the premier Revelation Software EMEA event of 2007
At 08 JUN 2007 05:38PM Richard Hunt wrote:
Just thought I would offer this…
Within a login routine (or startup routine), you could set a common variable that would contain individual user info.
At 08 JUN 2007 09:25PM Bob Carten wrote:
Have your job processor spawn child instances of OI using shellexecute with parameters such as "/ap=MYAPP /un=MYUSER /pw=MYPASS /sn=T1234".
Have your application's startup script Get_Property('SYSTEM, 'SERVERNAME'). If servername starts with 'T' then call run_task(1234), then exit.
This technique lets each task run independently. Long running tasks do not block the job queue. Tasks run as OpenInsight, not just Oengine, so can generate OIPI reports.