Magnet promotes digital transformation of your mobile efforts through transactional messaging. Mobile transactional messaging allows developers to integrate the creation of approvals, surveys, and checklists—combined with rich media attachments and backend server/3rd party service integration—into their mobile apps. Developers can integrate these features to fit their organization's unique use cases and workflows. This results in faster results, better field intelligence and reduced costs.
Magnet provides the infrastructure to perform these messaging based workflows and processes that is designed to allow rapid development into new or existing apps. This includes a middleware that connects mobile apps to business systems.
Go to https://developer.magnet.com and select Option #3 as shown below
Unzip the downloaded archive to install the server.
From the terminal window go to the bin folder of the extracted server and execute the following:
./max-server.sh start
orNote: For *nix systems use chmod -x max-server.sh
if the file is not executable.
This command will start the server in background.
After the server is up, launch the admin console using the following URL:
http://localhost:7777
Use the default credentials to log in:
From the terminal window go to the server's bin folder and execute the following:
./max-server.sh stop
By default the Magnet Max server uses embeded HyperSQL (HSQL). But the developer can configure the server to use MySql or PostgreSQL.
To specify the database type edit the server/conf/default/datasource.properties
file for the desired database:
datasource=datasource_mysql.properties
datasource=datasource_postgres.properties
To specify the database configuration edit the following file for the desired database:
server/conf/default/datasource_mysql.properties
server/conf/default/datasource_postgres.properties
Magnet recommends that the following three properties be updated to specify the database username, password and URI:
javax.persistence.jdbc.user
javax.persistence.jdbc.password
javax.persistence.jdbc.url