IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
Currently even though we have multiple SSP engines it isn't possible to perform a true "high availability" upgrade of the engines because anybody who is connected to an individual SSP engine will be disconnected when the engine is taken down for patching, even though the other engine is still online and available.
We need to be able to shut down engines in a manner that allows "in-flight" connections to finish while preventing new connections from starting,
How will this idea be used?
Upgrade SSP with 2+ SSP engines:
1. Shut down first SSP engine. Engine will immediately stop listening for new connections which will cause Load balancers to redirect new inbound connecitons to other nodes. Existing sessions are allowed to complete before engine completes shut down.
2.Upgrade first engine to new version
3. Restart first engine
4. Repeat steps 1-3 for each remaining engine.
This allows upgrades to be completed with no interruptions to our end-users. Current design results in many users being disconnected mid-transfer at the moment the SSP engines are stopped.
|What is your industry?||Automotive|
|What is the idea priority?||High|
|Link to original RFE|