Resolution:
Description:
============
How to increase debug level in FOM.

Environment:
===========
All

Resolution:
==========
OMS GUI :
Enable logging by appending "?log_level=DEBUG" in the URL of OMSUI. This will open a popup window which will give all logging that is happening for UI. This is GWT specific logging. Debug level for OMS UI is in $AF_HOME/config/OMSUILog4j.xml .

OMS/JEOMS:
Enable log4j logging with files:
$AF_HOME/config/OMSServerLog4j.xml
$AF_HOME/config/JeoMSLog4j.xml

HIBERNATE:
To see the queries used by OMS/JEOMS:
In $AF_HOME/config/ConfigValues_OMS.xml property hibernate.show_sql to true
In $AF_HOME/config/ConfigValues_JEOMS.xml property hibernate.show_sql to true

EMS:
To see messages in EMS and connections to queues. The messages will be seen in the WMS log. To find where the EMS log is located, check in tibemsd.conf. Set following properties in EMS with the EMS admin tool.

set server log_trace=+DEFAULT,+PRODCONS,+CONNECT
addprop queue > trace=body

To monitor temporal queues:
In $EMS_HOME/bin there is a tool to monitor named Tibemsmonitor. Run this tool with the following parameters (change hostname and port accordingly):

[Linux] ./tibemsmonitor -server localhost:7222  -monitor '$sys.monitor.Q.r.$TMP$.>'
[Windows] tibemsmonitor.exe -server 10.100.2.188:7222  -m "$sys.monitor.Q.r.$TMP$.>

BE:
To get more debugging within the FOM BE code add the following in the tra files:

tibco.clientVar.CommonServicesClientLib/Events/logLevel 4
tibco.clientVar.commonServices/configuration/GLB_LogLevel 10
To get debug in BE itself:
Debug level is in the cdd file (location of cdd file is in the tra file)
&ltlog-config id="logConfig">
            &ltenabled&gttrue</enabled>
            &ltroles>*:all</roles>

ACTIVESPACES:
Connect to metaspace to check members:
$AS_HOME/lib
java -jar as-admin.jar
connect name "AF_Orchestrator" discovery "tibpgm://7777/0.0.0.0;224.4.3.87"
show members
show spaces

In OMS members will join the space when sending an order. In the log we have to see:
[ASCache] [] - Getting metaspace "oms_metaspace"...
[ASCache] [] - Metaspace "oms_metaspace" connected

With BE we will get the members in the space when starting the engines.
[SME-Comments] customer
BE will create AS log in $TIBCO_HOME/tra/domain/&ltdomain>/application/logs with name as-PID.log. Being PID the PID used by the BE engine.
AOPD does not use AS.
BE using AS:
ORCH agent,cache
OCV agent,cache

Increasing FOM Debug level.