[OPEN-ILS-GENERAL] EDI Help (part 2)

[Patrick Gardella]

That did it!  Thanks for the help.

Patrick


On Tue, Oct 1, 2013 at 3:32 PM, Ben Shum <ben at evergreener.net> wrote:

> Hi Patrick,
>
> Since it's marked "pending" state, now I'm wondering if maybe you need to
> have the action_trigger_runner.pl script going as well to actually
> translate events using the PO JEDI template.
>
> In our utility server, the action/trigger runner goes off every quarter
> hour, and then we have edi_pusher.pl set to run once per hour at 10 after
> the hour.  So presumably, the action/trigger runner has enough time to
> process things out prior to each push action.
>
> -- Ben
>
>
> On Tue, Oct 1, 2013 at 3:26 PM, Patrick Gardella <
> patrick.gardella at asburyseminary.edu> wrote:
>
>> Thanks for the response, Ben!
>>
>> EDI messages were blank for each of the POs until I did the manual
>> trigger for the two recent POs.  It always showed (0) for EDI Messages in
>> the client and had nothing in the DB. So right now, I have two messages in
>> the edi_messages table.
>>
>> All of the action_trigger.event records with an event_def of 23 are
>> "pending":
>> 6732
>> 424
>> 23
>>  2013-09-26 17:37:11.76534+002013-09-26 17:37:11+00*NULL**NULL* *NULL**
>> NULL*pending*NULL**NULL* *NULL**NULL*
>> So it seems to me that the event never fires.
>>
>> Patrick
>>
>>
>> On Tue, Oct 1, 2013 at 3:07 PM, Ben Shum <ben at evergreener.net> wrote:
>>
>>> Hi Patrick,
>>>
>>> Have you checked the EDI messages to see if it generated anything?
>>> It's possible that there was an error or issue with the order
>>> processing as generated based on the PO JEDI and it's just stuck on
>>> that.  Alternatively, one could check the action_trigger.event table
>>> in the database and see if the associated EDI generated message failed
>>> to create with a proper template as well.  Presumably, they would have
>>> an associated event_def of 23 (which seems to be the ID for your PO
>>> JEDI action trigger template).
>>>
>>> In my system, on B&T orders handled with EDI, I can see that there are
>>> listed EDI messages associated with the PO.  Clicking on that link
>>> takes me to view the messages as processed.  I would expect multiple
>>> messages normally, one when using edi_pusher.pl to send the content on
>>> its way, and then later messages with edi_fetcher.pl when retrieving
>>> back the processed files on B&T's end of things via the FTP.
>>>
>>> -- Ben
>>>
>>> On Fri, Sep 27, 2013 at 4:00 PM, Patrick Gardella
>>> <patrick.gardella at asburyseminary.edu> wrote:
>>> > Back in July, Rob asked for assistance in setting up EDI to BT and YBP.
>>> >
>>> http://thread.gmane.org/gmane.education.libraries.open-ils.general/8465/focus=8470
>>> >
>>> > As he said there, we believe we have it set up correctly.  We can FTP
>>> into
>>> > the ftp servers for BT using the credentials configured in the EDI
>>> Accounts.
>>> > Those same EDI Accounts are then referenced in the Providers list (EDI
>>> > Default filed).
>>> >
>>> > We created a PO for one book as a test to BT, but there is absolutely
>>> no
>>> > indication the file was actually sent to BT. No messages show up in
>>> the PO.
>>> > Ditto for the YBP one, but I want to focus on just one of these for
>>> now.
>>> >
>>> > The PO has been activated as well.
>>> >
>>> > edi_pusher.pl is set to run every 10 minutes.  When run by hand, it
>>> shows:
>>> >
>>> > opensrf at evergreen:/openils/var/log$ cd /openils/bin && /usr/bin/perl
>>> > ./edi_pusher.pl
>>> > FTP_PASSIVE is OFF
>>> >
>>> > Hook 'acqpo.activated' is used in 1 event definition(s):
>>> >  23 - 'PO JEDI'
>>> > Event definition 23 has 0 (completed) event(s)
>>> >
>>> > done
>>> >
>>> > We're running Evergreen 2.4.2.
>>> >
>>> > Can anyone offer any suggestions on what might be going on?  Is there
>>> > something we need to do to make the order actually transmit?  Or some
>>> log we
>>> > can look in to figure out what is happening with this order?
>>> >
>>> > Patrick Gardella
>>> > Asbury Theological Seminary
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20131004/e5652796/attachment-0001.htm>