Skip to Main Content
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
  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 Not under consideration
Categories Integration
Created by Guest
Created on Apr 14, 2021

Maximo Message Tracking throws error "Content is not allowed in prolog" in SystemOut.log

Problem: When using Publish Channels with an XSLT transformation and sending JSON data when viewing the data in Message Tracking it produces an error in SystemOut.log

"Problem converting bytes to document
org.jdom.input.JDOMParseException: Error on line 2: Content is not allowed in prolog."

Also in the Publish Channel 'Message Tracking; settings you set a External Message ID it will produce the same error in SystemOut and not populate the External Message ID.

Idea priority Urgent
  • Admin
    Kim Woodbury
    Reply
    |
    Dec 8, 2021

    This is not something that should behave as requested. You can only use XPATH for XML messages, be sure when creating enterprise service or channel what datatype it should carry (XML or JSON). It cannot be both.

  • Guest
    Reply
    |
    Sep 23, 2021

    Hi Kim,

    I don���t know if the new system sends you alerts.
    I have added in text about this ��� it isn���t one of my RFEs but I heard about something that sounds like it and fits the description.

    https://ibm-ai-apps.ideas.ibm.com/ideas/MASM-I-347

    best regards,
    Mark

  • Guest
    Reply
    |
    Sep 23, 2021

    This sounds like a bug that should be raised as a PMR although Development may correctly that it is a missing feature.

    I believe this relates to an integration feature for Enterprise Service/Publish Channel


    Open either of those applications and select the Message TRacking option.

    The Message Tracking Settings dialog box is displayed.


    This IBM document describes this feature:

    https://www.ibm.com/docs/en/mam/7.6.0?topic=mt-message-tracking-configuration


    XPath values can be put into the "External Message ID" and "Search ID" fields.

    The XPATH can be used to extract a single value from the XML e.g. to populate the workorder number so administrators can search for messages with that workorder number.


    Xpath can't be successfully executed against JSON text (which is in a different format)

    I suspect that the error described above would be written to the log.

  • Guest
    Reply
    |
    Apr 14, 2021

    Sure sounds like a bug to me.