summaryrefslogtreecommitdiff
path: root/qpid/packaging/windows/INSTALL_NOTES.html
diff options
context:
space:
mode:
Diffstat (limited to 'qpid/packaging/windows/INSTALL_NOTES.html')
-rw-r--r--qpid/packaging/windows/INSTALL_NOTES.html73
1 files changed, 18 insertions, 55 deletions
diff --git a/qpid/packaging/windows/INSTALL_NOTES.html b/qpid/packaging/windows/INSTALL_NOTES.html
index 0eda0aa2fe..4aecce697a 100644
--- a/qpid/packaging/windows/INSTALL_NOTES.html
+++ b/qpid/packaging/windows/INSTALL_NOTES.html
@@ -1,11 +1,11 @@
<html>
<head>
-<title>Apache Qpid C++ 0.6 Installation Notes</title>
+<title>Apache Qpid C++ 0.9 Installation Notes</title>
</head>
<body>
-<H1>Apache Qpid C++ 0.6 Installation Notes</H1>
+<H1>Apache Qpid C++ 0.9 Installation Notes</H1>
-<p>Thank you for installing the Apache Qpid version 0.6 for Windows kit.
+<p>Thank you for installing Apache Qpid version 0.9 for Windows.
If the requisite features were installed, you can now run a broker,
use the example programs, and design your own messaging programs while
reading the Qpid C++ API reference documentation.</p>
@@ -20,11 +20,10 @@ on the same system as the client, but it must be reachable using TCP/IP.</p>
<p>The broker executable is installed in the <code>bin</code> subdirectory
of your Qpid installation directory. The broker program is
-<code>qpidd.exe</code>. The simplest way to experiment with the
-broker is to open a command prompt window, cd to the installation
-directory, and execute the broker:
+<code>qpidd.exe</code>. The installation procedure adds the Qpid bin
+directory to the PATH environment variable, so the simplest way to experiment
+with the broker is to open a command prompt window and execute the broker:
<pre>
-cd "C:\Program Files\Apache\qpidc-0.6\bin"
qpidd
</pre>
A small amount of information will be displayed to let you know the broker
@@ -65,60 +64,24 @@ channel (C++ Broker Compatible)."</p>
<H1>Notes</H1>
<p>Please read the following sections for important notes regarding this
release.</p>
-<H2>WCF Channel</H2>
-<p>This release includes a new .NET WCF Channel implementation. The WCF DLL
-is named <code>Apache.Qpid.Channel.dll</code> located in the <code>bin</code>
-directory under the Qpid installation location.</p>
-<p>WCF Channel programming examples are located in the
-<code>examples\Channel</code> under the installation directory.</p>
-<p>The WCF Channel DLLs are not loaded into the Global Assembly Cache (GAC)
-at install time; therefore, they must be referenced explicitly from the install
-location.</p>
-<p>If you wish to install the WCF Channel DLLs into the GAC, you can use the
-following commands (assuming the Qpid install location is
-<code>C:\Program Files\Apache\qpidc-0.6</code>):</p>
-<pre>
-gacutil -I "C:\Program Files\Apache\qpidc-0.6\bin\Apache.Qpid.Channel.dll"
-gacutil -I "C:\Program Files\Apache\qpidc-0.6\bin\Apache.Qpid.Interop.dll"
-</pre>
-<p>To remove the DLLs from the GAC:</p>
-<pre>
-gacutil /u "Apache.Qpid.Channel"
-gacutil /u "Apache.Qpid.Interop"
-</pre>
-To use transactions with the WCF channel, you must enable the Microsoft Distributed Transaction Coordinator service and configure it to find and use the Qpid XA transaction module.
-<ul>
-<li>
-Update the PATH environment variable for services:
-right click <i>Computer</i>, select <i>Properties > Advanced System
-Settings > Environment Variables > System Variables</i> and add
-"C:\Program Files\Apache\qpidc-0.6\bin" to the PATH variable.
-<li>
-Following the instructions in
-<a href="http://support.microsoft.com/kb/817066">
-http://support.microsoft.com/kb/817066</a>,
-update the MSDTC security settings to allow XA transactions, and
-create an XADLL registry entry for "qpidxarm" with string (REG_SZ)
-value "C:\Program Files\Apache\qpidc-0.6\bin\qpidxarm.dll"
-<li>
-Open <i>Control Panel > Administrative Tools > Services</i> and start
-(or restart) the DTC service and make sure that the DTC service is set
-to start automatically when the system reboots.
-</ul>
-<H2>Broker Persistence Module</H2>
-<p>This release includes a new persistence module. The broker can use this
+<H2>CLFS-Based Broker Persistence Module</H2>
+<p>This release includes a second persistence module. The broker can use this
module to facilitate durable queues, exchanges, bindings, configuration, and
-messages. The persistence module uses SQL Server Express (or SQL Server) 2005
-or newer. The persistence module is a Qpid broker plugin. It is not loaded by
+messages. The new persistence module, like the SQL-based store introduced in
+Qpid 0.6, uses SQL Server Express (or SQL Server) 2005 or newer. However, it
+also used Common Log File System (CLFS) to store message and transaction-related
+information. CLFS and, thus, the new store, is available on Windows Vista and
+Server 2005 and newer.
+The persistence module is a Qpid broker plugin. It is not loaded by
default; therefore, to gain support for durable items the persistence plugin
must be loaded into the broker. This can be done using the
-<code>--module-dir</code> option to load all available plugins. For example:
+<code>--load-module</code> option to load the needed plugins. For example:
<pre>
-cd "C:\Program Files\Apache\qpidc-0.6"
-bin\qpidd.exe --module-dir plugins\broker
+cd "C:\Program Files\Apache\qpidc-0.9"
+qpidd.exe --load-module plugins\broker\store.dll --load-module plugins\broker\msclfs_store.dll
</pre>
-The <code>--module-dir</code> option can also take a full path. The option
+The <code>--load-module</code> option can also take a full path. The option
can also be included in the broker configuration file. A sample is located
in the <code>conf\qpidd.conf</code> file under the installation directory.</p>