|No abstract provided. Tags: configuration, monitor, process, daemon, access manager, wgattachd, wgated, wgmgrd, command, start, stop, inetd, artcore, artdial
This article describes the primary Lotus
Mobile Connect processes and their purposes: wgattchd, wgated, wgmgrd,
artdial, and artcore.
- wgattachd. The Connection Manager
server process which is responsible for starting, monitoring, and performing
recovery operations on the main driver process. On AIX, the system
resource controller is used to start, manage, and stop the Connection Manager
processes. They can be issued directly from the command line:
startsrc -s wgated
stopsrc -s wgated
lssrc -s wgated
- wgated. The process that is the
main driver of the Connection Manager. If this process is
killed or stops abnormally, the wgattachd process will restart it.
- wgmgrd. The access manager process
that listens for incoming requests from Gatekeeper, accesses the various
external datastores, and sends dynamic update requests to local and remote
wgated processes. This process uses inetd/xinetd as
a catalyst and requires no monitoring. However, it will not work
without the inetd or xinetd process running. To verify that inetd
is functioning and configured properly:
netstat -na | grep 9555
- artdial.exe. The Mobility Client
dialer is started either from a shortcut or from the Mobility Client Connections
folder. The dialer uses the Mobility Client API to drive up the connection
and present the progress of the connection establishment process to users.
The dialer calls various APIs to establish a connection between artcore.exe
and the Connection Manager wgattachd process. After the connection has
been successfully established, artdial.exe exits.
- artcore.exe. The main processing
of the Mobility Client is performed by this process, which is started by
the dialer using the Mobility Client API.