Red Hat JBoss Enterprise Application Platform (EAP) is primarily used for enterprise-level Java applications. Enterprise applications, Java applications such as banking and financial applications, insurance portals, government, e-governance applications, internal employee portals, customer self-service portals, ERP and HR management applications, and REST-based web services are deployed on Red Hat JBoss Enterprise Application Platform (EAP). These applications are typically built using Java EE or Jakarta EE technologies and packaged as a WAR or EAR file, which are deployed on Red Hat JBoss EAP. Due to a confidentiality agreement, the exact application names cannot be shared. However, they are enterprise business applications that support critical business operations, and the role involves ensuring that they are deployed, monitored, patched, and running reliably on Red Hat JBoss EAP.

Red Hat JBoss Enterprise Application Platform (EAP) is primarily deployed in a hybrid environment within the organization. Deployments are running on on-premises infrastructure as well as cloud platforms, depending on the application and customer requirement. Some workloads are hosted on cloud environments such as AWS and OCI, while others require on-premises deployment. This hybrid approach provides flexibility, supports business continuity, and allows the organization to meet different security and compliance requirements.

My main use case for Red Hat JBoss Enterprise Application Platform (EAP) is as an application server, and sometimes I have used it as a web server on a few servers as well. It provides great middleware technology to use as an application server and compensates for all my application requirements.

A specific example of where I used Red Hat JBoss Enterprise Application Platform (EAP) as an application server is for my in-house applications that mainly utilize JBoss or WildFly, which is the new name for JBoss. I am using it for managing my applications and, as mentioned, also using it as a web server, so it helps in communicating and integrating with the database. I have used many applications currently with the help of just the JBoss application, and it is very easy to use. Until last year, I was using JBoss 7 version, and then I migrated to JBoss EAP 8 version, as the 7 version was at end of life.

The main use case for Red Hat JBoss Enterprise Application Platform (EAP) is to deploy web applications, WAR files and JAR files of our developed app, and also to use Red Hat JBoss orchestrator for containerization and everything.

We primarily use Red Hat JBoss Enterprise Application Platform (EAP) for various environments such as dev, SIT, and prod, and we have been using it exclusively for SAP-based front-end while the back-end is Spring Boot, and we were using JBoss particularly for deploying these servers, with a very easy way to deploy the JAR files mainly.

Red Hat JBoss Enterprise Application Platform (EAP) is used to deploy web applications and web services, which is the primary purpose.

Red Hat JBoss Enterprise Application Platform (EAP) connectors are particularly valuable for connecting to mainframe systems. Previously, a Bull mainframe was used, and connectors were available for that system. The platform is also used for databases and management of connection pools for these types of connectors, as well as for security and securing access. The ability to manage multiple instances on the same server with different ports is a significant capability.

Optimization has been used only once to optimize the Java runtime. Pool and connector adjustments are sometimes made to achieve optimum performance.

Microservices have been used for specific tasks, such as a microservice dedicated to signature functionality for PDF documents. The plan for the future is to migrate all applications and implement microservices during the next refactoring.

The typical use case is to deploy Red Hat JBoss Enterprise Application Platform (EAP) on premises, which is your on-premises native platform. You can manage everything, and you have a lot of freedom to do deployments and create new inventions such as integrating Red Hat JBoss Enterprise Application Platform (EAP) with GitHub, then integrating with Jenkins to collect day-by-day logs or previous day's logs with the help of a pipeline, and we can do small deployments with the help of GitLab plus Jenkins.

My main use case for JBoss is the administration of the application mostly.

My use case implies installation, configuration, and setting JBoss EAP on different systems such as Linux, Windows and configuring the standalone or domain. This implies working with the web console, automation tools, and CLI. Additionally, it involves securing it, implementing authentication, RBAC or Role-Based Access Control, SSL, TLS, and so on. Performance tuning, thread pool management, logging, and clustering are mostly what I have done with the product.

I assessed the modular architecture in terms of enhancing resource utilization as very scalable. I used this solution because we had almost around 450 APIs running in that organization. I wanted to compile all those APIs into one place, and therefore I used this particular tool. This was a very good Java application server which is commonly used to deploy and run Java-based applications. Our application was also Java-based, therefore it was a very good operating system for us.

The cloud-native design definitely helps with DevOps integration. Migrating to cloud-native architecture helps with DevOps integration because when migrating large applications and large monolithic applications, sometimes Red Hat JBoss Enterprise Application Platform (EAP) gets a little expensive and also risky as well, because sometimes you tend to lose some of your data from it. But apart from that, it was pretty good.

The implementation of highly transactional applications on Red Hat JBoss Enterprise Application Platform (EAP) definitely improved our customers' reliability. When we embedded our APIs into the system, we removed the methods in our code and replaced them with the caches. Once we did that, our application experienced a surge of around almost 64% or 65%, an increase in the transaction speed and also in the customer onboarding journey. I would definitely rate that a solid 10.

My main use case for Red Hat JBoss Enterprise Application Platform (EAP) is the deployment of our specific applications.

A specific example of an application I have deployed using Red Hat JBoss Enterprise Application Platform (EAP) is some application pages about educational support from the government that stands out.

Red Hat JBoss Enterprise Application Platform (EAP) fits into that process by helping with scalability, which is the most important factor because the product gives me scalability opportunities, such as G-group or load balance or other options.

We are currently using Ansible for Jira installations and all the management tasks. We perform some tasks manually, however, Ansible helps in automating some of these processes.

My main use case for Red Hat JBoss Enterprise Application Platform (EAP) is for a web application for any customers we have on my main apps.

A specific example of how I use Red Hat JBoss Enterprise Application Platform (EAP) with my web application for my customers is that I customize a payment link. We call it on other platforms, and we can process the monthly payment.

Our product is agnostic, so we have been using JBoss as our default app server. We have been using it for over ten years.

I use it for Java server applications.

Our primary use case is for web applications.

In my previous company, we relied on third-party APIs from a vendor. Recently, we were tasked with bringing those APIs in-house, reducing dependence on external vendors. We employed a JBoss server to facilitate the transition of these APIs into our existing system.

Our company uses the solution for enterprise clients in the banking and finance industries. 

We use different versions of the open source solution depending on client needs. 

I use the solution in my company since we have developed an application that runs on the application server, JBoss, and another application server, such as Oracle WebLogic Server or WebSphere. In my company, we developed an application for the bank, and we deployed it under JBoss, WebSphere, or Oracle WebLogic Server.

JBoss is a middleware product. The customers use it to make connections between front-end applications and databases.

I use JBoss for our websites and multiple products.

JBoss is an on-premises solution we use in a banking setting.  It is used to manage servers and applications. There are two modes: domain and development. We can monitor and control all types of deployments in JBoss.

We have around 20,000 to 30,000 users on the same application and everything is going via the JBoss. We were using JBoss 1.0 when I first installed it, but they've probably included some more security patches in the latest version. 

We use the solution for the installation of the hardware and microservices.

For our application to deploy, we used to set up different platforms. We are certifying JBoss support as well for the deployment.

We use JBoss exclusively for API integration and do not use it for other purposes. Our focus is solely on providing services and configuring ACLs.

We primarily use the solution for business processes and mostly from the level of approval, within the organization.

JBoss is a product that we implement for our clients. It is used as an application server and a web server. 

The product is basically middleware. What we have is several applications running on JBoss. Basically, it is very old and there we have those services exposed. Our target is to move them to ERPC, or something more modern, like REST or ESPC, or a combination of both.

What we currently have here, still, is SOAP services, which is a very old middleware. They also are using it for scheduling some items such as some recurrent procedures. They have a queue manager as well.

The use cases include online webshops and any organization doing online business can use JBoss.

I use the platform mainly for presentations and meetings. It is also used to implement web applications.

JBoss is used for our main applications, it is our core system. All the core systems that we use are on JBoss and we use mod_proxy combined with WildFly to do the load balancing. Additionally, we use automation using Red Hat Ansible Tower, and for a web server, we use Red Hat for the entrance.

I am working on a deal where JBoss is being renewed. It is a legacy version. The use case is around a financial institution that enables banks to do peer-to-peer transactions. Finance is the core business of the companies I'm working with.

We provide the very basic JBoss setup for the implementation and the setup.