New Openness in Dassault V6 r2012.
达索v 6 R 2012的新开放性。
Dassault V6 Cloud - What Does it Mean?
达索V 6云是什么？
Stop the V6 node and application servers.
停止版本 6 的节点和应用程序服务器。
Remove the V6 deployment manager profile.
删除版本 6 的部署管理器概要文件。
How do V6 profiles relate to V5 instances?
v6概要文件与V5实例的联系。
Each node in turn is migrated from V5 to V6.
将每一个节点依次从V5迁移到V6。
Start the V6 node and the application servers.
启动版本6的节点和应用程序服务器。
The deployment manager is migrated to V6 first.
首先将部署管理器迁移到V6。
Figure 1 shows the message format up through v6.
图1显示了V6及之前版本的消息格式。
Use the new format when operating on the V6 node.
在版本6的节点上操作时使用新的格式。
At this point, a fully functional V6 cell will exist.
此时，将出现一个功能齐全的V 6单元。
In V6, this concept is continued without obvious changes.
v6中继续使用这一概念，并没有显著的变化。
Part 1: Introduction to WebSphere V6 messaging resources.
第一部分：WebSphereV6消息资源介绍。
For use case 1, you will validate v6 to v6 communication.
对于用例1，您将验证v 6到v6的通信。
In V5 and V6, we have maintained the same scripting support.
在V5和v6中，我们维持了相同的脚本支持。
Restart the V6 deployment manager, and the V5 node and servers.
重新启动版本6的部署管理器，及版本5的节点和服务器。
Once a cluster contains a V6 member, it becomes a mixed cluster.
一旦集群中包含了版本6的成员，它就成为了混合集群。
Recent Dassault announcement about Cloud V6 is just one of them.
其中之一便是刚刚发布云计算V6的达索系统。
Nodes can be migrated from V5 to V6 with compatibility mode off.
可以在关闭兼容性模式的情况下将节点从版本 5移植到版本 6。
Where an issue is unique to V6, we will identify it specifically.
其中有一个问题是V6特有的，我们会特别指出。
However, unchanged V6 BAR files can be deployed into a V7 broker.
不过，未更改的V6BAR文件可以部署到V 7代理中。
V6 also has tooling that can be used to create and manage these profiles.
V6还具备可以用于创建和管理这些配置文件的工具。
Figure 11 shows an example of the V6 administrative console login screen.
图11显示了V6管理控制台登录屏幕的示例。
These values are used when creating V6 profiles for each node in the cell.
在为单元中的每个节点创建V 6配置文件时要使用这些值。
However, V4 users must migrate all V4 nodes to utilize them in the V6 cell.
然而，V4用户必须迁移所有的V 4节点才能在V 6单元中利用它们。
The V6 migrated deployment manager profile can manage all V5 nodes in the cell.
迁移到V6的部署管理器配置文件可以管理单元中的所有V 5节点。
A new V5 server may not be created after the deployment manager is upgraded to V6.
在将部署管理器升级到版本6之后，不能新建版本5的服务器。
A workaround is to first upgrade the node to V6 before the conversion or expansion.
在转换或扩展之前，工作区首先将节点升级到版本6。
All of the V5 application server nodes can then connect to the V6 deployment manager.
然后可以将所有的V5应用服务器节点连接到V 6部署管理器。
Delete the V6 node profile so that you cannot start both V5 and V6 nodes simultaneously.
将版本6的节点概要文件删除，以防将版本5和版本6的节点同时启动。
应用推荐