From feffd3eb9fa0b25933e6e8889b5c9d337692fa3f Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Fri, 1 Oct 2010 13:25:00 -0400 Subject: [PATCH] rework the section/subsection scheme to compress the TOC; --- 1.6/admin/StaffclientInstallation.xml | 1276 +++++++++++++++++---------------- 1 file changed, 642 insertions(+), 634 deletions(-) diff --git a/1.6/admin/StaffclientInstallation.xml b/1.6/admin/StaffclientInstallation.xml index a66da53d64..afedd07558 100644 --- a/1.6/admin/StaffclientInstallation.xml +++ b/1.6/admin/StaffclientInstallation.xml @@ -1,144 +1,148 @@ -
- Installing a Pre-Built Staff Client - You can install the Staff Client from pre-built images and packages without actually having to first build it. Pre-built packages are currently available for Windows, MAC OS X, and Linux. If you need to manually build the Staff Client, see the section "Manually Building the Staff Client". - - Installing on Windows - A standard Microsoft Windows installer that contains the current version of the Staff Client is available from the downloads section of the Evergreen website at http://www.evergreen-ils.org/downloads.php. Download the staff client installer, then run it. A screen that looks similar to this should appear: -
- Running the Staff Client installer - - - - - -
- 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 should appear: -
- Running the Staff Client for the first time - - - - - -
- First, configure the server you would like to connect to in the Server section. For example, the PINES demo system is demo.gapines.org. 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 the Staff Client on every workstation is to assign it a workstation name. This is covered in the section "Assigning Workstation Names". - - - Installing on Mac OS X - A Mac package that contains the current version of the Staff Client is available for use with XULRunner. -
- Evergreen Indiana Pkg file [Evergreen v1.2.3.0] - - Download and install the latest version of XULRunner for Mac OS. Release notes for the latest version can be found here: http://developer.mozilla.org/en/docs/XULRunner_1.8.0.4_Release_Notes. Note, later versions may not work correctly. - Download and install the Mac Installation package for the 1_2_3_0 Version Staff Client from http://evergreen.lib.in.us/opac/extras/files/evergreen_osx_staff_client_1_2_3.zip. - To upgrade to a more recent version of the staff client, you can copy the "build" directory from a working Windows installation of the desired version of the staff client to your Mac. The required files may be located in a directory like this on the Windows machine: C:\Program Files\Evergreen Staff Client\build. Copy these files into the "Resources" folder within the Open-ILS package in your Applications directory on the Mac, overwriting files with the same names. - Drag the application's icon into your toolbar for easier access. - - - When you run the staff client installer, a screen will appear that looks similar to this: +
+ Installing the Staff Client + The Staff Client is automatically built by default as part of the normal make install process for Evergreen server-side software. See the section to review details related to building the Staff Client in the final compile/link/install phase of the default Evergreen build process. See the section for help on manually building the Staff Client. Otherwise, continue with the following sections to install a pre-built Staff Client. + + Installing a Pre-Built Staff Client + You can install the Staff Client from pre-built images and packages without actually having to first build it. Pre-built packages are currently available for Windows, MAC OS X, and Linux. If you need to manually build the Staff Client, see the section . + + Installing on Windows + A standard Microsoft Windows installer that contains the current version of the Staff Client is available from the downloads section of the Evergreen website at http://www.evergreen-ils.org/downloads.php. Download the staff client installer, then run it. A screen that looks similar to this should appear:
Running the Staff Client installer - +
- FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif - 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. + 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 should appear:
- Finishing the installation + Running the Staff Client for the first time - +
- FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif -
-
- Running directly using XULRunner - You must install an apropriate version of XULRunner to match the Evergreen version. See the following table for the recommended version of XULRunner: - - Evergreen / XULRunner Dependencies - - - - - - Evergreen 1.6.x.x - XULrunner 1.9 - - - Evergreen 1.4.x.x - XULrunner 1.8.0.4 or XULrunner 1.8.0.3 - - - Evergreen 1.2.x.x - XULrunner 1.8.0.4 or XULrunner 1.8.0.3 - - - -
- If you have issues removing previously installed XULRunner versions see the next section on removing previous XULRunner versions. - The staff client data from the ./staff_client/build directory must be placed somewhere on the machine (e.g. ~/Desktop/Evergreen_Staff_Client). Remember to call XULRunner with the full path to the binary, followed by the install command and the path to the client data. See the following command: -
- Executing XULRunner - + First, configure the server you would like to connect to in the Server section. For example, the PINES demo system is demo.gapines.org. 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 the Staff Client on every workstation is to assign it a workstation name. This is covered in the section . + + + Installing on Mac OS X + A Mac package that contains the current version of the Staff Client is available for use with XULRunner. + + + Evergreen Indiana Pkg file [Evergreen v1.2.3.0] + + Download and install the latest version of XULRunner for Mac OS. Release notes for the latest version can be found here: http://developer.mozilla.org/en/docs/XULRunner_1.8.0.4_Release_Notes. Note, later versions may not work correctly. + Download and install the Mac Installation package for the 1_2_3_0 Version Staff Client from http://evergreen.lib.in.us/opac/extras/files/evergreen_osx_staff_client_1_2_3.zip. + To upgrade to a more recent version of the staff client, you can copy the "build" directory from a working Windows installation of the desired version of the staff client to your Mac. The required files may be located in a directory like this on the Windows machine: C:\Program Files\Evergreen Staff Client\build. Copy these files into the "Resources" folder within the Open-ILS package in your Applications directory on the Mac, overwriting files with the same names. + Drag the application's icon into your toolbar for easier access. + + + When you run the staff client installer, a screen will appear that looks similar to this: +
+ Running the Staff Client installer + + + + + +
+ FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif + 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. +
+ Finishing the installation + + + + + +
+ FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif + + + Running directly using XULRunner + You must install an apropriate version of XULRunner to match the Evergreen version. See the following table for the recommended version of XULRunner: + + Evergreen / XULRunner Dependencies + + + + + + Evergreen 1.6.x.x + XULrunner 1.9 + + + Evergreen 1.4.x.x + XULrunner 1.8.0.4 or XULrunner 1.8.0.3 + + + Evergreen 1.2.x.x + XULrunner 1.8.0.4 or XULrunner 1.8.0.3 + + + +
+ If you have issues removing previously installed XULRunner versions see for information on removing previous XULRunner versions. + The staff client data from the ./staff_client/build directory must be placed somewhere on the machine (e.g. ~/Desktop/Evergreen_Staff_Client). Remember to call XULRunner with the full path to the binary, followed by the install command and the path to the client data. See the following command: +
+ Executing XULRunner + /Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/Evergreen_Staff_Client -
- This command should exit quietly. A folder will be created, named /Applications/OpenILS, containing a launcher named open_ils_staff_client. -
-
- Removing previously installed XULRunner versions - If you already have a newer version installed, per the release notes, you will need to remove the entire directory /Library/Frameworks/XUL.framework before downgrading. - In addition, you may also need to remove the previous file /Library/Receipts/xulrunner-ver-mak.pkg. - If there is no file /Library/Receipts/xulrunner-ver-mak.pkg (possibly in newer OSX releases) you need to flush the receiptdb file. - If you install a newer version over a previous (older) install, the older one is not removed but the symlinks get changed to the newer one. - First, get the package identifier, then purge/forget the build that was initially installed: -
- Purging previous build - +
+ This command should exit quietly. A folder will be created, named /Applications/OpenILS, containing a launcher named open_ils_staff_client. + + + Removing previously installed XULRunner versions + If you already have a newer version installed, per the release notes, you will need to remove the entire directory /Library/Frameworks/XUL.framework before downgrading. + In addition, you may also need to remove the previous file /Library/Receipts/xulrunner-ver-mak.pkg. + If there is no file /Library/Receipts/xulrunner-ver-mak.pkg (possibly in newer OSX releases) you need to flush the receiptdb file. + If you install a newer version over a previous (older) install, the older one is not removed but the symlinks get changed to the newer one. + First, get the package identifier, then purge/forget the build that was initially installed: +
+ Purging previous build + sudo pkgutil --pkgs > /tmp/pkgs.txt sudo pkgutil --forget org.mozilla.xulrunner -
- It may not be necessary to edit the file /Library/Receipts/InstallHistory.plist after deleting the folder XUL.framework. -
-
- Creating an APP file: Staff Client & XULRunner Bundled - An APP file is basically a folder. Start with a folder stucture like this: -
- Sample APP file folder structure - +
+ It may not be necessary to edit the file /Library/Receipts/InstallHistory.plist after deleting the folder XUL.framework. + + + Creating an APP file: Staff Client & XULRunner Bundled + An APP file is basically a folder. Start with a folder stucture like this: +
+ Sample APP file folder structure + * Evergreen.app * Contents * Frameworks * Resources * MacOS -
- Create an APP folder structure with the following commands: -
- Creating a folder structure - +
+ Create an APP folder structure with the following commands: +
+ Creating a folder structure + mkdir -p Evergreen.app/Contents/Frameworks mkdir -p Evergreen.app/Contents/Resources mkdir -p Evergreen.app/Contents/MacOS -
- - - - Create a new file in the folder Evergreen.app/Contents/Info.plist containing the following data (adjust for your version of Evergreen): -
- Creating a new file - +
+ + + + Create a new file in the folder Evergreen.app/Contents/Info.plist containing the following data (adjust for your version of Evergreen): +
+ Creating a new file + <?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"> @@ -164,14 +168,14 @@ </dict> </plist> -
- - Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (see above for recommendations). - - Make a copy of /Library/Frameworks/XUL.Framework inside your APP file. It should look something like this: -
- Example of APP file framework - +
+ + Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (see above for recommendations). + + Make a copy of /Library/Frameworks/XUL.Framework inside your APP file. It should look something like this: +
+ Example of APP file framework + * Evergreen.app/ __* Contents/ ____* Frameworks/ @@ -183,14 +187,14 @@ ______* libxpcom.dylib -> Versions/Current/libxpcom.dylib ______* xulrunner-bin -> Versions/Current/xulrunner-bin -
- - Copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/MacOS (do not symlink; copy the file). - - Make Evergreen.app/Resources the root of your Evergreen application files like this: -
- Example APP file - +
+ + Copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/MacOS (do not symlink; copy the file). + + Make Evergreen.app/Resources the root of your Evergreen application files like this: +
+ Example APP file + * Evergreen.app/ __* Contents/ ____* Resources/ @@ -200,115 +204,117 @@ ______* components/ ______* etc. -
+ + + Put a Mac format icon file named Evergreen.icns in Resources. + - Put a Mac format icon file named Evergreen.icns in Resources. - -
- - - Installing on Linux -
- Quick Upgrade of the Staff Client - A Linux Staff Client is automatically built on the server as part of the normal make install process for Evergreen server-side software. To upgrade the Staff Client on a remote workstation with a new version, just copy the directory tree containing the Staff Client from the server to the remote workstation. - The following example assumes you already have an "opensrf" user account on both the server and the remote workstation. Remember to replace "user", "client.linux.machine" and "eg-client-x.x.x.x" with the proper user name, client machine name, and version number in the following example. - As the opensrf user, change directory to the Staff Client source directory, then recursively copy the entire directory tree to the remote workstation: -
- Copying the Staff Client to a remote workstation - + + + + Installing on Linux +
+ Quick Upgrade of the Staff Client + A Linux Staff Client is automatically built on the server as part of the normal make install process for Evergreen server-side software. To upgrade the Staff Client on a remote workstation with a new version, just copy the directory tree containing the Staff Client from the server to the remote workstation. + The following example assumes you already have an "opensrf" user account on both the server and the remote workstation. Remember to replace "user", "client.linux.machine" and "eg-client-x.x.x.x" with the proper user name, client machine name, and version number in the following example. + As the opensrf user, change directory to the Staff Client source directory, then recursively copy the entire directory tree to the remote workstation: +
+ Copying the Staff Client to a remote workstation + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ scp -r build user@client.linux.machine:~/eg-client-x.x.x.x/ -
- To test the newly copied Staff Client, as the opensrf user log into the remote workstation and execute it as shown: -
- Testing the copied Staff Client - +
+ To test the newly copied Staff Client, as the opensrf user log into the remote workstation and execute it as shown: +
+ Testing the copied Staff Client + $ su - opensrf $ xulrunner ~/eg-client-x.x.x.x/build/application.ini -
-
-
- Building the Staff Client on the Server - A Linux Staff Client is automatically built on the server as part of the normal make install process for Evergreen server-side software. - In order to install a compatible Staff Client on another Linux system, just copy the applicable files from the server to that system, or even manually build it on that system. Ensure that the BUILD_ID you choose on the server matches the BUILD_ID for each staff client you use on other systems. - If you will be using a pre-packaged Windows version on some systems, you may want to choose the BUILD_ID on both server and other versions to match that of the Windows Staff Client. To determine which BUILD_ID is used in an existing Staff Client installation, just click "About this Client" on the running Staff Client. - If you are allowed to make changes on the Evergreen server, another option is to create a symbolic link. In order for a copy of the Staff Client and server to work together, the BUILD_ID 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. -
- Creating a symbolic link - +
+
+
+ Building the Staff Client on the Server + A Linux Staff Client is automatically built on the server as part of the normal make install process for Evergreen server-side software. + In order to install a compatible Staff Client on another Linux system, just copy the applicable files from the server to that system, or even manually build it on that system. Ensure that the BUILD_ID you choose on the server matches the BUILD_ID for each staff client you use on other systems. + If you will be using a pre-packaged Windows version on some systems, you may want to choose the BUILD_ID on both server and other versions to match that of the Windows Staff Client. To determine which BUILD_ID is used in an existing Staff Client installation, just click "About this Client" on the running Staff Client. + If you are allowed to make changes on the Evergreen server, another option is to create a symbolic link. In order for a copy of the Staff Client and server to work together, the BUILD_ID 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. +
+ Creating a symbolic link + $ su - root $ cd /openils/var/web/xul $ ln -s SERVER_BUILD_ID/ CLIENT_BUILD_ID -
-
-
- Building the Staff Client on the client Machine - This section is directed toward end-users who wish to use Linux rather than Windows for client machines, but have limited Linux experience. You can build the Staff Client on a Linux system without installing the Evergreen Server component. This is a relatively simple process compared to server installation, but does require some command-line work. The following directions are for building Staff Client version 1.2.1.4 on Kubuntu 7.10; you must modify them for other distributions (the instructions should work as-is for Ubuntu or Ubuntu derivatives). - - - Prerequisites - Both "subversion" and "xulrunner" are required to build the Staff Client. As the root user, use "apt-get" to install packages for "subversion" and "xulrunner". You can also use "synaptic", the graphical user interface for "apt-get". For "subversion", select the latest version; for "xulrunner", select version 1.8.1.4-2ubuntu5. -
- Installing subversion and xulrunner - +
+
+
+ Building the Staff Client on the client Machine + This section is directed toward end-users who wish to use Linux rather than Windows for client machines, but have limited Linux experience. You can build the Staff Client on a Linux system without installing the Evergreen Server component. This is a relatively simple process compared to server installation, but does require some command-line work. The following directions are for building Staff Client version 1.2.1.4 on Kubuntu 7.10; you must modify them for other distributions (the instructions should work as-is for Ubuntu or Ubuntu derivatives). + + + Prerequisites + Both "subversion" and "xulrunner" are required to build the Staff Client. As the root user, use "apt-get" to install packages for "subversion" and "xulrunner". You can also use "synaptic", the graphical user interface for "apt-get". For "subversion", select the latest version; for "xulrunner", select version 1.8.1.4-2ubuntu5. +
+ Installing subversion and xulrunner + $ sudo apt-get install subversion $ sudo apt-get install xulrunner -
- - - Download the Source Code - - - Determine which version is needed - For most end-users, a specific version is required to communicate properly with the Evergreen server. Check with your system admininstrator, IT person, or HelpDesk to determine which Staff Client versions are supported. - Next, you 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://svn.open-ils.org/trac/ILS/browser. Look in the "Visit" drop-down box; see the list of Branches and, further down, a list of Tags. You may have to do some guesswork, but it is fairly straightforward to determine which tag to use. If the server is version 1.2.1.4, you will want to use the tag that looks most appropriate. For example, as you look through the tag list, notice the tag named 'rel_1_2_1_4'. This is the tag you need; make a note of it for the next step. - - - Download the Code - As the opensrf user, open a terminal (command-line prompt) and navigate to the directory in which you wish to download the Staff Client. Use the following commands to download the proper version of the source code by tag name: -
- Downloading the source code - +
+ + + Download the Source Code + + + Determine which version is needed + For most end-users, a specific version is required to communicate properly with the Evergreen server. Check with your system admininstrator, IT person, or HelpDesk to determine which Staff Client versions are supported. + Next, you 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://svn.open-ils.org/trac/ILS/browser. Look in the "Visit" drop-down box; see the list of Branches and, further down, a list of Tags. You may have to do some guesswork, but it is fairly straightforward to determine which tag to use. If the server is version 1.2.1.4, you will want to use the tag that looks most appropriate. For example, as you look through the tag list, notice the tag named 'rel_1_2_1_4'. This is the tag you need; make a note of it for the next step. + + + Download the Code + As the opensrf user, open a terminal (command-line prompt) and navigate to the directory in which you wish to download the Staff Client. Use the following commands to download the proper version of the source code by tag name: +
+ Downloading the source code + $ su - opensrf $ cd /YOUR/DOWNLOAD/DIRECTORY $ svn co svn://svn.open-ils.org/ILS/tags/rel_1_2_1_4/ -
- Remember to change "rel_1_2_1_4" to the appropriate tag for your installation. - - - - - Build the Staff Client -
- Evergreen 1.2.x - In the following example, navigate to the directory in which the source code was downloaded, then navigate to the proper subdirectory and run the "make" utility to actually build the Staff Client. Remember to check with your system administrator 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 instance, for the PINES installation (version 1.2.1.4) the supported BUILD_ID is "rel_1_2_1_4". Modify the following commands accordingly. - As the opensrf user, run the following commands to build the Staff Client: -
- Finding the downloaded source code - +
+ Remember to change "rel_1_2_1_4" to the appropriate tag for your installation. + + + + + Build the Staff Client + + + Evergreen 1.2.x + In the following example, navigate to the directory in which the source code was downloaded, then navigate to the proper subdirectory and run the "make" utility to actually build the Staff Client. Remember to check with your system administrator 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 instance, for the PINES installation (version 1.2.1.4) the supported BUILD_ID is "rel_1_2_1_4". Modify the following commands accordingly. + As the opensrf user, run the following commands to build the Staff Client: +
+ Finding the downloaded source code + $ su - opensrf $ cd /YOUR/DOWNLOAD/DIRECTORY $ cd Open-ILS/xul/staff_client $ make STAFF_CLIENT_BUILD_ID='rel_1_2_1_4' ... -
-
-
- Evergreen 1.4.x - The 1.4 series of Evergreen has complicated the build process for the Staff Client a bit. If you downloaded a .tar.gz (compressed tar archive) of Evergreen, then your steps will resemble the following: - FIXME -- Need instructions for getting certain Javascript files from OpenSRF, preferably without actually installing OpenSRF. +
+ + + Evergreen 1.4.x + The 1.4 series of Evergreen has complicated the build process for the Staff Client a bit. If you downloaded a .tar.gz (compressed tar archive) of Evergreen, then your steps will resemble the following: + FIXME -- Need instructions for getting certain Javascript files from OpenSRF, preferably without actually installing OpenSRF. -
- Building 1.4.x - +
+ Building 1.4.x + $ su - opensrf $ wget http://evergreen-ils.org/downloads/Evergreen-ILS-1.4.0.4.tar.gz $ tar xfz Evergreen-ILS-1.4.0.4.tar.gz @@ -317,12 +323,12 @@ $ 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: -
- Building from a "subversion" checkout - +
+ + If you're installing from a Subversion checkout: +
+ Building from a "subversion" checkout + $ su - opensrf $ svn co svn://svn.open-ils.org/ILS/tags/rel_1_4_0_4/ $ cd rel_1_4_0_4 @@ -331,319 +337,320 @@ $ cd Open-ILS/xul/staff_client/ $ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install -
-
- - - Run the Staff Client (from the command line) - As the opensrf user, navigate to the build/ subdirectory (not staff_client/) and run the following command: -
- Running the Staff Client - +
+ + + + + Run the Staff Client (from the command line) + As the opensrf user, navigate to the build/ subdirectory (not staff_client/) and run the following command: +
+ Running the Staff Client + $ su - opensrf $ xulrunner application.ini -
- - - (OPTIONAL) Cleaning Up / Creating Shortcuts - The source code download included many files that are needed to build the Staff Client, but are not necessary to run it. You may wish to remove them to save space, or to create a clean directory containing the built staff client that can be copied to other machines. To create a clean "staging" directory in which to place the finished staff client, issue the following commands: -
- Creating a "staging" directory - +
+ + + (OPTIONAL) Cleaning Up / Creating Shortcuts + The source code download included many files that are needed to build the Staff Client, but are not necessary to run it. You may wish to remove them to save space, or to create a clean directory containing the built staff client that can be copied to other machines. To create a clean "staging" directory in which to place the finished staff client, issue the following commands: +
+ Creating a "staging" directory + $ mkdir ~/<Destination Directory> $ cd ~/<Download Directory>/Open-ILS/xul/ $ cp -r staff_client ~/<Destination Directory> -
- Finally, test the Staff Client to verify that all the necessary files were moved to the destination directory: -
- Testing the copied Staff Client - +
+ Finally, test the Staff Client to verify that all the necessary files were moved to the destination directory: +
+ Testing the copied Staff Client + $ cd ~/<Destination Directory>/staff_client/build $ xulrunner application.ini -
- If there were no problems, then finish the cleanup by removing the original download directory and all subdirectories: -
- Cleaning up - +
+ If there were no problems, then finish the cleanup by removing the original download directory and all subdirectories: +
+ Cleaning up + $ rm -r -f ~/<Download Directory> -
- Finally, test the copied Staff Client. You can create "Desktop / Start Menu / K-Menu" shortcuts for the Staff Client by using the following command as the target: -
- Running the copied Staff Client - +
+ Finally, test the copied Staff Client. You can create "Desktop / Start Menu / K-Menu" shortcuts for the Staff Client by using the following command as the target: +
+ Running the copied Staff Client + $ xulrunner ~/<Destination Directory>/staff_client/build/application.ini -
- - -
-
- Using Wine to Install On Linux - The Linux application Wine is another alternative for those who wish to install the packaged Windows versions rather than building the Staff Client manually. Wine is a Linux application that allows users to directly run Windows executables, and is a simple way for casual Linux users to use the Staff Client. More information about Wine can be found at http://www.winehq.org/site/docs/wineusr-guide/getting-wine. - As the root user, use "apt-get" to install the package for "wine". You can also use "synaptic", the graphical user interface. - - - Install wine -
- Installing "wine" - +
+ + +
+
+ Using Wine to Install On Linux + The Linux application Wine is another alternative for those who wish to install the packaged Windows versions rather than building the Staff Client manually. Wine is a Linux application that allows users to directly run Windows executables, and is a simple way for casual Linux users to use the Staff Client. More information about Wine can be found at http://www.winehq.org/site/docs/wineusr-guide/getting-wine. + As the root user, use "apt-get" to install the package for "wine". You can also use "synaptic", the graphical user interface. + + + Install wine +
+ Installing "wine" + $ sudo apt-get install wine -
- - - Download Windows installer for the Staff Client - As the opensrf user, run the following commands to download the Windows installer for the proper Staff Client from the open-ils.org website and place it in a temporary directory: -
- Downloading the Staff Client installer - +
+ + + Download Windows installer for the Staff Client + As the opensrf user, run the following commands to download the Windows installer for the proper Staff Client from the open-ils.org website and place it in a temporary directory: +
+ Downloading the Staff Client installer + $ su - opensrf $ cd /YOUR/DOWNLOAD/DIRECTORY $ wget http://open-ils.org/downloads/evergreen-setup-rel_version-number.exe -
- - - Run the downloaded Windows installer - As the opensrf user, navigate to the directory where you downloaded the Windows executable file, then execute it: -
- Using Wine to run the Windows installer - +
+ + + Run the downloaded Windows installer + As the opensrf user, navigate to the directory where you downloaded the Windows executable file, then execute it: +
+ Using Wine to run the Windows installer + $ su - opensrf $ cd /YOUR/DOWNLOAD/DIRECTORY $ wine evergreen-setup-rel_version-number.exe -
- If this step fails, you may need to configure Wine first to properly 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, then click "Apply". - - - Launch the Staff Client - A new entry for the Staff Client should now appear somewhere in the "All Applications" menu of your Linux desktop. Also, find a new desktop shortcut for the Staff Client. To launch the Staff Client, visit the "All Applications" menu, find a section similar to "Wine->Program Files->Evergreen Staff Client->Evergreen Staff Client", or else launch the Staff Client from the desktop shortcut. - - -
-
- Running the Staff Client over an SSH Tunnel - The Staff Client can use an SSH tunnel as a SOCKS 5 proxy. For more details, see the section Configuring a Proxy for the Staff Client. -
- - - Assigning Workstation Names - The Staff Client must be assigned to a library and given a unique name before it will connect fully to the Evergreen server. The only restriction is that the workstation's name must be unique within the assigned library. Make sure to select a workstation name that you will remember later, and reflects the role, purpose, and/or location of a particular computer. These names will come up later in statistical reporting, and can also be handy when troubleshooting. -
- Example of unconfigured Staff Client - - - - - -
- In order to assign a workstation a name, a user with appropriate permissions must login to the Staff Client. In PINES, the local system administrator (OPSM) has the ability to assign workstation names in his or her library system. Library managers (LIBM's) have the ability within their branch. To assign a workstation a name, login to the system. You will be prompted to assign the workstation a library and a name: -
- Example of configured Staff Client - - - - - -
- Select the library this workstation physically operates in from the drop down menu. In this example, we have selected "MGRL-MA". Type in a friendly name for the workstation. In this example, we are installing the Staff Client on the director's personal system, and have named it as such. Then hit Register. - Once you have registered your workstation with the server, your screen will look like this: -
- Example of registered Staff Client - - - - - -
- You are now ready to log into the Staff Client for the first time. Type in your password again, and hit Login. + + If this step fails, you may need to configure Wine first to properly 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, then click "Apply". + + + Launch the Staff Client + A new entry for the Staff Client should now appear somewhere in the "All Applications" menu of your Linux desktop. Also, find a new desktop shortcut for the Staff Client. To launch the Staff Client, visit the "All Applications" menu, find a section similar to "Wine->Program Files->Evergreen Staff Client->Evergreen Staff Client", or else launch the Staff Client from the desktop shortcut. + + +
+
+ Running the Staff Client over an SSH Tunnel + The Staff Client can use an SSH tunnel as a SOCKS 5 proxy. For more details, see the section . +
+
+ Assigning Workstation Names + The Staff Client must be assigned to a library and given a unique name before it will connect fully to the Evergreen server. The only restriction is that the workstation's name must be unique within the assigned library. Make sure to select a workstation name that you will remember later, and reflects the role, purpose, and/or location of a particular computer. These names will come up later in statistical reporting, and can also be handy when troubleshooting. +
+ Example of unconfigured Staff Client + + + + + +
+ In order to assign a workstation a name, a user with appropriate permissions must login to the Staff Client. In PINES, the local system administrator (OPSM) has the ability to assign workstation names in his or her library system. Library managers (LIBM's) have the ability within their branch. To assign a workstation a name, login to the system. You will be prompted to assign the workstation a library and a name: +
+ Example of configured Staff Client + + + + + +
+ Select the library this workstation physically operates in from the drop down menu. In this example, we have selected "MGRL-MA". Type in a friendly name for the workstation. In this example, we are installing the Staff Client on the director's personal system, and have named it as such. Then hit Register. + Once you have registered your workstation with the server, your screen will look like this: +
+ Example of registered Staff Client + + + + + +
+ You are now ready to log into the Staff Client for the first time. Type in your password again, and hit Login. +
+ - -
- Manually Building the Staff Client - The Staff Client is automatically built by default as part of the normal make install process for Evergreen server-side software. See the section "Compile, Link and Install Evergreen" to review details related to building the Staff Client in the final compile/link/install phase of the default Evergreen build process. - - Building the Staff Client - You can also manually build the Staff Client by using the make utility in the Staff Client source directory (e.g., the directory /home/opensrf/Evergreen-ILS-1.6.0.x/Open-ILS/xul/staff_client for the current Evergreen version). There are a number of possible options to manually build special versions of the Staff Client on a Linux system. Following is a list of environment variables that can be passed to make to influence the manual build process: + + Manually Building the Staff Client + The Staff Client is automatically built by default as part of the normal make install process for Evergreen server-side software. See the section to review details related to building the Staff Client in the final compile/link/install phase of the default Evergreen build process.
- Option STAFF_CLIENT_BUILD_ID - During the normal make install Evergreen server-side software build process, the variable defaults to an automatically generated date/time string, but you can also override the value of BUILD_ID. - The following commands could be used during the normal build process: -
- Commands used during normal Evergreen build - + Building the Staff Client + You can also manually build the Staff Client by using the make utility in the Staff Client source directory (e.g., the directory /home/opensrf/Evergreen-ILS-1.6.0.x/Open-ILS/xul/staff_client for the current Evergreen version). There are a number of possible options to manually build special versions of the Staff Client on a Linux system. Following is a list of environment variables that can be passed to make to influence the manual build process: +
+ Option STAFF_CLIENT_BUILD_ID + During the normal make install Evergreen server-side software build process, the variable defaults to an automatically generated date/time string, but you can also override the value of BUILD_ID. + The following commands could be used during the normal build process: +
+ Commands used during normal Evergreen build + $ su - root $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_7 install ... -
- The following commands will manually build the Staff Client using a different BUILD_ID. - As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: -
- Commands to manually build the Staff Client - +
+ The following commands will manually build the Staff Client using a different BUILD_ID. + As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: +
+ Commands to manually build the Staff Client + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make STAFF_CLIENT_BUILD_ID=my_test_id build ... -
-
-
- Option STAFF_CLIENT_VERSION - During the normal make install Evergreen server-side software build process, the variable is pulled automatically from a README file in the Evergreen source root. The variable defaults to 0trunk.revision, where the value of "revision" is automatically generated. You can override the value of VERSION similarly to the BUILD_ID. - The following commands could be used during the normal build process: -
- Commands used during normal Evergreen build - +
+
+
+ Option STAFF_CLIENT_VERSION + During the normal make install Evergreen server-side software build process, the variable is pulled automatically from a README file in the Evergreen source root. The variable defaults to 0trunk.revision, where the value of "revision" is automatically generated. You can override the value of VERSION similarly to the BUILD_ID. + The following commands could be used during the normal build process: +
+ Commands used during normal Evergreen build + $ su - root $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 $ make STAFF_CLIENT_VERSION=0mytest.200 install ... -
- The following commands will manually build the Staff Client using a different VERSION. - If you plan to make extensions update automatically, the VERSION needs to conform to the format recommended in Toolkit Version Format and newer versions need to be "higher" than older versions. - As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: -
- Commands to manually build the Staff Client - +
+ The following commands will manually build the Staff Client using a different VERSION. + If you plan to make extensions update automatically, the VERSION needs to conform to the format recommended in Toolkit Version Format and newer versions need to be "higher" than older versions. + As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: +
+ Commands to manually build the Staff Client + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make STAFF_CLIENT_VERSION=0mytest.200 build ... -
-
-
- Option STAFF_CLIENT_STAMP_ID variable - During the normal make install Evergreen server-side software build process, this variable is generated from STAFF_CLIENT_VERSION. You can override the value of STAMP_ID similarly to the BUILD_ID. - The following commands could be used during the normal build process: -
- Commands used during normal Evergreen build - +
+
+
+ Option STAFF_CLIENT_STAMP_ID variable + During the normal make install Evergreen server-side software build process, this variable is generated from STAFF_CLIENT_VERSION. You can override the value of STAMP_ID similarly to the BUILD_ID. + The following commands could be used during the normal build process: +
+ Commands used during normal Evergreen build + $ su - root $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 $ make STAFF_CLIENT_STAMP_ID=my_test_stamp install ... -
- The following commands will manually build the Staff Client using a different STAMP_ID. - It is possible to have multiple versions of the Staff Client by specifying a different STAMP_ID for each, possibly for different uses or client-side customizations. - As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: -
- Commands to manually build the Staff Client - +
+ The following commands will manually build the Staff Client using a different STAMP_ID. + It is possible to have multiple versions of the Staff Client by specifying a different STAMP_ID for each, possibly for different uses or client-side customizations. + As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: +
+ Commands to manually build the Staff Client + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make STAFF_CLIENT_STAMP_ID=my_test_stamp build ... -
+
+
- - - Advanced Build Options - In addition to the basic options listed above, there are a number of advanced options for building the Staff Client. Most are target names for the make utility and require that you build the Staff Client from its source directory. See the following table for a list of possible make target keywords: - - Keywords Targets for "make" Command - - - - - - Keyword - Description - - - - - clients - Runs "make win-client", "make linux-client", and "make generic-client" individually - - - client_dir - Builds a client directory from the build directory, without doing a rebuild. The same as "copy everything but server/". - - - client_app - Prerequisite "client_dir"; removes "install.rdf" from client directory so an APP bundle can't be installed as an extension - - - client_ext - Prerequisite "client_dir"; remove "application.ini", "autoupdate.js", "standalone_xul_app.js" from client directory so an extension won't break Firefox - - - extension - Prerequisite "client_ext"; rewritten to use "client_ext" - - - generic-client - Prerequisite "client_app"; makes an XPI file suitable for use with "xulrunner --install-app"" - - - win-xulrunner - Prerequisite "client_app"; adds Windows xulrunner to client build - - - linux-xulrunner - Prerequisite "client_app"; adds Linux xulrunner to client build - - - win-client - Prerequisite "win-xulrunner"; builds "setup exe" (requires that "nsis" package be installed, will add options for automatic update if configured and developer options if client build was a "make devbuild") - - - linux-client - Prerequisite "linux_xulrunner"; builds a "tar.bz2" bundle of the Linux client - - - [generic-|win-|linux-|extension-]updates[-client] - Calls external/make_updates.sh to build full and partial updates generic/win/linux/extension prefix limit to that distribution; Adding "-client" builds clients and copies them to a subdirectory of the "updates" directory as well; "extension-updates-client" doesn't exist. - - - -
- Descriptions of other special build options follow: - - - Developer Build - You can create a so-called "developer build" of the Staff Client by substituting "devbuild" for "build" when running make. The build will contain an extra configuration file that enables some developer options. - As the opensrf user, run make from the Staff Client source directory: -
- Commands to do a "developer build" - +
+ Advanced Build Options + In addition to the basic options listed above, there are a number of advanced options for building the Staff Client. Most are target names for the make utility and require that you build the Staff Client from its source directory. See the following table for a list of possible make target keywords: + + Keywords Targets for "make" Command + + + + + + Keyword + Description + + + + + clients + Runs "make win-client", "make linux-client", and "make generic-client" individually + + + client_dir + Builds a client directory from the build directory, without doing a rebuild. The same as "copy everything but server/". + + + client_app + Prerequisite "client_dir"; removes "install.rdf" from client directory so an APP bundle can't be installed as an extension + + + client_ext + Prerequisite "client_dir"; remove "application.ini", "autoupdate.js", "standalone_xul_app.js" from client directory so an extension won't break Firefox + + + extension + Prerequisite "client_ext"; rewritten to use "client_ext" + + + generic-client + Prerequisite "client_app"; makes an XPI file suitable for use with "xulrunner --install-app"" + + + win-xulrunner + Prerequisite "client_app"; adds Windows xulrunner to client build + + + linux-xulrunner + Prerequisite "client_app"; adds Linux xulrunner to client build + + + win-client + Prerequisite "win-xulrunner"; builds "setup exe" (requires that "nsis" package be installed, will add options for automatic update if configured and developer options if client build was a "make devbuild") + + + linux-client + Prerequisite "linux_xulrunner"; builds a "tar.bz2" bundle of the Linux client + + + [generic-|win-|linux-|extension-]updates[-client] + Calls external/make_updates.sh to build full and partial updates generic/win/linux/extension prefix limit to that distribution; Adding "-client" builds clients and copies them to a subdirectory of the "updates" directory as well; "extension-updates-client" doesn't exist. + + + +
+ Descriptions of other special build options follow: + + + Developer Build + You can create a so-called "developer build" of the Staff Client by substituting "devbuild" for "build" when running make. The build will contain an extra configuration file that enables some developer options. + As the opensrf user, run make from the Staff Client source directory: +
+ Commands to do a "developer build" + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make devbuild ... -
- - - Compressed Javascript - You can execute the Google "Closure Compiler" utility to automatically review and compress Javascript code after the build process completes, by substituting "compress-javascript" for "build" when running make. For more information see Google "Closure Compiler". - As the opensrf user, run the following commands from the Staff Client source directory: -
- Commands to compress Javascript - +
+ + + Compressed Javascript + You can execute the Google "Closure Compiler" utility to automatically review and compress Javascript code after the build process completes, by substituting "compress-javascript" for "build" when running make. For more information see Google "Closure Compiler". + As the opensrf user, run the following commands from the Staff Client source directory: +
+ Commands to compress Javascript + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make compress-javascript ... -
- You can also combine Javascript review and compression, and also perform a "developer build". - As the opensrf user, run the following commands from the Staff Client source directory: -
- Commands to compress Javascript and do a "developer build" - +
+ You can also combine Javascript review and compression, and also perform a "developer build". + As the opensrf user, run the following commands from the Staff Client source directory: +
+ Commands to compress Javascript and do a "developer build" + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client @@ -651,181 +658,181 @@ $ make devbuild compress-javascript ... -
- - - Automatic Update Host - The host used to check for automatic Staff Client updates can be overridden by specifying the AUTOUPDATE_HOST option. The following commands could have been used during the normal build process: -
- Commands to set AUTOUPDATE_HOST for normal Evergreen build - +
+ + + Automatic Update Host + The host used to check for automatic Staff Client updates can be overridden by specifying the AUTOUPDATE_HOST option. The following commands could have been used during the normal build process: +
+ Commands to set AUTOUPDATE_HOST for normal Evergreen build + $ su - root $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 $ make AUTOUPDATE_HOST=localhost install ... -
- You can manually set AUTOUPDATE_HOST to set up automatic update checking. The following commands will manually build the Staff Client using a different AUTOUPDATE_HOST. - As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: -
- Commands to manually specify AUTOUPDATE_HOST - +
+ You can manually set AUTOUPDATE_HOST to set up automatic update checking. The following commands will manually build the Staff Client using a different AUTOUPDATE_HOST. + As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client: +
+ Commands to manually specify AUTOUPDATE_HOST + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make AUTOUPDATE_HOST=localhost build ... -
- For more information on Automatic Updates, see the section "Automatic Updates". - - - - - Installing and Activating a Manually Built Staff Client - The Staff Client is automatically built, installed and activated as part of the normal make install process for Evergreen server-side software. However, if you manually build the Staff Client, then you need to take additional steps to properly install and activate it. You also have the option of installing the Staff Client on the same machine it was built on, or on a different machine. - Assuming you have already built the Staff Client, and that your installation is in the directory /openils/var/web/xul, as the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands to install the Staff Client on the same machine - +
+ For more information on Automatic Updates, see the section . + + +
+
+ Installing and Activating a Manually Built Staff Client + The Staff Client is automatically built, installed and activated as part of the normal make install process for Evergreen server-side software. However, if you manually build the Staff Client, then you need to take additional steps to properly install and activate it. You also have the option of installing the Staff Client on the same machine it was built on, or on a different machine. + Assuming you have already built the Staff Client, and that your installation is in the directory /openils/var/web/xul, as the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands to install the Staff Client on the same machine + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ mkdir -p "/openils/var/web/xul/$(cat build/BUILD_ID)" $ cp -R build/server "/openils/var/web/xul/$(cat build/BUILD_ID)" -
- - - Packaging the Staff Client - Once the Staff Client has been built, you can create several forms of client packages by using some targetted make commands in the Staff Client source directory. - - - Packaging a Generic Client - This build creates a Staff Client packaged as an XPI file to use with XULRunner. It requires that you already have the "zip" utility installed on your system. It will create the output file "evergreen_staff_client.xpi", suitable for use with the XULRunner parameter --install-app. - As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands to package a "generic" client - +
+
+
+ Packaging the Staff Client + Once the Staff Client has been built, you can create several forms of client packages by using some targetted make commands in the Staff Client source directory. + + + Packaging a Generic Client + This build creates a Staff Client packaged as an XPI file to use with XULRunner. It requires that you already have the "zip" utility installed on your system. It will create the output file "evergreen_staff_client.xpi", suitable for use with the XULRunner parameter --install-app. + As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands to package a "generic" client + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make generic-client ... -
- - - Packaging a Windows Client - This build creates a Staff Client packaged as a Windows executable. It requires that you already have the "unzip" utility installed on your system. It also requires that you install NSIS (Nullsoft Scriptable Install System), a professional open source utility package used to create Windows installers (the "makensis" utility is installed as part of the "nsis" package). We recommend using Version 2.45 or later. This build will create the output file "evergreen_staff_client_setup.exe". - (OPTIONAL) If you wish for the Staff Client to have a link icon/tray icon by default, you may wish to provide a pre-modified xulrunner-stub.exe. Place it in the Staff Client source directory and make will automatically use it instead of the one that comes with the downloaded XULRunner release. The version of xulrunner-stub.exe need not match exactly. - (OPTIONAL) You can also use a tool such as Resource Hacker to embed icons. "Resource Hacker" is an open-source utility used to view, modify, rename, add, delete and extract resources in 32bit Windows executables. See the following table for some useful icon ID strings: - - Useful icon ID strings - - - - - - IDI_APPICON - Tray icon - - - 32512 - Default window icon - - - -
- As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands to build a Windows client - +
+ + + Packaging a Windows Client + This build creates a Staff Client packaged as a Windows executable. It requires that you already have the "unzip" utility installed on your system. It also requires that you install NSIS (Nullsoft Scriptable Install System), a professional open source utility package used to create Windows installers (the "makensis" utility is installed as part of the "nsis" package). We recommend using Version 2.45 or later. This build will create the output file "evergreen_staff_client_setup.exe". + (OPTIONAL) If you wish for the Staff Client to have a link icon/tray icon by default, you may wish to provide a pre-modified xulrunner-stub.exe. Place it in the Staff Client source directory and make will automatically use it instead of the one that comes with the downloaded XULRunner release. The version of xulrunner-stub.exe need not match exactly. + (OPTIONAL) You can also use a tool such as Resource Hacker to embed icons. "Resource Hacker" is an open-source utility used to view, modify, rename, add, delete and extract resources in 32bit Windows executables. See the following table for some useful icon ID strings: + + Useful icon ID strings + + + + + + IDI_APPICON + Tray icon + + + 32512 + Default window icon + + + +
+ As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands to build a Windows client + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make win-client ... -
- - - Packaging a Linux Client - This build creates a Staff Client package for Linux as a "tar.bz2" file with XULRunner already bundled with it. It creates the output file "evergreen_staff_client.tar.bz2". - As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands to build a Linux client - +
+ + + Packaging a Linux Client + This build creates a Staff Client package for Linux as a "tar.bz2" file with XULRunner already bundled with it. It creates the output file "evergreen_staff_client.tar.bz2". + As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands to build a Linux client + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make linux-client ... -
- - - Packaging a Firefox Extension - This build requires that you already have the "zip" utility installed on your system. It creates a Staff Client packaged as a Firefox extension and creates the output file "evergreen.xpi". - As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands to build a Firefox extension - +
+ + + Packaging a Firefox Extension + This build requires that you already have the "zip" utility installed on your system. It creates a Staff Client packaged as a Firefox extension and creates the output file "evergreen.xpi". + As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands to build a Firefox extension + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make extension ... -
- - - - - Staff Client Automatic Updates - It is possible to set up support for automatic Staff Client updates, either during the normal Evergreen server-side build process, or by manually building the Staff Client with certain special options. -
- WARNINGS - Automatic update server certificate requirements are more strict than normal server requirements. Firefox and XULRunner will both ignore any automatic update server that is not validated by a trusted certificate authority. Servers with exceptions added to force the Staff Client to accept them WILL NOT WORK. - In addition, automatic updates have special requirements for the file update.rdf: - - It must be served from an SSL server, or - It must be signed with the McCoy tool. - - You can pre-install the signing key into the file install.rdf directly, or install it into a copy as install.mccoy.rdf. If the latter exists it will be copied into the build instead of the original file install.rdf. +
+ + -
- Autoupdate Host - The name of the automatic update host can be provided in either of two ways: - - At configuration time for the normal build of the Evergreen server-side software, or - During a manual Staff Client build process. - - - - - At configuration time for the normal build of Evergreen server-side software - This must be done when the Evergreen server-side software is first configured (see the section "Configure Evergreen" ). As the opensrf user, use the utility "configure" as shown: -
- Commands to configure Evergreen - +
+ Staff Client Automatic Updates + It is possible to set up support for automatic Staff Client updates, either during the normal Evergreen server-side build process, or by manually building the Staff Client with certain special options. +
+ WARNINGS + Automatic update server certificate requirements are more strict than normal server requirements. Firefox and XULRunner will both ignore any automatic update server that is not validated by a trusted certificate authority. Servers with exceptions added to force the Staff Client to accept them WILL NOT WORK. + In addition, automatic updates have special requirements for the file update.rdf: + + It must be served from an SSL server, or + It must be signed with the McCoy tool. + + You can pre-install the signing key into the file install.rdf directly, or install it into a copy as install.mccoy.rdf. If the latter exists it will be copied into the build instead of the original file install.rdf. +
+
+ Autoupdate Host + The name of the automatic update host can be provided in either of two ways: + + At configuration time for the normal build of the Evergreen server-side software, or + During a manual Staff Client build process. + + + + + At configuration time for the normal build of Evergreen server-side software + This must be done when the Evergreen server-side software is first configured (see the section ). As the opensrf user, use the utility "configure" as shown: +
+ Commands to configure Evergreen + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 $ ./configure --prefix=/openils --sysconfdir=/openils/conf --with-updateshost=hostname $ make ... -
- - - During a manual Staff Client build process - You will used the variable AUTOUPDATE_HOST=hostname (see above). If you specify just a hostname (such as "example.com") then the URL will be a secure URL (such as "https://example.com". If you wish to use a non-HTTPS URL then prefix the hostname with "http://" (such as "http://example.com"). - If neither option is used then, by default, the Staff Client will not include the automatic update preferences. - - -
-
- Building Updates - Similar to building clients, the targets "generic-updates", "win-updates", "linux-updates", and "extension-updates" can be used individually with make to build the update files for the Staff Client. To build all the targets at once, simply use the target "updates". - A "full" update will be built for each specified target (or for all if you use the target "updates"). For all but extensions any previous "full" updates (archived by default in the directory /openils/var/updates/archives) will be used to make "partial" updates. Partial updates tend to be much smaller and will thus download more quickly, but if something goes wrong with a partial update the full update will be used as a fallback. Extensions do not currently support partial updates. - As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands for building updates - +
+ + + During a manual Staff Client build process + You will used the variable AUTOUPDATE_HOST=hostname (see above). If you specify just a hostname (such as "example.com") then the URL will be a secure URL (such as "https://example.com". If you wish to use a non-HTTPS URL then prefix the hostname with "http://" (such as "http://example.com"). + If neither option is used then, by default, the Staff Client will not include the automatic update preferences. + + +
+
+ Building Updates + Similar to building clients, the targets "generic-updates", "win-updates", "linux-updates", and "extension-updates" can be used individually with make to build the update files for the Staff Client. To build all the targets at once, simply use the target "updates". + A "full" update will be built for each specified target (or for all if you use the target "updates"). For all but extensions any previous "full" updates (archived by default in the directory /openils/var/updates/archives) will be used to make "partial" updates. Partial updates tend to be much smaller and will thus download more quickly, but if something goes wrong with a partial update the full update will be used as a fallback. Extensions do not currently support partial updates. + As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands for building updates + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client @@ -843,16 +850,16 @@ $ make extension-updates ... -
-
-
- Building updates with clients - To save time and effort you can build updates and manual download clients at the same time by adding the string "-client" to each target name. For instance, you can specify "win-updates-client". You can also specify "updates-client" to build all the targets at once. This does not work for extension-updates. - The clients will be installed alongside the updates and listed on the "manualupdate.html" page, rather than left in the Staff Client directory. - As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Commands for building updates - +
+
+
+ Building updates with clients + To save time and effort you can build updates and manual download clients at the same time by adding the string "-client" to each target name. For instance, you can specify "win-updates-client". You can also specify "updates-client" to build all the targets at once. This does not work for extension-updates. + The clients will be installed alongside the updates and listed on the "manualupdate.html" page, rather than left in the Staff Client directory. + As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Commands for building updates + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client @@ -868,46 +875,47 @@ $ make linux-updates-client ... -
-
-
- Activating the Update Server - This section reviews scripts associated with the update server, and requires some final adjustments to file permissions. - The Apache example configuration creates an "updates" directory that, by default, points to the directory /openils/var/updates/pub. This directory contains one HTML file and several specially-named script files. - The "updatedetails.html" file is the fallback web page for the update details. The "check" script is used for XULRunner updates. The "update.rdf" script is used for extension updates. The "manualupdate.html" script checks for clients to provide download links when automatic updates have failed and uses the download script to force a download of the generic client XPI (compared to Firefox trying to install it as an extension). - The following scripts should be marked as executable: check, download, manualupdate.html, update.rdf. As the root user, change directory to the updates directory, then execute the following commands: -
- Changing file permissions of scripts - +
+
+
+ Activating the Update Server + This section reviews scripts associated with the update server, and requires some final adjustments to file permissions. + The Apache example configuration creates an "updates" directory that, by default, points to the directory /openils/var/updates/pub. This directory contains one HTML file and several specially-named script files. + The "updatedetails.html" file is the fallback web page for the update details. The "check" script is used for XULRunner updates. The "update.rdf" script is used for extension updates. The "manualupdate.html" script checks for clients to provide download links when automatic updates have failed and uses the download script to force a download of the generic client XPI (compared to Firefox trying to install it as an extension). + The following scripts should be marked as executable: check, download, manualupdate.html, update.rdf. As the root user, change directory to the updates directory, then execute the following commands: +
+ Changing file permissions of scripts + $ su - root $ cd /openils/var/updates/pub $ chmod +x check download manualupdate.html update.rdf -
+
+
- - - Other tips
- Multiple workstations on one install - Multiple workstation registrations for the same server can be accomplished with a single Staff Client install by using multiple profiles. When running XULRunner you can specify the option "-profilemanager" or "-P" (uppercase "P") to force the Profile Manager to start. Unchecking the "Don't ask at startup" option will make this the default. - Once you have opened the Profile Manager you can create additional profiles, one for each workstation you wish to register. You may need to install SSL exceptions for each profile. - When building targets "win-client", "win-updates-client", or "updates-client", you can specify "NSIS_EXTRAOPTS=-DPROFILES" to add an "Evergreen Staff Client Profile Manager" option to the start menu. - As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: -
- Command to add start menu option - + Other tips +
+ Multiple workstations on one install + Multiple workstation registrations for the same server can be accomplished with a single Staff Client install by using multiple profiles. When running XULRunner you can specify the option "-profilemanager" or "-P" (uppercase "P") to force the Profile Manager to start. Unchecking the "Don't ask at startup" option will make this the default. + Once you have opened the Profile Manager you can create additional profiles, one for each workstation you wish to register. You may need to install SSL exceptions for each profile. + When building targets "win-client", "win-updates-client", or "updates-client", you can specify "NSIS_EXTRAOPTS=-DPROFILES" to add an "Evergreen Staff Client Profile Manager" option to the start menu. + As the opensrf user, change directory to the Staff Client source directory, then execute the following commands: +
+ Command to add start menu option + $ su - opensrf $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client $ make NSIS_EXTRAOPTS=-DPROFILES win-client ... -
-
-
- Multiple Staff Clients - This may be confusing if you are not careful, but you can log in to multiple Evergreen servers at the same time, or a single Evergreen server multiple times. In either case you will need to create an additional profile for each additional server or workstation you want to log in as (see previous tip). - Once you have created the profiles, run XULRunner with the option "-no-remote" (in addition to "-profilemanger" or "-P" if neeeded). Instead of XULRunner opening a new login window on your existing session it will start a new session instead, which can then be logged in to a different server or workstation ID. +
+
+
+ Multiple Staff Clients + This may be confusing if you are not careful, but you can log in to multiple Evergreen servers at the same time, or a single Evergreen server multiple times. In either case you will need to create an additional profile for each additional server or workstation you want to log in as (see previous tip). + Once you have created the profiles, run XULRunner with the option "-no-remote" (in addition to "-profilemanger" or "-P" if neeeded). Instead of XULRunner opening a new login window on your existing session it will start a new session instead, which can then be logged in to a different server or workstation ID. +
-- 2.11.0