Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

Kinetic Task 3.0

Kinetic Task 3.0 was released March 31st, 2013.  Features include: the ability to automate workflow for any application, the Kinetic Security Language (KSL), pure Java and complete 64bit compatibility, and a web-based installer (see What's New in 3.0 for more information).

IDF guide rendered from cache
  • Kinetic Task™ is an advanced automation engine that extends approvals and task management to BMC® Remedy® and third-party enterprise applications.  Installation of this version of the application consists of three general steps: Deploy the Kinetic Task WAR file to the web server Run the web-based installation application to install the remedy forms and workflow and data Confiure the application using the web based administration console   Who Should Read This Manual? The person performing the installation of Kinetic Task™ must have file system access to the web server that the application will run on.  A general knowledge of the ARS server connection information is also required.   Pre-Requisites The following requirements must be met to install Kinetic Task™ Java Development Kit (JDK) version 1.6 or greater - either 32-bit or 64-bit if Tomcat is not to be installed, a stand-alone Servlet Engine such as Apache Tomcat 5.5 or greater using a JDK version 1.6 or greater is required   Obtaining the WAR A zip file containing the kineticTask.war file can be obtained from the Install Files page located here. Special builds of the war file for WebSphere and WebLogic can be found in the appropriately named directories of the package.   Deploying the WAR Access the web server that Kinetic Task is going to be installed on and copy the kineticTask.war file inside the proper deployment directory.  Using Tomcat as an example, this location would be in <tomcat_home>/webapps/.  Restart your web server if it is required to deploy WAR files.   Running the web-based configuration application Complete the following steps to install a new instance of Kinetic Task 3.0 on your system. Open a web browser and point it to the Kinetic Task application directory of the web server that you just deployed the war file on.  This should be something like  You will see the following screen: Click the Continue button.   Enter the Remedy server connection information including a username and password of an account with Administrator permissions.  Click the Continue button when finished. For all new installations of Kinetic Task you will see the screen below.  If this is not a new installation you will see a different screen.  In that case, click here to jump to the upgrade page. Click Continue. Click Continue to confirm that you want to import the workflow and data required to install Kinetic Task. When the workflow and data has all been imported you will receive the following screen. Click the Continue button to configure the Task Engine. Click the Edit Properties button. Update the application properties accordingly.  The properties are listed below by section. Note: all fields marked with an asterisk (*) are required. Application License Application License - the Kinetic Task License key that was provided to you by Kinetic Data   Remedy Server Settings Server Name -  the name of your Remedy server.  This should either be the server’s DNS name or IP address.  The value you enter here must match the value used to generate the Kinetic Task licenses. TCP Port - the Remedy server’s TCP Port.  If your Remedy server uses portmapper, enter 0. Username - the Remedy user name that the task engine will use to log in and process tasks. Password - this password for the aforementioned username   Kinetic Task Engine Settings Enable - check this box to enable the task engine and display other settings for it. Sleep Delay - the number of seconds the task engine will wait between checking for new triggers to process.  This value is only used if the Max Threads setting is set to 0. Max Threads - indicates the number of worker threads the task engine will use to process triggers. If set to 0, the task engine will only use one worker thread in a synchronized manner, meaning it will process all the triggers with one worker thread, then sleep for the specified duration as indicated by the Sleep Delay parameter, then wake up and process the new triggers. If this value is set higher than 0, that many worker threads will be available to process triggers simultaneously. More threads require more memory and higher CPU utilization. Query Limit - the maximum number of triggers that will be processed during each wake cycle. If there are more triggers than the value of the query limit, the remaining triggers will be processed in future wake cycles. Query - allows the user to customize what trigger records are selected by a specific engine. This is typically only applicable in multiple task engine environments. Cache Handlers - allows the task engine to cache the task handler files in memory. Changes to the task handler file will not be applied until the web server is restarted. This provides a performance improvement over loading the task handler file every time it is needed. Outgoing Mailbox Unique ID - used to identify a specific Remedy mailbox to use when generating system emails. This value corresponds to the 'Unique Identifier' field on the AR System Email Mailbox Configuration form. If this value is left blank, the default outgoing mailbox will be used. Notify Process Owner - tells the task engine to send an email to the process owner when an error occurs with that process tree. The process owner is configurable for each task process tree by clicking the 'Configure' button in the Task Builder, and configuring the email address in the Author field. Notify System Owner - tells the task engine to send an email to the system administrator when any error occurs in the task engine. When selected, a text input field will appear that will accept an email address, or a comma separated list of email addresses.   Default Logging Settings -  Log Level - determines what level of detail the information is written to the log file.  The values are listed in order of detail from least (Off) to most (All).  A higher detailed value provides more logging information, but is also more resource intensive on your server. Max Log Size - The logger is configured as a rolling file appender, which means that when the log file reaches the max size limit, it will be closed and a new file will be started.  This prevents the file from growing too large, and allows administrators the ability to delete old log data without having to stop the web server.   Configuration Administration Credentials Config Admin User - the configuration administrator username.  The default value is admin. Edit Password - check this box to display the Admin Password field so that you can update it.   When you have finished updating the properties click the Update Properties button to save them. You should see a green confirmation message letting you know that the properties have updated successfully. That's it.  You're done.   Related
  • In previous versions of Kinetic Task, Remedy was the DB/system of record. Now in Task 4, you can select among several DBs. This update allowed for many other things to change, and required some other things to change. Transitioning from one system to the other, though, doesn't have to be painful or difficult. Below are the recommended steps and possible things to consider for making the transition from Task 3 to Task 4. If you are on an earlier version of Task, there may be additional items for
  • Kinetic Task 3.0 exposes the advanced workflow automation that has been proven in Kinetic Request to any application.  Task trees can now be developed, using existing handlers, to automate solutions like Remedy ITSM, Salesforce, Oracle Identity Management.  This list is limitless!  Additionally, multiple enhancements are included in this release including: pure Java and 64bit compatibility, a new and improved web-based installer, and the Kinetic Security Language (KSL).