acq:edi_configuration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| acq:edi_configuration [2011/08/02 12:37] – formatting changes bshum | acq:edi_configuration [2013/10/01 14:29] (current) – this content now lives in official docs bshum | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== EDI Install/ | ||
| - | |||
| - | **This is a DRAFT document that will be revised as exploration continues.** | ||
| - | |||
| - | For Indiana and Bibliomation, | ||
| - | |||
| - | Starting with a fresh checkout of " | ||
| - | |||
| - | The edi translator code is found in Open-ILS/ | ||
| - | |||
| - | Next, as the root user (or a user with sudo rights) we need to install the dependencies, | ||
| - | |||
| - | Suggestion -- install.sh should probably be doing an apt-get update first too? | ||
| - | |||
| - | Now, we're ready to start " | ||
| - | |||
| - | Using the command "ps aux | grep edi" should show you something similar if the script is running properly: | ||
| - | |||
| - | <code bash> | ||
| - | root 30349 | ||
| - | </ | ||
| - | |||
| - | Also, to shutdown EDI translator you can use something like pkill (assuming no other ruby processes are running): | ||
| - | |||
| - | <code bash> | ||
| - | kill -INT $(pgrep ruby) | ||
| - | </ | ||
| - | |||
| - | The EDI translator runs on localhost and listens on port 9191 by default. | ||
| - | |||
| - | ===== EDI Scripts ===== | ||
| - | |||
| - | ==== edi_pusher.pl ==== | ||
| - | |||
| - | As opensrf, copy edi_fetcher.pl and edi_pusher.pl from Open-ILS/ | ||
| - | |||
| - | edi_pusher.pl is the script that will actually send and receive information between Evergreen and the … client? | ||
| - | |||
| - | 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: | ||
| - | |||
| - | <code bash> | ||
| - | 10 * * * * cd / | ||
| - | </ | ||
| - | |||
| - | ==== edi_fetcher.pl ==== | ||
| - | |||
| - | Also run, the edi_fetcher.pl script to pull in new incoming files for EDI accounts: | ||
| - | |||
| - | <code bash> | ||
| - | 0 1 * * * cd / | ||
| - | </ | ||
| - | |||
| - | We’re only running it once every night at 1 am while we test the edi_fetcher components. | ||
| - | |||
| - | ===== Configuring Providers and EDI Accounts ===== | ||
| - | |||
| - | ==== Providers ==== | ||
| - | |||
| - | Look in Admin > Server Administration > Acquisitions > Providers | ||
| - | |||
| - | ^ Column ^ Description/ | ||
| - | | 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) | | ||
| - | | Email | 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/ | ||
| - | |Label|A unique name to identify the provider| | ||
| - | |Host|FTP/ | ||
| - | |Username|FTP/ | ||
| - | |Password|FTP/ | ||
| - | |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. | ||
| - | |||
| - | |||
| - | ===== 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:/ | ||
| - | FTP_PASSIVE is OFF | ||
| - | |||
| - | Hook ' | ||
| - | 23 - 'PO JEDI' | ||
| - | Event definition 23 has 0 (completed) event(s) | ||
| - | |||
| - | done | ||
| - | opensrf@server:/ | ||
| - | </ | ||
| - | |||
| - | There may be errors generated that require troubleshooting. | ||
| - | |||
| - | < | ||
| - | 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. | ||
| - | |||
| - | Check this [[https:// | ||
| - | < | ||
| - | Can't locate object method " | ||
| - | </ | ||
acq/edi_configuration.1312303076.txt.gz · Last modified: 2022/02/10 13:33 (external edit)