Real world batch implementations and frameworks.
These slides explores various ways in which batch processing can implemented with Java EE and other frameworks. It includes pro and cons of batch implementations with JCL, prepared statements, CDI, JSR 352 and embedded EJB containers. It helps to understand when to use JSR 352 and when not to, the benefits of using an embedded EJB container for batch processing, and the best practices to follow when designing batch processes.
Happy Java SE 8 was released! But for the Java EE?
This materials shows the current status of EE 6/7 with SE 8, and some limitation in current EE 7 app servers with 8.
This session materials is for the Japan Java Users Group (JJUG) CCC 2014 Spring session. #jjgc_ccc #ccc_r11
Many enterprise systems build at 2000 - 2010 uses J2EE old specifications with Struts web framework. But nowadays J2EE improved as Java EE, with standard web framework JSF 2. With this slides you can learn how to migrate old-styled J2EE + Struts systems to sophisticated Java EE with JSF 2 specification. This slides was used in Java Day Tokyo 2014 C4 window, presented by the author. And some slides is specialized for Japanese enterprise systems, but the theme is very standard and for almost all J2EE users in the world.
Java EE 7 from an HTML5 Perspective, JavaLand 2015Edward Burns
This 45 minute session begins by explaining what we mean by the admittedly vague term "HTML5 web application". We use the Cargo Tracker sample Java EE 7 application as the vehicle for this explanation. Diving into the code, we examine the parts of the Java EE 7 family of technologies, and the HTML5 techniques used in the application.
HTTP/2 comes to Java. What Servlet 4.0 means to you. DevNexus 2015Edward Burns
It’s hard to overstate how much has changed in the world since HTTP 1.1 went final in June of 1999. There were no smartphones, Google had not yet IPO’d, Java Swing was less than a year old… you get the idea. Yet for all that change, HTTP remains at version 1.1.
Change is finally coming. HTTP 2.0 should be complete by 2015, and with that comes the need for a new version of Servlet. It will embrace HTTP 2.0 and expose its key features to Java EE 8 applications. This session gives a peek into the progress of the Servlet spec and shares some ideas about how developers can take advantage of this exciting
update to the world’s most successful application protocol on the world’s most popular programming language.
Case Study of Financial Web System Development and Operations with Oracle Web...Hirofumi Iwasaki
To stay ahead of the technology curve, financial companies require the power, flexibility, and scalability of latest enterprise technologies for 24/7 services. Rakuten Card, one of the largest credit card companies in Japan, recently renewed its web front-end systems utilizing Java EE. This session provides answers to the following questions: Among the myriad of available technologies, why did it choose Oracle WebLogic and Oracle Exadata, managed by Oracle Enterprise Manager? How did it drive this huge project to completion in only six months, using only in-house development? What were the key success factors in launching and operating this mission-critical service? Hear about its extraordinary improvement results and how its selections are effective for financial enterprise systems.
Real world batch implementations and frameworks.
These slides explores various ways in which batch processing can implemented with Java EE and other frameworks. It includes pro and cons of batch implementations with JCL, prepared statements, CDI, JSR 352 and embedded EJB containers. It helps to understand when to use JSR 352 and when not to, the benefits of using an embedded EJB container for batch processing, and the best practices to follow when designing batch processes.
Happy Java SE 8 was released! But for the Java EE?
This materials shows the current status of EE 6/7 with SE 8, and some limitation in current EE 7 app servers with 8.
This session materials is for the Japan Java Users Group (JJUG) CCC 2014 Spring session. #jjgc_ccc #ccc_r11
Many enterprise systems build at 2000 - 2010 uses J2EE old specifications with Struts web framework. But nowadays J2EE improved as Java EE, with standard web framework JSF 2. With this slides you can learn how to migrate old-styled J2EE + Struts systems to sophisticated Java EE with JSF 2 specification. This slides was used in Java Day Tokyo 2014 C4 window, presented by the author. And some slides is specialized for Japanese enterprise systems, but the theme is very standard and for almost all J2EE users in the world.
Java EE 7 from an HTML5 Perspective, JavaLand 2015Edward Burns
This 45 minute session begins by explaining what we mean by the admittedly vague term "HTML5 web application". We use the Cargo Tracker sample Java EE 7 application as the vehicle for this explanation. Diving into the code, we examine the parts of the Java EE 7 family of technologies, and the HTML5 techniques used in the application.
HTTP/2 comes to Java. What Servlet 4.0 means to you. DevNexus 2015Edward Burns
It’s hard to overstate how much has changed in the world since HTTP 1.1 went final in June of 1999. There were no smartphones, Google had not yet IPO’d, Java Swing was less than a year old… you get the idea. Yet for all that change, HTTP remains at version 1.1.
Change is finally coming. HTTP 2.0 should be complete by 2015, and with that comes the need for a new version of Servlet. It will embrace HTTP 2.0 and expose its key features to Java EE 8 applications. This session gives a peek into the progress of the Servlet spec and shares some ideas about how developers can take advantage of this exciting
update to the world’s most successful application protocol on the world’s most popular programming language.
Case Study of Financial Web System Development and Operations with Oracle Web...Hirofumi Iwasaki
To stay ahead of the technology curve, financial companies require the power, flexibility, and scalability of latest enterprise technologies for 24/7 services. Rakuten Card, one of the largest credit card companies in Japan, recently renewed its web front-end systems utilizing Java EE. This session provides answers to the following questions: Among the myriad of available technologies, why did it choose Oracle WebLogic and Oracle Exadata, managed by Oracle Enterprise Manager? How did it drive this huge project to completion in only six months, using only in-house development? What were the key success factors in launching and operating this mission-critical service? Hear about its extraordinary improvement results and how its selections are effective for financial enterprise systems.
Java EE 6 Adoption in One of the World's Largest Online Financial Systems (fo...Hirofumi Iwasaki
Financial companies need Java EE to power its business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. You can learn why we choose Java EE, and our experiences and lessons we learned. This is the first disclosing of a large credit card company in Japan sharing their story.
How to start such a big project? Why we choose it, how we selected the in house development policies, educated ourselves, and developed the additional libraries? How to launch within only six months? What is the key factor driving them as 24/7 critical real financial systems successfully? How to migrate to EE 7 in the future? We’ll answer these questions and any that you may have.
This version is the exclusive session for JJUG CCC Fall 2014 in Japan, binding both JavaOne and OOW 2014 sessions.
JavaScript Frameworks and Java EE – A Great MatchReza Rahman
The sea change in JavaScript frameworks is shifting the pendulum away from today's thin-client based server-side web frameworks like Spring MVC and JSF to JavaScript powered rich clients. With strong support for REST, WebSocket and JSON, Java EE is well positioned to adapt to this landscape.
In this heavily code driven session, we will show you how you can utilize today's most popular JavaScript frameworks like AngularJS and React to utilize the core strengths of Java EE using JAX-RS, WebSocket, JSON-P, JSON-B, CDI and Bean Validation.
WebSocket in Enterprise Applications 2015Pavel Bucek
Presentation from JavaOne 2015.
This session, which covers use cases of JSR 356 (Java API for WebSocket) and some features of Oracle’s implementation related to enterprise applications, contains description of standard use cases and recommends optimizations and best practices for using the JSR 356 API. After that, it presents more-complex schemes involving authentication support, fallback support, and clustering.
WebLogic 12.1.3 was released late last year. It brings a large set of changes including support for some key new Java EE 7 APIs such as WebSocket, JAX-RS 2, JSON-P and JPA 2.1, support for Java SE 8, WebSocket fallback support, support for Server-Sent Events (SSE), improved Maven support, enhanced REST administration support, Oracle Database 12c driver support and much, much more. In this session we will take a detailed tour of these features. In addition we will also cover updated WebLogic support in the Oracle Cloud, the new Oracle public Maven repository, using WebLogic with Arquillian for testing and well as official Docker support for WebLogic.
Towards the end of the session we will discuss what's coming in WebLogic 12.2.1 this year including full support for Java EE 7, multi-tenancy and more.
With a strong focus on annotations, minimalist configuration, simple deployment, intelligent defaults and Java centric type-safety, Java EE is one of the most productive full-stack development platforms around today. This very code centric workshop is a quick tour of the Java EE platform as it stands today. If you haven't seen Java EE for a while and want to catch up, this session is definitely for you.
We will start with the basic principals of what Java EE is and what it is not, overview the platform at a high level and then dive into each key API like JSF, CDI, EJB 3, JPA, JAX-RS, WebSocket and JMS using examples and demos. This is your chance to look at Java EE 7 in the context of a realistic application named Cargo Tracker, available with an MIT license at http://cargotracker.java.net.
We will also briefly take a look at the emerging horizons of Java EE 8.
The days of EJB’s being the center of the Java EE universe are coming to an end. CDI is increasingly becoming the de facto component framework, due to its flexibility and lack of legacy. Starting in Java EE 7 and continuing in 8, the Java EE platform is migrating to enable all of EJB’s best features to be usable in the CDI world. In this session, you’ll learn implementation-level details on how they relate to each other, where we are in the EJB/CDI alignment story, what trade-offs you might need to make, and what you have to gain from making the transition. You will walk out with runnable examples and vendor-level insights. This is the perfect session for heavy EJB users looking to keep up with Java EE’s transition to CDI.
JavaOne 2011: Migrating Spring Applications to Java EE 6Bert Ertman
The Spring Framework has no-doubt played a major role in evolving the way we write enterprise applications on the Java platform today. However, it is still a proprietary framework owned by a single company. The age of having to rely on such proprietary frameworks in order to develop decent enterprise applications is now over and Java EE 6 has become an even easier way to develop enterprise applications based on standards which makes it the best choice for any enterprise application. In this session you will experience how to migrate a typical full stack Spring application to a standards based, completely portable, Java EE 6 application including integration tests.
Consideration points for migrating from older pre-J2EE, J2EE 1.2-1.4, Java EE 5-6 to EE 7, and migration points especially for web front-end systems and back-ends. JSP to JSF, EJB to CDI with migration procedure details. Slide materials on Java Day Tokyo 2016.
JSR 236 Concurrency Utils for EE presentation for JavaOne 2013 (CON7948)Fred Rowe
Presentation about the newly released JSR236 spec that Anthony Lai (Oracle) and Fred Rowe (IBM) did for session CON7948 at JavaOne SF 2013.
JSR 236 is part of EE7 platform and defines extensions to the SE concurrency APIs to allow them to be used in an app server environment.
Java EE 6 Adoption in One of the World’s Largest Online Financial SystemsArshal Ameen
Financial companies need Java EE to power their business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. Learn why it chose Java EE, and hear about its experiences and lessons learned. This is the first time a large credit card company in Japan is sharing its story. How do you start such a big project? Why did it choose Java EE? How did it select the in-house development policies, educate itself, and develop the additional libraries? How did it launch within only six months? What is the key factor driving 24/7 critical financial systems successfully? How do you migrate to Java EE 7 in the future? This presentation answers these questions and any others you may have.
Java EE 6 Adoption in One of the World’s Largest Online Financial Systems [Ja...Hirofumi Iwasaki
Financial companies need Java EE to power their business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. Learn why it chose Java EE, and hear about its experiences and lessons learned. This is the first time a large credit card company in Japan is sharing its story. How do you start such a big project? Why did it choose Java EE? How did it select the in-house development policies, educate itself, and develop the additional libraries? How did it launch within only six months? What is the key factor driving 24/7 critical financial systems successfully? How do you migrate to Java EE 7 in the future? This presentation answers these questions and any others you may have.
Case Study of Financial Web System Development and Operations with Oracle Web...Arshal Ameen
To stay ahead of the technology curve, financial companies require the power, flexibility, and scalability of latest enterprise technologies for 24/7 services. Rakuten Card, one of the largest credit card companies in Japan, recently renewed its web front-end systems utilizing Java EE. This session provides answers to the following questions: Among the myriad of available technologies, why did it choose Oracle WebLogic and Oracle Exadata, managed by Oracle Enterprise Manager? How did it drive this huge project to completion in only six months, using only in-house development? What were the key success factors in launching and operating this mission-critical service? Hear about its extraordinary improvement results and how its selections are effective for financial enterprise systems.
Java EE 6 Adoption in One of the World's Largest Online Financial Systems (fo...Hirofumi Iwasaki
Financial companies need Java EE to power its business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. You can learn why we choose Java EE, and our experiences and lessons we learned. This is the first disclosing of a large credit card company in Japan sharing their story.
How to start such a big project? Why we choose it, how we selected the in house development policies, educated ourselves, and developed the additional libraries? How to launch within only six months? What is the key factor driving them as 24/7 critical real financial systems successfully? How to migrate to EE 7 in the future? We’ll answer these questions and any that you may have.
This version is the exclusive session for JJUG CCC Fall 2014 in Japan, binding both JavaOne and OOW 2014 sessions.
JavaScript Frameworks and Java EE – A Great MatchReza Rahman
The sea change in JavaScript frameworks is shifting the pendulum away from today's thin-client based server-side web frameworks like Spring MVC and JSF to JavaScript powered rich clients. With strong support for REST, WebSocket and JSON, Java EE is well positioned to adapt to this landscape.
In this heavily code driven session, we will show you how you can utilize today's most popular JavaScript frameworks like AngularJS and React to utilize the core strengths of Java EE using JAX-RS, WebSocket, JSON-P, JSON-B, CDI and Bean Validation.
WebSocket in Enterprise Applications 2015Pavel Bucek
Presentation from JavaOne 2015.
This session, which covers use cases of JSR 356 (Java API for WebSocket) and some features of Oracle’s implementation related to enterprise applications, contains description of standard use cases and recommends optimizations and best practices for using the JSR 356 API. After that, it presents more-complex schemes involving authentication support, fallback support, and clustering.
WebLogic 12.1.3 was released late last year. It brings a large set of changes including support for some key new Java EE 7 APIs such as WebSocket, JAX-RS 2, JSON-P and JPA 2.1, support for Java SE 8, WebSocket fallback support, support for Server-Sent Events (SSE), improved Maven support, enhanced REST administration support, Oracle Database 12c driver support and much, much more. In this session we will take a detailed tour of these features. In addition we will also cover updated WebLogic support in the Oracle Cloud, the new Oracle public Maven repository, using WebLogic with Arquillian for testing and well as official Docker support for WebLogic.
Towards the end of the session we will discuss what's coming in WebLogic 12.2.1 this year including full support for Java EE 7, multi-tenancy and more.
With a strong focus on annotations, minimalist configuration, simple deployment, intelligent defaults and Java centric type-safety, Java EE is one of the most productive full-stack development platforms around today. This very code centric workshop is a quick tour of the Java EE platform as it stands today. If you haven't seen Java EE for a while and want to catch up, this session is definitely for you.
We will start with the basic principals of what Java EE is and what it is not, overview the platform at a high level and then dive into each key API like JSF, CDI, EJB 3, JPA, JAX-RS, WebSocket and JMS using examples and demos. This is your chance to look at Java EE 7 in the context of a realistic application named Cargo Tracker, available with an MIT license at http://cargotracker.java.net.
We will also briefly take a look at the emerging horizons of Java EE 8.
The days of EJB’s being the center of the Java EE universe are coming to an end. CDI is increasingly becoming the de facto component framework, due to its flexibility and lack of legacy. Starting in Java EE 7 and continuing in 8, the Java EE platform is migrating to enable all of EJB’s best features to be usable in the CDI world. In this session, you’ll learn implementation-level details on how they relate to each other, where we are in the EJB/CDI alignment story, what trade-offs you might need to make, and what you have to gain from making the transition. You will walk out with runnable examples and vendor-level insights. This is the perfect session for heavy EJB users looking to keep up with Java EE’s transition to CDI.
JavaOne 2011: Migrating Spring Applications to Java EE 6Bert Ertman
The Spring Framework has no-doubt played a major role in evolving the way we write enterprise applications on the Java platform today. However, it is still a proprietary framework owned by a single company. The age of having to rely on such proprietary frameworks in order to develop decent enterprise applications is now over and Java EE 6 has become an even easier way to develop enterprise applications based on standards which makes it the best choice for any enterprise application. In this session you will experience how to migrate a typical full stack Spring application to a standards based, completely portable, Java EE 6 application including integration tests.
Consideration points for migrating from older pre-J2EE, J2EE 1.2-1.4, Java EE 5-6 to EE 7, and migration points especially for web front-end systems and back-ends. JSP to JSF, EJB to CDI with migration procedure details. Slide materials on Java Day Tokyo 2016.
JSR 236 Concurrency Utils for EE presentation for JavaOne 2013 (CON7948)Fred Rowe
Presentation about the newly released JSR236 spec that Anthony Lai (Oracle) and Fred Rowe (IBM) did for session CON7948 at JavaOne SF 2013.
JSR 236 is part of EE7 platform and defines extensions to the SE concurrency APIs to allow them to be used in an app server environment.
Java EE 6 Adoption in One of the World’s Largest Online Financial SystemsArshal Ameen
Financial companies need Java EE to power their business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. Learn why it chose Java EE, and hear about its experiences and lessons learned. This is the first time a large credit card company in Japan is sharing its story. How do you start such a big project? Why did it choose Java EE? How did it select the in-house development policies, educate itself, and develop the additional libraries? How did it launch within only six months? What is the key factor driving 24/7 critical financial systems successfully? How do you migrate to Java EE 7 in the future? This presentation answers these questions and any others you may have.
Java EE 6 Adoption in One of the World’s Largest Online Financial Systems [Ja...Hirofumi Iwasaki
Financial companies need Java EE to power their business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. Learn why it chose Java EE, and hear about its experiences and lessons learned. This is the first time a large credit card company in Japan is sharing its story. How do you start such a big project? Why did it choose Java EE? How did it select the in-house development policies, educate itself, and develop the additional libraries? How did it launch within only six months? What is the key factor driving 24/7 critical financial systems successfully? How do you migrate to Java EE 7 in the future? This presentation answers these questions and any others you may have.
Case Study of Financial Web System Development and Operations with Oracle Web...Arshal Ameen
To stay ahead of the technology curve, financial companies require the power, flexibility, and scalability of latest enterprise technologies for 24/7 services. Rakuten Card, one of the largest credit card companies in Japan, recently renewed its web front-end systems utilizing Java EE. This session provides answers to the following questions: Among the myriad of available technologies, why did it choose Oracle WebLogic and Oracle Exadata, managed by Oracle Enterprise Manager? How did it drive this huge project to completion in only six months, using only in-house development? What were the key success factors in launching and operating this mission-critical service? Hear about its extraordinary improvement results and how its selections are effective for financial enterprise systems.
Today the Java EE is a de-facto standard architecture for any kind of enterprise systems in the world, and realized as ease of development on its specification. But especially for the huge enterprise systems, not small or mediocre, there are still many issue for designing, developing, and operating. You can learn the overview and some details of the huge enterprise system design, with referring latest Java EE specifications on this session.
https://tech.rakuten.co.jp/
MicroProfile and Jakarta EE - What's Next?Ian Robinson
Session from Oracle Code One 2018.
MicroProfile is well established as a microservices development platform for Java and has blazed the trail for Jakarta EE. In it's first two years MicroProfile has has introduced us to specifications and open implementations of Fault Tolerance, JWT Propagation, Metrics, Rest Client, Config, Health Check, OpenAPI, and OpenTracing. In 2019 it introduces Reactive Messaging and Reactive Streams integrations for Java microservices. Meanwhile Jakarta EE has rebooted enterprise Java by rehoming it next door to MicroProfile at the Eclipse Foundation. What's next for these two key Eclipse projects? Will MicroProfile stay independent and continue to demonstrate it's fast-paced innovation? Or, will it be combined with Jakarta EE, which is also promising a faster development cycle than the previous Java EE platform?
Specializing in Spring, Hibernate, IVR, Webfocus, Microsoft DataStage, Oracle DB, web analytics, Quartz scheduler, etc in multiple platform (OS) and also have experience in migrating .net application to J2EE application.
In my presentation, I will summarize the applied and practical aspects of creating sustainable software products. What does it mean - "green" software for users and developers? I want to explain how creating “green” software can be driven by multiple organizational layers. And how building “green” software products can help the organization increase overall software product efficiency.
This presentation introduces the OWASP Top 10:2021.
It explains how to look at the data related to OWASP Top 10:2021, and provides detailed explanations of items with distinctive data. It also introduces the OWASP Project related to each item.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
[RakutenTechConf2013] [E-3] Financial Web System with Java EE 6
1. Financial Web System
with Java EE 6
Hirofumi Iwasaki
Financial Service Department, Development Unit,
Rakuten, Inc.
http://www.rakuten.co.jp/
2. Speaker Biography
Hirofumi Iwasaki
– Vice Group Manager, Technology Manager
– Financial Service Department, Development Unit,
Rakuten, Inc.
Carrier
– Planning, designing & implements for many huge enterprise
systems for financial, manufacturer, public systems with enterprise
middleware, especially Java EE & .NET in Japan for about 15
years.
Opus, Lectures, etc.
– Magazine: @IT (2005-2010), CIO Magazine (2009), IT Architect
(2005-2009), Web+DB Press (2005), Java World (2001-2004), etc.
– Lectures: WebLogic key person roundtable (2012-2013), etc.
– twitter: @rockcape
2
3. Agenda
1. Java EE 6 Specifications
2. Financial Requirements &
Java EE Specifications
3. How to Apply Java EE 6
to Real Financial Systems
3
4. Agenda
1. Java EE 6 Specifications
2. Financial Requirements &
Java EE Specifications
3. How to Apply Java EE 6
to Real Financial Systems
4
5. What's Java EE (1/2)
Standard specifications for application servers (except for MS).
Java EE
Specification
Commercial
etc.
Open Source
5
6. What's Java EE (2/2)
For ENTERPRISE systems (Enterprise Edition) specifications (full
profile)
– 'Enterprise' means transactional.
– Core architecture is EJB (JTA & CMT) with auto transaction
systems.
– Transactional connectivity for other systems with JPA (JDBC),
JMS, RMI-IIOP.
– Web architecture with JSF (Servlet & Facelet), JAX.
Each Java EE specification covers general enterprise requirements.
6
7. The History of Java EE
J2EE
1.2
(1999)
Born!
J2EE
1.3
(2001)
Pandemic
Era
J2EE
1.4
(2003)
Java EE
5
(2006)
Mess Era
(for EE spec)
Java EE
6
(2009)
Java EE
7
(2013)
Integration
Era
Unite to Single
Standard
Again!
7
8. Grouping of the Java EE Servers
App
Engine
WebLogic World
GlassFish &
Compatible Group
Geronimo &
Compatible Group
Copy
Japan Galapagos
Group
JBoss World
8
9. Java EE Application Servers Versions
Vendor
App Server
EE 1.4
(2003-)
EE 5
(2006-)
EE 6
(2009-)
EE 7
(2013-)
Open Source
GlassFish
-
2.x
3.x
4.0
Oracle
WebLogic
9.x
10.x
12.x
-
IBM
WebSphere
5.1
6.x, 7.x
8.x
-
Red Hat
JBoss
4.x
5.1
7.1
-
Fujitsu
Interstage
9.0,9.1
9.2,10.x,11.0 11.1
-
Open Source
Geronimo
-
2.x
3.x
-
Hitachi
Cosminexus
7.x
8.x
9.x
-
The de facto
latest version
is EE6
9
10. Agenda
1. Java EE 6 Specifications
2. Financial Requirements &
Java EE Specifications
3. How to Apply Java EE 6
to Real Financial Systems
10
12. Financial Services of Rakuten Group
Big 6 Services
Each has huge transactions
24/7 non-stop services
12
13. Requirements for Rakuten Financial Systems
Financial
Systems
1. Rapid business logic changeable
as business model changes
2. Huge request capacity as
business grows
3. Must be transactional
13
14. For our 3 Big Targets
Like periodic
re-construction
known as
"Shikinen-Sengu"
in Japan.
E.g.
Re-construct to next
place once every
20 years in Ise-Shrine
Re-construct
New!
Photo by author (2009 in Ise-Shrine)
14
15. 3 Big Targets for New Architecture
①
sustain
ability
③
System
Transpa
rency
for
new
Arch.
②
Flexibil
ity
15
16. Typical Usage of EE 6 Specs
Business Logic
(no presentations)
Web Presentation
(no business logics)
Data Access
Call
JPA
DBs
Call
JSF
EJB
Rich Clients
(no business logics)
Messaging
MQ
Connection
RMI-IIOP
Call
Java FX
Call
JMS
JAX
Automatic
Transaction
JavaMail
Other
Servers
Call
MTA
EMail
JTA
Call
16
17. Applying Service Oriented Architecture
Business Logic
(no presentations)
Web Presentation
(no business logics)
Data Access
Call
JPA
DBs
Call
JSF
EJB
Messaging
Design asJMS
Services
Connection
(aka 'API')
Rich Clients
(no business logics)
RMI-IIOP
Call
Java FX
JAX
Automatic
Transaction
JavaMail
MQ
Call
Other
Servers
Call
MTA
EMail
JTA
Call
17
18. Simplified Model
Rich Clients
(no business logics)
Web Presentation
(no business logics)
Service
Interfaces
A Shared
Function
Design as
Services
(aka 'API')
Full Service ('API-nization')
Re-use one business logic
for another front-end
18
20. Enterprise 'Transactional' Model (Error Case)
Client
(caller,
views or so)
BEGIN
SELECT
DELETE
ROLLBACK
Transaction Boundary
Transactional
Services
UPDATE
ERROR
No Data Broken Model
20
22. Distributed Transaction Model (Error Case)
BEGIN
ERROR
Transactional
Services
ROLLBACK
Database 1
Database 2
Local
Transaction
MQ
Global
Transaction
Other
Transactional
Services
No Data Broken Model
22
23. Each Technology & Java EE Specs
Core Spec
is EJB
JPA
BEGIN
Transactional
Services
JPA
Database 1
Database 2
EJB
Local
Transaction
JMS
MQ
Automatic
EJB Transaction
RMI-IIOP
Global
Transaction
= Container
Managed
JTA Transaction (CMT)
Other
Transactional
Services
23
24. Agenda
1. Java EE 6 Specifications
2. Financial Requirements &
Java EE Specifications
3. How to Apply Java EE 6
to Real Financial Systems
24
26. 1. Policies: Case of Rakuten
Internal Development First,
not order to external SI vendors. (Group All)
Financial businesses are also the target for the
application of this policy.
ORDER NO
Educate
&
Develop
26
27. 2. Education: Read, Read, Read!
Start from HERE
4th Edition
Good & Only
Japanese
EE 6 book
Good Pocket
Reference!
For NetBeans 7
with EE 6
RECOMMENDED
for WebLogic 12c
27
28. 2. Education: Online Materials
Original Tutorial
for Newbies (Start here!)
NetBeans Java EE docs
for Advanced Information
28
29. 3. Architecture: Apply EE 6 Specs
Business Logic
(no presentations)
Web Presentation
(no business logics)
Data Access
Call
JPA
DBs
Call
JSF
EJB
Rich Clients
(no business logics)
Messaging
Call
JMS
MQ
Connection
RMI-IIOP
Call
Java FX
There's no
rich clients
JAX
Automatic
Transaction
JavaMail
Other
Servers
Call
MTA
EMail
JTA
Call
29
30. 3. Architecture: Migrate from Old
Old Arch (e.g. PHP case)
Spring
PHP
DAO
Transaction
Boundary
JSF 2
Logic
View
New Arch
EJB 3 + JPA
External
DB
External
View
Services
(aka APIs)
DB
Fully Re-written
100% API-nized
30
31. 3. Architecture: Simplified
Web Site A
Web Site B
Internal Site
Batch Exec
Core
Services (aka APIs)
L7 Balancer
Reverse Proxy
Front Real-time
System B
Gateway
Database
System C
Sub Proc
Front Batch
31
32. 4. Environment: Ease of Dev.
Full Local Programming,
Build & Execute support
=
X
X
32
33. 4. Environment: Easy Startup
2. Download
Code from
Repository
4. Refer the JIRA
as for his today's
task improvement
1. Join a
project.
3. Install JDK with IDE,
App servers, build,
and run on you local PC
33
34. 5. Test: Full Auto Testing &Valid.
1. Auto PULL
4. Report
Hourly
ZERO Violations!
3. Auto
Validate
2. Auto
Build
& Test
Management Server
34
35. Agenda
1. Java EE 6 Specifications
2. Financial Requirements &
Java EE Specifications
3. How to Apply Java EE 6
to Real Financial Systems
Appendix: Java EE 6 Unveiled
35
36. Is Java EE 6 Useful for Real Projects?
Web Front End
Wait the
Java EE 7
Back End
Not Bad
36
39. 1st Issue: JSF Backing bean defectively in EE 6
Not worked these JSF 1.x codes in JSF 2.x properly.
protected FacesContext getFacesContext(HttpServletRequest request,
HttpServletResponse response) {
FacesContext facesContext = FacesContext.getCurrentInstance();
if (facesContext == null) {
FacesContextFactory contextFactory
= (FacesContextFactory)FactoryFinder.getFactory(FactoryFinder.FACES_CONTEXT_FACTORY);
LifecycleFactory lifecycleFactory
= (LifecycleFactory)FactoryFinder.getFactory(FactoryFinder.LIFECYCLE_FACTORY);
Lifecycle lifecycle = lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
facesContext = contextFactory.getFacesContext(request.getSession().getServletContext(),
request, response, lifecycle);
// Set using our inner class
InnerFacesContext.setFacesContextAsCurrentInstance(facesContext);
// set a new viewRoot, otherwise context.getViewRoot returns null
UIViewRoot view = facesContext.getApplication().getViewHandler()
.createView(facesContext, "");
facesContext.setViewRoot(view);
}
return facesContext;
}
39
40. 1st Issue: JSF Backing bean defectively in EE 6
Java EE 6 (JSF 2.1)
NG!
CDI
don't have
@View
Scoped
Facelet
Filter
Faces
Servlet
Phase
Listeners
NG!
CDI
don't have
@View
Scoped
Facelet
NG!
Facelet
Managed
Bean
@Session
Scoped
OK!
CDI
don't have
@View
Scoped
Integrated
CDI World
40
41. 1st Issue: JSF Backing bean defectively in EE 6
Java EE 7 (JSF 2.2)
OK!
Facelet
Filter
Facelet
New CDI
@View
Scoped
Facelet
Faces
Servlet
New CDI
@View
Scoped
New CDI
@View
Scoped
Phase
Listeners
CDI
@Session
Scoped
OK!
Wait the Java EE 7
if you can
Integrated
CDI World
41
42. 2nd Issue: Non-interchangeable Facelet tags in EE 6
Java EE 6 (JSF 2.1)
<input type="text"
jsfc="h:inputText"
name="id"
value="#{bean.property}" />
Java EE 7 (JSF 2.2)
Changed!
<input type="text"
jsf:id="id"
jsf:value="#{bean.property}" />
Wait the Java EE 7
if you can
42
43. How's Back End in EE 6?
Business Logic
(no presentations)
Data Access
Call
JPA
DBs
Call
EJB
Messaging
Call
JMS
MQ
Connection
RMI-IIOP
Call
JAX
Automatic
Transaction
JavaMail
Other
Servers
Call
MTA
EMail
JTA
Call
43
44. Agenda
1. Java EE 6 Specifications
2. Financial Requirements &
Java EE Specifications
3. How to Apply Java EE 6
to Real Financial Systems
Appendix: Java EE 6 Unveiled
Conclusion
44
45. Conclusion
Java EE 6 is suitable for huge
financial systems.
We made new financial architecture
with many measurements
Wait for the EE 7 servers if you can
Go Ahead,
Ride the Wave!
Make our enterprise
future with Java EE!
45
Hello, let's get started my presentation. "Financial web system with Java EE 6".
My biography. I'm a financial system vice group manager of Rakuten.And a professional of enterprise financial system management, planning and development.
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.
Next.
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.
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.
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.
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.
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.
Next, financial requirements and Java EE specs.
Here at Rakuten, we have 6 big services of financial.Rakuten Card, Rakuten Bank, Rakuten Edy, Rakuten Security, Rakuten Life, Rakuten Insurance.
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.
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.
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.
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.
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.
And the EJB interfacescan be considered as the 'services', or 'web API'.It doesn't have any user interface, only has pure data interfaces.
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.
Next shows enterprise transactional model.This is a very basic model for the transaction processes, begin (or start) & commit.
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.
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.
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.
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.
Next, the last part, how to apply Java EE 6 to real financial systems.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Ok, we have some additional time to talk to the real Java EE 6 world. Unveiled.
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".
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.
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.
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.
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.
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.
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.
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!
Last, here's my conclusion.
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.
That's all. Thanks for listening, have a good day.