Message |
[+]
Avaya Orchestration Designer
» OD application cannot call AES connector, 27/04/2023 07:02:40
» Go to message
|
|
Hi Massimo-san,
Thank you for your helpful support.
We just took a sniffer trace.
Then we confirmed TLS handshake failed between application "/***_****/Start" and AES connector "/aesconnector/CallInfoInitialCall" due to certificate unknown error.
Since it is after Server Hello message, so it is because client doesn’t trust the server certificate as a cause.
Therefore we decided to manually export the AES connector server certificate chain from the avayaprca.jks file and import into runtimeconfig trust certificates page.
Any way, we tried to use "fetch" button to download certificate from aesconnector URL. After the AES connector certificate chain is imported into trust list, the application was able to connect AES connector internally.
So, please close this forum.
Thank you and regards, Kenji
|
|
[+]
Avaya Orchestration Designer
» FileNotFoundException error occurd about xml-apis.jar that is not included in OD RuntimeSupport File, 27/04/2023 05:46:09
» Go to message
|
|
Hi massimo-san,
Thank you for your support.
Please find attached file.
(attached file : OD_ver.png)
|
|
[+]
Avaya Orchestration Designer
» FileNotFoundException error occurd about xml-apis.jar that is not included in OD RuntimeSupport File, 26/04/2023 20:46:26
» Go to message
|
|
Hi massimo-san,
Thank you for your support.
We can NOT found the "xml-apis.jar" file in OD(8.1.2.1101) install package.
If we need to check other package, please advise.
Export>Export Runtime Support Files>IBM WebSphere
As a result of outputting with
- runtimeSupportWebSphere.zip does not include xml-apis.jar.
We tried to expanded all the contents of runtimeconfig.ear, but WEB-INF/lib only contains "runtimeconfig.jar" and does not include "xml-apis.jar".
Best regards, Kenji
|
|
[+]
Avaya Orchestration Designer
» OD application cannot call AES connector, 26/04/2023 13:16:05
» Go to message
|
|
Hi massimo-san,
Thank you for your quick support.
Furthermore , I created a similar environment in Tomcat and confirmed that values could be obtained from the aesconnector in the test call flow as below.
Instructions for Tomcat
1, Create an HTTP (non-secure) environment and confirm that we can get values from aesconnector in the test call flow.
2, Configure Tomcat so that it can be connected via HTTPS.
3, Create a self-certificate from the Certificates menu of runtimeconfig. Export the created self-certificate.
4, Import the self-certificate exported in 3 to the trusted certificate of the certificate on the EP management screen.
5, Change the flow launch URL from http to https in EP Admin, execute a test call flow, and confirm that the value can be obtained from aesconnector with HTTPS (secure access).
From the above, HTTPS access was successful in the Tomcat environment, but the problem occurred only in the WebSphere environment, so I think that the cause is in the settings related to WebSphere.
So, If my understanding is correct, we need to follow below procedure with WebSphere.
If it is wrong, please correct me.
1, Create an HTTP (non-secure) environment and confirm that we can get values from aesconnector in the test call flow.
I was able to create the environment without any problems.
2, Set WebSphere to be able to connect to HTTPS.
3, Create a self-certificate from Websphere management console. Export the created self-certificate.
4, Import the self-certificate exported in 3 to the trusted certificate of the certificate on the EP management screen.
5, Change the flow launch URL from http to https in EP Admin, execute a test call flow, and confirm that the value can be obtained from aesconnector with HTTPS (secure access).
Best regards, K.Yamahara
|
|
[+]
Avaya Orchestration Designer
» OD application cannot call AES connector, 26/04/2023 11:20:08
» Go to message
|
|
Hi massimo-san,
Thank you for your quick reply.
>Have you configured the tsapi.pro file accordingly (in our DevGuide https://download.avaya.com/css/public/documents/101083618 on page 599 ):
[Kenji]
Yes. We already configured them into the tsapi.pro file.
Actually, we performed below steps at this time.
What kind of any other action require to resolve this exception?
1, Create an HTTP (non-secure) environment and confirm that we can get values from aesconnector in the test call flow.
We were able to create the environment without any problems.
2, Set WebSphere to be able to connect to HTTPS.
It worked fine up to Validate.jsp, but when I called it, the flow was not called and an error occurred.
When I looked at the log viewer, the errors PAVB_00225 / PAVB_00187 / PAVB_03064 were output.
PAVB_00225?Socket Error in function SSL_connect - SSL_ERROR_SSL (A failure in the SSL library occurred, usually a protocol error)
3, We configure "Enabling Server Identity Verification" on security setting from "Yes" to "No".
4, As a results, an SSL related error occured. Then the OD application cannot run with below exception.
[23/04/24 9:14:20:127 JST] 000c7d88 SystemErr R ***** Saw exception, tracing before report
[23/04/24 9:14:20:127 JST] 000c7d88 SystemErr R javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target
Best regards, K.Yamahara
|
|
[+]
Avaya Orchestration Designer
» runtimeconfig woluld not get license from WebLM, 26/04/2023 10:59:19
» Go to message
|
|
Hi Massimo-san,
Thank you for your quick reply.
>With IBM, the JVM should be "IbmX509". "SunX509" is the default value used by JBoss. Did you explicitly configure that name ?
[Kenji]
I believe answer is "No".
So, please advise how to configure the Name for "IbmX509"?
If there are some recommended procedure in Dev guide or other Devconn thread, please advise.
Best regards, Kenji
|
|
[+]
Avaya Orchestration Designer
» FileNotFoundException error occurd about xml-apis.jar that is not included in OD RuntimeSupport File, 26/04/2023 10:42:27
» Go to message
|
|
Hi massimo-san,
Thank you for your quick reply.
I will try to do that tomorrow. Then I will feed results back to you.
Best regards, Kenji
|
|
[+]
Avaya Orchestration Designer
» FileNotFoundException error occurd about xml-apis.jar that is not included in OD RuntimeSupport File, 26/04/2023 10:15:28
» Go to message
|
|
Hi massimo-san,
Thank you for your quick reply.
I understood your answer. However I still need more help.
We are using Websphere. Then I found below similer thread. Then I understood we also need to follow below procedure for 'xml-apis.jar' as well.
Is this my understanding correct?
Subject: Axis2 Problems
https://www.devconnectprogram.com/forums/posts/list/21782.page#p152614
for webShepre follows next steps and recomendation, you can fin this in the OD dev_guide :
Performing additional WebSphere configuration
About this task
For WebSphere 7.0 and later, the Axis2 library files provided by Orchestration Designer conflicts
with the Axis2 library files from WebSphere installation. Therefore, you must configure a separate
class loader for Orchestration Designer applications to use Axis2 library effectively.
Perform the following steps for the additional WebSphere configuration:
Procedure
1. Open the WebSphere Administrative Console.
2. On the Environment menu, click Shared libraries and create a shared library.
3. Copy the following entries into the Classpath field:
${WAS_INSTALL_ROOT}/lib/ext/axiom-api-1.2.13.jar
${WAS_INSTALL_ROOT}/lib/ext/axiom-dom-1.2.13.jar
${WAS_INSTALL_ROOT}/lib/ext/axiom-impl-1.2.13.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-adb-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-adb-codegen-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-json-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-kernel-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-saaj-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-transport-http-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-transport-local-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/neethi-3.0.2.jar
${WAS_INSTALL_ROOT}/lib/ext/woden-api-1.0M9.jar
${WAS_INSTALL_ROOT}/lib/ext/woden-impl-dom-1.0M9.jar
${WAS_INSTALL_ROOT}/lib/ext/woden-tool-1.0M9.jar
${WAS_INSTALL_ROOT}/lib/ext/XmlSchema-1.4.7.jar
${WAS_INSTALL_ROOT}/lib/ext/VPWebServiceClient-<version>.jar
${WAS_INSTALL_ROOT}/lib/ext/VPAppLogClientWS_<version>.jar
You must modify the version for VPWebServiceClient -<version>.jar according to
the file deployed in the lib or ext directory.
4. Click Servers > Server Types > WebSphere application servers to navigate to the server
configuration page.
5. From the server list, select the server that you want to associate with the shared library.
6. Click Java and Process Management in Server Infrastructure section, and click the Class
Loader link.
7. Create a new class loader, and set the class loader order to Classes loaded with local
class loader first (parent last). Click OK.
8. Select the newly create class loader.
9. On the Configuration page, click the Shared library references link.
10. On the Configuration page, ensure that the shared library you created is selected.
11. Click OK to save the configuration.
12. Make sure you verify all the configuration has been saved, and restart the application server.
Best regards, k.Yamahara
|
|
[+]
Avaya Orchestration Designer
» runtimeconfig woluld not get license from WebLM, 26/04/2023 09:44:23
» Go to message
|
|
Hi Team,
Thank yo for your support.
Occurrence scenario
1.In the runtimeconfig management console, specify the license server as follows.
https://[IP of EPM]:8443/WebLM/LicenseServer
2. When I press update, the following error is output.
License Url is invalid, or server is not up, or license version is too low.
We deployed to use AAOD 8.1.2 with WebSphere v9.0.2 and Standalone webLM server 10.1.2.
In this configuration, AAOD 8.1.2 runtime config with WebSphere unable to reach WebLM server 10.1.2 for the runtime licenses with https.
But we confirmed AAOD 8.1.2 runtime config with WebSphere able to reach WebLM server 10.1.2 for the runtime licenses with http.
Furthermore we confirmed AAOD 8.1.2 runtime config with Tomcat able to reach WebLM server 10.1.2 for the runtime licenses with https.
We got below message in SystemErr.log when AAOD 8.1.2 runtime config with WebSphere unable to reach WebLM server 10.1.2 for the runtime licenses with https.
(java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available)
And we also got below message in License status for platform on Validation Page of OD.
Error :com.avaya.weblm.LicenseException: : Unable to create SSLContext
If my understanding is correct, the Java system is able to look into the trust store file trusted_weblm_certs.jks in the lib directory for the certificate on Tomcat.
Therefore we truyed to import “trusted_weblm_certs.jks” using IBM console on WebSphere.
And we also enable TLS setting using IBM console as well with below.
SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP) settings.
How can I resolve above error message? Please advise.
We are using this system with below products.
[[ EPM ]]
<swversion>
Avaya Connector Server
Version: RH8.4.64-AV04EP8
Offer Type: bundled
Operating System Version
Linux 4.18.0-372.26.1.el8_6.x86_64
<iaversion.php>
installagent 8.1.2.0.0202 full
docs 8.1.2.0.0202 full
vpms 8.1.2.0.0202 full
vpms 8.1.2.0.0341 patch
docs 8.1.2.0.0341 patch
<OVA for deploy>
ExperiencePortal-Primary-EPM-8.1.2.0.0202.ova
<Patches>
epavl-8.x.x.0.2210.tar.gz
EPM_8.1.2.0.0328.tar.gz
EPM_8.1.2.0.0341.tar.gz
[[ Web Application Server ]]
Orchestration Designer?08.12.11.01
JAVA?IBM Java V1.8.0
WAS?WebSphere Application Server V9.0.2.x
OS?RHEL8.1
Best regards, K.Yamahara
|
|
[+]
Avaya Orchestration Designer
» OD application cannot call AES connector, 26/04/2023 09:18:12
» Go to message
|
|
The attached file is our collected logs.
|
|
[+]
Avaya Orchestration Designer
» OD application cannot call AES connector, 26/04/2023 09:10:28
» Go to message
|
|
Occurrence opportunity
all the time
Occurrence scenario
1. The OD application calls aesconnector, so it accesses as follows. (The following is an excerpt from the OD log)
CTICommand.execute: request to manager is https://localhost:9443/aesconnector/CallInfoInitialCall?extension%3D59904&k=XHLGU0OPUf71kD9JCHrDHb96m9Ns8LQs
2. An SSL related error occured. Then the OD application cannot run with below exception.
[23/04/24 9:14:20:127 JST] 000c7d88 SystemErr R ***** Saw exception, tracing before report
[23/04/24 9:14:20:127 JST] 000c7d88 SystemErr R javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target
We would like to resolve above exception. So, please advice how should we any action.
Here after are our system deployments.
[[ EPM ]]
<swversion>
Avaya Connector Server
Version: RH8.4.64-AV04EP8
Offer Type: bundled
Operating System Version
Linux 4.18.0-372.26.1.el8_6.x86_64
<iaversion.php>
installagent 8.1.2.0.0202 full
docs 8.1.2.0.0202 full
vpms 8.1.2.0.0202 full
vpms 8.1.2.0.0341 patch
docs 8.1.2.0.0341 patch
<OVA for deploy>
ExperiencePortal-Primary-EPM-8.1.2.0.0202.ova
<Patches>
epavl-8.x.x.0.2210.tar.gz
EPM_8.1.2.0.0328.tar.gz
EPM_8.1.2.0.0341.tar.gz
[[ Web Application Server ]]
Orchestration Designer?08.12.11.01
JAVA?IBM Java V1.8.0
WAS?WebSphere Application Server V9.0.2.x
OS?RHEL8.1
Best regards, K.Yamahara
|
|
[+]
Avaya Orchestration Designer
» FileNotFoundException error occurd about xml-apis.jar that is not included in OD RuntimeSupport File, 26/04/2023 08:48:33
» Go to message
|
|
Occurrence scenario
1. After deploying the OD application to WebSphere, start the application.
2. The following exception was outputed to the FFDC log of WebSphere.
Exception:java.io.FileNotFoundException SourceId:com.ibm.ws.classloader.ClassLoaderUtils.addDependents ProbeId:246 Reporter:java.lang.Class@c0bc96c0
java.io.FileNotFoundException: /AP/IHS/htdocs/CCSWebServer11/runtimeSupport/xml-apis.jar
So, please advise below my inquiry.
1. In OD 07.00.18.01 environment, xml-apis.jar exists in runtimeSupport for WebSphere.
Is it a estimated results as design that does not exist in the environment of OD 08.12.11.01?
Does the occurrence of this exception affect the operation of the application?
2. If 1 has no effect, is there a way to make this exception go away?
3. Will this exception affect https communication, etc.?
We are using this system with below products.
[[ EPM ]]
<swversion>
Avaya Connector Server
Version: RH8.4.64-AV04EP8
Offer Type: bundled
Operating System Version
Linux 4.18.0-372.26.1.el8_6.x86_64
<iaversion.php>
installagent 8.1.2.0.0202 full
docs 8.1.2.0.0202 full
vpms 8.1.2.0.0202 full
vpms 8.1.2.0.0341 patch
docs 8.1.2.0.0341 patch
<OVA for deploy>
ExperiencePortal-Primary-EPM-8.1.2.0.0202.ova
<Patches>
epavl-8.x.x.0.2210.tar.gz
EPM_8.1.2.0.0328.tar.gz
EPM_8.1.2.0.0341.tar.gz
[[ Web Application Server ]]
Orchestration Designer?08.12.11.01
JAVA?IBM Java V1.8.0
WAS?WebSphere Application Server V9.0.2.x
OS?RHEL8.1
Best regards, K.Yamahara
|
|
[+]
Proactive Outreach Manager
» Inquiry regarding support policy for PostreSQL 9.6, 15/04/2021 01:19:42
» Go to message
|
|
Hi Mike-san,
Thank you for your support.
I correct my question as below.
Q2) Does AVAYA has plan to support the PostgreSQL11.x with POM3.x(3.1.2 or 3.1.3 or future version of 3.x)?
Because AVAYA doesn't release EO(M)S for POM3.x now.
It is very helpful to use POM3.x using customer.
Please advice.
K.Yamahara
|
|
[+]
Proactive Outreach Manager
» Inquiry regarding support policy for PostreSQL 9.6, 08/04/2021 20:21:59
» Go to message
|
|
Hi
Thank you for your reply.
I understood your explanation.
By the way, please advise below points.
----
POM 3.1.3 COMPATIBLE RELEASES
PostgreSQL 9.11.x
9.4.x
9.6.x
----
Q1) What is TPostgreSQL9.11.x? Is it special version for AVAYA products(POM, EP, etc,..)
So, there are compatible version for PostgreSQL9.11.x with POM3.1.3 as above.
However there is no 9.11.x information in postgresql.org.
---
https://www.postgresql.org/support/versioning/
Releases
Version Current_minor Supported FirstRelease FinalRelease
13 13.2 Yes September 24, 2020 November 13, 2025
12 12.6 Yes October 3, 2019 November 14, 2024
11 11.11 Yes October 18, 2018 November 9, 2023
10 10.16 Yes October 5, 2017 November 10, 2022
9.6 9.6.21 Yes September 29, 2016 November 11, 2021
9.5 9.5.25 No January 7, 2016 February 11, 2021
---
Q2) Does AVAYA has plan to support the PostgreSQL9.11.x for POM3.x(3.1.2 or 3.1.3 or future version of 3.x)?
Because AVAYA doesn't release EO(M)S for POM3.x now.
It is very helpful to use POM3.x using customer.
Best regards, K.Yamahara
|
|
[+]
JTAPI
» Can NOT success secure connection with AES, 08/04/2021 01:43:14
» Go to message
|
|
Hi Team,
When our Customer performed the "WAS" service restart with AESConnector on VM, it can NOT success secure connection with AES after start up it.
It can be logged-in to AES. Then they are going to change timeout timer to separate cause if AESConnector has.
So, please advise are there any timeout timer related secure connection Authentication?
Here after are AESConnector_trace.log.
29/03/2021 05:07:46:691 DEBUG - ProviderMonitor:AES#2 is not available
29/03/2021 05:07:54:691 DEBUG - ProviderMonitor: Checking:AES#1 for availability
29/03/2021 05:07:57:170 DEBUG - ProviderMonitor: Checking:AES#2 for availability
29/03/2021 05:07:57:170 DEBUG - ProviderMonitor:AES#2 is null in our list, attempt to reget
29/03/2021 05:07:57:325 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
29/03/2021 05:07:57:325 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
29/03/2021 05:07:57:325 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#KTAES2#CSTA-S#ACIKTAES02
29/03/2021 05:07:57:439 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained
29/03/2021 05:07:57:439 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: give provider cycles:40 of delay:100ms
29/03/2021 05:07:57:439 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is not in service -- STATE: 1, give small delay
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 13
29/03/2021 05:07:57:539 DEBUG - CTIConnectorManager.initProvider: setup named licensing.
29/03/2021 05:08:42:541 WARN - CTIConnectorManager.initProvider: problem with requestPrivileges; the version of AES may not support Named Licensing. (Exception - com.avaya.jtapi.tsapi.TsapiPlatformException: setPrivileges TSAPI failure: com.avaya.jtapi.tsapi.TsapiPlatformException: setPrivileges unexpected exception: com.avaya.jtapi.tsapi.TsapiPlatformException: no conf event)
29/03/2021 05:08:42:541 DEBUG - CTIConnectorManager.initProvider: Will retry with a non secure connection.
29/03/2021 05:08:52:753 ERROR - CTIConnectorManager.initProvider: provider:AES#2 is unavailable reason :com.avaya.jtapi.tsapi.TsapiPlatformException: no conf event
29/03/2021 05:08:52:753 INFO - CTIConnectorManager.ConfigureFromConfigurationFile: Configure failover servers and extensions.
29/03/2021 05:08:52:753 INFO - CTIConnectorManager.ConfigureFromConfigurationFile: Configure failover server provider name - AES#1
29/03/2021 05:08:52:753 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: Provider - AES#1 - already added.
29/03/2021 05:09:00:753 DEBUG - ProviderMonitor: Checking:AES#1 for availability
29/03/2021 05:09:03:215 DEBUG - ProviderMonitor: Checking:AES#2 for availability
Best regards, K.Yamahara
|
|