Re: headless DOORs client
llandale - Sun Jan 16 14:59:03 EST 2011
I don't do this sort of thing but have played with it.
I think you are asking to be able to have an open DOORS client that you could send script commands to, perhaps via VBA. Yes, but don't start the doors client in "batch" mode as this means [1] DOORS ends when the script is done [2] there is no interface.
This solution will indeed get DOORS to start visibly and normally, but you can then send it DXL scripts to execute. Here's some VBA that worked:
Set DOORSObj = CreateObject("DOORS.Application")
MsgBox "After CreateObject..."
If IsNull(DOORSObj) Then
MsgBox "Login to Doors and click OK"
End If
DOORSObj.runStr ("#include <c:\doors-stuff\DXL-Local\Includes\HyperlinkToObj.inc>; fHyperLinkToObj(""SSHP-13"", """")")
In this case its insisting the user start DOORS manually. The VBA script was sucessful in a hyperlink or on the desktop, and would run the "Hyperlink" code, finding and displaying the object in question (SSHP-13).
In your case you'd probably want to see if DOORS was running, and if not then invoke it. Don't recall exactly how to invoke DOORS, but the command string would look something like this:
"C:\Program Files\IBM\Rational\DOORS\9.2\bin\doors.exe" -u Administrator -P "MyPassword"
The bad part of all this is when there are multiple DOORS versions on the computer or when the client can get at different DOORS databases. These facts lead me to the above original solution, the user logs into DOORS manually.
Hopefully someone with more experience will jump in here
|