We have tried Joget Workflow v3 with Microsoft SQL Server 2005. However, if you find any issue(s), please feel free to inform the community through forum discussion.
- Create a database in SQL Server; name it jwdb (or another preferred database name).
- Make sure that you grant the intended database user with sufficient access to "jwdb".
- Download jwdb-mssql.sql and load this SQL file to "jwdb". This will populate all necessary Joget Workflow table structures into "jwdb".
- In joget-installation-directory/wflow/, create a new datasource profile file - app_datasource-mssql.properties.
- Open to edit joget-installation-directory/wflow/datasource-mssql.properties in text editor and insert contents as shown in Figure 1 below. You may need to edit the configurations (such as datasource URL, database user/password) according to your environment.
- Open to edit joget-installation-directory/wflow/app_datasource.properties in text editor and change the content as shown in Figure 2 below. This is to activate the datasource profile named "mssql".
- Restart Joget Workflow server.
You may need to change the datasource URL, database user and database user's password accordingly.
In order to connect to the Microsoft SQL Server remotely (such as JDBC datasource), TCP/IP needs to be enabled. This is disabled by default on Microsoft SQL Server 2005 Express edition. TCP/IP may also be manually disabled on other editions of Microsoft SQL Server 2005.
To enable TCP/IP on Microsoft SQL Server 2005:
- In Microsoft SQL Server 2005 -> Configuration Tools, open 'Microsoft SQL Server Configuration Manager'.
- Expand ‘SQL Server 2005 Network Configuration’ and then click on ‘Protocols for <Instance Name>’. <Instance Name> is the name of the database instance used by Joget Workflow.
- Right-click on ‘TCP/IP’ and then click on ‘Enable’. The icon for the protocol will change to show that the protocol is enabled.