Get the following file from your ArkCase contact: acm.war. Note, unfortunately this file is too large to store in the ArkCase Github distribution repository. Soon we will have another official location for the war files.
Copy the appropriate database driver (either the PostgreSQL JDBC driver jar, or the Oracle JDBC driver jar) to the Tomcat lib folder.
If your database is PostgreSQL, before the first time you start ArkCase, edit the $HOME/.acm/datasource.properties, and set the acm.autoCommit property to true. (If you skip this step, the Activiti tables will not be created and ArkCase will not work). After first startup, shutdown ArkCase and set the autocommit property to false. If your database is Oracle, leave acm.autoCommit=false, since Oracle will create the Activiti tables even with autoCommit=false. Only PostgreSQL needs autoCommit=true.
After all the configuration files are updated, just drop the acm.war into the webapps folder of the ArkCase Tomcat service. In the Tomcat catalina.out file, you should see extensive log messages. If the application does not start, the log output will include sufficient diagnostic output to figure out what went wrong.
Assuming the webapp started normally, which will take about 3-5 minutes, you can take a few steps to verify the installation.
- Check the ArkCase database schema. You should see many new tables.
- Log into the application as a user from one of the LDAP groups mapped to the ROLE_ADMINISTRATOR role. Visit the Administration module. You should see the RBAC configuration page, the labels configuration page, the report configuration, the dashboard configuration, and other pages.
- Visit your user profile page and upload a profile picture. You should see the picture you uploaded on the profile page. Ensure the profile information that came from LDAP appears on the page (your group memberships and e-mail address).
- From here you can continue to explore the application.
After the First Startup
Reset the acm.autoCommit property
If your database is PostgreSQL, after the first startup, verify the Activiti tables were created in the ArkCase database schema (you should see many tables with names starting with “ACT_”). If you don’t see such tables, perhaps ArkCase did not start correctly, or perhaps you didn’t set acm.autoCommit to true in datasource.properties. If you do see the Activiti tables, YOU MUST:
- Shutdown the ArkCase Tomcat service
- Edit the $HOME/.acm/datasource.properties, and set the acm.autoCommit property to false
- Restart the ArkCase Tomcat service
DO NOT LEAVE ACM.AUTOCOMMIT SET TO TRUE!!!!
Business Rule Configuration
ArkCase copies a set of business rule spreadsheets to the $HOME/.acm/rules folder. You may need to edit them. The spreadsheets can be modified at any time. Any new or updated rule file in this folder is detected and deployed by the application at runtime; no application restart is needed.
These files only have to be updated if you need to change the default rules.
- drools-access-control-rules.xlsx: defines the access granted to each participant type for each object type.
- drools-assignment-rules.xlsx: allows specification of default participants based on object type; for example, to ensure evidence technicians have access to all evidence documents. You should update drools-assignment-rules.xlsx to specify the default owner and group for complaints and case files.
- drools-case-file-rules.xlsx: controls the format of the case number, and the CMIS folder where new case files are stored.
- drools-complaint-number-rules.xlsx: controls the format of the complaint number, and the CMIS folder where new complaints are stored.
- drools-form-business-process-rules.xlsx: controls which document types generate a new business process, and some attributes of the new business process.
drools-task-rules.xlsx: controls the CMIS folder where new tasks are stored.