Prophecy 10.0 Development Guide Home  |  Frameset Home

  How to: Delete a Group  |  TOC  |  How to: Create a New Virtual Platform  

Managing Virtual Platforms

Server services, such as ASR engines, browsers, and VoIP gateways can be grouped within a Community on a Virtual Platform used to identify Resources for your voice applications. Resources are logical Resources advertised by the Virtual Platform. Resources are based on a collection of one or more prioritized services in Groups from one or more servers. Virtual Platforms are comprised of the components described in the following table:

Concept Description
Server A physical computer configured to provide one or more services.
Service A single type Resource, such as an XML browser, ASR engine, or gateway, advertised on a Virtual Platform to voice applications, s.
Group A collection of one or more servers providing the same or different services as a Virtual Service, on a Virtual Platform as a Resource.
Resource A single, prioritized Virtual Service advertised to voice applications on a Virtual Platform, such as the en-US TTS Resource, or a Cisco gateway Resource.
Virtual Platform The complete set of available voice application Resources that are load balanced and configured for failover in one or more Groups advertised to voice applications.

To open the Virtual Platform List

  • On the Prophecy Commander toolbar, click the Servers module icon, and then click the Virtual Platform List page.

  • To understand the Virtual Platform, you need to understand how the components, both physical and virtual, are interrelated.

    Physical servers are configured to provide physical services. In the following illustration, the two servers provide five physical services: VXML, TTS - US English, ASR - US English, a second instance of TTS - US English on Server 2, and finally ASR - Spanish.

    Although all five physical services could be available as individual services to a voice application, to access the services directly, the voice application must request the service directly from the server, and must be aware of the address of each server. in Prophecy, by combining Server 1 and Server 2 into a Group, Prophecy can offer four Virtual Services where the two TTS - US English services are offered as a single virtual service from Group 1.

    Note: Identical physical services within a Group are automatically offered externally from the Group as load balanced Virtual Services.

    In the following illustration, Group 2 is added with two more physical services on Server 3. You can group the two Groups to provide failover capability for TTS - US English and ASR - Spanish services by assigning Priority 2 to the service provided by Group 2 when adding the service as a Resource oo the Virtual Platform. From both Groups, a single Virtual Service called TTS - US English is available.

    Next, you need to create a Resource with a name used by the voice application to access that Resource, for example, TTS-English, ASR-English, and ASR-Spanish. With a named Resource, you can now map the Resource to one or more Groups that offer that virtual services as shown in the Add Resource dialog in the following illustration.

    Resources are now available on the Virtual Platform where the voice application runs that are provided by the Virtual Services offered by the two Groups of physical servers. To the voice application, the TTS-English Resource is a single Resource. However, in this example, the TTS-English Resource is load balanced within Group 1 and has a failover in Group 2. Behind the scenes, this means that each request for the TTS-English Resource will be provided by Server 1 or Server 2 using load balancing. If neither Server 1 nor Server 2 is available, the service will be provided by Server 3 as the failover.

    Your Virtual Platform is a collection of prioritized services available as Resources on a Virtual Platform to your voice applications. For voice applications with different requirements, you can create multiple Virtual Platforms and configure the same servers in different Groups, Virtual Services, and Resources.

    The Process

    To create a Virtual Platform for a voice application, complete the following steps:
    1. Install and configure a service on a server.
    2. Add servers with the same service to one or more Groups.
    3. Create a named Resource and map one or more services in Groups, and then assign a Priority to each service added.

    Next Steps

    Before you can configure your Resources, you must have installed and configured your servers with a service, and then added the servers to Prophecy. For more information, see Managing Servers. After your servers are added to Prophecy, you must create and add them to Groups to offer to the Virtual Platform as Virtual Services. For more information, see Managing Groups. If you just need a single Virtual Platform, you can use the Default Virtual Platform, and begin adding Resources. For more information, see How to: Create a New Resource.

    You can view your Virtual Platform as a hierarchical tree and search the tree by using the Virtual Platform Tree. For more information, see Using the Virtual Platform Tree. The Virtual Platform Tree is useful to see all Resources available to a voice application operating on the Virtual Platform.

    See Also

        Prophecy Overview
        Prophecy Commander
        How to: Create a New Virtual Platform
        How to: Edit a Virtual Platform
        How to: Copy Virtual Platform Resources
        How to: Delete a Virtual Platform
        How to: Create a New Resource
        How to: Add or Remove a Group from a Resource
        How to: Edit a Resource
        How to: Load Balance Services
        How to: Setup Failover for Services
        Using the Virtual Platform Tree
        Voxeo Support

    0 posts - click the button below to add a note to this page

      How to: Delete a Group  |  TOC  |  How to: Create a New Virtual Platform  

    © 2012 Voxeo Corporation  |  Voxeo IVR  |  VoiceXML & CCXML IVR Developer Site