Media Interaction SDK
Java Code Examples

Table of Contents

• Introduction
• Setup
  • Prerequisites
  • Configuration
• Running the Examples

Introduction

This code example consists of a stand-alone application that uses the Media Interaction Layer (MIL) to submit interactions.

The application parses a directory specified in the program arguments at startup. Each time the application finds a file smaller than 50MB, it creates an interaction, attaches the file, saves it in UCS (Universal Contact Server) and submits it to Interaction Server.

Setup

Prerequisites

You must install the following components and media:
• Genesys Configuration Server
• Genesys MCR Universal Contact Server
• Genesys MCR Interaction Server
  
• MIL .jars
  

Configuration

1. Expand the sdk_exmpl_ixn_java-media archive file containing the code samples.
   
2. Set the configuration properties in the OpenMediaSdk.properties file. You can define these properties in the Configuration Layer.
   
3. Set the location of your MIL .jar files in the compile.bat and compile.sh files. Replace the <path_to_MIL_Libraries> placeholder text with the appropriate path.
   
4. Compile the code examples, in the following order:
   • OpenMediaSdkData
   • SimpleConnector
   • SimpleCustomExtension
   • SimpleMediaServer
   • StartMedia
   • StartCustomMedia
   
   
5. In the go.bat and go.sh files, set the location of your MIL .jar files. Replace the <path_to_MIL_Libraries> placeholder text with the appropriate path.
   
6. Set the arguments for StartMedia in the go.bat and go.sh files. Or, to start the server in custom mode, set the arguments for StartCustomMedia in the goCustom.bat and goCustom.sh files. Replace the <your_argument_list> placeholder text with the following information:
   
   
   • arg0  the name of the queue to which media interactions are submitted.
   • arg1  the media type; possible values are defined in the Configuration Layer as "Media Type" attribute values.
   • arg2  interaction_type; possible values are defined in the Configuration Layer as "Interaction Type" attribute values.
   • arg3  interaction_subtype; possible values are defined in the Configuration Layer as "Interaction Subtype" attribute values.
   • arg4  the source directory containing files to attach to the new interactions.
   • arg5  the directory to use for saving the files in case the simple media server fails to manage Open Media interactions.
   
   For instance, consider the following arguments:
   
   RoutingWorkItem WorkItem Inbound InboundNew ./source ./save
   
   With these arguments, the new interactions will be WorkItem interactions of type Inbound, with a subtype of InboundNew.
   These interactions will be submitted to the RoutingWorkItem queue.
   Warning: These attached data for these interactions will be obtained from the ./source directory and then deleted from that directory. In case an error occurs during the processing of a file, that file is saved in the ./save directory.
   
   
7. Make sure there is a source directory corresponding to arg4.
8. If you want to launch the simple media server in custom mode, you must define an ESP (External Service Property) strategy in the Interaction Routing Designer and create an External Service. In the External Service Property text box, specify the custom extension media.sdk.java.examples.SimpleCustomExtension and the method to call doProcessRequest.

Running the Examples

• go to launch the simple media server.
• goCustom to launch the simple media server in custom mode.