Skip to main content
Kinetic Community

Get Started

This page provides the files and steps necessary to get KURL up and running.

Requirements

  • Java Development Kit (JDK) 1.6 or greater

  • BMC® Remedy® AR Server 7.0 or greater

  • Kinetic Request 4.4.3 or greater

Downloads

The kurl.jar is an executable JAR file that retrieves and builds Kinetic Request service items to and from KURL code.  The kurl.jar is executed from the command line and requires only a small configuration file to get up and running.

kurl.jar

A YAML configuration file defines the connection to the AR Server that the Kinetic Request instance is installed on.  This file can be downloaded and configured manually, or it can be generated automatically by the kurl.jar during a setup process (recommended).

config.yml

Configuration

To configure the kurl.jar one must create a YAML configuration file (with a .yml extension) that defines a connection to the AR Server.  For simplicity, the YAML file is generally located in the same directory as the kurl.jar.  The contents of the YAML file should be in the format shown here:

kurl:
  username: myusername
  password: mypassword
  server: myremedyserver
  port: 0

Running the command below will prompt the user for the required configuration values and automatically generate a YAML configuration file named config.yml in the current working directory.

java -jar kurl.jar -setup

Testing Configuration

To test the configuration run the command below.

java -jar kurl.jar -config=config.yml -action=list_catalogs

If the configuration is valid this command will print a complete list of catalogs for the Kinetic Request instance.

Troubleshooting Configuration

Below are some common errors (not all of the possible errors) that may result from the command above and descriptions of their causes.

MessageNum: 623
MessageText: Authentication failed
AppendedText:

The error above occurs if the configuration file contains invalid values for username and/or password.

MessageNum: 90
MessageText: Cannot open catalog; Message number = 90
AppendedText: myremedyserver : RPC: Name to address translation failed - No such hostname

The error above occurs if the configuration files contains an invalid value for server.

MessageNum: 90
MessageText: Cannot open catalog; Message number = 90
AppendedText: myremedyserver : RPC: Miscellaneous tli error - System error (Socket error - 10060)