tag:blogger.com,1999:blog-6992129293870658291.post183824447864396377..comments2024-02-13T00:36:59.095+11:00Comments on Impossible Siebel: An XML LoggerJason Lehttp://www.blogger.com/profile/13322055780076477366noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6992129293870658291.post-31296745043357087142013-05-08T08:29:59.060+10:002013-05-08T08:29:59.060+10:00Hi Mik,
Thanks for your detailed comment. I look ...Hi Mik,<br /><br />Thanks for your detailed comment. I look forward to seeing your alternative approach.Jason Lehttps://www.blogger.com/profile/13322055780076477366noreply@blogger.comtag:blogger.com,1999:blog-6992129293870658291.post-28371018369993810482013-05-08T05:59:40.522+10:002013-05-08T05:59:40.522+10:00Hi Jason
I have made XML logging a component of t...Hi Jason<br /><br />I have made XML logging a component of the eScript Framework I blogged about quite a while ago (I guess it is due for an update):<br /><br />http://thesiebelscholar.blogspot.com/2010/05/escript-framework-logging.html<br /><br />The premise of my logging service is to store all data in the DB. This serves two points:<br />(1) Easy to relate Logging data to Txn records in various ways (Link integration and escript logs to a particular quote id being transacted upon)<br />(2) Do not need access to the file system to see log data which is especially useful when dealing with Unix app servers<br /><br />To overcome the file length limitations you mention, what I did was to break the text XML across multiple detail records. I then use a business service to concatenate all these detail records into a single calculated field so it is displayed in the UI. I basically copy and paste the XML data into a better Notepad++ so I can use Pretty Print on it, though I have been exploring how I can use browser script to launch a web editor to do this (browser script is not my strong suit)<br /><br />I will try to spend some time updating the blog so people can see an alternative approach<br /><br />MikMikhttps://www.blogger.com/profile/05638418157858689830noreply@blogger.comtag:blogger.com,1999:blog-6992129293870658291.post-65835891230031237172013-05-07T19:53:31.940+10:002013-05-07T19:53:31.940+10:00Hi, Thank you for your interest. The next article ...Hi, Thank you for your interest. The next article is scheduled to be published in two weeks.Jason Lehttps://www.blogger.com/profile/13322055780076477366noreply@blogger.comtag:blogger.com,1999:blog-6992129293870658291.post-27143432478019978432013-04-19T05:29:57.544+10:002013-04-19T05:29:57.544+10:00Great Articles!!
How is the next part coming alon...Great Articles!!<br /><br />How is the next part coming along?<br /><br />I have a proof of concept to build :)<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6992129293870658291.post-38780408792622966052013-03-25T21:37:33.017+11:002013-03-25T21:37:33.017+11:00Hi NanPats
Thats a valid concern, bad file loggi...Hi NanPats<br /><br /><br />Thats a valid concern, bad file logging design can bring a system to its knees, but IMHO I see the file attachment as an advantage. A small hit in performance to capture critical information when an error occurs is quite justified. <br /><br />Readers take note on the excellent archiving advice! =)<br /><br />JasonJason Lehttps://www.blogger.com/profile/13322055780076477366noreply@blogger.comtag:blogger.com,1999:blog-6992129293870658291.post-91074771317447189402013-03-22T20:21:14.266+11:002013-03-22T20:21:14.266+11:00Thanks ! I see you have referenced my blog in this...Thanks ! I see you have referenced my blog in this article as well. Thanks for that :)<br />Using EAI Queue in Siebel has another disadvantage. The XML message is stored as an individual file in Siebel file system which increases the disk I/O usage impacting performance directly. As well an enterprise solution using such approach should have a good archiving solution in place to keep the system health green.<br /><br />Cheers,<br />NanPatsNanPatshttps://www.blogger.com/profile/04071400551290708701noreply@blogger.com