This is an old revision of the document!
Table of Contents
EDI Install/Configuration
This is a DRAFT document that will be revised as exploration continues.
For Indiana and Bibliomation, we've chosen to run this on our "utility" server as this is where we also store things like notices, A/T event outputs, etc.
Starting with a fresh checkout of "rel_2_0" branch from the community Git (http://git.evergreen-ils.org/?p=Evergreen.git;a=tree;h=refs/heads/rel_2_0;hb=rel_2_0) as that's the version we're currently running. If you need help with checking out the latest version of the code, please see http://evergreen-ils.org/dokuwiki/doku.php?id=dev:git
The edi translator code is found in Open-ILS/src/edi_translator and I've copied it to /openils/var/edi
Next, as the root user (or a user with sudo rights) we need to install the dependencies, via "install.sh". This will perform some apt-get routines to install the code needed for the EDI translator to function. Note: subversion package must be installed.
Suggestion – install.sh should probably be doing an apt-get update first too?
Now, we're ready to start "edi_webrick.bash" which is the script that calls the "Ruby" code to translate EDI. Note: This script needs to be started in order for EDI to function so please take appropriate measures to ensure this starts following reboots/upgrades/etc.
Using the command "ps aux | grep edi" should show you something similar if the script is running properly:
root 30349 0.8 0.1 52620 10824 pts/0 S 13:04 0:00 ruby ./edi_webrick.rb
Also, to shutdown EDI translator you can use something like pkill (assuming no other ruby processes are running):
kill -INT $(pgrep ruby)
The EDI translator runs on localhost and listens on port 9191 by default. This is controlled via the edi_webrick.cnf file located in the edi_translator directory.
EDI Scripts
edi_pusher.pl
As opensrf, copy edi_fetcher.pl and edi_pusher.pl from Open-ILS/src/support-scripts into /openils/bin
edi_pusher.pl is the script that will actually send and receive information between Evergreen and the … client? ordering agency?
Run edi_pusher.pl script regularly to push EDI messages out. This is best configured as a cronjob… for example, this command will run edi_pusher.pl 10 minutes past the hour, every hour:
10 * * * * cd /openils/bin && /usr/bin/perl ./edi_pusher.pl > /dev/null
edi_fetcher.pl
Also run, the edi_fetcher.pl script to pull in new incoming files for EDI accounts:
0 1 * * * cd /openils/bin && /usr/bin/perl ./edi_fetcher.pl > /dev/null
We’re only running it once every night at 1 am while we test the edi_fetcher components. Perhaps this needs to run more regularly depending on the response time of the vendors.
Configuring Providers and EDI Accounts
Providers
Look in Admin > Server Administration > Acquisitions > Providers
| Column | Description/Notes |
|---|---|
| Provider Name | A unique name to identify the provider |
| Code | A unique code to identify the provider |
| Owner | The org unit who will “own” the provider. |
| Currency | The currency format the provider accepts |
| Active | Whether or not the Provider is “active” for use |
| Default Claim Policy | ?? |
| EDI Default | The default “EDI Account” to use (see EDI Accounts Configuration) |
| The email address for the provider | |
| Fax Phone | A fax number for the provider |
| Holdings Tag | The holdings tag to be utilized (usually 852, for Evergreen) |
| Phone | A phone number for the provider |
| Prepayment Required | Whether or not prepayment is required |
| SAN | The vendor provided, org unit specific SAN code |
| URL | The vendor website |
EDI Accounts
Look in Admin > Server Administration > Acquisitions > EDI Accounts
| Column | Description/Notes |
|---|---|
| Label | A unique name to identify the provider |
| Host | FTP/SFTP/SSH hostname – vendor assigned |
| Username | FTP/SFTP/SSH username – vendor assigned |
| Password | FTP/SFTP/SSH password – vendor assigned |
| Account | Vendor assigned account number associated with your organization |
| Owner | The organizational unit who owns the EDI account |
| Last Activity | The date of last activity for the account |
| Provider | This is a link to one of the “codes” in the “Providers” interface |
| Path | The path on the vendor’s server where Evergreen will send it’s outgoing .epo files |
| Incoming Directory | The path on the vendor’s server where “incoming” .epo files are stored |
| Vendor Account Number | Vendor assigned account number. |
| Vendor Assigned Code | Usually a sub-account designation. Can be used with or without the Vendor Account Number. |
Configuring Organizational Unit SAN code
Currently, there is no interface to configure this. You must manually set the actor.org_unit.san row for each org unit’s mailing address entry. This is a REQUIRED field to properly envelope the JEDI message for the provider.
Some Troubleshooting Notes
If running edi_pusher.pl manually, you should see something like this when there are no POs that are awaiting translation:
opensrf@server:/openils/bin$ ./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 opensrf@server:/openils/bin$
There may be errors generated that require troubleshooting. For example, an error like this:
ERROR: attempt_translation failed for event 573913, PO 132, template_output 207516
This means you should check the data field from action_trigger.event_output with an ID of 207516. There must be something wrong with the data contained within. Potential problem source may be bad character strings or line breaks in the PO generation itself. See bug ticket where title with quotes fails to properly translate.
Check this bug ticket, if you see this error:
Can't locate object method "is_dir" via package "Net::FTP" at /openils/lib/perl5/OpenILS/Utils/RemoteAccount.pm line 614.