Watson Commerce Ideas

Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, Call Center and CPQ are now a part of Watson Supply Chain. Please bookmark the Watson Supply Chain Idea Portal.

Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, Dynamic Pricing, 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 and the Order Management Interest Group, now a part of Watson Supply Chain.

Submit ideas for other Watson Customer Engagement Products:

  • Watson Marketing
  • Watson Supply Chain

IBM Sterling Rest Services should support BASIC and STANDARD authstyles at a time in the same instance

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 20 2018
  • Needs review
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
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 27, 2018 13:00

    Strongly recommend

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 16, 2018 09:55

    I don't see any update on this. Appreatiate if any one form PRODUCT repsonds on this.



    Sunith Dodda.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    January 07, 2019 06:06

    Token information should not be a part of URL. There should be a provision to pass it in header parameter.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    April 11, 2019 07:57

    "Token information should not be a part of URL. There should be a provision to pass it in header parameter." -- I too agree with this.