Permalink
Browse files

Updated context broker setup docs for 2.3

  • Loading branch information...
1 parent 5e4aeca commit 7f5a911109c67ae9b1bad585fe5df4f1ce8b684c @labisso labisso committed Mar 19, 2010
Showing with 8 additions and 8 deletions.
  1. +8 −8 docs/src/admin/reference.html
@@ -1900,14 +1900,20 @@
enable <a href="../clouds/clusters.html">one click clusters</a>.
</p>
<p>
- The new TP2.2 broker (see <a href="#context-broker">above</a>)
- is installed separately from Nimbus, there is not a
+ The new broker (see <a href="#context-broker">above</a>)
+ is installed by default with Nimbus 2.3, but there is not a
dependency on any Nimbus service component. It can run by itself in a
container. You can use it for deploying virtual clusters on EC2 for
example without any other Nimbus service running (the cloud client #11 has
an "ec2script" option that will allow you to do this).
</p>
<p>
+ If you want to install the broker separately from Nimbus, download the
+ Nimbus source tarball, extract it, and run
+ <i>bin/broker-build-and-install.sh</i> with an appropriate
+ <b>$GLOBUS_LOCATION</b> set.
+</p>
+<p>
To set up a NEW broker that is compatible with post-010 cloud clients,
follow these steps:
</p>
@@ -1944,12 +1950,6 @@
</li>
<li>
<p>
- Install the broker by setting <b>$GLOBUS_LOCATION</b> and then
- running the included <i>deploy-broker.sh</i> script.
- </p>
- </li>
- <li>
- <p>
Navigate to "<i>$GLOBUS_LOCATION/etc/nimbus-context-broker</i>"
and adjust the "caCertPath" and "caKeyPath" parameters in the
"<i>jndi-config.xml</i>" file to point to the CA certificate

0 comments on commit 7f5a911

Please sign in to comment.