Section I – SCXML > Introduction > Overview         Bottom of Page
Genesys 8.1
SCXML Technical Reference
            

Overview

SCXML application processing is actually comprised of several parts (that is, more than just SCXML), as shown in Figure 1. Some parts are delivered as part of the orchestration platform and are utilized by the developer when creating the orchestration application (salmon color), while other parts are created by the developer (grey color) for their specific orchestration application and this is then deployed on the orchestration platform. The following describes the details associated with each part.

Orchestration Platform Overview

The orchestration platform components are really the framework for building an orchestration application and controlling it during run time.

SCXML Engine

This is the component of the orchestration platform that manages the execution of the orchestration applications. This component manages the application through an SCXML session and its object model, which represents an instance of the application. This object is called a session. It contains all of the data and objects needed for the orchestration application and its logic. The following is the set of objects and data maintained with each session:

The SCXML engine also has an ECMAScript engine imbedded. This provides the orchestration application with a data model and a way to provide low-level scripting functionality for the orchestration application.

This engine provides an interface that gives orchestration applications access to the functional modules and their functions.

Orchestration Application

An orchestration application is broken down into parts so as to create the appropriate separation between the part of the application that does the orchestration-related logic and the part that does the business-specific logic. This separation provides the developer with greater access to other business systems and functionality without having to change the orchestration logic itself. The orchestration-related logic is executed on the orchestration platform and the business-specific logic is executed on the application server, as shown in Figure 2. As a result, the following are the parts of an orchestration application that need to be created by a developer using the Composer IDE or by hand using other IDE tools.

Orchestration Application

Functional Module Framework

The orchestration platform must be the integration hub for orchestration-related services from media channels (new or supplied) to back end services (recommendation systems, marketing systems, optimization systems (WFO, pacing, business policies, and so on)). This part of the orchestration platform is the functional module framework. This framework provides a common integration model and framework which will allow a developer to create a functional module for any media channel or back end service so that it can be used directly in orchestration logic.

A functional module for a given functional domain has the following types of interfaces, which will be available to orchestration logic through the functional module:

For details on functional module functionality and interfaces see the Functional Modules section.

A functional module will interface with platform components using the functional module framework and the platform component interfaces. The following interfaces that will be available to a functional module:

Figure 3 shows the relationships between the different parts:

Functional Module Framework

Platform Service

The following services can be used by the other platform components (for example, functional modules, SCXML engine, and so on) to help manage their functionality:

Orchestration External Interface

This interface is provided by the orchestration platform and is used to control and monitor the execution of orchestration logic by external systems. It has two different forms:

The interface has two parts.




Section I – SCXML > Introduction > Overview         Top of Page
Genesys 8.1
SCXML Technical Reference