Standby Server License Option for AppServer and VisiBroker Sample Clauses

Standby Server License Option for AppServer and VisiBroker. Licensee may install the Licensed Software on a single standby server and use the Licensed Software in object code form solely in a standby, non-production mode for use in the event the primary server fails (“Standby Server License”). Licensee may not use the Licensed Software on a production basis under a Standby Server License except during periods when one or more copies of the Licensed Software for which Licensee has purchased a Deployment License are nonfunctional, and, in such event, only in accordance with the terms of the Deployment License.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs

Related to Standby Server License Option for AppServer and VisiBroker

  • Server License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license to internally use and install the Software on the number of Server(s) listed in the Order Form for Commercial purposes. Unless stated otherwise in the Order Form, for the purposes of this license grant, you may install the Software on one (1) Machine as a substitute for, and not in addition to, one (1) Server. The total count of Server(s) where the Software is installed must not exceed the number of licenses purchased on the applicable Order Form(s).

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!