LPS Side Injection

The ExMeX Tool - LPS Side Injection is a SQL Script for injecting a Load Process Step (LPS) into the ExMeX Framework Core.

This injected LPS is used to allow external applications to use the ExMeX Logging Framework.

The injected LPS allows external applications to collect data logistic statistics not only for batches but also for the atomic LPSs contained in them.

Main features are

  • Inject a LPS
  • Add injected LPS to a batch

How to inject an LPS?

At least Version 2.11.0 of ExMeX Framework Core has to be installed. 1. Extract 7z-file to /library/tool in your root directory.…

At least Version 2.11.0 of ExMeX Framework Core has to be installed.

1. Extract 7z-file to /library/tool in your root directory.

2. A new folder will be added (if it not already exists): LPS Side Injection.

3. Copy or rename LPS Side Injection/LPSSideInjection.orig.sql  to LPS Side Injection/LPSSideInjection.sql  and open script LPS Side Injection/LPSSideInjection.sql in SSMS.

4. Change the following lines (73 and following) to add a LPS Side Injection

You can adapt the script as often as you like, as an LPS side injection only has to take place once. Reinstalling the metadata does not change the injected LPS and its assignment to a batch. Of course, a script can also be created for each LPS side injection.

Specify only the batch to which the LPS Side Injection is to be assigned. Not a related parent, master or child batch.

--#-----------------------------------------------------------------------------
--# Edit Insert below
--# Recommendation: DO NOT INSERT more than 1 (one) row
--#-----------------------------------------------------------------------------

INSERT INTO @LPSSideInjection
    -- Source
    VALUES (
            -- Model, add a fictitious model (ModelCode, ModelName)
            -- Do NOT change the fictitious model!
            'LPSSideInjection','LPS Side Injection'
            -- Add a fictitious Source Entity ('<YourFictitiousSourceEntityCode>','<YourFictitiousSourceEntityName>','<YourFictitiousSourceDatabase>','<YourFictitiousSourceSchema>')
            ,'<YourFictitiousSourceEntityCode>','<YourFictitiousSourceEntityName>','<YourFictitiousSourceDatabase>','<YourFictitiousSourceSchema>'
            -- Add a fictitious Target Entity ('<YourFictitiousTargetEntityCode>','<YourFictitiousTargetEntityName>','<YourFictitiousTargetDatabase>','<YourFictitiousTargetSchema>')
            ,'<YourFictitiousTargetEntityCode>','<YourFictitiousTargetEntityName>','<YourFictitiousTargetDatabase>','<YourFictitiousTargetSchema>'
            -- Batch to which LPS is associated, must exist in table MetadataZone.LoadBatch ('<YourBatchLabel>')
            ,'<YourBatchLabel>'
            )
;

--##############################################################################
--#-----------------------------------------------------------------------------
--# DO NOT EDIT BELOW
--#-----------------------------------------------------------------------------

5. Execute the script.

6. Done. A new LPS is injected and added to a batch.

7. Now the stored procedures uspProcessStepVapourTrail and uspBatchVapourTrail can be used to write to the ExMeX Logging Framework. See also section Framework In Depth -> Stored Procedure.

It is not necessary to install the metadata again. An LPS Side Injection is independent of the ExMeX Framework Core metadata. It is only necessary to use the ExMeX Logging Framework.

Posted 1 year agoby Dirk.Lerner