Bug 777493 (SOA-5)

Summary:	Migration scenario - from EAP to SOA Platform - we need to define, document, and verify/test
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Len DiMaggio <ldimaggi>
Component:	Documentation	Assignee:	Joshua Wulf <jwulf>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	lcarlon, ldimaggi
Target Milestone:	---
Target Release:	4.2 CR3
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-5
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-07 06:05:18 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Len DiMaggio 2007-08-21 15:24:49 UTC

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.

Comment 1 Len DiMaggio 2007-08-23 19:19:52 UTC

The test execution of this test will be tracked in Testify

Comment 2 Len DiMaggio 2007-08-28 19:15:37 UTC

Link: Added: This issue is a dependency of JBQA-926

Comment 4 trev 2007-11-16 09:39:05 UTC

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

Comment 5 Len DiMaggio 2007-11-16 21:40:07 UTC

We'll verify this during the doc reviews - the comment from Burr should also be in the getting started guide.

Comment 7 Len DiMaggio 2008-02-05 13:40:15 UTC

Assigning to Josh to make last doc changes

Comment 9 Joshua Wulf 2008-02-07 06:05:18 UTC

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.