Red Hat JBoss Middleware Use Cases Clause Samples

The 'Red Hat JBoss Middleware Use Cases' clause defines the permitted ways in which Red Hat JBoss Middleware software can be used under the agreement. It typically outlines specific business scenarios, application types, or deployment models where the software is authorized, such as development, testing, or production environments. By clearly specifying these use cases, the clause helps ensure that customers use the software within agreed boundaries, thereby preventing unauthorized or unintended uses and reducing the risk of license violations.
Red Hat JBoss Middleware Use Cases. Subscription Services are provided for Red Hat JBoss Middleware Software Subscriptions only when used for its supported purpose (“Use Case”) as set forth at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/support/offerings/jboss/. If Red Hat determines that any of the JBoss Middleware Software Subscription Services or Software is being used to support software obtained from community sites without purchasing a corresponding Software Subscription for such community software, Red Hat may, without limiting its other rights or remedies, immediately suspend performance and/or terminate the Agreement.
View SourceView Similar (65)
Red Hat JBoss Middleware Use Cases. Subscription Services are provided for Red Hat JBoss Middleware Software Subscriptions only when used for its supported purpose (“Use Case”) as set forth at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/support/offerings/jboss/. If Red
View SourceView Similar (20)
Red Hat JBoss Middleware Use Cases. Subscription Services are provided for Red Hat JBoss Middleware Software Subscriptions only when used for its supported purpose (“Use Case”) as set forth at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇▇/. If Red Hat determines that any of the JBoss Middleware Software Subscription Services or Software provided hereunder is being used to support software obtained from community sites without purchasing a corresponding Software Subscription for such community software, Red Hat may, without limiting its other rights or remedies, immediately suspend performance and/or terminate the Agreement. 1. Red Hat JBoss Middleware 소프트웨어 서브스크립션 1.1 Red Hat JBoss Middleware 소프트웨어 서브스크립션 개요. (Red Hat JBoss Enterprise Application Platform 등) Red Hat JBoss Middleware에 대한 소프트웨어 서브스크립션을 구매하는 경우 다음 사항을 제공받는다.  (위의 예에서 Red Hat JBoss Enterprise Application Platform 등) 구매한 Red Hat JBoss Middleware 소프트웨어 서브스크립션에 대한 소프트웨어 접속 및 아래의 섹션 1.2에서 설명한 Supplemental JBoss 소프트웨어 조건이 적용되는 특정한 기타 Red Hat JBoss Middleware 소프트웨어 코드(본 기타 코드를 “Supplemental JBoss Software”로 지칭)로의 접속  Supplemental JBoss Software를 제외하고 구매한 Red Hat JBoss Middleware 소프트웨어 서브스크립션에 대한 생산 및 개발 지원(위의 예에서 Red Hat JBoss Enterprise Application Platform)  구매한 Red Hat JBoss Middleware 소프트웨어 서브스크립션 제품과 아래의 Supplemental JBoss 소프트웨어 조건이 적용되는 Supplemental JBoss Software에 대한 소프트웨어 유지보수 1.2 Supplemental JBoss 소프트웨어 조건. Supplemental JBoss Software에 대한 소프트웨어 접속 및 소프트웨어 유지보수는 개발용으로만 의도되어 사용 가능하며 구매한 Red Hat JBoss Middleware 소프트웨어의 각 16코어 밴드 서브스크립션에 대한 최대 25명의 사용자를 위한 것이다. 생산용으로 또는 25명이 넘는 사용자에 대하여 Supplemental JBoss Software를 배치하거나 사용하는 경우 배치하거나 사용하는 각 단위에 대하여 적절한 소프트웨어 서브스크립션을 구매하는 데 동의하는 것이다. Red Hat의 오픈 소스 보장 프로그램은 (위의 예에서 Red Hat JBoss Enterprise Application Platform 등) 고객이 구매한 Red Hat JBoss Middleware 소프트웨어 서브스크립션에 적용되며 Supplemental JBoss Software에는 적용되지 않습니다. 1.3 Red Hat JBoss Middleware 사용 사례. 서브스크립션 서비스는 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇▇/에 명시한 대로 지원용(“사용 사례”).으로 사용되는 경우에만 Red Hat JBoss Middleware 소프트웨어 서브스크립션에 대해 제공된다 Red Hat은 이와 같이 제공된 JBoss Middleware 소프트웨어 서브스크립션 서비스 또는 소프트웨어가 커뮤니티 사이트에서 획득한 소프트웨어를 지원하는 용도로 사용되며 이러한 사용이 해당 커뮤니티 소프트웨어의 소프트웨어 서브스크립션의 구매 없이 이루어진다고 판단한 경우, 다른 권리 또는 구제의 제한 없이 즉시 성능을 중단하거나 해당 협정을 종료할 수 있다. EXHIBIT 1.C DEVELOPER SUBSCRIPTIONS 증거문서 1.C
View SourceView Similar (5)
Red Hat JBoss Middleware Use Cases. Subscription Services are provided for Red Hat JBoss Middleware Software Subscriptions only when used for its supported purpose (“Use Case”) as set forth at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/support/offerings/jboss. 1. Red Hat JBoss Middleware 软 件 订 阅 1.1 Red Hat JBoss Middleware 软件订阅概述。在购买 Red Hat JBoss Middleware 的软件订阅（如 Red Hat JBoss Enterprise Application Platform）时，贵方将收到：  贵方所购买的 Red Hat JBoss Middleware 软件订阅（例如 Red Hat JBoss Enterprise Application Platform）的软件访问途径，以及对某些额外的 Red Hat JBoss Middleware 软件代码的访问（我们将这种额外的代码称为 “JBoss 补充软件”），具体取决于下面第 1.2 节规定的 JBoss 补充软件的条件；  贵方所购买的 Red Hat JBoss Middleware 软件订阅产品 （例如 Red Hat JBoss Enterprise Application Platform）的生产支持和开发支持，但不涉及 JBoss 补充软件；以及  贵方所购买的 Red Hat JBoss Middleware 软件订阅产品及 JBoss 补充软件的软件维护，具体取决于下文规定的 JBoss 补充软件条件。 1.2 JBoss 补充软件条件。JBoss 补充软件的软件访问途径和软件维护仅用于开发用途，并且适用于最多 25 名用户，针对的是贵方所购买的每个 Red Hat JBoss Middleware 软件 16 核心组订阅。如果贵方出于生产目的部署或使用 JBoss 补充软件，或将其用于超过 25 名用户，则表示贵方同意为所部署或使用的每个单位购买适当的软件订阅。红帽的开源代码保证计划仅适用于贵方购买的 Red Hat JBoss Middleware 软件订阅 （例如 Red Hat JBoss Enterprise Application Platform），而不适用于 JBoss 补充软件。 1.3 Red Hat JBoss Enterprise Middleware 使 用 案 例 。
View Source
Red Hat JBoss Middleware Use Cases. Subsciption Services 1.3 Bapnaht ncmouasobahnr Red Hat JBoss Middleware. are provided for Red Hat JBoss Middleware Software Subscriptions only when used for its supported purpose (“Use Case”) as set forth at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/support/offerings/jboss/. If Red Hat determines that any of the JBoss Middleware Software Subscription Services or Software is being used to support software obtained from community sites without purchasing a corresponding Software Subscription for such community software, Red Hat may, without limiting its other rights or remedies, immediately suspend performance and/or terminate the Agreement. Ycuyfn mo moДmncke mpeДoctaburdtcr Дur NO Red Hat JBoss Middleware touako mpn ncmouasobahnn mo hasha¬ehnd («Bapnaht ncmouasobahnr») cofuacho omncahnd mo aДpecy: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/support/offerings/jboss/. Ecun Red Hat yctahobnt, ¬to Ycuyfn mo NoДmncke ha NO JBoss Middleware nun NO ncmouasydtcr Дur moДДepmkn mpofpammhofo o6ecme¬ehnr, mouy¬ehhofo c hekommep¬ecknx cantob 6es mpno6petehnr cootbetctbydyen NoДmnckn ha NO Дur takofo hekommep¬eckofo mpofpammhofo o6ecme¬ehnr, Red Hat momet 6es ofpahn¬ehnr Дpyfnx cbonx mpab n cpeДctb saynt hemeДuehho mpnoctahobnta ncmouhehne Cofuamehnr n/nun pactopfhyta efo.
View Source

Related to Red Hat JBoss Middleware Use Cases

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • 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.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • 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.