Overview
For regions outside of the EMEA region, Red Hat® JBoss® Enterprise Application Platform (JBoss EAP) delivers enterprise-grade security, performance, and scalability in any environment. Whether on-premise, virtual, private, public, or hybrid clouds, JBoss EAP can help you deliver apps faster, everywhere.
JBoss EAP provides simplified deployment and full Jakarta EE performance for applications in any environment. JBoss EAP features a modular architecture that starts services only as they are required. JBoss EAP is built for performance and flexibility in modern application environments. Its modular architecture and services-driven components reduce scale-out times and provide flexibility for applications. JBoss EAP maximizes administrative productivity by making it easy to maintain and update your deployments. JBoss EAP features an updated management console user interface with navigation and support for large-scale domain configurations.
Highlights
- Fully Supported Jakarta EE Platform
- Optimized for development on cloud and containers
- Flexible management, configuration, and administration
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
- ...
Dimension | Cost/hour |
|---|---|
m5.xlarge Recommended | $0.244 |
r6i.32xlarge | $7.808 |
u-18tb1.112xlarge | $27.328 |
m5.24xlarge | $5.856 |
r5a.large | $0.122 |
r5a.8xlarge | $1.952 |
m6id.2xlarge | $0.488 |
m5n.xlarge | $0.244 |
c5d.metal | $5.856 |
m3.xlarge | $0.244 |
Vendor refund policy
All fees are non-refundable.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Additional details
Usage instructions
- Launch the product via the AWS Marketplace listing.
- When prompted, use your existing VPC, Subnet, and Key pair, or create new ones via the AWS Console.
- To access your instance from your desktop, your VPC will need external connectivity. Follow the "VPC And More" workflow when creating the VPC.
- Once launched, access your instance using ssh:
- Open an SSH client or use the built-in Connect option on the AWS console.
- Locate your private key file that was used to launch this instance.
- Use the default username ec2-user and the ssh key registered with AWS to connect with your SSH client.
- Once logged in, start JBoss EAP by following the Launch a Non-Clustered JBoss EAP Instance documentation .
- To confirm JBoss EAP has started, navigate to http://[AWS Public IP]:8080 in your browser, or view the server log and ensure there are no errors by running the following command: cat /opt/rh/eap8/root/usr/share/wildfly/standalone/log/server.log
- For advanced deployment options (e.g. clustering, auto-scaling, management console access), refer to the JBoss EAP on AWS documentation .
Resources
Support
Vendor support
This offering is covered by the Premium tier of Red Hat Support and includes direct access to Red Hat support engineers during business hours and 24x7 access to support engineers for high severity issues. To enable Red Hat Support for this subscription and for all of your Red Hat on AWS Marketplace purchases, follow the instructions at https://aws.amazon.com/marketplace/pp/prodview-fyphbrmils4dg . Get answers quickly by opening a support case with us at
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Lightweight clustering has improved banking channels and delivers faster, reliable deployments
What is our primary use case?
Our main use cases with JBoss Enterprise Application Platform were that we are an application software developer, developing the channel platform, the internet banking, and the mobile banking for the banks.
The channel platform was hosted on JBoss Enterprise Application Platform .
What is most valuable?
JBoss Enterprise Application Platform's best features include that it was very simple to install and enabling clustering between two instances was simpler than compared to WebSphere or WebLogic. Clustering became very much easier, and setup was very straightforward.
I used other products such as WebSphere and WebLogic, and I saw JBoss Enterprise Application Platform as a very lightweight container rather than a heavy container. The startup time was much faster compared to other application servers, and debugging was reliable. We did not see the application going into a hang state. It never happened in JBoss Enterprise Application Platform. Other application servers typically degrade over time, and the application resources can become hung.
The memory utilization and the heap garbage collection that was running was very efficient, so the resource utilization was better. The robust security model of JBoss Enterprise Application Platform contributed positively to our data integrity and compliance in our development processes, and it was very good.
What needs improvement?
In my opinion, there are areas that could be improved with JBoss Enterprise Application Platform, such as the management console.
I am not certain whether it has all of the enterprise features incorporated such as what IBM WebSphere has, including real-time performance monitoring of your application, monitoring your JVM heap graphs, or even the CPU utilization graphs. I am not certain whether this is present or not.
We thought that if application performance monitoring tools were already part of the management console at runtime, it would be very helpful.
For how long have I used the solution?
The last time I used JBoss Enterprise Application Platform was version 7.7.4 recently.
Which solution did I use previously and why did I switch?
I used other products such as WebSphere and WebLogic, and I saw JBoss Enterprise Application Platform as a very lightweight container rather than a heavy container.
How was the initial setup?
The startup time was much faster compared to other application servers, and debugging was reliable. We did not see the application going into a hang state.
What's my experience with pricing, setup cost, and licensing?
My thoughts on JBoss Enterprise Application Platform's pricing is that from a subscription model perspective, the price was very reasonable compared to other application servers and other commercial products. JBoss Enterprise Application Platform was much better in terms of cost.
What other advice do I have?
I have experience with JBoss Enterprise Application Platform, as we earlier used it, but we moved completely to Tomcat .
I did not use JBoss Enterprise Application Platform with AWS as our main cloud provider, as it is a standalone solution.
We generally put it on premises at the financial institutions.
I am not certain if Red Hat uses AWS as their cloud provider for this product.
We did utilize the JBoss Enterprise Application Platform management console. We were running both in standalone mode as well as the domain mode.
We are more of a modular monolith, so we did not write microservices.
I did not try anything on the cloud, so I am probably not aware of its adaptability between cloud and on-premises deployments.
I do not know much about JBoss Enterprise Application Platform's support or the documentation, as we did not get into that too much.
Our company originally purchased JBoss Enterprise Application Platform through Red Hat partnerships.
The reasons I rate it so highly are that it was simple, lightweight, and the performance was very good. I rate this product a 9 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
High availability has supported omnichannel ticketing and banking middleware reliably
What is our primary use case?
I have an application with JBoss Enterprise Application Platform and a middleware. I used JBoss Enterprise Application Platform for about eight years until 2016. I implemented a ticketing solution and middleware application to connect several databases and several languages, creating an omnichannel experience. I have two kinds of implementations in the commercial area, including ticketing and e-commerce with the same middleware, and I used it for bank financials. One bank in Guayaquil used my middleware.
What is most valuable?
The best feature for JBoss Enterprise Application Platform for me is high availability, and it is very strong. It is strong because it supports many concurrencies.
What needs improvement?
I lost one opportunity for licensing to a bank that was implementing on-premises. It was too expensive to license JBoss Enterprise Application Platform for each process. The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000. Because they are a bank, they need local support, not international support. For that reason, it was too expensive for them, and we were discarded and could not implement the solution.
For how long have I used the solution?
I used JBoss Enterprise Application Platform for about eight years until 2016.
What do I think about the stability of the solution?
I do not have any problems with this deployment.
How are customer service and support?
Because the bank needed local support rather than international support, it was too expensive for them, and we were discarded.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I offered implementing the same services in Microsoft IIS , but they needed several months to develop the new solution, and they did not have time for that developer.
How was the initial setup?
JBoss Enterprise Application Platform is easy to implement.
What's my experience with pricing, setup cost, and licensing?
The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000.
Which other solutions did I evaluate?
I offered implementing the same services in Microsoft IIS , but they needed several months to develop the new solution, and they did not have time for that developer.
What other advice do I have?
I use JBoss Enterprise Application Platform management both through the management interface and through command line. I use JBoss Enterprise Application Platform for deployment in Microsoft servers, and in Linux and Oracle Linux . I am trying it in my own cloud and have deployed JBoss Enterprise Application Platform on Oracle Cloud to implement it in the cloud, which is very good. My overall rating for this solution is ten out of ten.
Enjoys improved setup and values database connection while noticing memory optimization needs
What is our primary use case?
I deploy the application as .war or .ear, which is part of Java Enterprise.
I use it for resources for the server, and I coordinate with the developer for deployment of the web application.
In my job, I am an administrator because I lead the team for development in Java.
What is most valuable?
I use the JBoss Enterprise Application Platform 7 EAP , and I appreciate the pool connection for the database the most.
What needs improvement?
The memory usage and memory RAM could be improved. JBoss Enterprise Application Platform could improve the use of memory on a server.
Sometimes, I observe the memory usage at 100% for the server, and this issue could be improved.
For how long have I used the solution?
I have used JBoss Enterprise Application Platform for about five years, and I know how to start the system.
What do I think about the scalability of the solution?
Regarding scalability capabilities, I am uncertain.
Which solution did I use previously and why did I switch?
I am unaware of their pricing. I normally use Tomcat , then I use JBoss Enterprise Application Platform 7, but I do not use WildFly.
How was the initial setup?
The deployment and initial setup is easy. It is easier than the previous version.
What other advice do I have?
A qualification for the version would be number seven.
Offers robust integration options for seamless application deployment
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
How would you rate customer service and support?
Neutral