View Only
  • 1.  Auto-discovery, or pre-fill with an SQL query plugin?

    Posted Oct 19, 2007 08:32 PM
    Does auto-discovery work with an SQL query plugin?

    I created an SQL query plugin with

    <plugin type="autoinventory"/>

    The following properties where set in the plugin, jdbcUrl, jdbcDriver, jdbcUser, & jdbcPassword. I was hoping the plugin would be auto-discovered.
    It was not auto-discovered. I thought at least the values would be used to pre-fill the fields when the service was created manually. The fields were not pre-filled.

    I followed the instructions on

    The web states,
    Overriding the defaults will make it easier to configure your custom service and in the future could allow for auto-discovery.

    Is there a way to make auto-discovery or at least pre-fill work with an SQL plugin?


  • 2.  RE: Auto-discovery, or pre-fill with an SQL query plugin?

    Posted Oct 24, 2007 01:38 AM
    Currently, auto-discovery of the SQL Query server is not supported. That's something that could be easily added though. Can you describe your use case in a bit more detail?


  • 3.  RE: Auto-discovery, or pre-fill with an SQL query plugin?

    Posted Oct 24, 2007 05:20 PM
    Hi Ryan,

    The plug-in has the following properties.

    <config include="sql"/>

    <property name="jdbcUrl"

    <property name="jdbcDriver"

    <property name="jdbcUser"

    <property name="jdbcPassword"

    It would be ideal if the plugin was auto-discovered. Currently we go to the HQ dashboard, and click on the “New Platform Service” and then edit “Configuration Properties”. We manually fill in jdbcDrive, jdbcUser, jdbcUrl and jdbcPassword. All of this information is part of the plugin. Why do we have to enter the information when it is already in the plugin? Can the plugin be auto-discovered?

    The interesting part is the password. Many of our customers would not like there unencrypted database password in an xml file! We could supply a password, maybe it is valid, maybe it is dummy, or maybe it has read access only, if needed we could go through the GIU to enter the correct password. Is there a way that you could call one of our jars to get the password?

    Is this the info we were looking for?