Grass Valley iControl Services Gateway - Manual (Page 6)

Page 6 of 26
I C ONTROL
™
G ATEWAY E NTITIES
To program an application that controls Services through an iControl™ Gateway, a programmer shall
understand the meaning of, and affect the following entities:
 iControl™ Directory Services
 iControl™ Services Gateway

Registered Services List

Service Node

Service Identifier

Service Access Key

Access Key Parameters List
1.1.1 I C ONTROL
™ D IRECTORY S ERVICES
A Miranda Service, when it starts up, register itself to a listening iControl™ Gateway through a portal
referred to as the iControl™ Directory Services.
A Miranda Service, by default, attempts to register itself to all li stening iControl™ Gateways. The Service
Registration process is handled by the iControl™ Gateway, and requires no interventions whatsoever
from any user or application.
An application shall, in order to identify and locate Miranda Services through an iCont rol™ Gateway,
query the iControl™ Directory Services for the list of the currently registered Services. An application will
use the information returned by the iControl™ Directory Services to identify, locate, assess, and control
the Miranda Services.
An a pplication will access the iControl™ Directory Services to query the list of Registered Services within
an iControl™ Gateway by establishing a TCP/IP-XML session through socket port 10001 of this
iControl™ Gateway‟ Host.
An application can request the iCo ntrol™ Directory Services to notify it of changes to the list of
Registered Services by establishing a TCP/IP-XML connection to socket port TBD of the iControl™
Gateway‟ Host.
An iControl™ Directory Services will notify to the listening applications through the TCP/IP-XML
connection of changes to the registered Services (Service expired, Service de-registered, Service
Status…); this will allow the listening application to query back the list of the currently registered Services
and update its internal base of information on these Services.