|Operating System||Linux/UNIX/MacOS or Windows platforms ( 64-bit )|
|Hardware||4 CPU, 8 GB RAM|
|Environment||JDK "1.8.0_45" or higher. Make sure the JDK bin directory is on your PATH ( |
As we have prepared our system, let’s grab Flint !
Flint follows a standard practice for its build versioning: major.minor.patchlevel.hotfix.
$ cd <file download directory> $ unzip flint-x.x.x.x.zip
Extract the files and folders from the zipped tarball into a directory of your choice.
Locate the compressed folder i.e flint-x.x.x.x.zip that you want to extract files and folders from. To extract the entire contents of the compressed folder, right-click the folder, click Extract All, and then follow the instructions.
Compressed folder flint-x.x.x.x.zip is the downloaded Flint distribution version. For example : flint-0.1.0.0.zip
After deployment of Flint build, we just need to kick-start it as below-
$ cd flint-x.x.x.x $ sh flint.sh start
You can also start Flint in a daemon mode, to do so issue the following command:
sh flint.sh -d start. To see list of available arguments run:
cd flint-x.x.x.x flint.bat start
You can also install and start Flint as Windows service, to do so open an Administrator command prompt and issue the following command:
flint.bat installservice. To see list of available arguments run:
You need to set Flint path in System Environment Variable as :
Variable Name : FLINT_HOME
Variable Value : C:\flint-x.x.x.x e.g: C:\Users\Administrator\flint-220.127.116.11\
This will bring up the first worknode/instance of Flint Grid.
To verify that the Flint process has started successfully, point your browser at: http://localhost:3500 If you see the Login screen as in below screenshot, then you're all set to go.
Default Login Credentials: Username = admin and Password = admin123
If you have started Flint in the daemon mode, then to stop Flint issue the following command :
$ cd flint-x.x.x.x $ sh flint.sh stop
If you have started Flint as a windows service, then to stop and uninstall Flint open an Administrator command prompt and issue the following command :
To install flint onremoreserver you need to perform some additional configuration
- Update flint.cluster.hostname parameter in config/application.cfg withhostnameofserver
- Update tcp-ip/member parameter in config/cluster.xml with hostname of server
<tcp-ip enabled="true" connection-timeout-seconds="10"> <member>node.hostname.com</member> </tcp-ip>
- Make sure you have configured DNS or hosts file to point configured hostname to server's IP address
For AWS EC2 please map private IP to hostname in hosts file.
Flint Folder Structure
├── config # all configuration files are stored here
│ ├── application.cfg # main configuration file
│ ├── cluster.xml # used to configure flint grid
├── base-mods # used to store base modules (do not change this folder)
├── connectors # used to store connector jars (add/replace new and updated connectors here)
├── db # used to store internal info (do not change this folder)
├── flintbox # used to store flintbox: these are cloned from remote git repo
│ ├── example # a flintbox cloned from remote git repo
│ │ |── hello.rb# a ruby flintbit inside aflintbox
│ │ |── hi.groovy # a groovy flintbit inside a flintbox
│ └── test # another flintbox
│ └── one.rb # a ruby flintbit inside a flintbox
├── gridconfig # used to store current and snapshots of Grid configuration
├── lib # used to store library jars. You can copy new jars here (e.g JMS, JDBC drivers etc)
├── listeners # used to store listener jars (add/replace new and updated listeners here)
├── logs # used to store all log files
│ │── startup.log # stores startup logs (when flint starts)
│ │── platform.log # have platform related logs
│ │── job.log # have flintbit job run logs (tail this to debug your flintbits)
├── sys-mod # System modules (Do not change this folder)
└── web-root # UI console files