Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Define an Accounting Event in Automation Center to generate the needed data in .csv format.

image-20240719-162903.png

Note the event name, and the output folder and output file name:

image-20240719-162406.png

Import and publish the workflow run_event_and_distribute with IWS UI.

Define a distribution profile in estar/tpe/dynamic/metadata/distributions/.

The distribution profile identifies the destination of files.

The azure blob type should identify the credentials, container name and dropdir name.

There should already be examples of distribution profiles sending to azure in your source environment.

Detailed documentation on distribution profiles:

Create an EJM profile in EJM Monitoring Tool (Activities tab) for the run_event_and_distribute workflow:

image-20240719-162716.png

eventName parameter is the name of the accounting event to execute.

localFileName_1 is the full path to the output file (this should match the accounting event definition).

Additional file names for events having multiple output files can be specified with localFileName_2 etc.

distributionprofilename identifies the distribution profile; for a profile named azure_prod_extracts_profile.json, the parameter value would be azure_prod_extracts.

 

The EJM profile can be run manually or from an Automation Center schedule.

  • No labels