This page was last edited on December 19, 2017, at 11:02.
Comments or questions about this documentation? Contact us for support!
You must perform the following configuration steps to enable the Orchestration Server (ORS) to work with your Genesys Mobile Services installation.
Start
End
Included with your installation are special configuration files, called DFM, which are required for Orchestration Server-based services. These files define Genesys Mobile Services-specific SCXML constructs that are required for the execution of SCXML applications used within Orchestration Server-based Services. For the Orchestration Server-based Services to function correctly, the following DFM files need to be configured in your Orchestration Server Application object:
The latest DFM definition files are included with the GMS installation and are available for download through the Service Management User Interface.
These files are default configuration files which need to be edited before being deployed. See Configuring DFMs. Details about deploying these DFM files in your environment are provided below.
After deploying these DFM files, you can use either an actual device with the demo application or an HTTP client (such as RestClient) to send API requests to Orchestration Server-based services. Refer to the Genesys Mobile Services API Reference for syntax of the requests.
Start
End
Service | Option Name | Option Value |
---|---|---|
Storage | gsgStorage | file://c:\dfms\storage.jsp |
Notification | gsgNotification | file://c:\dfms\notification.jsp |
Genesys Mobile-Based Services | gsgBasedServices | file://c:\dfms\basedservices.jsp |
Callback | gsgCallback | file://c:\dfms\callback.jsp |
Statistics | gsgStatistics | file://c:\dfms\statistic.jsp |
See the Orchestration Server Deployment Guide to perform the following additional configuration steps.