[Desktop] Hi, I'm Ondřej Žižka. I'm gonna take a few minutes today to introduce Windup. [github.com/windup] Windup is an opensource PROJECT that is intended to help migration from different application platforms to JBoss. Different platforms include WebLogic to JBoss, WebSphere to JBoss, perhaps even JBoss to JBoss if you're upgrading. [app folder window] It runs against either a source code, or compiled applications, for which it uses decompiler. [commandline] It's kicked off by the command line and it PROFILES different resources within the application to produce HTML report that will help with assessment of the application and the migration after. =========================================================================================================== [Report Index] Windup report shows several views on the information gathered. The first view you see is the ten thousand feet view which shows very quickly what the application is made of. [Application Details] ... -> first sub-jar then a report of things that will require your attetion during migration, [Migration Issues] and index of the same information sorted by cause, [...other reports] and then various specialized reports like EJB report showing EJB beans, JPA report showing entities, and so on. Besides that, each analyzed file is available as a source code with the highlighted places with an advice on how to proceed. ----------------------------------------------------------------------------------------------------------- [App details - scroll to the WAR] Windup does two things: It classifies the resources at various levels like JARs, datasources, WSDL endpoints, JNDI calls and descriptors which is used to recognize what the application consists of. And it provides hints on how to migrate the code which needs it, according to your target platform. In other words. If you have an application that you are responsible for migrating, Windup makes it very simple to jump for an application you may have no knowledge of and very quickly come up to speed. We also define "story points" which give you a rough estimate of how much effort the migration will take. [Scroll to the top] So, what are story points? It is an agile methodology definition of effort. The reason we use it, as opposed to hours, is that for teams with previous migration experience, the migration tasks it will take less time, and vice versa. [Migration Issues] -> WebLogic...Listener link The Application Details and the Migration Index views link to all of the resources that Windup recognized as relevant to the migration. Within these linked resources view, Windup shows full syntax highlighting of different resources like Java files, XML's, JSP files, Manifests, and so on. And at the very top of this source view, it's going to show the classification of this resource, so we can say "Hey, it's a WebLogic application lifecycle listener, and it must be migrated." Additionally, we can provide links, as you can see here, to relevant articles defining how to migrate that particular resource, and you can add these links very easily. [line 43] You can also see that we can add inline hints to the source code, so in this particular case the MBean server is doing a context lookup from InitialContext, and so Windup has provided full syntax inline hints that describe how to migrate JNDI reference to JBoss. =========================================================================================================== [Github.com - XML rule] Extending Windup is easy. There's no Java code required at all, it's all XML, and the whole idea is that you can very quickly add your rules. Windup itself packages a default set of rules, and you can add your own into a folder in your user directory. [Github.com - quickstarts tab] Windup project provides a quickstarts repository on Github, so you can very quickly stub out new Windup migration rules, and then provide them back to the project so they can be incorporated in the base ruleset. [Github.com - XML rule] What Windup rules look like? All of the Windup rules targetting Java projects migration are in a special XML syntax. You may find the rules on github in the windup-rulesets repo. [Home - Wiki - How to contribute] So how can you contribute. Even if you don't have time to create rules, we appreciate to know what Windup should cover. [Jira - https://issues.jboss.org/browse/WINDUPRULE-159] If you know how to migrate something not covered by Windup rules yet, create a Jira issue at issues.jboss.org/browse/WINDUPRULE or just send us an email to windup-users@lists.jboss.org . [Github.com - windup-rulesets] If you create a rule, you can attach it to jira or email. Ideal, of course, would be a pull request to github/windup/windup-rulesets. [Home - Wiki - How to contribute] If you have any questions, you can contact us directly at these contacts. All information you need is at windup.jboss.org.