Hide Forgot
Date of First Response: 2007-11-16 04:39:05 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 EAP to SOA Platform - we need to define, document, and verify/test the process by which users can migrate - including users running the EAP as installed from RPMs.
The test execution of this test will be tracked in Testify
Link: Added: This issue is a dependency of JBQA-926
From converstaion with Burr The process is upgrade to the appropriate EAP following the EAP procedure - Install the SOA Platform into /usr/soa_p/ - Drag & Drop your wars,ears,jars from the EAP to /usr/soa_p/jboss_as/server/all
We'll verify this during the doc reviews - the comment from Burr should also be in the getting started guide.
Assigning to Josh to make last doc changes
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. Many applications will 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.