From 16579be0ef62926e9cd597dae90dca2c4f2341fc Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Sat, 2 Oct 2010 21:57:54 -0400 Subject: [PATCH] change xml:id for chapter to "staffclientinstallation"; rename all .PNG files from "serversideinstallation-*.png" to "staffclientinstallation-*.png"; correct all local links to read "staffclientinstallation-*" instead of "serversideinstallation-*"; --- 1.6/admin/staffclientinstallation.xml | 52 +++++++++++++-------------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/1.6/admin/staffclientinstallation.xml b/1.6/admin/staffclientinstallation.xml index fcf78093ef..6ec8a727c5 100644 --- a/1.6/admin/staffclientinstallation.xml +++ b/1.6/admin/staffclientinstallation.xml @@ -1,17 +1,17 @@ - + Installation of Evergreen Staff Client Software This section describes installation of the Evergreen Staff Client software. -
+
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. - + 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 . + 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: @@ -19,7 +19,7 @@ Running the Staff Client installer - + @@ -29,12 +29,12 @@ 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 . + 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 @@ -54,7 +54,7 @@ Running the Staff Client installer - + @@ -64,7 +64,7 @@ Finishing the installation - + @@ -94,7 +94,7 @@ - If you have issues removing previously installed XULRunner versions see for information on removing previous XULRunner versions. + 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 @@ -106,7 +106,7 @@ 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. @@ -219,7 +219,7 @@
-
+
Installing on Linux
Quick Upgrade of the Staff Client @@ -441,14 +441,14 @@
-
+
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 - +
@@ -457,7 +457,7 @@ Example of configured Staff Client - +
@@ -467,7 +467,7 @@ Example of registered Staff Client - + @@ -475,7 +475,7 @@
- + 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.
@@ -687,7 +687,7 @@ ... - For more information on Automatic Updates, see the section . + For more information on Automatic Updates, see the section .
@@ -786,7 +786,7 @@
-
+
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.
@@ -923,7 +923,7 @@
-
+
Running the Staff Client Run the Staff Client on a Linux system by using the application XULRunner (installed automatically and by default with Firefox version 3.0 and later on Ubuntu and Debian distributions). For example, if the source files for the Evergreen installation are in the directory /home/opensrf/Evergreen-ILS-1.6.0.7/, start the Staff Client as shown in the following command example: @@ -934,7 +934,7 @@ $ xulrunner /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client/build/application.ini - + Running the Staff Client over an SSH Tunnel The Staff Client can use an SSH tunnel as a SOCKS 5 proxy.
@@ -957,7 +957,7 @@ Setting up an SSH tunnel in PuTTY - + @@ -978,7 +978,7 @@ The SOCKS section of "all.js" before changes - + @@ -987,11 +987,11 @@ Change the value of network.proxy.socks from "" to "localhost". Change the value of network.proxy.socks_port from "0" to 9999. -
+
The SOCKS section of "all.js" after changes - +
-- 2.43.2