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 [2012/02/08 11:53] – [Some Troubleshooting Notes] tspindler | 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.** | ||
- | |||
- | ===== Install EDI Translator ===== | ||
- | |||
- | For Indiana and Bibliomation, | ||
- | |||
- | One may start with a fresh checkout of " | ||
- | |||
- | - As the opensrf user, copy the EDI Translator code found in Open-ILS/ | ||
- | cp -r Open-ILS/ | ||
- | </ | ||
- | - Navigate to where you have saved the code to begin next step.< | ||
- | cd / | ||
- | </ | ||
- | - Next, as the root user (or a user with sudo rights) we need to install the dependencies, | ||
- | ./ | ||
- | </ | ||
- | - 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 | ||
- | </ | ||
- | |||
- | 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 | ||
- | | 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 | ||
- | | Active | ||
- | | Default Claim Policy | ?? | | ||
- | | EDI Default | ||
- | | 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 | ||
- | | SAN | The vendor provided, org unit specific SAN code | | ||
- | | URL | The vendor website | ||
- | |||
- | ==== EDI Accounts ==== | ||
- | |||
- | Look in Admin > Server Administration > Acquisitions > EDI Accounts | ||
- | |||
- | ^ Column | ||
- | | Label | A unique name to identify the provider | ||
- | | Host | FTP/ | ||
- | | Username | ||
- | | Password | ||
- | | Account | ||
- | | Owner | The organizational unit who owns the EDI account | ||
- | | Last Activity | ||
- | | Provider | ||
- | | Path | The path on the vendor’s server where Evergreen will send it’s outgoing .epo files | | ||
- | | Incoming Directory | ||
- | | 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 ===== | ||
- | |||
- | The admin > Server Settings > Organizational Units interface allows a library to configure their SAN, along side their address, phone, etc. | ||
- | |||
- | ===== Some Troubleshooting Notes ===== | ||
- | |||
- | === Potential Error Messages === | ||
- | |||
- | 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 " | ||
- | </ | ||
- | |||
- | === PO JEDI Template Issues === | ||
- | |||
- | Some libraries may also run into issues with the action/ | ||
- | |||
- | Original template has: | ||
- | |||
- | < | ||
- | [% | ||
- | {" | ||
- | [%- ELSIF target.provider.edi_default.vendcode && target.provider.code == ' | ||
- | {" | ||
- | {" | ||
- | [%- ELSE -%] | ||
- | {" | ||
- | [%- END -%] | ||
- | ], | ||
- | </ | ||
- | |||
- | modified has the following where it matches on Provide SAN instead of code. More testing should be done but it seems to be working. | ||
- | < | ||
- | [% | ||
- | {" | ||
- | {" | ||
- | [%- ELSIF target.provider.edi_default.vendcode && (target.provider.san == ' | ||
- | {" | ||
- | {" | ||
- | [%- ELSE -%] | ||
- | {" | ||
- | [%- END -%] | ||
- | ], | ||
- | |||
- | |||
- | </ |
acq/edi_configuration.1328720015.txt.gz · Last modified: 2022/02/10 13:33 (external edit)