IBM Sustainability Software - Ideas Portal
This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 updates on 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
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.
Hi Michael,
We have had a series of internal discussions around this Idea.
Our MAS architecture must spec two levels of subdomain to the domain provided by the user: <<workspaceId>>.<<applicationId>> and that's pretty much unavoidable because we are a suite operating under a single domain and we need to partition up the things in the suite.
If the user sets the spec domain to <<myco.ca>> then the hostname would be:
https://<<wsId>>.<<appId>>.myco.ca
This is the closest we can get to the 'simple URL' you are looking for, and the difference could be a little as three characters for your ideal.
Any other form of redirect would need to happen at the HTTP level outside of MAS.
We are not in a position to improve upon this within our current architecture, so I'm setting this idea to future consideration.
Hi Andrew,
This would still not work and is not what most clients are looking for. For example man of my clients that expose Maximo Internally or externally and that are even on IBM Managed services have a very simple hostname such as maximo.myco.ca. You suggestion of having something like https://mxe.manage.stg.myco.ca is not what clients use today as we start to migrate them and they have clearly communicated that they want to keep the same DNS name as they have today. In your example the preference would be https://manage.myco.ca or https://maximo.myco.ca or https://???.myco.ca. Clean simple and URL friendly.
Hi Michael,
Today's MAS allows you to configure the base domain that is used for all the URLs, however it does require you to use fixed subdomains.
The complex URL shown in the introduction results from using the default, which is based on the OCP cluster domain.
To illustrate this if you examine https://mxe.manage.stg.apps.masmfa.myco.ca, the first 3 portions are required:
mxe is the workspace id
manage shows what application it is
stg is the instance id
The remaining bits can be replaced, so you can simplify this to
https://mxe.manage.stg.myco.ca
Let me know if this addresses your need.
Hi Michael, Thanks for submitting the idea. I will review with the team and come back to you.