WebSphere Hybrid Edition from IBM is a collection of WebSphere application runtimes and modernization tools that provides support for on-premise and major public cloud deployments, in virtual machines, containers and Kubernetes. The user can choose any WebSphere edition and deploy Liberty and application modernization tools to help move to a cloud-native architecture, modernize existing applications and support an existing WebSphere estate.
$88.50
per month
Nintex
Score 8.1 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
Plesk provides assistance via its community forums, knowledge base, and premium support plans. Additionally, I had trouble integrating a new website onto the hosting, which was a bit of a frantic operation because it uses more server resources than other control panels. The …
IBM Websphere was better suited for our needs as we are a primarily Java shop, and it provided better customization and potential ROI. It also requires less downtime, and support is easier than Weblogic. Also, Websphere is better suited for a hybrid environment.
Cleo Integration Clould has many bells and whistles; however, when we added more maps and trading partners, it really slowed down. We found that the Cleo support was very slow to respond and there was a language barrier. IBM Websphere had better customer support and its …
IBM and weblogic are equally robust and support JVM's very well but where IBM is better is its out of the box integration with active directory that makes it easier to manage access control and security posture. In addition, the licensing model for IBM is lot more flexible for …
I like the well built hybrid edition that is very favourable for our cloud apps and real-time monitoring of our applications deployment and development. I like it support real-time visibility a complete and clear view of our applications development and application awareness. I …
Both Apache Tomcat and Hybris have been in use, and we have provided support for both tomcat and IIS-based systems. Companies with a substantial investment in IBM technology will find this application particularly useful. Support and licensing fees might be prohibitive, …
WebSphere Application Server admin console is very detailed and there are a huge number of configurations available to maintain and configure. JBoss is complex where stand vs full configuration is confusing sometimes. Modularity proved complex there, so I love WebSphere …
Websphere Application Server provides better Security, high availability, easy troubleshooting, and good 24/7 support. Websphere Application Server has an easy to use interface.
WAS is an IBM product and gels with IBM database product. So, we have decided to go with IBM WAS. WAS supports more data sources than Oracle web logic. So, ideally it can be used with multiple databases.
IBM support is better than Oracle, from past experience. Weblogic and WebSphere Application Server are somewhat similar versus the open source JBOSS. For many applications we had selected WAS to have a supported platform and used some of the competitors in other various use …
I have worked on JBOSS and WEBLOGIC Application servers apart from Websphere application servers. WebSphere Application Server has a more user friendly admin console GUI. I believe WAS administration and maintenance activities are more easy and effective as compared to other …
Websphere Application Server supports enterprise Java open standards, streamlines deployment, has very flexible management capabilities and better reliability and availability.
I did not choose IBM WAS, it was a coporate decision. We are glad that we have been using this for a number of years and are quite happy as a corporation. However, it does take more time to learn WAS because of its complexity in terms of installation, various features and …
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. …
Nintex is easier than Visual Studio and richer than SharePoint Designer, chosen for accessibility, scalability, and faster business process automation.
Nintex is great! It works well with these applications. We can build profiles to give the bot the ability to use the applications like an employee. This gives us the ability to automate tasks inside our applications. As stated earlier, some of the applications are web-based. …
Nintex licensing is very suitable for our needs and solutions built are embedded and is adding a lot of value with the added benefit of being easy to maintain. The time to production for building some complex solutions versus other low code platforms is significantly less …
We selected Nintex because Process Manager is a purpose designed platform for knowledge management. However, what we discovered is that there are significant limitations, which has lead us to now explore developing a knowledge management platoform in sharepoint. this is a much …
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform …
Nintex Process Platform is a great tool for automatic tasks and creating forms in SharePoint Online. For automating using other applications, including third party, Power Automate has more usage.
Xmind was great for mind mapping, but when I tried to use it as a process mapper, I found it was rather lacking. It has its uses, but process mapping (at least for us in our stage and phase of mapping) was not up to the task, unfortunately. We didn't have any other software we …
We use Outsystems for other processes in our operation but we see that this platform is not able to indentify processes when drawed. Besides that OutSystems requires some basic development knowledge to use it. This makes it not really useable for business units.
IBM WebSphere Hybrid edition is well-suited for the development and deployment of large enterprise-level applications such as Electronic Health Records that are used in our organization. IBM WebSphere is appropriate for organizations that require strong security and compliance as it provides a high level of security and compliance features. This works well with organizations that are subject to strict regulatory requirements, such as hospitals.
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
It works out of the box. Its basic functionality is all there and everything works with no adjustments.
The functionality is there for fine tuning, to allow applications to be easier to access and quicker with some tweaks, but again, these aren't necessary for basic running.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
New Responsive Form does not allow to create a custom button anywhere we want. It will be useful to allow to add the button control anywhere within the form that can trigger the click event rule.
It will be useful to allow CSS in New Responsive Form.
Found HTML Table tag does not work properly in New Responsive Form.
More functionalities related to HTML, CSS and JavaScript in New Responsive Form will be very helpful.
Mostly we will be renewing unless the strategic direction changes drastically or there are other complelling external circumstances. We've been on a multi year project to modernize our legacy applications and that effort will continue for the foreseeable future.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
WebSphere Application Server is used across our organization. Most projects use this for Java products and applications. Being robust and scalable makes it even more usable. We love using WebSphere Application Server due to its configuration management ability made simple and vast across all java related parameters. It is dependent on the features and upgrades and IBM releases some great upgrades to WebSphere Application Server.
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
IBM was quick to respond when we had an issue with our specific infrastructure. We raised a PMR, which they picked up quickly and updated us about every step of the way. We had an appropriate fix for quite a business critical issue within a fortnight, which was impressive!
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
I did not choose IBM WAS, it was a coporate decision. We are glad that we have been using this for a number of years and are quite happy as a corporation. However, it does take more time to learn WAS because of its complexity in terms of installation, various features and special deployment and packaging needs.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.