Supplemental JBoss Software Conditions Sample Clauses

Supplemental JBoss Software Conditions. Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Sample 1Sample 2Sample 3See All (53)
AutoNDA by SimpleDocs
Supplemental JBoss Software Conditions. Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software.
Sample 1Sample 2Sample 3See All (52)
Supplemental JBoss Software Conditions. Software Access 1.2 ¶omouhnteuah e ycuobnr Дur NO JBoss. and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss OpenShift Container Platform Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss OpenShift Container Platform CompobomДehne n qoctym k qomouhnteuahomy NO JBoss mpeДhasha¬eh n mpeДuafadtcr touako Дur ⎝euen paspa6otkn Дur he 6ouee ¬em 25 mouasobateuen Дur kamДon NoДmnckn 16 Core Band Дur mpno6petehhofo bamn NO Red Hat JBoss. Ecun b samyckaete nun ncmouasyete qomouhnteuahoe NO JBoss Дur ⎝euen mponsboДctba nun Дur 6ouee ¬em 25 mouasobateuen, b cofuamaeteca mpno6pectn cootbetctbydyne NoДmnckn ha NO Дur kamДon ncmouasyemon nun pasbept baemon bamn EДnhny . Npofpamma fapahtnn ka¬ectba pemehnn c otkp t m ncxoДh m koДom Red Hat Дenctbyet touako Дur mpno6petehh x bamn NoДmncok ha NO Red Hat JBoss Middleware (hampnmep, Red Hat JBoss Enterprise Application Platform b mpnbeДehhom b me mpnmepe) n he Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription. Дenctbyet Дur qomouhnteuahofo NO JBoss. NoДmnckn ha JBoss OpenShift Container Platform (cofuacho ompeДeuehnd, mpnbeДehhomy hnme) he c¬ntadtcr qomouhnteuah m NO JBoss. KamДar yctahobka n mpnmehehne NoДmncok ha NO JBoss OpenShift Container Platform un6o Дur ⎝euen paspa6otkn, un6o Дur ⎝euen mponsboДctba c¬ntaetcr EДnhnyen n tpe6yet omua¬ehhon NoДmnckn ha NO.
Sample 1
Supplemental JBoss Software Conditions. Software Access and Software Maintenance for Supplemental JBoss Software are intended and available for Development Purposes only and for up to twenty-five (25) users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than twenty-five (25) users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss OpenShift Container Platform Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss OpenShift Container Platform
Sample 1

Related to Supplemental JBoss Software Conditions

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA):

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Contractor hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace. The Contractor will give written notice to the State within ten (10) days after receiving actual notice that the Contractor, or an employee of the Contractor in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of contract payments, termination of this Contract and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in this Contract is in excess of $25,000.00, the Contractor certifies and agrees that it will provide a drug-free workplace by:

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

Time is Money Join Law Insider Premium to draft better contracts faster.