How can we integrate to an enterprise logging system?
The client needs to integrate to their enterprise logging system. I see a 'LogController' tool available in Pega 8.0, however I cannot find any help resources for it and it doesn't seem intuitive to use from the studio. Can anyone provide some insight into this?
Thanks,
Gar
Pegasystems Inc.
US
The LogController is a component for enabling and disabling the Pega Robotics RuntimeLogs. To integrate with your logging system, you'd need to provide more specific about what you need to do. Likely, there isn't a component that does that for you, but rather a set of components or one you'd create or integrate into your solution that would work for you.
Unum
US
Hi Gar,
So happens that I too just recently implemented Enterprise Logging into our Openspan (7.1) Automatons. I took our existing Enterprise Logging Class, that had been created in Visual Studio/.NET and modified it to inherit from the Component Class. It must be inherited from Component, otherwise you will not be able to add it to the Toolbox in Visual Studio. Once you get the Logging Component added to the Toolbox, you can then drop it into the Global Containers across your Automation Projects. Once in your GC(s), you can them drag & drop on the Automation Designers, set the properties and you are good to go! If you need any additional information, just let me know.
Regards,
Scott
Accenture
CA
Thank you Scott, this is very helpful. Just to clarify, does this mean we would need to drag & drop this custom component every time we want to log to our enterprise logging system?
Unum
US
Well, that really depends on how many separate Projects (Global Containers) that are in you Solution. You would have to drag & drop from the Toolbar into each distinct GC. From there, you would have to then select form GC in order to use within your Automation (Designer). Hopefully that makes sense...? If not, then I can try and pull together some screen shots and upload a document to better explain the process, just let me know?
Accepted Solution
Unum
US
Just to follow-up and to clarify, this also may depend on how exactly your Enterprise Logging Component is designed and coded. For ours, you have to make explicit calls to it's Methods. We have a Method for just logging informational data and we have a Method for logging Exceptions (Errors). Both Methods take a few parameters. We then implemented within Automatons that have TRY...CATCH in them, so on the Exception path, we can log them.
Accenture
CA
This is very helpful Scott, you saved me a lot of trouble!