Avaya(Non-java app) integration with ADF

Question

Hi,
We have a desktop application Avaya (non-Java) & want to integrate it with ADF. Currently we do it by passing parameters in HTTP URL. If the user clicks on a button in non-java app, it should:
(1) open search page of an ADF application and execute search.
(2) if the ADF application is already open, the button on Avaya app should execute search with partial page refresh. However, the whole page is being refreshed.
Can you please guide, how to do this with partial page refresh? , as the No 1 is almost achieved.
Thanks,
NC

Answer 1

Hi Shay,
Below Options were tried for integration. Please have a look at them and suggest if there is any other possible way to Integrate Avaya with ADF.
1) Calling ADF application with URL parameters.
Reasons to drop:
Every time a URL is called the entire page will get rendered again taking some 2-3 seconds which is very critical to the application.
ADF is capable of handling URL parameters without re-loading the whole page(http://oracamp.com/passing-parameters-adf-application-through-url). But we can't use this inbuilt way as we have many customized developments implemented in the page. This way directly works at AMImpl (at Model level) level. We want the events to be fired at View level. That is backing bean level.
2) Avaya is capable of dealing with ActiveX (OCX). They sent me 2 DLLs which handles communication between web page and Avaya application. A simulator was also sent (bundle attached herewith). The steps to be carried out for testing are-
Installation procedures:
i. Register the DTLCRMINT.ocx file. Start->Run-> Type the command
ii. regsvr32 <ocx file location>
iii. Register the DTLINTCMP.ocx file. Start->Run-> Type the command
iv. regsvr32 <ocx file location>
v. Double click on the Clinet.exe it would open up a windows application with a Textbox and Command button. Put In the data which needs to be sent.
vi. Open the CRM Page.html. On opening the OCX would be loaded by default.
vii. Now clicking the Send Data button on the client application, whatever information is there in the Client Text Box would be sent to the web page.
viii. From CRM side, the application needs to use the OCX provided, and must wait for the event. On receiving the event the data that is retrieved as a part of the event can be parsed to update the text box and click on the search button.
Reasons to drop:
It works fine with basic HTML page. But once integrated with ADF page as an inline frame it doesn't work. We tried to embed the OCX object inside <verbatim> tags, but was not successful. The event fired by ActiveX object is triggered at client side by VBScript function. Avaya's ActiveXs seem to be only working with VBScript according to my understanding. So there was no way for ADF to capture VBScript events.
ADF is capable of javascript up to some extent. To do a critical application like this, my feeling is javascript is never a good option.
3) To use a text file. Avaya writes, ADF application reads.
Reasons to drop:
ADF can read the text files with normal java IO methods. But only the server directories are visible. So, Avaya has to write the information in the server file. With using a parameter like user name, ADF application can read the file in regular time intervals (with using poll feature) and get relevant information and automatically run the search.
Initially the idea was to do this at client side. But since this is a web application, file reading at client side is next to impossible. Again when one side is reading and the other side is writing, file access violations may occur.
4) Another option is if Avaya can offer the value in a web service, the ADF application can get it.
Reasons to drop:
There may occur a latency as well as Avaya says they can't offer web services.
5) The ideal solution is, the ADF application's front end control's IDs can be provided. If the Avaya system is capable of accessing or getting hold of DOM and pushing the value to the controls and clicking the button; things would become pretty straight forward. JMeter works like this in testing J2EE applications.
Any Recommendations how can it be done .
Thanks.