What is your primary use case for IBM WebSphere Application Server?

I currently support projects within my company that use IBM WebSphere Application Server, IBM MQ (message queue), and Jenkins pipelines. We used WebSphere for enterprise application deployment. We used the WebSphere Admin Console for deployment. We would deploy EARs and WARs through the console. If there are issues accessing the admin console, I would occasionally use command-line tools for troubleshooting.

We use it for a web application related to insurance.

We are mainly using it for managing the core banking applications.

We deploy the solution both on-premise and Azure, AWS, and IBM cloud. We use a solution for our e-commerce application. We have an application deployed on AWS Cloud, for a client, which has a large B2B customer base in Australia. Therefore, we use WebSphere Application Server for the e-commerce website.

IBM WebSphere Application Server ensures that there's communication between applications from the customer side to the banks, markets, insurance companies, and even the retail industry.

We sell IBM WebSphere licenses and provide core installation of WebSphere for our customers.

We primarily use a generic WAS. We have WAS, which we basically use for JVM containers for services and REST APIs. We have some portal servers, and it is also used to host Pega. So it serves three primary functions. It's an application server in general.

I am always working. I am working with WebLogic and WebSphere. Some things are running on WebLogic and others on WebSphere. I use both. It is deployed on-premise, and I am able to do everything they are doing on the cloud.

We use IBM WebSphere Application Server in the financial industry for applications.

There are two use case categories. We use it for integration with other parties or external parties across the world, and we also use it for internal applications. It has an enterprise service bus, and all applications talk to each other through IIB. We also using WebSphere for the exchange of messages between core banking applications and other applications and servers.

This solution is part of an enterprise web presence. It integrates well with the Tivoli Federated Identity Management system, which works as a single sign-on mechanism for other e-services that we have shared with other clients. They utilize some of our authentication engines and they provided access for their users back into their system, however, the presentation and the web presence for it comes on the WebSphere portal solution.

We have used it for the implementation of a web interface on very old mainframe system.

This solution is normally used on the front-end of applications that we have in DB2. Our customers are in a variety of industries including insurance, financial, and retail. They use the WebSphere Application Server as part of their portal that talks with our database. We have installed this application under several different operating systems including Red Hat Linux and IBM AIX.

We use it as a gateway for our payment application. It receives requests and processes it.

We have some services which are doubled up using Java. To deploy this research we are using the WebSphere Application Server. A lot of channel applications are consuming these services in particular.

I am a specialist in content management solutions, especially IBM and other open-source products. I am the director of my team, and we specialize in this solution. We use this in many areas including banking, insurance, and public administration.

We use on-premise model, primarily for hosting a case management system.