This is an IBM Automation portal for Digital Business Automation products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Automation Decision Services (ADS) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Business Automation Manager Open Edition
Specific links you will want to bookmark for future use
we had a major outage for one day on our platform because our DB has a problem with high CPU usage which are using for res consoles and RTS schema. we are researching all ways to look at any slow executing queries that are consuming more CPU.
we are using XUs and res console for communication for any rulesets update to client code execution, we are thinking res consoles are down our XU's should continue to execute rulesets with older versions(cache) and should not impact older rulesets
My L3 team has analyzed the problem in this case & concluded that the functionality we are seeing is how it is designed.
Although the parsing of the ruleset is done in a separate thread, loading from the db is not & hence if the loading fails then further ruleset execution fails too.
This impacts our platform to 36.9M unprocessed transactions in one hour, so we would like to make it work independently if one thread down.
Do not place IBM confidential, company confidential, or personal information into any field.