https://communities.bmc.com/communities/docs/DOC-22528

Refer Page 4:


Disable Email Engine Logging to Form



Logging to file and AR Form is enabled by default in Email Engine at logging 
level SEVERE. When there are no entries found in 'logging.properties' file for 
the Email Engine then the file and form log appenders are added dynamically by 
Email Engine.

File logs of Email Engine can be found in <AR SERVER 
HOME>/AREmail/Logs/stdout.log (WINDOWS) and <AR SERVER 
HOME>/AREmail/Logs/emaild.log (Unix). Each message logged in log file is also 
logged in Email Engine log form 'AR System Email Error Log'. So logging to form 
is generally not useful unless you access the log form a remote machine. So it 
is safe and better to disable the logging to form which will reduce API calls 
from Email Engine related to logging.

The 'logging.properties' file can be found under the directory 
'{JRE_INSTALL_DIR}/lib/' (Or you can refer to the EmailStart.bat file on 
Windows or emaild.sh file on UNIX for the JRE which is being used.). For 
disabling the form logging, add or update the following entries in the 
'logging.properties' file.
com.bmc.arsys.emaildaemon.ARSystemHandler.level = OFF

Also the data in the said can be cleaned up.


Non-functional Data Clean Up

The said database table contains Non-Functional Data/error logs which can be 
purged

1)       AR System Email Error Logs

Agree/Acknowledge on the indexing part; there is a cleanup act in place and 
should see in the product as well.

Regards,
Ravi

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Jason Miller
Sent: 14 February 2013 01:05
To: [email protected]
Subject: Re: Email Messages Form Indexes?

**
Idea submitted...  Review Email Engine form(s) indexing and adjust as 
appropriate<https://communities.bmc.com/communities/ideas/1758>

Jason

On Wed, Feb 13, 2013 at 9:44 AM, Drew Shuller 
<[email protected]<mailto:[email protected]>> wrote:
** After running combined SQL and API logs, Misi's suggestion was the one that 
identified the problem. The Email Error Messages form has no indexes, so I 
added one for the Email Message ID, which is in one of the queries that I saw 
in the log file. Now even an unqualified search on the 3400 or so records runs 
very fast. Then I set the table property to false as suggested, just for good 
measure. And yes, there were a ton of records in the Email Error Messages form 
that are taking up space in the db. Those will be gone soon!

Thanks everyone for the help!

Drew Shuller
JTF-Bravo Honduras


On Wed, Feb 13, 2013 at 2:16 AM, Misi Mladoniczky 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

The typical problem is too many records in the AR System Email Error Logs form.

You can see this if it takes time to flip between records after you have
performed the search. You can safely remove the refresh-on-entry-change for
the table field that loads the Error Logs data to save time.

If you look at the indexes, and almost anything related to the AR System Email
forms, you will see that the person who built them had next to no clue on how
to build Remedy applications ;-)

        Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to