Can anyone explain the differences between NGXXJ and JLINK connectors? I am not finding any information in the documentation.

Much thanks!
Kyle

This message has been edited. Last edited by: Kerry,

Hi
Hope this helps
http://ibiweb.fau.edu/ibi_html.../client_settings.htm
I had to "GOOGLE" question, but it took me right tp the IBI site abd documentation.

Cheers
Rhonda
IBI_EDACONNECTOR = '{NGXXJ|JLINK}'

Is the type of client communication program being used to connect to the WebFOCUS Reporting Server.


NGXXJ - Implements the Java version of the default iWay connector. This is the default value.


JLINK - Implements the JLINK connector.


Note: This setting has no effect on the driver used by the Managed Reporting Realm Driver when it is configured to authenticate Managed Reporting users to the Reporting Server. The Realm driver always uses JLINK.

Rhonda, Thank you. I should have posted that I already found that in IBI's documentation. The problem is that there is no explanation about the difference between the two. I need to know why I would use JLINK over NGXXJ or NGXXJ over JLINK.

According to the WebFOCUS Security and Administration manual: "For more information, see the IBI_EDACONNECTOR setting's online help", wherever that is!

Let me look for an old problem that we encountered and w/the Distribtion server on AIX and Reporting server with MVS we had to change from JLINK to NGXXJ to fix the problem. I am sure the details are in there...

I don't have a full answer as to why we needed to change from JLINK to NGXXJ other than we were experiencing problems in both cases receiving a -12.
In one issue when a particuliar FOCEXEC was run on MVS with RCASTER on AIX. As it turned out the -12 was a symptom of the problem; miss match on the Loadlibs for their user COBOL functions.

In the other problem, we needed to change from JLINK to NGXX because we were upgrading from 5.3.3 on MVS to 7.2.5 full-function server and it was recommended that we use the NGXX with the IWAY Java connector and that corrected our other problem. We were experiencing JLINK errors.

Don't know if you found this link:
http://techsupport.information...ay/iway_tmo_028.html

"This document explains how to use the iWay Java Connector (jlink) in conjunction with a third-party Java Application to access data on a Full Function Server. To successfully use the distributed iWay Java Connector as an access junction to the vast list of adapters on the server..."

Not sure if I fully answered your question; I was new to the company at the time this problem arose. I just wanted to get it working.