2.1.2.2 Workshop-Facades

eas facade、fuction开发实例一、引言EAS（Enterprise Application Suite）是一款面向企业级应用开发的解决方案，它包括了一系列的开发框架、开发工具、组件和运行环境，为企业级应用的开发、部署和运行提供了全面的支持。

EAS Facade和Function是EAS中两个重要的部分，本文将以EAS Facade和Function的开发实例为例，介绍其基本概念和开发方法。

二、EAS Facade的概念和作用1. EAS Facade是EAS框架中的一个重要组成部分，它提供了一种统一的接口，用于封装各个业务模块的服务，将底层的业务逻辑与上层的数据传输进行了解耦，为客户端提供了一种简单、统一的访问接口。

2. EAS Facade的作用包括但不限于：(1) 封装业务逻辑：将业务逻辑进行封装，提供统一的访问接口，隐藏底层实现细节，降低客户端与服务端的耦合度。

(2) 提供统一的数据传输格式：通过EAS Facade可以统一定义数据传输格式，客户端可以通过统一的接口进行数据交互，简化了开发和维护工作。

(3) 安全性和事务管理：EAS Facade提供了安全性控制和事务管理的机制，保障了系统的安全性和数据的完整性。

三、EAS Facade的开发实例1. 创建Facade接口进入Eclipse开发环境，首先创建一个新的Facade接口，命名为"SampleFacade"，并定义一些基本的业务方法，如：```public interface SampleFacade {public void doBusiness1();public void doBusiness2();// 更多业务方法}```2. 实现Facade接口在创建好Facade接口之后，需要我们进行具体的业务逻辑实现，这一步需要我们编写对应的Java类，实现SampleFacade接口，例如"SampleFacadeImpl"类，代码如下：```public class SampleFacadeImpl implements SampleFacade {public void doBusiness1() {// 实现业务逻辑}public void doBusiness2() {// 实现业务逻辑}// 更多业务方法的实现}```3. 配置Facade在EAS框架中，需要对Facade进行一些必要的配置，如注册到Spring容器中，进行依赖注入等操作。

ZendFramework⼊门教程⼀、Zend Framework简介1. 什么是ZendFrameworkZend Framework（ZF or ZFW）是PHP的母公司Zend公司开发的⼀套PHP开发框架技术，它提供了⼀个优秀的、简单的综合开发环境，提供了很多可⽤的解决⽅案，可以⽤来建⽴⼀个稳定的、可升级的的Web应⽤。

所谓框架，是整个或者部分系统的可重⽤设计，它⾸先要提供⼀个可复⽤的应⽤参考架构，阐明整个设计、组件之间的依赖关系、责任分配和控制流程，也包含⼀些设计规范等等。

它提供了对⼀些通⽤问题的解决⽅案。

另外Zend Framework采⽤常见的MVC模型(在后续具体介绍)，这样可以⽐较⽅便的达到关注点分离的⽬的，可以⽐较⽅便的建⽴基于MVC 架构的Web应⽤(典型的MVC Web架构还有Struct等等,它们原理都很类似)(PHP的类似框架还有很多如：yaf)2. 什么是LAMPLAMP是Linux+Apache+Mysql+Perl/PHP/Python的缩写，它们是⼀组经常⽤来搭建动态⽹站或者服务器的开源软件，本⾝都是各⾃独⽴的程序，但是因为常被放在⼀起使⽤，拥有了越来越⾼的兼容度，共同组成了⼀个强⼤的Web应⽤程序平台，由于都是开源软件，除了免费使⽤的诱惑，还有可以修改源码、⾃⼰进⾏控制等优点，LAMP是⼤多数⽹站开发者和很多⼤公司(如：Facebook和Baidu)的不⼆选择。

从⽹站的流量上来说，70%以上的访问流量是LAMP来提供的，可见LAMP是最强⼤的⽹站解决⽅案．(其它类似的⽅案如MS的.NET框架和Oracle的J2EE框架，三者同样强⼤)为什么要说LAMP呢，因为这些软件的组合强⼤到只要提到⼀个就必须要提到另外三个的地步，⽽在实验室⽹站的建设中，我们使⽤PHP，我们采取的当然也是LAMP的框架3. Zend Framework的安装XAMPP：Apache FriendsZend安装和使⽤另外需要注意的是，默认的Zend Framework使⽤MVC机制，它采⽤rewrite的⽅式进⾏跳转，这就需要在apache的配置⽂件中(⼀般是httpd.conf)修改加⼊允许rewrite的选项，需要的步骤是：1. 找到LoadModule rewrite_modulemodules/mod_rewrite.so将其前⾯的#去掉2. 在项⽬所在的⽬录下<Directory “projectPath”>中修改AllowOverride的值为All，Order allow,deny / Allow from all3. 在项⽬所在根⽬录下建⽴.htaccess⽂件，内容为RewriteEngine on #重写引擎打开RewriteRule!\.(js|ico|gif|jpg|png|css)$ index.php#制定除js,ico,gif,jpg,png,css以外的⽂件全都被重置到index.php，index.php为项⽬的⾸页(其实是前端转发控制页)简单的Zend Framework安装测试⽅法：创建⽂件test.php内容：<?phprequire_once(‘Zend/Date.php’);$date=new Zend_Date();echo $date>如果能正常输出则说明Zend安装⼤体正常。

写在前面虽说是技术手册，但是没有源码的研究就算是一个教程吧。

由于本人能力有限，文章中有很多不当之处，请各位原谅。

Bigheader联系：gdsqz2@worldwind技术手册目录：1.WorldWind软件架构――――――――――――――――０２WW功能介绍WW与XMLClient与ServerWW使用链接本地缓存路径本地功能配置http请求与aspWMS、WFS2.WorldWind金字塔体系―――――――――――――――――－０３瓦片金字塔详解及其对应公式――――――――――――――――――０３NASA World Wind Tile Structure ―――――――――――――――――０３NASA World Wind Map Tile System ――――――――――――――――０４瓦片请求调度策略―――――――――――――――――０５2.2.1 当前显示请求及其显示（客户端）――――――――――――――――――０５2.2.2目标瓦片快速搜索算法――――――――――――――――――０８2.2.3瓦片数据的请求预测（服务器）――――――――――――――――――０８2.3 可视化的地球空间数学模型――――――――――――――――――１０2.3.1 地球三维LOD模型――――――――――――――――――１０3.Geospatial image processing ――――――――――――――――――１４3.1步骤：（准备知识：LOTD：0层瓦片大小；TileSize：）―――――――――――１４3.2 NLT Landsat处理技术范例―――――――――――――１５3.3 dstile howto ―――――――――――――１５4.Creat a new world ―――――――――――――１７4.1World Wind本地文件说明4.1.1. Worlds4.1.2. 在安装目录下4.2 创建新的世界模型5.Making layer ――――――――――――――１８5.1 添加新图层(更详细可参考)5.2 Point ―――――――――――――――２０5.3 Lines ―――――――――――――――２０5.4 Polygon ―――――――――――――――２３5.5 Model Feature ―――――――――――――――２５5.6 Effects and Multi-Texturing ―――――――――――――――２７5.7 Shapefile ―――――――――――――――３２5.8 KML/KMZ6.ddons与plugins ―――――――――――――――３２addons与plugins区别插件总汇及其功能7.script脚本―――――――――――――――――３３8.编译调试―――――――――――――――――――３３9.读书籍和论文―――――――――――――――――――――３４10.1.4.1版本发展―――――――――――――――３５一、WW软件结构1.1 功能介绍World Wind(简称WW，中文有人直翻译为世界风)，是NASA发布的一个开放源代码(Open Source)的地理科普软件(由NASA Research开发，由NASA Learning Technologies來發展)，它是一个可视化地球仪，将NASA、USGS以及其它WMS服务商提供的图像通过一个三维的地球模型展现，近期还包含了月球、金星、火星、天文星系等的展现。

MAC安装hyperfHpertf ,是基于swoole开发，只能安装在类Linux 环境下，windows ⽤docker.1.环境安装时，判断PHP环境要⼤于php7.2 php -v PHP 7.4.11 (cli) (built: Oct 1 2020 18:41:10) ( NTS )php -vPHP 7.4.11 (cli) (built: Oct 1 2020 18:41:10) ( NTS )2.判断是否安装swoolephp --ri swooleExtension 'swoole' not present. 安装swoole 2.1 去GitHub 获取到最新的swoole release 地址wget https:///swoole/swoole-src/archive/refs/tags/v4.6.6.tar.gztar -xzvf v4.6.6.tar.gz ###解压cd swoole-src-4.6.6 ###进⼊swoole扩展包phpize ###编译./configure --enable-http2 --enable-openssl --with-openssl-dir=/usr/local/opt/openssl@1.1###打开http2,openssl,指定openssl安装地址。

如果不知道openssl安装地址使⽤ brew info opensslmake -j12 ####测试⼀下，看是否以后错误make install ####安装 2.2 安装到完后，把swoole加载到PHP中####php.ini⽬录在哪qutao@MacBook-Pro# php -i | grep iniConfiguration File (php.ini) Path => /usr/local/etc/php/7.4Loaded Configuration File => /usr/local/etc/php/7.4/php.ini2.3进⼊到/usr/local/etc/php/7.4/php.ini####添加以下两⾏extension="swoole.so"e_shortname = 'Off'　2.4查看swoole 安装信息####查看swoole 安装信息php --ri swoole 2.5进⼊到项⽬⽬录后，使⽤composer 创建项⽬，安装hyperf注意 ,⼀路按n 不要同意安装任何扩展composer create-project hyperf/hyperf-skeleton2.5 启动hyperf服务#启动php bin/hyperf.php start#####启动后会有以下提⽰[DEBUG] Event Hyperf\Framework\Event\AfterWorkerStart handled by Hyperf\Server\Listener\InitProcessTitleListener listener. [DEBUG] Event Hyperf\Framework\Event\AfterWorkerStart handled by Hyperf\Server\Listener\InitProcessTitleListener listener. [INFO] Worker#6 started.[INFO] Worker#7 started.2.6 打开新窗⼝看是否启动成功, 端⼝是9501curl 127.0.0.1:9501{"method":"GET","message":"Hello Hyperf."}%。

Wi-SUN SDK 1.2.1.0 GAGecko SDK Suite 4.0January 26, 2022Wireless Smart Ubiquitous Network (Wi-SUN) is the leading IPv6 sub-GHz mesh technol-Array ogy for smart city and smart utility applications. Wi-SUN brings Smart Ubiquitous Networksto service providers, utilities, municipalities/local government, and other enterprises, byenabling interoperable, multi-service, and secure wireless mesh networks. Wi-SUN canbe used for large-scale outdoor IoT wireless communication networks in a wide range ofapplications covering both line-powered and battery-powered nodes.Silicon Labs' Wi-SUN hardware is certified by the Wi-SUN Alliance, a global industry as-sociation devoted to seamless LPWAN connectivity. Wi-SUN builds upon open standardinternet protocols (IP) and APIs, enabling developers to extend existing infrastructure plat-forms to add new capabilities. Built to scale with long-range capabilities, high-datathroughput and IPv6 support, Wi-SUN simplifies wireless infrastructure for industrial ap-plications and the evolution of smart cities.These release notes cover SDK versions:1.2.1.0 released January 26, 20221.2.0.0 released December 15, 2021Compatibility and Use NoticesFor information about security updates and notices, see the Security chapter of the Gecko Platform Release notes installed with this SDK or on the Silicon Labs Release Notes page. Silicon Labs also strongly recommends that you subscribe to Security Advisories for up-to-date information. For instructions, or if you are new to the Silicon Labs Wi-SUN SDK, see Using This Release.Compatible Compilers:IAR Embedded Workbench for ARM (IAR-EWARM) version 8.50.9•Using wine to build with the IarBuild.exe command line utility or IAR Embedded Workbench GUI on macOS or Linux could result in incorrect files being used due to collisions in wine’s hashing algorithm for generating short file names.•Customers on macOS or Linux are advised not to build with IAR outside of Simplicity Studio. Customers who do should carefully verify that the correct files are being used.GCC (The GNU Compiler Collection) version 10.2.1, provided with Simplicity Studio.Contents Contents1Wi-SUN Stack (2)1.1New Items (2)1.2Improvements (2)1.3Fixed Issues (2)1.4Known Issues in the Current Release (3)1.5Deprecated Items (3)1.6Removed Items (3)2Wi-SUN Applications (4)2.1New Items (4)2.2Improvements (4)2.3Fixed Issues (4)2.4Known Issues in the Current Release (4)2.5Deprecated Items (4)2.6Removed Items (5)3Using This Release (6)3.1Installation and Use (6)3.2Security Information (6)3.3Support (7)1 Wi-SUN Stack1.1 New ItemsAdded in release 1.2.0.0•Added release quality libraries. They provide the same Wi-SUN features but are not logging anything.•Added a new API sl_wisun_reset_statistics that resets all the counters read by calling sl_wisun_get_statistics.•Added new APIs sl_wisun_get_neighbor_count() and sl_wisun_get_neighbors() that indicate the neighbor count (par-ents and children) and their MAC address.•Added a new API sl_wisun_get_neighbor_info() that returns information about a neighbor.•Added a new API sl_wisun_set_unicast_settings() that configures the frequency hopping unicast dwell interval. •Added a new API sl_wisun_set_trace_level() and sl_wisun_set_trace_filter() that configure the stack traces.1.2 ImprovementsAdded in release 1.2.1.0•Reduced the stack log verbosityAdded in release 1.2.0.0•Added support for mbedtls v3.0•Stack flash footprint reduction1.3 Fixed IssuesFixed in release 1.2.1.0756339 Fixed an error that could cause the stack to assert on a RAIL_StartCcaCsmaTx when trying to connect to a network that cannot be reached. The stack MAC was unnecessarily re-initialized in the timeout routine and wasinvalidating some internal status.778492 Fixed a build issue that caused the stack entropy source to malfunction.Fixed in release 1.2.0.0752766 Reworked Wi-SUN stack tasks priorities. A race between an interruption routine and a task was causing intempestive connection losses when using FreeRTOS.750407 Fixed the unicast channel filtering. Under certain conditions, a bit-order conversion was missing and was allowing forbidden channels to be used to transmit.731225 Fixed an error causing the authentication waiting list to be broken. It was causing the authentication of new devices to be significantly slower when connecting a few dozen in parallel.1.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release.773952 The stack randomly asserts on RAIL_StartCcaCsmaTx. It seems to occur more often when the communication between the faulty device and itsneighbors is non-optimal.1.5 Deprecated ItemsNone1.6 Removed ItemsNone2 Wi-SUN Applications2.1 New ItemsAdded in release 1.2.0.0BRD4002A SupportNew Applications:•Wi-SUN - SoC Network Measurement•Wi-SUN - SoC RCP. Used by the border router reference design2.2 ImprovementsChanged in release 1.2.0.0•Major refactor at the Application Framework•More granular components (OR relationship)•Wi-SUN SDK - Application Core•Wi-SUN SDK - POSIX-compliant Socket•Wi-SUN SDK - Application CLI•Wi-SUN SDK - Ping•Wi-SUN SDK - Event Manager•CoAP PUT request to LED toggle•Nanostack dependency removal•Wi-SUN SoC Border Router: added new CLI commands to configure the frequency hopping unicast and broadcast intervals.•Wi-SUN SoC CLI: added new CLI commands to read neighbors’ information, configure the stack traces and the frequency hopping unicast interval, and reset the stack statistics.2.3 Fixed IssuesFixed in release 1.2.1.0759495 Added concurrent access protection onto the Linux border router RCP host interface transmit function. On rare occasions, concurrent was causing CRC errors.758848 Added concurrent access protection onto Wi-SUN CLI application console write function. On rare occasions, concurrent access was causing requests, confirmation, and indication messages to be mixed.2.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release.Simplicity Studio – Network Analyzer: Wi-SUN Encrypted Packets arenot supported yet.2.5 Deprecated ItemsNone2.6 Removed Items•Wi-SUN - SoC Border Router with backhaul.3 Using This ReleaseThis release contains the following•Wi-SUN stack library•Wi-SUN sample applications•Wi-SUN border router pre-compiled demos•DocumentationIf you are a first time user, see QSG181: Silicon Labs Wi-SUN Quick-Start Guide.3.1 Installation and UseThe Wi-SUN SDK is provided as part of the Gecko SDK (GSDK), the suite of Silicon Labs SDKs. To quickly get started with the GSDK, install Simplicity Studio 5, which will set up your development environment and walk you through GSDK installation. Simplicity Studio 5 includes everything needed for IoT product development with Silicon Labs devices, including a resource and project launcher, software configuration tools, full IDE with GNU toolchain, and analysis tools. Installation instructions are provided in the online Simplicity Studio 5 User’s Guide.Alternatively, Gecko SDK may be installed manually by downloading or cloning the latest from GitHub. See https:///Sili-conLabs/gecko_sdk for more information.Simplicity Studio installs the GSDK by default in:•(Windows): C:\Users\<NAME>\SimplicityStudio\SDKs\gecko_sdk•(MacOS): /Users/<NAME>/SimplicityStudio/SDKs/gecko_sdkDocumentation specific to the SDK version is installed with the SDK.3.2 Security InformationSecure Vault IntegrationThis version of the stack does not integrate Secure Vault Key Management.Security AdvisoriesTo subscribe to Security Advisories, log in to the Silicon Labs customer portal, then select Account Home. Click HOME to go to the portal home page and then click the Manage Notifications tile. Make sure that ‘Software/Security Advisory Notices & Product Change Notices (PCNs)’ is checked, and that you are subscribed at minimum for your platform and protocol. Click Save to save any changes.3.3 SupportDevelopment Kit customers are eligible for training and technical support. Contact Silicon Laboratories support at /support.Silicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USA IoT Portfolio /IoT SW/HW /simplicity Quality /quality Support & Community /communityDisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software imple-menters using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and “Typical” parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the infor -mation supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A “Life Support System” is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications. Note: This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit /about-us/inclusive-lexicon-projectTrademark InformationSilicon Laboratories Inc.®, Silicon Laboratories ®, Silicon Labs ®, SiLabs ® and the Silicon Labs logo ®, Bluegiga ®, Bluegiga Logo ®, EFM ®, EFM32®, EFR, Ember ®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals ®, WiSeConnect , n-Link, ThreadArch ®, EZLink ®, EZRadio ®, EZRadioPRO ®, Gecko ®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio ®, Telegesis, the Telegesis Logo ®, USBXpress ® , Zentri, the Zentri logo and Zentri DMS, Z-Wave ®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.。

Compass技术文档目录一、原理描述：.................................................................................................................................二、术语解释：.................................................................................................................................三、下载地址：.................................................................................................................................四、使用流程: …………………………………………………………………………………….五、基于SSH的compass的实例: …………………………………………………………………一、原理描述：Compass是一流的开放源码JAVA搜索引擎框架，对于你的应用修饰，搜索引擎语义更具有能力。

依靠顶级的Lucene搜索引擎，Compass 结合了，像Hibernate和Spring的流行的框架，为你的应用提供了从数据模型和数据源同步改变的搜索力.并且添加了2方面的特征,事物管理和快速更新优化.Compass的目标是：把java应用简单集成到搜索引擎中.编码更少，查找数据更便捷.二、术语解释：三、下载地址：四、使用流程:五、基于SSH的compass的实例:step1在ssh2的基础上开发加入jar包（compass-2.1.2.jar compass-index-patch.jarlucene-analyzers-2.4.0.jar lucene-core-2.4.0.jar lucene-highlighter-2.4.0.jar paoding-analysis.jar）step2先来看下实体bean的编写Java代码1.package com.v512.example.model;2.import pass.annotations.*;3./**4. * Product entity.5. *6. * @author MyEclipse Persistence Tools7. */8.@Searchable9.public class Product implements java.io.Serializable {10.11. // Fields13. @SearchableId14. private String id;15. @SearchableProperty(name="name",index=Index.ANALYZED,store=Store.YES)16. private String name;17. @SearchableProperty(name="price",index=Index.NOT_ANALYZED,store=Store.YES)18. private Double price;19. @SearchableProperty(name="brand",index=Index.ANALYZED,store=Store.YES)20. private String brand;21. @SearchableProperty(name="description",index=Index.ANALYZED,store=Store.YES)22. private String description;23.24. // Constructors25.26. /** default constructor */27. public Product() {28. }29.30. /** full constructor */31. public Product(String name, Double price, String brand, String description) {32. = name;33. this.price = price;34. this.brand = brand;35. this.description = description;36. }37.38. // Property accessors39.40. public String getId() {41. return this.id;42. }43.44. public void setId(String id) {45. this.id = id;46. }47.48. public String getName() {49. return ;50. }52. public void setName(String name) {53. = name;54. }55.56. public Double getPrice() {57. return this.price;58. }59.60. public void setPrice(Double price) {61. this.price = price;62. }63.64. public String getBrand() {65. return this.brand;66. }67.68. public void setBrand(String brand) {69. this.brand = brand;70. }71.72. public String getDescription() {73. return this.description;74. }75.76. public void setDescription(String description) {77. this.description = description;78. }79.80.}step3属性文件Product.hbm.xmlJava代码1.<?xml version="1.0" encoding="utf-8"?>2.<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN"3."/hibernate-mapping-3.0.dtd">4.<!--5. Mapping file autogenerated by MyEclipse Persistence Tools6.-->7.<hibernate-mapping>8. <class name="com.v512.example.model.Product" table="PRODUCT" >9. <id name="id" type="ng.String">10. <column name="ID" length="40" />11. <generator class="uuid.hex" />12. </id>13. <property name="name" type="ng.String">14. <column name="NAME" length="80" />15. </property>16. <property name="price" type="ng.Double">17. <column name="PRICE" precision="6" />18. </property>19. <property name="brand" type="ng.String">20. <column name="BRAND" length="40" />21. </property>22. <property name="description" type="ng.String">23. <column name="DESCRIPTION" length="2000" />24. </property>25. </class>26.</hibernate-mapping>要使用Compass必须加入一个applicationContext-compass.xml文件，文件名可以自行定义这个就不用说了废话step4applicationContext-compass.xml：Java代码1.<?xml version="1.0" encoding="UTF-8"?>2.3.<beans xmlns="/schema/beans"4. xmlns:xsi="/2001/XMLSchema-instance"5. xsi:schemaLocation=" /schema/beans /schema/beans/spring-beans -2.5.xsd"6. default-lazy-init="true">7.8. <!-- 配置compass的注解功能 -->9. <bean id="annotationConfiguration"10. class="passAnnotationsConfiguration">11. </bean>12.13.14. <bean id="compass" class="pass.spring.LocalCompassBean">15. <!-- 配置需要索引的实体映射文件的路径 -->16. <property name="resourceDirectoryLocations">17. <list>18. <value>classpath:com/v512/example/model</value>19. </list>20. </property>21. <!-- 设置存放索引的路径 -->22. <property name="connection">23. <value>/lucene/indexes</value>24. </property>25.26. <!--配置要搜索的类，作用：会根据以下的类建立索引 -->27. <property name="classMappings">28. <list>29. <value>com.v512.example.model.Product</value>30. </list>31. </property>32. <property name="compassConfiguration"33. ref="annotationConfiguration" />34.35. <!--compass的一些属性设置 -->36. <property name="compassSettings">37. <props>38. <prop key="compass.transaction.factory">39. pass.spring.transaction.SpringSyncTransactionFactory40. </prop>41. <prop key="compass.engine.analyzer.MMAnalyzer.CustomAnalyzer">net.paoding.analysis.analyzer.PaodingAnalyzer </prop>42. </props>43. </property>44. <!--compass的事务管理器 -->45. <property name="transactionManager" ref="transactionManager" />46. </bean>47.48.49. <bean id="hibernateGpsDevice"50. class="pass.gps.device.hibernate.HibernateGpsDevice">51. <property name="name">52. <value>hibernateDevice</value>53. </property>54. <property name="sessionFactory" ref="sessionFactory" />55. <property name="mirrorDataChanges">56. <value>true</value>57. </property>58. </bean>59. <!-- 同步更新索引 -->60. <bean id="compassGps" class="pass.gps.impl.SingleCompassGps"61. init-method="start" destroy-method="stop">62. <property name="compass" ref="compass" />63. <property name="gpsDevices">64. <list>65. <bean66. class="pass.spring.device.SpringSyncTransactionGpsDeviceWrapper">67. <property name="gpsDevice" ref="hibernateGpsDevice" />68. </bean>69. </list>70. </property>71. </bean>72.73.74. <bean id="compassTemplate"75. class="passTemplate">76. <property name="compass" ref="compass" />77. </bean>78.79. <!-- 定时重建索引(利用quartz)或随Spring ApplicationContext启动而重建索引 -->80. <bean id="compassIndexBuilder"81. class="passIndexBuilder"82. lazy-init="false">83. <property name="compassGps" ref="compassGps" />84. <property name="buildIndex" value="true" />85. <property name="lazyTime" value="10" />86. </bean>87.88.89.90.</beans>中间都有注解就不多解释了下面来编写dao及dao的实现以及severce层step5Java代码1.package com.v512.example.dao;2.3.import java.util.List;4.5.import com.v512.example.model.Product;6.7.public interface ProductDao {8. public void create(Product p);9. public Product getProduct(String id);10. public List getProducts();11. public void update(Product product);12. public void remove(String id);13.14.}Java代码1.package com.v512.example.dao.hibernate;2.3.import java.util.List;4.5.import com.v512.example.dao.ProductDao;6.import com.v512.example.model.Product;7.import org.springframework.orm.hibernate3.support.HibernateDaoSupport;8.public class ProductDaoHibernate extends HibernateDaoSupport implements ProductDao {9.10. public void create(Product p) {11. getHibernateTemplate().save(p);12.13. }14.15. public Product getProduct(String id) {16. return (Product)getHibernateTemplate().get(Product.class, id);17. }18.19. public List getProducts() {20. return getHibernateTemplate().find("from Product order by id desc");21. }22.23. public void remove(String id) {24. getHibernateTemplate().delete(getProduct(id));25.26. }27.28. public void update(Product product) {29. getHibernateTemplate().saveOrUpdate(product);30.31. }32.33.}serveceJava代码1.package com.v512.example.service;2.3.import java.util.List;4.5.import com.v512.example.model.Product;6.7.public interface ProductManager {8. public void insertProduct(Product p);9. public Product findProdcut(String id);10. public List searchProducts(String queryString);11.12.13.}servece的实现Java代码1.package com.v512.example.service.impl;2.3.import java.util.ArrayList;4.import java.util.List;5.6.import passHits;7.import passSession;8.import passTemplate;9.import passTransaction;10.11.import com.v512.example.dao.ProductDao;12.import com.v512.example.model.Product;13.import com.v512.example.service.ProductManager;14.import pass;15.public class ProductManagerImpl implements ProductManager {16. private ProductDao productDao;17. private CompassTemplate compassTemplate;18.19.20.21.22. public void setCompassTemplate(CompassTemplate compassTemplate){23. passTemplate=compassTemplate;24. }25.26. public void setProductDao(ProductDao productDao){27. this.productDao=productDao;28. }29.30. public Product findProdcut(String id) {31. return productDao.getProduct(id);32. }33.34. public void insertProduct(Product p) {35. productDao.create(p);36. }37.38. public List searchProducts(String queryString) {39. Compass compass = compassTemplate.getCompass();40. CompassSession session=compass.openSession();41. List list = new ArrayList();42. //这里不需要开启事务了，因为在调用这个方法之前就已经开启了事务43. CompassHits hits= session.queryBuilder().queryString("name:"+queryString).toQuery().hits();44. System.out.println("queryString:"+queryString);45. System.out.println("hits:"+hits.getLength());46. for(int i=0;i<hits.length();i++){47. Product hit=(Product)hits.data(i);48. list.add(hit);49. }50.51. return list;52. }53.54.55.56. public CompassTemplate getCompassTemplate() {57. return compassTemplate;58. }59.60.}所有的都做完了现在编写jsp页面step6insertProduct.jspJava代码1.<%@ page language="java" contentType="text/html; charset=UTF-8"2. pageEncoding="UTF-8"%>3.<%@ taglib prefix="s" uri="/struts-tags"%>4.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""/TR/html4/loose.dtd">5.<html>6.<head>7.<meta http-equiv="Content-Type" content="text/html; charset=utf-8">8.<link href="style/oa.css" rel="stylesheet" type="text/css"> 9.10.<title>添加信息</title>11.</head>12.<body>13.<center>14. <s:form action="insert.action" theme="simple">15.16.<TABLE class="tableEdit" border="0" cellspacing="1" cellpadding="0" style="width:300px;">17. <TBODY>18. <TR>19. <td align="center" class="tdEditTitle">添加商品名称</TD>20. </TR>21. <TR>22. <td>23.24.25.<table class="tableEdit" style="width:300px;" cellspacing="0" border="0" cellpadding="0">26. <tr>27. <td class="tdEditLabel" >商品名称</td>28. <td class="tdEditContent"><s:textfield name="product.name" label="名称" /></td>29. </tr>30.31. <tr>32. <td class="tdEditLabel" >商品品牌</td>33. <td class="tdEditContent"><s:textfield name="product.brand" label="品牌" /></td>34. </tr>35.36. <tr>37. <td class="tdEditLabel" >商品价格</td>38. <td class="tdEditContent"><s:textfield name="product.price" label="价格" /></td>39. </tr>40.41. <tr>42. <td class="tdEditLabel" >商品描述</td>43. <td class="tdEditContent"><s:textarea name="product.description" label="描述" />44. </td>45. </tr>46. <tr>47. <td>&nbsp;48. </td>49. <td><s:submit/>50. <br></td>51. </tr>52.</table>53. </td>54. </TR>55. </TBODY>56.</TABLE>57.</s:form>58.</center>59.</body>60.</html>step7编写actionJava代码1.package com.v512.example.action;2.3.import java.util.List;4.5.import com.opensymphony.xwork2.ActionSupport;6.import com.v512.example.model.Product;7.import com.v512.example.service.ProductManager;8.import org.apache.struts2.ServletActionContext;9.10.public class ProductAction extends ActionSupport {11.12. private static final long serialVersionUID = 3795048906805728732L;13. private ProductManager productManager;14. private Product product;15. private String queryString;16.17. public void setQueryString(String queryString){18. this.queryString=queryString;19. }20.21. public Product getProduct() {22. return product;23. }24.25. public void setProduct(Product product) {26. this.product = product;27. }28.29. public void setProductManager(ProductManager productManager){30. this.productManager=productManager;31. }32.33. public String insert(){34. productManager.insertProduct(product);35. return SUCCESS;36. }37. public String search(){38. List results=productManager.searchProducts(queryString);39. System.out.println(results.size());40. ServletActionContext.getRequest().setAttribute("searchresults", results);41. return SUCCESS;42. }43.44.45.}step8关于Struts2的配置文件如下Java代码1.<?xml version="1.0" encoding="UTF-8" ?>2.<!DOCTYPE struts PUBLIC3. "-//Apache Software Foundation//DTD Struts Configuration 2.0//EN"4. "/dtds/struts-2.0.dtd">5.6.<struts>7. <constant name="struts.objectFactory" value="spring" />8.9. <include file="struts-default.xml"/>10.11. <package name="product" extends="struts-default"12. namespace="/product">13.14. <!-- 配置Struts2的Action，class值要与applicationContext*.xml中的id的值一致。

wamp中zendframwork、pear、phpUnit、Smarty安装与配置安装WampServer下载WAMPSERVER并安装，在本例中，安装目录为C:\wamp，即选择C盘安装。

对wampserve 的安装在此就不做说明了。

第一部分zendframwork安装1.下载zendframwork最好下载解压的bin文件夹中包含zf.bat文件的zend framwork压缩包解压至C:\wamp\library\zendframwork(library为自己新建，其实也可以安装在其他新建的文件夹，此处是方便管理，zendframework文件夹下面为全部子文件夹，一般这个文件夹为重新命名的。

)2.开启支持rewrite module编辑httpd.conf。

- 编辑C:\wamp\bin\apache\Apache2.2.10\conf\httpd.conf 文件。

或- 右击托盘里WampServer小图标--> Apache --> httpd.conf# LoadModule rewrite_module modules/mod_rewrite.so去掉'#'，改为：LoadModule rewrite_module modules/mod_rewrite.so同时修改所有的AllowOverride None 为AllowOverride All3.PHP library 设置- 编辑C:\wamp\bin\php\php5.2.7\php.ini，或- 右击托盘里WampServer小图标--> PHP --> php.ini; Windows: "\path1;\path2"; include_path = ".;c:\php\includes"去掉';'，并且加上Zend Framework 压缩包安装路径，改为：; Windows: "\path1;\path2"include_path = ".;c:\php\includes; C:\wamp\library\ZendFramework\library"4.配置虚拟环境在统环境变量Path末尾加;C:\wamp\library\ZendFramework\bin;C:\wamp\bin\php\php5.4.3;(因为要用到php.exe和zf.bat)5.创建Project在C:\wamp\www文件夹下新建文件夹test打开命令输入框（运行：cmd）,输入zf create project C:\wamp\www\test即创建完成6.配置虚拟主机2中rewrite module已经开启了，接着修改httpd.conf将# Virtual hosts#Include conf/extra/httpd-vhosts.conf修改为# Virtual hosts#Include conf/extra/httpd-vhosts.conf （即去掉#）打开C:\wamp\bin\apache\apache2.2.22\conf\extra中的httpd-vhosts.conf文件，在其后面添加：<VirtualHost *:80>DocumentRoot "C:/wamp/www/test/public" （新建工程public路径）ServerName （为自定义）DirectoryIndex index.php （还可以加入index.html等首页）<Directory />Options Indexes FollowSymLinksAllowOverride None（我的配置时此处为None才行，我不是很理解）Order allow,denyAllow from all</Directory></VirtualHost>接着配置C:\WINDOWS\system32\drivers\etc中hosts文件，在其尾部加上127.0.0.1 (前面设置保持一致)至此设置好之后重启wamp,浏览器中输入即可见第二部分pear安装（推荐浏览/2012/04/04/在-wampserver-安裝-pear/?utm_source=rss）我就是参照这个的，挺详细的。

XAF学习1.总览场景一：从头编写场景二：购买成熟的系统场景三：使用XAFXAF是用于从头开发一个应用。

但是，XAF技术能够实现如下目标：•可以开发不同平台的应用（Winform和Webform），并且对于相同的业务逻辑能够容易实现复用。

•提供数据到UI的构造算法。

这样可以使你不需要手工建立很多相同的，用于数据浏览和编辑的界面。

而且使应用程序的维护变得简单，因为如果你改变数据定义，系统会自动更新这些界面。

•隐藏数据管理细节。

你不需要处理任何DBMS或者使用去管理数据。

XAF向你提供一个数据管理的有效工具。

这个工具可以很容易把你的数据存储到主流的DBMS，即使你不是很熟悉这些DBMS。

同时，你也很容易切换数据库管理系统。

•对于建立那种存储和查看数据的业务应用系统，使用XAF就会非常的简单。

•XAF应用程序可以使用.NET的任一语言进行开发。

还有两个功能，是你使用XAF能得到的好处：•容易扩展。

•系统主要部分的质量可以保证。

其中，XPO是一种面向对象的数据库工具，以及可视化组件都是使用DXperience的主要产品。

所以，相关产品都是经过验证可以信赖的。

2.基本原理2.1.应用程序解决方案组件2.2.将XAF应用程序连接到数据库2.3.使用中间层应用程序服务器2.4.建立和更新应用程序数据库3.教程3.1.业务模型设计3.1.1.建立和运行一个新方案F IGURE 3-13.1.2.从业务类库中继承F IGURE 3-2更新如下代码：[DefaultClassOptions]public class Contact : Person{private string webPageAddress;private string nickName;private string spouseName;private TitleOfCourtesy titleOfCourtesy;private string notes;private DateTime anniversary;public Contact(Session session) : base(session) { }public string WebPageAddress{get { return webPageAddress; }set { SetPropertyValue("WebPageAddress", ref webPageAddress, value); } }public string NickName{get { return nickName; }set { SetPropertyValue("NickName", ref nickName, value); } }public string SpouseName{get { return spouseName; }set { SetPropertyValue("SpouseName", ref spouseName, value); } }public TitleOfCourtesy TitleOfCourtesy{get { return titleOfCourtesy; }set { SetPropertyValue("TitleOfCourtesy", ref titleOfCourtesy, value); } }public DateTime Anniversary{get { return anniversary; }set { SetPropertyValue("Anniversary", ref anniversary, value); } }[Size(4096)]public string Notes{get { return notes; }set { SetPropertyValue("Notes", ref notes, value); }}}public enum TitleOfCourtesy { 博士, 小姐, 先生, 夫人, 女士};注：Contact类的扩展属性DefaultClassOptionsAttribute，即[DefaultClassOptions]•Contact类会显示在主页面左侧的浏览菜单项。

Bluetooth ® SDK 2.12.2.0 GA19Q2 Gecko SDK Suite August 16, 2019Silicon Labs is a leading vendor in Bluetooth hardware and software technologies, used in products such as sports and fitness, consumer electronics, beacons, and smart home applications. The core SDK is an advanced Bluetooth 5-compliant stack that provides all of the core functionality along with multiple API to simplify development. The core func-tionality offers both standalone mode allowing a developer to create and run their appli-cation directly on the SoC, or in NCP mode allowing for the use of an external host MCU. Extensions to the SDK include Bluetooth Mesh and Apple ® HomeKit ® for customers seek-ing the additional capabilities.These release notes cover SDK version(s): 2.12.2.0 released on August 16, 2019 2.12.1.0 released on July 19, 2019 2.12.0.0 released on June 7, 2019Compatibility and Use NoticesIf you are new to the Silicon Labs Bluetooth SDK, see Using This Release . Compatible Compilers:IAR Embedded Workbench for ARM (IAR-EWARM) version 8.30.1• Using w ine to build with the IarBuild.exe command line utility or IAR Embedded Workbench GUI on macOS or Linux could result inincorrect files being used due to collisions in wine’s hashing algorithm for generating short file names. • Customers on macOS or Linux are advised not to build with IAR outside of Simplicity Studio. Customers who do should carefullyverify that the correct files are being used. GCC (The GNU Compiler Collection) version 7.2.1, provided with Simplicity Studio.KEY FEATURESAdded support for new parts [B|M]GM210PContents Contents1New Items (3)1.1New Features (3)1.2New APIs (3)2Improvements (4)2.1Changed APIs (4)3Fixed Issues (5)4Known Issues in the Current Release (6)5Deprecated Items (7)6Removed Items (8)7Using This Release (9)7.1Installation and Use (9)7.2Support (9)8Legal (10)8.1Disclaimer (10)8.2Trademark Information (10)New Items 1 New ItemsGecko Platform release notes are now available through Simplicity Studio’s Launcher Perspective, under SDK Documentation > Blue-tooth SDK 2.12.n.n > Release Notes. The Gecko Platform code provides functionality that supports protocol plugins and APIs in the form of drivers and other lower layer features that interact directly with Silicon Labs chips and modules. Gecko Platform components include EMLIB, EMDRV, RAIL Library, NVM3, and mbedTLS.1.1 New FeaturesAdded in release 2.12.2.0PHY settings on a Bluetooth connectionThis feature allows the application to set preferred PHYs the stack should take into account in PHY selection, and the PHYs the stack can accept when the remote device initiates a PHY update.Added in release 2.12.0.0Advertising packet chainingWith this feature, the total amount of advertising data in an advertising packet can be up to 1650 bytes in extended advertising.1.2 New APIsFor additional documentation and command descriptions please refer to the Bluetooth Software API Reference Manual.Added in release 2.12.2.0cmd_le_gap_set_conn_phycmd_le_connection_set_preferred_phyAdded in release 2.12.0.0cmd_gatt_server_set_max_mtucmd_le_connection_set_timing_parameterscmd_le_gap_set_conn_timing_parameterscmd_le_gap_set_long_advertising_datacmd_sm_set_minimum_key_sizecmd_system_data_buffer_writecmd_system_data_buffer_clearImprovements 2 Improvements2.1 Changed APIsChanged in release 2.12.0.0cmd_le_gap_bt5_set_adv_dataRemoved the 191 bytes advertising data limitation for extended advertising.cmd_le_gap_set_adv_dataRemoved the 191 bytes advertising data limitation for extended advertising.evt_le_gap_extended_scan_responseAdded new value in packet_type parameter for data incomplete status.evt_le_gap_scan_responseAdded new value in packet_type parameter for data incomplete status.evt_sync_dataAdded new value in data_status parameter for data incomplete status.Fixed Issues 3 Fixed IssuesFixed in release 2.12.2.05701 Fix the voice_over_ble Thunderboard example to dynamically perform GATT service discovery for using correct handles to read characteristic values.6349 More fixes for the disconnection issue caused by connection updates with certain parameters.6581 Fix NCP wake-up pin polarity handling (NCP_WAKEUP_POLARITY), so that the defined polarity is taken into account. 6585 Fix the usage of HFXO calibration values for xGM210 modules to avoid reading incorrect calibration values at initialization time.Fixed in release 2.12.1.05942Fix unstable connection issue while the master device has multiple simultaneous connections and is performing scanning. 5943 Fix an issue that the stack may return the link layer procedure response timeout error when closing a Bluetooth connec-tion.6136 After advertising is started the stack will send the first advertisement straight away. Previously it might send it after the first advertisement interval has elapsed.6349 Fix disconnection issue when performing connection update with slave latency and specific interval parameters.6375 Apploader can now write images right up to the NVM start address.6458 Fix missing ADI field in chained advertisement packets.6465 The stack can now handle 255 bytes data in cmd_system_data_buffer_write command.6475 Periodic advertising data can now be set in stack when the periodic advertising has not been started. Previously this command returns an error.6501 The stack now blocks the example LTK in Bluetooth specification if sent by the other device. This security improvement addresses vulnerability CVE-2019-2102.6502 Fix default RF antenna pin selection for EFR32xG21 parts, radio boards and xGM210 modules.6520 If advertising single event at a time, the stack does not check anymore if packet length would exceed advertising interval.Previously packet_too_long error would have been returned.6532 The stack ensures that the GATT database hash value is calculated when it is first read by commandgecko_cmd_gatt_server_read_attribute_value. Previously an incorrect value might be returned in this case. Additionallythe fix also prevents from overwriting the hash value with gecko_cmd_gatt_server_write_attribute_value.6542 A change was introduced in version 2.12.0 which caused compatibility issues with TB Sense mobile app. This change was reversed to fix those issues and it will be reintroduced when board detection gets improved on the TB Sense mobile appside.Fixed in release 2.12.0.03414 In Bluetooth SDK 2.11.4 and 2.11.5, occasionally the stack is unable to receive all GATT write without response or charac-teristic value notification PDUs.4559 Deleting the bonding of a device while the device is still connected causes the stack using outdated bonding data on the connection. This has been fixed so that the connection is also closed after the bonding has been deleted.5940 The application cannot configure the maximum ATT MTU if GATT client is excluded. This has been fixed by adding a new equivalent API in GATT server class.6051 When Bluetooth runs in RTOS, the stack initialization may cause assertions.6135 Advertising could not be restarted if a timeout has been set previously.6189 Increasing security on a connection with previously bonded devices may fail.6279 The stack does not correctly inform the application about ATT MTU size change if the remote device first denies the stack’s ATT MTU exchange request and then initiates another ATT MTU exchange request.Known Issues in the Current Release 4 Known Issues in the Current ReleaseIssues in bold were added since the previous release.1835 With certain events, GCC breakpoints cannot be set. Change optimization level to none in projectsettings4521 Command gecko_cmd_gatt_discover_primary_services_by_uuidreturns success in case of incomplete parameters.None5390 The sync_data event does not report TX power. None3530 The radio on EFR32xG13 parts could become unresponsivewhen the RSSI is low in a Bluetooth connection. The typicalbehavior is the connection has lost but le_connection_closedevent was not received.None6567 In Bluetooth SDK 2.12.0, 2.12.1 and 2.12.2, EFR32xG13 partshave an IOP problem with multiple smartphones thatconnection requests from these phones are often not received.This issue causes connections taking too long to establish.None6586 With iPhone6, the stack could become unresponsive if it is sending lots of data using characteristic notifications to thephone. In application, do not use a loop waiting for the success of sending characteristic notification operation. When an out of memory error is received from this operation, a timer should be used to retry the operation later.Deprecated Items 5 Deprecated ItemsDeprecated in release 2.12.2.0Deprecated APIscmd_le_connection_set_phyThe replacement is cmd_le_connection_set_preferred_phy.Deprecated in release 2.12.1.0Deprecated item: EFR32BG14 Part SupportReason: The EFR32BG14 is EOL.End-of-Service (EoS) Date: June 2020. As of this EoS date, EFR32BG14 part support will no longer be available in the then current and future GSDK releases, and EFR32BG14 parts will no longer be supported in any GSDK releases.Maintenance Period: From now until the EoS date, only critical bug fixes and security patches may be made available on currently supported GSDK releases.Replacement: EFR32BG13.Deprecated in release 2.12.0.0As of June 2019 Simplicity Studio 3.0 is being deprecated. All access will be removed from Silicon Labs' website at the end of 2019. Deprecated APIscmd_le_gap_set_conn_parametersThe replacement is cmd_le_gap_set_conn_timing_parameters.cmd_le_connection_set_parametersThe replacement is cmd_le_connection_set_timing_parameters.Removed Items 6 Removed ItemsNoneUsing This Release 7 Using This ReleaseThis release contains the following•Silicon Labs Bluetooth stack library•Bluetooth sample applicationsFor more information about the Bluetooth SDK see QSG139: Getting Started with Bluetooth® Software Development. If you are new to Bluetooth see UG103.14: Bluetooth LE Fundamentals.7.1 Installation and UseA registered account at Silicon Labs is required in order to download the Silicon Labs Bluetooth SDK. You can register at https:///apex/SL_CommunitiesSelfReg?form=short.Stack installation instruction are covered in QSG139: Getting Started with Bluetooth® Software Development.Use the Bluetooth SDK with the Silicon Labs Simplicity Studio V4 development platform. Simplicity Studio ensures that most software and tool compatibilities are managed correctly. Install software and board firmware updates promptly when you are notified. Documentation specific to the SDK version is installed with the SDK. Additional information can often be found in the knowledge base articles (KBAs). API references and other information about this and earlier releases is available on https:///.7.2 SupportDevelopment Kit customers are eligible for training and technical support. You can use the Silicon Labs Bluetooth LE web page to obtain information about all Silicon Labs Bluetooth products and services, and to sign up for product support.You can contact Silicon Laboratories support at /support.Legal 8 Legal8.1 DisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications.Application examples described herein are for illustrative purposes only.Silicon Labs reserves the right to make changes without further notice and limitation to product information, specifications, and descrip-tions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.8.2 Trademark InformationSilicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, ISOmodem®, Micrium, Preci-sion32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress®, Zentri, Z-Wave and others are trade-marks or registered trademarks of Silicon Labs.ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings.Keil is a registered trademark of ARM Limited.Apple and HomeKit are registered trademarks of Apple Inc. All other products or brand names mentioned herein are trademarks of their respective holders.。

安裝指南SolidWorks Enterprise PDM 2013內容法律注意事項 (7)1SolidWorks Enterprise PDM安裝指南 (10)2安裝概要 (11)必要安裝元件 (11)可選安裝元件 (12)Enterprise PDM部署案例 (12)系統需求 (14)安裝摘要 (14)安裝協助 (15)3安裝與組態SQL Server (16)SQL Server2012支援 (16)安裝SQL Server2008 (16)安裝SQL Server2008之前 (17)執行SQL Server2008安裝 (17)安裝SQL Server2008之後 (20)確認是否正確安裝SQL Server2008 (20)升級至SQL Server2008 (20)執行升級至SQL Server2008 (21)升級至SQL Server2008之後 (22)安裝SQL Server2005 (23)安裝SQL Server2005之前 (23)執行SQL Server2005安裝 (23)安裝SQL Server2005之後 (25)確認是否正確安裝SQL Server2005 (26)升級至SQL Server2005 (26)升級至SQL Server2005之前 (26)執行升級至SQL Server2005 (26)升級至SQL Server2005之後 (28)安裝SQL Server2005Service Pack (28)決定目前安裝的SQL Server2005版本 (29)取得SQL Server2005Service Pack (29)準備安裝SQL Server2005Service Pack (29)安裝SQL Server2005Service Pack (30)SQL Server疑難排解 (31)客戶端無法在檔案資料保險箱中工作 (31)Enterprise PDM管理功能發生故障 (31)Enterprise PDM無法連接至伺服器 (31)變更Enterprise PDM使用的SQL Server登入帳戶 (32)產生新的SQL登入帳戶 (32)在Enterprise PDM保存檔上使用新的SQL登入： (32)給予SQL使用者對現有Enterprise PDM檔案資料保險箱資料庫的db_owner存取權限 (33)不足的SQL權限 (33)4安裝SolidWorks Enterprise PDM (35)初始化Enterprise PDM的安裝 (35)安裝SolidWorks Enterprise PDM資料庫伺服器 (36)安裝資料庫伺服器之前 (37)執行資料庫伺服器安裝 (37)安裝SolidWorks Enterprise PDM保存檔伺服器 (38)安裝保存檔伺服器之前 (38)執行保存檔伺服器安裝 (39)開啟客戶端/伺服器通訊的連接埠 (43)在Windows Vista上執行保存檔伺服器 (43)在WAN環境中新增保存檔伺服器 (44)安裝SolidWorks Enterprise PDM Web伺服器 (45)安裝SolidWorks Enterprise PDM客戶端 (45)安裝客戶端之前 (46)使用安裝精靈安裝客戶端 (47)啟用記錄以排解安裝問題 (47)產生Enterprise PDM客戶端管理安裝點 (48)使用Windows Active Directory部署客戶端 (49)在部署Enterprise PDM時啟用記錄 (51)編寫Enterprise PDM的無訊息安裝指令碼 (51)5產生與發送檔案資料保險箱視圖 (54)產生檔案資料保險箱 (54)使用視圖設定精靈產生檔案資料保險箱視圖 (54)在有Windows防火牆時啟用廣播 (56)將共用檔案資料保險箱視圖與多個使用者設定檔搭配使用 (57)在終端機伺服器上使用Enterprise PDM (58)產生檔案資料保險箱視圖設定檔案 (58)編寫檔案資料保險箱視圖設定指令碼 (59)使用Microsoft Windows Active Directory散發Enterprise PDM檔案資料保險箱視圖 (60)尋找Enterprise PDM資料保險箱ID (61)接收發送的檔案資料保險箱視圖 (61)在WAN環境中散發檔案資料保險箱視圖 (61)手動組態向Enterprise PDM客戶端宣告的保存檔伺服器 (61)手動指定SolidWorks Enterprise PDM設定群組原則 (62)SolidWorks Enterprise PDM設定原則選項 (62)6組態內容搜尋 (65)內容搜尋概要 (65)建議的電腦組態 (65)在SQL Server系統上組態索引服務 (66)確認Microsoft索引服務的安裝 (66)監控及微調Microsoft編制索引的服務 (66)編制Enterprise PDM檔案資料保險箱保存檔的索引 (66)在非SQL Server系統上組態索引服務 (67)使用索引伺服器名稱更新檔案資料保險箱資料庫 (67)變更資料庫伺服器登入帳戶 (68)變更SQL Server登入帳戶 (68)新增索引伺服器濾器 (69)壓縮保存檔(gzip)濾器 (69)Microsoft索引濾器 (70)管理檔案資料保險箱索引目錄 (70)移除檔案資料保險箱索引 (70)7備份與回復檔案資料保險箱 (71)備份檔案資料保險箱資料庫 (71)備份Enterprise PDM主資料庫 (72)備份保存檔伺服器設定 (72)備份保存檔案 (72)使用維護計劃排定資料庫備份 (73)啟動SQL Server Agent (73)設定資料庫備份的維護計劃 (73)回復檔案資料保險箱 (75)回復SQL Server檔案資料保險箱資料庫 (75)確認ConisioMasterDb回復 (75)回復保存檔伺服器與檔案資料保險箱保存檔 (76)8升級Enterprise PDM (77)關於Enterprise PDM升級 (77)從Conisio6.2之前的版本升級 (77)升級Enterprise PDM Web伺服器 (77)客戶端授權 (77)Visual Basic6附加程式 (78)升級之前 (78)判斷目前版本 (78)決定已被套用的更新 (79)移除Visual Basic6附加程式 (79)升級保存檔伺服器 (79)升級資料庫伺服器 (80)升級檔案資料保險箱 (81)升級檔案資料保險箱資料庫 (81)升級檔案資料保險箱保存檔 (83)升級在Enterprise PDM中的Toolbox (88)9升級SolidWorks檔案 (90)升級SolidWorks檔案 (90)所需的升級公用程式軟體 (91)系統需求 (91)安裝檔案版本升級公用程式 (92)準備升級 (92)選擇版本設定 (93)產生檔案的新版本 (94)覆寫檔案的現有版本 (97)執行一試做的檔案升級 (109)執行升級公用程式 (109)產生及使用工作指示檔案 (110)完成中斷的升級 (110)升級之後 (111)升級記錄檔的檔案名稱格式 (111)管理備份檔案 (111)備份檔案的產生 (112)從備份中復原一被不正確升級的版本 (112)找出及移除備份檔案 (113)10其他組態 (114)管理SQL交易記錄檔大小 (114)變更為簡單復原模式 (114)壓縮交易記錄檔 (114)組態Enterprise PDM以便僅使用IP位址進行通訊 (115)更新保存檔伺服器以使用IP位址進行通訊 (115)更新SQL Server以使用IP位址進行通訊 (115)更新Enterprise PDM客戶端以使用IP位址進行通訊 (116)確認IP位址通訊 (116)將伺服器元件移至其他系統 (116)將檔案複製到新伺服器 (116)組態移動的SQL檔案資料保險箱資料庫 (117)組態移動的保存檔伺服器 (118)更新客戶端登錄機碼 (118)更新複製的設定 (119)確認伺服器移動 (119)法律注意事項©1995-2013,Dassault Systèmes SolidWorks Corporation,a Dassault Systèmes pany, 175Wyman Street,Waltham,Mass.02451USA.All Rights Reserved.本文件中提及的資訊和軟體如有更改，恕不另行通知，Dassault Systèmes SolidWorks Corporation (DS SolidWorks)不負任何責任。

Serenity框架官⽅⽂档翻译（1-2开始、安装和界⾯）1.开始最好的和最快速地上⼿Serenity的⽅法是使⽤SERENE，它是⼀个⽰例应⽤程序模板。

您有2个选项来安装SERENE模板到您的Visual Studio：您不⼀定要使⽤这个模版来配合Serenity框架，你可以通过NuGet添加Serenity 库到任何 .NET项⽬中 .您也可以添加Serenity作为git⼦模块到您的项⽬中来保持它总是能更新到最新的源代码。

我们将在其他章节中涵盖这些。

1.1从 Visual Studio Gallery 安装 Serene输⼊ Serene到Visual Studio Gallery的搜索框中，敲回车键。

你将看到Serene (Serenity Application Template)，点击打开它。

点击下载传输的 VSIX⽂件到你的电脑中。

下载完后，安装 VSIX ⽂件到你的VS扩展中。

注意：扩展要求VS2012及以上版本。

启动 Visual Studio (或者重启VS).点击⽂件 => 新项⽬.你将会看到 Serenity template在模版在Visual C# 节点下⾯.给你的项⽬取名字⽐如MyCompany, MyProduct, HelloWorld or 或者Serene1.别给项⽬取名为Serenity.他可能会对 Serenity 程序集产⽣冲突.点击确定等待VS创建项⽬⽂件。

1.2直接从Visual Studio安装 Serene启动 Visual Studio并且单击新建=> ⼯程.程序模版要求Vs2012以及以上版本，请确保您更新到最新的visual studio在新建项⽬对话框会显⽰最近安装和联机部分。

点击在线模版。

等待加载结果。

输⼊SERENE到搜索框搜索在线模版。

你将会看到Serene (Serenity Application Template):给你的项⽬取名字⽐如MyCompany, MyProduct, HelloWorld or 或者Serene1.别给项⽬取名为Serenity.他可能会对 Serenity 程序集产⽣冲突.点击确定等待VS创建项⽬⽂件。

A8平台接口和增值开发手册© 2006 UF Seeyon Co。

, Ltd。

All rights reserved。

This document contains information that is proprietary and confidential to UF Seeyon。

, which shall not be disclosed outside the recipient's company or duplicated，used or disclosed in whole or in part by the recipient for any purpose other than to evaluate this file. Any other use or disclosure in whole or in part of this information without the express written permission of UF Seeyon. is prohibited。

Date: 2009-01—04Author：王文友Version：V1.0修改记录31.概述41。

1编写目的41.2开发背景41.3应用价值41.4接口范围52。

二次开发接口52。

1接口一览62。

2服务列表63.Portal集成73.1单点登录（SSO)73。

1。

1外部平台集成A8 (7)3。

1.1。

1实现说明73。

1.1.2接口说明73。

1。

1。

3代码示例83。

1。

1。

4部署说明93。

1。

2A8集成第三方系统93。

1。

2。

1实现方式一：Ticket93。

1。

2.2实现方式二：关联系统+扩展栏目113。

2Portlet (12)3.2.1概述123。

2。

2开发说明133。

2.2。

1确定栏目数据133.2.2.2确定栏目显示模板133。

2。

2.3开发说明133.2。

2。

4注册到系统143.2。

多种解决ansys workbench 不能正常运行的方法如下。

（一）方法1、以管理员身份运行“ANSYS License manager”2、在选项列表中找到Specify the License Server Mavhine3、点击，出现以下界面：4、选择OK,而后出现以下界面，选择ADD：5、在以下界面中，将服务器主机名输入，点击“OK”即可（二）方法, FLExlm not running问题FLExlm not running是端口被占用了，只要关闭被占用端口就可以。

第一步：开始>运行> 输入cmd 回车进入dos界面，再出入netstat -a -o,（注意:是空格-a空格-o否则无效），找到计算机名：1055端口对应的pid值。

第二步：打开任务管理器查看进程，打开“查看”-“选项列”，勾选PID选项，找到PID值对应的映像名称，右击结束进程。

第三步：打开Server ANSLIC_ADMIN Utility ，点击stop the ANSYS,lnc.License Manager,再点击start the ANSYS,lnc.License Manager，看看FLEXlm是不是变成running了。

我的是ansys12.1已解决，希望能帮到你！！13.0试试看（三）方法,此种方法就是运行许可管理Server ANSLIC_ADMIN Utility，，，先点击stop ，，再点击start ，，再看是不是全部running(四)，方法，重新生成许可文件license.txt，，再重新装载许可文件。

同样是先运行Server ANSLIC_ADMIN Utility，再点击，找到刚生成的许可文件(最好复制到软件安装的文件地址中)，装入之后，再点击，不行的话，就实行第三个方法就行，实在不行的话就实行第二种方法，那就绝对解决问题，祝你工作愉快！！就是FLEXlm没有运行，这个问题怎么解决呢？解决方法：1.按Server Anslic_Admin Utility 中的Stop...停步所有许可证，并关闭本窗口；2.打开任务管理器，结束所有与ansys相关的进程；3.删除C：、Program Files\ANSYS Inc\Shared Files下的License文件夹；4.删除开始菜单中的Inc. License Manager这个选项； 5.重新启动计算机；6.打开ansys安装程序，重新安装Install ANSYS, Inc. License Manager,就像最初装ansys一样，一步一步安装，中间需要添加*.txt的许可证文件，直到最后安装完毕。

User TSconfig is designed for users or groups of users. User TSconfig can be entered for both BE users and BE groups. User TSconfig Top Level Objects:Demo configuation:On the root page of the site with one main template these extensions are the inserted in “Include basis templates”.TYPO3 projects should be regularly checked for available extension updates. This is easy with the menu “Check for extension updates”. Just click on the extension name to install the update – but be sure to read the comments and update information in the manual. Did we mention that it is a good idea to have a recent backup?The extension automaketemplate converts according to the setup below all div tags into subparts.<div id="contentMain"> </div>The main templates are stored in the folder "fileadmin/template/main/", all sub templates are stored in the folder sub. Save the following templates in the folders.Main template: template_01.html (wrapper for the sub templates) in folder mainFile->Filelist module. A right-click on the name of the template file offers the option TemplaVoila:In the first step, a root container must be mapped to the body-tag of the template. By clicking on the map button, the HTML tags in the template are displayed in the preview:By mapping the <body> tag, a container is created that will contain the elements of the webpage. To create the elements, a fieldname must be added. The name always starts with field_ and must be unique. Only letters a-z and underscore are allowed. The first element will be the main navigation of the website:Depending on the layout and implementation of the template, it may sometime be easier to map in the HTML source view:After saving we can click on the edit icon and now have the option to add a path to our future Typoscript object:Using the TYPO3 Element Browser the editor can now search for keywords and quickly get a list of all matching files:Firefox Add-on: Web DeveloperAdds a menu and a toolbar with various web developer tools.。