Hide Forgot
Date of First Response: 2007-11-15 06:01:16 project_key: SOA The discussion of this migration scenario started in the SOA Platform test plan - http://intranet.corp.redhat.com/ic/intranet/SOAplatformQEPlan.html#migration Migration scenario - from ESB PROJECT to SOA PLATFORM - we need to define, document, and verify/test the process by which users can migrate These people may also develop on ESB project and deploy to SOA platform.
The test execution for this task will be tracked in Testify.
Link: Added: This issue is a dependency of JBQA-926
From Burr Yes. We were hoping to make sure that someone who developed a .esb archive and tested it on the project could easily run it on the platform. In our case, if the quickstarts from the project run un-modified on platform then we've done the job. The goal is to manage all of those users who might start on the project then decide at a later date they wish to be on the supported bits.
We'll verify this during the doc reviews - the comment from Burr should also be in the getting started guide.
Assigning to Josh - doc issue
All of the jBPM related quickstarts in the platform 4.2.1GA branch had to be rewritten for the new jBPM integration. So they won't work on the SOA Platform. Many quickstarts will work though. But I suspect the easiest thing to say is what Len has said: CP1 works, but everything else is unknown.
Upgrading from JBoss ESB 4.0 You will need to perform a clean install of JBoss Enterprise SOA Platform. Please refer to the steps detailed in Section 1.3, "Installing the SOA Platform". Once you have done this you can copy your ear, war, and jar files from your ESB installation into the appropriate SOA Platform folder: either <install_location>/jboss_as/server/production in the case of the embedded JBoss EAP version, or <install_location>/jboss_as/server/default in the case of the standalone version. You should then test your applications to see if they function. Some applications may work with no modification, but 100% code portability between the JBoss Enterprise SOA Platform and JBoss ESB is not guaranteed. Upgrading from JBoss ESB 4.2 You should install the SOA Platform as per the instructions in Section 1.3, "Installing the SOA Platform". You will need to move your applications to the newly installed platform manually, where you should test them to see if they require modification. There have been significant changes from 4.2.1GA, especially in the area of JBPM integration. Applications developed for ESB 4.2.1CP1 may not require any modification to run on the JBoss Enterprise SOA Platform.