[RakutenTechConf2013] [E-3] Financial Web System with Java EE 6

Editor's Notes

• #2: Hello, let's get started my presentation. "Financial web system with Java EE 6".
• #3: My biography. I'm a financial system vice group manager of Rakuten.And a professional of enterprise financial system management, planning and development.
• #4: This is agenda. First, I'll talk about the Java EE 6 specs, second, financial requirements and Java EE specs, and last, how to apply EE 6 to real financial systems.
• #5: Next.
• #6: What is Java EE. The answer is "standard spec for applications servers", but unfortunately, Microsoft excluded. They worked together for EE specs, but unfortunately, parted in anger at the end of 20th century.
• #7: What is "Enterprise"?At first, enterprise requires transactional system, and it represented by EJB with JTA container managed transaction.And each Java EE specs convers general enterprise requirements.
• #8: This is history of Java EE. The first name is JPE, Java Professional Edition in 1998, and the revised first version is J2EE 1.2.Before the J2EE, NetBeans and WebLogic were already released, and after J2EE, many products and libraries were born.But after J2EE 1.3, Microsoft released .NET Framework, and confused the Java EE world with many blames about the configuration complexity.After Oracle acquired Sun, they cleared the complexity and united under a single specification again.
• #9: This is the grouping of the Java EE products. 3 big servers are WebLogic by Oracle, WebSpehere by IBM, and JBoss by Red Hat, and additional Japanese group.And these have free open source version, GlassFish, Geronimo, and WildFly. Their competitors are Google App Engine, and Microsoft .NET Framework.
• #10: And each app server target spec is as shown. Very complex.And the de-facto latest version is Java EE 6. Generally, if you want to plan JEE system, consider EE 6 firstly.Anyway, I want to reflect these version matrix to Wikipedia.
• #11: Next, financial requirements and Java EE specs.
• #12: Here at Rakuten, we have 6 big services of financial.Rakuten Card, Rakuten Bank, Rakuten Edy, Rakuten Security, Rakuten Life, Rakuten Insurance.
• #13: Each service has many enterprise systems including Java EE.And each enterprise services has huge transactions.Especially almost web front-end is twenty-seven non-stop services.
• #14: Let's dig a little deeper. The big 3 requirement of Rakuten financial systems.First, rapid changeable logics, Second, huge request expansion capacity, and last, transactional.Very hard requirements for systems.
• #15: Historically, Japanese held these periodic re-construction in many areas, like a "式年遷宮" at Japanese shrines.We planned that our financial systems should be done in the same way for the next 3 big targets.
• #16: We aim to realize the system which is sustainable, flexibility and transparent to catch some errors immediately.And these are not only the new architecture, but the requirements.
• #17: Then let's see the typical usage of Java EE 6 specs.Almost all enterprise systems requires data source, and each source type requires suitable framework, JPA, JMS, RMI-IIOP and JAX, and Java Mail. And these data connectivity framework operated transactionaly by EJB.Finally front-end frameworks like JSF & JavaFX call EJB. These are the basic Java EE structure.
• #18: And the EJB interfacescan be considered as the 'services', or 'web API'.It doesn't have any user interface, only has pure data interfaces.
• #19: And some interface must be re-used by another interface, view, or functions. Called 'Shared functions'.We called these design as 'API-nization'.This is a required basic strategy for the enterprise systems to re-use business logics.
• #20: Next shows enterprise transactional model.This is a very basic model for the transaction processes, begin (or start) & commit.
• #21: If some error occurred, all processing data must be roll backed completely and safely.It means one or zero, or all or nothing.These basic operations must be implemented to core financial systems completely, or some financial data, especially some money data, must be broken.
• #22: Next, consider the real financial systems. It has many data sources, including some databases, message queue servers, and other transactional systems.When a transactional service which is calling some transactional services called, the local transactions must be gathered.It is called global transaction.
• #23: Of course this complex model also has transactional abilities.If some database or MQ or services fails with some error, all data source must be roll backed.This is the huge financial requirements.
• #24: And the Java EE supports this big structures.Each data source calling supported by JPA, JMS and RMI-IIOP, and operated by EJB and JTA.As you might know, Java EE core specification is still EJB, not Servlet or JSPs.
• #25: Next, the last part, how to apply Java EE 6 to real financial systems.
• #26: I planned the Java EE to real financial systems, with these 5 big issues.1st, policies, 2nd, education, 3rd, architecture, 4th, environment, and 5th, test.
• #27: 1st, policies. In the case of Rakuten, we have a policy, "internal development first". Of course, financial systems also. No basic policies to throw external vendors.We must clear this core policies, and consider the next solutions to run.
• #28: 2nd, educational issues. Read, read, and read.There's many good Java EE books in book stores, but English book only, not Japanese.Fortunately, we already changed our standard language to English, and many programmer can read them.
• #29: And there are many useful articles in world wide web.Thanks to the NetBeans team, nice tutorial are still in the web site.Refer to this site if you want to start Java EE development.
• #30: 3rd, I designed to apply Java EE 6 specs to the new architecture.Basic structure is obeyed to standard architecture, and applied front-end to JSF.And due to the no rich client requirement, I skipped JavaFX spec.
• #31: We had some older systems to integrate to the new architecture.In the PHP case, we designed each from PHP business logics to the EJB API codes. Full rewriting, 100% API-nized for re-use & collaborating services in the future.
• #32: We also re-designed the application module blocks. Center API-nized logics, with many front-ends. All business logic designed as API, with SOAP, REST, and IIOP protocol access enabled for future service-oriented architectures to simplify.
• #33: For the ease of development, we adopt the new IDE, NetBeans 7 with Apache maven automatic building systems. And we build full local programming environment to easy coding & run for rapid programming.
• #34: We made the easy startup environment to reduce startup costs.If some programmer attends the project, 2. just download from git server, 3. install tools, and 4. refer to JIRA for his or her for today's task management.
• #35: And to educate the accurate programming manners,we introduced Jenkins auto-building server with static security analyzers, Sonar & VeraCode. And we achieved zero violations before the new system release.
• #36: Ok, we have some additional time to talk to the real Java EE 6 world. Unveiled.
• #37: Is the Java EE 6 useful? for real project?My answer is for the backend, it is so-so, but for the web front-end, it is difficult. I want to say "wait the Java EE 7".
• #38: The reasons. 2 big problems found in our real projects.First, JSF backing bean conflict CDI managed bean specifications.Second, JSF HTML-styled tags were changed in JSF 2.2.
• #39: 1st issue, JSF backing bean defectively. When some facelet or managed bean set to the session scoped bean, the filter cannot access to the session scoped bean directly.
• #40: Some blogs and web sites shows these codes to access backing bean from non-JSF objects, but not worked properly in JSF 2.So we must override phase listeners for filtering, but very harmful and uncertain codes required.
• #41: Of course you can switch the backing bean from JSF managed bean to CDI bean.But unfortunately, Java EE 6 CDI didn't have @ViewScoped annotations, so we cannot use one-by-one style with facelets.I cannot understand this conflicted situation in EE 6.
• #42: In EE 7, these conflicts are already cleared and well integrated with JSF and CDI.CDI added @ViewScoped annotation to access one-by-one style with facelet.This strategy must be considered in the first JSF, but achieved in Java EE 7. It's too late for us!So wait for the Java EE 7 if you can.
• #43: Java EE 6 has some irregular tags named 'jsfc'.Java EE 7 JSF 2.2 changed these silly tags to XML schema compliant style. It's good for applying standards, but there's many cost required for updating from JSF 2.1.So, you should start from Java EE 7 if you can.
• #44: In the contrary, back-end side of java EE 6 seems almost been completed as its requirement for enterprise systems. EJB, JTA, JPA, JMS are already established the basic style, and just a small improvements in EE 7. Please start right away from EE 6 for background!
• #45: Last, here's my conclusion.
• #46: Java EE 6 is suitable for huge financial systems.And we made new financial architecture with many education and measurements.Make our enterprise future with Java EE.
• #47: That's all. Thanks for listening, have a good day.