CN100521711C - 用于过程数据访问服务器的远程配置的系统 - Google Patents
用于过程数据访问服务器的远程配置的系统 Download PDFInfo
- Publication number
- CN100521711C CN100521711C CNB018189687A CN01818968A CN100521711C CN 100521711 C CN100521711 C CN 100521711C CN B018189687 A CNB018189687 A CN B018189687A CN 01818968 A CN01818968 A CN 01818968A CN 100521711 C CN100521711 C CN 100521711C
- Authority
- CN
- China
- Prior art keywords
- bstr
- configuration
- data access
- node
- name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0226—Mapping or translating multiple network management protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0883—Semiautomatic configuration, e.g. proposals from system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/564—Enhancement of application control based on intercepted application data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/10—Plc systems
- G05B2219/12—Plc mp multi processor system
- G05B2219/1208—Communication, exchange of control, I-O data between different plc
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/10—Plc systems
- G05B2219/13—Plc programming
- G05B2219/13121—DDE direct data exchange, DLL dynamic library linking
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/23—Pc programming
- G05B2219/23262—DDE direct data exchange, DLL dynamic library linking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
- H04L41/0869—Validating the configuration within one network element
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
Abstract
公开了一种用于制造/过程扩控制系统数据访问服务器的远程配置体系结构。位于远程结点(250)的服务器代理程序通知系统上的现有的数据访问服务器的配置控制台。配置实用程序包括一控制台,用户从该控制台选择标识的数据访问服务器之一。然后,配置控制台通过远程接口获得配置参数(280)及与所选数据访问服务器相关的有关规则(270)。然后配置实用程序在用户界面面板内显示检索到的配置信息,该界面面板是对于所选的配置结点的类型定义的,用于从所选的DAS显示/编辑。使用对于所选结点类型的各种面板,对于与所选数据访问服务器相关的配置,用户生成,清理,检验和/或操作分层布置的结点。
Description
与相关申请的交叉对比
本申请要求2000年9月15日提交的、名称为“Remote MultipleClient Protocol Support”的Todorov etal.U.S.临时申请Serial No.60/232,731的优先权,其内容包含在这里作为参考,包括其中包含的任何对比文件的内容和教导。
技术领域
本发明一般涉及计算机化过程控制网络的领域。更具体来说,本发明涉及访问制造/过程控制网络内的服务器组件的配置实用程序,以适应服务器组件的操作。这种服务器组件的一个例子是,支持通过监控级客户应用程序对过程控制信息访问的数据访问服务器系统。
背景技术
工业过程控制技术中的显著进展已经极大改进了制造厂和工厂操作的所有方面。在引入今天现代的工业过程控制系统之前,工业过程由人和初级的机器控制操作/控制。其结果是,对过程的控制的复杂性和程度受到速度的限制,一个或多个人员只能凭借这样的速度判断故障过程状态变量的状态,比较当前状态与所需操作水平,计算矫正的动作(如果需要),并实现对控制点的改变以影响状态变量的变化。
过程控制技术的改进已使非常大和更复杂的工业过程,能够通过编程控制处理器控制。控制处理器执行控制程序,这种程序读取过程状态变量,并基于状态变量数据与所需的设置点信息执行控制算法,以便对工业过程中的控制点提交输出值。这种控制处理器和程序支持本质上自运行的工业过程(一旦建立了设置点)。
尽管工业过程能够在编程过程控制器下在先前建立的设置点处不加干预地操作,但还是希望对控制处理器及它们相关的过程进行监控和监视。这种监控是由人和较高级控制程序两者在多级过程控制网络的应用程序/人界面层提供的。一般希望这种监控能在较低级过程控制器下检验受控过程的正确执行,并配置被控制过程的设置点。
数据访问服务器便于在各种较高级监视/控制客户应用程序内放置过程控制数据。操作过程中,过程控制器产生关于相关过程的状态和控制信息。控制器的过程状态和控制信息存储在过程控制数据库内和/或向过程控制网络内的若干位置分配。其它过程信息在具有数字数据通信能力的现场装置(例如智能传输器)内产生/存储。过程信息是从数据库和现场装置由数据服务器检索的,供过程控制系统进一步的处理/使用。例如,数据访问服务器,向提供高级控制和监视(人和计算机化)服务的各种客户应用程序,提供检索到的信息。
在包含数据服务服务器的系统中,高级控制和监视应用程序依赖于数据服务服务器适当的配置,以提供这些应用程序赖以进行决策的信息。这种信息包括实时过程变量值、警告等。制造/过程控制系统由于过程控制装置和过程本身的变化而被修改。许多数据服务服务器在复杂的过程控制计算环境中以时间临界方式操作。在具有散布在众多的建筑物中成百上千的计算机的成百上千数据访问服务器的非常大的系统中,配置运行中的数据访问服务器和从其接收它们数据的装置的操作成本,是随这种服务器数目的增加而指数上升的。完成调整操作的滞后也会增加。这种滞后对制造商代价高昂。因而,制造商一般要寻求尽量减少当调整数据访问服务器及其相关过程控制装置时遇到的滞后。重要的是在这种情形下要提供一种装置,供迅速配置数据访问服务器并尽量减少过程停滞的时间。
此外,重要的是可快速校正由过程控制系统管理的工业/制造过程中的配置错误。因为不适当的配置而有故障或不能工作的数据访问服务器可能对制造过程造成严重的停工。在许多应用程序中,如果由数据访问服务器提供的信息或控制通路不可用,则可能导致整个生产线停顿。
发明内容
本发明提供了一种新的体系结构和方法,用于从远程地点配置数据访问服务器,从而使制造/过程控制系统管理员能够配置多个数据访问服务器,而无需身体行进到执行数据访问服务器的网络上的每一结点。本发明建立了中心化的实用程序,这允许从一个地点配置一组联网的数据访问服务器(DAS)。
根据本发明,一种分布式的配置体系结构,便于过程控制数据访问服务器的远程配置。实施本发明的一种系统包括一个控制台,用户从该控制台操作配置编辑器。配置编辑器包括用户界面基础结构。配置系统还包括配置数据库,存储描述用于被标识的数据访问服务器特定的配置参数的信息。该配置系统还包括规则数据库,用于存储与可通过该配置系统配置的数据访问服务器相关的一组规则。这组配置规则指导用于数据访问服务器的配置定义的构成和/或编辑。在本发明一具体的实施例中,对每一结点类型规定这些规则。
在本发明的一实施例中,用于具体的数据访问服务器的配置规则和参数的远程连接是通过一服务器代理实施的,该服务器代理在能够运行数据访问服务器的远程结点上执行。服务器代理包括可执行的程序,用于通知配置编辑器在它们各结点上数据访问服务器的存在。本发明具体实施例的一个方面是,对于在配置系统内所支持的可配置组件(结点)类型的各种类型的每一个,配置系统能够支持定制编辑器面板。
附图说明
所附权利要求具体陈述了本发明的特征。从以下参照附图详细的说明可最好地理解本发明及其目的和先进性,其中:
图1是描绘对于本发明一示例性过程控制环境的示意图,其中一过程数据访问服务器包括一远程配置实用程序,该程序检索其它数据访问服务器内的配置信息,并转而检索/接收过程控制信息,并向驻留在过程控制网络的监视/监控层的各客户应用程序提供这种信息;
图2描绘了用于执行远程配置多分级软件结构;
图3是根据本发明的一实施例,标识一组构成客户的组件和远程配置设施的服务器组件的示意图;
图4根据本发明的一示例性实施例描绘了一组由数据访问服务器包主机(Package Host)支持的接口;
图5根据本发明的一示例性实施例描绘了一组由编辑器主机(Editor Host)支持的接口;
图6描绘了一组支持对远程存储配置数据库访问的接口;
图7是一顺序图,概括了为打开结点编辑器所执行的一组步骤,以便对远程结点上的所选的数据访问服务器的配置进行编辑;
图8是一顺序图,概括了用于向配置分层结构添加结点的一组步骤;以及
图9是一顺序图,概括了用于在远程配置存储器中保存通过配置设施作出的变化的一组步骤。
具体实施方式
结合到实施本发明的数据访问服务器系统中的远程配置实用程序和附加的接口,使用户能够从单一的远程计算机配置数据访问服务器。公开了一种示例性配置实用程序体系结构,用于通过MMC(MICROSOFT Management Console)Snap-in执行的数据访问服务器远程配置。通过远程配置咬接(snap-in),对于其本地结点内或在任何网络连接的结点上的任何数据访问服务器,用户可生成,清除,检查和/或操纵所选的数据访问服务器配置。
现转向图1,其中图示地描绘了过程控制网络10的一示例性部分。如前所述,本发明可用于任何包括数据访问服务器的网络。然而,对数据访问服务器进行远程配置的价值,随制造/过程控制网络内数据访问服务器数目和监视站与数据访问服务器之间距离的增加而增加。过程控制网络10,可被看作是连接到与过程控制网络10的特定级相关的一个或多个网络链路的一组装置。在该示例性实施例中,所描绘的过程控制网络10的部分包括现场总线级12,本地控制级14,及管理控制级16。虽然示例性实施例是作为有三级描绘的,但业内专业人员易于理解,本发明可用于具有更多或更少或相同网络级数的数个过程控制网络体系结构。示例性描绘的网络10实施了多级总线拓扑结构。然而,本发明能够结合到实施其它网络拓扑结构(例如星形网络,混合总线/星形网络等),包括单级和分层配置两者的过程控制网络中。
在图1所示的过程控制网络示例性部分中,一组智能现场装置20驻留在现场总线级12。现场装置包括智能过程变量传输器,它们检测在被控制的工业过程中的压力,温度,液流等。现场装置还包括激励器,诸如能够打开和关闭用于储箱、燃烧器的液流阀的装置。
在本地控制级14的控制处理器30对于智能现场装置20组执行本地控制功能。控制处理器30接收由智能现场装置20提供的过程状态信息。例如状态信息包括压力,温度,质量流,容积式流等。控制过程向对过程设置的所需的点施加所接收的状态信息,并然后向激励器传送控制信号,以便获得或维持所需的设置点。控制处理器被编程/配置,以便存储与它们的控制功能相关的状态和控制信息。
管理控制级16包括较高级的控制应用程序,这些程序帮助和/或实现企业/工厂级决策形成和管理(例如设置点)控制值指定功能。警告服务器40从数个较低级来源,包括控制处理器30和形成装置20,接收过程状态数据。警告服务器40对照一组警告/事件条件比较收到的状态数据,并响应检测到的警告/事件条件向监视器或控制过程(例如控制处理器30)发出适当的通知。控制处理器30向被控制的现场装置/激励器发出适当的信号,以便告知事件/警告条件。也是操作在管理控制级16的历史记录器(historian)42把从过程控制系统的上述任何级收到的数据存档。这种数据可用于由各种应用程序进行的审核和检验。人机接口(HMI)44是另一连接到管理控制级16的结点。人机接口44提供了一组图形/文本用户界面功能,使人能够查看与所描绘的图1的项相关的过程控制系统有关的被控制过程的操作/状态。
在本发明的一示例性实施例中,一组数据访问服务器结点50a,50b,50c插入在过程控制系统的管理控制级16的处理结点与较低级(例如本地控制级14与现场总线级12)之间。运行一个或多个逻辑DA服务器的数据访问服务器结点50b,从现场装置20(通过信道52)和/或控制处理器30(通过信道54)接收和/或抽取数据,并把对应的的数据(可能重定格式)提供给过程控制网络10的管理控制级16的处理结点-包括运行其它数据访问服务器之一的一个或多个结点。数据访问服务器结点50a-c执行向各种客户应用程序提供数据的任务,这些应用程序要根据具体的数据交换协议获得数据,否则不能访问在本地控制级14和现场总线级12提供的过程控制数据。在Todorov et al.U.S.patentapplication(number not yet assigned)filed on September 14,2001,andentitled“An Industrial Process Control Data Access ServerSupporting Multipl Client Data EXchange Protocols,”描述了一种用于支持多客户数据交换协议的方法和系统,该文献在此就其包含的任何对比文献整体结合以资对比。
在数据访问服务器(DAS)50c,任何其它的数据访问服务器,或任何管理级16上的结点执行的配置实用程序(在图1中以窗口56指示),提供了用于远程配置过程控制系统数据访问服务器的方法。在本发明的一实施例中,数据访问服务器配置实用程序是在与数据访问服务器一同结点上执行的应用程序。例如如图1中所描绘,配置实用程序在数据访问服务器结点50c上执行。然而,不需要使配置实用程序驻留在任何特定类型的结点上(因为它是独立于DAS数据获取/传送过程执行的)。在本发明的示例性实施例中,配置实用程序(工具)通过至少在结点50a和50b例示的DAS代理(查询这些结点每一个上的注册表),发现运行在50a,50b及50c上的DAS结点数据访问服务器,并把一列表呈现给用户。DAS代理是用于发现网络上数据访问服务器的工具。然后用户能够选择有关的一个或多个数据访问服务器以进行配置。一旦在DAS结点上运行的配置实用程序与数据访问服务器之间建立起连接,数据访问服务器内的其它组件就可从配置实用程序接收并处理信息请求。那些组件将在以下参照图2讨论。还应注意,在本发明的实施例中,配置实用程序被结合到包含在每一数据访问服务器结点50a,50b及50c内的基库中,因而为支持网络内的配置实用程序,管理员方面不必添加任何特别程序或可执行代码。
在图1中所述的示例性实施例中,执行每一DAS结点50a-c核心功能的处理引擎主控配置实用程序,并通过这里以下参照图4-6所述的一组明确定义的接口公开一组默认的配置信息。如以上这里所述,经过DA服务器的服务器特别部分的定制,通过扩展由数据访问服务器向配置实用程序公开的可配置特性范围,能够强化数据访问服务器结点的功能。
此外,要重申的是,本发明不限于特定的过程控制系统网络拓扑结构或技术。例如,所公开的示例性过程控制网络包括分层安排的数字系统。然而在另外的网络实施例中,本发明被结合到与单级过程控制网络连接的监视结点,其中现场装置,控制处理器,及管理控制应用程序组成单总线上的结点。在另一情形下,DAS接收关于采用4-20毫安标准用于过程通信的传统的模拟式现场装置的数据。
若干特性有助于强化从远程地点配置数据访问服务器。首先,配置实用程序结合了一般的多层次体系结构。可辨别的层次包括接口,规则解释,及配置持续层次。其次,配置实用程序支持在上述级的热(在线)配置。第三,能够定义任何数目的分层级。第四,配置实用程序支持进行远程配置。将在以下更详细地讨论这些特性的每一个。
参见图2,配置实用程序的一般多层级软件体系结构包括数据服务层100,业务服务层110,及表示服务层120。各层级是通过在数据服务层100执行的“规则”文件实现的,就是说与(对)每一数据访问服务器相关(规定)。数据访问服务器特定的规则文件,规定了一组配置分层级以及关于对每一分层级配置结点定义的性质的信息。关于性质的信息包括:所允许的子结点的最小/最大数,所允许的子结点的名称和类型,默认性质值,最小/最大性质值,以及性质的名称和类型。
“规则”文件例如是通过一组XML定义实现的。然而,作为业内专业人员易于理解,其它语言/格式规定规则也能够采用。在底层级内规则文件访问的封闭允许对这一方案进一步的修改而不会影响配置分层结构的任何其它层。而且包含在规则文件中的还有对每一分层结构级激活的ActiveX面板的GUID。
分层的组织支持一种一般的体系结构,允许在一级的改变而不影响未改变的其它级。在表示服务层次120的主配置MMC咬接使用业务服务层次110作为“规则解释程序/监视程序”,该程序防止用户在配置的树视图中建立无效的分层结构。业务服务层次110还保证了由用户输入的数据,就由特定数据访问服务器规则文件而言是有效的。
关于所公开的远程配置体系结构的第二方面,热配置是指允许用户修改服务器的配置部分,并把这些改变结合到运行中的并且是工作中的服务器中。被更新的配置参数的实际推动依赖于由服务器开发者规定的界面,该界面便于通知服务器这一配置的改变。DAS代理跟踪DAS结点上当前工作的服务器,并允许用户作出对当前服务器状态所允许的配置的修改。
就所公开的远程配置体系结构的第三方面来说,在配置树的分层结构内任何级(不要与图2所描绘的程序分层结构混淆),规则’文件定义了能够添加到当前结点下的树的配置结点(树叶和/或分支)。这样,配置树体系结构由实际访问服务器开发者所定义,并且没有另外会限制这种开发的预先定义分层结构。
就所公开的远程配置体系结构第四方面来说,实现配置实用程序的MMC咬接,在任何网络可访问结点上对于特定的实际访问服务器(可以是远程的或本地的)是可执行的。结点之间的通信通过DCOM进行。安装在所有服务器结点上的DAS代理处理服务器定位/接口功能。通过DAS代理客户(配置实用程序)查询所安装的服务器和/或当前运行的服务器。
现转向图3,其中简略描绘了配置软件组件的编排,用于通过安装在数据访问服务器结点50c上的配置实用程序,实现远程配置信息抽取/操作。这里还称作为DAS控制客户(DASCC200)MMC的咬接模块200,是根据Microfoft MMC实用程序的要求书写的,并构成由用户从WINDOWS 98(以及后来的WINDOWS版本)资源工具包调用的MMC主要的可执行模块。MMC咬接表示许多潜在的方式之一,以便捆绑配置实用程序的组件。程序包主机210是把通信封闭在用于远程配置的暂留区内的模块(DLL)。暂留区是物理存储装置与存储在物理存储装置上的配置/规则的逻辑组织的一种组合。例如,暂留区可以是存储在存储结点上的带有XML文本的文件。另外,暂留区具体可定义为存储结点上的关系数据库。程序包主机210完成以下任务:(1)从暂留区抽取可用的数据并使其对于结点编辑器可用,(2)核实并把由结点编辑器提供的值暂留到暂留区,以及(3)向与生成并删除新的/现有的配置分层结构结点相关的DASCC提供服务。结点程序包220是服务器专用(即从工具包模板定制的用户)的模块,对业务服务器110提供定制验证逻辑。
编辑器主机230模块(DLL)是在支持用于编辑特定结点类型的定制配置接口中,对用户开发者可生成的所有定制面板(结点编辑器)的一般主机。编辑器主机230对所有的配置分层结构-诸如对于“施加”变化,“回复”参数值到上次被暂类留值等,提供一种公共的GUI外观和感觉。结点编辑器240,如同可得程序包,是对在DAS配置实用程序中支持的每一结点类型专用的一种定制的面板。结点编辑器240一般是由数据访问服务器开发者提供的,并封闭在编辑器主机230上配置的具体结点类型的细节。在本发明的一实施例中,结点编辑器240的库(由配置系统支持的每一结点类型一个)存储在DAS控制客户200的计算机结点上。然而这不是要求,并实际上在本发明另外的实施例中,结点编辑器的例子(从一般结点编辑器接口定义推导)存储在例如包含用于特定DAS的配置和规则信息的远程结点上。
存储在包含可访问的DAS每一远程结点上的远程基础结构250,包括一组便于远程配置的模块。远程基础结构250例如包括两个模块(并能够在未来需要时扩展)。首先,DASConfigAssess.dll便于与存储器/暂留区通信,以便对于所选数据访问服务器访问/存储当前配置和规则。这一接口从配置参数和规则区存储在系统的各种方式抽取配置编辑器。这允许配置编辑器可与各种存储区格式(例如文件,数据库等)不必修改而操作。与特定存储格式和访问方法相关的访问方法。第二,DASAgent.eXe便于对已安装的/运行的DAS实例查询结点,并向用户的远程配置实用程序返回报告。
规则270是一种暂留区,一般由用户在远程配置期间规定并然后存储在远程DAS结点,包含所有分层结构参数和它们的关系/相关性的描述。在本发明的一实施例中,XML列表存储在规则文件中,但另外的一种实现也考虑诸如数据库。类似于C++编程语言,规则文件对应于类,同时配置280对应于“规则”定义的类的一组实例。配置280是标识/描述所有配置的分层结点及其相关参数的远程配置的一种暂留区(在由用户进行远程配置后存在)组件。又虽然XML用于一示例性实施例,但本发明的其它的实施例以不同的格式/语言(例如数据库)规定了配置。
图4,5和6包括与远程配置设备相关的对象类和类的相关接口。转向图4,其中描绘了在CnodeEditor类290中实现的一组接口,结点编辑器240是从该类例示的。CnodeEditor类对象是基于以下所规定的接口对于配置结点的每一类型生成的。IDASEditor接口295对于编辑器主机230提供了一种机制,以便与结点编辑器240通信。IDASEditorEvent 310接口(以下参照与编辑器主机230相关的对象类描述)对程序包主机210提供了一种机制,以便通知结点编辑器240关于上下文的变化。
Declaration
[
object,
uuid(320C0A36-AB7C-11d4-93E4-00B0D0201D61),
pointer_default(unique)
]
/*
IDASEditor is an interface implemented by each Node Editor.It allows the
Editor host to initialize the Node Editor and notify it about extenal events.
*/
interface IDASEditor:IUnknown
{
HRESULT Initialize (
[in]IDASPackageSite *pPackage,
[in]IDASEditorSite *pHostSite,
[in]BSTR bstrFullNodeName,
[in]BSTR bstrNodeName,
[in]BSTR bstrDelimeter,
[in]VARIANT_BOOL bIsReadOnly,
[in,unique]VARIANT* pVarAux);
HRESULT Apply();
HRESULT Restore();
HRESULT Close();
}
Description
{vb}
Operations
Apply
/*Notifies the Node Editor to persist(store)current data*/
Declaration
HRESULT Apply ()
Return Value
S_OK
The status change was noted.
E_FAIL
Failure
Close
/*Notifies the Node Editor that editor will be closed*/
Declaration
HRESULT Close ()
Return Value
S_OK
CleanUpwas succeeful.
E_FAIL
Failure
Initialize
/*Initialize the Node Editor with parameterrs allowingitto comunicate with DAS infrastructure*/
Declaration
HRESULT Initialize (
[in]IDASPackageSite *pPackage,
[in]IDASEditorSite *pHostSite,
[in]BSTR bstrFullNodeName,
[in]BSTR bstrNodeName,
[in]BSTR bstrDelimeter,
[in]vARIANT_BOOL bIsReadonly,
[in,unique]VARIANT* pVarAux)
Return Value
S_OK
The status change was noted.
E_FAIL
Failure
Restore
Declaration
HRESULT Restore()
/*Instruct the Node Editor to restore the last persisted values*/
Return Value
S_OK
The status change was noted.
E_FAIL
Failure
继续参照图4,其中描绘了一组接口,它们是在编辑器主机230从其被例示的CDASEditorHost类300中实现的。对于每一DAS例子例示一个编辑器主机对象。IDASEditorEvent 310接口对程序包主机210提供了一种机制,以便通知编辑器主机230关于上下文的变化。上下文的变化例如包括:结点名称的变化和由特定结点编辑器240公开的参数的变化。IDASEditorEvent 310的操作用来通知编辑器主机230和结点编辑器240关于由这些项事件查询的行动。在编辑器主机230的情形下,这种调用例如由程序包主机210使用。
Declaration
[
object,
uuid(320C0A33-AB7C-11d4-93E4-00B0D0201D61),
pointer_default(unique)
]
interface IDASEditorEvents:IUnknown
{
HRESULT OnNameChange
(
[in,string]BSTR bstrFullOldNodeName,
[in,string]BSTR bstrOldNodeName,
[in,string]BSTR bstrNewNodeName
);
HRESULT OnAtributeChange
(
[in,string]BSTR bstrFullNodeName,
[in,string]BSTR bstrAttrName,
[in]DWORD PropID,
[in]VARIANT varNewValue
);
}
Description
{vb}
OnAtributeChange
/*Notifies the Node Editor about parameter changes*/
Declaration
HRESULT OnAtributeChange
(
[in,string]BSTR bstrFullNodeName,
[in,string]BSTR bstrAttrName,
[in]DWORD PropID,
[in]VARIANT varNewValue
)
Parameters
BstrFullNodeName Specifies the full node name
BstrAttrName Specifies the attribute name
PropID Specifiesthe property ID
VarNewValue New attribute Value
Reiurn Value
S_OK
Success
OnNameChange
/*Notifies the Node Editor about node name changes*/
Declaration
HRESULT OnNameChange
(
[in,string]BSTR bstrFullOldNodeName,
[in,string]BSTR bstrOldNodeName,
[in,string]BSTR bstrNewNodeName
)
parameters
bstrFullOldNodeName Specifies the full old node name
BstrOldNodeName Specifies the node name
BstrNewNodeName Specifies the node name
Return Value
S_OK
Success
IDASEditorHost接口320是由EditorHos组件实现的并在各结点编辑器之间提供公共的功能。例如它主控定制结点编辑器,并处理诸如当用户寻求暂留新的配置数据或存储上一个暂留配置数据时的事件。
Declaration
[
object,
uuid(320C0A34-AB7C-11d4-93E4-00B0D0201D61),
pointer_default(unique)
]
interface IDASEditorHost:IUnknown
{
HRESULT Initialize(
[in]IDASPackageSite *PackageSite,
[in]BSTR strEditorGuid,
[in]BSTR strFullNodePath,
[in]BSTR strNodeName,
[in]BSTR strNodeType,
[in]BSTR bstrDelimiter);
HRESULT Close(
[in]BOOL bForce);
HRESULT IsDirty(
[out]BOOL* dirty);
}
ODerations
Close
/*Notification that hosted Configuration Node Editor will be closed*/
Declaration
HRESULT Close(
[in]BOOL bForce)
Parameters
BForce Flag specifying whether to Close and discard changes
without prompting user to save changes or not:
TRUE-discard changes(if any)and do not prompt user
FALSE-prompt user if changes since last′Apply′
Return Value
S_OK
Sucess.
Initialize
/*Initia]ize that editor host with parameters allowing it to communicate with the storage area*/
Declaration
HRESULT Initialize (
[in]IDASpackageSite *PackageSite,
[in]BSTR strEditorGuid,
[in]BSTR strFullNodePath,
[in]BSTR strNodeName,
[in]BSTR strNodeType,
[in]BSTR bstrDelimiter)
Parameters
PackageSite Interface to the Storage area
strEditorGuid GUID for the custom editor
strFullNodePath This is fully qualified name of the parent.
strNodeName Specifies the Node Name
strNodeType Specifies is Node Type
bstrDelimiter Specifies is Node Type
Return Value
S_OK
Succees.
IsDirty
/*Checks whether some of the parameters in the Node Editor were changed(state‘dirty’)since the lasr
“Apply”*/
Declaration
HRESULT IsDirty(
[out]BOOL* dirty)
Parameters
Dirty Flag indicating whetherthe editor is“dirty”(has changed attributes)
TRUE-the attribures has been change
FALSE-no change from the last save operation
Return Value
S_OK
Succees.
IDASEditorSite接口330对于结点编辑器240提供了一种机制,以便对编辑器主机230通信。
Declaration
[
object,
uuid(F4136354-C2A0-47db-89F1-463ADEDFFDFF),
pointer_default(unique)
]
interface IDASEditorSite:IUnknown
{
HRESULT OnStatusChange ();
}
Description
{vb}
Opcations
OnStatusChange
Declaration
HRESULT OnStatusChange ()
Return Value
S_OK
The status change was noted.
参见图5,其中描绘了在CDASPackage类400中实现的一组接口。IDASPackage接口410对于结点编辑器240提供了一种访问存储区的机制。IDASPackage接口410还提供了对DAS定制控制台(或DASCC)的服务。例如当用户向一配置添加新的结点时。DASCC在对特定存储的结点规定的规则视图中呈现“可用”结点的指示。例如,用户在规则文件中配置一类型“TCP”的结点。该TCP结点能够具有类型PLC的多达3个子结点,以及多达5的PyramidIntegrator结点。在用户添加3个PLC结点之后,将不允许添加这种类型更多的结点,因为配额用完。这种对于配置规则一致性的测试是由PackageHost 210向DASCC 200提供的信息实现的。PackageHost 210“编译”了来自规则和配置的信息,并把过程的结果提供给DASCC 200或结点编辑器240。
Declaration
[
object,
dual,
uuid(320C0A37-AB7C-11d4-93E4-00B0D0201D61),
pointer_default(unique)
]
/*
IDASPackage provides information to the DASCC about the current DAS
configuration and notifies the Package Host about user commands(like
add/delete a node for example)
*/
interface IDASPackage:IDispatch
{
HRESULT Initialize(
[in,string]BSTR bstrServerGUID,
[in]IUnknown* pCfgRules
);
HRESULT GetChildren(
[in,string]BSTR bstrFullNodeName,
[in,string]BSTR bstrNodeDelimiter,
[out]SAFEARRAY(BSTR)*bstrArrayChildrenNames,
[out]SAFEARRAY(BSTR)*bstrArrayChildrenTypes,
[out]SAFEARRAY(BSTR)*bstrArrayChildrenDelimiters
);
HRESULT GetPossibleChildTypes(
[in,string]BSTR bstrFullNodeName,
[out] SAFEARRAY(BSTR)*bstrChildTypes
);
HRESULT GetNodeProperties(
[in,string] BSTR bstrNodeType,
[out] BSTR*strEditorGUID,
[out] BSTR*strDelimiter
);
HRESULT RenameNode(
[in,string]BSTR bstrFullOldNodeName,
[in,string] BSTR bstrOldNodeName,
[in,string] BSTR bstrNewNodeName
);
HRESULT AddChild(
[in,string] BSTR bstrFullNodeName,
[in,string] BSTR bstrType,
[in,string] BSTR bstrDelimiter
);
HRESULT DeleteChild(
[in,string] BSTR bstrFullNodeName
);
HRESULT SelectionChange(
[in,string] BSTR bstrFullNodeName,
[in,string] BSTR bstrNodeType
);
HRESULT GetCfgSetFileName(
[out] BSTR* pFileName
);
HRESULT SetCfgSetFileName(
[in] BSTR bstrFileName
);
HRESULT EnumCfgSets(
[out]SAFEARRAY(BSTR)* pConfigSets
);
HRESULT SwitchToCfgSet(
[in] BSTR bstrConfigSet
);
HRESULT SaveCfgSetAs(
[in] BSTR bstronfigSet
);
HRESULT ClearCoinfig(
);
HRESULT DeleteCfgSet (
[in] BSTR bstrConfigSet
);
}
Operations
AddChild
Declaration
HRESULT AddChild(
[in,string]BSTR bstrFullNodeName,
[in,string]BSTR bstrType,
[in,string]BSTR bstrDelimiter
)
Parameters
bstrFullNodeName Specifies fully qualified Node name
BstrType Specifies node type
bstrDelimiter Specifies the new Node Delimiter
Return Value
S_OK
Success
E_FAIL
Error
ClearConfig
Declaration
HRESULT ClearConfig(
)
Return Value
S_OK
Success
E_FAIL
Error
DeleteCfgSet
Declaration
HRESULT DeleteCfgSet (
[in] BSTR bstrConfigSet
)
Parameters
bstrCongfigSet Specify configation set name
Return Value
S_OK
Success
E_FAIL
Error
DeleteChild
Declaration
HRESULT DeleteChild(
[in,string]BSTR bstrFullNodeName
)
Parameters
bstrFullNodeName Specifies fully qualified node name
Return Value
S_OK
Success
E_FAIL
Error
EnumCfgSets
Declaration
HRESULT EnumCfgSets(
[out]SAFEARRAY(BSTR)* pConfigSets
)
Parameters
pConfigSets returns list wit configuration set(only names,no path)
GetCfgSetFileName
Declaration
HRESULT GetCfgSetFileName(
[out] BSTR* pFileName
)
Parameters
pFileName full name
GetChildren
Declaration
HRESULT GetChildren(
[in,string]BSTR bstrFullNodeName,
[in,string]BSTR bstrNodeDelimiter,
[out]SAFEARRAY(BSTR)*bstrArrayChildrenNames,
[out]SAFEARRAy(BSTR)*bstrArrayChildrenTypes,
[out]SAFEARRAY(BSTR)*bstrArrayChildrenDelimiters
)
Parameters
bstrFullNodeName Specifies fully qualified node name
bstrNodeDelimtter Specifies fully qualified node name
bstrArrayChildrenNames Array with the names of the all children
bstrArrayChildrenTypes Array with the types for each children
bstrArrayChildrenDelimiters Array with the delimiters for each children
Return Value
S_OK
Success
E_FAIL
Error
GetNodeProperties
Declaration
HRESULT GetNodeProperties(
[in,string]BSTR bstrNodeType,
[out]BSTR *strEditorGUID,
[out]BSTR *strDelimiter
)
Parameters
bstrNodeType Specifies node type
StrEditorGUID Returns the Editor GUID for the specified Node type
strDelimiter Returns Node delimiter
Return Value
S_OK
Success
E_FAIL
Error
GetPossibleChildTypes
Declaration
HRESULT GetPossibleChildTypes(
[in,string]BSTR bstrFullNodeName,
[out]SAFEARRAY(BSTR)*bstrChildTypes
)
Parameters
bstrFullNodeName Specifies fully qualified node name
bstrChildTypes Returns a list with child types
Initialize
Declaration
HRESULT Initialize(
[in,string]BSTR bstrServerGUID,
[in]IUnknown* pCfgRules
)
Parameters
BstrServerGUID Specifies Server Name(ProgID of the Server)
PCfgRules Interface to the IOAgent on the node where the Server resides
Return Value
S_OK
Success
E_FAIL
Error
RenameNode
Declaration
HRESULT RenameNode(
[in,string]BSTR bstrFullOldNodeName,
[in,string]BSTR bstrOldNodeName,
[in,string]BSTR bstrNewNodeName
)
Parameters
bstrFullOldNodeName Specifies the Full Old Node a Name
bstrOldNodeName Specifies the Full New name for a Node
bstrNewNodeName Specifies the Full New name for a Node
Return Value
S_OK
Success
E_FAIL
Error
SaveCfgSetAs
Declaration
HRESULT SaveCfgSetAs (
[in] BSTR¨ bstrConfigSet
)
Parameters
bstrConfigSet
specify configation set name
Return Value
S_OK
Success
E_FAIL
Error
SelectionChange
Declaration
HRESULT SelectionChange(
[in,string]BSTR bstrFullNodeName,
[in,string]BSTR bstrNodeType
)
Parameters
BstrFullNodeName Specifies fully qualified node name
BstrNodeType Specifies Node type
Return Value
S_OK
Success
E_FAIL
Error
SetCfgSetFileName
Declaration
HRESULT SetCfgSetFileName(
[in] BSTR bstrFileName
)
SwitchToCfgSet
Declaration
HRESULT SwitchToCfgSet(
[in] BSTR bstrConfigSet
)
IDASPackageSite接口420支持结点编辑器240与对于它们的参数值之间的连接。这一接口不直接与存储区通信。在示例性实施例中,还有存储区与PackageHost210之间的一个间接级(这实现IDASPackageSite)。这一间接级是通过在远程基础结构250中实现了IIOSrvCfgPersist和IioSrvCfgRules接口的DASConfigAccess.dll提供的。
Declaratlon
[
object,
uuid(320C0A39-AB7C-11d4-93E4-00B0D0201D61),
pointer_default(unique)
]
interface IDASPackageSite:IUnknown
{
HRESULT GetAttribute
(
[in]DWORD attributeHandle,
[in]DWORD PropID,
[out,retval]VARIANT*pVarValue
);
RRESULT SetAttribute
(
[in]DWORD attributeHandle,
[in]DWORD PropID,
[in]VARIANT varValue,
[out,retval]VARIANT_BOOL* pbSuccessFlag
);
HRESULT GetAttrHandle
(
[in,string]BSTR attParent,
[in,string]BSTR attName,
[out,retval]DWORD* pAttributeHandle
);
HRESULT CloseAttrHandle
(
[in]DWORD attributeHandle
);
HRESULT GetPackageShapeInfo
(
[in,string]BSTR bstrFullNodeName,
[in]SHORT nSelection,
[out]SAFEARRAY(BSTR)*bstrAttrNames
);
HRESULT Commit
(
BSTR bstrFullNodeName,
BSTR bstrType,
BSTR bstrDelimiter,
SHORT *CommitStatus
);
}
Descrlption
{vb}
Operations
CloseAttrHandle
Declaration
HRESULT CloseAttrHandle
(
[in]DWORD attributeHandle
)
Parameters
attributeHandle Handle of the attribute,retrieved from Shape Data Collection.
Return Value
S_OK
ShapeInfo was successfully retrieved.
Commit
Declaration
HRESULT Commit
(
BSTR bstrFullNodeName,
BSTR bstrType,
BSTR bstrDelimiter,
SHORT *CommitStatus
)
Parameters
bstrFullNodeName Full Node name
bstrType Node type
bstrDelimirer Node Delimiters
CommitStatus Indicates the status of the Commit.Following values are defined
COMMIT_OK-Changes are saved COMMIT_INVALID_HANDLE-
invalid handle specified COMMIT_FAIL-The changes are not saved due to
problems with the overall integriry of the node attributes
COMMIT_REMOTE_FAIL-Remote method call has failed
Return Value
S_OK
new values were successfully set
E_FAIL
Fail to save the change
GetAttrHandle
Declaration
HRESULT GetAttrHandle
(
[in,string]BSTR attParent,
[in,string]BSTR attName,
[out,retval]DWORD* pAttributeHandle
)
Parameters
attParent The paret of the attribute.
attName The parent of the attribute.
pAttributeHandle The returned handle of the attribute.Canbe used in Get/Set Attribute calls.
Retuurn Value
S_OK
Successfully set the value of the property.
注释
GetAttriHandle操作获得属性处理,然后该属性处理能够用于Get/Set属性调用。GetAttriHandle操作不解决阵列或性质基准。如果需要这些,客户应当在发出Get或Set调用之前直接更新适当的MxAttributeHandle字段。
GetAttribute
Declaration
HRESULT GetAttribute
(
[in]DWORD attributeHandle,
[in]DWORD PropID,
[out,retval]VARIANT *pVarValue
)
Paraneters
attributeHandle Handle of the attribute,retrieved from Shape Data Collection.
PropID Requested Property ID
pVarValue Receives the Value of the attribute/property.
Return Value
S_OK
Successfully retrieved the value.
Remarks
Used to get the attribute values of a primitives.
GetPackageShapeInfo
Declaration
HRESULT GetPackageShapeInfo
(
[in,string]BSTR bstrFullNodeName,
[in]SHORT nSelection,
[out]SAFEARRAY(BSTR)+bstrAttrNames
)
Parameters
BstrFullNodeName Full Node Name
NSelection Speeifies the type of array to return For all allowed values please
refer to enumerator SHAPE_INFO_ENUM
BstrAttrNames BSTR Safe array pointer.This array will be filled with reqested
shape informatioin for specifique node
Return Value
S_OK
ShapeInfo was successfully retrieved.
SetAttribute
Declaration
HRESULT SetAttribute
(
[in]DWORD attributeHandle,
[in]DWORD PropID,
[in]VARIANT varValue,
[out,retval]VARIANT_BOOL* pbSuccessFlag
)
Parameters
AttributeHandle Handle of the attribute,retrieved from Shape Data Collection.
PropID Requested Property ID
VarValue Value of the property.
pbSuccessFlag Signifies whether set was accepted.
Return Value
S_OK
Successfully set the value of the property.
注释
用来设置原语的属性值。
现参见图6,其中描绘了在CIOSrvCfgpersist类500中实现的一组接口。IIOSrvCfgpersist类510定义了一组方法,用于读取当前配置,用于编辑或在配置280中保存一新的配置。
Declaration
[
object,
dual,
uuid(52088D9A-DED4-11D3-83F2-00A024A866AC),
helpstring("IIOSrvCfgPersist Interface"),
pointer_default(unique)
]
/*
IIOSrvCfgPersist provides a way to persis the current configuration into
the storage area and retreive this information later
*/
interface IIOSrvCfgPersist:IDispatch
{
HRESULT GetCfgFileName (
[in] BSTR ServerClsIdString,
[out] BSTR* pFileName
);
HRESULT SetCfgFileName(
[in] BSTR ServerClsIdString,
[in] BSTR FileName
);
HRESULT EnumCfgSets(
[in] BSTR ServerClsIdString,
[out]SAFEARRAY(BSTR)* pConfigSets
);
HRESULT SwitchToCfgSet(
[in] BSTR ServerClsIdString,
[in] BSTR pConfigSet
);
HRESULT SaveCfgSetAs(
[in] BSTR ServerClsIdString,
[in] BSTR pConfigSet
);
HRESULT ClearCfgFile(
[in] BSTR ServerClsIdString
);
HRESULT DeleteCfgFile(
[in] BSTR bstrServerClsIdString,
[in] BSTR bstrConfigurationSet
);
HRESULT SetHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Type,
[in] BSTR Delimiter,
[in,unique]SAFEARRAY(BSTR)* pProperties
);
HRESULTGet]HierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[out] BSTR * pType,
[out] BSTR * pDelimiter,
[out]SAFEARRAY(BSTR)* pProperties
);
HRESULT RemoveHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name
);
HRESULT RenameHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR NewName);
HRESULT SetTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[in] BSTR Type,
[in] LONG UpdateInterval,
[in,unique]SAFEARRAY(BSTR)* pProperties
);
HRESULT GetTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[out] BSTR * pType,
[out] LONG * pUpdateInterval,
[out]SAFEARRAY(BSTR)* pProperties
);
HRESULT RemoveTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent);
HRESULT RenameTopic Object(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR Parent,
[in] BSTR NewName);
HRESULT SetLeafObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[in] BSTR Type,
[in] BSTR Delimiter,
[in,unique] SAFEARRAY(BSTR)* pProperties
);
HRESULT GetLeafObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[out] BSTR* pType,
[out] BSTR* pDelimiter,
[out]SAFEARRAY(BSTR)* pProperties
);
HRESULT RemoveLeafObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent);
HRESULT RenameLeafObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR Parent,
[in] BSTR NewName);
HRESULT BrowseHierarchyObjects(
[in] BSTR ServerClsIdString,
[in] BSTR BranchName,
[out]SAFEARRAY(BSTR)* pBranches,
[out]SAFEARRAY[BSTR)* pLeaves,
[out]SAFEARRAY(BSTR)* pTopics
);
HRESULT SetDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Type,
[in,unique]SAFEARRAY(BSTR)* pProperties
);
HRESULT GetDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[out] BSTR* pType,
[out]SAFEARRAY(BSTR)* pProperties
);
HRESULT RemoveDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name);
HRESULT RenameDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR NewName);
HRESULT BrowseDataObjects(
[in] BSTR ServerClsIdString,
[out]SAFEARRAY(BSTR)* pDataObjects
);
HRESULT GetSystemObject(
[in] BSTR ServerClsIdString,
[out] SAFFARRAY(BSTR)* pProperties
);
HRESULT SetSystemObject(
[in] BSTR ServerClsIdString,
[in,unique]SAFEARRAY(BSTR)* pProperties
);
HRESULT RemoveSystemObject(
[in] BSTR ServerClsIdString);
}
Operations
BrowseDataObjects
Declaration
HRESULT BrowseDataObjects(
[in] BSTR ServerClsIdString,
[out]SAFEARRAY(BSTR)* pDataObjects
)
BrowseHierarchyObjects
Declaration
HRESULT BrowseHierarchyObjects(
[in] BSTR ServerClsIdString,
[in] BSTR BranchName,
[out]SAFEARRAY(BSTR)* pBranches,
[out]SAFEARRAY(BSTR)* pLeaves,
[out]SAFEARRAY(BSTR)* pTopics
)
ClearCfgFile
Declaration
HRESULT ClearCfgFile(
[in] BSTR ServerClsIdString
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
DeleteCfgFile
Declaration
HRESULT DeleteCfgFile(
[in] BSTR bstrServerClsIdString,
[in] BSTR bstrConfigurationSet
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function wasinvalid.
EnmCfgSets
Declaration
HRESULT EnumCfgSets(
[in] BSTR ServerClsIdString,
[out]SAFEARRAY(BSTR)* pConfigSets
)
Parameters
pConfigSets returns list wit configuration set(only names,no path)
GetCfgFileName
Declaration
HRESULT GetCfgFileName(
[in] BSTR ServerClsIdString,
[out] BSTR* pFileName
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
GetDataObject
Declaration
HRESULT GetDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[out] BSTR* pType,
[out]SAFEARRAY(BSTR)* pProperties
)
GetHierarchyObject
Declaration
HRESULT GetHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[out] BSTR* pType,
[out] BSTR* pDelimiter,
[out]SAFEARRAY(BSTR)* pProperties
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
GetLeafObject
Declaration
HRESULT GetLeafObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[out] BSTR* pType,
[out] BSTR* pDelimiter,
[out]SAFEARRAY(BSTR)* pProperties
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
GetSystemObject
Declaration
HRESULT GetSystemObject(
[in] BSTR ServerClsIdStriag,
[out]SAFEARRAY(BSTR)* pProperties
)
GetTopicObject
Declaration
HRESULT GetTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR parent,
[out] BSTR* pType,
[out] LONG* pUpdateInterval,
[out]SAFEARRAY(BSTR)* pProperties
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RemoveDataObject
Declaration
HRESULT RemoveDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name)
Return Value
S_OKThe operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RemoveHierarchyObject
Declaration
HRESULT RemoveHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RemoveLeafObject
Declaration
HRESULT RemoveLeafObject{
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_UTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RemoveSystemObject
Declaration
HRESULT RemoveSystemObject(
[in] BSTR ServerClsIdString)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RemoveTopicObject
Declaration
HRESULT RemoveTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RenameDataObject
Declaration
HRESULT RenameDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR NewName)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RenameHierarchyObject
Declaration
HRESULT RenameHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR NewName)
Reiurn Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RenameLeafObject
Declaration
HRESULT RenameLeafObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR Parent,
[in] BSTR NewName)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
RenameTopicObject
Declaration
HRESULT RenameTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR OldName,
[in] BSTR Parent,
[in] BSTR NewName)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
SaveCfgSetAs
Declaration
HRESULT SaveCfgSetAs(
[in] BSTR ServerClsIdString,
[in] BSTR pConfigSet
)
SetCfgFileName
Declaration
HRESULT SetCfgFileName(
[in] BSTR ServerClsIdString,
[in] BSTR FileName
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INvALIDARG An argument to the function was invalid.
SetDataObject
Declaration
HRESULT SetDataObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Type,
[in,unique]SAFEARRAY(BSTR)* pProperties
)
SetHierarchyObject
Declaration
HRESULT SetHierarchyObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Type,
[in] BSTR Delimiter,
[in,unique]SAFEARRAY(BSTR)* pProperties
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INVALIDARG An argument to the function was invalid.
SetLeafObject
Declaration
HRESULT SetLeafobject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[in] BSTR Type,
[in] BSTR Delimiter,
[in,unique]SAFEARRAY(BSTR)* pProperties
)
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Notenough memory
E_INVALIDARG An argument to the function was invalid.
SetSystemObject
Declaration
HRESULT SetSystemObject(
[in] BSTR ServerClsIdString,
[in,unique]SAFEARRAY(BSTR)* pProperties
)
SetTopicObject
Declaration
HRESULT SetTopicObject(
[in] BSTR ServerClsIdString,
[in] BSTR Name,
[in] BSTR Parent,
[in] BSTR Type,
[in] LONG UpdateInterval,
[in,unique]SAFEARRAY(BSTR)* pProperties
)
Parameters
Name name of the topic
Parent fully qualified name
Return Value
S_OK The operation succeeded.
E_FAIL The operation failed.
E_OUTOFMEMORY Not enough memory
E_INvALIDARG An argument to the function was invalid.
SwitchToCfgSet
Declaration
HRESULT SwitchToCfgSet(
[in] BSTR ServerClsIdString,
[in] BSTR pConfigSet
)
IIOSrCfgrules接口520定义了一组方法,用于通过远程基础结构250从诸如规则270这样的存储区抽取配置规则。这一接口隔离了调用程序与在特定的物理装置上以特定的位置和形式抽取或存储数据的细节。
Declaration
[
object,
dual,
uuid(52088D9A-DED4-11D3-83F2-00A024A866AD),
helpstring("IIOSrvCfgRules Interface"),
pointer_default(unique)
]
/*
This interface provides a way to extract the configuration rules from the rules storage area
*/
interface IIoSrvCfgRules:IDispatch
{
HRESULT GetCfgRuleFileName(
[in] BSTR ServerClsIdString,
[out] BSTR* pFileName
);
HRESULT SetCfgRuleFileName(
[in] BSTR ServerClsIdString,
[in] BSTR pFileName
);
HRESULT GetHostClsIds(
[in] BSTR ServerClstdString,
[out] BSTR* pPackageClsIdString,
[out] BSTR* pEditorHostClsIdString
),
HRESULT GetRulesForObjectType(
[in] BSTR ServerClsIdString,
[in] BSTR ObjectType,
[out] BSTR* pEditorClsIdString,
[out] BSTR* pPackageClsIdString,
[out] BSTR* pDelimiter
);
HRESULT GetCfgChildRulesForObjectType(
[in] BSTR ServerClsIdString,
[in] BSTR Type,
[out] SAFEARRAY(BSTR)* ChildTypes,
[out] SAFEARRAY(LONG)* ChildTypesMaxOccurs,
[out] LONG* pOptions
);
HRESULT GetCfgPropertyRulesForObjectType(
[in] BSTR ServerClsIdString,
[in] BSTR Type,
[out] SAFEARRAY(BSTR)* PropertyName,
[out] SAFEARRAY(LONG)* PropertyType,
[out] SAFEARRAY(VARIANT)* DefaultValue,
[out] SAFEARRAY(VARIANT)* PropertyMin,
[out] SAFEARRAY(vARIANT)* PropertyMax,
[out] SAFEARRAY(BSTR)* PropertyEditHeader,
[out] SAFEARRAY(BSTR)* PropertyEditUnit,
[out] SAFEARRAY(BSTR)* PropertyEditHelp,
[out] SAFEARRAy(LONG)* PropertyAccessRights
);
}
Operations
GetCfgChildRulesForObjectType
Declaration
HRESULT GetCfgChildRulesForObjectType(
[in] BSTR ServerClsIdString,
[in] BSTR Type,
[out] SAFEARRAY(BSTR)* ChildTypes,
[out] SAFEARRAY(LONG)* ChildTypesMaxOccurs,
[out] LONG* pOptions
)
Parameters
ServerClsIdString server clsid.
Type type name-if rules for the root are to be
retrieved pass empty string:
ChildTypes Get the array of possible child types.The
configuration snap-in displays these types as
choices to the user to create child objects
ChildTypesMaxOccurs
Number of maximum occurences of the corresponding
child object type.
pOptions List of bit-optionsin returned DWORD currently 3
bits are defined:
注释
获得用于对象类型的子规则。规则是基于用户类型的。这意思是说,相同用户类型的对象具有相同的规则集。
GetCfgPropertyRulesForObjectType
Declaration
HRESULT GetCfgPropertyRulesForObjectType(
[in] BSTR ServerClsIdString,
[in] BSTR Type,
[out] SAFEARRAY(BSTR)* PropertyName,
[out] SAFEARRAY(LONG)* PropertyType,
[out] SAFEARRAY(VARIANT)* DefaultValue,
[out] SAFEARRAY(VARIANT)* PropertyMin,
[out] SAFEARRAY(VARIANT)* PropertyMax,
[out] SAFEARRAY(BSTR)* PropertyEditHeader,
[out] SAFEARRAY(BSTR)* PropertyEditUnit,
[out] SAFEARRAY(BSTR)* PropertyEdi tHelp,
[out] SAFEARRAY(LONG)* PropertyAccessRights
)
Parameters
ServerClsIdString
server clsid.
Type type name-ifrules for the root are to be
retrieved pass empty string:
PropertyName Array of unique property names.The
configuration snap-in will display an edit field
for each property.
PropertyType Array of ptoperty types.The configuration snap-
in uses this type to perform validation on user
input.
DefaultValue Array of property default values.The
configuration snap-in uses this value to
initialize user input values.Any configuration
data client uses this as the default value if
not present.In the case of VARIANT_EMPTY there
is no default value.
PropertyMin Artay of minimum property values.The
configuration snap-in uses this value to
validate user input values.In case of type
STRING′this represents the minimum number of
(UNICODE)characters.
PropertyMax Array of maximum property values.The
configuration snap-in usesthis value to
validate user input values.In case of type
STRING′this represents the maximum number of
(UNICODE)characters.
PropertyEditHeader Array of property edit headers.The
configuration snap-in uses this value to
precede the edit field for user input.
PropertyEditUnit Array of property edit units.The configuration
snap-in uses this string to be diplayed after
the edit field for user input.
PropertyEditHelp Array of property edit help strings.The
configuration snap-in uses this stringto
display an online help string on user request
for the corresponding edit field.
PropertyAccessRights Array of ptopertyedit lock flags.The
configuration snap-in uses this value to
determine the accessrights on this property.
注释
获得用于对象类型的性质规则。规则是基于用户类型的。这意思是说,相同用户类型的对象具有相同的规则集。
GetCfgRuleFileName
Declaration
HRESULT GetCfgRuleFileName(
[in] BSTR ServerClsIdString,
[out] BSTR* pFileName
)
Pararmeters
ServerClslaString DAS server class ID
pFileName pointer to file name
注释
检索服务器的现用配置文件的cfg规则文件名。配置咬接通常不需要知道这一文件名。这只是用于通知的目的。
GetHostClsIds
Declaration
HRESULT GetHostClsIds(
[in]BSTR ServerClsIdString,
[out]BSTR* pPackageClsIdString,
[out]BSTR* pEditorHostClsIdString
)
Parameters
ServerClsldString DAS server class ID
PPackageClsIdString Clsid of the package
PEditorHostClsldString Clsid of the editor host
注释
检索用于给定对象类型的编辑器DisId
GetRulesForObjectType
Declaration
HRESULT GetRulesForObjectType(
[in]BSTR ServerClsIdString,
[in]BSTR ObjectType,
[out]BSTR* pEditorClsIdString,
[out]BSTR* pPackageClsIdString,
[out]BSTR* pDelimiter
)
Parameters
ServerClsIdString DAS server class ID
ObjectType object type(value of the type attribute of the
corresponding object in the configuration file)
pEditorClsIdString Clsid of the editor ActiveX responsible for
editing all object properties
pPackageClsIaString Clsid of the package
pDelimiter Delimiter of the type(post delimiter)
注释
检索用于给定对象类型的编辑器DisId
SetCfgRuleFileName
Declaration
HRESULT SetCfgRuleFileName(
[in] BSTR ServerClsIdString,
[in] BSTR pFileName
)
Parameters
ServerClsIdString DAS server class ID
pFileNane file name
注释
设置规则文件名
现转向图7,其中一顺序图描绘了当结点编辑器打开并由用户选择了一特定的数据访问服务器时所执行的一组步骤。在步骤600期间,用户通过MMC启动DAS控制台客户。对此的响应是DASCC在步骤602与位于支持DAS的每一结点上的DAS代理通信,以便列举网络上所有DAS。然后,在步骤604用户选择用于配置的被列举DAS之一,并在步骤606和608,DASCC发出请求以便生成程序包主机210对象的实例及编辑器主机230的实例。如果规定了结点程序包或结点编辑器,则这些对象也被例示。
在生成以上配置组件之后,在步骤610 DASCC向程序包主机210发出请求,对于包含由用户在步骤604期间所选的数据访问服务器请求一组结点配置参数。在步骤612程序包主机210通过CIOSrvCfgPersist接口510把阅读请求传送给远程基础结构。远程基础结构调用配置存储器280以便在步骤614期间阅读与所选DAS相关的现有的参数,并在步骤616期间调用规则存储器2270以便阅读任何与所选DAS相关的适用的规则。然后所检索的配置参数和规则被返回调用程序包主机210。
在步骤618期间,DAS控制台在寻求生成的编辑器主机230上发出“init”调用。在步骤620与622期间,编辑器主机230对此响应而生成由的访问的结点规定的结点编辑器240定制面板的实例,并然后把“init”调用转发给结点编辑器240。在步骤624,结点编辑器240调用程序包主机210,以便获得对每一由结点(及任何相关规则)规定的参数值,并然后在步骤626期间根据相关规则通过定制面板显示配置参数。然后,用户请求结点编辑器240与对所选DAS配置会话相关改变结点参数。
现转向图8,其中一顺序图描绘了一系列为编辑现有配置所执行的示例性步骤,并具体在对所选的数据访问服务器规定的配置分层结构中添加了一新的结点。在步骤700期间,用户选择父结点(类型),以便通过向DASCC 200传送一适当的用户接口请求添加到一配置。在步骤702期间DASCC 200对此的响应而向程序包主机210发出一请求,以便获得与所选结点(包含任何子结点)类型相关的配置参数和规则的一列表。在步骤704,程序包主机210从CIOSrvCfgPersist对象500请求对于所选结点的所有规则。然后,CIOSrvCfgPersist对象500把配置规则请求传送给规则存储器270。然后,在步骤708程序包主机210向CIOSrvCfgPersist对象500发出请求以便对于所选结点阅读子结点参数。在步骤710对此响应请求被传送给配置存储器280。在接收适当的规则和参数时,程序包主机向接收的参数施加配置规则以生成适当的父结点结构。
然后在步骤714,用户向DASCC 200发出接口命令以便添加寻求所选类型的新的结点。然后在步骤716,DASCC 200向程序包主机210发出请求,以便向配置分层结构内的所选/标识的子结点添加一新的结点。在步骤718,程序包主机210调用CIOSrvCfgPersist对象500,以便对当前所选配置向存储区添加一新的结点。然后在步骤720,CIOSrvCfgPersist对象500向配置存储器280发出存储生成的新结点的请求。
现在转向图9,其中一顺序图描绘了使用先前描绘的分布式配置组件向一配置保存变化的步骤。在步骤800期间响应用户通过在编辑器主机230的用户界面上选择“施加”按钮发出保存请求。在步骤802期间编辑器主机230对此响应传送一调用(结点类型专用面板)以便向结点编辑器240保存配置的变化。在步骤804期间,结点编辑器240对此响应使用一请求调用程序包主机210保存结点参数新的值。程序包主机210在步骤806期间,可能参照定制结点程序包220,核实所请求的结点变化信息。在步骤808期间程序包主机210调用CIOSrvCfgPersist对象500请求保存对一组规定的结点参数操作。CIOSrvCfgPersist对象500在步骤810通过在配置存储器280中存储改变的参数值执行保存请求。在新的配置信息存放在配置存储器280之后,CIOSrvCfgPersist对象500确定受到影响的DAS当前是否在运行。在DAS运行的情形下,在步骤812CIOSrvCfgPersist对象500把该变化(包括规定被改变的结点)通知给对应的DAS。在步骤812实施的该通知机制便于运行数据访问服务器的热配置。对此响应,服务器从配置存储器280阅读新的值,并在这种改变不破坏正在进行的DAS的操作的一时间点更新其配置。
以下是在程序包主机210和结点编辑器240的一示例性实现中使用的一组类型定义。
Type Definitions:
ATTR_PROPERTYIDS
Declaration
enum
{
_PROPERTY_INVALID_PROPID_=0,
_PROPERTY_NAME_,
_PROPERTY_TYPE_,
_PROPERTY_VALUE_,
_PROPERTY_MIN_,
_PROPERTY_MAX_,
_PROPERTY_HEADER_,
_PROPERTY_EUNITS_,
_PROPERTY_HELP_,
_PROPERTY_ACCESSRIGHTS_
}
Description
Specifies the Attribute properties
Elements
_PROPERTY_VALUE_
_PROPERTY_HEADER_
_PROPERTY_MAX_
_PROPERTY_MIN_
_ROPERTY_INVALID_PROPID_ Zero is reserved for invalid PropID
_PROPERTY_TYPE_
_PROPERTY_HELP_
_PROPERTY_CCESSRIGHTS_
_PROPERTY_EUNITS_
_PROPERTY_NAME_
COMMIT_ENUM
Declaration
enum {
COMMIT_INVALID_HANDLE,
COMMIT_FAIL,
COMMIT_REMOTE_FAIL
}
Description
Specifies the options for status of Commit operation
Elements
COMMIT_INVALID_HANDLE
COMMIT_REMOTE_FAIL
COMMIT_OK
COMMIT_FAIL
IOSRVPROPERTY
Declaration
typedef struct tagIOSRVPROPERTY {
[string] BSTRsz Key,
[string] BSTR szroperty;}IOSRVPROPERTY
Descriptlon
Describes a parameter′s name and value.
PROPERTYACCESSRIGHT
Declaration
typedef enum tagPROPERTYACCESSRIGHTS{
PROPERTYACCESSRIGHT_ALL=0,
PROPERTYACCESSRIGHT_LOCKED=1}PROPERTYACCESSRIGHT
Description
Describes user access rights for a property
SHAPE_INFO_ENUM
Declaratlon
enum {
SHAPE_INFO_ATTRIBUTES=1,
SHAPE_INFO_NODES,
SHAPE_INFO_TOPICS,
SHAPE_INFO_LEAVES
}
Description
Specifies the Shape information options
Elements
SHAPE_INFO_ATTRIBU
TES
SHAPE_INFO_TOPICS
SHAPE_INFO_LEAVES
SHAPE_INFO_NODES
以下是构成远程配置规范的暂留区第一部分的规则文件270的一例。一组标签说明先于实际的例子。
关键字 | XML属性 | 说明 |
<COFIGURATIONRULES> | NAMEPACKAGEHOSTIDEDITORHOSTID | 用于配置规则的根关键字(DAS相关数据只在这根关键字内)。这根关键字的存在潜在地允许附加的数据被存储在平行根关键字下的相同的文件中。 |
<HIERARCHYNODE> | TYPEEDITORIDPACKAGEIDDELIMITER | 类型“type”对象的规则关键字(与DAS对象类型相关)。需要TYPE(服务器特定类)和NAME-DELIMITER是可选的(如果不存在默认为.“”) |
<CHILDRULES> | ENABLEDEVICEGROUPENABLEDEVICEITEMSENABLESYSTEMITEMS | 对于类型“MANE”对象的CHILDRULES的子-关键字。EVICEGROUPS,EVICEITEMS,SYSTEMITEMS是布尔标志,允许规定的对象在类型NAME”这一分支对象上 |
<“user types”> | MAXOCCURENCESMINOCCURENCES | 对于用于在子规则下对象的用户类型关键字 |
<PROPERTYRULES> | 用于性质/编辑器元素的关键字 | |
<PROPERTYTYPE> | 用于在性质规则下变异性质类型的关键字 | |
<DEFAULTVALUE> | 用于在性质规则下性质默认值的关键字 | |
<PROPERTYMIN> | 用于在性质规则下性质最小值的关键字 |
<PROPERTYMAX> | 用于在性质规则下性质最大值的关键字 | |
<PROPERTYEDITHEADER> | 用于在性质规则下性质编辑字段头部的关键字 | |
<PROPERTYUNIT> | 用于在性质规则下性质编辑字段单元的关键字 | |
<PROPERTYHELP> | 用于在性质规则下性质编辑字段帮助的关键字 |
?xml version="1.0"encoding="TF-8"?>
<CONFIGURATIONRULESNAME="DAS ABTCP"PACKAGEHOSTID="{7F5B8DEE-AB78-11D4-93E4-
00B0D0201D61}"EDITORHOSTID="{5C9AF1AA-AEC8-11D4-93E6-00B0D0201D61}">
<HIERARCHYNODE TYPE="$ROOT$">
<CHILDRULES ENABLEDEVICEGROUPS="1"ENABLEDEVICEITEMS="0"
ENABLESYSTEMITEMS="1">
<PORT_TCPIP MAXOCCURRENCES="1"/>
</CHILDRULES>
<PROPERTYRULES>
<UpdateInterval>
<PROPERTYTYPE>VT_I4</PROPERTYTYPE>
<DEFAULTVALUE>1000</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>100000</PROPERTYMAX>
<PROPERTYEDITUNIT>ms</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Update interval of default topics for hierarchies without overriding
configuration</PROPERTYEDITHELP>
</UpdateInterval>
<SlowP.Interval>
<PROPERTYTYPE>VT_I4</PROPERTYTYPE>
<DEFAULTVALUE>10000</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>100000</PROPERTYMAX>
<PROPERTYEDITUNIT>ms</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Update interval of topics for hierarchies in slow poll
mode</PROPERTYEDITHELP>
</SlowPollInterval>
<CaseSensitive>
<PROPERTYTYPE>VT_I4</PROPERTYTYPE>
<DEFAULTVALUE>0</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITUNIT>T/F</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>TRUE meains case-sensitive Device Group and Item ID
names</PROPERTYEDITHELP>
</CaseSensitive>
<DefaultPokeMode>
<PROPERTYTYPE>VT_I4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERYMIN>
<PROPERTYMAX>2</PROPERTYMAX>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>0=Control,1=Transition,2=Optimized,</PROPERTYEDITHELP>
</DefaultPokeMode>
<DefaultDelimiter>
<PROPERTYTYPE>VT_BSTR</PROPERTYTYPE>
<DEFAULTVALUE>.</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>3</PROPERTYMAX>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Delimiter for hierarchies not configured</PROPERTYEDITHELP>
</DefaultDelimiter>
<SimulationMode>
<PROPERTYTYPE>VT_I4</PROPERTYTYPE>
<DEFAULTVALUE>0</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITUNIT>T/F</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>TRUE means simulate for DAServers that support
simulation</PROPERTYEDITHELP>
</SimulationMode>
<EnableSystemItems>
<PROPERTYTYPE>VT_I4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITUNIT>T/F</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>TRUE to allow system items</PROPERTYEDITHELP>
</EnableSystemItems>
<LinkTopicCache>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>0</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITUNIT>T/F</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>TRUE merges all subscription items in a single cache</PROPERTYEDITHELP>
</LinkTopicCache>
<UniqueDeviceGroup>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITUNIT>T/F</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>TRUE requires all device group names be unique</PROPERTYEDITHELP>
</UniqueDeviceGroup>
<ProtocoITimerTick>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>50</DEFAULTVALUE>
<PROPERTYMIN>10</PROPERTYMIN>
<PROPERTYMAX>100000</PROPERTYMAX>
<PROPERTYEDITUNIT>ms</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Protocol timer tick interval in milliseconds</PROPERTYEDITHELP>
</ProtocolTimerTick>
<TransactionTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>60000</DEFAULTVALUE>
<PROPERTYMIN>10</PROPERTYMIN>
<PROPERTYMAX>60000</PROPERTYMAX>
<PROPERTYEDITUNIT>ms</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Default transaction timeout for hierarchies with no
coRfiguration</PROPERTYEDITHELP>
</TransactionTimeout>
<LockConfigurationFile>
<PROPERTYTYPE>VT_BOOL</PROPERTYTYPE>
<DEFAULTVALUE>0</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITUNIT>T/F</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>TRUE for non-Magellan configurers locked out</PROPERTYEDITHELP>
</LockConfigurationFile>
<SubscriptionTransactionRatio>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>2</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>1000</PROPERTYMAX>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Subscription/Transaction ratio</PROPERTYEDITHELP>
</SubscriptionTransactionRatio>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PORT_TCPIP"EDITORID="{1B48839F-B68E-4CDA-A090-C8BD87932126}"
PACKAGEID="{7F5B8DEE-AB78-11D4-93E4-00B0D0201D61}"DELIMITER=".">
<CHILDRULES>
<PLC5_TCPIP MAXOCCURRENCES="100"/>
<SLC500_TCPIP MAXOCCURRENCES="100"/>
<PYRAMID EI MAXOCCURRENCES="100"/>
</CHILDRULES>
<PROPERTYRULES>
<MaxQueuedMsgs>
<!-Maximum number of queued messages for a topic-->
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>4</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>20</PROPERMAX>
<PROPERTYEDITHEADER>Max QueuedMsgs</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Number of Messages</PROPERTYEDITHELP>
</MaxQueuedMsgs>
<MaxSockets>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>200</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>200</PROPERTYMAX>
<PROPERTYEDITHEADER>Maximum number of sockets</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Maximum number of sockets</PROPERTYEDITHELP>
</MaxSockets>
<MaxUnsolConn>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>20</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>30</PROPERTYMAX>
<PROPERTYEDITHEADER>Maximum uumber of peer-to-peer
cornections</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Maximum number of peer-to-peer connections</PROPERTYEDITHELP>
</MaxUnsolConn>
<UnsolicjtedMsgTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>5000</DEFAULTVALUE>
<PROPERTYMIN>1000</PROPERTYMIN>
<PROPERTYMAX>10000</PROPERTYMAX>
<PROPERTYEDITHEADER>Timeout for peer-to-peer unsolicited
communication</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Timeout for peer-to-peer unsolicited communication</PROPERTYEDITHELP>
</UnsolicitedMsgTimeout>
<FlipStringBytes>
<!--Flip String Bytes-->
<PROPERTYTYPE>VT_BOOL</PROPERTYTYPE>
<DEFAULTVALUE>0</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITHEADER>Flip String Bytes</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Flip String Bytes</PROPERTYEDITHELP>
</FlipStringBytes>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PLC5_TCPIP"PACKAGEID=""EDITORID="{85B57144-49F8-47D2-B5B7-
E55CD82CFBC2}"DELIMITER=".">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<HostName>
<PROPERTYTYPE>VT_BSTR</PROPERTYTYPE>
<DEFAULTVALUE/>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>255</PROPERTYMAX>
<PROPERTYEDITHEADER>device IP address</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Device IP Host Name/Address</PROPERTYEDITHELP>
</HostName>
<DataBiockSize>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>2000</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>2000</PROPERTYMAX>
<PROPERTYEDITHEADER>Message data block size(bytes)for PLC5 on
Ethernet</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Message data block size(bytes)for PLC5 on
Ethernet</PROPERTYEDITHELP>
</DataBlockSize>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>15</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>Sec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Reply Timeout</PROPERTYEDITHELP>
</ReplyTimeout>
<SupportsPID>
<PROPERTYTYPE>VT_BOOL</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITHEADER>Support PID and StringFiles</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Support PID and String Files</PROPERTYEDITHELP>
</SupportsPID>
<UnsolClientMsg>
<PROPERTYTYPE>VT_BOOL</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>1</PROPERTYMAX>
<PROPERTYEDITHEADER>Support Unsolicited′CLIENT Messaging</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELt>Support Unsolicited′CLIENT Messaging</PROPERTYEDITHELP>
</UnsolClientMsg>
<ConnectionTimeout>
<!--Connection Timeout->
<PROPERTYTYPE>VT_U4</PROPERTYTYPE>
<DEFAULTVALUE>2000</DEFAULTVALUE>
<PROPERTYMIN>1000</PROPERTYMIN>
<PROPERTYMAX>20000</PROPERTYMAX>
<PROPERTYEDITHEADER>Connection Attempt Timeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Connection Attempt Timeout</PROPERTYEDITHELP>
</ConnectionTimeout>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="SLC500_TCPIP"PACKAGEID=""EDITORID="{63B40882-4981-41F0-868B-
CBCD508C0733}"DELIMITER=".">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<HostName>
<PROPERTYTYPE>VT_BSTR</PROPERTYTYPE>
<DEFAULTVALUE>10.32.12.36</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>255</PROPERTYMAX>
<PROPERTYEDITHEADER>device IP address</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Device IP Host Name/Address</PROPERTYEDITHELP>
</HostName>
<DataBlockSize>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>510</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>510</PROPERTYMAX>
<PROPERTYEDITHEADER>Data packet size for PLC5 on Ethernet</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Data packet size for PLC5 on Ethemet</PROPERTYEDITHELP>
</DataBlockSize>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4<PROPERTYTYPE>
<DEFAULTVALUE>15<DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>Sec<PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Reply Timeout</PROPERTYEDITHELP>
</ReplyTimeout>
<Connection Timeout>
<!--Connection Timout->
<PROPERTYTYPE>VT_U4</PROPERTYTYPE>
<DEFAULTVALUE>2000</DEFAULTVALUE>
<PROPERTYMIN>1000</PROPERTYMIN>
<PROPERTYMAX>20000</PROPERTYMAX>
<PROPERTYEDITHEADER>Connection Attempt Timeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Connection Attempt Timeout</PROPERTYEDITHELP>
</ConnectionTimeout>
</PROPERTYRULES>
</HIERtARCHYNODE>
<HIERARCHYNODE TYPE="PYRAMID_EI"EDITORID="{4D9DE9D0-48BB-489E-9CED-
5284FFA3EFED}"DELIMITER=".">
<CHILDRULES>
<PYRAMID_KA MAXOCCURRENCES="4"/>
<PYRAMID_RM MAXOCCURRENCES="1"/>
<PYRAMID PLC5250MAXOCCURRENCES="4"/>
</CHILDRULES>
<PROPERTYRULES>
<HostName>
<PROPERTYTYPE>VT_BSTR</PROPERTYTYPE>
<DEFAULTVALUE>10.32.12.36</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>255</PROPERTYMAX>
<PROPERTYEDITHEADER>device IP address</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Device IP Host Name/Address</PROPERTYEDITHELP>
</HostName>
<ConnectionTimeout>
<!--ConnectionTimout-->
<PROPERTYTYPE>VT_U4</PROPERTYTYPE>
<DEFAULTVALUE>2000</DEFAULTVALUE>
<PROPERTYMIN>1000</PROPERTYMIN>
<PROPERTYMAX>20000</PROPERTYMAX>
<PROPERTYEDITHEADER>Connection Attempt Timeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Connection Attempt Timeout</PROPERTYEDITHELP>
</ConnectionTimeout>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PYRAMID_PLC5250"PACKAGEID=""EDITORID="{A7EBCF9D-9ECE-
4DD5-B417-506ABA20855F}"DELIMITER=".">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>15</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDlTUNIT>Sec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Reply Timeout</PROPERTYEDITHELP>
</ReplyTimeout>
<DataBlockSize>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>2000</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>2000</PROPERTYMAX>
<PROPERTYEDITHEADER>Message packet size for PLC5 on Ethernet</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Message packet size for PLC5 on Ethernet</PROPERTYEDITHELP>
</DataBlockSize>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PYRAMID_RM"EDITORID=""DELIMITER=".">
<CHILDRULES>
<PORT_DHP MAXOCCURRENCES="2"/>
<PORT_DH MAXOCCURRENCES="2"/>
</CHILDRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PYRAMID_KA"EDITORID="{8A04DA4D-F6C0-4CIF-A771-
806CDA40029F}"DELIMITER=".">
<CHILDRULES>
<PORT_DHP MAXOCCURRENCES="2"/>
<PORT_DH MAXOCCURRENCES="2"/>
</CHILDRULES>
<PROPERTYRULES>
<Pushwheel>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>4</PROPERTYMAX>
<PROPERTYEDITHEADER>Push Wheel</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Push Wheel</PROPERTYEDITHELP>
</Pushwheel>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PORT_DHP"EDITORID="{2B22472C-2F98-4DlB-A211-7036FCBF9AA2}"
PACKAGEID=""DELIMITER=".">
<CHILDRULES>
<PLC5_DHP MAXOCCURRRENCES="100"/>
<SLC500_DHP MAXOCCURRENCES="100"/>
<PLC3_DHP MAXOCCURRENCES="100"/>
</CHILDRULES>
<PROPERTYRULES>
<PortNumber>
<!--Port Number-->
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>2</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>3</PROPERTYMAX>
<PROPERTYEDITHEADER>Ghannel Number</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Channel Number</PROPERTYEDITHELP>
</PortNumber>
</PROPERTYRULES>
</HIERARGHYNODE>
<HIERARCHYNODE TYPE="PORT DH"PACKAGEID=""EDITORID="{67D79FDA-4DC4-43A2-9B24-
5735C3E3B428}"DELIMITER=".">
<CHILDRULES>
<PLC2DH MAXOCCURRENCES="100"/>
</CHILDRULES>
<PROPERTYRULES>
<PortNumber>
<!--Port Number-->
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>2</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>3</PROPERTYMAX>
<PROPERTYEDITHEADER>Chanmel Number</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Channel Number</PROPERTYEDITHELP>
</PortNumber>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PLC5_DHP"EDITORID="{BF71A6EF-818F-4406-9038-60745B9A1538}"
DELIMITER="."">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<NodeAddress>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>63</PROPERTYMAX>
<PROPERTYEDITHEADER>DH+Node Nukmber</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>Octal</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Datahighway Plus Node Number</PROPERTYEDITHELP>
</NodeAddress>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>15</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>Sec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Reply Timeout</PROPERTYEDITHELP>
</ReplyTimeout>
<DataBlockSize>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>240</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>240</PROPERTYMAX>
<PROPERTYEDITHEADER>Message packet size for PLC5 on Datahiway
Plus</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Message packet size for PLC5 on Datahiway Plus</PROPERTYEDITHELP>
</DataBlockSize>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="SLC500_DHP"EDITORID="{78FF43FC-EA3B-4B37-AFA9-
D8D95CFB69A5}"DELIMITER=".">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<NodeAddress>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>63<</PROPERTYMAX>
<PROPERTYEDITHEADER>DH+Node Nukmber</PROPERTYEDITHEADER>
<PROPERTYEDITUNI>Octal</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>DatahighwayPlusNodeNumber</PROPERTYEDITHELP>
</NodeAddress>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>15</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>ReplyTimeout</PROPERTYEDITHELP>
</ReplyTimeout>
<DataBlockSize>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>204</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>204</PROPERTYMAX>
<PROPERTYEDITHEADER>Message packet size for PLC5 on Datahiway
Plus</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Message packet size for PLC5 on Datahiway Plus</PROPERTYEDITHELP>
</DataBlockSize>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODETYPE="PLC3_DHP"EDITORID="{F59F96D7-FA1D-4C9F-91F3-FABC09E00683}"
DELIMITER=".">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<NodeAddress>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>63</PROPERTYMAX>
<PROPERTYEDITHEADER>DH+Node Nukmber</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>Octal/PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Datahighway Plus Node Number</PROPERTYEDITHELP>
</NodeAddress>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>15</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDTTUNIT>
<PROPERTYEDITHELP>Reply Timeout</PROPERTYEDITHELP>
</ReplyTimeout>
<DataBlockSize>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>240</DEFAULTVALUE>
<PROPERTYMIN>2</PROPERTYMIN>
<PROPERTYMAX>240</PROPERTYMAX>
<PROPERTYEDITHEADER>Message packet size for PLC5 on Datahiway
Plus</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Message packet size for PLC5 on Datahiway Plus</PROPERTYEDITHELP>
</DataBlockSize>
</PROPERTYRULES>
</HIERARCHYNODE>
<HIERARCHYNODE TYPE="PLC2_DH"EDITORID="{9C53E368-C85A-44B1-8F7E-5EE6EE07DBED}"
DELIMITER=".">
<CHILDRULES ENABLEDEVICEGROUPS="1"/>
<PROPERTYRULES>
<NodeAddress>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>1</DEFAULTVALUE>
<PROPERTYMIN>0</PROPERTYMIN>
<PROPERTYMAX>255</PROPERTYMAX>
<PROPERTYEDITHEADER>DH Node Nukmber</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>Octal</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Datahighway Node Number</PROPERTYEDITHELP>
</NodeAddress>
<ReplyTimeout>
<PROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>15</DEFAULTVALUE>
<PROPERTYMIN>1</PROPERTYMIN>
<PROPERTYMAX>300</PROPERTYMAX>
<PROPERTYEDITHEADER>ReplyTimeout</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT>MSec</PROPERTYEDITUNIT>
<PROPERTYEDITHELP>Reply Timeout</PROPERTYEDITHELP>
</ReplyTimeout>
<DataBlockSize>
<ROPERTYTYPE>VT_UI4</PROPERTYTYPE>
<DEFAULTVALUE>240</DEFAULTVALUE>
<PROPERTYMIN>100</PROPERTYMIN>
<PROPERTYMAX>240</PROPERTYMAX>
<PROPERTYEDITHEADER>Message packet size for PLC5 on Datahiway
Plus</PROPERTYEDITHEADER>
<PROPERTYEDITUNIT/>
<PROPERTYEDITHELP>Message packet size for PLC5 on Datahiway Plus</PROPERTYEDITHELP>
</DataBlockSize>
</PROPERTYRULES>
</HIERARCHYNODE>
</CONFIGURATIONRULES>
以下是构成远程配置规范的暂留区第二部分的配置文件280一例。
关键字 | XML属性 | 说明 |
<DASConfiguration> | 用于配置的根关键字(DAS相关数据只在这根关键字内)。这根关键字的存在潜在地允许附加的(用户-)数据被存储在平行根关键字下的相同的文件中。 | |
<DeviceNode> | TYPENAMEDELIMITER | 分层级(与DAS对象类型相关)的关键字。需要TYPE(服务器特定类)和NAME-DELIMITER是可选的(如果不存在默认为.“”) |
<ItemHint> | TYPEDELIMITER | 对于预配置项或项提示的-关键字。需要TYPE(服务器特定类)和NAME |
<DeviceGroup> | TYPENAMEUPDATEINTERVAL | 对于OPC访问通路/DDE/SL主题(与装置组相关)关键字。需要NAME和UPDATEINTERVAL-TYPE(服务器特定类)是可选的 |
<Data> | TYPENAME | 用于DAServer整体(用户)设置的关键字。需要TYPE(服务器特定类)和NAME |
<System> | 用于DAServer整体系统设置的关键字。 |
<?xml version="1.0"encoding="UTF-8"?>
<DASConfiguration NAME="Wonderware ABTCP(non-official)"DELIMITER=".">
<!--Wonderware AB TCP/IP Server-->
<created>03.29.2000 16:40</created>
<user>Clement Lie</user>
<DeviceNodeTYPE="PORT_TCPIP"NAME=""TCP"DELIMITER=".">
<!--TCP/IP Port for ABTCP-->
<MaxQueuedMsgs>3</MaxQueuedMsgs>
<MaxSockets>200</MaxSockets>
<MaxUnsolConn>20</MaxUnsolConn>
<UnsolicitedMsgTimeout>5000</UnsolicitedMsgTimeout>
<DeviceNode TYPE="PYRAMID_EI"NAME="EI"DELIMITER=".">
<!--Ethemet Interface Module of Pyramid Integrator-->
<HostName>P5250_1</HostName>
<ConnectionTimeout>2000</ConnectionTimeout>
<DeviceNode TYPE="PYRAMID_PLC5250"NAME="P5250_1"DELIMITER=".">
<DataBlockSize>2000</DataBlockSize>
<ReplyTimeout>15</ReplyTimeout>
<DeviceGroup NAME="P5250_1_Fast"UPDATEINTERVAL="100"/>
<DeviceGroup NAME="P5250_1"UPDATEINTERVAL="1000"/>
<DeviceGroup NAME="P5250_1_Slow"UPDATEINTERVAL="5000"/>
</DeviceNode>
<DeviceNode TYPE="PYRAMID_RM"NAME="RM"DELIMTTER=".">
<DeviceNode TYPE="PORT_DHP"NAME="CH2"DELIMITER=".">
<PortNumber>2</PortNumber>
<DeviceNode TYPE="PLC5_DHP"NAME="P511_1"DELIMITER=".">
<NodeAddress>6<NodeAddress>
<DataBlockSize>240</DataBlockSize>
<ReplyTimeout>15</ReplyTimeout>
<DeviceGroup NAME="P511_1"UPDATEINTERVAL="1000"/>
<DeviceGroup NAME="P511_1_Fast"UPDATEINTERVAL="100"/>
<DeviceGroup NAME="P511_1_Slow"UPDATEINTERVAL="5000"/>
</DevviceNode>
</DeviceNode>
<DeviceNode TYPE="PORT_DHP"NAME="CH3"DELIMITER=".">
<PortNumber>3</PortNumber>
<DeviceNode NAME=″SLC504_2"TYPE="SLC500_DHP"DELIMIITER=".">
<NodeAddress>24</NodeAddress>
<ReplyTimeout>15</ReplyTimeout
<DataBlockSize>204</DataBlockSize>
</DeviceNode>
<DeviceNode NAME="P520E_2"TYPE="PLC5_DHP"DELIMITER=".">
<NodeAddress>7</NodeAddress>
<ReplyTimeout>15</ReplyTimeout>
<DataBlockSize>240</DataBlockSize>
</DeviceNode>
</DeviceNode>
<DeviceNode>
<DeviceNode TYPE="PYRAMID_KA"NAME="KA"DELIMITER=".">
<Pushwheel>1</Pushwheel>
<DeviceNode TYPE="PORT_DHP"NAME="CH2"DELIMITER=".">
<PortNumber>2</PortNumber>
<DeviceNode TYPE="PLC3_DHP"NAME="P3101"DELIMITER=".″>
<NodeAddress>9</NodeAddress>
<DataBlockSize>240</DataBlockSize>
<ReplyTimeout>15</ReplyTimeout>
<DeviceGroup NAME="PLC3"UPDATEINTERVAL=″1000″/>
<DeviceaGroup NAME="PLC3_Fast"UPDATEINTERVAL=″100″/>
<DeviceaGroup NAME="PLC3_Slow"UPDATEINTERVAL="5000"/>
<DeviceNode>
<DeviceNode NAME="P520C_1"TYPE="PLC5_DHP"DELIMITER=".">
<NodeAddress>52</NodeAddress>
<ReplyTimeout>15</ReplyTimeout>
<DataBlockSize>240</DataBlockSize>
<DeviceNode>
<DeviceNode NAME="P580E_1"TYPE="PLC5_DHP"DELIMITER=".">
<NodeAddress>5</NodeAddress>
<ReplyTimeout>15</ReplyTimeout>
<DataBlockSize>240</DataBlockSize>
</DeviceNode>
<DeviceNode NAME="P520E_2"TYPE="PLC5_DHP"DELIMITER=".">
<NodeAddress>7</NodeAddress>
<ReplyTimeout>15</ReplyTimeout>
<DataBiockSize>240</DataBlockSize>
</DeviceNode>
</DeviceNode>
<DeviceNode TYPE="PORT_DH"NAME="CH3"DELIMITER=".">
<PortNumber>2</PortNumber>
<DeviceNode TYPE="PLC2_DH"NAME="P216_1"DELIMITER=".">
<NodeAddress>83</NodeAddress>
<DataBlockSize>100</DataBlockSize>
<ReplyTimeout>15</ReplyTimeout>
</DeviceNode>
</DeviceNode>
</DevfviceNode>
</DeviceNode>
<DeviceNode TYPE="PLC5_TCPIP"NAME="P520E_2"DELIMITER=".">
<!--PLC5 on TCP/IP-->
<HostName>P520E_2</HostName>
<ReplyTimeout<300</ReplyTimeout>
<DataBlockSize>1000</DataBlockSize>
<SupportsPID>1</SupportsPID>
<UnsolClientMsg>1</UnsolClientMsg>
<ConnectionTimeout>2000</ConnectionTimeout>
<DeviceGroup NAME="P520E_2"UPDATEINTERVAL="1000"/>
<DeviceGroup NAME="P520E_2_Slow"UPDATEINTERVAL="5000"/>
<DeviceGroup NAME="P520E_2_Fast"UPDATEINTERVAL="100"/>
<DeviceGroup NAME="P520E_2Unsol"UPDATEINTERVAL="10000000000"/>
</DeviceNode>
<DeviceNode TYPE="SLC500_TCPIP"NAME="SLC505_2"DELIMITER=".">
<HostName>SLC505_2</HostName>
<ReplyTimeout>10</ReplyTimeout>
<DataBlockSize>510</DataBlockSize>
<ConnectionTimeout>2000</ConnectionTimeout>
<DeviceGroup NAME="SLC505_1_Fast"UPDATEINTERVAL="100"/>
<DeviceGroup NAME="SLC505_1"UPDATEINTERVAL="1000"/>
<DeviceGroup NAME="SLC505_1_Slow"UPDATEINTERVAL="5000"/>
</DeviceNode>
<DeviceNode NAME="MyPLC5"TYPE="PLC5_TCPIP"DELIMITER=".">
<HostName>10.32.12.36</HostName>
<DataBlockSize>2000</DataBlockSize>
<ReplyTimeout>3</ReplyTimeout>
<SupportsPID>1</SupportsPID>
<UnsolClientvsg>1</UnsolClientMsg>
<ConnectionTimeout>2000</ConnectionTimeout>
<DeviceGroup NAME="Fast PLC5"TYPE="Topic"UPDATEINTERVAL="20"/>
<DeviceGroup NAME="Medium PLC5"TYPE="Topic"UPDATEINTERVAL="1000"/>
<DeviceGroup NAME="Slow PLC5"TYPE="Topic"UPDATEINTERVAL="10000"/>
<Deviceltem TYPE=""NAME="N7:0"/>
<Deviceltem TYPE=""NAME="N7:2"/>
<Deviceltem TYPE=""NAME="N7:3"/>
<Deviceltem TYPE=""NAME="N7:11"/>
<DeviceItem TYPE=""NAME="N7:14"/>
<DeviceItem TYPE=""NAME="N17:0"/>
<DeviceItem TYPE=""NAME="N17:1"/>
<DeviceItem TYPE=""NAME="N17:2"/>
<DeviceItem TYPE=""NAME="N17:3"/>
<DeviceItem TYPE=""NAME="N17:50"/>
<DeviceItem TYPE=""NAME="N17"99"/>
<DeviceItem TYPE=""NAME="N27:0"/>
<DeviceItem TYPE=""NAME="N27:1"/>
<DeviceItem TYPE=""NAME="N27:2"/>
<DeviceItem TYPE=""NAME="N27:3"/>
<DeviceItem TYPE=""NAME="N27:50"/>
<DeviceItem TYPE=""NAME="N27:99"/>
<DeviceItem TYPE=""NAME="B3:0/8"/>
<DeviceItem TYPE=""NAME="B13:0/180"/>
<DeviceItem TYPE=""NAME="A9:0-8"/>
<DeviceItem TYPE=""NAME="F8:2"/>
<DeviceItem TYPE=""NAME="F8:12"/>
<DeviceItem TYPE=""NAME="ST10:0"/>
</DeviceNode>
<DeviceNode NAME="MyPLC37"TYPE="PLC5_TCPIP"DELIMITER=".">
<HostName>10.32.12.37</HostName>
<DataBlockSize>2000</DataBlockSize>
<ReplyTimeout>3</ReplyTimeout>
<SupportsPID>1</SupportsPID>
<UnsolClientMsg>1</UnsolClientMsg>
<ConnectionTimeout>2000</ConnectionTimeout>
<DeviceGroup NAME="Fast PLC37"TYPE="Topic"UPDATEINTERVAL="20"/>
<DeviceGrouP NAME="Medium PLC37"TYPE="Topic"UPDATEINTERVAL="1000"/>
<DeviceGroup NAME="Slow PLC37"TYPE="Topic"UPDATEINTERVAL="10000"/>
<ItemHint TYPE=""NAME="N7:0-4"/>
<ItemHint TYPE=""NAME="F8:0-3"/>
<ItemHint TYPE=""NAME="BT9:0-3"/>
<ItemHint TYPE=""NAME="N10:0-74"/>
<ItemHint TYPE=""NAME="B11:0-0"/>
<ItemHint TYPE=""NAME="PD12:0-0"/>
<ItemHint TYPE=""NAME="N13:0-3"/>
<ItemHint TYPE=""NAME="N14:0-4"/>
<ItemHint TYPE=""NAME="N15:0-4"/>
</DeviceNode>
</DeviceNode>
<System NAME="SYSTEM"TYPE="SYSTEM">
<UpdateInterval>1000</UpdateInterval>
<SlowPollInterval>10000</SlowPollInterval>
<CaseSensitive>0</CaseSensitive>
<DefaultPokeMode>0</DefaultPokeMode>
<DefaultDelimiter>"."</DefaultDelimiter>
<SimulationMode>0</SimulationMode>
<EnableSystcmItems>1</EnableSystemItems>
<LinkTopicCache>0</LinkTopicCache>
<UniqueDeviceGroup>1</UniqueDeviceGroup>
<ProtocolTimerTick>60</ProtocolTimerTick>
<TransactionTimeout>2000</TransactionTimeout>
<LockConfigurationFile>0</LockConfigurationFile>
<SubscriptionTransactionRatio>2</SubscriptionTransactionRatio>
</System>
</DASConfiguration>
本发明的示例性实施例及其一定的变形,已经在附图中及伴随的书面说明中提供。但并不是要把本发明限于这些实施例。本发明是要在以下这里所附权利要求定义的这一公开和发明所允许的最充分的程度上,函盖公开的各实施例以及其它属于本发明的范围和精神的实施例。
Claims (8)
1.一种分布式配置系统,便于过程控制数据访问服务器的远程配置,该分布式配置系统包括:
位于控制台的配置编辑器;
包括当前服务器配置说明的配置存储器;
规则数据库,用于存储一组与每一通过该配置系统可配置的数据访问服务器相关的配置规则,其中该组配置规则提供了到配置存储器内信息的导向,规定了对一些过程控制数据访问服务器的配置;以及
服务器代理,位于远离控制台的计算结点,并包含可配置的过程控制数据访问服务器,该服务器代理包括可执行程序,用于通知配置编辑器可配置过程控制数据访问服务器的存在,从而便于在配置编辑器与可配置过程控制数据访问服务器之间建立配置接口。
2.权利要求1的分布式配置系统,其中该组配置规则规定了配置分层级。
3.权利要求2的分布式配置系统,其中该组配置规则规定了与配置分层级的一些特定配置结点相关的性质。
4.权利要求1的分布式配置系统,还包括一种可执行的通知机制,这种机制建立到一已经改变了配置参数值的运行的数据访问服务器的连接,并通知该运行的数据访问服务器对其配置的改变。
5.权利要求1的分布式配置系统,还包括一用户编辑器主机,提供一接口支持编辑器接口面板,接口面板是对过程控制数据访问服务器配置的特定组件类型规定的。
6.权利要求1的分布式配置系统,其中,所述配置存储器和规则数据库在所述可配置的过程控制数据访问服务器所处的计算节点上进行维护。
7.权利要求1的分布式配置系统,其中,所述服务器代理支持关于位于计算节点上的多个数据访问服务器向配置编辑器进行通知。
8.权利要求1的分布式配置系统,其中,所述配置编辑器位于处于过程控制系统的管理级的计算节点上。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US23273100P | 2000-09-15 | 2000-09-15 | |
US60/232,731 | 2000-09-15 |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1504041A CN1504041A (zh) | 2004-06-09 |
CN100521711C true CN100521711C (zh) | 2009-07-29 |
Family
ID=22874318
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB018189687A Expired - Lifetime CN100521711C (zh) | 2000-09-15 | 2001-09-14 | 用于过程数据访问服务器的远程配置的系统 |
CNB018188648A Expired - Lifetime CN1261892C (zh) | 2000-09-15 | 2001-09-14 | 支持多个客户数据交换协议的工业过程控制数据访问服务器 |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB018188648A Expired - Lifetime CN1261892C (zh) | 2000-09-15 | 2001-09-14 | 支持多个客户数据交换协议的工业过程控制数据访问服务器 |
Country Status (5)
Country | Link |
---|---|
US (4) | US7644120B2 (zh) |
EP (3) | EP1327348B1 (zh) |
CN (2) | CN100521711C (zh) |
AU (5) | AU9268901A (zh) |
WO (3) | WO2002023875A1 (zh) |
Families Citing this family (165)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6826590B1 (en) * | 1996-08-23 | 2004-11-30 | Fieldbus Foundation | Block-oriented control system on high speed ethernet |
US7146230B2 (en) * | 1996-08-23 | 2006-12-05 | Fieldbus Foundation | Integrated fieldbus data server architecture |
US20040194101A1 (en) * | 1997-08-21 | 2004-09-30 | Glanzer David A. | Flexible function blocks |
US6999824B2 (en) * | 1997-08-21 | 2006-02-14 | Fieldbus Foundation | System and method for implementing safety instrumented systems in a fieldbus architecture |
US6928336B2 (en) * | 2001-02-12 | 2005-08-09 | The Stanley Works | System and architecture for providing a modular intelligent assist system |
US8073967B2 (en) | 2002-04-15 | 2011-12-06 | Fisher-Rosemount Systems, Inc. | Web services-based communications for use with process control systems |
JP2002288229A (ja) * | 2001-03-23 | 2002-10-04 | Hitachi Ltd | マルチレベル構成図情報の表示方法およびシステム |
US6832366B2 (en) * | 2001-05-17 | 2004-12-14 | Simdesk Technologies, Inc. | Application generator |
CA2349083A1 (en) * | 2001-05-30 | 2002-11-30 | Ibm Canada Limited-Ibm Canada Limitee | Server configuration tool |
US7016751B2 (en) * | 2001-07-13 | 2006-03-21 | Helix Technology Corporation | Vacuum system central control information server |
US7251248B2 (en) | 2001-07-31 | 2007-07-31 | Bridgeworks Ltd. | Connection device |
GB0118646D0 (en) * | 2001-07-31 | 2001-09-19 | Digital Interfaces Ltd | A connection device |
SE519905C2 (sv) * | 2001-10-05 | 2003-04-22 | Abb Ab | Dataåtkomstmetod för ett styrsystem |
US7225193B2 (en) * | 2001-12-21 | 2007-05-29 | Honeywell International Inc. | Method and apparatus for retrieving event data related to an activity |
AU2003303102A1 (en) * | 2002-01-18 | 2004-08-23 | Idetic, Inc. | Method and system of performing transactions using shared resources and different applications |
US7032014B2 (en) * | 2002-01-18 | 2006-04-18 | Sun Microsystems, Inc. | Service management system for configuration information |
US7246360B2 (en) * | 2002-02-07 | 2007-07-17 | Mobitv, Inc. | Plug-in API for protocol and payload transformation |
EP1343271B1 (en) * | 2002-03-08 | 2005-08-10 | Sun Microsystems, Inc. | Method and apparatus for providing configuration data |
EP1483781A4 (en) * | 2002-03-12 | 2012-04-25 | Ils Technology Inc | DIAGNOSTIC SYSTEM AND METHOD FOR INTEGRATED REMOTE TOOL ACCESS, COLLECTION AND DATA CONTROL |
US20030204588A1 (en) * | 2002-04-30 | 2003-10-30 | International Business Machines Corporation | System for monitoring process performance and generating diagnostic recommendations |
US7363543B2 (en) * | 2002-04-30 | 2008-04-22 | International Business Machines Corporation | Method and apparatus for generating diagnostic recommendations for enhancing process performance |
US7599999B1 (en) * | 2002-05-21 | 2009-10-06 | Rockwell Automation Technologies, Inc. | System and methodology that facilitates client and server data exchange in a distributed industrial automation environment |
FI113121B (fi) * | 2002-05-30 | 2004-02-27 | Metso Automation Oy | Järjestelmä, tietoliikenneverkko ja menetelmä tietojen lähettämiseksi |
US6950931B2 (en) * | 2002-05-30 | 2005-09-27 | International Business Machines Corporation | Server configuration using profile templates |
US20040003007A1 (en) * | 2002-06-28 | 2004-01-01 | Prall John M. | Windows management instrument synchronized repository provider |
US20040006652A1 (en) * | 2002-06-28 | 2004-01-08 | Prall John M. | System event filtering and notification for OPC clients |
US20040045009A1 (en) * | 2002-08-29 | 2004-03-04 | Bae Systems Information Electronic Systems Integration, Inc. | Observation tool for signal processing components |
DE10243783A1 (de) * | 2002-09-20 | 2004-03-25 | Sick Ag | Elektronische Vorrichtung für ein Bussystem |
US7467018B1 (en) * | 2002-11-18 | 2008-12-16 | Rockwell Automation Technologies, Inc. | Embedded database systems and methods in an industrial controller environment |
DE10313389A1 (de) * | 2003-03-25 | 2004-10-07 | Endress + Hauser Process Solutions Ag | Verfahren zur Übertragung von Softwarecode von einer Steuereinheit zu einem Feldgerät der Prozessautomatisierungstechnik |
US20040148370A1 (en) * | 2003-01-23 | 2004-07-29 | Electronic Data Systems Corporation | System and method for composing, configuring, deploying, and managing services using a graphical user interface |
US7386609B2 (en) | 2003-02-20 | 2008-06-10 | International Business Machines Corporation | Method, system, and program for managing devices in a network |
EP1460540A1 (en) * | 2003-03-20 | 2004-09-22 | Dassault Systèmes S.A. | Server process with interface adapters for accessing data from various types of client processes |
EP1614254A1 (en) * | 2003-04-04 | 2006-01-11 | Computer Associates Think, Inc. | Method and system of alert notification |
US7516161B1 (en) * | 2003-08-27 | 2009-04-07 | Sparta Systems, Inc. | Administrative triggers |
US20050080897A1 (en) * | 2003-09-29 | 2005-04-14 | Capital One Financial Corporation | Remote management utility |
US7529814B2 (en) | 2003-10-15 | 2009-05-05 | International Business Machines Corporation | Autonomic computing algorithm for identification of an optimum configuration for a web infrastructure |
US7376083B2 (en) * | 2003-12-09 | 2008-05-20 | International Business Machines Corporation | Apparatus and method for modeling queueing systems with highly variable traffic arrival rates |
US7587421B2 (en) * | 2004-01-30 | 2009-09-08 | International Business Machines Corporation | Method, system, and article of manufacture for generating device specific requests |
US7234084B2 (en) | 2004-02-18 | 2007-06-19 | Emerson Process Management | System and method for associating a DLPDU received by an interface chip with a data measurement made by an external circuit |
US7058089B2 (en) * | 2004-02-18 | 2006-06-06 | Rosemount, Inc. | System and method for maintaining a common sense of time on a network segment |
US7703019B2 (en) * | 2004-03-26 | 2010-04-20 | Sap Ag | Visual administrator for specifying service references to support a service |
US7661066B2 (en) * | 2004-03-26 | 2010-02-09 | Sap Ag | Visual administrator providing java management bean support |
SE532068C2 (sv) * | 2004-11-14 | 2009-10-13 | Abb Research Ltd | Metod för presentation av data vid ett industriellt styrsystem |
US20060133412A1 (en) * | 2004-12-22 | 2006-06-22 | Rockwell Automation Technologies, Inc. | Integration of control and business applications using integration servers |
US7536449B2 (en) * | 2005-02-11 | 2009-05-19 | Microsoft Corporation | Server-functionality role extensibility model |
US7706895B2 (en) * | 2005-02-25 | 2010-04-27 | Rockwell Automation Technologies, Inc. | Reliable messaging instruction |
US7565351B1 (en) | 2005-03-14 | 2009-07-21 | Rockwell Automation Technologies, Inc. | Automation device data interface |
US9201420B2 (en) | 2005-04-08 | 2015-12-01 | Rosemount, Inc. | Method and apparatus for performing a function in a process plant using monitoring data with criticality evaluation data |
US7233830B1 (en) * | 2005-05-31 | 2007-06-19 | Rockwell Automation Technologies, Inc. | Application and service management for industrial control devices |
US7822857B2 (en) * | 2005-09-07 | 2010-10-26 | Hewlett-Packard Development Company, L.P. | Methods and systems for sharing remote access |
US7698691B2 (en) * | 2005-09-20 | 2010-04-13 | Microsoft Corporation | Server application state |
US7930363B2 (en) * | 2005-10-12 | 2011-04-19 | Powerreviews, Inc. | Application service provider delivery system |
EP1955281A4 (en) | 2005-12-01 | 2009-03-11 | Firestar Software Inc | SYSTEM AND METHOD FOR EXCHANGING INFORMATION BETWEEN EXCHANGE APPLICATIONS |
US7489977B2 (en) * | 2005-12-20 | 2009-02-10 | Fieldbus Foundation | System and method for implementing time synchronization monitoring and detection in a safety instrumented system |
US8676357B2 (en) | 2005-12-20 | 2014-03-18 | Fieldbus Foundation | System and method for implementing an extended safety instrumented system |
US20070198554A1 (en) * | 2006-02-10 | 2007-08-23 | Sun Microsystems, Inc. | Apparatus for business service oriented management infrastructure |
US8576731B2 (en) * | 2006-02-14 | 2013-11-05 | Jds Uniphase Corporation | Random data compression scheme in a network diagnostic component |
US8607145B2 (en) * | 2006-02-14 | 2013-12-10 | Jds Uniphase Corporation | Show OOB and speed negotiation data graphically in a network diagnostic component |
US8769152B2 (en) * | 2006-02-14 | 2014-07-01 | Jds Uniphase Corporation | Align/notify compression scheme in a network diagnostic component |
US8125906B2 (en) * | 2006-03-03 | 2012-02-28 | Kiranmai Vedanabhatla | Capture RCDT and SNTT SAS speed negotiation decodes in a network diagnostic component |
US20070189175A1 (en) * | 2006-02-14 | 2007-08-16 | Finisar Corporation | Capture timing and negotiation data with repeat counts in a networking diagnostic component |
SE531389C2 (sv) | 2006-03-01 | 2009-03-17 | Abb Ab | Metod för hantering av olika versioner av en applikation och ett automationssystem |
US7756973B2 (en) * | 2006-04-27 | 2010-07-13 | International Business Machines Corporation | Identifying a configuration for an application in a production environment |
US20070288254A1 (en) * | 2006-05-08 | 2007-12-13 | Firestar Software, Inc. | System and method for exchanging transaction information using images |
US7698242B2 (en) * | 2006-08-16 | 2010-04-13 | Fisher-Rosemount Systems, Inc. | Systems and methods to maintain process control systems using information retrieved from a database storing general-type information and specific-type information |
US10031830B2 (en) * | 2006-10-13 | 2018-07-24 | International Business Machines Corporation | Apparatus, system, and method for database management extensions |
US9053492B1 (en) * | 2006-10-19 | 2015-06-09 | Google Inc. | Calculating flight plans for reservation-based ad serving |
CN100456237C (zh) * | 2007-01-31 | 2009-01-28 | 华为技术有限公司 | 数据库访问方法和装置 |
US8332819B2 (en) * | 2007-05-03 | 2012-12-11 | Siemens Industry, Inc. | Diagnostic and trouble-shooting methods in a wireless control and sensor network |
US7856517B2 (en) | 2007-05-25 | 2010-12-21 | Red Hat, Inc. | Data management interface with configurable plugins that determines whether to monitor for configuration data |
US7716399B2 (en) * | 2007-05-25 | 2010-05-11 | Red Hat, Inc. | Method and system for data management interface with intelligent plugins that determine whether to perform the requested data operation received from an application |
US8145655B2 (en) * | 2007-06-22 | 2012-03-27 | International Business Machines Corporation | Generating information on database queries in source code into object code compiled from the source code |
DE102007032715B4 (de) * | 2007-07-13 | 2009-04-09 | Abb Ag | System und Verfahren zur Überwachung des Datenverkehrs bei einem Feldbus |
US8769291B2 (en) * | 2007-07-23 | 2014-07-01 | Red Hat, Inc. | Certificate generation for a network appliance |
US8621027B2 (en) | 2007-11-16 | 2013-12-31 | Red Hat, Inc. | Automatically providing identity information for a network appliance |
US8191123B2 (en) * | 2007-11-27 | 2012-05-29 | Red Hat, Inc. | Provisioning a network appliance |
US8191122B2 (en) * | 2007-11-27 | 2012-05-29 | Red Hat, Inc. | Provisioning a network appliance |
DE102007062985B4 (de) * | 2007-12-21 | 2014-01-02 | Abb Research Ltd. | Verfahren und Einrichtung zur Kommunikation gemäß dem Standardprotokoll OPC UA in einem Client-Server-System |
DE102008016048A1 (de) * | 2008-03-28 | 2009-10-08 | Abb Ag | Prozessleitsystem einer Automatisierungsanlage |
US20090302588A1 (en) * | 2008-06-05 | 2009-12-10 | Autoliv Asp, Inc. | Systems and methods for airbag tether release |
CN101364175B (zh) * | 2008-07-02 | 2013-11-20 | 深圳国人通信有限公司 | 嵌入式系统的配置方法及装置 |
US9026918B2 (en) * | 2008-10-16 | 2015-05-05 | Accenture Global Services Limited | Enabling a user device to access enterprise data |
CN101738958B (zh) * | 2008-11-14 | 2012-05-02 | 四零四科技股份有限公司 | 主动式监控系统及其方法 |
US20100153866A1 (en) | 2008-12-11 | 2010-06-17 | Accenture Global Services Gmbh | Method and system for modifying the execution of a native application running on a portable electronic device |
US20100312879A1 (en) * | 2009-06-09 | 2010-12-09 | International Business Machines Corporation | Plug-in provisioning integration in a clustered environment |
US8155761B2 (en) * | 2009-07-23 | 2012-04-10 | Fisher-Rosemount Systems, Inc. | Process control system with integrated external data sources |
US8788513B2 (en) * | 2009-10-30 | 2014-07-22 | Dassault Systemes Americas Corp. | Computer method and system providing access to data of a target system |
US8775581B2 (en) * | 2010-01-19 | 2014-07-08 | Ianywhere Solutions, Inc. | Controlling lifetime of server add-ins |
US20110219387A1 (en) * | 2010-03-04 | 2011-09-08 | Microsoft Corporation | Interactive Remote Troubleshooting of a Running Process |
US9122764B2 (en) * | 2010-03-24 | 2015-09-01 | Fisher-Rosemount Systems, Inc. | Methods and apparatus to access process data stored on a server |
US9392072B2 (en) | 2010-04-15 | 2016-07-12 | Rockwell Automation Technologies, Inc. | Systems and methods for conducting communications among components of multidomain industrial automation system |
US8484401B2 (en) * | 2010-04-15 | 2013-07-09 | Rockwell Automation Technologies, Inc. | Systems and methods for conducting communications among components of multidomain industrial automation system |
US8984533B2 (en) | 2010-04-15 | 2015-03-17 | Rockwell Automation Technologies, Inc. | Systems and methods for conducting communications among components of multidomain industrial automation system |
DE102010040055B4 (de) * | 2010-08-31 | 2023-08-17 | Endress + Hauser Process Solutions Ag | System zur Kommunikation von mehreren Clients mit mehreren Feldgeräten in der Automatisierungstechnik |
CN101964798A (zh) * | 2010-10-15 | 2011-02-02 | 德讯科技股份有限公司 | 基于远程桌面协议的多图形协议统一代理系统 |
DE102010048809A1 (de) | 2010-10-20 | 2012-04-26 | Hüttinger Elektronik Gmbh + Co. Kg | Leistungsversorgungssystem für eine Plasmaanwendung und/oder eine Induktionserwärmungsanwendung |
DE102010048810A1 (de) | 2010-10-20 | 2012-04-26 | Hüttinger Elektronik Gmbh + Co. Kg | System zur Bedienung mehrerer Plasma- und/oder Induktionserwärmungsprozesse |
US8898761B2 (en) * | 2011-01-13 | 2014-11-25 | International Business Machines Corporation | Systems and methods for generating and validating configuration files for computing devices |
US9927788B2 (en) | 2011-05-19 | 2018-03-27 | Fisher-Rosemount Systems, Inc. | Software lockout coordination between a process control system and an asset management system |
US8885665B2 (en) * | 2011-05-31 | 2014-11-11 | General Electric Company | Systems and methods for foundation fieldbus alerts |
US8856302B2 (en) * | 2011-05-31 | 2014-10-07 | General Electric Company | Systems and methods for foundation fieldbus alerts |
US8667078B2 (en) * | 2011-05-31 | 2014-03-04 | General Electric Company | Systems and methods of extracting, storing, and serving device definition file information |
US8730054B2 (en) | 2011-05-31 | 2014-05-20 | General Electric Company | Systems and methods to customize alert presentation |
US10165007B2 (en) * | 2011-09-15 | 2018-12-25 | Microsoft Technology Licensing, Llc | Securing data usage in computing devices |
US9098312B2 (en) | 2011-11-16 | 2015-08-04 | Ptc Inc. | Methods for dynamically generating an application interface for a modeled entity and devices thereof |
US8909641B2 (en) | 2011-11-16 | 2014-12-09 | Ptc Inc. | Method for analyzing time series activity streams and devices thereof |
US9576046B2 (en) | 2011-11-16 | 2017-02-21 | Ptc Inc. | Methods for integrating semantic search, query, and analysis across heterogeneous data types and devices thereof |
US20130184883A1 (en) * | 2012-01-18 | 2013-07-18 | General Electric Company | System and method to control subsystems |
EP2823617B1 (de) * | 2012-05-31 | 2018-07-11 | Siemens Aktiengesellschaft | Kommunikation zweier clients über einen server |
CN103577456B (zh) | 2012-07-31 | 2016-12-21 | 国际商业机器公司 | 用于处理时序数据的方法和装置 |
KR101638656B1 (ko) * | 2012-08-23 | 2016-07-11 | 엘에스산전 주식회사 | 산업용 자동화를 위한 클라우드 컴퓨팅 기반의 데이터 공유 시스템 및 산업용 기기 관리 장치 |
EP2713301A1 (de) * | 2012-09-27 | 2014-04-02 | Siemens Aktiengesellschaft | Verfahren und System zur Anbindung einer Steuerung für eine Maschine an ein übergeordnetes IT-System |
US9015212B2 (en) | 2012-10-16 | 2015-04-21 | Rackspace Us, Inc. | System and method for exposing cloud stored data to a content delivery network |
US9049076B1 (en) | 2013-01-07 | 2015-06-02 | Google Inc. | Content selection with privacy features |
US10425355B1 (en) * | 2013-02-04 | 2019-09-24 | HCA Holdings, Inc. | Data stream processing for dynamic resource scheduling |
EP2973047A4 (en) | 2013-03-15 | 2016-11-02 | Ptc Inc | METHODS OF MANAGING APPLICATIONS USING SEMANTIC MODELING AND LABELING, AND DEVICES THEREOF |
CN103235835B (zh) * | 2013-05-22 | 2017-03-29 | 曙光信息产业(北京)有限公司 | 用于数据库集群的查询实现方法和装置 |
DE102013108478A1 (de) * | 2013-08-06 | 2015-02-12 | Endress+Hauser Process Solutions Ag | Verfahren zur Erweiterung einer eingebetteten Softwarekomponente eines Feldgerätes |
US20150058392A1 (en) * | 2013-08-20 | 2015-02-26 | Cellco Partnership D/B/A Verizon Wireless | Provisioning chain queuing and processing |
CN104426880A (zh) * | 2013-09-03 | 2015-03-18 | 中国银联股份有限公司 | 一种基于网络的集中式文件自动收集和分发装置 |
CN104468148B (zh) * | 2013-09-12 | 2019-03-22 | 中兴通讯股份有限公司 | 一种nginx服务器配置维护方法及系统 |
CN104750049B (zh) * | 2013-12-31 | 2018-05-08 | 北京北方华创微电子装备有限公司 | 半导体制造中气路配置处理的方法及系统 |
US9413682B2 (en) | 2014-02-07 | 2016-08-09 | International Business Machines Corporation | Provisioning legacy systems network architecture resource communications through a group of servers in a data center |
US9916188B2 (en) * | 2014-03-14 | 2018-03-13 | Cask Data, Inc. | Provisioner for cluster management system |
WO2015143416A1 (en) | 2014-03-21 | 2015-09-24 | Ptc Inc. | Systems and methods for developing and using real-time data applications |
US10313410B2 (en) | 2014-03-21 | 2019-06-04 | Ptc Inc. | Systems and methods using binary dynamic rest messages |
US9961058B2 (en) | 2014-03-21 | 2018-05-01 | Ptc Inc. | System and method of message routing via connection servers in a distributed computing environment |
US9660877B1 (en) | 2014-03-21 | 2017-05-23 | Cisco Technology, Inc. | Transaction management in multi-protocol SDN controller |
US9467533B2 (en) | 2014-03-21 | 2016-10-11 | Ptc Inc. | System and method for developing real-time web-service objects |
US9350791B2 (en) | 2014-03-21 | 2016-05-24 | Ptc Inc. | System and method of injecting states into message routing in a distributed computing environment |
US9467536B1 (en) * | 2014-03-21 | 2016-10-11 | Cisco Technology, Inc. | Shim layer abstraction in multi-protocol SDN controller |
US10025942B2 (en) | 2014-03-21 | 2018-07-17 | Ptc Inc. | System and method of establishing permission for multi-tenancy storage using organization matrices |
US9560170B2 (en) | 2014-03-21 | 2017-01-31 | Ptc Inc. | System and method of abstracting communication protocol using self-describing messages |
US9350812B2 (en) | 2014-03-21 | 2016-05-24 | Ptc Inc. | System and method of message routing using name-based identifier in a distributed computing environment |
US9762637B2 (en) | 2014-03-21 | 2017-09-12 | Ptc Inc. | System and method of using binary dynamic rest messages |
US9462085B2 (en) | 2014-03-21 | 2016-10-04 | Ptc Inc. | Chunk-based communication of binary dynamic rest messages |
CN104363201B (zh) * | 2014-10-11 | 2017-10-20 | 中国农业银行股份有限公司 | 一种服务器投产变更方法和系统 |
EP3015984A1 (en) * | 2014-10-29 | 2016-05-04 | Hewlett-Packard Development Company, L.P. | Providing data from data sources |
JP6337741B2 (ja) * | 2014-10-31 | 2018-06-06 | 富士通株式会社 | 制御プログラム、制御装置、制御方法及びデータベースシステム |
US20160170405A1 (en) * | 2014-12-10 | 2016-06-16 | General Electric Company | Systems and methods for memory map utilization |
CN107548475B (zh) * | 2015-03-27 | 2020-04-14 | 布勒有限公司 | 自适应跨设备控制和操纵系统及其对应的方法 |
CN104881254B (zh) * | 2015-05-27 | 2018-09-07 | 北京百度网讯科技有限公司 | 数据存储方法和装置 |
US10482231B1 (en) * | 2015-09-22 | 2019-11-19 | Amazon Technologies, Inc. | Context-based access controls |
US10048713B2 (en) * | 2015-11-19 | 2018-08-14 | Rockwell Automation Technologies Inc. | Energy operations across domains |
US10495336B2 (en) * | 2015-11-19 | 2019-12-03 | Rockwell Automation Technologies, Inc. | Energy operations across domains |
US10225149B2 (en) * | 2015-12-15 | 2019-03-05 | Nicira, Inc. | Method and tool for diagnosing logical networks |
US20170187835A1 (en) * | 2015-12-26 | 2017-06-29 | Lee Booi Lim | Technologies for unified and modular gateway abstraction |
CN106982236B (zh) * | 2016-01-18 | 2020-07-28 | 阿里巴巴集团控股有限公司 | 一种信息处理方法、装置和系统 |
US10241820B2 (en) | 2016-03-14 | 2019-03-26 | Nicira, Inc. | Determining the realization status of logical entities in logical networks |
US10243797B2 (en) | 2016-03-14 | 2019-03-26 | Nicira, Inc. | Identifying the realization status of logical entities based on a global realization number |
JP6701859B2 (ja) * | 2016-03-24 | 2020-05-27 | 富士ゼロックス株式会社 | 通信プログラム、通信装置及び通信システム |
JP6696252B2 (ja) * | 2016-03-24 | 2020-05-20 | 富士ゼロックス株式会社 | 通信プログラム、通信装置及び情報処理装置 |
WO2017214861A1 (en) * | 2016-06-14 | 2017-12-21 | SZ DJI Technology Co., Ltd. | Supporting protocol independent movable object application development |
US10447541B2 (en) * | 2016-08-13 | 2019-10-15 | Nicira, Inc. | Policy driven network QoS deployment |
DE102016125171A1 (de) * | 2016-12-21 | 2018-06-21 | Endress+Hauser Process Solutions Ag | Überwachung der Datenübertragung in einem Client-Server-basierten Gerätezugriffssystem |
US11323519B2 (en) * | 2017-04-19 | 2022-05-03 | Microsoft Technology Licensing, Llc | Internet of things pub-sub data publisher |
CN107730077A (zh) * | 2017-09-13 | 2018-02-23 | 平安科技(深圳)有限公司 | 节点任务数据显示方法、装置、存储介质和计算机设备 |
US10904088B2 (en) * | 2018-11-15 | 2021-01-26 | Western Digital Technologies, Inc. | Reconfiguring network settings for operating configuration installation |
CN109617232B (zh) * | 2018-12-13 | 2021-04-23 | 高新兴科技集团股份有限公司 | 一种基于4g模组的微电源监控设备、系统及方法 |
JP6973427B2 (ja) * | 2019-02-15 | 2021-11-24 | 株式会社安川電機 | 通信システム、通信方法、及びプログラム |
US10645196B1 (en) * | 2019-04-26 | 2020-05-05 | Clario Tech Limited | Multicomponent software-controllable system and a method for interaction of server-client processes and a machine-readable carrier for performing the method |
CN112181509A (zh) * | 2019-07-02 | 2021-01-05 | 施耐德电气美国股份有限公司 | 确保在模块化设备和外部系统之间的数据一致性 |
US11726995B2 (en) | 2019-12-17 | 2023-08-15 | Hewlett Packard Enterprise Development Lp | System and method for value pack generation using generic SQL plugin for unified console |
US11128529B1 (en) | 2020-03-17 | 2021-09-21 | Capital One Services, Llc | Cloud infrastructure for isolation and run-time behavioral tuning through configuration externalization |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5887171A (en) * | 1996-01-29 | 1999-03-23 | Hitachi, Ltd. | Document management system integrating an environment for executing an agent and having means for changing an agent into an object |
US5987633A (en) * | 1997-08-20 | 1999-11-16 | Mci Communications Corporation | System, method and article of manufacture for time point validation |
US6049819A (en) * | 1997-12-10 | 2000-04-11 | Nortel Networks Corporation | Communications network incorporating agent oriented computing environment |
US6091811A (en) * | 1997-11-13 | 2000-07-18 | Lucent Technologies Inc. | Ringing technique in automatic call distribution |
Family Cites Families (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA1293819C (en) * | 1986-08-29 | 1991-12-31 | Thinking Machines Corporation | Very large scale computer |
US5165018A (en) * | 1987-01-05 | 1992-11-17 | Motorola, Inc. | Self-configuration of nodes in a distributed message-based operating system |
CA2044022A1 (en) | 1990-06-28 | 1991-12-29 | Miriam A. Nihart | Common agent computer management system and method |
EP0490595B1 (en) * | 1990-12-14 | 1998-05-20 | Sun Microsystems, Inc. | Method for operating time critical processes in a window system environment |
US5386566A (en) * | 1991-03-20 | 1995-01-31 | Hitachi, Ltd. | Inter-processor communication method for transmitting data and processor dependent information predetermined for a receiving process of another processor |
US5329619A (en) * | 1992-10-30 | 1994-07-12 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
US5491791A (en) * | 1995-01-13 | 1996-02-13 | International Business Machines Corporation | System and method for remote workstation monitoring within a distributed computing environment |
US5872928A (en) | 1995-02-24 | 1999-02-16 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US5655081A (en) * | 1995-03-08 | 1997-08-05 | Bmc Software, Inc. | System for monitoring and managing computer resources and applications across a distributed computing environment using an intelligent autonomous agent architecture |
US5882534A (en) * | 1995-05-17 | 1999-03-16 | Lg Semicon Co., Ltd. | Method for fabricating a multistage phase shift mask |
GB2301717B (en) * | 1995-06-02 | 1999-08-11 | Dsc Communications | Network controller for monitoring the status of a network |
US6732170B2 (en) * | 1996-02-13 | 2004-05-04 | Hitachi, Ltd. | Network managing method, medium and system |
US5819042A (en) | 1996-02-20 | 1998-10-06 | Compaq Computer Corporation | Method and apparatus for guided configuration of unconfigured network and internetwork devices |
US5845283A (en) * | 1996-04-24 | 1998-12-01 | Lingua Teq, Inc. | Method and apparatus for rationalizing different data formats in a data management system |
US5872966A (en) * | 1996-05-10 | 1999-02-16 | Apple Computer, Inc. | System and method for logging and enabling further manipulation of system state information |
US5822534A (en) * | 1996-06-04 | 1998-10-13 | Sun Microsystems, Inc. | Method and apparatus for selectively unmanaging elements on a network |
US6718550B1 (en) * | 1996-06-26 | 2004-04-06 | Sun Microsystems, Inc. | Method and apparatus for improving the performance of object invocation |
US5958012A (en) * | 1996-07-18 | 1999-09-28 | Computer Associates International, Inc. | Network management system using virtual reality techniques to display and simulate navigation to network components |
US5875306A (en) * | 1996-10-01 | 1999-02-23 | International Business Machines Corporation | Reconfiguring computer resources in a distributed computer enterprise environment |
US5884046A (en) * | 1996-10-23 | 1999-03-16 | Pluris, Inc. | Apparatus and method for sharing data and routing messages between a plurality of workstations in a local area network |
US6330008B1 (en) * | 1997-02-24 | 2001-12-11 | Torrent Systems, Inc. | Apparatuses and methods for monitoring performance of parallel computing |
GB9707550D0 (en) * | 1997-04-15 | 1997-06-04 | British Telecomm | Design of computer networks |
US6247128B1 (en) * | 1997-07-22 | 2001-06-12 | Compaq Computer Corporation | Computer manufacturing with smart configuration methods |
US6038399A (en) * | 1997-07-22 | 2000-03-14 | Compaq Computer Corporation | Computer manufacturing architecture with two data-loading processes |
US6051449A (en) * | 1997-08-06 | 2000-04-18 | Micron Technology, Inc. | Method and apparatus for Epoxy loc die attachment |
US6134581A (en) | 1997-10-06 | 2000-10-17 | Sun Microsystems, Inc. | Method and system for remotely browsing objects |
US6041347A (en) * | 1997-10-24 | 2000-03-21 | Unified Access Communications | Computer system and computer-implemented process for simultaneous configuration and monitoring of a computer network |
US6314422B1 (en) * | 1997-12-09 | 2001-11-06 | Chrysler Corporation | Method for softlinking between documents in a vehicle diagnostic system |
CA2233794C (en) * | 1998-02-24 | 2001-02-06 | Luc Bessette | Method and apparatus for the management of medical files |
US6154778A (en) * | 1998-05-19 | 2000-11-28 | Hewlett-Packard Company | Utility-based multi-category quality-of-service negotiation in distributed systems |
US6317786B1 (en) * | 1998-05-29 | 2001-11-13 | Webspective Software, Inc. | Web service |
US6480597B1 (en) * | 1998-06-12 | 2002-11-12 | Mci Communications Corporation | Switch controller for a telecommunications network |
US6192364B1 (en) * | 1998-07-24 | 2001-02-20 | Jarg Corporation | Distributed computer database system and method employing intelligent agents |
AU9033998A (en) | 1998-08-26 | 2000-03-21 | Harris Corporation | Diagnostic system and method for monitoring plural software applications using plural diagnostic tools |
US6446136B1 (en) | 1998-12-31 | 2002-09-03 | Computer Associates Think, Inc. | System and method for dynamic correlation of events |
US6430598B1 (en) * | 1999-01-29 | 2002-08-06 | International Business Machines Corporation | Method and system for deleting messages from a server |
US6480901B1 (en) * | 1999-07-09 | 2002-11-12 | Lsi Logic Corporation | System for monitoring and managing devices on a network from a management station via a proxy server that provides protocol converter |
US6449739B1 (en) * | 1999-09-01 | 2002-09-10 | Mercury Interactive Corporation | Post-deployment monitoring of server performance |
US7600039B2 (en) * | 2000-02-16 | 2009-10-06 | Motorola, Inc. | Label-based multiplexing |
US6658598B1 (en) * | 2000-02-17 | 2003-12-02 | Motive Communications, Inc. | Technical support chain automation with guided self-help capability using active content assertions |
US6498835B1 (en) * | 2000-02-29 | 2002-12-24 | Ameritech Corporation | Method and system for providing visual notification in a unified messaging system |
US6601094B1 (en) * | 2000-04-27 | 2003-07-29 | Hewlett-Packard Development Company, L.P. | Method and system for recommending an available network protocol |
US6721880B1 (en) * | 2000-05-31 | 2004-04-13 | Lucent Technologies Inc. | Method and apparatus for maintaining configuration information in a computing environment |
US6785723B1 (en) * | 2000-06-22 | 2004-08-31 | International Business Machines Corporation | Tracking the transmission of web documents or files sent from resource locations through servers on the web to client computer stations which send tracked transmission characteristics data back to said servers |
US6959332B1 (en) * | 2000-07-12 | 2005-10-25 | Cisco Technology, Inc. | Basic command representation of quality of service policies |
-
2001
- 2001-09-14 AU AU9268901A patent/AU9268901A/xx active Pending
- 2001-09-14 CN CNB018189687A patent/CN100521711C/zh not_active Expired - Lifetime
- 2001-09-14 AU AU2001292691A patent/AU2001292691B2/en not_active Ceased
- 2001-09-14 US US09/954,508 patent/US7644120B2/en active Active
- 2001-09-14 WO PCT/US2001/028955 patent/WO2002023875A1/en active IP Right Grant
- 2001-09-14 AU AU2001292689A patent/AU2001292689B2/en not_active Ceased
- 2001-09-14 US US09/954,423 patent/US8095632B2/en active Active
- 2001-09-14 US US09/954,422 patent/US7779089B2/en active Active
- 2001-09-14 EP EP01973073.8A patent/EP1327348B1/en not_active Expired - Lifetime
- 2001-09-14 WO PCT/US2001/028951 patent/WO2002023405A1/en active Application Filing
- 2001-09-14 EP EP01973071.2A patent/EP1330724B1/en not_active Expired - Lifetime
- 2001-09-14 AU AU9269101A patent/AU9269101A/xx active Pending
- 2001-09-14 AU AU2001292690A patent/AU2001292690A1/en not_active Abandoned
- 2001-09-14 CN CNB018188648A patent/CN1261892C/zh not_active Expired - Lifetime
- 2001-09-14 EP EP01973072.0A patent/EP1330737B1/en not_active Expired - Lifetime
- 2001-09-14 WO PCT/US2001/028949 patent/WO2002023364A1/en active Application Filing
-
2010
- 2010-01-05 US US12/652,562 patent/US20100205244A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5887171A (en) * | 1996-01-29 | 1999-03-23 | Hitachi, Ltd. | Document management system integrating an environment for executing an agent and having means for changing an agent into an object |
US5987633A (en) * | 1997-08-20 | 1999-11-16 | Mci Communications Corporation | System, method and article of manufacture for time point validation |
US6091811A (en) * | 1997-11-13 | 2000-07-18 | Lucent Technologies Inc. | Ringing technique in automatic call distribution |
US6049819A (en) * | 1997-12-10 | 2000-04-11 | Nortel Networks Corporation | Communications network incorporating agent oriented computing environment |
Also Published As
Publication number | Publication date |
---|---|
EP1330737A1 (en) | 2003-07-30 |
AU2001292689B2 (en) | 2006-10-26 |
AU2001292690A1 (en) | 2002-03-26 |
WO2002023875A1 (en) | 2002-03-21 |
US20020112044A1 (en) | 2002-08-15 |
EP1330724B1 (en) | 2018-11-14 |
US20020116453A1 (en) | 2002-08-22 |
CN1504041A (zh) | 2004-06-09 |
US20020112038A1 (en) | 2002-08-15 |
EP1327348A4 (en) | 2009-08-05 |
AU9268901A (en) | 2002-03-26 |
EP1327348B1 (en) | 2015-10-21 |
EP1330724A4 (en) | 2009-11-11 |
EP1330737B1 (en) | 2014-02-26 |
EP1330737A4 (en) | 2009-11-11 |
WO2002023405A1 (en) | 2002-03-21 |
AU2001292691B2 (en) | 2007-05-24 |
EP1327348A1 (en) | 2003-07-16 |
AU9269101A (en) | 2002-03-26 |
WO2002023364A1 (en) | 2002-03-21 |
US7644120B2 (en) | 2010-01-05 |
EP1330724A1 (en) | 2003-07-30 |
US7779089B2 (en) | 2010-08-17 |
US20100205244A1 (en) | 2010-08-12 |
CN1474976A (zh) | 2004-02-11 |
CN1261892C (zh) | 2006-06-28 |
US8095632B2 (en) | 2012-01-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN100521711C (zh) | 用于过程数据访问服务器的远程配置的系统 | |
AU2001292691A1 (en) | A method and system for remote configuration of process data access servers | |
CN1386220B (zh) | 多协议环境中的自动工具管理 | |
US6098116A (en) | Process control system including a method and apparatus for automatically sensing the connection of devices to a network | |
US5828851A (en) | Process control system using standard protocol control of standard devices and nonstandard devices | |
US7010294B1 (en) | Wireless control of a field device in an industrial process | |
US8122161B2 (en) | Associating and evaluating status information for a primary input parameter value from a profibus device | |
US7675935B2 (en) | Apparatus and method for integrating wireless or other field devices in a process control system | |
CN102736600B (zh) | 用于将无线数据合并到已建过程控制系统中的设备及方法 | |
CN101154104B (zh) | 用于过程控制系统网络的统一应用编程界面 | |
US7146230B2 (en) | Integrated fieldbus data server architecture | |
CN105991765A (zh) | 将工业自动化工厂备份在云中 | |
US20040260404A1 (en) | Method and apparatus for self-configuring supervisory control and data acquisition (SCADA) system for distributed control | |
MX2009000782A (es) | Metodo de configuracion de dispositivos electronicos e inteligentes para facilitar mensajes de comunicacion estandarizados entre una pluralidad de ied dentro de una red. | |
CN101496371A (zh) | 在过程控制系统中把无线现场设备与有线协议相集成的设备和方法 | |
WO2001009690A9 (en) | Methods and apparatus for object-based process control | |
WO2001057823A2 (en) | Apparatus and method for web-based tool management | |
US20100064297A1 (en) | Configuring And Providing Enhanced Access To Profibus Device Diagnostic Data | |
CN107077128A (zh) | 控制工业设施中的现实世界对象 | |
US7756963B2 (en) | Automated tool management in a multi-protocol environment | |
Penarrieta et al. | Development of an Industrial Communication Driver for Ethernet/IP Devices | |
George et al. | The Impact of Information Technology on Industrial Automation–A Critical Evaluation | |
Fortin et al. | Using PLCopen OPC-UA Client Function Blocks to model MDIS Information | |
Newton et al. | Implementation of object-oriented protocol agents in communication devices | |
Aihkisalo | VTTTIEDOTTEITA |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
TR01 | Transfer of patent right |
Effective date of registration: 20171107 Address after: American California Patentee after: Schneider Electronic Software Co., Ltd. Address before: American California Patentee before: Invensys System Inc. |
|
TR01 | Transfer of patent right | ||
CX01 | Expiry of patent term |
Granted publication date: 20090729 |
|
CX01 | Expiry of patent term |