Give the argument passed in the method the scenario name for which the data will be captured in log file.
既然方法中有通过的论断，数据将会从日志文件得到场景名。
This relates the data in the ErrorDetails file to the scenario, because the entries in the log file are preceded by the scenario name.
这就会把ErrorDetails文件中的数据与场景联系起来，因为日志文件中条目的前面就是场景名。
If the log file contains any entries, the code creates a text file based on the scenario name and, scans the log file, and writes the entries to that text file.
如果日志文件中包含有什么条目，那么代码就会创建基于场景名的文本文件，浏览日志文件，并将条目写入到文本文件中。
Propagating custom tokens gives an additional level of flexibility to security attribute propagation (Scenario 8), in that it enables the developer to name, specify the type, and implement any token.
传播自定义的令牌为安全属性传播(场景8)提供了附加的灵活性，因为它允许开发人员命名、指定类型和实现任何令牌。
All I needed for each case was a logical name for the component under test and a series of steps to create the scenario.
对于每种情况，我需要的只是被测试的组件的逻辑名称以及一系列步骤，以便创建场景。
This scenario involves a source agent and a destination agent. The agent queue managers have the same name as the agents.
这个场景涉及一个源代理和一个目标代理，代理队列管理器的名称和代理名称相同。
One common scenario for using custom agents is name lookups, where SAP users can be represented in an incoming message with their SAP user IDs.
使用定制代理的一个常见场景是名称查找，其中SAP用户可以以SAP用户ID的形式在进入的消息中呈现出来。
Important: the hostname is case specific, and in this scenario the hostname RHAALAB2 is all capital letters to match the name we used for testing.
重要提示：主机名对大小写敏感，为了与我们用于测试的名称相匹配，在这个场景中，主机名rhaalab2全部是大写字母。
Delete the name space binding that you configured in Advanced scenario 1.
删除在高级场景1中配置的命名空间绑定。
A usage scenario is exactly what its name indicates — the description of a potential way your system is used.
使用方案恰如其名称所揭示的那样——描述使用系统的潜在方法。
In a scenario with multiple persistence units, the selection can be constrained by persistence unit name using an LDAP style filter.
在一个拥有多个持久性单元的场景中，可使用一个ldap样式过滤器根据持久性单元限制选择。
There is overlap among them, and often teams attach the same name — scenario, for example — to techniques that are widely disparate.
这些技术相互之间有重叠的部分，而且团队也经常给他们赋予相同的名字——例如，场景——事实上这些技术根本不相同。
Taking the same basic principles we used to make the name generator, we can make what's called a scenario generator.
利用构建名字生成器使用的相同基本原理，我们可以构建场景生成器。
To make the scenario simple, you will only populate a customer BO with the first name and last name.
为了简化场景，您将仅仅使用姓氏和名字填充客户BO。
The two that are important for our scenario are Name and Handler class.
对于我们的场景，两个重要的属性是Name和Handler 类。
You need to do this because Advanced scenario 2 will use the same name space identifier echo.
之所以需要这样做是因为，高级场景2将使用相同的命名空间标识符echo。
For example, for this sample scenario you would enter the name ChineseShortMsgKB.
例如，对于此示例场景，输入名称ChineseShortMsgKB。
In this scenario, the resource reference name is arbitrarily changed to customer.
在这种情形中，资源引用名可以被随意地改为customer。
This section shows the scenario of configuring a user name token for a Web services Web client. The configuration steps are.
本节展示为一个Web服务的Web客户机配置用户名令牌的场景。
The Distinguished Name for this user in this scenario is: uid=taiuser,cn=trustedusers,dc=ibm,dc=com.
在该场景中，这个用户的专有名称为：uid=taiuser,cn=trustedusers,dc=ibm,dc=com 。
However, the reverse situation is problematic: in a multi-identity scenario, WebSphere has trouble accepting a name in Domino format.
但是，反过来却存在问题：在一个多身份场景中，WebSphere在接受domino格式的名称时遇到了麻烦。
For the same user registry scenario, John may submit a job against the first base node without specifying user name and password.
对于相同用户注册中心方案，John可以向第一个基本节点提交作业，而不需要指定用户名和密码。
Additionally, as is the case in this scenario, if the referred element is a nested element without a visible qualified name, it is not possible to refer to it from the Fact complex type.
此外，和这个场景一样，如果参考元素是一个嵌套元素且没有一个明确限定名，则不可能从Fact复杂类引用它。
The adjuster in the JK insurance scenario subscribes to Intelligent notification Services and requests notification when an insurance claim is filed in his or her name.
JKInsurance场景中的调整器可以订阅IntelligentNotificationServices，并且当保险请求以他或她的姓名归档时，该调整器会申请通知。
In the case of this scenario, that will be the subdirectory name under the directory c: \ monitored \.
在这个场景中，这将是C： \ monitored \目录下的子目录名。
Scenario: You wish to change the name of this database from TESTDB to NEWNAME.
场景：希望将数据库名从testdb改为newname。
In this scenario, the master replicate definition needs to be created with the column name verification attribute turned off.
在这个场景中，需要在关闭列名检验属性的情况下创建主复制定义。
In this scenario a query gets the name and e-email address from a user, as in the following example.
如下例所示，在此情况下，查询语句获得用户的名称和电子邮件地址。
In this sample scenario, the name SRCSRV is used.
在这个示例场景中，使用名称SRCSRV。
In this sample scenario, the name SRCSRV is used.
在这个示例场景中，使用名称SRCSRV。
应用推荐