Red Hat Jboss Middleware Software Subscriptions Sample Clauses

The 'Red Hat JBoss Middleware Software Subscriptions' clause defines the terms under which customers may access, use, and receive support for Red Hat's JBoss Middleware products through a subscription model. This typically includes provisions regarding the scope of licensed use, the duration of the subscription, and the services provided, such as software updates and technical support. For example, it may specify which products are covered, the number of permitted users or instances, and the process for renewing or terminating the subscription. The core function of this clause is to clearly outline the rights and obligations of both the customer and Red Hat regarding the use and support of JBoss Middleware, thereby ensuring both parties understand the extent of their entitlements and responsibilities under the subscription.
Red Hat Jboss Middleware Software Subscriptions. 1.1 Red Hat JBoss Middleware Software Subscription Overview. When you purchase a Software Subscription to Red Hat JBoss Middleware (such as Red Hat JBoss Enterprise Application Platform), you will receive:
Red Hat Jboss Middleware Software Subscriptions 

Related to Red Hat Jboss Middleware Software Subscriptions

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the County Information Security Office.

  • Software Updates ▇▇▇▇▇ agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by ▇▇▇▇▇ governance. This timeline will be communicated by NWRDC to the Districts.

  • Software Support During the Term, Seller shall use commercially reasonable efforts to provide all Software updates and qualified Software upgrades in accordance with the terms of the Service Contract as such materials become commercially available for distribution. Purchaser’s use of all Software, updates, and upgrades of Software shall be subject to this Agreement, the Original Terms, and the applicable ▇▇▇▇.

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.