| Author |
Message
|
| kanchan |
 Posted: Fri Jun 29, 2007 5:27 am Post subject: Migration to Native java API |
 |
|
Newbie
Joined: 29 Jun 2007
Posts: 3
Location: BANGALORE
|
Want to migrate form classic WF java API(fmcojagt.jar) to WF native API(fmcjapi.jar), but we want to access the services of PEA. ie want to fetch incontainer and outcontainer values with pea object(i.e Activity Implementation). Is their any way of acheiving this with the help of fmcjapi.jar.
Thanks in advance.... |
|
| Back to top |
|
 |
| jmac |
| Posted: Fri Jun 29, 2007 5:35 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
It is my opinion that you can not use a PEA with Native Java API
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kanchan |
| Posted: Sun Jul 01, 2007 9:54 pm Post subject: |
|
|
Newbie
Joined: 29 Jun 2007
Posts: 3
Location: BANGALORE
|
thanks john, then you mean to say i should rely on fmcojagt.jar, can any fix pack be able to fix this problem. pls suggest any other alternatives. If not we need to modify the entire application to migrate from 3.5 to 3.6, coz most of the activities in our implementation are PEA activities.
thanks in advance |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jul 02, 2007 5:24 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
You will have to use fmcojagt (or fmcojapi) jar files if you are using PEA. I believe that the "classic" java api is still supported. Is there some compelling reason you want to move to fmcjapi? IBM's stated direction for many years on MQWF was to move away from PEA.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kanchan |
| Posted: Mon Jul 02, 2007 9:29 pm Post subject: |
|
|
Newbie
Joined: 29 Jun 2007
Posts: 3
Location: BANGALORE
|
| thanks john, their is no such compelling reason, we will use fmcojagt.jar. However currently workflow 3.6 supports classic java API, But how about future releases of workflow versions, If they won,t support classic java API, then atleast we need modify our Application right. |
|
| Back to top |
|
|
| hos |
| Posted: Tue Jul 03, 2007 12:15 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
if you intend to use MQWF for a long period of time and maybe add new applications, I urgently recommend to move from PEA to UPES. MQWF 3.6 provides an UPES framework and it is not a big deal to migrate your applications to UPES logic. |
|
| Back to top |
|
|
|
|
