NOTE: These instructions are also available in the Evergreen documentation at http://docs.evergreen-ils.org/1.6/draft/html/staffclientinstallation.html. In github: http://github.com/rsoulliere/Evergreen-DocBook/blob/master/1.6/admin/staffclientinstallation.xml.
The staff client is available for download from the downloads section on the Open-ILS website at http://www.evergreen-ils.org/downloads.php. Download the staff client installer, and run it. A screen will appear that looks similar to this:
Click the Next button to continue through the guided install process. The install wizard will ask you to agree to the end-user license, ask you where to install the software, ask about where to place icons, and then will install the software on your workstation.
When you run the staff client for the first time, a screen similar to this will appear:
First, configure the server you would like to connect to in the Server section. After selecting a server, click the Re-Test Server button.
Because this is the initial run of the staff client, the Workstation section in the upper-right states: Not yet configured for the specified server. The first thing that must be done to every workstation is to assign it a workstation name. This is covered in the Workstation Names section of the documentation.
When you run the staff client installer, a screen will appear that looks similar to this:
Click continue, accept the license, then finish the installation. The application will be located at the destination you selected during installation. You will then be able to drag the application into your toolbar for easier access.
Install recommended XULRunner Version
Evergreen 1.6.x.x - XULRunner 1.9
*Note: If you have issues removing previously installed XULRunner versions see after this entry.
The staff client data from the ./staff_client/build directory must be placed somewhere on the machine (e.g. ~/Desktop/Evergreen_Staff_Client). Need to clarify “./staff_client/build directory”
XULRunner must be called via the full path to the binary, followed by the install command and the path to the client data.
/Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/Evergreen_Staff_Client
This command should exit quietly.
A folder named OpenILS under /Applications, with a launcher named open_ils_staff_client, will be created.
If you already have a newer version installed, per the release notes, you'll need to remove the entire /Library/Frameworks/XUL.framework directory before downgrading.
In addition, you may also need to remove the previous xulrunner-ver-mak.pkg file from /Library/Receipts/
If there is no xulrunner-ver-mak.pkg file in /Library/Receipts/ (possibly in newer OSX releases) we need flush receiptdb file.
*Note: If we install a newer version over a previous (older) install the older one is not removed but the symlinks get changed to the newer one.
Flush Receiptdb file:
First we get the package identifier:
sudo pkgutil --pkgs > /tmp/pkgs.txt
Since I wanted to purge/forget the build that was initially installed:
sudo pkgutil --forget org.mozilla.xulrunner
Note: At first I thought after deleting the folder XUL.framework I had to also edit InstallHistory.plist in /Library/Receipts but that does not seem necessary.
mkdir -p Evergreen.app/Contents/Frameworks mkdir -p Evergreen.app/Contents/Resources mkdir -p Evergreen.app/Contents/MacOS
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleExecutable</key> <string>xulrunner</string> <key>CFBundleGetInfoString</key> <string>OpenILS open_ils_staff_client rel_1_6_0_0</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>Evergreen Staff Client</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>rel_1_6_0_0</string> <key>CFBundleVersion</key> <string>rel_1_6_0_0.rel_1_6_0_0</string> <key>NSAppleScriptEnabled</key> <true/> <key>CFBundleTypeIconFile</key> <string>Evergreen.icns</string> <key>CFBundleIdentifier</key> <string>org.evergreen-ils.Evergreen</string> </dict> </plist>
A Linux staff client is built on the server as part of the initial installation of Evergreen. To upgrade the client copy the folder containing the new client on to your workstation from the server.
cd ~/ILS/Open-ILS/xul/staff_client scp -r build firstname.lastname@example.org:~/eg-client-x.x.x.x/
It can be run from the build directory by:
A Linux staff client is built on the server as part of the initial installation of Evergreen, using the following steps:
cd ~/ILS/Open-ILS/xul/staff_client make STAFF_CLIENT_BUILD_ID='12345' mkdir /openils/var/web/xul/ mkdir /openils/var/web/xul/12345/ cd build/ cp -R server/ /openils/var/web/xul/12345/
It can be run from the build directory by:
In order to install a compatible staff client on another Linux machine, you can copy the applicable files from the server to that Linux machine, or even build it from scratch on that machine. Just be sure the Build ID you chose on the server (12345 in this example) matches the Build ID for each staff client you use on other machines.
If you will be using a pre-packaged Windows version on some computers as well, you may want to choose your Build ID on both server and other versions to match that of the Windows staff client. You can determine what Build ID has been used for existing installations of the staff client by clicking the “About this Client” button.
An alternative option if you have access to make changes to the Evergreen server is to create a symbolic link. In order for a copy of the staff client and server to work together, the Build ID (shown when you click “About this Client”) of the client, must match the name of the directory containing the server components of the staff client or the name of a symbolic link to that directory.
cd /openils/var/web/xul sudo ln -s server_build_id/ client_build_id
This section is more toward an end-user who may wish to use Linux rather than Windows for client machines, but has limited Linux experience. The Staff Client can be built on Linux without installing the Evergreen Server component; this is a relatively simple process, compared to server installation, though does require some command-line work. The following directions are for building Staff Client version 184.108.40.206 on Kubuntu 7.10, so you may need to modify them for other distributions (these instructions should work as-is for Ubuntu or Ubuntu derivatives).
Using apt-get to acquire these:
sudo apt-get install subversion sudo apt-get install xulrunner
Synaptic can also be used; search for subversion and select the latest version, and search for xulrunner and select version 220.127.116.11-2ubuntu5.
For most end-users, a specific version is required to communicate properly with the Evergreen server. Check with your system admin, IT person, or HelpDesk to determine which Staff Client versions are supported.
Next, you'll need to determine which tag to use when downloading the source code. Tags are markers in the source code to create a snapshot of the code as it existed at a certain time; tags usually point to tested and stable code, or at least a community-recognized release version.
To determine which tag to use, browse to http://git.evergreen-ils.org/?p=Evergreen.git;a=summary. The summary page includes a list of tags and branches. Depending on whether a release was made before or after the project moved to Git, select either the Git tag or the branch converted from an SVN release tag (e.g., tags/rel_1_2_1_4.)
Now, open a terminal (command-line prompt) and navigate to the directory in which you wish to download the staff client. Navigate to the desired directory and use the following command to download the proper version of the source code by tag:
git clone git://git.evergreen-ils.org/Evergreen.git git checkout -b tmp_branch origin/rel_1_2_1 # or git checkout rel_1_2_1
Note that you'll want to change “rel_1_2_1_4” to the appropriate tag for your installation.
From the command line, navigate to the directory in which you downloaded the source code. Then, navigate to the proper subdirectory:
Now, we'll run the “make” script to actually build the Staff Client files. Be sure to check wtih your sysadmin about which “Staff Client Build ID” to use; the server checks the Staff Client Build ID against itself to determine whether or not a connecting client is supported. For the PINES installation at 18.104.22.168, the supported build id is “rel_1_2_1_4”. Modify the following command accordingly:
The 1.4 series of Evergreen has complicated the build process for staff clients a bit. If you downloaded a .tar.gz (tarball) of Evergreen, then your steps will resemble:
wget http://evergreen-ils.org/downloads/Evergreen-ILS-22.214.171.124.tar.gz tar xfz Evergreen-ILS-126.96.36.199.tar.gz cd Evergreen-ILS-188.8.131.52/ ./configure --prefix=/openils --sysconfdir=/openils/conf cd Open-ILS/xul/staff_client/ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install
If you're installing from a Subversion checkout:
git clone git://git.evergreen-ils.org/Evergreen.git git checkout rel_1_4_0_4 ./autogen.sh # If you downloaded a .tar.gz of Evergreen, you may skip this step ./configure --prefix=/openils --sysconfdir=/openils/conf cd Open-ILS/xul/staff_client/ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install
Navigate to the 'build' subdirectory, then run the following command:
Make sure you run this from 'build\', not from 'staff_client\'.
The source code download included many files that are needed to build the Staff Client, but not necessary to run it. You may wish to remove them to save space, or to create a directory containing the built staff client that can be copied to other machines.\ To do this, first create the directory where you wish to place your 'finished' staff client:
mkdir ~/<Destination Directory>
Then, copy the 'staff_client' directory to it:
cd ~/<Download Directory>/Open-ILS/xul/ cp -r staff_client ~/<Destination Directory>
Test to verify that all the necessary files were moved to the destination directory:
cd ~/<Destination Directory>/staff_client/build xulrunner application.ini
The Staff Client should run properly. Now remove the original download directory and all sub directories:
rm -r -f ~/<Download Directory>
Almost done! Now, the command
xulrunner ~/<Destination Directory>/staff_client/build/application.ini
will run the Staff Client. You may wish to create Desktop/Start Menu/K-Menu shortcuts for the Staff Client. To do so, use the previous command as the target.
Wine is also an alternative for those who want to install the packaged Windows versions rather than building the Staff Client manually. Wine is application that allows Linux users to run Windows executables, and is a simple way for casual Linux users to use the Evergreen Staff Client.
1: Install Wine (using apt-get):
command-prompt:~/sudo apt-get install wine
Here is more information about installing Wine: http://www.winehq.org/site/docs/wineusr-guide/getting-wine
2) Download the proper EG Staff Client installer from the open-ils.org website and put it in a directory you like:
command-prompt:~/cd directory/of/choice command-prompt:~/wget http://open-ils.org/downloads/evergreen-setup-rel_version-number.exe
3) In the GUI, navigate to the file where you downloaded the setup file and run it; this will install the SC. If this fails, you may need to configure Wine first to emulate Windows XP.
To do so, type “winecfg” from the command line; in the “Applications” tab of the window that pops up, select “Default Settings” and choose “Windows XP” from the drop-down menu and click “Apply”.
4) To launch the Evergreen Staff Client, go to the All Applications menu, select “Wine→Program Files→Evergreen Staff Client→Evergreen Staff Client”, or launch from the desktop shortcut.
The Evergreen Staff Client can use an SSH tunnel as a SOCKS 5 proxy. For more details, see configuring_a_proxy_for_the_staff_client.