Author Message
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
Hi Team,

We are facing "AES Connector Not Logging" issue on OD 8.1.2.1101 on Websphere.
It seems "AES Connector" is working well without any error.
However only logs were not outputted after below logged message.

30/05/2023 18:06:31:654 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
30/05/2023 18:06:31:657 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
30/05/2023 18:06:31:657 DEBUG - CTIConnectorManager.init: AES Connector Version is 08.12.11.01
30/05/2023 18:06:31:657 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
30/05/2023 18:06:31:658 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
30/05/2023 18:06:31:658 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
30/05/2023 18:06:31:658 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
30/05/2023 18:06:31:661 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#CM#CSTA-S#TPBKCCS0PA001F0

On the other hand, I found below as known issue in release note.
In this case of workaround, it is for Tomcat.
If we are using OD with Websphere, please advise how to fix this issue as workaround.
I'm asking same question to OD team as well.
However this is issue on AES connector side.

Avaya Orchestration Designer 8.1.2.1101 release note
4 Known Issues
• AES Connector Not Logging
Due to the upgrade of JTAPI to support Log4j v2, AES Connector might stop logging at the following statement (in italic) in early stage of setting up the AES connection.
CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:xxxxxxxxxxxxx
*Note: by default, a version of log4j.xml has also been placed in the WEB-INF/classes directory. This could fix the issue without the following workaround.
When this happens, it is necessary to take the following steps:
a. Go to the TOMCAT_HOME/webapps/aesconnector/WEB-INF/ directory
b. Copy the aeslog4j2.xml file into TOMCAT_HOME/lib as log4j.xml
c. Edit this line to tell aesconnector where to create the log file: <Property name="log-path"> ${log4j:configParentLocation}/../data/log</Property>
Or it will just create the trace.log file in the TOMCAT_HOME/data/log directory as the default

Best regards, K.Yamahara
HarryPresley
Joined: Aug 11, 2023
Messages: 3
Offline
Hi Kenji, Copy aeslog4j2.xml to the Websphere dir, rename it to log4j.xml, and edit the path. The adapted workaround should resolve the AES logging issue.
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
Hi all.

I got below suggestion. After follow it, I could resolved this issue.
===
Following two files located in “<aesconnector install directory>\WEB-INF\lib” needs to be move/copy to “lib\ext” directory.

ecsjtapia.jar (Move to "C:\Program Files\IBM\WebSphere\AppServer\lib\ext")
avayaprca.jks (Copy to "C:\Program Files\IBM\WebSphere\AppServer\lib\ext")

Logs are generated as defined in “<aesconnector install directory>\WEB-INF\classes\ log4j2.xml”
===

Thank you, Kenji
Go to:   
Mobile view