清单2给出动态库文件的格式。
当然，不应该直接修改这些脚本库文件。
Of course, you shouldn't modify these script library files directly.
这样就安装了所需的库文件和gem命令。
数据库文件将创建在这个目录下。
The database files are going to be created under this directory.
WordNet：词法数据库文件。
根据邮件目录和数据库文件。
ODM数据库文件驻留在对象存储库中。
fabridge库文件的位置取决于您的环境。
The location of the FABridge library files depends on your environment.
应该复制希望查看的库文件，然后只编辑自己的拷贝。
Make a copy of any library file that you want to view, and then edit only your copy.
拷贝头文件和库文件。
确保您安装了已找到的以-dev为后缀的库文件。
Make sure you install the found library files with names ending in the -dev suffix.
这需要对自动化中用到的所有头文件和外部库文件进行此工作。
It needs to be done with all the header files and external library files used in your automation.
为了最大限度的扩展性，不要应用外部路径和库文件。
To the greatest extent possible, do not refer to external paths and libraries.
将二进制文件，库文件和头文件放在一致的逻辑位置。
Place binaries, libraries and header files in a logical and consistent location.
清单4展示了脚本库文件中包含的main . py文件。
Listing 4 shows the main.py file included in the script library.
从本教程的下载一节下载DB 2“大富翁”游戏数据库文件。
Download the DB2 business game database file from the Downloads section of this tutorial.
它确保内部使用的数据库文件不会干扰用户或数据库应用程序。
It makes sure that internally used database files won't interfere with user or database applications.
其次是利用Linux的新特性和新版本的工具及库文件。
The secondary focus is utilization of new Linux features and recent tools and libraries.
也可以把应用程序使用的其它库文件(JAR文件)放置到EAR文件中。
Other libraries (JAR files) used by the application can be located in the EAR file as well.
这些类允许访问IBMi文件资源—数据库文件和IFS文件。
These classes allow access to IBM I file resources, both database files as well as IFS files.
上述代码最有趣的部分是我们如何找到一个位置来放置数据库文件。
The most interesting part of this code is how we find a location to keep the database files.
脱机备份是正常关闭数据库之后，对所有物理数据库文件执行的备份。
Offline backup is the backup of all the physical database files after a normal database shutdown.
选择任何组织，就会显示此组织的用户数据库文件中定义的文件夹结构。
Selecting any of the organizations below will display the folder structure defined for that organization in its user database file.
使用本地主机的安全数据库文件中的用户和组信息装载ldap数据库。
The LDAP database is loaded with the user and group information from the localhost's security database files.
安装DB 2客户机，确保选择了用于应用程序开发的头文件和库文件。
Install the DB2 client, ensuring that you select the application development headers and libraries.
这里的主要活动是将这个模型和您之前建立的概要文件和库文件连接起来。
The key activities here are to connect this model with the profile and library you created earlier.
在启动时，提供者解析这个文件，然后装载引用的每个单一组织数据库文件。
On startup, the provider parses this file, and loads each of the referenced single organization files in turn.
因为LDAP用作后端存储，所以没有在本地文件系统中创建数据库文件。
Since LDAP is used as back-end storage, database files are not created on the local file system.
最有意思的情况是使用SQL精简版数据库文件作为不经常更改的数据的本地缓存。
The most interesting scenario is to use SQL Compact Edition database file as a local cache of data that do not change often.
创建概要文件时可导入一些模块的库文件，这些操作同样也可以在创建完成后进行。
The model libraries could be imported during the profile creation, but that could be done afterwards as well.
应用推荐