如果你想试一试，秉“语音配置文件管理器”，它会马上弹出。
If you want to try it, Bing for "Speech Profile Manager", and it will pop right up.
像IEAK自定义向导，IEAK配置文件管理器仍非常易于使用。
Like IEAK Customization Wizard, IEAK Profile Manager is fairly user-friendly.
您已经将加载项选项添加到您的软件包后，运行设置文件的配置文件管理器。
After you've added the INS option to your package, run Profile Manager to set up the file.
当您打开配置文件管理器的第一次，将只有一个默认的配置文件，你可以创建多个配置文件在这里。
When you open profile Manager for first time, there will be only one default profile and you can create multiple profiles here.
完成后，可以使所做的更改已成功部署到您的所有用户实时的加载项和CAB文件替换为新的IEAK配置文件管理器从中。
Once that's done, you can replace the live INS and CAB files with the new ones from IEAK Profile Manager so the changes are successfully deployed to all your users.
在将部署管理器和版本5的节点之间的配置文件同步化时，将变换设置成版本6的格式以便与版本5兼容。
When synchronizing the configuration file between the deployment manager and a V5 node, transformations are applied to the V6 format to make it V5-compatible.
如果增加SORTHEAP，请确定是否还需要调整数据库管理器配置文件中的SHEAPTHRES参数。
If you increase SORTHEAP, determine whether the SHEAPTHRES parameter in the database manager configuration file also needs to be adjusted.
利用部署管理器配置文件，可对跨越多个节点的多个应用服务器进行配置管理。
The deployment manager profile allows you to manage the configuration of multiple application servers across multiple nodes.
定义备用中央管理器时，您应该在配置文件中设置下面的关键字。
When you define alternate central managers, you should set the following keywords in the configuration file.
transaction - manager属性保存一个对在Spring配置文件中定义的事务管理器bean的引用。
The transaction-manager property holds a reference to the transaction manager bean defined in the Spring configuration file.
您应该手动修改启动管理器配置文件 /boot/grub/grub.conf，以使用新的initrd镜像。
You should manually modify your boot manager configuration file /boot/grub/grub.conf to use the new initrd image.
这个命令使用在数据库管理器配置文件和授权系统编目视图(SYSCAT.DBAUTH)中找到的值。
This command USES the values found in the database manager configuration file and the authorization system catalog view (SYSCAT.DBAUTH). Listing 5 shows the results of issuing the command.
图1展示了响应文件选项，用于在静默模式下使用配置文件创建器创建ProcessServer6.0.2部署管理器。
Figure 1 shows response file options for creating the Process Server 6.0.2 deployment manager using the profile creator in silent mode.
如果您的队列管理器执行需要传递或设置上下文的程序，那么实现配置文件和最少的特权，以便只有需要这个特权的用户拥有相应特权。
If your queue managers execute programs that need to pass or set context, then implement profiles and least privilege so that only the users that require this authority have it granted to them.
对于部署管理器配置文件没有命名约束，这是由于v4中没有类似的对象。
There are no naming restrictions for the deployment manager profile, since there is no analogous object in V4.
如果是，您指定单元管理器配置文件名和集群名，而安装程序会完成其余操作。
If you do, you specify the cell manager profile name and the cluster name, and the installer will do the rest.
下一个主题是如何定义这些类中的配置文件来保护队列管理器及其资源。
The next topic is how profiles in these classes can be defined to protect a queue manager and its resources.
如果定义了多个配置文件(如同一个系统上的V6部署管理器和V 6节点配置文件)，则选择要使用的配置文件。
If more than one profile is defined, such as a V6 deployment manager and a V6 node profile on the same system, select which profile to be used.
当您确定自己的安全要求之后，就可以开始设计配置文件来最好地保护您的队列管理器及其应用程序消息。
Once you have documented your security requirements, then you can start designing profiles to best secure your queue managers and their application messages.
迁移到V6的部署管理器配置文件可以管理单元中的所有V 5节点。
The V6 migrated deployment manager profile can manage all V5 nodes in the cell.
因此，对于从V 5向V6迁移，必须在V 6创建部署管理器配置文件，只有V 5部署管理器能够迁移到该配置文件。
Therefore, for a V5 to V6 migration, you must create a deployment manager profile on V6 to which ONLY the V5 deployment manager will be migrated.
必须定义RACF配置文件来保护您为您的队列管理器定义的本地应用程序对象。
RACF profiles must be defined to protect the local application objects that you define for your queue managers.
另外，V 6部署管理器配置文件的单元名称必须与V 5部署管理器的单元名称相匹配。
Additionally, the cell name of the V6 deployment manager profile must match the cell name from V5 deployment manager.
如果V 6部署管理器配置文件在新的系统上，则需要将备份目录复制到该新的系统。
If the V6 deployment manager profile is on a new system, the backup directory will need to be copied to this new system.
设置新队列管理器的安全性或检查现有队列管理器的配置文件时的出发点应该是考虑哪些访问需要保护。 也就是说，哪些人可以发出哪些命令？
The starting point when setting up security for a new queue manager, or reviewing the profiles for an existing queue manager, should be to consider what needs to be secured.
ASLHEAPSZ或QUERY_HEAP _ SZ可能不够大，这两个配置参数是在数据库管理器配置文件中定义的。
You may not have a large enough ASLHEAPSZ or QUERY_HEAP_SZ, both of which are defined in the database manager configuration file.
每个实例还具有自己的配置文件，数据库管理器配置文件(DBMCFG)用于进行实例级的安全、性能变量和通信配置。
Each instance also has its own configuration file, the Database Manager configuration file (DBM CFG) for instance level security, performance variables, and communication configuration.
当将V 5部署管理器迁移到v6时，V6配置文件的单元名称的值必须与V5的单元名称相匹配。
When migrating a V5 deployment manager to V6, the cell name value of the V6 profile must match the cell name from V5.
回过来参看图1，部署管理器的主存储库存储着所有版本6标准的配置文件，还设计成能够适应版本5的配置信息。
Referring back to Figure 1, the deployment manager master repository stores all configuration files at the V6 level, but is designed to also accommodate V5 configuration information.
无论何时迁移V 5单元，部署管理器配置文件都必须是迁移的第一个配置文件。
Whenever a V5 cell is migrated, the deployment manager profile must be the first profile migrated.
应用推荐