选择默认的模板。
Make your profile the default profile.
使您的概要文件成为缺省概要文件。
Consider, for example, the default profile IOBOUND.
例如，请考虑缺省概要IOBOUND。
In the default profile, only one SOA lifecycle is supported.
在默认概要文件中，只有一个SOA生命周期受到支持。
This name is used as the partition and default profile name, as well.
此名称也用作分区和默认的配置文件名。
Take the default profile name and profile directory location and click Next.
接受缺省概要名称和概要目录位置，然后单击 Next。
The Service Registry comes with a default profile, which you can modify and extend for your business needs.
ServiceRegistry附带了一个默认的配置文件，可以根据业务需求进行修改和扩展。
Please use the profile Wizard to set a default profile before running the Message file Conversion Wizard.
请在运行邮件文件转换向导之前，使用配置文件向导设置默认配置文件。
Service Registry V6.2 provides a default profile, as well as a governance profile suitable for real application environment.
ServiceRegistryV6.2提供了一个默认概要文件，以及用于真实应用程序环境的治理概要文件。
No default profile set. Please use the profile Wizard to set a default profile before running the Message file Conversion Wizard.
未设置默认配置文件。请在运行邮件文件转换向导之前，使用配置文件向导设置默认配置文件。
You can mark a profile as the default profile under an installation directory at profile creation time, as you can see in Figure 1.
您可以在创建概要文件时，将其标记为安装目录下的缺省概要文件，如图1所示。
More than one profile can be defined for each LPAR, and the name of each additional profile should be a variation on the default profile name.
可以为每个LPAR定义多个配置文件，每个额外的配置文件的名称应该是默认配置文件名的变体。
Select the default profile for new Log Reader Agents. To update existing Log Reader Agents to use the selected profile, select the check box below.
为新的日志读取器代理程序选择默认配置。若要更新现有的日志读取器代理程序以使用选定的配置，请选择下面的复选框。
The migration tool doesn't support the non-default profile path, meaning that you cannot place the profile under these paths, or the migration fails.
迁移工具不支持非默认配置文件路径，这意味着不能将配置文件放在这些路径下，否则迁移会失败。
By using the node name as the LPAR and default profile name, it enables automation scripts to easily identify the LPAR and profile for manipulation and modification.
通过使用节点名作为LPAR和默认的配置文件名，自动化脚本就很容易识别要操作和修改的LPAR和配置文件。
The default profile is used to package any kind of software asset, while the other two profiles are intended for use with components and Web services, respectively.
Default配置文件用于打包任意类型的软件资产，而其他两个配置文件分别用于与组件和Web服务一起使用。
However, it is not a good idea to use the default profile notion when there are multiple profiles under the same installation directory, even if the idea of a default profile still applies.
然而，在相同安装目录中有多个概要文件时，即使仍然可以应用缺省概要文件，但这并不是好办法。
As with the LPAR name, experience with data center automation techniques has shown the default profile name should correspond with the node name and be an enterprise-wide unique profile name.
与lpar名一样，数据中心自动化技术的经验表明，默认的配置文件名应该与节点名对应，应该是在企业范围内惟一的配置文件名。
The OMG currently offers three profiles: the Default profile, the Default Component profile, and the Default Web Service profile.
OMG目前提供三种概要文件：默认概要文件，默认组件概要文件，以及默认Web服务概要文件。
The OMG currently offers three profiles: the Default profile, the Default Component profile, and the Default Web Service profile.
OMG目前提供三种概要文件：默认概要文件，默认组件概要文件，以及默认Web服务概要文件。
应用推荐