IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for IBM Sterling 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
It was noticed that the current steps(mentioned in below link) for SSO implementation is not suitable for External connection Via SSP/SEAS
for docker based B2Bi install.
According to the steps mentioned in above link,
1. files needs to be copied inside the container.
2. /private diretory needs to be created inside container after the container is build.
3. jar files needs to be copied inside container's /private directory.
These steps needs to be repeated every time the container is deleted and a new container is spawned.
In docker based implementation, we should not go inside container and do manual changes.
So a more cleaner approach is required for docker based SSO implementation.
As there are many customers using SSP and SEAS, so this implementation becomes a critical part.
Please provide a cleaner way of doing this implementation.
Attached is the reply from developer and the PMR raised for this is:TS002637002
How will this idea be used?
we should do a better way of implementation of this piece because this a component which is used by our Major clients who are using SSP/SEAS for external traffic. Because every time the container is dropped, we need to rebuild this components inside container.
|What is your industry?||Government|
|What is the idea priority?||High|
|Link to original RFE|