|
Debugging and troubleshooting
|
If Mobilchange doesn't work correctly, you can run some of its component in debug mode. It means component doesn't
run as a service but as a console application which writes messages about its work to the screen. These messages
help you discover where is problem.
Content
- How to run Mobilchange components in debug mode?
- How to set console window to be usable?
- How SMS is processed during sending?
- How SMS is processed during receiving?
- Special debugging options
How to run Mobilchange components in debug mode?
Most of Mobilchange server components can be run in debug mode. In this mode you
can see what component really does or not.
Procedure:
- Stop and disable service to be debugged
- Find EXE file for this service - usually in Mobilchange/bin
- Run EXE file with parameter for debug mode, see table
What you can debug and using which command line:
| Service | EXE name |
| Mobilchange.Kernel | mxkernel.exe debug (all subprocesses writing to the same window 1) |
| Mobilchange.Kernel (out process) | mxkernel.exe out (starts outgoing SMS manager only 2) |
| Mobilchange.Kernel (in process) | mxkernel.exe in (starts incoming SMS manager only 2) |
| Mobilchange.Kernel (line process) | mxkernel.exe line line1 (starts line driver for line1 only 2) |
| Mobilchange.SMS Forward | smsfw.exe |
| SMS Reminder | smsrmnd.exe |
| Mobilchange.Gateway.SMS | mxGwsms2k.exe notserv Mobilchange-Gateway-sms |
| Mobilchange.SmtpPop3 | mxsmtp.exe -d |
| UMS.TaskManager 3) | DSServMngr.exe -debug |
1) equivalent of running bin/0mxKernel!.cmd
2) equivalent of running bin/2mxKernel_multiwindow.cmd - starts all processes, every in its own window
3) see also here
back to top of page
How to set console window to be usable?
Click to icon on upper left corner of command prompt window. Select Properties in displayed menu.
Set Screen Buffer Size - Height parameter on Layout tab to 9999.
Now scrollbar is created at the right window edge and window "remembers" program's output up to 9999 lines. You can
mark all written text and copy it to the clipboard using Edit function in menu under corner icon.
back to top of page
How SMS is processed during sending?
SMS is represented by "control" text file and by one data file in all points of
processing. Control file is common text file editable for example by Notepad.
In mail/in/ and mail/out/ folders first letter determines which gateway should process this file
(e,f = MS Exchange, l = Lotus Notes, s = SMTP/POP3), control file extension is CTL here.
SMS processing runs according this order:
- Gateway gets message from the user and save it to mail/in/ folder.
- Outgoing SMS manager takes message, check user's rights, moves control file to queue/out/lineX (according line, which
will send the message) and data file to queue/text/lineX.
- Line driver searches for queue/out/lineX/*.mx files. If some file is found,
it tries to send SMS referenced by this file. Then the following occurs:
- If sending was successful and operator supports delivery reports, control file is moved to queue/drwait/. It
waits here for delivery report - when it is received, user is sent message about SMS delivery to the MP. If time limit for DR is reached
(no DR is received), user is sent message that SMS was sent, but DR wasn't received.
- If sending was successful and operator doesn't support delivery reports, user gets message that SMS was sent.
- If sending was unsuccessful user gets message that SMS wasn't sent.
back to top of page
How SMS is processed during receiving?
Technology of control files etc. is the same as during SMS sending.
- Line driver receives SMS and stores it to queue/in/.
- Incoming SMS manager takes these files and searches for message recipients - see here.
- If message is adressed to the mail recipient, it is send him by saving it to mail/out/.
back to top of page
Special debugging options
Some services can be debugged without necessity to running in debug mode. You can direct service to create logfile
via registry editing, then restart service.
- Mobilchange.Kernel
Kernel logging is described in this KB document.
- Mobilchange.SMS Forward
SMS Forward logging is described here.
- SMS Reminder
SMS Reminder logging is described here.
- Mobile Connection
Can be turned on in the registry, description for MCO and for MCN.
- Lotus gateway
Automatically creates ERR files in Mobilchange/mail/out/err folder. You can found information about last
completed operation done by gateway in this file. When gateway is correctly terminated, ERR file is deleted.
In case of error file remains in the folder and you can analyze it.
- Exchange gateway
Logging of gateway 's work - in HKLM/SOFTWARE/Datasys/Mobilchange/global/exchange change GwDebugMode value from zero to one.
After service restart log file C:\gwlog-mx-sms.log will be generated.
- Scripting application logging
Described here. Can be used to get debug information during application development
and also for application monitoring.
back to top of page
