Skip to main content
Kinetic Community

Task V4 Configuration Guide

Steps involved in configuring Kinetic Request 5.2 to work with Kinetic Task 4.x

Details

Because Kinetic Task v4.x is not directly connected into BMC Remedy, you need to complete a few extra configuration steps so the applications can integrate effectively. The steps break down into the following broad topics:

  1. Check Configuration Manager Values
  2. Configure the Task 4 Manager
  3. Configure the Service Catalog/Service Item
  4. Update the Tasks tab
  5. Add the Task Source

Configuration Manager Value

After Upgrading to Kinetic Request 5.2 the default value of the Default Task Version is set to Kinetic Task 4+. Any new service item is set to use version 4 of Kinetic Task.

task4%2Bconfigurationvalue.png

Other values available are:

  • Blank or Legacy - Pre-Kinetic Request v5 task engine.
  • Kinetic Task 2/3 - Version 2 or 3 of the Task Engine

 

Task 4+ Manager

The first step is to add your Task 4+ application to Kinetic Request. The link to start this is on the left hand of the Service Catalog Console. task4+managerlink.png

This link will take you to the actual manager configuration console for the entire Request application. Values set here are used in the following settings. The console has two sections (tables). The top table defines Task 4+ applications that can be used by Kinetic Request, and the bottom shows errors (failed API calls) related to that application.

task4+managerconsole.png

To add a reference to a specific Kinetic Task 4+ application, click on the Add button and complete at least the name and Name and Application Base URL fields.

The Name field can be any unique name related to the instance of Kinetic Task 4+. The Application Base URL is a unique URL pointing to that application it has the following format: http://yourserver.yourcompany.com:yourport/kinetic-task

The yourserver.yourcompany.com:yourport is configured by your System Administrator in charge of the server and/or tomcat.

The Authentication Token is optional and is used to provide a unique token recognized by the system. It is not used by the current source/consumer file, but can be added by hand if desired.

The Status options is set to Active by default.

You can Modify and Delete existing Task Servers. If you modify these values, you need to make changes to the settings in the next step, configuring the Service Catalog or Service Item.

Configure Catalog/Service Item

Once the Configuration Value and the Manager console are set you need to decide if the Task 4+ engine is going to be used by entire service catalogs, or just on a per service item basis. In either case, the configuration is the same. It is handled by settin values on two attributes. The first is called Task Server Name. Select this attribute and choose your Name from the drop-down list. The Name will match the value set on the Task 4+ manager console. The attribute is Task Source Name. This is defaulted to Kinetic Request and should stay at that value.

task4+attributesettings.png

Tasks Tab

Now that all the configuration is complete, it's time to point your tasks tab at the Kinetic Task 4+ Engine for trees and runs.

The Add drop-down includes the following options:

  • Complete Tree - Sets tree name as Complete. Fires on complete of requests
  • Create Tree - Sets tree name as Create. Fires on create of request.
  • Custom Tree - Set the name and if it will fire on Complete or Create
  • Local Routine - Creates a routine for your service item. You complete the name, ID, inputs and outputs.

After creation you can click on the name to open in the tree builder.

Task Source

The last step after creating/modifying trees is to add the bindings (@answers etc) to your available parameters. This requires adding a specific source file into the web directory.

The Community article with sources is available here:

Task Consumers

Select the source (Consumer) that you want and then download and copy to your WEB-INF/consumers directory on your web server. After the install you must restart your web server.

After the install of the consumers file, you need to configure the source. Go to the Admin|Sources dialog and Add New Source. You will need to configure the source to connect to your Remedy server. The only unusual piece of configuration is the Web Server. It should have the following format:

http://yourwebserver:yourport/kinetic/