Kinetic Task 4.0 now allows your organization to easily add workflow automation to nearly any process from request management approvals to SLA’s to network alerts. Platform-agnostic, Kinetic Task can communicate with virtually any enterprise application, such as ERP, human resources and ITSM platforms through its open architecture. With Kinetic Task, enterprises benefit from a non-proprietary approach for centralized business process automation and service delivery management.
Kinetic Task 4.0 now runs completely stand-alone without any platform dependencies.
- Trigger tasks and workflow from your Remedy application, service catalog, Salesforce.com, JIRA ServiceNow or almost any other system
- Open architecture allows customers to extend our connectors (both inbound and outbound) for custom systems or tailor an existing connector to specific requirements of other applications
|Web Application Server||
Tomcat 5.5 or greater
|Java||Java 1.6.0 or greater - either 32-bit or 64-bit|
The install files include both a stand-alone .war file and a full Tomcat to easily get up and running.
Kinetic Task can run in trial mode without applying a license. For production use please contact Kinetic Data sales to purchase a license or support to have a license generated for an existing purchase.
4.0.3 Change Log
- KT-725 - Error building results with Join/Junction after retrying/skipping errors
- KT-726 - Results on update branch after management action not working as described
- KT-728 - $ in connector expressions causes error
Web Server Recommendations
|Web Application Server||Tomcat 7.0.54+|
|Web Server Heap Memory||
Minimum 512MB (-Xms512m)
Maximum 1024MB (-Xmx1024m)
|Web Server PermGen||
Applies only to Java 1.6 or Java 1.7. Does NOT apply if using Java 1.8.
Maximum 256MB (-XX:MaxPermSize=256m)
The recommended properties can be added to the JAVA_OPTS environment variable for the web server. If running a Tomcat server, the CATALINA_OPTS environment variable should be used instead.
- If running a Tomcat server in a Linux environment, the properties should be added to the <tomcat>/bin/setenv.sh file. Simply create the setenv.sh file if it doesn't exist, and ensure the file has execute permission (chmod +x setenv.sh).
- export CATALINA_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=256m"
- If running a Tomcat server as a Windows service, the properties must be added to the Windows registry. The recommended way to do this is to use the Tomcat Monitor application.
- The initial memory pool setting is the same as the -Xms property, so set this to 512 MB.
- The maximum memory pool setting is the same as the -Xmx property, so set this to 1024 MB.
- The maximum permgen size must be added to the Java Options property. This field only allows one option per line, so add the following on the first blank line after all the other options:
- If running a Tomcat server manually from a Windows command prompt, the properties should be added to the <tomcat>/bin/setenv.bat file. Simply create the setenv.bat file if it doesn't exist.
- SET CATALINA_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=256m"
- If running any other web server, consult the web server documentation for setting Java options.