Auto-cleaning invalid identities in InfoSphere Metadata Asset Manager for InfoSphere

-

Problem(Abstract)

When you use InfoSphere Metadata Asset Manager with InfoSphere BigInsights to import metadata, if the contents of an import include objects with invalid identities, you must fix the invalid identities before you can preview the result of sharing the import to the metadata repository. You cannot import objects with invalid identities into the metadata repository.

Symptom

The analysis shows invalid identities in the import. The Preview button is disabled.


Cause

Importing objects with invalid identities can lead to problems in the metadata repository. Users of suite tools might not be able to access the objects. Therefore, the identities must be fixed before import.

Resolving the problem

You can fix the invalid identities in the source tool, when possible.

You can also fix invalid identities by "auto-cleaning" the objects. Auto-cleaning can remove the following types of characters that make identities invalid:

  • Preceding white space
  • Trailing white space
  • Consecutive white space
  • Unprintable characters from the identity strings of objects.

For example, the identity of a host computer is its name. The host name " XA23D" is invalid because of a preceding whitespace character. If you auto-clean that identity, the whitespace is removed and the name becomes "XA23D".

To auto-clean invalid identities, take the following steps:

  1. Create the file admin.properties in
    IISHOME/ASBServer/apps/lib/iis/70imam
    where IISHOME is the directory where InfoSphere Information Server is installed.

  2. Specify the following contents for the file:

    mmi.admin.invalidIdentities.autoClean.precedingWhiteSpace=true
    mmi.admin.invalidIdentities.autoClean.trailingWhiteSpace=true
    mmi.admin.invalidIdentities.autoClean.consecutiveWhiteSpace=true
    mmi.admin.invalidIdentities.autoClean.unprintableCharacters=true

  3. Stop WebSphere Application Server Liberty profile if it is running.

    For example:
    /opt/IBM/InformationServer/ASBServer/wlp/bin>server stop iis

  4. Run the following command from IISHOME/bin:
    iisAdmin -deploy -libModule 70imam -srcDir ISHOME/ASBServer/apps/lib/iis/70imam

    For example:
    /opt/IBM/InformationServer/ASBServer/bin>iisAdmin -deploy -libModule 70imam -srcDir /opt/IBM/InformationServer/ASBServer/apps/lib/iis/70imam

  5. Restart WebSphere Application Server Liberty profile.
    For example:
    /opt/IBM/InformationServer/ASBServer/wlp/bin>server start iis


For all subsequent imports, invalid characters are removed from the identity values. To auto-clean a staged import that has invalid identities, you must reimport the staged import.

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more