Try the latest OD 8.1.21101 with the latest POM PDC 4.0.2.147. It works for me.

Hi. The flow is fine, I see the 'getVars' Data node (containing the 'Get Contact Info') before the servlet and the 'INTRO' Announce node after the servlet to trace the "pominfo" variable.

- Concerning the Dynamic Attributes from the POM, take a look at

https://www.devconnectprogram.com/forums/posts/list/20106.page


- Concerning the 'pominfo' values, it sounds weird that on the trace, you got 'ContactNumber' and 'PrimaryPomServer' properly populated, 'FirstName', 'LastName' and 'PhoneNumber1' empty with no error message. Let me investigate a bit.

Ok, thanks. So the default pominfo data were not totally populated.

- I see you are using the latest OD 8.1.2 . But which POM release are you trying to connect ? What POM PDC are you using ?

- Try to add a Data node prior to calling the servlet with a 'getContactInfo:dynamicAttributes' from the palette then check if the default pominfo data is being populated.

Hi.

- Might you add additional info/a screenshot to clarify what you are trying to do ?

- Did you successfully drag/drop the 'Add Contact Info' item into a Data node ? First name and Last Name variables you mentioned are there.

- Do you see any error message on the OD 'Error Log' tab od the 'Console' tab ? Did you enable the trace on the OD and get any error message ?

Thanks Raymond for getting the trick after investigating in your environment (I just provided a few tips).

Let me recap what happened for all members/visitors facing the same issue.

This is an error message received at runtime (com.avaya.sce.runtimecommon.SCERuntimeException: Module "SF_TMI_GetTINModule" was not accessable in the development environment at code generation time. Unable to determine the input parameters for the dialog).

Nevertheless the upgrade worked cleanly, some issues raised referencing files from the old installation. There were some referenced libraries from the old installation and the new one (I mean the upgraded one) inherited this code, so the new one had some bad references related to the application server (ex. Apache Tomcat) causing some code becoming inaccessible (in this specific case an RDM).

How to fix :
Try to make a clean copy of the OD application server directory from the original installation and put that into your upgraded workspace. Then take a look at your app server library directory (ex. <TOMCAT_HOME>/lib) to see if there are old libraries (.jar files) that were being referenced. If yes, clean that up, rebuilt and things should work as expected.

Sorry for inconvenience. Please, read carefully the first post in this thread

"
Bug in the AOD release 8.1.2
...
The fix will be included in future OD releases (this means OD releases > 8.1.2, the OD 8.1.2 does not come with this fix)
...
"

so the fix does not come with the release 8.1.2 (the latest one available at this very moment) but it will be included in future OD releases (> 8.1.2).

You can

- install the patch manually on the OD 8.1.2; for this, please open a Devconnect technical support ticket: https://www.devconnectprogram.com/technicalTicket/create ;

- work with a previous OD release not affected by this bug (ex. 8.1.1);

- wait for the next release (I have no timeline/deadline for that).

Hi.

My only Java installed on the system (see attached picture).

Sometimes there are problems using different Java distributions: they are officially fully compatible but maybe one or more .jar file is/files are not updated.

My tip:
Try to always use the same Java: the host on which OD is running, the OD when designing then building apps, the server on which the platform EP is running on.

Same for the app server when possible:
The OD can only use the Apache Tomcat coming with the .iso file for simulation, anyway you can use the same Tomcat release with the platform EP (otherwise, pay attention when you export the runtimeconfig files and the project .war file to select the appropriate app server to be used with the EP).

Hi.

This issue sounds weird.

I tested a Menu node in a brand-new app created on a brand-new OD 8.1.2 with Java 11 (I used Azul Zulu that is a distribution of OpenJDK) in the Menu node but I had no problem with the grammar, it works as expected and it appears as expected (no line feeds or blank spaces).

Might you provide some details (also screenshots are fine) to reproduce the same problem in my environment ? I read 'custom grammar'. Did you test an external grammar in a development 's environment ?

Hi Matthew.

Maybe the issue was caused by the TSAPI. Might you kindly check for the TSAPI version in your AES/CTI connector ?

You can retrieve this value in the 'aesconnector.war' file

1. Download the war file

2. Unzip the war file

3. Find ecsjtapia.jar in the WEB-INF/lib folder.

4. Extract 'ecsjtapia.jar'

5. Unzip 'ecsjtapia.jar'

6. Edit 'META-INF/MANIFEST.MF'

7. Look for Implementation-Version or something that looks like a build version.


Ex.

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.13
Implementation-Title: ecsjtapia
Implementation-Version: 8.1.3.6.0.8
Built-By: Avaya
...

in this case the TSAPI version is 8.1.3.6.0.8

Hi. I see just warnings on Tomcat logs, no error messages.

While upgrading, did you move from Log4j to Log4j2 ?
Note: If I remind fine, the OD 8.1.0 was still using the old Log4j, Log4j2 was introduced in the OD 8.1.1

If the answer to the above question is YES:

- make sure you are using the proper '.properties' file or the '.xml' file. Log4j2 supports
'.properties' files but they have changed the property syntax. You can check the official
documentation

https://logging.apache.org/log4j/2.0/manual/configuration.html#Properties

it covers all you need to create new configuration.


- check if, while your code does not use Log4j 1.x, your legacy libraries do.

- make sure the logj4.properties or the log4j2,xml is the classpath

Hi.

Take a look at this thread

https://www.devconnectprogram.com/forums/posts/list/20941.page#p148981

here developers stated as follows
"
We use ANT scripts. There are no plans for OD to support Maven.
"

Avaya is not investing in the Apache Maven built tools at this time.
Feel free to search the web for how to use the Apache Maven in place of the Apache Ant, anyway Devconnect cannot provide any tip/help/support.

" I was told that the log4j needs to be updated in 8.1.1 and I either need to copy in a log4j1-2 or upgrade to 8.1.2 .... "

Correct, anyway I always suggest to use a fresh stand-alone OD 8.1.2 (no need to install).


UUI:
Did you try the Consultation call (see the attached picture) ?
Picture to show you the consultation item:

Hi.


" CTIConnectorManager.setTServerWait: TServer wait time is 4 ... CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0) "

It sounds as the AES/CTI connector is unable to retrieve the configurations from 'ddconfig' for some reason.

- Did you recently upgrade the OD ?
If the answer is YES, did you follow instruction on these docs

https://www.devconnectprogram.com/fileMedia/download/5dd0af54-c2cd-4ab0-9efd-62f131665917 on page 3

https://www.devconnectprogram.com/fileMedia/download/58dcf8ac-9a55-4ada-8bbe-a0e3d114527f on page 31

"After upgrading Orchestration Designer, you must update to connectors or other dependant
libraries on the application server. You must update the connector applications
icconnector.war and aesconnector.war, and run-time support files runtimeSupport platform.zip ."

Any chance to see what happens with a fresh installation of the latest OD 8.1.2 ?



- what are the current releases of the OD, the AES/CTI connector and the AES ?

- You already set "debugLevel"=7 in your 'tsapi.pro' file.
Might you try as follows

a) Take a look at the "tsapi_trace.txt" for the start up attempt. The exact error message should be visible;

b) Set debugLevel back to 0 in your "tsapi.pro" when done.

"tsapi_trace.txt" usually resides in your Tomcat root dir.
In the "tsapi.pro" file, the 'altTraceFile' needs to be configured in order to collect the tsapi tracing
associated with the client libraries such as JTAPI and CTIConnector. There isn't any default
location or name for the trace file, so you have to specify the absolute path (full path).


- Please, double-check on the "tsapi.pro" file if a valid path was configured. I see on your file

altTraceFile=tsapi_trace.txt

Is that correct ? Remember to use the forward slash in the path name for all operating systems.

Example:
altTraceFile=C:/temp/tsapi_trace.txt

For more information on JTAPI tracing reference the JTAPI programmer's guide (https://download.avaya.com/css/public/documents/100068966)

Hi Mauricio.

I'm not aware of a similar issue, I never faced a blank URL from time to time before.

- ' Is there any patch for this ?'

You can see the list of the latest patches in the Release Notes under the section 'Features'
(latest 8.1.2 https://www.devconnectprogram.com/fileMedia/download/7f9d1a31-af5a-4a2f-8349-324faf7976f8 on pages 2 and 3).

- 'What log are you referring to?'

Firstly, test with the OD simulator (before exporting the .war file) and check the console log (see the attached picture) to see what is happening


- We need to clarify the behavior. Please, on the OD, try as follows

Configure the URL and save, then reopen the Eclipse and check the URL.

Does the issue happen in this case ? Does the URL get blank ?


- Did you strictly follow the 'Web Service' section of the Developer's Guide for the OD 8.1.0 ( I mean with format and input parameter)?

Here https://www.devconnectprogram.com/fileMedia/download/c16fa671-5ae8-4902-9e33-c1912c6a3f6a starting from page 320

Hi Mauricio.

- What is your exact release ? 8.1.0 ?

- Does " the configured URLs for the REST web services get lost" mean you see a blank URL from time to time ? Does this happen randomly or just after something specific (ex. OD reboot) ?

- Any error on logs ? Did you enable the trace (in the OD designer the trace is a bit different compared to the EP execution platform) ?