Enovia配置培训资料_02_AEF Components Overview-已转档.docx

Enovia配置培训资料_02_AEF Components Overview-已转档.docx

  1. 1、本文档共78页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Unit 1: AEF Components Overview AEF组件预览 1- PAGE 1- PAGE 5 Lesson 1: Overview of AEF Components AEF Overview AEF Overview 1-6 1-6 AEF概述 The Application Exchange Framework (AEF) is an extension to the Matrix product line 应用程序交换框架(AEF)是矩阵产品线的扩展 All MatrixOne Business Process Applications use the AEF 所有MatrixOne业务流程应用程序都使用AEF The AEF is comprised of the following components: AEF由以下组件组成 Database Objects Web Files Database Objects Database Objects Pre-defined Schema Administrative Objects Business Objects Program Objects Tcl JPO User Interface (UI3 Objects) Administrative Schema Objects Administrative Schema Objects The following Administrative objects are installed in the Matrix database for all applications: 所有应用程序的矩阵数据库中都安装了以下管理对象 attributes commands/menus formats groups/roles/persons policies relationships types vaults wizards (for admin use only) programs (JPO and MQL/Tcl) Program Objects Program Objects 1-8 1-8 MQL/Tcl program objects Java Program Objects (JPO) To supply utility functions and common access procedures to all applications 为所有应用程序提供实用功能和公共访问程序 Support object naming and trigger management procedures支持对象的命名和触发管理程序 1-8 1-8 The Application Exchange Framework (AEF) and the Business Process Applications that sit on top of the AEF ship with JPOs defined for most Business Types in the schema 应用程序交换框架(AEF)和位于AEF之上的业务流程应用程序,其中为模式中的大多数业务类型定义了JPOs Each JPO is shipped as a combination of a “base” class and a “derived” class. All OOTB business logic is placed in the base class Example: Business Type named Part would be represented by the 2 JPOs named emxPartBase and emxPart (which extends emxPartBase) 每个JPO都作为“基础”类和“派生”类的组合提供。所有OOTB业务逻辑都放在基类中 示例:名为Part的业务类型将由两个名为emxPartBase的JPOs和emxPart(扩展了emxPartBase)表示 The derived class is available for extensions to the business logic 派生类是可扩展的业务逻辑 Since the system always refers to the derived class, custom extensions are picked up without a need for changing OOTB logic

文档评论(0)

kolr + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档