Skip to main content
Kinetic Community

Kinetic SR Install and Config Guide

 

 

 

KINETIC SR (Survey and Request)

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image001.jpg

Installation and Configuration Guide

Version 5.0.3

 

Revised  July 12, 2011

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image002.jpg

 

 


© 2011, Kinetic Data, Inc.

Kinetic Data, Inc, a BMC Software® Solutions Partner.

Remedy, a BMC Software Company

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


Contents

 


Figures

Figure 1: InstallAnywhere timing screen. 9

Figure 2: Introduction screen. 10

Figure 3: Choose Installation Folder11

Figure 4: Installation Option. 12

Figure 5: ARS Connection information. 13

Figure 6: Web Application Context Information. 14

Figure 7: Please Wait15

Figure 8: Choose a File. 16

Figure 9: Enter License Keys. 17

Figure 10: Please Wait18

Figure 11: Kinetic SR Web User19

Figure 12: Please Wait20

Figure 13: Web Component Details - No Web Install21

Figure 14: ARS Web Configuration Information – New Tomcat Install22

Figure 15: Web Component Details – New Tomcat Install23

Figure 16: Please Wait24

Figure 17: Tomcat port in use warning. 25

Figure 18: Tomcat Shutdown Port in use warning. 25

Figure 19: Tomcat Manager User Credentials. 26

Figure 20: Tomcat Optimizations. 27

Figure 21: JDK Directory. 28

Figure 22: Web Configuration Information – Existing Tomcat Install29

Figure 23: Web Component Details - Existing Tomcat Install30

Figure 24: Select the deployment folder31

Figure 25: Pre-Installation Summary. 32

Figure 26: ARS Data and/or Definition Import33

Figure 27: Installing Kinetic SR. 33

Figure 28: Install Complete. 34

Figure 29: Kinetic SR Web Administration Console – Properties. 38

Figure 30: Configuration Manager40

Figure 31: Configuration Menu Hyperlinks. 41

Figure 32: Kinetic SR Administration Console – Properties. 42

Figure 33: Web Administration Console - Task Manager45

Figure 34: Web Administration Console – Import46

Figure 35: Web Administration Console - Export47

Figure 36: Web Administration Console - Logging. 48

Figure 37: Web Administration Console – Dependencies. 49

Figure 38: Web Administration Console - Licensing. 49

Figure 39: Change Web Server50

Figure 40: Categories Tab. 51

Figure 41: Users Tab. 52

Figure 42: Configuration Items Tab. 52

Figure 43: Exceptions Tab. 54

Figure 44: Web Logging Level Choices. 54

Figure 45: Audit Tab. 55

Figure 46: Kinetic Audit Information. 55

Figure 47: Web Messages Tab. 56

Figure 48: Manage Messages Tab. 56

Figure 49: Attribute Types Tab. 57

Figure 50: Add/Modify Attribute Type dialog. 58

Figure 51: Configuration Manager, Style Tab. 59

Figure 52: Pattern Tab (Add)60

Figure 53: Deleted Templates Tab. 61

 


Chapter 1                             Overview

Kinetic SR (Survey and Request)

Important


Kinetic SurveyTM and Kinetic RequestTM are comprehensive Enterprise Feedback Management (EFM) applications for creating and administering all types of templates, reports and forms using BMC Remedy Action Request System® (AR System). 

To install Kinetic SR software, an installer must be a Remedy Administrator and have some knowledge and access to your intended Web server. 

This manual is intended for AR System administrators, not users or managers.


This installation and configuration guide is applicable to both applications.  References will be to both systems, simultaneously, as Kinetic SR

The Installer Overview

Kinetic SR is typically installed using an executable installer and includes two parts:  Installing the Remedy forms, workflow and data, and installing a Tomcat Web Server and Kinetic SR Web component.  The installer does include an option to choose just the Remedy component, just the web server component or both, so it may be run multiple times to accommodate your environment.  

For the Remedy component the installer can be run from any Windows machine.  The installer will connect to your Remedy server to import the necessary components and configure the necessary data. 

TIP


Often an Administrator will choose to install the Tomcat web component in a development environment to get running quickly.  Then for a staging/production environment, manually install the web application to an existing web server.


For the web component, the installer must be run on the machine that is to host your web server and again must be a Windows machine.  If you prefer to install the web component on another operating system, a different web server, or an existing Tomcat instance, just install the Remedy components and follow the directions later in this manual to manually deploy the web application. 

 

Pre-requisites

§  BMC Remedy AR Server 6.3 or greater.

o    If you are installing into 6.3, you will need the BMC Remedy Administrator tool to run the installer.

§  32-bit Java Development Kit (JDK) 1.5 or greater (required only if Tomcat will be installed on this server).

§  If Tomcat is not going to be installed, a stand-alone Servlet Engine such as Apache Tomcat 5.5 or Apache Tomcat 6.0 is required with a 32-bit JDK version 1.5 or above.

Licensing

Kinetic SR is licensed per AR System server and per Kinetic SR Manager user.  

Server licensing

 

Note: 

Kinetic Survey and Kinetic Request are licensed separately.  If both applications are purchased, a license key is included for each application. 

 

If an organization has a production server and a development server, it’s necessary to purchase a license for each server. 

The applications are licensed per Remedy server.  The license key is tied to your AR System or your Remedy Server.  An organization can choose to have as many web servers as needed pointing to a Remedy server, but licenses are purchased per Remedy Server. 

Each AR System production server, on which Kinetic SR is installed, must have its own license.

User (Manager) licensing

Kinetic SR Managers can use both Kinetic Survey and Kinetic Request with one license purchase.  Manager licenses are named licenses, meaning they are tied to specific Remedy User records.

Example:  If Jane works in Kinetic Survey and Kinetic Request, she does not need two Manager licenses, but only one in order to access both systems.  But if Jane works only in Kinetic Survey and Joe works in Kinetic Request, they will each require one Manager license. 

If the number of users exceeds the number of licenses purchased, users receive a warning dialog when opening the manager console. There is no limitation to the number of inspectors or submitters (customers) using the system.

Remedy AR System licensing

Kinetic SR licenses are in addition to any AR System licenses needed for your users, and do not take the place of AR System licenses. See AR System documentation. 

Support

For customer service support, go to the support section of our Web site http://www.kineticdata.com or call 651-695-8566.

Chapter 2                             Installation

Downloading the Installer

To download the installer, follow the instructions from Kinetic Data when you receive your license key.  The installer consists of one file (Setup.exe) that will be run from a Windows machine. 

Running the Installer

The following are instructions for using the installer. 

1.             Double click on the “KineticSR_5.0.2.exe” icon.  The InstallAnywhere timing screen will appear as the contents are unpacked.  

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image003.jpg

Figure 1: InstallAnywhere timing screen


2.             The InstallAnywhere Introduction screen states the software title and version currently being installed on your system. InstallAnywhere will guide you through the installation.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image004.jpg

Figure 2: Introduction screen

3.     Click Next.

4.         From the Choose Install Folder screen select where you would like to install the locally installed components.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image005.jpg

Figure 3: Choose Installation Folder

5.         Click Next.


 

6.         The Installation option screen appears.  From here you can choose to install the ARS Definitions and/or installation options for the web component.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image006.jpg

Figure 4: Installation Option

7.         Check the ARS checkbox to install the Remedy forms and workflow for Kinetic SR.

8.         Choose the web component option that is appropriate:

a.     Local Tomcat webserver:  A new instance of Apache Tomcat will be installed in the installation folder selected in step 4, and configured for use with Kinetic SR.

b.     Add to an existing Kinetic Tomcat installation: Apache Tomcat will not be installed with this option.  Select this option if a Kinetic installed Apache Tomcat instance already exists on the local server.  The web application files will be installed inside this existing Tomcat instance. For example, you have already installed Kinetic Calendar, and are adding Kinetic Request and/or Survey.

c.     Don’t install web component:  No web component files or Tomcat instance will be installed.

Installing ARS Definitions and Data

If you chose to install the ARS component, you will need to provide the installer with the AR Server information that you are installing Kinetic SR to.

1.             From the ARS Connection Information Screen enter your ARS information including login information, server and ports. 

This information is used to connect to your AR Server if you are installing the ARS components, and for the web server configuration, as well. 
 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image007.jpg

Figure 5: ARS Connection information

2.         Enter the AR Server name or your Remedy server name. 

Note:  If you typically connect to your AR Server via a fully qualified name, enter that name here. 

 

Example: ARServer.mycompany.com

 

This server name must exactly match the server name provided to Kinetic Data when generating your license key. 

 

3.         Enter the Login name.  If installing the ARS components, this person must have administrator access.  It will be through this user that the forms and definitions will be imported into your server.  If only the web component is being installed, this user can be an existing Kinetic SR “default web user” or an Administrator.

4.         Enter the corresponding Password for the login name.

5.         Enter TCP and RPC ports.  If you have ports configured for your AR Server, enter them here.  If you do not then leave them as “0.”

6.         Enter the Authentication string if used.  If not, leave blank. 

7.         Review all lines for accuracy. 

8.         Click Next. 

9.         The Web Application Context Information screen appears.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image008.jpg

Figure 6: Web Application Context Information

Note:  This screen will only be displayed if installing the ARS Component.

10.        Enter a Mid-Tier server context to reflect the path to your mid-tier server, complete with the Mid-tier context.  For example:  http://mymidtierserver.mycompany.com/arsys/
 

11.       Enter a Kinetic Task server context to reflect the path to your Kinetic Task Engine, complete with Kinetic Task context.  For example:

http://mymidtierserver.mycompany.com/kineticTask/

12.       Click Next. 

Please wait while Kinetic SR is being configured.  The system is retrieving the server version and applying the correct information, as well as verifying that the user is an Administrator and has the correct permissions.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image009.jpg

Figure 7: Please Wait


 

13.          If you are installing on a Remedy 6.3.0 server you will be now see the Choose a File screen.  This screen asks you to choose the location of your Remedy Administrator tool.  This happens because the API used by this installer cannot run against a 6.3 server so an Admin tool must be used.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image010.jpg

Figure 8: Choose a File

14.          The file location will be prepopulated with the location of any Remdy Administrator tool that the installer was able to find on the local system.  If this is not the correct location, select the location of the Remedy Administrator tool (aradmin.exe) that you wish to use by clicking the Choose button.

15.  Click Next.

 


16.       The license key screen appears next.  You may enter your license keys on this screen, or do it after the installation using the Remedy User tool.  If you do enter them here, it is best to simply copy and paste the values from the email you received from Kinetic Data.  Make sure there are no spaces before or after the serial numbers.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image011.jpg

Figure 9: Enter License Keys

17.       Click Next. 


Again, please wait while Kinetic SR is being configured.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image012.jpg

Figure 10: Please Wait


The Kinetic SR Web User screen appears (NOTE:  Screen does not appear when only installing into an existing Kinetic Tomcat instance). Kinetic SR needs to create a default user record with the appropriate credentials to handle some interactions with the AR Server.  The user entered here will be created with the appropriate groups and a fixed license.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image013.jpg

Figure 11: Kinetic SR Web User

 

Note:  If there are multiple web servers connecting to a single Remedy server, other users will need to be manually created; one for each web server.

18.         By default, this login name is called KD_WEBUSER.  You may change it if you see fit.

19.       Enter a Password.  Use your company’s normal protocol. 

20.       Click Next.


Again, please wait

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image014.jpg

Figure 12: Please Wait

21.         The Web component details screen appears.


Web Component Details

The Web Component Details screen will vary in appearance based on options you selected in a previous screen.  The following sections will walk you through the remainder of the installation based on the options you have selected.

 

 

Don’t install web component

If you selected the “Don’t install web component” option you will still be prompted for a couple of simple web component details.  These items will be used to configure the Remedy data for the application. 

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image015.jpg

Figure 13: Web Component Details - No Web Install

 

1.             Enter the Web Server Name used in your implementation.  This is typically the name of the web server, but may be an alias or an IP number.  This will be used for configuring the sample data.  This field is not visible if not installing the ARS component.  Example:  “mywebserver.mycompany.com” or “209.98.44.22”.

2.             Enter the Port Number that the Tomcat server is or will be listening  on.  By default, Tomcat listens on port 8080. 

3.             Click Next.  This will take you to the Pre-Installation Summary and you can skip the remainder of this section.


Installing a Local Tomcat Web Server

The first screen shown depends if the ARS component is being installed, or if you are only installing the web component.  If you are only installing the web component, you will see a screen to enter the ARS information that your web component will be conecting to.  This information is needed to automatically configure the Kinetic SR web application properties file.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image016.jpg

Figure 14: ARS Web Configuration Information – New Tomcat Install

1.     Enter the AR Server name or your Remedy server name. 

Note:  If you typically connect to your AR Server via a fully qualified name, enter that name here. 

Example: ARServer.mycompany.com

This server name must exactly match the server name provided to Kinetic Data when generating your license key. 

 

2.             Enter TCP and RPC ports.  If you have ports configured for your AR Server, enter them here.  If you do not then leave them as “0.”

3.         Enter the Authentication string if used.  If not, leave blank. 

 

4.         Kinetic SR needs to create a default user record with the appropriate credentials to handle some interactions with the AR Server.  The user entered here will be created with the appropriate groups and a fixed license.  Enter the Login name of the Kinetic Web User.

5.         Enter the corresponding Password for the login name.

6.         Click Next. 

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image017.jpg

Figure 15: Web Component Details – New Tomcat Install

7.             Enter the Web Server Name to use for your installation.  This is typically the name of the web server, but may be an alias or an IP number.  This will be used for configuring the sample data.   Example:  “mywebserver.mycompany.com” or “209.98.44.22”.  Note:  this field is not visible if not installing the ARS component.

8.             Enter the Port Number you want the Tomcat server to listen on.  By default, Tomcat listens on port 8080.  If the port entered here is already in use by another application (another Tomcat instance for example), you will be alerted and prompted to select a new port number.

9.             Enter the Shutdown Port Number for Tomcat to listen for the shutdown command from the system.  If the port entered here is already in use by another application (another Tomcat instance for example), you will be alerted and prompted to select a new shutdown port number.

10.          Choose which Tomcat administration application to install with the Tomcat server.  These applications are useful for administering and managing the Tomcat server, but they are not required.

11.          Click Next.  A Please Wait screen appears while Kinetic SR configures your system.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image018.jpg

Figure 16: Please Wait

12.       If you have entered a Port number that is currently in use, a warning dialog will appear.  Click OK for the previous screen to appear and enter the new Port number. 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image019.png

Figure 17: Tomcat port in use warning

 

13.       If you have entered a Shutdown Port number that is currently in use, a warning dialog will appear.  Click OK for the previous screen to appear and enter the new Shutdown Port number.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image020.jpg

Figure 18: Tomcat Shutdown Port in use warning

14.       If you selected to install either the Tomcat Manager Application or the Tomcat Admin Application, a screen will appear to that allows you to create a Tomcat manager/admin user.  Please note, this user is not a Remedy user and will not create a record in the Remedy User form.  It is simply an account on the Tomcat server to allow access to the Tomcat Manager and Tomcat Admin applications.  This screen will be skipped if you did not select to install either application.

 File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image021.jpg

Figure 19: Tomcat Manager User Credentials

15.       Click Next.

16.       The Tomcat optimization screen will appear.  Here you can choose to install Tomcat with performance tuned production mode optimizations, or development mode settings (default).

a.     Production mode optimizations tell Tomcat to only compile JSP pages when the service starts.  This provies better performance because the Tomcat server doesn’t need to check the JSP pages for changes every time the page is served.  If any JSP pages are changed however, the Tomcat service will need to be restarted for the changes to become effective. 

b.     Development mode settings allow the JSP pages to compile on the fly, without requiring a Tomcat service restart.  There is a performance penalty with this because the Tomcat server must check the JSP page for changes every time the page is served.

17.           The Min Heap Size is the amount of memory allocated to the Java Virtual Machine when the Tomcat service starts.  The maximum value that Microsoft Windows supports is 1024 MB.

18.          The Max Heap Size is the maximum amount of memory allocated to the Java Virtual Machine.  The maximum value that Microsoft Windows supports is 1024 MB.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image022.jpg

Figure 20: Tomcat Optimizations

19.       Click Next.

 


File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image023.jpg

Figure 21: JDK Directory

20.       From the JDK Directory screen (Shown for new Tomcat installations only), locate an existing JDK installation folder.  Click Choose to browse for the location.  JDK 1.5 or greater is required.

21.       Click Next.  You will see another Please Wait screen followed by the Pre-Installation Summary.  You can skip the remainder of this section to receive instructions on finishing your installation.


Installing into an Existing Tomcat Server

The first screen shown depends if the ARS component is being installed, or if you are only installing the web component.  If you are only installing the web component, you will see a screen to enter the ARS information that your web component will be conecting to.  This information is needed to automatically configure the Kinetic SR web application properties file.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image024.jpg

Figure 22: Web Configuration Information – Existing Tomcat Install

1.           Enter the AR Server name or your Remedy server name. 

Note:  If you typically connect to your AR Server via a fully qualified name, enter that name here. 

Example: ARServer.mycompany.com

This server name must exactly match the server name provided to Kinetic Data when generating your license key. 

 

2.           Enter TCP and RPC ports.  If you have ports configured for your AR Server, enter them here.  If you do not then leave them as “0.”

3.           Enter the Authentication string if used.  If not, leave blank. 

 

4.           Enter the Login name of an existing Kinetic Web User.

5.           Enter the corresponding Password for the login name.

6.           Click Next.

7.           The next screen is the web component details screen.  The installer is asking for the web server name and port number because it uses these values to automatically set some configuration properties in the Kinetic SR web application properties file.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image025.jpg

Figure 23: Web Component Details - Existing Tomcat Install

8.             Enter the Web Server Name to use.  This is typically the name of the web server, but may be an alias or an IP number.  Example:  “mywebserver.mycompany.com” or “209.98.44.22”.

9.           Enter the Port Number the Tomcat server is listening on.  By default, Tomcat listens on port 8080.

10.        Click Next.

 


11.        The Web server directory screen appears.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image026.jpg

Figure 24: Select the deployment folder

12.        Choose the “webapps” folder for your existing Kinetic Tomcat installation.  This is where the “kinetic” web application will be installed.

13.        Click Next.


Completing The Installation

1.             From the Pre-Installation Summary screen, please review the following for accuracy before continuing. 

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image027.jpg

Figure 25: Pre-Installation Summary

2.         Click Next.  If you selected to install the ARS portion, the ARS Data and/or definition import screen appears verifying that you have elected to import ARS data and/or definitions. 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image028.jpg

Figure 26: ARS Data and/or Definition Import

3.         Click Install.  This process will take a while as Remedy forms, workflow and data are imported to the AR System Server.  Please do not interrupt the process until the Install Complete notification has appeared. 

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image029.jpg

Figure 27: Installing Kinetic SR

4.             After the installation is complete, you may be asked to restart your computer if the Tomcat Web Server was installed.  

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image030.jpg

Figure 28: Install Complete

5.         From the Install Complete screen click either, Yes, restart my system, or No, I will restart my system myself. 

6.         Click Done.  The installation of Kinetic SR is finished.

 

Congratulations.  Kinetic Survey and Kinetic Request are now installed on your server. 

If any warnings occurred you can view the log files in the installation directory you chose at the beginning of the installation.

Inside the logs directory, an individual log is created for each component installed and data file imported. 

 

Note:  For each set of data imported, see .arx.log.  For each set of work flow imported, see .def.log (Remedy forms). 

 

Support:  For customer service, please contact the support section of our web site http://www.kineticdata.com or call 651-695-8566.   


Chapter 3                             Other Web Servers

 

Kinetic SR can be installed with a stand-alone Apache Tomcat server for easy deployment.  However, in many situations, another Servlet Container may be required. 

 

Kinetic SR is created as a standard J2EE web application and can be deployed into almost any standard Web Server/Servlet Container including Tomcat, Websphere, and ServletExec AS. 

 

The following sections describe the general process for deploying to other servlet containers.   Each container may have other processes for deploying an application.  Please refer to your specific documentation for complete instructions.

 

Note:  The terminology for web servers may be confusing.  Servlet containers are often called web servers.  However, not all web servers are servlet containers and some servlet containers require a separate web server.  Some examples may help:

 

  • IIS:  Web Server (not a servlet container)
  • ServletExec IS:  A lightweight servlet container that requires a web server front end like IIS.  This is what Remedy Mid-Tier was bundled with prior to version 7.
  • ServletExec AS:  The application server version of ServletExec.  This can run as a servlet container and web server, or can connect up to IIS or other web servers for front end page serving.
  • Apache Tomcat:  An open source servlet container that can also be used as a stand-alone web server.
  • Apache Web Server:  An open-source web server.  This is not a servlet container, and is often paired with Tomcat as a back-end servlet container.

 

Deploying Kinetic SR

Deploying Kinetic SR to a web server involves moving the directories included in your installation to your web server as well as configuring some of the web server properties.  

 

NOTE:  If you need a WAR file for your environment (Web application archive), it can be found in the Web folder of the Installation Directory listed below. 

 

Terminology:

  • Installation Directory: This is a backup copy of the web application files that the installer placed on the local hard drive.  The default location for this directory is C:\Program Files\Kinetic Apps\Kinetic SR\.
  • Deployment Directory <webapps>: This is the directory where your web server is hosting your web application.  Please consult your web server manual if you need help determining where your web server’s deployment directory is located.
    • An example for Tomcat would be: <TomcatDir>\webapps\
    • An example for ServletExec AS would be:  C:\Program Files\New Atlanta\Servlet Exec AS\se-<instance>\webapps\

 

 

  1. Locate the installation directory chosen at the beginning of the installation process.  The required files have been included in the Web directory.
     
  2. Move the “kinetic” directory into the web server’s deployment directory for automatic deployment, or another desired location on your web server.
     
  3. Add the kinetic application context to your web server configuration.  This is often done from a management/configuration screen for your environment.  Typically this involves:
    1. Naming the application. Example “KineticSR”
    2. Including the URL context.  The default is “/kinetic/”
    3. Including the path to the kinetic directory moved in step 2.
    4. NOTE: If a Tomcat server is used and the application was moved into the Tomcat deployment directory, this step is not necessary as Tomcat will automatically add the application when the service is started.
       
  4. Include the ARS API files specific to your ARS installation.  If you are installing Kinetic SR on the same instance of a web server running BMC Remedy Mid-tier, please read the next section on Shared Java Resources before doing this step.

    The kdi_arshelpers.jar file is included as part of Kinetic SR.  The other API files are also included in the installation directory.  However, we suggest getting the latest version/patch that your ARS Server is using.  You can typically find these in your AR System/ARServer/Api/lib directory, or in the WEB-INF/lib directory of your Mid-Tier installation.  These can also be downloaded from http://www.ARSWiki.org.

    Place these files in the <webapps>/kinetic/WEB-INF/lib directory.  This would include minimally:
    1. kdi_arshelpers.jar found in <installation directory>/Web/
    2. arapi6x/7x.jar
    3. arutil6x/7x.jar
    4. If no other Remedy applications are installed on your machine (such as Midtier/Flashboards/Email Engine etc), you will also need to include the Remedy API dynamic link library (DLL) files.  You can look in the  <installation directory>/Web/<your AR Version> to see what files are necessary.   The location of the API DLL files must be included in the system PATH.

 

  1. If you had to add the location of the Remedy API DLLs to the system PATH variable, you will need to restart your server.

 

  1. Restart your Web Server/Servlet Container.

 

  1. You are now ready to configure your Kinetic SR web application with your Remedy server information.  Please see the next section Configuring the Web Application Properties.

 

Configuring the Web Application Properties

If you have successfully deployed the Kinetic SR web application, you will need to configure it with the Remedy server information, and a few other configuration items.

 

  1. Open your web browser and connect to the Administration Console.  http://<webservername>:<port>/<context>/AdminConsole

 

Replace the following items with your web server specific values:

<webservername>         Name or IP of your web server.

<port>                                  Port your web server uses (8080)

<context>                           Context of application (kinetic)

 

  1. This web page requires authentication to gain access to it.  Only Remedy Administrators have access to it, with the exception of a configuration administrator user.  This user is necessary for first time access to the system because a Remedy server has not yet been configured, so the web application doesn’t know where to authenticate.

 

  1. Log in with the default configuration administrator for this web server (admin/admin).  After logging in, the credentials for this user may be changed.

 

  1. Now edit the properties for your Remedy server.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image031.jpg

Figure 29: Kinetic SR Web Administration Console – Properties

 

  1. Click the ‘Edit Properties’ button to enter your Remedy server and user properties.  Please see Web Admin Console - Properties Tab for a description of each property.

 

  1. Click the ‘Update Properties’ to save your changes, or click the ‘Cancel’ link to discard your changes.

 

 

Shared Remedy Java Resources

Because the BMC Remedy Java API uses a JNI interface, there are some special requirements if the Servlet Container running Kinetic SR is also running BMC Remedy Mid-Tier. 

 

A few notes on sharing a servlet container:

 

  • Kinetic Survey/Kinetic Request can no longer be installed inside your Mid-tier application (inside the Mid-Tier directory) as it could in previous versions of the product.
     
  • ServletExec ISAPI is not supported if Mid-Tier is already installed inside this container because shared libraries are not available.  ServletExec AS is supported, and ServletExec ISAPI is supported if Kinetic SR is the only Remedy-based web application running.
     
  • If you are setting up a new environment we suggest installing BMC Remedy Mid-Tier first.  Testing your install, then installing Kinetic SR Web component as described earlier.

 

Important Note:  Kinetic SR cannot be installed in a Servlet Container running BMC Knowledge Management.  If your Servlet Container is running BMC Knowledge Management, you will need to install another instance of the Servlet Container, or another Servlet Container altogether.

 

Shared Jar files

To run the applications together in the same instance, you must move some jar files that both applications need to a directory that is available to your container for this purpose.  To do this:

 

 

  1. Copy the arapi6x/7x.jar and arutil6x/7x.jar from BOTH the kinetic/WEB-INF/lib (if present) AND your Mid-Tier/WEB-INF/lib directories.  You will need these files in the next step.

 

  1. Place these files in the shared directory for your servlet container:

 

    1. For Tomcat this is in <tomcat_folder>/shared/lib/
       
    2. For ServletExec AS, this is <servletexec_folder>/<SE instance>/classes/

      For SE you must also alter the <servletexec_folder> /<SE instance>/StartServletExec.bat script to include these three files in the classpath. You will see a –classpath line followed by many paths, each separated by a semi-colon.  Enter the path to each jar after the last item in the path.
       
    3. For other web servers or more information, please your specific server’s documentation.

 

  1. In a shared environment, you should not include the other DLL’s/libraries that you would typically include in your kinetic/WEB-INF/lib directory.  These are already included in the Mid-Tier server and added to the PATH environment variable for your server. 

 

IMPORTANT NOTE:  When you upgrade your Mid-Tier server in a shared environment you will need to again remove the jars from your Mid-Tier/WEB-INF/lib directory.  You should replace the files in the shared directory with these new files.

Chapter 4                             Configuration Manager

 

The Configuration Manager allows Remedy Administrators to monitor and control some of the behaviors of Kinetic Survey and Kinetic Request.

Remedy Administrators can access the Configuration Manager via the “Configuration” link on the left side of either the Kinetic Survey Author console or the Kinetic Request Service Catalog Console. 

It is within this area that an administrator can manage configuration items including the ability to:

§Set configuration items like default web server and the license keys.

§Monitor stuck email messages.

§Arrange answer patterns from which users can choose

§Create error messages that submitters will see, and much more.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image032.jpg

Figure 30: Configuration Manager

Configuration Manager Hyperlinks

The hyperlinks located on the left side of the Configuration Manager provide access to these configuration applications.  The hyperlinks, visible only to Remedy Administrators, include:

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image033.png

Figure 31: Configuration Menu Hyperlinks

Web Admin Console

The web admin console hyperlink opens a web browser to the web application’s administration console page.  The administration console is comprised of multiple pages that provide administrators with tools to configure the web application properties, manage service catalogs and surveys, and troubleshoot problems.  The web admin console is where a Remedy Administrator will go to import and/or export survey and request templates.

Exporting and importing templates involves taking an entire template with all the elements, styles, etc., and moving it “out of” (export) or “into” (import) your survey or request environment. 

 

Note:

The exporting and importing tabs, make it easier for a user to create a template on a development (or staging) environment and then move that template over to production, or another server. 

NOTE: This action includes the definition of your “template” information.  It does not export data related to submitted requests. 

Anything that requires merging or migrating to a production or a staging environment would be accomplished here.  In addition, sharing templates or downloading new samples from Kinetic Data is also much easier.

Migrating a template is a two-step process.  First, export the template out from your “Source” server.  This process will create a zip file that contains the Remedy data files for all the forms the template uses, along with a text file of the export information. 

The next step, Importing, involves taking the newly created zip file and importing it into your “Destination” server.  This two-step process is important for audit ability when moving from one environment to another.

Importing and exporting information is provided below, in the import tab and export tab sections.

Properties Tab

The Properties tab provides the ability to configure the web application settings, so it knows what Remedy server to connect to, what Remedy user credentials to use to login with, etc.  Each property setting is described below.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image034.jpg

Figure 32: Kinetic SR Administration Console – Properties

Remedy Server Settings
  • Enter the Server 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 SR licenses.

 

  • Enter the Remedy server’s TCP Port.  If your Remedy server uses portmapper, enter 0.

 

  • Enter the Remedy server’s RPC Port.  If your Remedy server is not using a specific RPC port, enter 0.

 

Encryption Settings
  • If you would like the web application to store the web user passwords encrypted in the properties file, check the Encrypt Passwords checkbox.

 

Web User Settings
  • Enter the Default User and Default Password for the Remedy user account that the web application will use to create Remedy records.  This must be an existing Remedy user and it must have a fixed write license.  This user also must belong to the KS_CORE and KS_SRV groups at a minimum.

 

  • You may also enter an optional Alternate User and Alternate Password.  This user account will be used if the default user account is not available or cannot connect to Remedy for some reason.  You can also choose to leave this value blank.

 

Task Manager Settings
  • Indicate if the task manager service should run on this web server by checking the Enable checkbox.  Kinetic Request uses the task manager to process tasks, such as approval records or to create records in other AR System forms, that are defined in service items.  The task manager polls the Remedy server to check if there are any tasks ready for processing.  If your Remedy server is only licensed for Kinetic Survey, you do not need to enable the task manager service. 

 

Note:  If you have multiple web servers pointing to the same Remedy server, ensure only one instance of the task manager service is enabled.

 

·         The task manager Query normally will not need to be modified.  The task manager service uses this query string as the Remedy qualification to check for pending tasks.

 

·         The Sleep Delay property determines how frequent the task manager service will poll the Remedy server.  The default value is 60 seconds, which means that a task may take up to 1 minute to be processed after a service request has been submitted.  We have found that this value is fast enough for most situations. 

 

CAUTION: If you must lower this value so the task manager service process records more frequently, take care not to set this value too low, or you may have tasks being processed multiple times.

 

Default Logger Settings

·         Enter the Log Level that the system will use to determine 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.

 

·         Enter the Max Log Size to limit the log file.  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.

 

·         If you want to further customize the information that is captured, enter the location of the logging properties file in the Log Properties File field.

 

Miscellaneous Settings

·         The Max Chars on Submit property is a way to limit the amount of data submitted to the web server.  This is a security measure to protect the server from becoming overloaded.  The default value for this property is 4000 characters.  If you have very large surveys or service items, you may need to increase this value.

 

·         The Map Fields Count limits how many fields may be mapped in a data set.  The default value is 128.

 

·         The Max Cache Size limits the number of fields that are cached on the server.  Caching provides a way to increase performance as certain data only has to be retrieved from the database once, but it does consume memory, so it must be limited.

 

SSO Adapter Settings

If you have a single sign-on solution that your company uses, and would like to include Kinetic SR with the technology, you need to tell the web application where this adapter is located.  For more information on writing a single sign-on adapter to work with Kinetic SR, please see the Kinetic SR Single Sign-On Adapter Tech Note.

 

·         The SSO Adapter Class setting is the name of the SSO Java Class.  If the SSO adapter is not used, leave this value blank.

 

·         The SSO Adapter Properties setting is the fully qualified filename of the SSO adapter properties if the adapter uses a properties file.

 

Configuration Administration Credentials

The configuration administration user is a built-in user for the web application.  This user has the ability to configure the web application properties to connect to a Remedy server.  This user is strictly used for configuring the web application, and is completely independent from Remedy.  Therefore, the user does not exist in the Remedy User table.

 

·         Enter the configuration administrator username in the Config Admin User field.  The default value is admin.

 

·         Enter the configuration administrator password in the Edit Password field.  The default value is admin.

 

Task Manager Tab

The Task Manager tab provides the ability to start and stop the Kinetic Record Poller service if it has been enabled in the properties.  This service polls your AR System server at regular intervals, creating approvals and other AR System records when indicated.  The status is also displayed, indicating if the service is currently running, stopped, or in a failed state.

 

Typically, this service runs on one web server.  Care should be taken if running in multiple web servers to alter the query so each web server is handling a subset of all tasks.  This query is managed in the properties tab of the Web Administration Console on each of your web servers.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image035.jpg

Figure 33: Web Administration Console - Task Manager

 

Import Tab

Importing only includes the definition of your “template” information and does not import information received from filled-out surveys or requests. 

The importing function looks at a selected file or template from your importing source and compares it to the destination file or template.  It evaluates and coordinates the two so they are “mirror” images of each other.  It performs this function by adding “new” records, and modifying and deleting existing records not included in your import source.

Important Note:  If a question is on your destination server, but not on your source server (meaning the question was deleted), when importing the template, this question will be deleted, along with any answers, on your destination server.  For historical reasons, it is often desirable to hide questions that are no longer needed rather than deleting them.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image036.jpg

Figure 34: Web Administration Console – Import

 

1.     Click Load to import a zip file.

2.     Open the choosen file and click Upload to bring the zip file into the Template Import File location.  See Figure above.

Clear:  A file can be changed by clicking Clear to empty the field.  Click on Load, again, to locate another file and Upload to enter the file into the Template Import File field.

3.     Click the Import button at the bottom of the form.  Expect a pause as the system migrates (or imports) this new information into your server.

4.     As the data is moved from one server to the other, The web server setting from your source server data will now be set on your destination server.  You will likely want to update this web server information.  This can be done from the “Advanced” tab of the Manager consoles, or from the Update Web Server link discussed in the next section.

 

 

Export Tab

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image037.jpg

Figure 35: Web Administration Console - Export

 

1.     From the Template drop-down selection, choose the template you want to export from the menu provided.  Include the Category/Service Catalog Definition,  Data Set, and Related Message Templates if applicable. 

Note:  If the categories, data set, or related message templates boxes are checked when exporting templates, they will override those existing categories and data sets in your destination template when imported.

2.     Click Submit.  The server will collect the data for all forms that the template uses, and package them in a convenient zip file.   A link will then be displayed to allow you to download the zip file to your local computer.

3.     Click Download the Zip.  A prompt will appear to download.

4.     Save the information through the browser, to your desktop, hard drive or network.  Information is now ready to be imported into your destination file or template

 

Logging Tab

The logging tab displays a snapshot of the latest 200 entries from the web application log file.   This provides an easy way to view the log file for administrators that do not have file system access to the web server.

Note:  The information displayed on this page is a snapshot of the last 200 entries in the log file when the tab was clicked.  This is not live information.  The page must be refreshed to load log entries that came in after the page was originally loaded.

Also provided on this tab is a link to download the entire log file to your local computer.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image038.jpg

Figure 36: Web Administration Console - Logging

 

Dependencies Tab

The dependencies tab displays important information about the Java library dependencies for the Kinetic SR web application.  It displays the name of all the dependent libraries, along with the version number (or file date if version is not available), the full name of the library’s jar file, and the confidence level of the version information. 

This could be helpful information when working with Kinetic Data support in troubleshooting an issue.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image039.jpg

Figure 37: Web Administration Console – Dependencies

 

 

Licensing Tab

The licensing tab contains information about your Kinetic SR licenses.  This information is retrieved from the license keys stored in the Configuration Items on the Remedy server.

This could be helpful information when working with Kinetic Data support in troubleshooting an issue.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image040.jpg

Figure 38: Web Administration Console - Licensing

 

Update Web Server

Use the Update Web Server hyperlink to reflect the web server that this template should be deployed to by default.  This is particularly helpful when migrating from a development server to a production server, or updating sample data as a batch.  This process will work on a single template, or a group of templates.

1.     Clicking on the Update Web Servers hyperlink brings up the Change Web Server dialog. 

This dialog enables you to pick one, some, or all of your current templates and set them to deploy to another web server individually or at the same time. 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image041.jpg

Figure 39: Change Web Server

2.     Choose one or more templates from the table field to update.  If you started from Kinetic Survey you will only see Survey templates, if coming from Kinetic Request, you will only see Service Items. 

3.     Select the New Web Server URL from the menu.   

4.     Click Update.  The process may take a few minutes if many templates are selected.  When using this tool, image links and other html references will be changed in each template, and take time to process.

Configuration Manager Tabs

The Configuration link allows administrators to configure parts of Kinetic SR including:

§Categories Tab (Kinetic Survey Only)

§Users Tab

§Configuration Items Tab

§Exceptions Tab

§Audit Tab

§Web Messages Tab

§Manage Messages Tab

§Attribute Types Tab

§Style Tab

§Pattern Tab

§Deleted Templates Tab

Note:  The Tabs entitled Categories, Attribute Types and Style are application specific to either Kinetic Survey or Kinetic Request (i.e. Categories does not appear in Kinetic Request, while Attribute Type and Style contain similar but different information for each application). 

Categories Tab

The categories tab displays a list of all Kinetic Survey Categories.  Existing categories can be modified or deleted from this console, and new categories can be added.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image042.jpg

Figure 40: Categories Tab

Users Tab

The users tab displays a list of users that have permission to one or more “KS_SRV” groups.  From this tab you can highlight a user to view their record or create a new user.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image043.jpg

Figure 41: Users Tab

Using one of these buttons will open your AR System User form.   The Configuration Manager dialog needs to be closed before the User record can be modified.

See your AR System documentation for more information on adding or modifying users.

Configuration Items Tab

The configuration items tab displays information on the configuration of your system.  This is typically used during the installation of the application and does not need to be changed unless your environment changes. 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image044.png

Figure 42: Configuration Items Tab

Add a Configuration Item

1.     From Configuration Manager click the Configuration Items tab and click Add.

2.     Make a selection from the Configuration Type drop-down list box.

3.     Select a Locale from the drop-down list box. For example: English (Canadian).

4.     Select a Status from the drop-down list box.

5.     Select a Property from the drop-down list box. For example: Remedy Property or Web Property.

6.     Enter your configuration value in the Configuration Value field. For example: Submit if you select Submit Button Text for the Configuration Type.

7.     Click the ellipses () next to the Configuration Value field to add, edit or delete content in that field.

8.     Click the Save button. Your new Configuration Item is saved.

Modify a Configuration Item

9.     Double click on the Configuration Item. Click the Modify button.

10.  Make your modifications to the Configuration Type, Locale, Status, Property and/or Configuration Value fields.

11.  Click the Save button.

Exceptions Tab

The exceptions tab lists exceptions (errors) users may have experienced while submitting a request via the web. 

Exceptions or errors are written back into Remedy when possible.

They are usually used during a support call or for your Administrator to troubleshoot problems.


Note


§Date, type, severity and description areas are offered describing the exception (or error). 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image045.jpg

Figure 43: Exceptions Tab

The exceptions tab also allows you to view and change the logging level on the Kinetic Survey or Kinetic Request web component.  By changing this value, it changes which messages are actually logged in real time for your web component.  This allows logging level changes without restarting your web server.  Log files are accessible from your web server in the Kinetic Survey or Kinetic Request directory.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image046.jpg

Figure 44: Web Logging Level Choices

Audit Tab

The Audit tab on the configuration manager allows you to view which survey or request templates that have been modified or deleted, and by whom.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image047.jpg

Figure 45: Audit Tab

View an Audit Item:

12.  Highlight the survey or request item you want to look at.

13.  Double-click on the request.

-Or-

Click the View button. The Kinetic Audit dialog displays for you to view the request.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image048.jpg

Figure 46: Kinetic Audit Information

14.  Click the Close button when you’re done viewing the audit data.

15.  Click the Close button on the Security Console dialog to end your session.

Web Messages Tab

The web messages tab displays the different error messages a user can see when submitting a survey or request.  By default these messages are in English.  These can be updated to include information more specific to your company. 

Web Messages can also be locale-specific.  By setting a locale for your messages (other than English) requests using that locale will display a message in the correct language for your customer.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image049.jpg

Figure 47: Web Messages Tab

 

Manage Messages Tab

 

The Manage Messages tab offers Administrators the ability to view email messages that have not been sent out of the system (in pending status).  Most often, the problem occurs because a message template has been incorrectly formatted. 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image050.jpg

Figure 48: Manage Messages Tab

The Message Template drop-down list allows you to investigate where a delay may be occurring by viewing available message templates. 

 

The Number of Hours Old box allows you to prioritize messages by the oldest “pending status”, or by a particular group of delayed messages. 

 

Attribute Types Tab

The attribute types available to a survey, request, or service catalog can be added and modified from the Attribute Types Tab.  Attribute Types show up on the Settings Tab of the survey or request or on the attributes tab of a service catalog. 

Attributes are useful for attaching additional information to a template or catalog without having to add new fields or workflow.  Such extensions could include items such as costing information, authors, owners, version information and more.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image051.jpg

Figure 49: Attribute Types Tab

 

1.     File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image052.jpgOn the Configuration dialog “Attribute Types” tab, Click New or Modify.  A dialog will appear.

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image053.jpgFile:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image054.jpg

Figure 50: Add/Modify Attribute Type dialog

2.     Choose Parent Form, either KS_SRV_SurveyTemplate for Survey or Service Items or KS_RQT_ServiceCatalog_base for service catalog attributes.

3.     Choose Data Type.  For example, if character is chosen as a Data Type, that choice enables the Enable Pattern Matching and Attach Menu checkboxes, offering a user more control over how request attribute can be adjusted and modified. 

If you choose an Integer in the Data Type, the Enable Range checkbox becomes available.  Enter a numerical range from Minimum to Maximum, Field Length and Default Value

4.     If a Category is set, the data type will only be available to survey or request templates with that Category.  Leaving category blank will make the attribute available to all surveys or requests. 

5.     Click Make Type Mandatory if needed.  This will require that an author fill in this attribute when saving a template. 

NOTE:  Mandatory attributes will only be required once a survey or request template becomes “Active”.  

6.      Click Allow Multiple Instances for those circumstances when an author will need to add multiple values to this attribute type. An example is “Request Business Unit”, where multiple values for a business unit would be entered such as: H.R., Request Business Unit IT, Request Business Unit, Marketing, etc. 

Admin Only Attribute Type are reserved for Kinetic Survey or Kinetic Request “out of the box” attribute types such as expiration date. 

7.     Enable Pattern Matching/Pattern allow you to set a pattern that the attribute follows.  These patterns use Remedy ARS Pattern syntax.  See your administrator guide for available pattern types in Remedy. 

8.     If needed, choose from the Menu Name drop-down list, as shown above. 

9.     Choose Save and Close

Style Tab

The Style Tab is used to manage the look and feel of your requests by displaying the Cascading Style Sheet (CSS) selectors used for any new templates.  The styles listed on this tab will be added to every new template created. 

 

The Kinetic Data product ships with pre-configured information offering basic layout styles for new surveys or requests including default fonts, padding and borders.  Newly created templates will inherit all style information configured for the survey or request product but any style can be changed in the Style Tab.

 

 

Tip:

 

 

 

Note:  Any changes made to styles will not affect previously existing templates, only new templates created from that point forward.

 

Use the Style Tab to make changes for all new templates created.

Use Page Editor for any positioning changes or “element to element” level changes. 

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image055.jpgFile:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image056.jpg

 

Figure 51: Configuration Manager, Style Tab

1.     Click Add to create a new style. 

Or

2.     To make changes to an existing style, highlight the Style Identifier you want to change and click Modify.  Use the drop-down menus and “Helpers”, or type-in changes for style type, selector and properties. 

3.     Click Save and Close

4.     To remove a style, select it in the table and click Delete

 

See Cascading Style Sheets-Predefined Styles (CSS) in the User Manual for more information. 

Pattern Tab

Patterns are used to restrict user input in to certain patterns to better control data entered into Kinetic Survey or Kinetic Request.  Patterns can be used to restrict phone numbers to a certain format, IP addresses to certain range and more. 

 

Kinetic SR uses standard Regular Expressions common to many programming languages to manage patterns.  Writing a regular expression does involve some background knowledge, but there are many existing patterns online as well as tutorials to write your own.


Kinetic SR includes a number of predefined patterns which can be used immediately.  Patterns defined here can be selected on the “Validation” tab when creating a question. 

 

 

A single quote {¢ } must be preceded by an escape character { / }.  

Tip: 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image057.jpg

Figure 52: Pattern Tab (Add)

1.     Choose from the drop-down menu, or type in a Pattern Label.  This is what authors will see when adding a pattern to a question and should be descriptive.   

2.     Underthe Pattern field type in a regular expression specific to the Pattern Label entered. 

3.     Regular pattern coding can be difficult to decipher.  Pattern Notes is an opportunity to offer helpful information for a future Administrator or user regarding this pattern. 

4.     The Defaults field allows you to specify whether this pattern will automatically be selected when an author creates a question of this type.  There should be only one Default response for each type of question.  Typically “Defaults’ is not used except for those included in your installation.

 

Deleted Templates Tab

The deleted templates tab provides Remedy Administrators the ability to manually remove survey and request templates that have been marked as deleted.  It also provides Remedy Administrators the ability to restore the templates to their previous status.

 

File:Documentation/Kinetic_Request/Kinetic_SR_Install_and_Config_Guide/image058.jpg

Figure 53: Deleted Templates Tab

 

 

Installation Troubleshooting

If you encounter errors, and the installation will not continue, you may wish to try running the installer again in debug mode.  To do this, exit the current installation, then run the installation executable again.  Before the progress bar reaches 100%, hold down the Ctrl key until a Windows command terminal opens.  This command terminal is a live log of the installation application, and will hopefully give some additional information to what is causing the error.  Do not close this command terminal, or the installation application will exit.