在这种情况下，可以为连接器定义一个全局项目类，作为对那些一直可以进行访问的属性进行检索的方法。
In this case, a global item class can be defined for the connector, to serve as a way to retrieve those properties that can always be accessed.
与系统属性相似，连接器将全局属性描述存储在一个全局条目类中。
Like system properties, global property descriptions are stored in the global item class by the connector.
您的连接器可能使用相似的循环，遍历所有可用的属性并将它们转换为正确的本机存储库格式。
Your connector will probably use a similar loop, as it will run through all of the available properties and convert them to the proper native repository format.
然而，对齐属性的有效性将受到固有的连接器局限性的限制。
The effectiveness of aligned attributes, however, is limited by inherent linker limitations.
因为示例连接器无法提前知道专用属性的存在，所以不在全局条目类中存储它们的属性描述。
Because the example connector cannot know about the existence of the ad-hoc properties ahead of time, it does not store their property descriptions in the global item class.
现在，示例连接器处理第二种属性，即全局定义的字段。
Now the example connector handles the second kind of property, which consists of the globally-defined fields.
为了避免进入性冲突，那么外部性对象的更新属性应该在更新Jazz项目之前使用项目连接器客户端来进行同步化。
To avoid incoming conflicts, the updated properties of an external object should be synced by using the item Connector client before the Jazz item is updated.
OmniFind连接器中的系统属性描述存储在一个全局条目类中。
System property descriptions in the OmniFind connector are stored in a global item class.
对于每个JAR文件，它使用connectorconfigbeaninfo类判断连接器需要的属性。
For each JAR file, it USES the ConnectorConfigBeanInfo class to determine the properties required by the connector.
大多数连接器需要适当地执行 ItemFinders，从而提供快速的属性检索机制。
Most connectors will need to facilitate a quick property retrieval mechanism by executing ItemFinders appropriately.
它演示这种新连接器的使用方法，以及使用JDBC驱动程序连接IDS所需的一些配置属性设置。
It shows usage of this new connector and also some of the configuration property Settings required to be able to connect to IDS using JDBC artifacts.
在示例连接器中，文件夹不能返回选择属性；而是返回null。
Folders will never be able to return selection properties in the example connector; instead, they return null.
一个好例子是文件夹，文件夹在OmniFind连接器中没有属性。
A good example is that of the folder, which does not have properties in the OmniFind connector.
将useRMI代理连接器属性设置为TRUE。
所以，OmniFind连接器只为内容支持一种单一的全局项目类，这样每个项目可能会有无限多的专门的其他属性。
Thus, the OmniFind connector would only support a single, global item class for content and there could be an unlimited number of other ad-hoc properties per item.
示例连接器：条目属性。
但是，对于您正在使用的GoogleAJAXSearchAPI，则不需要其他特殊配置，只需指定连接器名称和空的属性数组。
However, for the Google AJAX Search API you are using, no other special configuration is required, so just specify the connector name and an empty properties array.
当读或写xml列时，连接器要求ArraySize属性设置为1。
The connector requires that the ArraySize property to be set to 1 when reading or writing XML columns.
等待1分钟（连接器属性中指定的轮询间隔）。
Wait for 1 minute (the polling interval specified in the connector properties).
这个文件定义连接器名称，以及连接器可能需要的任何属性。
This file defines the name for the connector, and any properties the connector might need.
最后，对于示例连接器中的第三种属性——专用属性，无法判断属性描述应该是什么。
Finally, the third kind of property in the example connector, the ad-hoc property, gives no way of determining what the property description should be.
为了理解应该如何为每种Property构建PropertyDescription，要仔细了解在连接器中如何使用这些属性，尤其是在基于属性的搜索中。
To understand how the PropertyDescription should be built for each kind of property, take a closer look at how these properties will be used in the connector, particularly in property-based search.
用于内部管理通信的连接器类型通过PreferredConnector特性来进行指定，这个属性是在每个服务器进程中的“AdministrationServices”选项卡上进行指定的。
The connector type used for internal administrative communication is specified via the Preferred connector property, which is specified on the "Administration Services" TAB for each server process.
当连接器需要将一个系统属性添加到Content对象中时，它首先从这个全局条目类查询属性描述。
When the connector needs to add a system property to a Content object, it will first look up the property description from the global item class.
连接器为这些数字添加一个字符串前缀，该字符串可以通过设置连接器源上下文属性Prefix forExpressionColumns进行配置。
The connector prefixes these with a string that can be configured by setting the connector source context property prefix for Expression Columns.
Encina连接器在网关列表(连接器的连接工厂的gatewayspec属性)中指定的网关之间循环来获取连接。
The Encina connector rotates among gateways specified in the gateway list (gatewaySpec property of the connection factory of the connector) to obtain connections.
Encina连接器在网关列表(连接器的连接工厂的gatewayspec属性)中指定的网关之间循环来获取连接。
The Encina connector rotates among gateways specified in the gateway list (gatewaySpec property of the connection factory of the connector) to obtain connections.
应用推荐