RedundancyMaster
8Pages

teKac (pG ji j i RedundancyMaster RedundancyMaster: $1295.00 RedundancyMaster increases the reliability and availability of OPC data by allowing multiple OPC Servers to be configured into redundant pairs assuring your data is always available. RedundancyMaster can be seamlessly integrated into any existing OPC application with no changes to your client and without loss of data. It transparently maps these redundant servers to appear as a single OPC Server connection to your OPC Client. The ability to "drop" RedundancyMaster into an existing application without reconfiguring the client application is a key design and development feature. RedundancyMaster Client Interfaces: Application Connectivity Support: OPC Data Access: 1.0a, 2.0, 2.05a industria! Strength Reliability: Support: 1 (207) 775-1660 1-888-Kepware extension 211 support@kepware.com Sales: 1 (207) 775-1660 1-888-Kepware extension 208 sales@kepware.com OPC Data Access (OPC DA) technology has proven to be reliable in virtually every possible situation requiring consistent data access to devices and systems. However, there are other factors that can jeopardize the integrity of a system, some being software, hardware, and even the human element. By using RedundancyMaster technology you can make these systems more reliable and efficient. increase ROi & Reduce System Down-time: RedundancyMaster resides on your OPC client machine and facilitates connections to a Primary and Secondary OPC server. If for any reason the OPC client loses its communications link with the primary OPC server or a user-specified condition is met (e.g. An item is not receiving updates, a specific item value is met, or the quality of an item set to bad) RedundancyMaster will drop the primary and promote the secondary OPC server on your network - reducing system down-time and saving you money. How It Works: RedundancyMaster works with a majority of OPC servers on the market, in addition to KEPServerEX. OPC Servers typically are out-of-process servers, better known as EXEs, and run in their own memory space. OPC servers can also be an in-process server, better known as a DLL. RedundancyMaster is an OPC Server, and can run as an In-Proc server, acting as a Proxy to a Redundant Pair of other OPC Servers. RedundancyMaster takes advantage that the majority of OPC clients do not explicitly specify whether they want to connect to a DLL or EXE version. In this case, the operating system will always prefer the DLL option since the performance between the client and server will be optimal. RedundancyMaster will hook to the client calls and operate in the Client Memory Space for maximum performance, and provides redundancy without client or server configuration changes. epware M TECHNOLOGIES Kepware Technologies | 400 Congress Street 3rd Floor | Portland, Maine 04101 | 207.775.1660 | FAX Copyright © 2009 Kepware Technologies, Inc. All rights reserved. 99

RedundancyMaster is a drop-in application that does not require any changes being made to the OPC client or server applications. The intuitive configuration takes only minutes and allows you to have a Redundant OPC system running with increased reliability and with no degradation in performance. Simply browse and select your primary and secondary OPC servers, and the system is up and running. RedundancyMaster has built in features such as email notification, object and link monitoring, and diagnostics logging. In a situation where you need multiple redundant OPC server pairs that utilize...

Connection Mode: The connection mode defines how and when the redundancy application should connect to the underlying primary and secondary servers. The mode in which you operate affects the amount of time it takes to fail over from one OPC server to the other. Some modes allow you to automatically promote communications to the primary when it is available. The following summarizes connection modes: Cold (Active machine only): In this mode, the application will only connect to one underlying server at a time. On startup, a connection to the primary server will be made and all client related...

Hot (Both machines, subscribe to items on both machines): In this mode, the application will attempt to maintain a connection to both the primary and secondary servers at all times. On startup, the application will initialize data callbacks for both primary and secondary servers so that both servers will send data change notifications. The data received from the primary server will be forwarded onto the client. In the event that the connection to the primary fails, or communications to the primary is lost, data received for the secondary will immediately be forwarded onto the client. In...

y 11 i r tuvaj You can specify either the host name or IP address of the preferred machine capable of sending email by utilizing the Simple Mail Transport Protocol. When an initial email notification is to be sent, the application will first attempt to send the notification through the primary machine. In the event that the connection to the primary SMTP Mail Server fails, an attempt to send the email notification through the secondary SMTP Mail Server will be attempted (if configured). Note: If the same email notification fails to be sent through the primary and secondary, the email will...

Usage Diagrams: Two OPC Servers Paired with RedundancyMaster The original OPC system has been redesigned using two OPC servers instead of a single OPC server. Each OPC client has been paired with RedundancyMaster to facilitate the redundant operation of the OPC servers. RedundancyMaster will keep both servers active or if configured to do so, start the secondary server only when the primary server fails. The use of either the Primary or Secondary OPC server can be controlled directly by using the configurable options within RedundancyMaster. RedundancyMaster can be configured to monitor...

Usage Diagrams Continue!: Local Machine Redundancy This scnario has the OPC Client, RedundancyMaster, and the Secondary OPC Server residing on the Local Machine with the Primary OPC Server on a Remote Machine. In this scenario be sure to make the most reliable Server your Secondary OPC Server. This scenario also reduces the need for another machine to run the Secondary OPC Server Kepware Technologies | 400 Congress Street 3rd Floor | Portland, Maine 04101 | 207.775.1660 | FAX: 207.775.1799 Copyright © 2009 Kepware Technologies, Inc. All rights reserved.