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.

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 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.

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 have used Red Hat JBoss Enterprise Application Platform (EAP) in many projects. As a Java developer, I have worked with ATG and we have used the application server Red Hat JBoss Enterprise Application Platform (EAP) extensively for building applications and deployments.

We use Red Hat JBoss Enterprise Application Platform (EAP) in our application development. We have utilized Red Hat JBoss Enterprise Application Platform (EAP) as an application server for deployment purposes. For local running and operating particular applications locally, we have extensively used Red Hat JBoss Enterprise Application Platform (EAP). I have primarily worked as an application developer.

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.

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.

I use it for Java server 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 primary use case is for web applications.

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.

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 JBoss for our websites and multiple products.

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 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.

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. 

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

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.

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.