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.

Automated migration with mixed version use<br />

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

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Network Deployment. Like when using the<br />

“Automated migration with whole node upgrade” on page 485 in the first step the<br />

existing <strong>WebSphere</strong> V5 / V6 configuration is recreated exactly in <strong>WebSphere</strong><br />

<strong>Application</strong>s <strong>Server</strong> <strong>V7.0</strong>. After that, additional new <strong>WebSphere</strong> <strong>Application</strong><br />

<strong>Server</strong> <strong>V7.0</strong> nodes are added and applications can be migrated one by one when<br />

they are ready. As soon as all applications of an old node are migrated, the old<br />

node can be removed from the configuration.<br />

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

► Advantages<br />

– There is no need for a self-written comprehensive set of scripts. All<br />

migration is performed using <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> tools.<br />

– All the information in 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<br />

missing something.<br />

– Allows more flexibility for application migration as migrations can be<br />

migrated when they are ready.<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 />

– Care must be taken if you want to re-factor your topology during the<br />

migration phase.<br />

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

15.2 <strong>Application</strong> development migration considerations<br />

This section provides a general overview of what needs to be considered when<br />

migrating applications between <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> versions.<br />

486 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

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

Saved successfully!

Ooh no, something went wrong!