<para>The Staff Client is automatically built by default as part of the normal <emphasis>make install</emphasis> process for Evergreen server-side software. See the section <xref linkend="serversideinstallation-compilingevergreen"/> 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 <xref linkend="staffclientinstallation-building-staffclient"/> for help on manually building the Staff Client. Otherwise, continue with the following sections to install a pre-built Staff Client.</para>
<simplesect xml:id="staffclientinstallation-prebuilt-staffclient">
<title>Installing a Pre-Built Staff Client</title>
- <para>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 <xref linkend="staffclientinstallation-building-staffclient"/>.</para>
+ <para>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, and Linux. If you need to manually build the Staff Client, see the section <xref linkend="staffclientinstallation-building-staffclient"/>.</para>
<section>
<title>Installing on Windows</title>
- <para>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 <ulink url="http://www.evergreen-ils.org/downloads.php">http://www.evergreen-ils.org/downloads.php</ulink>. Download the staff client installer, then run it. A screen that looks similar to this should appear:</para>
+ <para>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 <ulink url="http://www.evergreen-ils.org/downloads.php">http://www.evergreen-ils.org/downloads.php</ulink>. Download the Staff Client installer, then run it. A screen that looks similar to this should appear:</para>
<figure>
<title>Running the Staff Client installer</title>
<mediaobject>
</textobject>
</mediaobject>
</figure>
- <para>Click the <emphasis>Next</emphasis> 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.</para>
- <para>When you run the staff client for the first time, a screen similar to this should appear:</para>
+ <para>Click <guibutton>Next</guibutton> 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.</para>
+ <para>When you run the Staff Client for the first time, a screen similar to this should appear:</para>
<figure>
<title>Running the Staff Client for the first time</title>
<mediaobject>
</textobject>
</mediaobject>
</figure>
- <para>First, configure the server you would like to connect to in the <emphasis role="bold">Server</emphasis> section. For example, the PINES demo system is <emphasis role="bold">demo.gapines.org</emphasis>. After selecting a server, click the <emphasis role="bold">Re-Test Server</emphasis> button.</para>
- <para>Because this is the initial run of the staff client, the <emphasis role="bold">Workstation</emphasis> section in the upper-right states: <emphasis role="bold">Not yet configured for the specified server</emphasis>. 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 <xref linkend="staffclientinstallation-workstationnames"/>.</para>
+ <para>First, add the name of your Evergreen server to the field <emphasis role="bold">Hostname</emphasis> in the <emphasis role="bold">Server</emphasis> section. For example, the PINES demo system is <ulink url="http://demo.gapines.org">http://demo.gapines.org</ulink>. After adding the server name, click <guibutton>Re-Test Server</guibutton>.</para>
+ <para>Because this is the initial run of the Staff Client, the <emphasis role="bold">Workstation</emphasis> section in the upper-right will state: <emphasis role="bold">Not yet configured for the specified server</emphasis>. The first thing you must do to the Staff Client on every workstation is to assign it a workstation name. This is covered in <xref linkend="staffclientinstallation-workstationnames"/>.</para>
</section>
<section>
- <title>Installing on Mac OS X</title>
+ <title>Installing on Mac OS</title>
<para>A Mac package that contains the current version of the Staff Client is available for use with XULRunner.</para>
- <itemizedlist>
- <listitem>
- <para>Evergreen Indiana Pkg file [Evergreen v1.2.3.0]</para>
- <orderedlist>
- <listitem>Download and install the latest version of XULRunner for Mac OS. Release notes for the latest version can be found here: <ulink url="http://developer.mozilla.org/en/docs/XULRunner_1.8.0.4_Release_Notes">http://developer.mozilla.org/en/docs/XULRunner_1.8.0.4_Release_Notes</ulink>. Note, later versions may not work correctly.</listitem>
- <listitem>Download and install the Mac Installation package for the 1_2_3_0 Version Staff Client from <ulink url="http://evergreen.lib.in.us/opac/extras/files/evergreen_osx_staff_client_1_2_3.zip">http://evergreen.lib.in.us/opac/extras/files/evergreen_osx_staff_client_1_2_3.zip</ulink>.</listitem>
- <listitem>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: <emphasis>C:\Program Files\Evergreen Staff Client\build</emphasis>. 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.</listitem>
- <listitem>Drag the application's icon into your toolbar for easier access.</listitem>
- </orderedlist>
- <para/>
- <para>When you run the staff client installer, a screen will appear that looks similar to this:</para>
- <figure>
- <title>Running the Staff Client installer</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../media/staffclientinstallation-staffclient-3.png" format="PNG" scalefit="1" width="20%"/>
- </imageobject>
- <textobject>
- <phrase>Running the Staff Client installer</phrase>
- </textobject>
- </mediaobject>
- </figure>
- <caution> FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif </caution>
- <para>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.</para>
- <figure>
- <title>Finishing the installation</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../media/staffclientinstallation-staffclient-4.png" format="PNG" scalefit="1" width="20%"/>
- </imageobject>
- <textobject>
- <phrase>Finishing the installation</phrase>
- </textobject>
- </mediaobject>
- </figure>
- <caution> FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif </caution>
- </listitem>
- <listitem>
- <para>Running directly using XULRunner</para>
- <para>You must install an apropriate version of XULRunner to match the Evergreen version. See the following table for the recommended version of XULRunner:</para>
- <table>
- <title>Evergreen / XULRunner Dependencies</title>
- <tgroup align="left" cols="2" colsep="1" rowsep="1">
- <colspec colnum="1" colwidth="1*"/>
- <colspec colnum="2" colwidth="3*"/>
- <tbody>
- <row>
- <entry>Evergreen 1.6.x.x</entry>
- <entry>XULrunner 1.9</entry>
- </row>
- <row>
- <entry>Evergreen 1.4.x.x</entry>
- <entry>XULrunner 1.8.0.4 or XULrunner 1.8.0.3</entry>
- </row>
- <row>
- <entry>Evergreen 1.2.x.x</entry>
- <entry>XULrunner 1.8.0.4 or XULrunner 1.8.0.3</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>If you have issues removing previously installed XULRunner versions see <xref linkend="staffclientinstallation-remove-xulrunner"/> for information on removing previous XULRunner versions.</note>
- <para>The staff client data from the <emphasis>./staff_client/build</emphasis> directory must be placed somewhere on the machine (e.g. <emphasis>~/Desktop/Evergreen_Staff_Client</emphasis>). 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:</para>
+ <section>
+ <title>Evergreen Indiana Pkg file [Evergreen v1.2.3.0]</title>
+ <orderedlist>
+ <listitem>Download and install the latest version of XULRunner for Mac OS. Release notes can be found here: <ulink url="http://developer.mozilla.org/en/docs/XULRunner_1.8.0.4_Release_Notes">http://developer.mozilla.org/en/docs/XULRunner_1.8.0.4_Release_Notes</ulink>. Note, later versions may not work correctly.</listitem>
+ <listitem>Download and install the Mac Installation package for the 1_2_3_0 Version Staff Client from <ulink url="http://evergreen.lib.in.us/opac/extras/files/evergreen_osx_staff_client_1_2_3.zip">http://evergreen.lib.in.us/opac/extras/files/evergreen_osx_staff_client_1_2_3.zip</ulink>.</listitem>
+ <listitem>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: <filename class="directory">C:\Program Files\Evergreen Staff Client\build</filename>. 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.</listitem>
+ <listitem>Drag the application's icon into your toolbar for easier access.</listitem>
+ </orderedlist>
+ <para/>
+ <para>When you run the Staff Client installer, a screen will appear that looks similar to this:</para>
+ <figure>
+ <title>Running the Staff Client installer</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../media/staffclientinstallation-staffclient-3.png" format="PNG" scalefit="1" width="20%"/>
+ </imageobject>
+ <textobject>
+ <phrase>Running the Staff Client installer</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <caution> FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif </caution>
+ <para>Click <guibutton>continue</guibutton>, 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.</para>
+ <figure>
+ <title>Finishing the installation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../media/staffclientinstallation-staffclient-4.png" format="PNG" scalefit="1" width="20%"/>
+ </imageobject>
+ <textobject>
+ <phrase>Finishing the installation</phrase>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <caution> FIX BAD LINK: http://es.zionsville.lib.in.us/atheos/eg_osx_a.gif </caution>
+ </section>
+ <section>
+ <title>Running directly using XULRunner</title>
+ <para>You must install an apropriate version of XULRunner to match the Evergreen version. See the following table for the recommended version of XULRunner:</para>
+ <table>
+ <title>Evergreen / XULRunner Dependencies</title>
+ <tgroup align="left" cols="2" colsep="1" rowsep="1">
+ <colspec colnum="1" colwidth="1*"/>
+ <colspec colnum="2" colwidth="3*"/>
+ <tbody>
+ <row>
+ <entry>Evergreen 1.6.x.x</entry>
+ <entry>XULrunner 1.9</entry>
+ </row>
+ <row>
+ <entry>Evergreen 1.4.x.x</entry>
+ <entry>XULrunner 1.8.0.4 or XULrunner 1.8.0.3</entry>
+ </row>
+ <row>
+ <entry>Evergreen 1.2.x.x</entry>
+ <entry>XULrunner 1.8.0.4 or XULrunner 1.8.0.3</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <note>If you have issues removing previously installed XULRunner versions see <xref linkend="staffclientinstallation-remove-xulrunner"/> for further information.</note>
+ <para>The Staff Client data from the directory <filename class="directory">./staff_client/build</filename> must be placed somewhere on the machine (e.g. <filename class="directory">~/Desktop/Evergreen_Staff_Client</filename>). 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:</para>
+ <figure>
+ <title>Executing XULRunner</title>
+ <screen>
+ /Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/Evergreen_Staff_Client
+ </screen>
+ </figure>
+ <para>This command should exit quietly. The folder <filename class="directory">/Applications/OpenILS</filename> will be created, containing a launcher named <application>open_ils_staff_client</application>.</para>
+ </section>
+ <section xml:id="staffclientinstallation-remove-xulrunner">
+ <title>Removing previously installed XULRunner versions</title>
+ <para>If you already have a newer version installed, per the release notes, you will need to remove the entire directory <filename class="directory">/Library/Frameworks/XUL.framework</filename> before downgrading.</para>
+ <para>In addition, you may also need to remove the previous file <filename>/Library/Receipts/xulrunner-ver-mak.pkg</filename> .</para>
+ <para>If file <filename>/Library/Receipts/xulrunner-ver-mak.pkg</filename> does not exist (possibly in newer OSX releases), you need to flush the file <filename>receiptdb</filename>.</para>
+ <note>If you install a newer version over a previous (older) install, the older one is not removed but the symlinks are changed to the newer one.</note>
+ <section>
+ <title>Flush Receiptdb file:</title>
+ <para>First, get the package identifier, then purge/forget the build that was initially installed:</para>
<figure>
- <title>Executing XULRunner</title>
+ <title>Purging previous build</title>
<screen>
- /Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/Evergreen_Staff_Client
- </screen>
- </figure>
- <para>This command should exit quietly. A folder will be created, named <emphasis>/Applications/OpenILS</emphasis>, containing a launcher named <emphasis>open_ils_staff_client</emphasis>.</para>
- </listitem>
- <listitem>
- <para>Removing previously installed XULRunner versions</para>
- <section xml:id="staffclientinstallation-remove-xulrunner">
- <para>If you already have a newer version installed, per the release notes, you will need to remove the entire directory <emphasis>/Library/Frameworks/XUL.framework</emphasis> before downgrading.</para>
- <para>In addition, you may also need to remove the previous file <emphasis>/Library/Receipts/xulrunner-ver-mak.pkg</emphasis>.</para>
- <para>If there is no file <emphasis>/Library/Receipts/xulrunner-ver-mak.pkg</emphasis> (possibly in newer OSX releases) you need to flush the <emphasis>receiptdb</emphasis> file.</para>
- <note>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.</note>
- <para>First, get the package identifier, then purge/forget the build that was initially installed:</para>
- <figure>
- <title>Purging previous build</title>
- <screen>
sudo pkgutil --pkgs > /tmp/pkgs.txt
sudo pkgutil --forget org.mozilla.xulrunner
</screen>
- </figure>
- <note>It may not be necessary to edit the file <emphasis>/Library/Receipts/InstallHistory.plist</emphasis> after deleting the folder <emphasis>XUL.framework</emphasis>.</note>
- </section>
- </listitem>
- <listitem>
- <para>Creating an APP file: Staff Client & XULRunner Bundled</para>
-
<para>An APP file is basically a folder. Start with a folder stucture like this:</para>
- <figure>
- <title>Sample APP file folder structure</title>
- <screen>
+ </figure>
+ <note>It may not be necessary to edit the file <filename>/Library/Receipts/InstallHistory.plist</filename> after deleting the folder <filename class="directory">XUL.framework</filename>. See <ulink url="http://lists.apple.com/archives/Installer-dev/2009/Jul/msg00008.html">http://lists.apple.com/archives/Installer-dev/2009/Jul/msg00008.html</ulink> for more information.</note>
+ </section>
+ </section>
+ <section>
+ <title>Creating an APP file: Staff Client & XULRunner Bundled</title>
+ <para>An APP file is basically a folder. Start with a folder stucture like this:</para>
+ <figure>
+ <title>Sample APP file folder structure</title>
+ <screen>
* Evergreen.app
* Contents
* Frameworks
* Resources
* MacOS
</screen>
- </figure>
-
<para>Create an APP folder structure with the following commands:</para>
- <figure>
- <title>Creating a folder structure</title>
- <screen>
+ </figure>
+ <para>Create an APP folder structure with the following commands:</para>
+ <figure>
+ <title>Creating a folder structure</title>
+ <screen>
mkdir -p Evergreen.app/Contents/Frameworks
mkdir -p Evergreen.app/Contents/Resources
mkdir -p Evergreen.app/Contents/MacOS
</screen>
- </figure>
- <orderedlist>
- <listitem>
- <para>Create a new file in the folder <emphasis>Evergreen.app/Contents/Info.plist</emphasis> containing the following data (adjust for your version of Evergreen):</para>
- <figure>
- <title>Creating a new file</title>
- <screen>
- <?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_7</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_7</string>
- <key>CFBundleVersion</key>
- <string>rel_1_6_0_7.rel_1_6_0_7</string>
- <key>NSAppleScriptEnabled</key>
- <true/>
- <key>CFBundleTypeIconFile</key>
- <string>Evergreen.icns</string>
- </dict>
- </plist>
- </screen>
- </figure>
- </listitem>
- <listitem>Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (see above for recommendations).</listitem>
- <listitem>
- <para>Make a copy of <emphasis>/Library/Frameworks/XUL.Framework</emphasis> inside your APP file. It should look something like this:</para>
- <figure>
- <title>Example of APP file framework</title>
- <screen>
+ </figure>
+ <para/>
+ <orderedlist>
+ <listitem>
+ <para>Create a new file in the folder <filename class="directory">Evergreen.app/Contents/Info.plist</filename> containing the following data (adjust for your version of Evergreen):</para>
+ <figure>
+ <title>Creating a new file</title>
+ <programlisting language="xml"><![CDATA[
+<?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_7</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_7</string>
+ <key>CFBundleVersion</key>
+ <string>rel_1_6_0_7.rel_1_6_0_7</string>
+ <key>NSAppleScriptEnabled</key>
+ <true/>
+ <key>CFBundleTypeIconFile</key>
+ <string>Evergreen.icns</string>
+</dict>
+</plist>
+]]></programlisting>
+ </figure>
+ </listitem>
+ <listitem>Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (see above for recommendations).</listitem>
+ <listitem>
+ <para>Make a copy of the folder <filename class="directory">/Library/Frameworks/XUL.Framework</filename> inside your APP file. It should look something like this:</para>
+ <figure>
+ <title>Example of APP file framework</title>
+ <screen>
* Evergreen.app/
__* Contents/
____* Frameworks/
______* libxpcom.dylib -> Versions/Current/libxpcom.dylib
______* xulrunner-bin -> Versions/Current/xulrunner-bin
</screen>
- </figure>
- </listitem>
- <listitem>Copy <emphasis>XUL.Framework/Versions/Current/xulrunner</emphasis> into <emphasis>Evergreen.app/MacOS</emphasis> (do not symlink; copy the file).</listitem>
- <listitem>
- <para>Make <emphasis>Evergreen.app/Resources</emphasis> the root of your Evergreen application files like this:</para>
- <figure>
- <title>Example APP file</title>
- <screen>
+ </figure>
+ </listitem>
+ <listitem>Copy <filename>XUL.Framework/Versions/Current/xulrunner</filename> into the folder <filename class="directory">Evergreen.app/MacOS</filename> (do not symlink; copy the file).</listitem>
+ <listitem>
+ <para>Make <filename>Evergreen.app/Resources</filename> the root of your Evergreen application files like this:</para>
+ <figure>
+ <title>Example APP file</title>
+ <screen>
* Evergreen.app/
__* Contents/
____* Resources/
______* components/
______* etc.
</screen>
- </figure>
- </listitem>
- <listitem>Put a Mac format icon file named <emphasis>Evergreen.icns</emphasis> in Resources.</listitem>
- </orderedlist>
- </listitem>
- </itemizedlist>
+ </figure>
+ </listitem>
+ <listitem>Put a Mac format icon file named <filename>Evergreen.icns</filename> in Resources.</listitem>
+ </orderedlist>
+ </section>
</section>
<section xml:id="staffclientinstallation-staffclient-linux">
<title>Installing on Linux</title>
<section>
<title>Quick Upgrade of the Staff Client</title>
<para>A Linux Staff Client is automatically built on the server as part of the normal <emphasis>make install</emphasis> 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.</para>
- <para>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.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then recursively copy the entire directory tree to the remote workstation:</para>
+ <para>The following example assumes you already have an <systemitem class="username">opensrf</systemitem> 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.</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then recursively copy the entire directory tree to the remote workstation:</para>
<figure>
<title>Copying the Staff Client to a remote workstation</title>
<screen>
$ scp -r build user@client.linux.machine:~/eg-client-x.x.x.x/
</screen>
</figure>
- <para>To test the newly copied Staff Client, as the <emphasis role="bold">opensrf</emphasis> user log into the remote workstation and execute it as shown:</para>
+ <para>To test the newly copied Staff Client, as the <systemitem class="username">opensrf</systemitem> user log into the remote workstation and execute it as shown:</para>
<figure>
<title>Testing the copied Staff Client</title>
<screen>
</section>
<section>
<title>Building the Staff Client on the Server</title>
- <para>A Linux Staff Client is automatically built on the server as part of the normal <emphasis>make install</emphasis> process for Evergreen server-side software.</para>
- <para>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.</para>
- <para>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.</para>
+ <para>A Linux Staff Client is automatically built on the server as part of the normal <emphasis>make install</emphasis> process for Evergreen server-side software, using a procedure similar to this:</para>
+ <figure>
+ <title>Building the Staff Client on the Server</title>
+ <screen>
+ $ 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/
+ </screen>
+ </figure>
+ <para>The Staff Client can be run from the build directory using this command:</para>
+ <figure>
+ <title>Running the Staff Client on the Server</title>
+ <screen>
+ $ su - opensrf
+ $ xulrunner application.ini
+ </screen>
+ </figure>
+ <para>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.</para>
+ <para>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 <guibutton>About this Client</guibutton> on the running Staff Client.</para>
<para>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.</para>
<figure>
<title>Creating a symbolic link</title>
<procedure>
<step>
<para>Prerequisites</para>
- <para>Both "subversion" and "xulrunner" are required to build the Staff Client. As the <emphasis role="bold">root</emphasis> 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 <emphasis>1.8.1.4-2ubuntu5</emphasis>.</para>
+ <para>Both <application>subversion</application> and <application>xulrunner</application> are required to build the Staff Client. As the <systemitem class="username">root</systemitem> user, use <command>apt-get</command> to install packages for <application>subversion</application> and <application>xulrunner</application>. You can also use <command>synaptic</command>, the graphical user interface for <command>apt-get</command>. For <application>subversion</application>, select the latest version; for <application>xulrunner</application>, select version <emphasis>1.8.1.4-2ubuntu5</emphasis>.</para>
<figure>
<title>Installing subversion and xulrunner</title>
<screen>
</listitem>
<listitem>
<para>Download the Code</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> 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:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> 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:</para>
<figure>
<title>Downloading the source code</title>
<screen>
<listitem>
<para>Evergreen 1.2.x</para>
<para>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.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, run the following commands to build the Staff Client:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, run the following commands to build the Staff Client:</para>
<figure>
<title>Finding the downloaded source code</title>
<screen>
<listitem>
<para>Evergreen 1.4.x</para>
<para>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:</para>
- <caution>FIXME -- Need instructions for getting certain Javascript files from OpenSRF, preferably without actually installing OpenSRF.
-</caution>
+ <caution>FIXME -- Need instructions for getting certain Javascript files from OpenSRF, preferably without actually installing OpenSRF.</caution>
<figure>
<title>Building 1.4.x</title>
<screen>
- $ 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
- $ cd Evergreen-ILS-1.4.0.4/
- $ ./configure --prefix=/openils --sysconfdir=/openils/conf
- $ cd Open-ILS/xul/staff_client/
- $ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install
- </screen>
+ $ 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
+ $ cd Evergreen-ILS-1.4.0.4/
+ $ ./configure --prefix=/openils --sysconfdir=/openils/conf
+ $ cd Open-ILS/xul/staff_client/
+ $ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install
+ </screen>
</figure>
<para/>
<para>If you're installing from a Subversion checkout:</para>
</step>
<step>
<para>Run the Staff Client (from the command line)</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, navigate to the <emphasis>build/</emphasis> subdirectory (not <emphasis>staff_client/</emphasis>) and run the following command:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, navigate to the <filename class="directory">build/</filename> subdirectory (not <filename class="directory">staff_client/</filename>) and run the following command:</para>
<figure>
<title>Running the Staff Client</title>
<screen>
</step>
<step>
<para>(OPTIONAL) Cleaning Up / Creating Shortcuts</para>
- <para>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:</para>
+ <para>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. As the <systemitem class="username">opensrf</systemitem> user, issue the following commands to create a clean "staging" directory in which to place the finished Staff Client, and to copy into it the "staff_client" directory:</para>
<figure>
<title>Creating a "staging" directory</title>
<screen>
+ $ su - opensrf
$ mkdir ~/<Destination Directory>
$ cd ~/<Download Directory>/Open-ILS/xul/
$ cp -r staff_client ~/<Destination Directory>
$ rm -r -f ~/<Download Directory>
</screen>
</figure>
- <para>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:</para>
- <figure>
- <title>Running the copied Staff Client</title>
- <screen>
- $ xulrunner ~/<Destination Directory>/staff_client/build/application.ini
- </screen>
- </figure>
+ <para>You may wish to create <menuchoice><guimenu>Desktop</guimenu><guimenuitem>Start Menu</guimenuitem><guimenuitem>K-Menu</guimenuitem></menuchoice> shortcuts for the Staff Client using the command <literal>xulrunner ~/<Destination Directory>/staff_client/build/application.ini</literal> as the target.</para>
</step>
</procedure>
</section>
<section>
<title>Using Wine to Install On Linux</title>
- <para>The Linux application <
emphasis>Wine</emphasis> 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 <ulink url="http://www.winehq.org/site/docs/wineusr-guide/getting-wine">http://www.winehq.org/site/docs/wineusr-guide/getting-wine</ulink>.</para>
- <para>As the <emphasis role="bold">root</emphasis> user, use "apt-get" to install the package for "wine". You can also use "synaptic", the graphical user interface.</para>
+ <para>The Linux application <
application>Wine</application> is another alternative if you 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 <ulink url="http://www.winehq.org/site/docs/wineusr-guide/getting-wine">http://www.winehq.org/site/docs/wineusr-guide/getting-wine</ulink>.</para>
+ <para>As the <systemitem class="username">root</systemitem> user, use <command>apt-get</command> to install the package for <application>Wine</application>. You can also use <command>synaptic</command>, the graphical user interface.</para>
<orderedlist>
<listitem>
<para>Install wine</para>
</listitem>
<listitem>
<para>Download Windows installer for the Staff Client</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, run the following commands to download the Windows installer for the proper Staff Client from the <emphasis>open-ils.org</emphasis> website and place it in a temporary directory:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, run the following commands to download the Windows installer for the proper Staff Client from the <ulink url="http://open-ils.org">open-ils.org</ulink> website and place it in a temporary directory:</para>
<figure>
<title>Downloading the Staff Client installer</title>
<screen>
</listitem>
<listitem>
<para>Run the downloaded Windows installer</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, navigate to the directory where you downloaded the Windows executable file, then execute it:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, navigate to the directory where you downloaded the Windows executable file, then execute it:</para>
<figure>
<title>Using Wine to run the Windows installer</title>
<screen>
$ wine evergreen-setup-rel_version-number.exe
</screen>
</figure>
- <para>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".</para>
+ <para>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 <guibutton>Apply</guibutton>.</para>
</listitem>
<listitem>
<para>Launch the Staff Client</para>
</textobject>
</mediaobject>
</figure>
- <para>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:</para>
+ <para>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 their 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:</para>
<figure>
<title>Example of configured Staff Client</title>
<mediaobject>
</textobject>
</mediaobject>
</figure>
- <para>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 <emphasis role="bold">Register</emphasis>.</para>
+ <para>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 click <guibutton>Register</guibutton>.</para>
<para>Once you have registered your workstation with the server, your screen will look like this:</para>
<figure>
<title>Example of registered Staff Client</title>
</textobject>
</mediaobject>
</figure>
- <para>You are now ready to log into the Staff Client for the first time. Type in your password again, and hit <emphasis role="bold">Login</emphasis>.</para>
+ <para>You are now ready to log into the Staff Client for the first time. Type in your password again, and click <guibutton>Login</guibutton>.</para>
</section>
</section>
</simplesect>
<para>The Staff Client is automatically built by default as part of the normal <emphasis>make install</emphasis> process for Evergreen server-side software. See the section <xref linkend="serversideinstallation-compilingevergreen"/> to review details related to building the Staff Client in the final compile/link/install phase of the default Evergreen build process.</para>
<section>
<title>Building the Staff Client</title>
- <para>You can also manually build the Staff Client by using the <emphasis>make</emphasis> utility in the Staff Client source directory (e.g., the directory <emphasis>/home/opensrf/Evergreen-ILS-1.6.0.x/Open-ILS/xul/staff_client</emphasis> 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 <emphasis>make</emphasis> to influence the manual build process:</para>
+ <para>You can also manually build the Staff Client by using the <command>make</command> utility in the Staff Client source directory (e.g., the directory <filename class="directory">/home/opensrf/Evergreen-ILS-1.6.0.x/Open-ILS/xul/staff_client</filename> 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 <command>make</command> to influence the manual build process:</para>
<section>
<title>Option STAFF_CLIENT_BUILD_ID</title>
<para>During the normal <emphasis>make install</emphasis> 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.</para>
</screen>
</figure>
<para>The following commands will manually build the Staff Client using a different BUILD_ID.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
<figure>
<title>Commands to manually build the Staff Client</title>
<screen>
</figure>
<para>The following commands will manually build the Staff Client using a different VERSION.</para>
<para>If you plan to make extensions update automatically, the VERSION needs to conform to the format recommended in <ulink url="https://developer.mozilla.org/en/Toolkit_version_format">Toolkit Version Format</ulink> and newer versions need to be "higher" than older versions.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
<figure>
<title>Commands to manually build the Staff Client</title>
<screen>
</figure>
<para>The following commands will manually build the Staff Client using a different STAMP_ID.</para>
<para>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.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
<figure>
<title>Commands to manually build the Staff Client</title>
<screen>
</section>
<section>
<title>Advanced Build Options</title>
- <para>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 <emphasis>make</emphasis> utility and require that you build the Staff Client from its source directory. See the following table for a list of possible <emphasis>make</emphasis> target keywords:</para>
+ <para>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 <command>make</command> utility and require that you build the Staff Client from its source directory. See the following table for a list of possible <command>make</command> target keywords:</para>
<table>
<title>Keywords Targets for "make" Command</title>
<tgroup align="left" cols="2" colsep="1" rowsep="1">
<itemizedlist>
<listitem>
<para>Developer Build</para>
- <para>You can create a so-called "developer build" of the Staff Client by substituting "devbuild" for "build" when running <emphasis>make</emphasis>. The build will contain an extra configuration file that enables some developer options.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, run <emphasis>make</emphasis> from the Staff Client source directory:</para>
+ <para>You can create a so-called "developer build" of the Staff Client by substituting "devbuild" for "build" when running <command>make</command>. The build will contain an extra configuration file that enables some developer options.</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, run <command>make</command> from the Staff Client source directory:</para>
<figure>
<title>Commands to do a "developer build"</title>
<screen>
</listitem>
<listitem>
<para>Compressed Javascript</para>
- <para>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 <
emphasis>make</emphasis>. For more information see <ulink url="http://code.google.com/closure/compiler/">Google "Closure Compiler"</ulink>.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, run the following commands from the Staff Client source directory:</para>
+ <para>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 <
command>make</command>. For more information see <ulink url="http://code.google.com/closure/compiler/">Google "Closure Compiler"</ulink>.</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, run the following commands from the Staff Client source directory:</para>
<figure>
<title>Commands to compress Javascript</title>
<screen>
</screen>
</figure>
<para>You can also combine Javascript review and compression, and also perform a "developer build".</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, run the following commands from the Staff Client source directory:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, run the following commands from the Staff Client source directory:</para>
<figure>
<title>Commands to compress Javascript and do a "developer build"</title>
<screen>
</screen>
</figure>
<para>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.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:</para>
<figure>
<title>Commands to manually specify AUTOUPDATE_HOST</title>
<screen>
<section>
<title>Installing and Activating a Manually Built Staff Client</title>
<para>The Staff Client is automatically built, installed and activated as part of the normal <emphasis>make install</emphasis> 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.</para>
- <para>Assuming you have already built the Staff Client, and that your installation is in the directory <emphasis>/openils/var/web/xul</emphasis>, as the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>Assuming you have already built the Staff Client, and that your installation is in the directory <filename class="directory">/openils/var/web/xul</filename>, as the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands to install the Staff Client on the same machine</title>
<screen>
</section>
<section>
<title>Packaging the Staff Client</title>
- <para>Once the Staff Client has been built, you can create several forms of client packages by using some targetted <emphasis>make</emphasis> commands in the Staff Client source directory.</para>
+ <para>Once the Staff Client has been built, you can create several forms of client packages by using some targetted <command>make</command> commands in the Staff Client source directory.</para>
<itemizedlist>
<listitem>
<para>Packaging a Generic Client</para>
- <para>This build creates a Staff Client packaged as an XPI file to use with <emphasis>XULRunner</emphasis>. 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 <emphasis>XULRunner</emphasis> parameter <emphasis>--install-app</emphasis>.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>This build creates a Staff Client packaged as an XPI file to use with <application>xulrunner</application>. 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 <application>xulrunner</application> parameter <emphasis>--install-app</emphasis>.</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands to package a "generic" client</title>
<screen>
<listitem>
<para>Packaging a Windows Client</para>
<para>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 <ulink url="http://nsis.sourceforge.net/">NSIS (Nullsoft Scriptable Install System)</ulink>, 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".</para>
- <para>(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 <emphasis>xulrunner-stub.exe</emphasis>. Place it in the Staff Client source directory and <emphasis>make</emphasis> will automatically use it instead of the one that comes with the downloaded <emphasis>XULRunner</emphasis> release. The version of <emphasis>xulrunner-stub.exe</emphasis> need not match exactly.</para>
+ <para>(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 <application>xulrunner-stub.exe</application>. Place it in the Staff Client source directory and <command>make</command> will automatically use it instead of the one that comes with the downloaded <application>XULRunner</application> release. The version of <application>xulrunner-stub.exe</application> need not match exactly.</para>
<para>(OPTIONAL) You can also use a tool such as <ulink url="http://www.angusj.com/resourcehacker/">Resource Hacker</ulink> 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:</para>
<table>
<title>Useful icon ID strings</title>
</tbody>
</tgroup>
</table>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands to build a Windows client</title>
<screen>
</listitem>
<listitem>
<para>Packaging a Linux Client</para>
- <para>This build creates a Staff Client package for Linux as a "tar.bz2" file with <emphasis>XULRunner</emphasis> already bundled with it. It creates the output file "evergreen_staff_client.tar.bz2".</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>This build creates a Staff Client package for Linux as a "tar.bz2" file with <application>XULRunner</application> already bundled with it. It creates the output file "evergreen_staff_client.tar.bz2".</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands to build a Linux client</title>
<screen>
<listitem>
<para>Packaging a Firefox Extension</para>
<para>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".</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands to build a Firefox extension</title>
<screen>
<para>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.</para>
<section>
<title>WARNINGS</title>
- <para>Automatic update server certificate requirements are more strict than normal server requirements. Firefox and <emphasis>XULRunner</emphasis> 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 <emphasis>WILL NOT WORK</emphasis>.</para>
- <para>In addition, automatic updates have special requirements for the file <emphasis>update.rdf</emphasis>:</para>
+ <para>Automatic update server certificate requirements are more strict than normal server requirements. Firefox and <application>XULRunner</application> 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 <emphasis>WILL NOT WORK</emphasis>.</para>
+ <para>In addition, automatic updates have special requirements for the file <filename>update.rdf</filename>:</para>
<orderedlist>
<listitem>It must be served from an SSL server, or</listitem>
<listitem>It must be signed with the <ulink url="https://developer.mozilla.org/en/McCoy">McCoy</ulink> tool.</listitem>
</orderedlist>
- <para>You can pre-install the signing key into the file <emphasis>install.rdf</emphasis> directly, or install it into a copy as <emphasis>install.mccoy.rdf</emphasis>. If the latter exists it will be copied into the build instead of the original file <emphasis>install.rdf</emphasis>.</para>
+ <para>You can pre-install the signing key into the file <filename>install.rdf</filename> directly, or install it into a copy as <filename>install.mccoy.rdf</filename>. If the latter exists it will be copied into the build instead of the original file <filename>install.rdf</filename>.</para>
</section>
<section>
<title>Autoupdate Host</title>
<itemizedlist>
<listitem>
<para>At configuration time for the normal build of Evergreen server-side software</para>
- <para>This must be done when the Evergreen server-side software is first configured (see the section <xref linkend="serversideinstallation-configure"/>). As the <emphasis role="bold">opensrf</emphasis> user, use the utility "configure" as shown:</para>
+ <para>This must be done when the Evergreen server-side software is first configured (see the section <xref linkend="serversideinstallation-configure"/>). As the <systemitem class="username">opensrf</systemitem> user, use the utility "configure" as shown:</para>
<figure>
<title>Commands to configure Evergreen</title>
<screen>
</section>
<section>
<title>Building Updates</title>
- <para>Similar to building clients, the targets "generic-updates", "win-updates", "linux-updates", and "extension-updates" can be used individually with <emphasis>make</emphasis> to build the update files for the Staff Client. To build all the targets at once, simply use the target "updates".</para>
- <para>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 <emphasis>/openils/var/updates/archives</emphasis>) 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.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>Similar to building clients, the targets "generic-updates", "win-updates", "linux-updates", and "extension-updates" can be used individually with <command>make</command> to build the update files for the Staff Client. To build all the targets at once, simply use the target "updates".</para>
+ <para>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 <filename class="directory">/openils/var/updates/archives</filename>) 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.</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands for building updates</title>
<screen>
<title>Building updates with clients</title>
<para>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.</para>
<para>The clients will be installed alongside the updates and listed on the "manualupdate.html" page, rather than left in the Staff Client directory.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Commands for building updates with clients</title>
<screen>
<section>
<title>Activating the Update Server</title>
<para>This section reviews scripts associated with the update server, and requires some final adjustments to file permissions.</para>
- <para>The Apache example configuration creates an "updates" directory that, by default, points to the directory <emphasis>/openils/var/updates/pub</emphasis>. This directory contains one HTML file and several specially-named script files.</para>
- <para>The "updatedetails.html" file is the fallback web page for the update details. The "check" script is used for <emphasis>XULRunner</emphasis> 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).</para>
- <para>The following scripts should be marked as executable: <emphasis>check, download, manualupdate.html, update.rdf</emphasis>. As the <emphasis role="bold">root</emphasis> user, change directory to the updates directory, then execute the following commands:</para>
+ <para>The Apache example configuration creates an "updates" directory that, by default, points to the directory <filename class="directory">/openils/var/updates/pub</filename>. This directory contains one HTML file and several specially-named script files.</para>
+ <para>The "updatedetails.html" file is the fallback web page for the update details. The "check" script is used for <application>XULRunner</application> 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).</para>
+ <para>The following scripts should be marked as executable: <command>check, download, manualupdate.html, update.rdf</command>. As the <systemitem class="username">root</systemitem> user, change directory to the updates directory, then execute the following commands:</para>
<figure>
<title>Changing file permissions of scripts</title>
<screen>
<title>Other tips</title>
<section>
<title>Multiple workstations on one install</title>
- <para>Multiple workstation registrations for the same server can be accomplished with a single Staff Client install by using multiple profiles. When running <emphasis>XULRunner</emphasis> 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.</para>
+ <para>Multiple workstation registrations for the same server can be accomplished with a single Staff Client install by using multiple profiles. When running <application>XULRunner</application> 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.</para>
<para>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.</para>
<para>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.</para>
- <para>As the <emphasis role="bold">opensrf</emphasis> user, change directory to the Staff Client source directory, then execute the following commands:</para>
+ <para>As the <systemitem class="username">opensrf</systemitem> user, change directory to the Staff Client source directory, then execute the following commands:</para>
<figure>
<title>Command to add start menu option</title>
<screen>
<section>
<title> Multiple Staff Clients</title>
<para>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).</para>
- <para>Once you have created the profiles, run <emphasis>XULRunner</emphasis> with the option "-no-remote" (in addition to "-profilemanger" or "-P" if neeeded). Instead of <emphasis>XULRunner</emphasis> 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.</para>
+ <para>Once you have created the profiles, run <application>XULRunner</application> with the option "-no-remote" (in addition to "-profilemanger" or "-P" if neeeded). Instead of <application>XULRunner</application> 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.</para>
</section>
</section>
</simplesect>
</section>
<section xml:id="staffclientinstallation-running-staffclient">
<title>Running the Staff Client</title>
- <para>Run the Staff Client on a Linux system by using the application <emphasis>XULRunner</emphasis> (installed automatically and by default with Firefox version 3.0 and later on Ubuntu and Debian distributions).</para>
- <para>For example, if the source files for the Evergreen installation are in the directory <emphasis>/home/opensrf/Evergreen-ILS-1.6.0.7/</emphasis>, start the Staff Client as shown in the following command example:</para>
+ <para>Run the Staff Client on a Linux system by using the application <application>XULRunner</application> (installed automatically and by default with Firefox version 3.0 and later on Ubuntu and Debian distributions).</para>
+ <para>For example, if the source files for the Evergreen installation are in the directory <filename class="directory">/home/opensrf/Evergreen-ILS-1.6.0.7/</filename>, start the Staff Client as shown in the following command example:</para>
<figure>
<title>Commands to run the Staff Client</title>
<screen>
<para>There are several reasons for sending network traffic for the Staff Client through an SSH proxy:</para>
<itemizedlist>
<listitem>
- <para><emphasis role="bold">Firewalls</emphasis> may prevent you from reaching the server. This may happen when you are connecting the Staff Client to a test server that should not be available generally, or it may be the result of network design priorities other than ease of use.</para>
+ <para>Firewalls may prevent you from reaching the server. This may happen when you are connecting the Staff Client to a test server that should not be available generally, or it may be the result of network design priorities other than ease of use.</para>
</listitem>
<listitem>
- <para>You may wish to <emphasis role="bold">improve security</emphasis> where Staff Client traffic may be susceptible to network eavesdropping. This is especially true when wireless is otherwise the best option for connecting a staff machine to the network.</para>
+ <para>You may wish to improve security where Staff Client traffic may be susceptible to network eavesdropping. This is especially true when wireless is otherwise the best option for connecting a staff machine to the network.</para>
</listitem>
</itemizedlist>
</section>
<listitem>Use the menu on the left to go to Connection > SSH > Tunnels.</listitem>
<listitem>Enter ''9999'' in the "Source port".</listitem>
<listitem>Choose "Dynamic". Do not enter anything in the Destination text entry box.</listitem>
- <listitem>Click the "Add" button. "D9999" will now appear in the "Forwarded ports" list.</listitem>
+ <listitem>Click <guibutton>Add</guibutton>; "D9999" will now appear in the "Forwarded ports" list.</listitem>
<listitem>Use the menu on the left to go back to "Session", and enter the host name of the SSH server.</listitem>
<listitem>A window will open up so that you can enter your username and password. Once you are logged in, the tunnel is open.</listitem>
</orderedlist>
</section>
<section>
<title>Configuring the Staff Client to Use the SSH Tunnel</title>
- <para>In order to tell the Staff Client that all traffic should be sent through the SSH tunnel just configured, you must edit the file <emphasis>C:\Program Files\Evergreen Staff Client\greprefs\all.js</emphasis>. Search this file for the word <emphasis role="bold">socks</emphasis> to find the appropriate section for the following changes.</para>
+ <para>In order to tell the Staff Client that all traffic should be sent through the SSH tunnel just configured, you must edit the file <filename>C:\Program Files\Evergreen Staff Client\greprefs\all.js</filename>. Search this file for the word <literal>socks</literal> to find the appropriate section for the following changes.</para>
<figure>
<title>The SOCKS section of "all.js" before changes</title>
<mediaobject>
</figure>
<para>Make the following changes:</para>
<itemizedlist>
- <listitem>Change the value of <emphasis>network.proxy.socks</emphasis> from <emphasis role="bold">""</emphasis> to <emphasis role="bold">"localhost"</emphasis>.</listitem>
- <listitem>Change the value of <emphasis>network.proxy.socks_port</emphasis> from <emphasis role="bold">"0"</emphasis> to <emphasis role="bold">9999</emphasis>.</listitem>
+ <listitem>Change the value of <literal>network.proxy.socks</literal> from <literal>""</literal> to <literal>localhost</literal>.</listitem>
+ <listitem>Change the value of <literal>network.proxy.socks_port</literal> from <literal>0</literal> to <literal>9999</literal>.</listitem>
</itemizedlist>
<figure xml:id="staffclientinstallation-socks-figure">
<title>The SOCKS section of "all.js" after changes</title>
projects / contrib / Conifer.git / commitdiff