Message |
[+]
Avaya Orchestration Designer
» Missing variables after upgrade, 13/02/2018 13:39:41
» Go to message
|
|
Hi,
I'm upgrading from EP 7.0.1.0.1601 to EP 7.2.0.0.1117 and noticed that some menus doesn't work anymore. Looking at trace.log I assume that it is the same problem as described in https://www.devconnectprogram.com/forums/posts/list/20504.page where some project variables relating to the menu is missing.
Probably not a new problem, I have looked back at old repositories and for an example menu_1416 is missing back already in VoicePortal 5.1 but for some reason it seems to have worked anyway.
I have tested to recreate the menus and that takes care of the problem.
So, my question isn't about the cause of the problem. It is more "is there a way to find these menus with missing variables other than manually go through all 100 applications"?
(I have another problem regarding prompts, but I'll take that in a separate thread when I have investigated it further)
|
|
[+]
Avaya Orchestration Designer
» getAbsoluteWEBINFPath, 12/02/2018 10:09:17
» Go to message
|
|
42 is the answer to Life, the Universe and Everything! :-)
Old installation:
OD 7.0.1.0804
EP 7.0.1.0.1601
Java 7
New installation:
OD 7.2.0.00904
EP 7.2.0.0.1117
Java 8
So here's the thing: we have a module called AvayaCentralizedOpeningHours (ACOH), built in EP/OD 5.00.15.05.
If I install a web server (Tomcat) with Java 8 and runtime files from EP 7.0 ACOH works.
If I install a web server with Java 8 and runtime files from EP 7.2 ACOH stops working with an error referencing NoSuchMethodError -> getAbsoluteWEBINFPath
If I open a servlet in OD 7.0 and start typing mySession.getAbsoluteWE.... Eclipse suggests that there is a method called getAbsoluteWEBINFPath.
If I do the same in OD 7.2 Eclipse doesn't show that method, so I assume that it is removed?
One way to solve this is to continue to run the app servers with 7.0 runtime files (and continue to use OD 7.0) but that kind of removes the whole idea of upgrading. Any other ideas of solving it?
|
|
[+]
Avaya Orchestration Designer
» getAbsoluteWEBINFPath, 12/02/2018 04:29:30
» Go to message
|
|
Hi,
We are upgrading from EP7.0 to 7.2 and planned to continue to use Java 7 on the application servers. Unfortunatelly that didn't work, we're having problems with configurable variables so we have upgraded to Java 8 which solved the CAV problem.
That introduced another problem though.
We are using an old APS developed module called AvayaCentralizedOpeningHours, and when we use that with Java 8 we get the error java.lang.Exception: java.lang.NoSuchMethodError: com.avaya.sce.runtimecommon.SCESession.getAbsoluteWEBINFPath()Ljava/lang/String; (repeated 1000 times per call; then the application stops).
Any suggestions?
|
|
[+]
Avaya Orchestration Designer
» EP Upgrade + VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2(), 08/02/2018 10:48:56
» Go to message
|
|
Found the problem, too old Java version on the application server!
|
|
[+]
Avaya Orchestration Designer
» EP Upgrade + VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2(), 08/02/2018 04:17:18
» Go to message
|
|
Hi,
It was a little bit premature to say that you saved my day... :-)
We reconfigured EP with ConfigureLegacyTLS.sh but it still doesn't work.
Attached is the trace.log from the application, and I changed vpAppLogClient to log Debug instead of warning, also attached.
/// Anders
|
|
[+]
Avaya Orchestration Designer
» EP Upgrade + VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2(), 06/02/2018 02:07:49
» Go to message
|
|
Thank's! You saved my day!
:-)
|
|
[+]
Avaya Orchestration Designer
» EP Upgrade + VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2(), 05/02/2018 14:00:19
» Go to message
|
|
|
|
[+]
Avaya Orchestration Designer
» REST Web service endpoint and password, 10/11/2015 10:29:40
» Go to message
|
|
Hi,
I have a REST web service, and I want to change the endpoint URL and password (basic auth).
Where and how do I do that?
Best regards
Anders
|
|
[+]
Avaya Orchestration Designer
» Web service changing server IP, 28/10/2015 11:04:00
» Go to message
|
|
Can I edit web.xml directly, or will it be overwritten?
|
|
[+]
Avaya Orchestration Designer
» Web service changing server IP, 28/10/2015 08:23:22
» Go to message
|
|
Hi,
I have an application with a web service which uses a web service with server IP 172.16.219.161
That server is going to be replaced by another server, so I have changed the old IP to a new in the wsop files.
If I search for the old IP after changing the wsop (and updating context and Regenerate Project) the old address is still there in WEB-INF/src/connectivity/ws/beans/Service1.wsdl and in web.xml
Should I be worried about that, or is it just old rubbish that never clears out?
|
|
[+]
Avaya Orchestration Designer
» Issue playing 10 minutes announcement, 27/10/2015 07:53:35
» Go to message
|
|
If I were you I should check what connectionTimeout in server.xml (in the folder ../Tomcat/conf ) is set to.
I think the standard is 20 seconds, and after that Tomcat think that the connection is dead.
|
|
[+]
Avaya Orchestration Designer
» long phrases causes error in the application., 19/05/2014 03:46:26
» Go to message
|
|
This is maybe a little bit late, but check the setting for connectionTimeout in server.xml
Example:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
In this case you can get problems if you play a single wav file that is longer than 20 seconds.
|
|
[+]
Avaya Orchestration Designer
» Errors in WSDL, 26/02/2014 06:21:41
» Go to message
|
|
Hi,
After creating a Axis2 web service from the attached WSDL I get the following two errors in Eclipse:
org.apache.asiomom.OMElement.Factory cannot be resolved
The method serialize(OutputStream, OMOutputFormat) in the type OMNode is not applicable for the arguments (QName, OMFactory, MTOMAwareXMLStreamWriter)
Any suggestions what I can do about it?
|
|
[+]
Avaya Orchestration Designer
» null pointer exception with breakpoint, 04/02/2014 02:07:12
» Go to message
|
|
|
|
[+]
Avaya Orchestration Designer
» Application name not updated, 03/02/2014 14:54:57
» Go to message
|
|
Found it!
It's META-INF/context.xml that is out of sync, and if I change the application name there and regenerate the project everything works again.
No idea why this has happened, but my guess would be that it is an old application, first developed by APS some 5 years ago and then we have exported and imported it several times (and most likely with different installations of Eclipse).
|
|