Mobile Data Now is a 3-tier Java application that works on most ODBC/JDBC compliant databases, including the likes of: MS SQL, Oracle, PostgreSQL, MySQL, DB2, MS Access, Sybase, and others. Additionally, Mobile Data Now will soon work with web services using the SOAP protocol.
Please see the pre-installation guide to determine the requirements for running Mobile Data Now (84 kb PDF).
Mobile Data Now can be deployed on any operating system that supports a Java Virtual Machine and is running Java 6.0 or later.
Mobile Data Now is tested for and supported on:
The following deployments are in development:
Mobile Data Now supports the following data access technologies:
Mobile Data Now uses JDBC / ODBC to access the customer's databases. This means that the customer may simply use a standard ODBC driver to provide MDN access to their data, or provide a 3rd party JDBC driver. Most commercial databases provide a JDBC driver as part of their product and others may be purchased from the Internet to provide quicker/better data access.
All configuration is done behind the company firewall. The only services exposed are to the end user ie. email, instant messaging and sms, for which access is tightly controlled.
Mobile Data Now has the following components:
1. MDN Server
2. Tomcat Server
3. MDN Mail Service
4. MDN Instant Messaging Service
5. SMS Messaging Service
MDN Server is a non-graphical database server module. This is the application that communicates with your databases, handling remote data access, the RMI registry, notifications and messages and provides a common point of access to all data (including internal and external databases) for the other components in the MDN system. It is expected that this component will run on a database server machine.
This module must be able to connect to the MDN configuration database using the supplied or 3rd party JDBC drivers.
This module needs to connect to all databases that you wish to publish data from, using the JDBC-ODBC bridge or 3rd party JDBC drivers.
The Tomcat server houses the graphical administration module and uses a flash based configuration tool inside a web browser. This component uses http to communicate to the Tomcat server, which in turn communicates with the MDN Server to configure MDN.
The other services handle the receipt and sending of messages from email, instant message or SMS.
The Mail Service connects to your IMAP mail server and sends and receives email.
The instant messaging service connects to various instant messaging services to send and receive instant messages.
The SMS service connects to a GSM modem for sending and receiving SMS messages.
These messaging services can only be stopped and started by the server administrator.
This is where all the configuration data to run Mobile Data Now is kept. As supplied, this database is Apache Derby. The customer is able to specify that MDN use another database (say Oracle or SQL Server) for the local configuration. This may be preferable to some clients as this may be their internal database standard. MDN database issues are only supported on the default supplied databases.
Here's 15 great reasons why Mobile Data Now does things better!
