1 = Hatch Install Documentation =
3 This documentation assumes Windows users will use the Hatch Windows
4 installer. The xref:linux[Linux]-only steps can also be done on Windows
5 from a source checkout but are not documented here.
11 Windows only requires a JRE to run Hatch, not a full JDK. Download and
12 install JRE version 1.8 or higher from (for example)
13 http://java.com/[java.com].
17 Execute the 'Hatch-Installer-(version).exe' executable.
19 NOTE: See installer/windows/README.adoc for building the Windows
20 installer from Linux or Windows. When building the Windows installer
21 on Windows a full JDK is required for compiling.
23 ==== Optional: Test Hatch ====
26 -------------------------------------------------------------------------
27 C:\>cd %ProgramFiles(x86)%\Hatch
28 C:\Program Files (x86)\Hatch>hatch.bat test
29 -------------------------------------------------------------------------
31 === Install Chrome Extension ===
33 If the extension was not installed automatically when installing Hatch you can get it directly in the browser from the
34 https://chrome.google.com/webstore/detail/hatch-native-messenger/ppooibdipmklfichpmkcgplfgdplgahl[Chrome App Store].
36 === Install Firefox Extension ===
38 The Firefox extension can not be installed automatically by the native application installer;
39 https://addons.mozilla.org/en-US/firefox/addon/hatch-native-messenger/[it is available on the Firefox Addons site].
41 === Continue with xref:using-hatch[Using Hatch] ===
51 -------------------------------------------------------------------------
52 # Debian/Ubuntu version
53 $ sudo apt-get install openjdk-8-jdk openjfx
54 -------------------------------------------------------------------------
59 -------------------------------------------------------------------------
61 -------------------------------------------------------------------------
64 === Configure Native Messaging ===
66 Edit extension/host/org.evergreen_ils.hatch.(chrome|firefox).json and change the "path"
67 value to match the location of your copy of "hatch.sh", found in the root
68 directory of the Hatch repository.
70 Copy the correct host file, changing the filename to org.evergreen_ils.hatch.json, into the browser's configuration directory.
75 -------------------------------------------------------------------------
76 $ mkdir -p ~/.config/google-chrome/NativeMessagingHosts/
77 $ cp extension/host/org.evergreen_ils.hatch.chrome.json ~/.config/google-chrome/NativeMessagingHosts/org.evergreen_ils.hatch.json
78 -------------------------------------------------------------------------
83 -------------------------------------------------------------------------
84 $ mkdir -p ~/.config/chromium/NativeMessagingHosts/
85 $ cp extension/host/org.evergreen_ils.hatch.chrome.json ~/.config/chromium/NativeMessagingHosts/org.evergreen_ils.hatch.json
86 -------------------------------------------------------------------------
91 -------------------------------------------------------------------------
92 $ mkdir -p ~/.mozilla/native-messaging-hosts/
93 $ cp extension/host/org.evergreen_ils.hatch.firefox.json ~/.mozilla/native-messaging-hosts/org.evergreen_ils.hatch.json
94 -------------------------------------------------------------------------
96 === Install Chrome Extension ===
98 Install the Chrome exenstion directly from the
99 https://chrome.google.com/webstore/detail/hatch-native-messenger/ppooibdipmklfichpmkcgplfgdplgahl[Chrome App Store].
101 === Install Firefox Extension ===
103 Install the Firefox extension from the
104 https://addons.mozilla.org/en-US/firefox/addon/hatch-native-messenger/[Firefox Addons site].
107 ==== Optional: Test Hatch ====
109 NOTE: print commands are disabled by default in the tests to avoid
110 unexpected printing but they can be added by un-commenting
111 them in src/org/evergreen_ils/hatch/TestHatch.java and recompiling.
114 -------------------------------------------------------------------------
115 $ mkdir -p ~/.evergreen
117 -------------------------------------------------------------------------
124 * In Chrome, navigate to the browser staff URL (https://HOSTNAME/eg/staff/).
125 * Open the Javascript console. It should show messages like:
128 -------------------------------------------------------------------------
129 Loading Hatch relay content script
131 sending to Hatch: {"key":"eg.workstation.all","action":"get","msgid":1}
133 Hatch responded to message ID 1
134 -------------------------------------------------------------------------
136 * Enable Hatch features by navigating to
137 https://HOSTNAME/eg/staff/admin/workstation/hatch.
138 * To determine if Hatch can see your printer(s), navigate to
139 https://HOSTNAME/eg/staff/admin/workstation/print/config
140 ** The "Select Printer" drop-down should show your printer(s).
141 ** The various printer attribute selectors should show values supported
142 by the selected printer.
144 === Optional: Debugging The Chrome Extension ===
146 * Navigate to chrome://extensions
147 * Enable "Developer Mode" along the top right of the page.
148 * Click the "Background Page" link to see the exension console.
149 * When the extension is loaded (or reloaded), it should show
150 "Connecting to native messaging host: org.evergreen_ils.hatch"
151 in the Background Page console with no errors.
152 * Use the "Reload" link to apply local changes made to the
153 extension (e.g. extension.js). (This might only work when installing
154 the exention manually via developer mode tools).
155 * See also https://developer.chrome.com/extensions/getstarted