6 Replies Latest reply on Aug 2, 2016 7:25 AM by dvrajitha

    Jboss AS/ESB application migration

    dvrajitha

      Hi All,

       

      I want to clarify two things.

       

      1. Can windup use to migrate application from Jboss SOA 4.2 to Latest ESB.

      2. Can windup use to migrate application from Jboss AS old version to new Wildfly

       

      If it is true what is the value for --target flag ? can i use 'eap' as normal.

       

      This is a new migration that i need to do and still not 100% sure about which version. If some one has already done this please share you view.

       

      Thank you.

        • 1. Re: Jboss AS/ESB application migration
          manarh

          Hi Rajitha,

           

          ad1) We don't have updated rulesets for the latest JBoss ESB which should be read as project Switchyard.

          ad 2) Yes, you can used Windup to analyse migration from JBoss AS 5/6 to Wildfly 10/EAP7.

           

          If you are not sure with source or target technology you can list available technologies by using

          --listSourceTechnologies or --listTargetTechnologies option on command line. For your concrete case you need to use only--target eap7

          • 2. Re: Jboss AS/ESB application migration
            dvrajitha

            Hi Marek,

             

            Thank you very much for the reply. I have 1 more question.

             

            3. Can we use windup to migrate from Jboss SOA 4.2 to Wildfly/EAP

             

            Thank you again.

            • 3. Re: Jboss AS/ESB application migration
              manarh

              I am afraid not, JBoss SOA-P 5 is outdated now too and based on EAP 5. We have rulesets from SOA-P 5 to FSW (JBoss Fuse Service Works 6) and I am not sure if these cover all features to migrate from. You can try with source = soa-p and target = fsw

              • 4. Re: Jboss AS/ESB application migration
                dvrajitha

                Thank you for the reply.

                 

                Now i have few more questions .

                 

                Since current application is based on Jboss SOA 4.3 (it is 4.3 not 4.2) What is the ideal platform to move on.? Is following platform evolution is right? if not please correct me.

                 

                Jboss SOA --> Jboss ESB --> Then ??

                Jboss AS --> Wildfly

                 

                Since existing application is based on JBoss SOA 4.3 what should be the target platform that application needed to be migrate?

                • 5. Re: Jboss AS/ESB application migration
                  manarh

                  I am not export on SOA platform product evolution, so bear my response as general info only.

                   

                  AFAIK JBoss SOA-P 4 or 5 includes JBoss ESB as a component. The successor product is JBoss FSW 6 (Red Hat JBoss Fuse - Red Hat Customer Portal)

                   

                  JBoss AS 4/5 -> JBoss AS 7 -> Wildfly 8/9/10 this line is the same as EAP 4/5 -> EAP 6 -> EAP7 if you work with products.

                   

                  Please find your recommended migration path with SOA-P /FSW support

                  • 6. Re: Jboss AS/ESB application migration
                    dvrajitha

                    Thank you Marek, This is a great help.