Escolar Documentos
Profissional Documentos
Cultura Documentos
• Configuration
• Runtime
• Administration
• Event Log
CONFIGURATION
Client/Server interface that is used to modify the runtime project. The Configutation
can be launched by multiple users and supports remote Runtime configuration.
This server supports the import and export of TAG DATA in a "Comma Separated
Variable (CSV)" File(archivo). When using CSV import and export, tags are created
quickly in the desired application.
RUNTIME
The Runtime is the Server Component that starts as a SERVICE by default. Client can
connect to the runtime remotely or locally
ADMINISTRATION
The Administration is used to VIEW and/or MODIFY Settings and Launch Applications
that pertain to user management and the server. By default, the Administration is
started and sent to the System Tray (bandeja del sistema) when a user account logs
onto the operating system.
PROJECT
The Project file contains the CHANNEL, DEVICE, AND TAG definitions as well as
preferences and other saved settings.
EVENT LOG
The Event Log SERVICE collects INFORMATION, WARNING, ERROR, and SECURITY
events. These events are sent to the Configuration's EVENT LOG window for viewing.
PROCESS MODES
The Runtime process mode can be changed while the server is running; however, doing
so while a client is connected interrupts the connection for a short period. The modes
of operation are:
• SYSTEM SERVICE
• INTERACTIVE
SYSTEM SERVICE
By default, the server is installed and runs as a service. When System Service is
selected, the Runtime does not requiere user intervention and starts when the
operating system opens. This provides USER INDEPENDENT ACCESS to the server by
the clients.
INTERACTIVE
When Interactive is selected, the Runtime REMAINS STOP UNTIL A CLIENT ATTEMPTS
CONNECT TO IT. Once started, it runs until ALL CLIENTS have disconnected and then
shuts down. The Runtime also SHUTS DOWN IF the user account logs off the operation
system.
Note: The Runtime process mode may be changed to meet client applications' needs
through the Administration settings dialogs.
OPC DA
Overview
“OPC” stand for Open Productivity and Connectivity in industrial automation and the
enterprise systems that support industry. It is a client/server technology where one
application acts as the server (providing data) and another acts as a client (using data).
OPC is composed of a series of standards specifications: OPC Data Access (DA) is the
most prolific standard. OPC DA is a widely accepted industrial communication standard
that enables data exchange between multi-vendor devices and control applications
without proprietary restrictions. An OPC server can communicate data continuously
among PLCs on the shop floor, RTUs in the field, HMI stations, and software
applications on desktop PCs. OPC compliance makes continuous real-time
communication possible (even when the hardware and software are from different
vendors.)
OPC Data Access 1.0a was the original specification developed by the OPC Foundation
in 1996. Although it continues to be supported by many of the OPC client applications
in use today, OPC Data Access 2.0 enhanced OPC better utilizes the underlying
Microsoft COM technology.
OPC Data Access 3.0 is the latest version of the OPC DA interface
OPC AE
OPC UA
OPC .NET
DDE
Supported Formats
CF_Text
XL_Table
Advanced DDE
Overview
Although this server is first and foremost an OPC server, there are still a number of
applications that require Dynamic Data Exchange (DDE) to share data. As such, the
server provides access to DDE applications that support one of the following DDE
formats: CF_Text ; XL_Table, and Advanced DDE.
CF_Text and XL_Table are standard DDE formats developed by Microsoft for use with
all DDE aware applications.
The DDE format CF_Text is the standard DDE format as defined by Microsoft. All DDE
aware applications suppor the CF_Text format. XL_Table is the standard DEE format as
defined by Microsoft that is used by Excel
Advanced DDE
Requirements
For the DDE interface to connect with the server, the Runtime must be allowed to
interact with desktop. (INTERACTIVE process mode)
FastDDE/SuiteLink
Overview
For security reasons, it is recommended that users utilize the most recent WonderWare
DAServer Runtime Components. For more information and available downloads, refer
to the Invensys Global Technical Support WDN website
Requirements: For the FastDDE interface to connect with the server, the Runtime must
be allowed to interact with the desktop.
The User Manager controls client Access to the project’s objects (which are the
channels, devices, tags, etc.) and their corresponding functions. The User Manager
allows permissions to be specified by user groups. For example, the User Manager can
restrict the Data Client user access to project tag data base on its permissions from the
Anonymous Clients user group. The User Manager can also transfer user information
between server installations through its import/export functions.
The User Manager has three built-in groups that each contains a built-in user. The
default groups are:
Administrators
Server Users
Anonymous Clients
Administrator
Default User
Data Client
Users cannot rename or change the description fields. Neither the default groups nor
the defaults users can be disable
VOC: BIND: enlazar; obligar; atar; ligar; encuadernar; ceñir; unir a; vincular con; ribetear;
aprisionar; apretar; trabarse; estreñir; endurecer; hacer; fraguar; tener fuerza
obligatoria; recogerse; ratificar; encordar; rematar; agavillar; liar. <verbos>
<sustantivos>: el lazo; el atasco; la lata.
Enable
Choose Yes to enable the Configuration API Server. If disabled (No); the service runs,
but does not bind to the HTTP and HTTPS Ports and clients CANNOT Access the server.
Enable HTTP: Select NO to limit data transfer to only secure/encrypted protocols and
endpoints. Select Yes to allow unencrypted data transfer.
• To prevent external Access over unsecure HTTP, this port should be blocked by
the Windows firewall.
HTTP Port
Specify the TCP/IP port for the REST client to communicate over uncrypted HTTP. The
valid range is 1 to 65535. HTTP and HTTPS ports must not match. The default port
number of 57412.
HTTPS Port
Specify the TCP/IP port for the REST client to communicate over secure HTTP. The valid
range is 1 to 65535. HTTP and HTTPS ports must not match. The default port number of
57512.
Restore Defaults:
Click to blue link to the right to restore the default HTTP and HTTPS port values.
View in Browser
Click the blue address link to the right to open the Configuration API documentation
landing page in a browser.
View in Browser(SSL)
Click the blue address link to the right to open the Configuration API documentation
landing page in a browser via the secure URL.
TRANSACTION LOGGING.
Arquitectura Cliente/Servidor
Cliente
Las funciones que lleva a cabo el proceso cliente se resumen en los siguientes puntos:
• Formatear resultados
Servidor
Las funciones que lleva a cabo el proceso servidor se resumen en los siguientes puntos:
• Las tareas del cliente y del servidor tienen diferentes requerimientos en cuanto
a recursos de cómputo como velocidad del procesador, memoria, velocidad y
capacidades del disco e input-output devices (I/O)
• Se establece una relación entre procesos distintos, los cuales pueden ser
ejecutados en la misma máquina o en máquinas diferentes distribuidas a lo largo
de la red.
• No existe otra relación entre clientes y servidores que no sea la que se establece
a través del intercambio de mensajes entre ambos. El mensaje es el mecanismo
para la petición y entrega de solicitudes de servicio.
• Una ventaja adicional del uso del esquema Cliente/Servidor es que es más rápido
el mantenimiento y el desarrollo de aplicaciones, pues se pueden emplear las
herramientas existentes (por ejemplo, los servidores de SQL o las herramientas
de más bajo nivel como los SOCKETS o el RPC).
ARQUITECTURA CLIENTE/SERVIDOR
CLIENTE: ROL que desempeña un equipo demandando servicios de los servidores, pero
también puede realizar procesamiento local, tales como desplegar páginas web,
mostrar ventanas y generar correo electrónico.
• ADMINISTRACIÓN DE DATOS: manejo de los datos (en una BD) que sirven a las
aplicaciones de la lógica de negocio, p ej. Datos de los productos de una factura,
productos en inventario.
CLIENTE: cualquier usuario o programa que quiere realizar una operación sobre el
sistema. Para apoyarlo, el sistema debe tener una CAPA DE PRESENTACIÓN a través de
la cual el usuario puede enviar las operaciones y obtener un resultado.
• Los clientes son INDEPENDIENTES ENTRE SÍ: se puede tener varias capas de
presentación dependiendo de lo que cada cliente quiere hacer.
El Middleware es un NIVEL DE INDIRECCIÓN entre los CLIENTES y las demás CAPAS DEL
SISTEMA.
Protocolo DDE
• Realizar e implementar comunicaciones de manera más eficiente usando un
protocolo de comunicación dinámico bajo el ambiente de Windows
Aplicaciones DDE
La comunicación entre aplicaciones que usan el protocolo DDE, establecen una
ESTRUCTURA DDE. Esta estructura es:
CLIENTE: programa que puede recibir datos DDE
SERVIDOR: programa que puede enviar datos al bus DDE
CLIENTE/SERVIDOR: programa que puede enviar/recibir datos a la vez.
MONITOR: puede acceder a mensajes, sin modificaciones
Comunicaciones DDE
Se basa en una convención de tres tipos de parámetro:
1. Aplicación: nombre del archivo del programa.
2. Tópico: ruta completa del proyecto desde el cual se lee
3. Elemento: Nombre de la variable que se va a leer (Tag Name)
• Node Name: solo se usa cuando la comunicación también será con otra PC. Se
deja en blanco si la COM es entre aplicaciones internas al PC
• Topic Name: Nombre del tópico del que se requiere leer (pj: nombre del archivo
EXCEL del que se quiere leer)
Almacenar los datos en SQL Server y Microsoft Azufre SQL. Para permitir
una mayor:
• Confiabilidad
• Seguridad sólida
• ESCALABILIDAD
• Facilidad de Administración a largo plazo
Features
Accessibility
KEPServerEX provides data access for client applications (such as MES and
SCADA) and IoT and Big Data analytics software via OPC, proprietary protocols
(including GE NIO, SuiteLink/FastDDE, and Splunk), IT protocols (including MQTT,
REST, ODBC, and SNMP), and flow measurement export to common Oil & Gas
industry formats.
OPC
Automation Interfaces
Cloud Interfaces
With the IoT Gateway, KEPServerEX can seamlessly stream real-time industrial
control data directly into Big Data and analytic software for Business Intelligence
and Operational Excellence. Its customizable data format supports most MQTT and
REST applications—enabling users to choose the vendors and communication
methodologies right for their system. The ThingWorx Native Interface also provides
data to the ThingWorx platform using the secure ThingWorx AlwaysOn™ protocol
for high throughput.
Exporters
OPTIMIZATION
KEPServerEX optimizes communications and reduces network and device load via
data conditioning and reduction, customized load balancing, and protocol-
specific optimization.
Redundancy
In large networks that have many devices and applications requiring information,
flexible control is necessary to allow for customized load-balancing of data
collection and information flow. KEPServerEX provides tools to schedule the
frequency of communications and throttle the demand across the network.
Communications
Machine-to-Machine Linking
Programmatic Changes
AGGREGATION
Centralized Platform
Unified Configuration
CONNECTIVITY
Driver-Based Access
Telemetry Enviroments
Rapid Deployment
SECURITY
KEPServerEX includes a variety of tools that control user access to the server, data
source, or data values, regulate read/write access, provide the ability to connect
or disconnect client applications, and support the configuration of secure data
tunnels.
Configuration
There are various tools available within KEPServerEX to control user access to the
server, data source, or data values. The Security Policies advanced plug-in limits
access based on OPC UA user credentials while supporting default handling for
anonymous users (both OPC UA and other client interfaces). The ability to
dynamically address information can be disabled, limiting user access to tags
defined within the project. KEPServerEX supports a number of secure client
standards including SNMP (v3 security), OPC UA, and OPC DA (DCOM security) to
further restrict access to the server, as well as a number of secure device protocols
to meet the requirements of DNP3, SNMP, and OPC UA data sources. Secure data
tunnels can be configured by leveraging multiple KEPServerEX instances at remote
endpoints to pass data through firewalls and meet authentication and encryption
requirements across the Internet.
DIAGNOSTICS
OPC Diagnostics
OPC Diagnostics provide a real-time and historical view of OPC events between
any OPC client and the server, including method calls made by the client or
callbacks made by the server. The ability to view actual communications and
responses is invaluable when troubleshooting client accessibility. The diagnostics
tools within KEPServerEX greatly speed deployment and reduce downtime.
Communications Diagnostics
APPLICATION CONNECTIVITY
The iFIX native client interface simplifies the connection task by allowing a direct
connection to the local iFIX application without the use of the iFIX OPC Power Tool.
When supported, this interface also has the ability to refine the connection
between the server and the iFIX Process Database (PDB).
En la nube (CLOUD):
Splunk
The Splunk API enables the streaming of real-time industrial data into
Splunk® software and Cloud services.
SNMP
REST
MQTT
ODBC
OPC.NET
OPC .NET is a family of APIs provided by the OPC Foundation that leverage
Microsoft's .NET technology and allow .NET clients to connect to the server.
KEPServerEX supports OPC .NET 3.0 WCF, formally known as OPC Xi. Unlike
other OPC .NET APIs, OPC .NET 3.0 uses Windows Communication
Foundation (WCF) for connectivity, avoiding DCOM issues and providing
secure communication via multiple communications bindings,
consolidation of the OPC Classic interfaces, and the simple development,
configuration, and deployment of Windows environments.
KEPServerEX adds OPC .NET 3.0 support using a customized version of the
OPC .NET 3.0 WCF Wrapper supplied by the OPC Foundation.
OPC Data Access 1.0a was the original specification developed by the
OPC Foundation in 1996. Although it continues to be supported by many of
the OPC client applications in use today, OPC Data Access 2.0 Enhanced
OPC better utilizes the underlying Microsoft COM technology. OPC Data
Access 3.0 is the latest version of the OPC DA interface.
The OPC Historical Data Access (HDA) specification defines query methods
and analytics that may be applied to historical data. It defines behaviors for
many well-known aggregates, which are methods that summarize data
values over a particular time domain at the time of data retrieval. It can be
used to create a simple trend data server and more complex data
compression and analysis servers that are capable of providing summary
data, history updates, history data annotations, and backfilling.