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

Upgrade Guide






Version 1.5.0

Upgrade Guide



Revised July 8, 2011




© 2011, Kinetic Data, Inc.

Kinetic Data, Inc, a Remedy® Alliance Partner.

Remedy, a BMC Software company©

Remedy the Remedy logo and all other Remedy product or service names and registered trademarks or trademarks of BMC Software, Inc.




Chapter 1                       Introduction


Kinetic Calendar 1.5 introduces a number of enhancements, most notably support for the pure Java Remedy API, multiple filtered event types per calendar, and a user selectable time zone for displaying event data.


Chapter 2                       Upgrade Instructions

This upgrade document is for users of Kinetic Calendar 1.4.  If your version is less than 1.4, please follow the upgrade documents of the previous versions to upgrade the Remedy portion of the application up to 1.4.  The web application does not need to be updated for each version as it will be overwritten again with this upgrade. 

The upgrade should be performed by a Remedy Administrator.

To upgrade to 1.5.0


1.     Verify your version of Kinetic Calendar is 1.4.

a.     Login to Remedy using the Remedy User tool

b.    Click the ‘Kinetic Calendar Console’ link from the home page

c.     Click the ‘Configuration’ link on the left hand side of the dialog window.

d.    The Kinetic Calendar version will be in the upper-right hand corner of the Configuration Manager dialog window.

e.     If Kinetic Calendar is at version 1.4, you may proceed with the instructions below.  If your calendar version is less than 1.4, please contact Kinetic Data support to obtain all the previous update packages.

2.     Import Remedy Workflow

a.     Using the appropriate application for your environment (Remedy Admin Tool or Developer Studio), import in-place the def file that came with the upgrade package:

                                          i.    ARS\KineticCalendar_v01.04.00_to_v01.05.00.def

b.    Be sure to select the ‘Replace Objects on the Destination Server’ option.

3.     Update Web Server Files

a.     Before you begin with this step, stop all of your servlet container servers (such as Tomcat or ServletExec) that are used for Kinetic Calendar.

b.    On each of your web servers, the KinCal webapp directory must be updated.  The easiest way to do this is to remove the existing application, and install the new web application.

c.     Move the “KinCal” webapp directory on each of your web servers to a backup location outside of the web server applications directory.  For tomcat, the applications directory is <tomcat_home>/webapps/.  If you copied the directory instead of moved it, please delete the existing KinCal web application directory at this time.

d.    Determine what version of the web application you will run for your environment.  Kinetic Calendar now comes with support for the 6.0 – 7.0 style API for Remedy 6.x servers, and support for the pure Java style API for Remedy 7.x servers.

                                          i.    6.3 servers – use the web application found in the Web/RemedyAPI_6.x directory of the upgrade package.

                                         ii.    7.0+ servers – use the web application found in the Web/RemedyAPI_7.x directory of the upgrade package.

e.     Copy the KinCal directory from the appropriate web directory you determined in step ‘d’ above to your web server’s web applications directory.  The files are in the default directory structure, so they can be moved en-masse.

f.     Configure the KinCal/WEB-INF/classes/KinCal.xml file to connect with your Remedy server.  The following parameters listed below can be copied from the /WEB-INF/KinCal.xml file in your backup directory.

                                          i.    LogLevel

                                         ii.    LogSubLevel

                                        iii.    UseEncryption

                                        iv.    EncryptionSeed

                                         v.    RemedyServer

                                        vi.    RemedyUser

                                       vii.    RemedyPassword

                                      viii.    RemedyPort

                                        ix.    RemedyRpc

                                         x.    RemedyAuth

                                        xi.    AuthenticationAdapter

                                       xii.    AuthenticationAdapterProperties

g.    Check you web server to see if there is an existing kdi_arshelpers.jar file in a shared classpath directory, such as <tomcat>/shared/lib.  Please remove all copies that you find.

h.     Check your backup for any custom output pages.  These files would be located in the /KinCal/resources/ directory.  If you have any other than ‘helloWorld.jsp’, copy these to the new /KinCal/resources/ directory at this time.

i.      Restore any other customizations you made to the application, such as stylesheets, images, etc…

j.      Restart your servlet container service.

k.     Repeat these steps for each web server used.

4.     Flush your web server’s compiled JSP store.

This example is for a Tomcat web server, and the exact procedure will vary with different web servers.

a.     Navigate to the <tomcat>/work/Catalina/localhost directory.

b.    Delete the KinCal directory.  This directory will be recreated when a user connects to Kinetic Calendar.

c.     Repeat these steps for each web server used.

Chapter 3                       Single-Sign On

The internal API for Single Sign On (SSO) changed in version 1.3.0.  If you are a customer using SSO with a version of Kinetic Calendar earlier than 1.3.0, please call Kinetic Data 651-695-8566 for support in transitioning your code.