Miscellaneous

Documentation / Standard Edition / User Guide / Appendix / Miscellaneous
 

Scripts

MyARM daemon support scripts

MyARM has several daemon processes described in section "Agent daemons" which are working in background and provide different kind of services. To simplify the starting and stopping of these daemon processes the following scripts are provided:

myarmtcpd.sh
starts and stops the myarmtcpd program.

Usage:

myarmtcpd.sh start|stop
myarmfiled.sh
starts and stops the myarmfiled program.

Usage:

myarmfiled.sh start|stop

These scripts can also be used as init.d scripts used to start processes during boot time of the machine.

Database URL notation

In MyARM a database is normally configured using MyARM configuration properties. If a database configuration should be specified for example on the command line these properties does not work. For this purpose MyARM provides an URL like notation for each supported database type. The type of the database is defined by the scheme (or normally known as protocol prefix) of the URL. Currently the following MyARM database URL types are supported:

sqlite3:///<sqlite_db_file>
defines a SQLite database where <sqlite_db_file> is the file name of the sqlite database file. The name can be an absolute or a relative file name.
xml:///<xml_file>
defines a XML file where <xml_file> is the file name of the XML file. The name can be an absolute or a relative file name.
mysql://<password>:<user>@<host>/<tranDB>/<appDB>/<defDB>
defines a MySQL database where <password> and <user> is the password and user name to log into the MySQL database. The <host> specifies the host name where the MySQL database is running on and the <tranDB>, <appDB> and <defDB> specifies the MyARM databases within the MySQL database server.