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.