17.2.1 UDAS
17.2.1.1 Logs setting
IN R1.0x : UDAS logs can be enabled by editing the file $UDAS_HOME/trace.xml
IN R1.1 : UDAS logs can be enabled by editing the file $UDAS_HOME/trace.xml
And modifying the xml node [<category name=”com.alcatel” ..>] as described bellow (UDAS server reads
this file every minutes so no need to restart it):
<category name="com.alcatel" additivity="false">
<priority value="info" />
<appender-ref ref="SIZEROLLING" />
</category>
<category name="com.alcatel" additivity="false">
<priority value="debug" />
<appender-ref ref="SIZEROLLING" />
</category>
UDAS logs are located under /logs/udas on OpenTouch server. The main's one is traces.log
The above example shows that UDAS cannot connect to LDAP server because of credentials.
05 juil. 2011 09:52:45,739 ERROR [main] (AlcLDAP.java:153) - Connection to ldapdir_20301 LDAP directory
failedjavax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
05 juil. 2011 09:52:45,739 ERROR [main] (AlcUdasImpl.java:717) - Connection to 'ldapdir_20301' directory failed
17.2.1.2 UDAS startup
At startup, some informations are logged and can be useful in case of bug.
When starting, UDAS firstly reads its configuration from CMS.
UDAS wont start until CMS request failed.
If you don’t see in log file the message : UDAS server OK on :
rmi://XXX.XXX.XXX.XXX:9811/RMI_NAME_UDAS, that means UDAS can’t reads its config from CMS.
In this case you will see this message : Initialization problem sleeping 5000 ms before next attempt
XXX.XXX.XXX.XXX must be replaced by the ICE server address.
17.2.2 LDAP
The content of an LDAP directory (ex: 8770 embedded one) can be browsed using tools like the LDAP
Browser/Editor 2.8.2 java tool (from Jarek Gawor).
Installation:
1. Get the main archive file:
2. Unzip on a Unix of Windows box
To Next Page
Loading...
Need help?
General
