# Jython Script to read Internal Database using javadocs

**URL:** <https://forum.inductiveautomation.com/t/jython-script-to-read-internal-database-using-javadocs/86777>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [March 4, 2024, 4:51pm UTC](https://forum.inductiveautomation.com/t/jython-script-to-read-internal-database-using-javadocs/86777 "2024-03-04T16:51:27Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![tyler.bennett](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tyler.bennett](https://forum.inductiveautomation.com/u/tyler.bennett)\
**Post date:** [October 29, 2025, 8:06am UTC](https://forum.inductiveautomation.com/t/jython-script-to-read-internal-database-using-javadocs/86777/17 "2025-10-29T08:06:54Z")

</div>

Thanks to all who contributed in this thread.  
The clues herein led me to develop a solution (unsupported as it may be) for reading all properties for existing devices (Ignition v8.1). Posted here:

> [@How to read properties of existing device connection - Example Code](https://forum.inductiveautomation.com/t/how-to-read-properties-of-existing-device-connection-example-code/111772):
>
> I had often been disappointed that not all device connection properties for existing devices were easily available through supported scripting (system.device.listDevices()) . I recently had cause to develop a methodology to create/update/remove devices, UDTs (definitions/instances), tags and tag alarms based on an Excel workbook. Without scripted access to device connection properties it was difficult to determine whether a device required an update so I dug in and finally found a way to retriev…

---

_[View the full topic](https://forum.inductiveautomation.com/t/jython-script-to-read-internal-database-using-javadocs/86777)._