Jump to: navigation, search

AIL, MIL, and QIL Basics

This page provides an overview of the three application program interfaces (APIs) whose installation is covered individually in the chapters that follow: Agent Interaction (Java API) 7.6, Media Interaction (Java API) 7.6, and Queued Interaction (Java API) 7.6.

API Roles and Components

To plan your deployment of Interaction SDK Java, please start by ensuring that you have a supported operating system and Java environment. Refer to the Genesys Supported Operating Environment Reference Guide document. (For access details, see Related Resources.)

API Role

Agent Interaction (Java API), also known as AIL, lets you build Java applications to control and manage voice, multimedia, and Open Media interactions issued by, or intended for, a contact center agent.

Components

AIL is comprised of the following components:

  • The Agent Interaction (Java API) library, which is written entirely in the Java language and delivered as a set of .jar files.
  • A javadoc API reference, which is an HTML tree in the docs/ directory of the installed product directory tree.
  • A developer’s guide, which is delivered on the documentation CD.
  • A set of code examples that exercise some important features of the API, delivered in .zip and .tar.gz format on the documentation CD.

API Role

Media Interaction (Java API), also known as MIL, lets you build Java applications to manage Open Media interactions in the Genesys Framework. MIL 7.6 provides a simple Java API that includes manager interfaces for developing server applications that:

  • Create and manage Open Media interactions submitted to Interaction Server.
  • Manage Open Media interactions submitted to the Universal Contact Server’s database.
  • Use ESP protocol to handle interactions’ extensions through Interaction Server.
  • Monitor your application run mode from the Local Control Agent component point of view.

  • Important
    MIL does not support the Genesys Chat or E-mail media types.

MIL Components

MIL is comprised of the following components:

  • The Open Media common library, written entirely in the Java language and delivered as a set of .jar files on the product CD.
  • The Media Interaction (Java API) library, which is written entirely in the Java language and delivered as a set of .jar files on the product CD.
  • A javadoc API reference, which is an HTML tree in the docs/ directory of the installed product directory tree.
  • A developer’s guide, which is delivered on the documentation CD.
  • A set of code examples that exercise some important features of the API, delivered in .zip and .tar.gz format on the documentation CD.

API Role

Queued Interaction (Java API), also known as QIL, lets you build Java applications to control queues made available by the Genesys Framework. QIL 7.6 provides a simple Java API, including manager interfaces to develop applications that can be used:

  • To get business attributes and their values.
  • To monitor changes in the queues’ state, and in associated interactions.
  • To get events on interactions in the queues.
  • For Genesys media types, and for Open Media types.

QIL 7.6 offers the ability to perform the following ad-hoc management transactions:

  • stopProcessing
  • placeInQueue
  • lock/unlock
  • set/RemoveProperties
  • pull/leave

QIL 7.6 retrieves queue content from Interaction Server, in order to provide the status of queue content to QIL’s clients.

QIL Components

QIL is comprised of the following components:

  • The Queued Interaction (Java API) library, which is written entirely in the Java language and delivered as a set of .jar files on the product CD.
  • A javadoc API reference, which is an HTML tree in the docs/ directory of the installed product directory tree.
  • A developer’s guide, which is delivered on the documentation CD.
  • A set of code examples that exercise some important features of the API, delivered in .zip and .tar.gz format on the documentation CD.

Tasks and Their Related Procedures

The following table summarizes the tasks and their related procedures addressed in this guide.
 

Tasks and Related Procedures

Objective

Related Procedures and Actions

To set up your environment so that you can develop using your AIL Interaction SDK component.

Preparing to Configure your Interaction SDK Component
Configuring your Interaction SDK for Deployment
Configuring the Properties Tab
Configuring the Options Tab for AIL

To install your AIL Interaction SDK component for use in developing custom applications.

Launching System Installation
Installing your Interaction SDK Component

To set up your environment so that you can develop using your QIL Interaction SDK component.

Preparing to Configure your Interaction SDK Component
Configuring your Interaction SDK for Deployment
Configuring the Properties Tab
Configuring the Options Tab for QIL

To install your QIL Interaction SDK component for use in developing custom applications.

Launching System Installation
Installing your Interaction SDK Component

To set up your environment so that you can develop using your MIL Interaction SDK component.

Preparing to Configure your Interaction SDK Component
Configuring your Interaction SDK for Deployment
Configuring the Properties Tab
Configuring the Options Tab for MIL

To install your MIL Interaction SDK component for use in developing custom applications.

Launching System Installation
Installing your Interaction SDK Component

To allow your custom application to run in a Genesys environment.

Setting up VoIP Support
Setting up your SIP Communication Server
Configuring for your Specific Switch
Running MIL and QIL on the Same JVM
Starting MIL in Server Mode
Configuring External Service Protocol Request

 

This page was last modified on January 7, 2014, at 09:01.

Feedback

Comment on this article:

blog comments powered by Disqus