MiniM Overview |
MiniM
Additional Tools | Nov 19, 2016 GT.M Tools for FIS GT.M Download GT.M Tools GT.M Tools is a set of two applications:
In depending of the target operating system this tools can be united by GT.M Tools Launcher. GT.M Tools are ported to the following operating system:
Windows version can be run under Windows x64 version too. Server side of GT.M Tools is a daemon written in MUMPS and working on the GT.M. GT.M Tools connects to this daemon and uses TCP/IP network. GT.M Tools fully tested on the GT.M version 6.2 runned on Linux and use only standard GT.M builtin system functions and Linux commands. GT.M Tools is a licensed software and to work without any nag-screens requires purchasing of license key. Anyway, GT.M Tools can work without entering license key during trial period. GT.M Tools are ports of MiniM Client Tools and Cache Tools to work with GT.M instead of MiniM Database Server or Intersystems Cache. If you are need port of GT.M Tools to FreeBSD i386 or FreeBSD x64, this can be done by separate request to MiniM support: support@minimdb.com Installation of GT.M Tools consists of two steps:
Installation of client executables depends of the target operating system and routine installation not. Installers make the following subdirectory tree inside of installation directory: bin - GT.M Tools executables doc - GT.M Tools documentation rou - GT.M routine for GT.M Tools GT.M Tools Installer for Windows is windowed application and self-extracted executable. Installer have file name like the following: setup-gtmtools-1.26-win32.exe This file name can vary from version to version. After running installer asks directory to place GT.M Tools executable, server routine and documentation. ![]() GT.M Tools Installer for Windows After installing see Programs menu and expand the GT.M Tools item. This menu item can looks different in depending of the Windows version and current Windows settings. GT.M Tools installer for Linux is a self-extracting executable and must be run in Linux terminal. Installer requires sudo command, so current user must be in the sudoers group. GT.M Tools for Linux have two installers in depending of architecture - i386 or x64. Installer file have a filename like the following: setup-gtmtools_1.26_linux-i386 setup-gtmtools_1.26_linux-x64After downloading installer it is an ordinal file so before executing this file must get executable rights. Run the chmod command: chmod +x setup-gtmtools_1.26_linux-x64or chmod +x setup-gtmtools_1.26_linux-i386Execute installer under the sudo: sudo ./setup-gtmtools_1.26_linux-i386Installer shows common information and asks the directory where executables must be placed: GT.M Tools 1.26 Installer. Copyright (C) Eugene Karataev http://www.minimdb.com Switched to install mode. Enter installation directory or press Enter to use default /var/usr/gtmtools : Processing binary files... Processing desktop files... Installation of GT.M Tools 1.26 complete. To uninstall run installer with option -u.After installer ends, see menu of the Linux, menu item with Development tools and applications. This common menu contains GT.M Tools Launcher, small window from where can be run GT.M Routine Editor, GT.M Global Editor and GT.M Tools documentation. ![]() GT.M Tools Launcher for Linux GT.M Tools Installer for MacOSX is a self-extracted executable installer and have a filename like the following: setup-gtmtools_1.26_darwin-i386After download it is ordinal file and before executing change executing rights in terminal: chmod +x setup-gtmtools_1.26_darwin-i386And next this installer can be executed in terminal under the sudo command: sudo ./setup-gtmtools_1.26_darwin-i386 GT.M Tools 1.26 Installer Copyright (C) Eugene Karataev http://www.minimdb.com Switched to install mode. Enter installation directory or press Enter to use default /var/usr/gtmtools : Processing binary files... Installation of GT.M Tools 1.25 complete. To uninstall run installer with option -u.After installer ends click the Applications folder or click Launchpad icon. ![]() GT.M Tools for MacOSX placement ![]() GT.M Tools Launcher for MacOSX Server-side part of GT.M Tools is a TCP/IP daemon written in MUMPS. This additional job opens TCP/IP port, waits incoming connections and runs job to each one to service requests. All code of this daemon is in one routine \%srv. After installing client side see subdirectory /rou where GT.M Tools located after installation. There is file %srv.rou with server side routine. First of all this routine must be imported into GT.M by using builtin routine import utility GTM>d ^%RIEnter there real full name of the file srv.rou. After importing compile them by call GTM>zcompile "_srv.m"Underscores are used by GT.M in file names instead of the percent symbol. And link routine by call GTM>zlink "_srv.m"After this steps routine %srv is ready to be used. This daemon uses by default TCP/IP port number 5002. To change this, write into global port number, for example to use port number 6003 execute: GTM>s ^%SRV("port")=6003To stop %srv daemon manually or from other procass call GTM>d stop^%srvThis code fire stop indicator and returns immadiately. Stop indicator periodically checked by \%srv daemon and daemon will stop. All child processes runned to service GT.M Routine Editor and GT.M Global Editor will work as is. To start %srv daemon manually or from other process call GTM>d ^%srvThis code runs MUMPS job for daemon and returs immadiately. To prevent manually enter this code on each start of GT.M server, add running of this code into the GT.M run script. See file gtmstart at point where this script runs GT.CM server. This may looks like this: echo "Starting GT.CM (${service}, ${id})..." if [ ! -d $logdir/$service ] then $echo "logging directory (${logdir}/${service}) ... mkdir $logdir/$service fi nohup $gtm_dist/gtcm_run -service $service -id ${id ... >> $logdir/${service}/session.log 2>&1 < /dev/null & if [ $? != 0 ]; then $echo "The GT.CM server (${service}) failed to start." fi sleep 1 done < $gtm_dist/gtcm_slistAnd after running GT.CM add running of %srv daemon by adding code $gtm_dist/mumps -r ^%srvAnd gtmstart script may looks like this: echo "Starting GT.CM (${service}, ${id})..." if [ ! -d $logdir/$service ] then $echo "logging directory (${logdir}/${service}) ... mkdir $logdir/$service fi nohup $gtm_dist/gtcm_run -service $service -id ${id ... >> $logdir/${service}/session.log 2>&1 < /dev/null & if [ $? != 0 ]; then $echo "The GT.CM server (${service}) failed to start." fi sleep 1 # Run tcp/ip listener ^%srv $gtm_dist/mumps -r ^%srv done < $gtm_dist/gtcm_slist fi else exit fiOn running of GT.M start sequence we may see additional diagnostic message: Starting the GT.CM server(s). Starting GT.CM (omi, 42)... GT.M TCP server ^%srv. GT.M server ^%srv is running.%srv daemon additionally writes internal diagnostic messages into system log and messages can be viewed in syslog in the /var/log subdirectory like the following line: Jul 9 13:01:44 debian GTM-MUMPS[2137]: GT.M server ^%srv is running. See next part, GT.M Tools overview Download GT.M ToolsEugene Karataev support@minimdb.com
|
|
Info Support |