Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Select a language:

  • Close [x]
  • Close [x]

Migrating WebSphere InterChange Server solutions to WebSphere Process Server V6: Part 2. Artifacts generated by migration

Philip McKinstry (philm1@us.ibm.com), Senior Software Engineer, EMC
Philip McKinstry is a senior software engineer at IBM Austin Lab in Austin, Texas. He is the technical team lead for the team of developers working on migration support in WebSphere Process Server.
Jonathan Schweikhart (jschweikjschweik@us.ibm.com), Software Engineer, EMC
Jonathan Schweikhart is a software engineer at the IBM Austin Lab in Austin, Texas. He is a member of the development team working on migration support in WebSphere Process Server.

Summary:  Part 2 of this article series explores the source artifacts migration capabilities provided in IBM WebSphere Process Server v6.0, specifically to support migration from WebSphere InterChange Server. It investigates the types of artifacts that are generated by migration in the simple WebSphere InterChange Server solution introduced in Part 1 of this series.

Date:  16 Dec 2005
Level:  Intermediate

Activity:  1011 views
Comments:  

Get the downloads

Part 2 of this article series explores the source artifacts migration capabilities provided in IBM WebSphere Process Server v6.0, specifically to support migration from WebSphere InterChange Server. It investigates the types of artifacts that are generated by migration in the simple WebSphere InterChange Server solution introduced in Part 1 of this series.

What is this article series about?

Now that you've completed Part 1 of this series, you are ready to examine the types of IBM® WebSphere® Process Server artifacts that were generated by migration from the simple IBM WebSphere InterChange Server solution presented in Part 1. Once you understand the purpose of these artifacts, you should be able to maintain and enhance the new versions of WebSphere Process Server solutions.

You should have a good understanding of WebSphere InterChange Server and the source artifacts that comprise a WebSphere InterChange Server solution. Knowledge of the WebSphere Process Server programming model is also recommended.

Part 1 of this series guides you through the migration of a simple WebSphere InterChange Server solution and the steps to test the migrated applications using the Visual Test Connector (VTC).

Part 3 of this series walks you through the migration of a complex WebSphere InterChange Server solution, discusses limitations of the current migration support, and explores some workarounds along the way.


Downloads

DescriptionNameSizeDownload method
code sampleSample_Application.zip9.3 MBHTTP
Article in PDF format0512_mckinstry-WICS2WPS_migration_p22.4 MBHTTP

Information about download methods          Get Adobe® Reader®


Resources

Biographies

Philip McKinstry is a senior software engineer at IBM Austin Lab in Austin, Texas. He is the technical team lead for the team of developers working on migration support in WebSphere Process Server.

Jonathan Schweikhart is a software engineer at the IBM Austin Lab in Austin, Texas. He is a member of the development team working on migration support in WebSphere Process Server.

Comments

Back to top

Close [x]

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Close [x]

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=100895
SummaryTitle=Migrating WebSphere InterChange Server solutions to WebSphere Process Server V6: Part 2. Artifacts generated by migration
publish-date=12162005
author1-email=philm1@us.ibm.com
author1-email-cc=
author2-email=jschweikjschweik@us.ibm.com
author2-email-cc=

Dig deeper into WebSphere on developerWorks

My developerWorks community

Interact, share, and communicate with developers worldwide.

My developerWorks overview

Try IBM PureSystems. No charge.

IBM PureSystems on a kaleideoscope background

Experience today!

Get started with the cloud-based trial and pattern development kit.

Share this page:

  • Close [x]

Follow developerWorks:

  • Close [x]