Hi,
I don't know a way to temporarily disable a DSO mapping which would keep
the entries pending, but if you have the basic DSO field Transfer Status
on your form, you can try inserting entries to Distributed Pending form
for the failed ones using some direct SQL statements, based on queries
on this field. To do this you have to let them fail first of course, by
disabling the mapping. This will save you from thinking about merge
filters, exports etc.
Here is an example that would work in Oracle:
INSERT INTO distributed_pending (PENDING_ID, SUBMITTER, CREATE_DATE,
OWNER, LAST_CHANGED_BY, LAST_CHANGED_TIME, STATUS, FORM, SOURCE_ID,
PENDING_TYPE, POOL, TRANSFER_MODE)
SELECT LPAD(request_id, 15, 'X00000000000000'), 'X', (sysdate -
cast('01-JAN-1970' as date)) * 86400), 'X', 'X', (sysdate -
cast('01-JAN-1970' as date)) * 86400, 0, 'My Form', request_id, 1, 'My
DSO Pool', null FROM my_form WHERE transfer_status > '0'
INSERT INTO H2 (ENTRYID, T0, U0) SELECT p.PENDING_ID, p.CREATE_DATE,
p.SUBMITTER FROM distributed_pending p WHERE NOT EXISTS (SELECT
h.entryid from H2 h where h.entryid = p.pending_id)
If the pending entries are not processed after issuing these statements
(don't forget to commit the transaction), kill the DSO process and
armonitor should restart it.
Best regards,
Serdar Ozcan
-----Original Message-----
From: Joe Castleman [mailto:[EMAIL PROTECTED]
Sent: Friday, May 09, 2008 6:09 PM
Subject: Temporarily disable DSO?
All,
Is there a way to temporarily disable a DSO mapping, such that any
transactions on the "from" server will go into the Pending
Distributions queue and reliably flush out when DSO is again enabled?
I want to disable outbound traffic in one direction (i.e. one
mapping), but not another (i.e. another mapping to a different "to"
server). Disabling the distributed mappings causes the transactions
to simply fail, with no queueing (I know the workaround for that is to
simply export those entries where Modified Date >= the time I disabled
DSO). I also want to avoid stopping and restarting the Remedy
service.
I have tried adding a line "Disable-Client-Operation: 5" to the ar.cfg
file and then running "arsignal -c". Actually this does work, but not
in reverse - I can't seem to undo it. If I comment out the line (or
delete it) and run "arsignal -c" again, DSO is not enabled (but no
errors). (I also tried this using driver.exe and running the "sig"
command, no luck, but no errors either.) A drawback to this method -
if it worked as expected - is that it disables the entire DSO, I
really just want to stop one mapping but not another. Re-starting the
Remedy service did not clear up the queue (and again, restarting is
something I want to avoid, anyway.).
It occurred to me to try commenting-out the "DSO-Target-Connection:"
lines in ar.cfg but, as mentioned, I'm having trouble using "arsignal"
to undo the changes.
Details (both "to" and "from" servers):
ARS 6.3, p22
Help Desk 6 (with a lot of home-grown objects)
MS-SQL 2005 (9.00.3042.00)
Windows Server 2k3 R2
Thanks in advance,
Joe Castleman
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
