... manage metadata in Data Mover

In Data Mover, these metadata classes are managed:

• Generic metadata class

• Spazio2 metadata class

• eMail metadata class

Generic metadata class

These metadata are used-defined and are composed of a pair with this syntax:

"custom_metadata_name":"custom_metadata_value"

For example:

"BUSINESS_UNIT":"Accounting"

"AUTHOR":"SUSAN"

"KEYWORD":"INVOICES_JAN_2025"

Each customer can manage its generic metadata by APIs (see the HTTP MFT Rest API page) or Get Metadata service task and Set Generic Metadata service task (see the Standard service tasks page).

Spazio2 metadata class

Spazio2 metadata are fixed.

Spazio2 metadata list

{Z_COMPRESS, FILE_LENGTH, FORMAT, ORIGIN_MESSAGE_FILE_ID, EOR_EOF, USER_ID, CODEPAGE, PRIORITY, ORIGIN_QUEUE, PUT_APPLICATION_TYPE, ORIGIN_INTERNAL_NUMBER, LOCALLY_EXTERNAL, ORIGIN_ACK_LEVEL, ORIGIN_CODED_CHARSET_ID, APPLICATION_IDENTITY_DATA, USER_CLASS=CLA1, APPLICATION_ORIGIN_DATA, DESTINATION_PATHNAME, REPLY_TO_QUEUE_MANAGER_NAME, START_PUT_DATE, ORIGIN_USER_CLASS, BINARY_FILE, CORRELATION_ID, ACCOUNTING_TOKEN, ACK_LEVEL, ID_FILESET, ORIGIN_CODEPAGE, QUEUE_MANAGER_NAME, SENDER, ID_FILE, QUEUE_NAME, DESTINATION_EXTERNAL, INTERNAL_NUMBER, NODE_NAME, DESTINATION_FILENAME, LAST_READ_DATE, PUT_APPLICATION_NAME, FIRST_READ_DATE, MESSAGE_FILE_ID, EXPIRY_DATE, ORIGIN_ENCODING, DESCRIPTION, ARRIVAL_DATE, ORIGINAL_FILENAME, REPLY_TO_QUEUE_WRITE_PASSWORD, DSTK, ADDRESS_TYPE, ID_ROW, REPLY_TO_QUEUE_NAME, ORIGIN_QUEUE_MANAGER, CODED_CHARSET_ID, REPLY_TO_QUEUE_ADDRESS_TYPE, ENCODING, SESSION_ID, ORIGINAL_FILESIZE}

To obtain the Spazio metadata of a file, the following syntax must be used:

"spazio_metadata_name":"spazio_metadata_value".

For example:

"SENDER":"JANEDOE"

"CORRELATION_ID":"invoices2025.xlsx"

Each customer can manage its Spazio metadata by APIs (see the HTTP MFT Rest API page) or Get Metadata service task and Set Spazio2 Metadata service task (see the Standard service tasks page).

eMail metadata class

eMail metadata are fixed.

eMail metadata list

{MAIL_RECEIVED_DATE, MAIL_SIGN_CERT, MAIL_SUBJECT, MAIL_BCC, MAIL_CERT, MAIL_FROM, MAIL_SENT_DATE, MAIL_TO, MAIL_SIGN_DN, MAIL_SIGN_DATE, MAIL_BODY_BLOB, MAIL_RAW_SIZE, MAIL_CC, MAIL_SIGN_STATE_MSG, MAIL_SIGN_STATE}

Each customer can get its eMail metadata by APIs (see the HTTP MFT Rest API page) or by using the Get Metadata service task (see the Standard service tasks page).