Watson Commerce Ideas
Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, CPQ, Dynamic Pricing, Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, Price Optimization, Promotion Optimization, Markdown and Deal Management. 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.
Connect with your peers and IBM experts on the Watson Marketing and Commerce Community
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Supply Chain
LIMITATION: In IBM Sterling Order Management 9.4 and 9.5, Currently If we want to use Rest Services in one deployment we have to choose either of the one authstyles 'BASIC' or 'STANDARD' only.
Customer has deployed SMCFS on 2 WAS instances to serve all the synchronous requests and wants to use OOTB Rest Apis.
One of the Order capture channels has need to call IBM Sterling synchronously, and with multiple parallel threads, And they dont have need to track any user activity to maintain the tokens, So planned to use BASIC servlet.authstyle.
But there are other scenarios where in customer will have a valid user LoginId/Token then they need to use those credentials to call Rest service instead. Then we need to use STANDARD servlet.authstyle.
Where-in most of the calls use BASIC authstyle way, and few need to use STANDARD authstyle.
Problem, with current Rest Services support is in IBM Sterling we don't have any servlet.authstyle specifying both these features of BASIC and STANDARD authstyle. I was wondering why was this not supported. This is need of the hour.
Please do needful.
How will this idea be used?
Provide synchronous REST calls to Order Capture system and To another application which has access to loginId and token. So that we will be able to call IBM Sterling via Rest Service calls REST APis in both modes (authstyles) with the same deployed Enterprise application in WAS.
|What is your industry?||Retail|
|What is the idea priority?||High|
|Link to original RFE|