v05.02.00
Requirements
Remedy | AR Server v7.0.0 or greater |
Web Application Server | Java Servlet Container
Examples
|
Java | Java 1.6.0 or greater - either 32-bit or 64-bit |
Architecture | Click for Architecture Requirements |
Kinetic Task Compatibility
Installation / Upgrade
The setup program is now embedded into the web application, so the installation and upgrade packages are the same. Since the setup program is built into the web application archive file, a web application server must already be installed on your server. There is no Kinetic Request installation executable, so we are no longer installing a Tomcat server before deploying the web application.
Download the appropriate file in the Attachments section at the bottom of this page. The following table indicates what file is necessary depending on which web application server you will be using.
Web Application Server | Attachment File |
Apache Tomcat 6+ | kinetic-request-survey-v5.2.0.zip |
Oracle WebLogic 10.3+ | kinetic-request-survey-v5.2.0-weblogic.zip |
IBM WebSphere 7.0+ | kinetic-request-survey-v5.2.0-websphere.zip |
Other web application server | kinetic-request-survey-v5.2.0.zip |
Installation Quick Start
Installation of Kinetic Request and/or Kinetic Survey requires you to have a web application server installed that supports the Java Servlet API 2.5 specification, and the JSP 2.1 specification. Once you have that installed, you can simply deploy the web application archive file (.war) into the web server to get the installation program running.
See the complete installation document for more details.
Installation Process (using Tomcat as an example)
- Download and unzip the web application package.
- Copy the kinetic.war file from the extracted upgrade package into the <tomcat_home>/webapps directory.
- If the war file did not automatically deploy, restart Tomcat and the web application archive should deploy on startup.
- Navigate your web browser to the deployed web application at http://<webserver>:<port>/kinetic/. This will initiate the setup wizard requiring you to login as the local administrator user. The default credentials are admin/admin, but you are encouraged to change them during the setup process.
- Follow the instructions on the setup wizard pages to walk you through the installation process. This will require you to enter the Remedy server information where Kinetic Request and/or Kinetic Survey will reside, and a few more optional pieces of information.
- Once the setup wizard is complete, your Kinetic Request application will be ready to use.
Upgrade Quick Start
The 5.2.0 upgrade requires that Kinetic Request is currently at least version 5.0. If you are on a version prior to 5.0, see the appropriate upgrade section for each successive version on how to upgrade your system to 5.0 before continuing. Typically you may skip the web application portion of any prior upgrades as the web application will again be overwritten in the 5.2.0 upgrade.
See the complete upgrade document for more details.
Upgrade Process (using Tomcat as an example)
- Download and unzip the web application package.
- Stop the Tomcat service
- BACKUP the existing kinetic directory located at <tomcat_home>/webapps/kinetic.
- Delete the existing web application located at <tomcat_home>/webapps/kinetic.
- Copy the kinetic.war file from the extracted upgrade package into the <tomcat_home>/webapps directory.
- Clear the cached JSP files.
For Tomcat, delete the entire <tomcat_home>/work directory. - Restart Tomcat and the web application archive will automatically deploy.
- Navigate your web browser to the deployed web application at http://<webserver>:<port>/kinetic/. This will initiate the setup wizard requiring you to login as the local administrator user. The default credentials are admin/admin, but you are encouraged to change them during the setup process.
- Follow the instructions on the setup wizard pages to walk you through the upgrade process.
- After the upgrade is finished, copy the themes directory and any other customized files from the backup made in step 2.
WebLogic Deployment Instructions
WebLogic requires the .war file to be exploded into a directory on the web server. Once that has been done, login to the WebLogic Console (http://webserver:7001/console) and add a new deployment from the directory where the war file was unpacked. Select the application option when the deployment wizard prompts if the directory should be deployed as an application or a libray. After that, follow from Step 4 of the installation instructions above, or from Step 8 of the update instructions above.
Changelog
Features Added
- Added Requester and Assignment fields to the base submission form.
- Implement strategy to store unlimited length answers.
- Added catalog attributes for various review request settings.
- Set new questions to not score by default for Kinetic Request.
- Updated the web administration console interface similar in style to the Kinetic Task administration console.
- Added a diagnostic console to monitor performance of service items, elements on service items, and server response times. Includes real time and aggregate reporting.
- Added support for Kinetic Task v4.
- Added security features that include prevention of Cross Site Request Forgery, settings for Web Frame Policies, and a Whitelist for Redirection.
- Introduced a web-based installer that helps customers more quickly install and configure the required application and server components.
Bugs Fixed
- KR-16, Some of the fields on the catalog console are not locked when the template status is active.
- KR-18, Use existing attribute mappings when switching an event from an SDR to a bridge, and vice-versa.
- KR-42, Prevent saving a checkbox question if a list value contains a comma. Commas are still allowed in the label, just not the value.
- KR-47, Incorrect FLD tag substitution.
- KR-71, Bug in HTML generation when max chars and required are both set on the question, and the question also contains a validation pattern.
- KR-73, Deleting a quetion does not delete all bridge resource records.
- KR-75, Renaming a bridge qualification parameter does not change the bridged resource parameter.
- KR-92, The ArsHelpers library fails to handle keyword substitution when a new Value object is used.
- KR-93, Multiple page reequests are calling the Task 4 API to run a create tree after each page is submitted.
- KR-100, Renaming a bridge record should prompt the user whether to update associated model mapping records.
- KR-25, Add the modified date to the list of Kinetic Task 2 / 3 trees associated to a service item.
- #2761, Fix permissions on the KS_SRV_Helper form.