External Integration Interfaces Sample Clauses

External Integration Interfaces. Publish/Subscribe Interface Provided by: Architecture The Publish/Subscribe interface gives modules within the system the ability to register their interest in receiving notifications describing system state changes. The behaviour of a publishing registration request is as follows:  The module interested to dispatch events will send a tuple [TypeId, Version]  A validation of the request is performed  If the request is valid, the platform will register the endpoint and will send a unique token id to as a response  From this moment on, the module is allowed to publish events to the platform The behaviour of a subscription registration request is as follows:  A module will contact the P/S Interface endpoint sending one or more tuples: [TypeId, version]  A validation of the request is performed  If all the issued tuples [TypeId, version] are available and the request is valid, the SubscriptionService will acknowledge the subscriptions;  If one of the issued tuples [TypeId, version] is not available, then the request is not valid, and the SubscriptionService will respond with an error. Please note: from the publishing module point of view, there is only a single endpoint where to send events. If a module that is attempting to publish data is not registered or has a token that is no longer valid, any event it issues will be automatically discard- ed by the communication middleware. Figure 4 Register as Publisher - Activity diagram Figure 5 Register as Subscriber - Activity diagram RegisterAsSubscriber informs the platform that a module wants to be registered as a subscriber for a given event id and version number. The platform stores the data about the subscriber and creates a new entry in the communication bus for the mod- ule. The RegisterAsPublisher message informs the platform that a module needs to pub- lish events to the system. Upon receipt of the message, the platform creates a logical link and a broadcast message queue for the new event stream (if not already pre- sent). It is important to note that multiple systems from the same logical module can register as event publishers. In that case, the platform will not guarantee causal or- xxxxxx on those messages.
Sample 1
AutoNDA by SimpleDocs

Related to External Integration Interfaces

  • Regional integration 1. The Parties recognise that regional integration is an integral element of their partnership and a powerful instrument to achieve the objectives of this Agreement.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Full Integration This Agreement, including the attached Order, is the final written expression and the complete and exclusive statement of all the agreements, conditions, promises, representations, and covenants between the parties with respect to the subject matter hereof, and supercedes all prior or contemporaneous agreements, negotiations, representations, understandings, and discussions between and among the parties, their respective representatives, and any other person or entity, with respect to the subject matter covered hereby.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS 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 DHCS Information Security Office.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Integration The Company shall not sell, offer for sale or solicit offers to buy or otherwise negotiate in respect of any security (as defined in Section 2 of the Securities Act) that would be integrated with the offer or sale of the Securities in a manner that would require the registration under the Securities Act of the sale of the Securities or that would be integrated with the offer or sale of the Securities for purposes of the rules and regulations of any Trading Market such that it would require shareholder approval prior to the closing of such other transaction unless shareholder approval is obtained before the closing of such subsequent transaction.

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