This is an IBM Automation portal for Cloud Platform products. 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
Decoupling WebSphere Application Server patterns and Cloud Pak System releases
Currently, IBM used to deliver a new version of the WebSphere Application Server Pattern type as part of the default content for new CPS releases.
WebSphere Application Server Pattern type is actually composed of 2 artefacts:
- the WebSphere Application Server Pattern type itself, that contains software components for WAS ND, Liberty and IHS, script packages, examples of patterns...
- an IBM Installation Manager repository that contains the installation binaries for IBM WebSphere Application Server Network Deployment (several versions), IBM HTTP Server, IBM Java SDK, IBM WebSphere Liberty
The WAS pattern type is documented to support WAS up to the versions provided in the IBM Installation Manager repository.
The frequency of the releases is different between CPS and WAS products:
- every month for WebSphere Liberty
- every quarter for traditional WebSphere Application Server
- the time between 2 CPS releases varies a lot (see https://www.ibm.com/support/pages/related-information-ibm-cloud-pak-system-releases), but, since v22.214.171.124 it was between 3 months and 10 months.
Moreover, because WAS pattern types versions are dependent on the CPS version, you need to first upgrade CPS, which requires SWAT team involvement, before upgrading the WAS pattern type, which is causing delays before implementing the latest versions of WAS.
Shorter cycles for WAS pattern type and repository content releases would help customers to stay up to date on WebSphere Application Server releases and fix packs, especially regarding security fixes.
We would like IBM to decouple the release cycle of the WAS pattern type from CPS release cycle and have more frequent updates of the WAS pattern type and repository content.
Do not place IBM confidential, company confidential, or personal information into any field.