Joget DX Beta Available for Download
Check out Joget DX, the next generation successor to Joget Workflow for faster, simpler digital transformation.
The architecture is based on a shared webapp connecting to separate databases or schemas. This allows for more cost-effective delivery of services, since many accounts can be hosted on a single app server. At the same time, each account has its own separate database and file upload directory to preserve data isolation.
Refer to the Knowledge Base for more detailed instructions at Installation using the Linux Bundle for more detailed instructions.
The basic Basic steps areto follow:
1. Create a new directory (e.g., /opt/joget) and extract the tar.gz bundle into that directory.
2. Install the Java Runtime Environment (JRE) or Java Development Kit (JDK) version 6 and above.
e.g. Example in Ubuntu: sudo apt-get install sun-java6-jdk
3. Install MySQL Server version 5 and above.
e.g. Example in Ubuntu: sudo apt-get install mysql-server
4. Create an empty database 'jwdb' in the MySQL server.
5. Execute the setup script to create the required database tables: ./setup.sh.
Alternatively, manually create the database tables as follows:
5.1 Populate the jwdb database with the SQL script in data/jwdb-empty.sql.
5.2 Edit wflow/app_datasource-default.properties to match your database settings.
6. Execute the bundled Apache Tomcat application server: ./cloud-tomcat.sh run.
7. Access the home page at http://localhost:8080.
8. Access the default Workflow Management Console at http://localhost:8080/jw.
In this case, requests to all subdomains of example.com (e.g. account1.example.com, account2.example.com, account3.example.com) are directed to Joget.
For local testing purposes, it is possible to just modify the local hosts file http://en.wikipedia.org/wiki/Hosts_(file) . Please note that typically, hosts file configuration does not support wildcards so it would will be necessary to add separate entries for each subdomain (e.g., account1.example.com, account2.example.com, etc.).
Each account (tenant) is tied to a datasource profile. More info on profiles can be found at Custom Database Configuration.
In v3 Community or Enterprise Edition, only 1 profile is selected at a time. In the Cloud Edition, this is enhanced such that all accounts and profiles are enabled concurrently.
Open the file (joget.home)/wflow/app_datasource.properties. An Here's an example of the file content:
There are a few approaches to provision (create) an account.
Account Profile Name
Desired account name (e.g., demo)
Main domain (e.g., example.com)
Account Domain Name
Account domain (e.g., demo.example.com)
Account Database Name
Database name for the account (e.g., jwc_demo)
Account Database User
Database user for the account (e.g., jwc_demo)
Account Database Password
Database password for the account (e.g., jwc_demo)
Joget home directory, ; defaults to current directory . directory
Joget configuration directory, ; defaults to ./wflow
MySQL host name
Database server host name
Database admin user (with permission to create database)
Database admin password
In a production environment, it is recommended for security purposes that this app be installed on a specific profile instead of the default profile.
As with a standard Joget installation on Apache Tomcat, the log file is at (joget.home)/apache-tomcat-6.0.18/logs/catalina.out.
Updates are to WAR files are done as per a standard Joget Workflow installation.
Backups should be done on for all the MySQL databases , as well as the configuration and data files in (joget.home)/wflow.