This portal is to open public enhancement requests for IBM Sterling products and services. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for taking the time to provide your ideas to IBM. We appreciate your willingness to share details about your experience and your recommendations.
After reviewing this we have decided to consider to implement this idea through a UI change in one of our future releases based on roadmap priorities. However, please do note that connection from SSP Engine to CM may pose a security challenge and hence we may consider doing this with a UI capability.
If you have any additional feedback, thoughts or ideas, or if there is anything else I can do, please do not hesitate to reply to this message to continue the conversation.
Thanks,
Product Management - Sterling Data Exchange
Currently we have to manually copy it via SSH from a jump host from the CM to the Engine. This is not sustainable for resiliency purposes (the copy must be automatically triggered by the Engine because the CM or the jump host has no way of knowing that the Engine was repaved and needs to ingest the file).