1 |
Background |
Background |
2 |
|
|
3 |
What is the DGEE |
What is the DGEE |
4 |
|
The DotGNU Execution Environment is an application framework for managing the |
5 |
|
execution of Webservices (and in the future other web-applications) for the |
6 |
|
DotGNU system. |
7 |
|
|
8 |
What is Goldwater |
What is Goldwater |
9 |
Goldwater is distributed message based middleware. It is highly scalable and |
Goldwater is distributed message based middleware. It is highly scalable and |
10 |
allows applications written with it to be distributed across multiple machines. |
allows applications written with it to be distributed across multiple machines. |
11 |
It ties the components of the DGEE together. |
It is used to tie the components of the DGEE together, performing request |
12 |
|
and reply queueing, load balancing, process sandboxing and resource management. |
13 |
|
|
14 |
|
|
15 |
Trouble at the top |
Trouble at the top |
16 |
|
Here we assume that the dgee was installed under /usr/local.... |
17 |
|
|
18 |
The DGEE fails to start, gives a message "Goldwater not started" |
The DGEE fails to start, gives a message "Goldwater not started" |
19 |
|
There are two phases to starting the DGEE. First is to start and instance of |
20 |
|
the Goldwater middleware, Second is to boot the DGEE application within that |
21 |
|
Goldwater instance. |
22 |
|
These two steps may be performed in one go by running the dgeestart script. |
23 |
|
|
24 |
Where do I find the logfiles |
Where do I find the logfiles |
25 |
|
The logfiles will be found as: |
26 |
|
The DGEE log: /usr/local/var/log/dgee/dgee.log |
27 |
|
Any STDOUT : /usr/local/var/log/dgee/stdout |
28 |
|
Any STDERR : /usr/local/var/log/dgee/stderr |
29 |
|
|
30 |
|
The user that the DGEE is configured to run as must have write permissions |
31 |
|
to the /usr/local/var/log/dgee directory. If permission is denied, then |
32 |
|
the Goldwater middleware will fail to start and complain loudly. |
33 |
|
|
34 |
|
Where is the master DGEE configuration file, and how do I change it? |
35 |
|
The master DGEE configuration file can be found at /usr/local/etc/dgeeconf.xml |
36 |
|
It defines where the logfiles are, where DGEE server processes are etc. If |
37 |
|
you change any of these resources, then you need to recompile the configuration. |
38 |
|
Make sure GWCONFIG is set to point to the binary version of the config file: |
39 |
|
export GWCONFIG=/usr/local/etc/dgeeconf.bin |
40 |
|
|
41 |
|
and compile it with gwmkcfg |
42 |
|
shell> gwmkcfg /usr/local/etc/dgeeconf.xml |
43 |
|
|
44 |
|
|
45 |
I get an "Invalid user/group name" when starting the DGEE, why? |
I get an "Invalid user/group name" when starting the DGEE, why? |
46 |
|
The dgee is configured with the username and groupname of someone to run as. |
47 |
|
When run as root, the DGEE immediately becomes that user. |
48 |
|
Have a look at the dgeeconf.xml file (see above) and check the user and group |
49 |
|
entries against your /etc/passwd and /etc/group files. |
50 |
|
The DGEE should be configured to run as the same user as Apache (if you're |
51 |
|
using apache) - if not, either reinstall the DGEE or edit the dgeeconf.xml |
52 |
|
manually and change the user and group entries to something valid. Don't |
53 |
|
forget to recompile the dgeeconf.xml file as described above. |
54 |
|
|
55 |
How do I see what has started? |
How do I see what has started? |
56 |
|
The DGEE server processes will report their startup to the screen as they |
57 |
|
boot. Such information is also written to the dgee logfile. |
58 |
|
You can make a manual inspection at any time through the Goldwater |
59 |
|
administration tool. |
60 |
|
Run dgadmin (this sets up the environment properly and then invokes Goldwater). |
61 |
|
and use the 'pl' command to list the Goldwater processes booted: |
62 |
|
|
63 |
|
shell> dgadmin |
64 |
|
Welcome to the Goldwater Administrator (version 1.1.20) |
65 |
|
(c) 2003 Free Software Foundation, Inc. |
66 |
|
|
67 |
|
Type 'help' or '?' for a list of commands. |
68 |
|
|
69 |
|
dotGNU DGEE> pl |
70 |
|
Currently booted servers: |
71 |
|
|
72 |
|
Server Class ID Domain/Node Pid Done FRst Status |
73 |
|
-------------- ------ ------ --------------- ----- ------- ---- --------------- |
74 |
|
guardian 1 1 DotGnuLocal 29008 12 0 Ready |
75 |
|
DGSvcMgr 100 100 DotGnuLocal 29011 1 0 Ready |
76 |
|
DGSvcMgr 100 101 DotGnuLocal 29012 0 0 Ready |
77 |
|
DGSvcMgr 100 102 DotGnuLocal 29013 0 0 Ready |
78 |
|
DGResMgr 200 200 DotGnuLocal 29014 1 0 Ready |
79 |
|
DGResMgr 200 201 DotGnuLocal 29015 0 0 Ready |
80 |
|
DGResMgr 200 202 DotGnuLocal 29016 0 0 Ready |
81 |
|
DGpnetVM 400 400 DotGnuLocal 29017 0 0 Ready |
82 |
|
DGpnetVM 400 401 DotGnuLocal 29018 0 0 Ready |
83 |
|
DGpnetVM 400 402 DotGnuLocal 29019 0 0 Ready |
84 |
|
|
85 |
|
10 servers listed from a total of 10 booted. |
86 |
|
|
87 |
|
dotGNU DGEE> |
88 |
|
|
89 |
|
|
90 |
How do I see how many requests have been processed? |
How do I see how many requests have been processed? |
91 |
|
The 'Done' column of the Goldwater "booted servers" list (above) indicates |
92 |
|
how may service requests each of the DGEE component processes have received. |
93 |
|
For instance, the requests 'Done' by the DGpnetVM processes indicates how many |
94 |
|
times portable.net webservices have been invoked. |
95 |
|
|
96 |
|
|
97 |
How do I stop DGEE components? |
How do I stop DGEE components? |
98 |
|
|
99 |
|
|
100 |
How do I start DGEE components? |
How do I start DGEE components? |
101 |
How do I cycle DGEE components? |
How do I cycle DGEE components? |
102 |
How do I change the log level? |
How do I change the log level? |