PeopleSoft Driver: stop endless events in publisher channel


Hi All,

I have configured a Peoplesoft driver (IDM 4.5). I have connected it
with a PeopleSoft Endpoint, which has lots of data in transaction CI.
Is there any configuration change can be done in driver property not to
allow any historical events? I also noticed that the driver cache has no
data, keeping the driver stop. Now it is 3 days the driver is running
like this. How can I stop this?

Thanks,
Raktim


--
Thanks,
Raktim Banerjee
Enterprise Risk and Security Services (ERSS)
------------------------------------------------------------------------
raktimb's Profile: https://forums.netiq.com/member.php?userid=4402
View this thread: https://forums.netiq.com/showthread.php?t=55300

  • raktimb wrote:

    > I have configured a Peoplesoft driver (IDM 4.5). I have connected it
    > with a PeopleSoft Endpoint, which has lots of data in transaction CI.
    > Is there any configuration change can be done in driver property not
    > to allow any historical events? I also noticed that the driver cache
    > has no data, keeping the driver stop. Now it is 3 days the driver is
    > running like this. How can I stop this?


    I don't belive there is a driver config for this.

    1. did you by any chance initiate a resync when you first started the
    driver? This is an option under driver startup type.

    2. Can you post a santitized level 3 trace?

    We can probably help with a veto rule that can veto data which is
    historical as early as possible in the transaction.
  • On 2/3/2016 6:49 AM, raktimb wrote:
    >
    > Hi All,
    >
    > I have configured a Peoplesoft driver (IDM 4.5). I have connected it
    > with a PeopleSoft Endpoint, which has lots of data in transaction CI.
    > Is there any configuration change can be done in driver property not to
    > allow any historical events? I also noticed that the driver cache has no
    > data, keeping the driver stop. Now it is 3 days the driver is running
    > like this. How can I stop this?
    >
    > Thanks,
    > Raktim
    >
    >


    If the trans01 event log is full of events and you don't need them to flow, your DBA can just truncate that table and the
    events will stop. I would suggest having the driver stopped when you do that however.
    This is a destructive event so make sure that you don't actually need the events.
    Worst case scenario however you can just have the DBA enter new events into that table.

    --
    -----------------------------------------------------------------------
    Will Schneider
    Knowledge Partner http://forums.netiq.com

    If you find this post helpful, please click on the star below.
  • On Wed, 03 Feb 2016 12:49:59 0000, raktimb wrote:

    > Hi All,
    >
    > I have configured a Peoplesoft driver (IDM 4.5). I have connected it
    > with a PeopleSoft Endpoint, which has lots of data in transaction CI. Is
    > there any configuration change can be done in driver property not to
    > allow any historical events? I also noticed that the driver cache has no
    > data, keeping the driver stop. Now it is 3 days the driver is running
    > like this. How can I stop this?


    Are these events being published because they're supposed to happen? If
    they're in the dirxml_trans01 table, they may be there for a reason. If
    you don't want them, change the status on the event(s) from "available"
    to "success" or "error" or maybe "warning", so the shim won't try to pick
    them up.


    --
    --------------------------------------------------------------------------
    David Gersic dgersic_@_niu.edu
    Knowledge Partner http://forums.microfocus.com

    Please post questions in the forums. No support provided via email.
    If you find this post helpful, please click on the star below.