29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note: It is always a good practice to have comprehensive scripts to<br />

configure the environment available as it eases various administration<br />

tasks (such as setting up a new environment for testing purposes,<br />

recreating the environment in case of a disaster, and so forth).<br />

► Disadvantages<br />

– Creation and continuous maintenance of these scripts can require a lot of<br />

effort and therefore be expensive.<br />

– Requires every change in the environment to be scripted.<br />

– Administration tasks performed through the Integrated Solutions Console<br />

in the existing environment are not migrated,<br />

Automated migration with whole node upgrade<br />

This migration approach relies on the runtime migration tools provided by<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Network Deployment. As when migrating a whole<br />

node, the existing <strong>WebSphere</strong> V5 / V6 configuration is initially recreated in<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>.". Subsequently, one node after the other<br />

can be migrated whereby you have to consider that all applications on a node are<br />

migrated at the same time.<br />

This approach provides the following advantages and disadvantages:<br />

► Advantages<br />

– There is no need for self-written scripts. All migration is done using<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> tools.<br />

– All the information of the current configuration is moved to <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>. Therefore you do not have to worry about missing<br />

something.<br />

► Disadvantages<br />

– All the information of the current configuration is moved to <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>. The disadvantage of this approach is that you will<br />

also move configuration items that you no longer need.<br />

– All applications on the node being migrated must be ready for migration at<br />

the same time. Therefore, the time of migration is triggered by application<br />

availability.<br />

– Manual enablement of some upgraded features is still required.<br />

– This approach is only viable if you are not redesigning your environment<br />

Chapter 15. Migration 485

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!