Home > Articles > Web Services > Cloud Computing

  • Print
  • + Share This
Like this article? We recommend Case Studies in Migration

Case Studies in Migration

This section presents several case studies that illustrate the overall procedure and critical points for migrating workloads.

Case Study 1: Migration of a J2EE Application

Our goal in this case study is migration of a J2EE application running in WebSphere from one data center to another, to avoid downtime caused by a maintenance activity. It uses the WebSphere Application Server 8.5 image in the SCE image catalog as an image base. The tools available in the WAS 8.0 image will be used to migrate the J2EE application. All steps can be performed using command-line tools or scripts to enable automation, avoiding the need to use a GUI over the Internet. A DNS service directs users to the secondary server at the new data center; a BIND server is configured to do this. In addition, there is a HTML redirection at the IP of the primary to the secondary to allow for DNS cache refresh that may be caused by caching in users' browsers. Figure 4 shows the procedure.

Figure 4 Migration of a J2EE application.

These are the required steps:

  1. Set up the primary environment.
    1. Provision the primary server on an instance of WebSphere Application Server 8.5.
    2. Deploy the application to WAS.
    3. Configure IBM HTTP Server.
    4. Set up the DNS system on an instance on the cloud.
    5. Test the application.
  2. Set up the secondary system.
    1. Repeat deployment of the application as for the primary system.
    2. Redirect traffic to the secondary system with DNS.
    3. Post the maintenance message on the primary.
    4. Test that the secondary system acts as a replacement transparently to the client.

The key to this scenario is the use of the BIND DNS server. Install and start BIND from the Linux yum repository with the commands in Listing 3.

Listing 3—Installing and starting BIND.

$ sudo /bin/bash
# yum install bind
# service named start

You'll need to add a zone statement for your domain and include a zone file that contains the individual resource records for the domain. Edit the main configuration file /etc/named.conf.

Case Study 2: Using rsync to Synchronize Files for a Database Application

This case study demonstrates using rsync to synchronize a directory tree from a primary to a secondary virtual machine. rsync is an ideal tool for this purpose because it detects changes in the directory tree in the primary system efficiently and then compresses and copies those changes on the secondary system, where they're reassembled. The case study uses Apache Derby as an example database.

The steps to perform the migration are as follows:

  1. Set up Derby on the primary server.
  2. Create a database.
  3. Create a table and add a record.
  4. Use rsync to copy the database files.
  5. Test that you can view the database records in the secondary system.
  6. Add more data to the primary database, synchronize, and test for the new data on the secondary.

Figure 5 illustrates this procedure.

Figure 5 Migration of a Derby database.

The key to this scenario is the rsync command. Run the command in Listing 4 from the primary system to the secondary system to copy the MigrationTest directory. You need to have the SSH key on the primary server in the .ssh directory. You should execute the command from the command line of the primary server.

Listing 4—Copying the database directory with rsync.

$ rsync -avz -e "ssh -i .ssh/<key_name>" /home/idcuser/<database directory>

The command <key_name> holds the SSH key filename, <database directory> is the directory where the Derby database is contained, and <secondary_server_ip> is the IP address of the secondary server.

Case Study 3: WebSphere Application Migration with Profiles

This case study is an example of the tools and approach for migrating a more complex application. The steps for the setup of the primary system are as follows (see Figure 6):

  1. Set up the Derby database.
  2. Enable user authentication.
  3. Run Derby in network mode.
  4. Run the Derby client in network mode.
  5. Install the example application.
  6. Perform WebSphere configuration with wsadmin Jython scripts.
  7. Create a JDBC provider.
  8. Create an authentication alias.
  9. Create and test a data source.

Figure 6 Migration of a WebSphere application using profile export.

WebSphere profiles include the applications packaged in them, as well as all other configuration settings. We'll use export of a profile to a configuration archive to migrate our upgraded example application. These steps are already automated in the WebSphere images in the SCE catalog, except for the additional customization specific to deployed applications.

The migration steps are as follows:

  1. Export the profile configuration archive from the primary WebSphere system.
  2. Copy the files to the secondary server.
  3. Test the database.
  4. Import the profile.
  5. Update the profile for the new hostname.
  6. Perform additional customization for application-specific settings, such as data sources.

Exporting and importing profiles requires a WebSphere restart. Use the manageprofiles command to export the profile. First stop the web server and admin server from the idcuser login. These steps are shown in Listing 5. Start the procedure logged in as idcuser in the SCE Linux virtual machine running WebSphere.

Listing 5—WebSphere profile export from the primary server.

$ sudo /opt/IBM/HTTPServer/bin/apachectl stop
$ sudo /opt/IBM/HTTPServer/bin/adminctl stop
$ su - virtuser
$ /opt/IBM/WebSphere/AppServer/bin/stopServer.sh server1
$ /opt/IBM/WebSphere/AppServer/bin//manageprofiles.sh -listProfiles
$ /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh
 -backupProfile -profileName AppSrv01
 -backupFile /home/virtuser/AppSrv01.car
INSTCONFSUCCESS: Success: The profile backup operation was successful.

Copy the backed-up profile from the previous step to the secondary server, stop the application server, and use the manageprofiles command to delete the existing profile and import the new one. These steps are shown in Listing 6.

Listing 6—Import of the WebSphere profile on the secondary server.

$ su - virtuser
$ /opt/IBM/WebSphere/AppServer/bin/stopServer.sh server1
$ /opt/IBM/WebSphere/AppServer/bin//manageprofiles.sh –delete AppSrv01
$ rm -rf /opt/IBM/WebSphere/Profiles/AppSrv01
$ /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh
 -restoreProfile -backupFile /tmp/AppSrv01.car
INSTCONFSUCCESS: Success: The profile was successfully restored.
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020