In the project, we are looking to migrate the application from Jboss EAP 6.4 to Wildfly 21?
Can anyone suggest:
what are the factors we need to take into consideration?
How I can do that?
what changes I required to do that?
You should take a look at https://github.com/windup as it will analyse all the required changes
Related
I am looking for the reasoning which version of JBOSS or WILDFLY I should choose for migration. Can somebody tell I should go for JBOSS AS5 but not JBOSS AS7 or even WILDFLY 8. My application is using EJB 3 and struts 1.2.8 with EAR packaging.
You should ask yourself which are the reasons why you want to migrate.
Did you hit a critical bug?
Do you need new features?
Do you need support?
JBoss 4 and 5 rather similar, but both outdated. Support for EAP5 ended 2013. You won't get much community-support either. If I decide I had to migrate, i would migrate to the latest EAP or stable WildFly version depending on the needs for support.
I'm looking for guides regarding specific details / instructions to migrate our app.
The closest I have found is this.
But that is about AS 4.2 GA to EAP 6.2.
Can anyone guide my poor soul? Please help.
I cant tell if this is an "answer". But just leaving this here in case somebody needs it.
We've now successfully ported our app with no errors. What fixed our problem was just properly adding our machine's hostname in /etc/hosts.
In our case, there were no other "porting-specific" files to change. Its either our app didnt use very complex features, or I think maybe AS 7 -> EAP 7 is just a direct port?
Anyways, cheers :D
I am working on building a workflow application and I'm planning to use JBPM as my BPM framework. Can anyone suggest me which is the stable version to use in producation environment?
You can try with enterprise release of jBPM which is Red Hat JBoss BPMS. Red Hat will provide hot-fix patches to known issues. Also rollup patches are provided on certain interval, which includes fix for multiple issues. Along with all this you will get 24x7 support for issue.
Just let you know, I have been using jbpm 6.5 with docker in production for 2 months. All work smoothly
My current application is running with JBPM 4 on JBoss 4.0.3 application server. We are planning to upgrade Jboss AS to 7.2 in the near future and we want to know the compatibility of JBPM4 with Jboss 7.2. We are unable to find useful documentation on compatibility between JBPM 4 and Jboss AS 7.2. Please help.
I wud suggest to migrate jBPM 4 also to latest version (6.X) as i have also worked on 4.x and moved back our application to 3.2.X becuase there was no product support aprat from community(https://developer.jboss.org/thread/150947).
Regarding the documentation and compatibility i think it shud work but again you need to test at your end only.
Post results here so it will be helpfull for other also.
Now we have a project with java 1.4 and ejb 2.1 running on jboss 3.2.1. We are trying to update up to java 6 and ejb3.1, but we are doing it in steps. So my question is simple, can we use ejb2.1 on jboss6?
In theory, yes. EJB 2.x is still part of the current JavaEE spec, and JBoss6 supports it fully.
However, JBossAS 3.x and 6.x are architecturally very different to each other. Do not assume the upgrade will be a smooth one, it may well feel like migrating to a completely new appserver.