Hi,

My customer wants to put aesconnector logs.
They are using the following's environment.
EP/OD:8.1.2
Web application server:IBM Websphere application server 9.0.5.

I found the known issue "AES Connector Not Logging" in Release note of 8.1.2.
But this is for Tomcat.

Is there any work around for IBM Websphere application server ?

Regards,
Kodera

Hi.

Did you face any error message with the WAS ?


Recently Devconnecxt faced this issue with the AES connector for WAS:

https://www.devconnectprogram.com/forums/posts/list/26001.page#p166488

Hi,

Thank you for your support.

Now there is no problem with TLS connection to AES.
But we cannot see the log of AESConnector.

Do you have any idea to put the AESConnector log?

Regards,
Kodera

Did you try to invoke the runtime configuration servlet and on the AES tab ? There is log level 0-3 with 3 being most verbose.

Are you looking in the AESConnector/data/log dir on your appserver ? Could it be a permission issue ?

Did you check the file 'aeslog4j.properties' ?

Hi,

>>Did you try to invoke the runtime configuration servlet and on the AES tab ? There is log level 0-3 with 3 being most verbose.
Yes, Trace Verbosity is 3.

>>Are you looking in the AESConnector/data/log dir on your appserver ? Could it be a permission issue ?
I'm using Windows 2019. And other applications put logs correctly.

>>Did you check the file 'aeslog4j.properties' ?
I updated 'aesconnector.war\WEB-INF\classes\log4j2.xml'. Because OD8.1.2 release note says so.
After changed it, I can see some log in the log files.
There are only 8 lines.
02/06/2023 17:59:53:686 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.init: AES Connector Version is 08.12.11.01
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
02/06/2023 17:59:53:701 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#APSCM8#CSTA-S#APSJP-AES8

Regards,
Kodera