Preventive Service Planning
Abstract
This Technote will be the primary source for WebSphere Adapter Migration information. It will be regularly updated with the latest information, references and frequently asked questions.
Content
1. Looking for Migration information specific to:
WebSphere Business Integration (WBI) Adapters
WebSphere Process Server
WebSphere Process Server Runtime
WebSphere Enterprise Service Bus
Migration steps
Migration tool reference information - Technote links
Migration tool reference information - Information Center links
2. Need help in making migration decision (when to migrate)?
WBI->JCA:
- a. If plans are to migrate from InterChange Server (ICS) to WebSphere Process Server, the WBI Adapter and applications need to be migrated to JCA adapter and applications.
b. WBI->JCA adapter migration tool cannot migrate custom DataHandlers.
c. WBI->JCA adapter migration tool support matrix. Please refer to the detail below in this document
JCA->JCA:
- If WebSphere Process Server 6.x is migrated to WebSphere Process Server 7.x, the deployed adapters and applications need to be migrated. All the adapters and applications need to be exported and migrated using WebSphere Integration Developer based tooling migration, and then redeploy the migrated adapters and applications to new WebSphere Process Server 7.x.
3. What if the migration failed in the middle?
- The whole migration process will be rolled back to its original.
WebSphere Business Integration (WBI) Adapters
WBI Adapter Version to Version Migration support matrix
Y: the specific migration path is supported
---: the specific migration path is not supported
WBI to JCA Migration
| WBI adapter | 7.0 | 6.2 | 6.1 | 6.0.2 |
| Y | Y | --- | --- | |
| FlatFile | Y | Y | --- | --- |
| FTP | Y | Y | --- | --- |
| IBM i | --- | --- | --- | --- |
| JDBC | Y | Y | --- | --- |
| JDE | Y | Y | --- | --- |
| LotusDomino | --- | --- | --- | --- |
| OracleEBS | Y | --- | --- | --- |
| PeopleSoft | Y | Y | Y | --- |
| SAP | Y | Y | Y | --- |
| Siebel | Y | Y | --- | --- |
Tooling migration in WebSphere Integration Developer
JCA Adapter Version to Version Migration support matrix
Y: the specific migration path is supported
---: the specific migration path is not supported
n/a: the source version of the adapter was not available
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
FlatFile
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
FTP
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
IBM i
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | n/a | n/a | n/a | n/a |
| JCA 6.1.0.x | n/a | n/a | n/a | n/a |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
JDBC
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
JDE
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
LotusDomino
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | n/a | n/a | n/a | n/a |
| JCA 6.1.0.x | n/a | n/a | n/a | n/a |
| JCA 6.2.0.x | n/a | n/a | n/a | n/a |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
OracleEBS
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | --- | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
PeopleSoft
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
SAP
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
Siebel
| Source version | 7.0.0.x | 6.2.0.x | 6.1.0.x | 6.0.2 |
| JCA 6.0.2 | Y | Y | Y | --- |
| JCA 6.1.0.x | Y | Y | --- | --- |
| JCA 6.2.0.x | Y | --- | --- | --- |
| JCA 7.0.0.x | --- | --- | --- | --- |
| JCA 7.0.1.x | --- | --- | --- | --- |
WebSphere Process Server Runtime
When WebSphere Process Server is migrated to a new version, the old JCA adapters that installed in old WebSphere Process Server can be automatically copied to the new WebSphere Process Server version and then they will be upgrade to new JCA adapter version. This is adapter runtime migration support in WebSphere Process Server.
This is the adapter runtime migration support matrix:
Y: the specific migration path is supported
M: supported but need manual steps post migration
---: the specific migration path is not supported
n/a: the source version of the adapter was not available
| Adapter | 6.2.x-> 7.0.0.3 | 6.1.x-> 7.0.0.3 | 6.0.2 -> 7.0.0.3 |
| Y | Y | Y | |
| FlatFile | Y | Y | M |
| FTP | Y | Y | Y |
| IBM i | Y | n/a | n/a |
| JDBC | Y | Y | Y |
| JDE | Y | Y | Y |
| LotusDomino | n/a | n/a | n/a |
| OracleEBS | Y | n/a | n/a |
| PeopleSoft | Y | Y | Y (6.0.0->7.0.0.3) |
| SAP | Y | Y | --- |
| Siebel | Y | Y | Y |
Note: For V6.0.2 FlatFile adapter, post migration manual steps in new WebSphere Process Server are needed. Users need to manually change the element name from “content” to “Content” in the Flat File XSD as well as any wrapper XSD. The XSD files to modify reside in the deployed ear in the installedApps folder of the WebSphere Process Server server.
The following example shows the correct element name of element name="Content":
<xsd:complexType name="FlatFile">
- <xsd:sequence minOccurs="1" maxOccurs="1">
- <xsd:element name="Content" type="xsd:anyType" minOccurs="0" maxOccurs="1" />
<xsd:element name="fileName" type="xsd:string" minOccurs="0" maxOccurs="1" />
<xsd:element name="directoryPath" type="xsd:string" minOccurs="0" maxOccurs="1" />
<xsd:element name="chunkFileName" type="xsd:string" minOccurs="0" maxOccurs="1" />
<xsd:element name="fileContentEncoding" type="xsd:string" minOccurs="0" maxOccurs="1" />
<xsd:element name="includeEndBODelimiter" type="xsd:string" minOccurs="0" maxOccurs="1"/>
<xsd:element name="stagingDirectory" type="xsd:string" minOccurs="0" maxOccurs="1" />
WebSphere Enterprise Service Bus
JCA Adapter Version to Version Migration
| 7.0 | 6.2 | 6.1 | 6.0.2 | 6.0.0 |
| WBI SAP | ||||
| Migration Tool | WBI JDBC |
- Import repository jar or the project interchange files into WebSphere Integration Developer
- Let the WebSphere Integration Developer ICS migration wizard finish the workspace migration
- Right click the adapter project, and in the pop-up menu launch the adapter migration wizard
- In the migration wizard select the right adapter target version and the modules to be migrated together, click “Next” to review the change summary, and then click “Finish” and wait for the adapter/module migration process to be completed
Note: It is not suggested, to migrate without using the migration automation tool. The completed migration requires adapter replacement, class path update, BO update and artifacts update. There are too many manual steps, and they vary from adapter to adapter, so the manual update is error-prone and is not recommended.
Migration Tool reference information - Technote links
The second migrated adapter project cannot be deployed to WebSphere Process Server
SAP ALE inbound only supports Async interface for WebSphere Adapter Migration Infrastructure
Build failed after migrating one adapter from version V6.0.2 to V6.2 or above
WebSphere Integration Developer 7.0: Adapter migration fails while migrating a WebSphere Business Integration adapter containing unsupported business objects
Adapter migration fails if there are read only files that need to be migrated
Migration tool reference information - Information Center links
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.email.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.email.doc/env/shared/stsha_migrate_wbia.html
FlatFile
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.ff.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.ff.doc/env/shared/stsha_migrate_wbia.html
FTP
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.ftp.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.ftp.doc/env/shared/stsha_migrate_wbia.html
IBM i
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.iseries.doc/env/shared/stsha_migrateisa.html
WBI->JCA 7.0
Is not supported
JDBC
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.jdbc.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.jdbc.doc/env/shared/stsha_migrate_wbia.html
JDE
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.jde.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.jde.doc/env/shared/stsha_migrate_wbia.html
LotusDomino
JCA 6.x -> JCA 7.0:
N/A. LotusDomino does not have V6.x adapters
WBI->JCA 7.0
Is not supported
OracleEBS
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.oracleebiz.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.oracleebiz.doc/env/shared/stsha_migrate_wbia.html
PeopleSoft
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.peoplesoft.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.peoplesoft.doc/env/shared/stsha_migrate_wbia.html
SAP
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.sap.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.sap.doc/env/shared/stsha_migrate_wbia.html
Siebel
JCA 6.x -> JCA 7.0:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.siebel.doc/env/shared/stsha_migrate.html
WBI->JCA 7.0
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.wsadapters.jca.siebel.doc/env/shared/stsha_migrate_wbia.html
[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Adapter Migration Infrastructure","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1;7.0;6.2;6.1","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21441550