Jump to: navigation, search

Installing and Configuring Interaction SDK Components

This chapter describes how to configure and install the Agent Interaction (Java API), Multimedia Interaction (Java API), and Queued Interaction (Java API) components in your Genesys environment, so that you can develop custom applications.

Important
Open Media services have been extended to support ad-hoc management. The extensions include methods enabling a supervisor to perform queue content modifications—such as retrieving information after monitoring the queue, and routing interactions from Interaction Server to agents.

template names should be changed

Configuration and Installation

Preparing to Configure your Interaction SDK Component

Purpose
To choose your configuration environment and verify that you have the required application templates before you configure your Interaction SDK component to work in your Genesys environment.
Start

  1. Choose your configuration environment. Depending on which of the Interaction SDKs that you choose to install, your component might have configuration environment alternatives. For details about making this choice, refer to the Agent Interaction SDK 7.6 Java Developer’s Guide. You can choose between the alternatives below.
    • AIL:
      • Stand-Alone (Interaction SDK client)
      • N-Tier (Interaction SDK server)
    • MIL: Stand-Alone
    • QIL: Stand-Alone
  2. Verify the template. Before creating an application, check to see that an application template exists. The template provides most of the application’s configuration options and default values.
    1. In Configuration Manager, open the Environment folder, and then open the Application Templates folder.
    2. Select the template for your Interaction SDK component:
      • AIL:
        Agent_Interaction_client_766.apd
        Agent_Interaction_server_766.apd
      • MIL:
        Media_Interaction_SDK_server_766.apd
      • QIL:
        Queued_Interaction_server_766.apd


    End
    Next Steps

Importing an Application Template into Configuration Manager

Purpose
To import the required application templates before you configure your Interaction SDK component to work in your Genesys environment.
Prerequisites


Start

  1. Open the Environment folder and select the Application Templates folder.
  2. From the File menu, select Import Application Template.
  3. In the Open window that appears, import one of the following templates from your CD:
    • AIL:
      templates/Agent_Interaction_client_766.apd
      templates/Agent_Interaction_server_766.apd
    • MIL:
      templates/Media_Interaction_server_766.apd
    • QIL:
      templates/Queued_Interaction_server_766.apd
  4. Click Open. The corresponding Properties window opens.
  5. Click OK. The template is imported into the Application Templates folder.
  6. Verify that the host on which you will install the component’s server is declared in the Hosts folder.


End
Next Steps

Configuring your Interaction SDK for Deployment

Purpose
To configure your Interaction SDK component to work in your Genesys environment.
Prerequisites


Start

  1. In Configuration Manager, open the Environment folder and select the Applications folder.
  2. From the File menu, selectNew > Application. The Browse window opens, listing all application templates present in Configuration Manager.
  3. Choose the application template.
    • AIL:
      Agent_Interaction_server_766.apd
      Agent_Interaction_client_766.apd.
    • MIL:
      Media_Interaction_SDK_server_766.apd
    • QIL:
      Queued_Interaction_server_766.apd
  4. Click OK. The Properties window appears.
  5. Configure the various tabs in the Properties window. For information of how to configure these tabs, see The Properties Tab.


End
Next Steps

Launching System Installation

Purpose
To locate and launch the your Interaction SDK’s installation wizard.
Prerequisites

  1. Navigate to the component’s directory on the CD.
    • AIL: AgentInteraction\Java\windows\
    • MIL: MediaInteraction\Java\windows\
    • QIL: QueuedInteraction\Java\windows\
  2. Run Setup.exe. Note the installation’s default location.
    • AIL:
      Program Files\GCTI\Interaction SDK for Java 7.6.6\AIL\
    • MIL:
      Program Files\GCTI\Interaction SDK for Java 7.6.6\MIL\
    • QIL:
      Program Files\GCTI\Interaction SDK for Java 7.6.6\QIL\
  3. Follow the onscreen instructions and prompts to complete the installation.


End
Next Steps

UNIX Installation


Prerequisites

  • Check to make sure you have installation rights.


Start

  1. Navigate to the component’s directory on the CD.
    • AIL:
      AgentInteraction/Java/<os>/
  2. MIL:
    MediaInteraction/Java/<os>/

  3. QIL:
    QueuedInteraction/Java/<os>/

  4. Run the install.sh script.
  5. Follow the onscreen instructions and prompts to complete the installation.
  6. Important
    After running the Windows or UNIX executable or script, you should inspect the directory tree to make sure your installation is consistent with the installation you chose.


End
Next Steps

Installing your Interaction SDK Component

Purpose
To install your Interaction (Java API) 7.6 component:
Prerequisites


Start

  1. Launch the install script or executable corresponding to your host operating system.
  2. If an Open FileSecurity Warning message box appears, click its Run button to proceed with installation.
  3. Follow the prompts to choose:
    • documentation (javadoc) only
    • libraries (.jar files) only
    • both documentation and libraries
  4. Enter the destination locations. The following table lists the libraries added during system installation.
     
    Libraries Installed During System Installation

    Libraries

    Vendor

    Javamail

    java.sun.com

    Java Beans Activation Framework

    java.sun.com

    Log4j

    jakarta.apache.org

    Xerces_J, including:

    • Dom interface
    • SAX interface
    • Jaxp

    jakarta.apache.org


    • w3c.org
    • www.saxproject.org
    • java.sun.com


End
Next Steps

  • You can now use your Interaction SDK component to create custom built applications. For examples, see Custom Applications.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 30 January 2014, at 07:41.