Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Submitted
Created by Guest
Created on Dec 5, 2024

ADDI Server code to notify unsupported Java

ADDI Server does not check that pre-reqs are in place. If ADDI Server is being installed on a supported version of Java JDK, memory/CPU requirements, etc.

Solution: A warning to notify the user that the pre-reqs are not in place, such as "Version of Java does not appear on a supported environments list", "Low Memory", "Low CPU Cores" etc. will make the on-boarding process more friendly.

Example Problem: Currently if an incorrect version of Java is installed, problems occur, but there's not really anything in the log files that would suggest why issues are occurring.

How this would improve onboarding: The Graph Database service starts and stops straight away - but doesn't generate an error - if certain unsupported versions of Java are installed. The logs do not say why the service is behaving in this way and this requires someone to "just know" that it's a Java problem. This can take days to troubleshoot rolling back VM snapshots and re-doing the install end-to-end each time.

Idea priority High