| title | description | ms.date | ms.topic | author | ms.author | search.audienceType | ms.custom | |||
|---|---|---|---|---|---|---|---|---|---|---|
JavaDDA in Unified Service Desk | MicrosoftDocs |
The Java data-driven adapter (JavaDDA) uses the Java Access Bridge to automate Java applications. User Interface Integration (UII) supports Java Access Bridge 2.0.2. |
08/23/2017 |
article |
gandhamm |
mgandham |
|
|
The [!INCLUDEpn_Java] data-driven adapter (JavaDDA) uses the Java Access Bridge to automate [!INCLUDEpn_Java] applications. [!INCLUDEpn_user_inteface_integration_uii] supports Java Access Bridge 2.0.2. You can use tools such as Java Monkey and Java Ferret to understand the accessibility structure of the application. To use the DDA, you need to inspect the application using either of these tools, and build the bindings manually and feed them to the DDA using initstring.
The JavaDDA defines three control types: JAccControl, JAccSelector, and JAccTree. Each control tag must have a name attribute that specifies the name of the control used in [!INCLUDEpn_hosted_application_toolkit_hat]automation activities.
Note
[!INCLUDEpn_Java] Abstract Window Toolkit (AWT) applications are not fully supported in [!INCLUDEpn_hosted_application_toolkit_hat]. You must configure the AWT applications with the WinDDA and run them as regular Win32 applications. The WinDDA uses Microsoft Active Accessibility (MSAA) to access the applications controls. Some AWT controls might not be fully compatible with MSAA, so they may not function properly. The JavaDDA is not supported for [!INCLUDEpn_WinSer2008]. To access [!INCLUDEpn_Java] AWT controls, you can use tools such as Java Monkey and Java Ferret.
The following are the various JavaDDA tags:
Use Data Driven Adapters
WinDDA
WebDDA
UIADDA
[!INCLUDEfooter-include]