Comtech EF Data Vipersat Circuit Scheduler v3.7.x ArrangeLink - Manual (Page 16)

Product Description
1-6 ArrangeLink User Guide
ArrangeLink and VMS
ArrangeLink shares functionality with the VMS to create a seamless operating
environment to control and manage a satellite communications system. This
combination provides the system operator and user with system management
and operation controls for all aspects of satellite communication system opera-
tion.
Using the real-time system configuration information from the VMS, the sched-
uler is able to display current network operating conditions and resource avail-
ability. At the time a scheduled event starts, any of the equipment required to
establish the new circuit that are currently in STDMA mode will be automati-
cally switched to SCPC mode, and remain in this mode for the duration of the
event. At the conclusion of the event, the modem units that were used during the
scheduled event are automatically switched back to their home states and once
again become available resources under VMS management.
ArrangeLink works with either the VMS installed on a single stand-alone
server, or with the VMS installed in the optional N:1 server redundancy config-
uration.
New in this Release (v3.7.2)
VMS Web Services Client
This version of Vipersat Circuit Scheduler is now fully integrated into the VMS
code base. The VMS Web Services SOAP (Simple Object Access Protocol)
Server offering provides an interface for VMS client applications such as
ArrangeLink for communications with the VMS. The SOAP interface runs on a
web services proxy server that also hosts the web applications using Internet
Information Services (IIS). The user interface for these applications is accessed
using a web browser from a client PC workstation.
For more information on VMS Web Services, including the SOAP Server
installation procedure, refer to the VMS User Guide (Part Number MN/22156).
Event Priority
In previous versions of the Circuit Scheduler, an event created in the scheduler
would always supercede any ongoing event that was in contention with the
scheduled event. This is no longer the case. A priority attribute is now assigned
to the scheduled event, and contention will be resolved by granting precedence
to the event which has the higher priority.