We can use the migration toolkit to automatically detect your previous configurations of WAS and import the configuration into the Intelligent Management cell.
- Bidirectional and atomic automation: With the migration toolkit, we can read from an older cell configuration and create the v8.5 configuration in an atomic process. You do not need to manually make any updates after the migration process begins.
- Multiple migration modes: We can also phase the migration. For example, we can read the data from the previous cell and manipulate the data before continuing with the migration.
- Delta generation: The migration toolkit scripts persist a copy of the previously generated environment data. When you rerun the scripts, the scripts create a delta between the configuration versions and can update and delete servers or applications as needed. Only major configurations such as servers, applications, and modules are factored into the delta. If port or endpoint information changes, for example, modify the data directly from the console.
- Automatic data entry: The migration toolkit scripts automatically preload data into the cell.
- Limited dynamic clustering: After the scripts complete, the static clusters are represented as dynamic clusters. Dynamic clusters can start and stop servers as the service policies or demand requires. The dynamic clustering capabilities for the migrated servers are limited. The limitations that apply to dynamic clusters of assisted life cycle middleware servers also apply to the dynamic clusters that the migration toolkit creates.
- HTTP traffic shaping: Because the applications are registered within the Intelligent Management configuration, the on demand router (ODR) can route to the clustered applications based on the demand and statistical analysis of the HTTP traffic. Traffic can be routed to the Version 6.1.x applications in the same way that traffic can be routed to v8.5 and later applications. Service and routing policies can be applied.
- The representations of the servers receive server status from the middleware agent. The middleware agent is installed on the previous server and provides the status information. However, this status might not be accurately represented at all times.
- We cannot fully monitor middleware applications from the v8.5 cell. The status of the applications is tied to the status of the target servers or clusters with which they are associated. When the corresponding servers or clusters start, so do the middleware applications, independent of the actual application status.