How can i generate my defined custom headers in data schemata

Legacy Contributor

Hi!

I can not find anything about the topic file template and object schematas. I think they work hand in hand, and there are some certain points that are still not clear to me.

 

I created different file templates, for example, a custom XML. I uploaded my file, set a filetemplate name and type, generated the metadata, and chose the ID field within my xml. After generating my XML File Template, I found the same filename in the object schema. I selected this object schema and added a customer header for my sync fileTemplate. I saved everything and expected that when I imported my file template from the file directory with my connection point, I would have my defined custom headers. I checked in OneView my imported file and there were no custom headers.

Do I need to generate the schema to enable my defined headers? How can I activate my defined custom headers in the schema?

When I changed something in my file template, I received a message stating that I would override my custom schema with this file template. I accepted and thought that my custom header definitions in the schematas were not set anymore because they were overridden by the generated metadata from filetemplate. After generating the file template again, the custom header definitions are still in my schema.

Thanks for answering these questions.

• How can i generate my data schemata into my file template?

• how can i enable my custom headers property in the data schemata?

• where will i find this custome headers?

• How will work data schemata and filetemplate together?

Thanks for your ideas, thoughts and help.

Kevin Heiman

There are several standard and optional headers available for a publisher of messages to use.  And as you note, there are 3 Custom_ Headers which can be defined in the Schemas in Data Catalog.

What you appear to be missing is the publish populating these headers.  File Connector does not have a way to populate most headers.  If it did, you would need to instruct it where to get that data from to fulfill the headers and other properties.   If you are using an IMS or Application connector, you have full control over the headers that are sent, and would be able to use additional ones there.

If you want to read the data in a script after the file connector, you can update / add headers in that script so they are carried forward from there.

If you re0generate from any of these, you will loose the custom schema as you note.

Some of the guidance relies on knowing what the use case is for these headers. Are you using these for Oneview filters, or is the Consumer side using them?  Or is this a Data Lake file usage?  Or is there a flow filter using them?