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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
System Certificate Name Update - Global Update to Adapters/CD Nodes
When editing a System Certificate under B2B console > Trading Partner > Digital Certificate > System > (Your System Cert) > "Edit Name or Usage of existing Certificate"... You aren't able to make that name change globally. So your CD nodes will fail and all adapters that were using that name.
What should happen is when you make that name change it should change it to the updated name anywhere that name was before. So to make an actual system cert name change you have to update every instance where the name is.. So in my case I would need to touch every environment where that system cert was which is in 150-200+ configurations manually.
I was told this was not something IBM was set up to with File Gateway.
What is your industry?
How will this idea be used?
In my case.. an admin before my time labeled the system cert as <systemcert>-2017 on all environments and then all of the nodes were created. But when renewal time came up it was kind of confusing seeing a date that would stay the same throughout and we would just update the cert itself.
So I attempted to just drop the 2017 from the name field. This just broke SFG so no connections could be made to any of the CD nodes or adapters.
Do not place IBM confidential, company confidential, or personal information into any field.