Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Nov 21, 2017

IMAM XSD Import from Engine Tier

InfoSphere Metadata Asset Manager (IMAM) allows you to import .xsd files to get metadata about respective .xml data files. However the way IMAM currently works is that the .xsd file you want to import can only be on the client from which the IMAM web console was opened. This means that if I open IMAM from my client machine, the .xsd file must be on my client machine. The problem is that when you pull in that metadata, it makes it look like the .xsd/.xml file could be under a directory such as "C:\Users\username\documents\file.xsd" instead of the real location of the data file which would be on your InfoSphere engine tier (if being used with DataStage).

I would like IMAM to have the ability to load .xsd/.xml metadata from .xsd files that exist on the InfoSphere engine tier, so the metadata is accurate as far as file location is concerned.

One solution that was proposed was to launch IMAM from a browser on the engine tier server, which does work, however it's not an acceptable solution. Doing this would mean we have to install and maintain a browser on the engine tier server (can be complicated when using RedHat Linux with no GUI, just command line). It would also mean people would have to have security permissions to get on the engine tier to launch IMAM to import .xsd files. Not a big deal when working on test servers, but inappropriate for production servers.

IMAM today is able to import sequential file definitions when that file exists on the InfoSphere engine tier. We'd like the same ability for .xsd files.