Integration


This is an IBM Automation portal for Integration 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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Jun 18, 2024

RELATED IDEAS

Fully support java 11

We have recently upgraded from 12.0.2.0 to 12.0.11.1 and it has created a number of issues for us:

  • We have a number of java user defined nodes and now we get the following java compilation warning - Execution environment is lower than one of the plug-in's dependencies (org.eclipse.jface) which has an execution environment of JavaSE-11.

  • We are using ANT build scripts and with the new version of Eclipse, you can't launch ANT scripts from Eclipse using less than java 11. So, we changed the JRE for launching ANT from Eclipse to use java 11 but now we are finding that mqsiapplybaroverride is no longer working.

We looked into moving to java 11 but because SOAP nodes are not yet supported, this is not an option for us. For the moment we will have to live with the compilation warnings, but I am not quite sure how we will resolve our ANT build issues yet.

I believe that IBM making the move to fully supporting java 11 would solve these issues.

Idea priority Urgent
  • Admin
    Ben Thompson
    Reply
    |     Nov 25, 2024

    In ACE 12, mqsiapplybaroverride has been deliberately designed to continue running using Java 8, as the majority of v12 users would still currently prefer this behaviour. If you attempt to refer to build artifacts which were built with Java 11 then receiving warnings does not sound too surprising. We have attempted to run a test using the mqsiapplybaroverride command as part of an Ant script on ACE 12 and the command seems to work fine:


    Buildfile: C:\ToolkitDevelopment\AlvarPromoteIssue\App\ant\axis_bujava.xml
         [echo] pulling in property files
         [echo] calling the web services generation ant task: axis_bujava
    main:
         [exec] BIP1138I: Applying overrides using runtime mqsiapplybaroverrides...
         [exec] BIP1140I: Overriding property Main#HTTP Node.URLSpecifier with 'changedit' in 'App.appzip/META-INF/broker.xml' ...
         [exec] BIP1143I: Saving Bar file C:\ToolkitDevelopment\AlvarPromoteIssue\TestModeBarFiles\Appproject.TestMode.bar...
         [exec] BIP8071I: Successful command completion.
    BUILD SUCCESSFUL
    Total time: 1 second


    So, our suspicion is that when executing your Ant script on ACE 12, in an attempt to run under Java 11, you are encountering an issue related to Java 11 which is causing the warnings.


    In ACE 13, mqsiapplybaroverride executes by default using Java 17. There is an undocumented environment variable which can be used in order to specify switching to Java 8 but this is not a tested / externalised option right now.


    Regarding the wider statement about "We looked into moving to java 11 but because SOAP nodes are not yet supported, this is not an option for us. For the moment we will have to live with the compilation warnings, but I am not quite sure how we will resolve our ANT build issues yet. I believe that IBM making the move to fully supporting java 11 would solve these issues." … some comments about this area of support …


    Our long term intent is for ACE 13 to exclusively utilize Java 17 (at the moment users can pick to use Java 8 or Java 17 with any given integration server), and in due course we will announce full timelines for these activities through official channels, including the plan for SOAP node and WS-Security support in ACE 13 to switch from Java 8 to Java 17. Regarding ACE 12, we expect support for Java 8 to continue until at least the end of standard support for ACE 12 users in September 2026. We do not currently expect a full-backport of the ACE13 Java 17 capabilities into ACE 12. Hopefully the above info helps outline the likely way in which this area of the product will evolve across the release versions. As mentioned more information will be published about these aspects in due course, but for now we will leave this idea open in case others wish to comment or lobby for changes to the proposed directions mentioned above.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.