IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

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.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 14 2018
  • Not Under Consideration
Idea Priority Medium
Customer Name Commerce Bank
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions