From 84adefa331c4159d432d22840663c38f155cd4c1 Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Fri, 20 Nov 2009 14:54:40 +0000 Subject: The R13B03 release. --- lib/orber/priv/orber_help.txt | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100755 lib/orber/priv/orber_help.txt (limited to 'lib/orber/priv/orber_help.txt') diff --git a/lib/orber/priv/orber_help.txt b/lib/orber/priv/orber_help.txt new file mode 100755 index 0000000000..a6580dc30a --- /dev/null +++ b/lib/orber/priv/orber_help.txt @@ -0,0 +1,42 @@ + + + + Help for the Orber administration tool + -------------------------------------- + + + + + + The purpose of this tool is to supply an easy way to + access Orber nodes and via a GUI explore: + - NameService + - Configuration settings + - Interface Repository + + All nodes that are known to this tool is shown in the node + window, normally this is all Erlang nodes visible with the + [node()|nodes()] commands. + + +The Node window +--------------- + + The node window monitor nodes. + + +Technical Detail +---------------- + + Trouble shooting + ---------------- + + Q. Why doesn't all my nodes show up in the node window? + + A. Are the nodes visible with the [node()|nodes()] commands + in the shell? If not you must do net:ping(NodeName) to add + nodes to the Erlang distribution. + + Q. When trying to access a node I get no valid response? + + A. Make sure that Orber is running on the node. -- cgit v1.2.3