I was part of an application where I integrated IBM WebSphere Application Server with Node.js and Blue Prism. I did a lot of REST applications because at my core, I'm a developer. Currently, I'm an architect as a title, but I remain a geek and developer since that's how I started.

At Royal Bank, the overwhelming environments are clustered with IBM HTTP Server in front. The clusters have not just two IBM WebSphere Application Server engines; some have four or six engines with IBM HTTP Server in front.

Oracle announced that 2030 will be the last year when they would deliver Java SDK 1.8. The entire IBM WebSphere Application Server is based on Java 1.8. The future direction remains unclear as I haven't found any official papers from IBM stating their plans.

I use it in tandem with IBM WebSphere Application Server, where the data is taken based on events. People are moving more to Kafka, which is open source and performs similar functions as IBM MQ. When having a cluster, it's beneficial because clustering means having high availability.

We are working on a project where the client hosts their own environments. The application we are developing is primarily an app server diagnostic tool. Our clients can choose whatever server they want to use. Some of our clients have used WebSphere quite extensively in the past.

I use the solution as a dependent tool for IBM's Information Server. It supports IBM Infosphere Application Server as a web server. I handle the Application Server, which has multiple servers configured for this application due to its additional features, such as the ability to configure multiple servers. Mainly, my work is related to administration support. I manage the WebSphere admin console, focusing on security issues and memory problems. For instance, if there are any Java heap memory issues from the application side, I am responsible for tweaking or tuning the heap size to address those concerns.

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.

My membership management involves CRM for membership management facilitated by WebSphere. The platform I use is WebSphere, however, most customers develop their own CRM and membership management systems.

We use the solution for core banking. Oracle will be the back end. 

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.

I use the solution in my company for enterprise applications. We also implemented a virtual portal server based on the virtual application server, but it is a portal server version meant for customers, agents, and customer service.

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.

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

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.

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.

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 use IBM WebSphere Application Server in the financial industry for applications.

This solution is normally used on the front-end of applications that we have in DB2 for IBM i. 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 the database.

We have installed this application under several different operating systems including Red Hat Linux, IBM i  and IBM AIX.

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

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.

We use it for a web application related to insurance.