Queued Interaction Java API Code Examples
Any authorized distribution of any copy of this code (including any related documentation) must reproduce the following restrictions, disclaimer and copyright notice:
The Genesys name, trademarks and/or logo(s) of Genesys shall not be used to name (even as a part of another name), endorse and/or promote products derived from this code without prior written permission from Genesys Telecommunications Laboratories, Inc.
The use, copy, and/or distribution of this code is subject to the terms of the Genesys Developer License Agreement. This code shall not be used, copied, and/or distributed under any other license agreement.
THIS CODE IS PROVIDED BY GENESYS TELECOMMUNICATIONS LABORATORIES, INC. (“GENESYS”) “AS IS” WITHOUT ANY WARRANTY OF ANY KIND. GENESYS HEREBY DISCLAIMS ALL EXPRESS, IMPLIED, OR STATUTORY CONDITIONS, REPRESENTATIONS AND WARRANTIES WITH RESPECT TO THIS CODE (OR ANY PART THEREOF), INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. GENESYS AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY DAMAGE SUFFERED AS A RESULT OF USING THIS CODE. IN NO EVENT SHALL GENESYS AND ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, ECONOMIC, INCIDENTAL, OR SPECIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, ANY LOST REVENUES OR PROFITS).
Copyright © 2006 Genesys Telecommunications Laboratories, Inc. All rights reserved.
Table of Contents
This code example consists of a GUI application, written in Java, that
demonstrates various features of the Queued Interaction Java APIsuch as
connecting servers, monitoring connections, and monitoring queues.
All of these actions are automatically updated using events from the Queued
Interaction Java API.
Setup
- Genesys Configuration Server
- Genesys MCR Interaction Server
- Open Media Interaction Application Blocks for Java
- Queued Interaction
.jar
files
- Expand the
75sdk_exmpl_ixn_java-queued
archive file containing
the code examples.
- Set the properties of the
OpenMediaSdk.properties
file.
- In the
compile
files,
go
files and goAlarm
files:
- Set the location of your QIL
.jar
files. Replace the
<path_to_QIL_Libraries>
placeholder text with the appropriate path.
- Set the location of your compiled application blocks, by replacing the
<path_to_application_blocks_class_files>
placeholder text with the appropriate path.
- In the
goAlarm.bat
and goAlarm.sh
files, set the arguments for SimpleQueueAlarm
.
Replace the <your_argument_list>
placeholder text with the following information:
arg0
the name of the queue to be monitored.
arg1
the maximum number of interactions allowed in the queue.
For instance, consider the following arguments: RoutingQueueEmail 5
With these arguments, SimpleQueueAlarm
monitors the queue RoutingQueueEmail
and, when there are 6 or more interactions in this queue,
it sends an alarm.
- Compile the code examples, in the following order:
- OpenMediaSdkTableModel
- OpenMediaSdkGui
- AlarmGui
- OpenMediaSdkData
- SimpleConnector
- SimpleService
- SimpleMonitorQueue
- SimpleMonitorInteraction
- SimpleSupervisor
- SimpleQueueAlarm
- MultipleAlarm
To run the examples, type:
go SimpleService
to launch the GUI example that displays the state of the services.
go SimpleMonitorQueue
to launch the GUI example that displays queues
and that lets you start or stop monitoring active queues.
go MultipleAlarm
to launch the GUI example that displays queues and alarms.
goAlarm
to launch a stand-alone application that sends an alarm
if there are more interactions than are allowed in a queue.
go MultipleAlarm
to launch the GUI example that displays queues and alarms.