webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

WmART and WmJDBCAdapter driver metadata retrieval

  • 1.  WmART and WmJDBCAdapter driver metadata retrieval

    Posted 29 days ago

    Hi,

    Does anyone know if there is a service or API call from these packages which retrieves the driver metadata (file, path, vendor, id, version, etc.) from a particular connection?

    I have to run a check on hundreds of Integration Servers and I'm trying to avoid to login in to each of their machines to check this info.

    Thank You.



    ------------------------------
    Gerardo Lisboa
    Information Logistics Strategist
    WRIGHTIA, SA
    Lisbon
    ------------------------------


  • 2.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 28 days ago

    Just to be sure: We are talking about the JDBC driver details and not the connection settings?



    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


  • 3.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 28 days ago

    Yes, it is about the database driver loaded by the IS, not the connection itself.

    Maybe it is available in the JVM related to the driver's loaded class?



    ------------------------------
    Gerardo Lisboa
    Information Logistics Strategist
    WRIGHTIA, SA
    Lisbon
    ------------------------------

    Original Message


  • 4.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 28 days ago
    Edited by Dave Laycock 28 days ago

    You could create an ExecuteService adapter service that calls a Java service

    The adapter service will have a $connectionName input parameter that you can set to the connection name(s) you care about.

    The Java service could contain code like this

    java.sql.Connection conn = (java.sql.Connection)IDataUtil.get(pipeline.getCursor(), com.wm.adapter.wmjdbc.services.ExecuteService.PIPELINE_CONNECTION);

    java.sql.DatabaseMetaData metaData = conn.getMetaData();


    String driverInfo = "JDBC Driver Information:\n";

    driverInfo += " Driver Name: " + metaData.getDriverName() + "\n";

    driverInfo += " Driver Version: " + metaData.getDriverVersion() + "\n";

    driverInfo += " Driver Major Version: " + metaData.getDriverMajorVersion() + "\n";

    driverInfo += " Driver Minor Version: " + metaData.getDriverMinorVersion() + "\n";

    + whatever info you want to collect


    You could remotely invoke this service.

    Maybe not a good fit, because you would need to deploy this code to your hundreds of Integration Servers




    ------------------------------
    Dave Laycock
    ------------------------------

    Original Message


  • 5.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 27 days ago

    Can you give some details on the bigger picture? What kind of access do you have to those machines?



    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


  • 6.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 25 days ago

    Hi,

    I do have full access to the command line but I would prefer to recover this in a programmatic way to integrate with an in-house auditing tool as I have hundreds of machines to analyse.

    Best regards,



    ------------------------------
    Gerardo Lisboa
    Information Logistics Strategist
    WRIGHTIA, SA
    Lisbon
    ------------------------------

    Original Message


  • 7.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 25 days ago

    note for a feature request: add this information to SPM+CCE.



    ------------------------------
    Gerardo Lisboa
    Information Logistics Strategist
    WRIGHTIA, SA
    Lisbon
    ------------------------------

    Original Message


  • 8.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 23 days ago
    Edited by Christoph Jahn 23 days ago

    I do have a few ideas, but there is not enough detail here yet. E.g. you mentioned Command Central. Does this mean that those machines are managed by Command Central? How is deployment of IS packages handled? Can stuff (whatever that would be) be deployed onto all those servers as part of the data gathering? What webMethods version? What OS? How is command line access granted (SSH key, username/password, etc.)? Are the machines on different environment types? Are the networks segregated or even air-gaped?

    Why is there interest in knowing the drivers per connection? This is something very different from just knowing what drivers are installed, which is more what I would have expected for auditing.

    In addition to the effort, when doing this manually, I would assume that auditors will not be happy about a manual approach. Plus you cannot simply repeat it next year.



    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


  • 9.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 14 days ago

    Hello,

    To simplify, let's assume everything is under RHEL, and using webMethods version 10.15 (the current LTS version), and that a central machine has full SSH access to all others, which is where all data gathering and deployment is made.

    As for auditing, everything must be known, and whereas the Java and DataDirect versions are under the platform control, other libraries (database, and others) are not, which is a knowledge gap when checking for updates and vulnerabilities.

    To make matters harder, not all developers document the libraries they use, which also adds to the maintenance chores (although this could be relaxed if the deployment is made using tools which keep a tally of all the included jars and make an SBOM out of it).

    Best regards,



    ------------------------------
    Gerardo Lisboa
    Information Logistics Strategist
    WRIGHTIA, SA
    Lisbon
    ------------------------------

    Original Message


  • 10.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 13 days ago

    Thanks for the details.

    Doesn't that change the requirement? In that the actual need is to know what additional libraries are deployed with packages?

    That is different from knowing, which jar a certain adapter connection is using.



    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


  • 11.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 13 days ago

    Hi,

    Well you're right, but it is just a slight change in the same problem category: identifying external resources. It usually boils down to identify jar files in use and recover their metadata.

    Best Regards,.



    ------------------------------
    Gerardo Lisboa
    Information Logistics Strategist
    WRIGHTIA, SA
    Lisbon
    ------------------------------

    Original Message


  • 12.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 13 days ago

    Try this   https://Your-Host:Your-Port/admin/jdbc/driver  or http://Your-Host:Your-Port/admin/jdbc/driver 

    https://docs.webmethods.io/on-premises/webmethods-integration-server/en/11.1.0/webhelp/index.html#page/pie-webhelp%2Fto-admin_api_2.html%23wwconnect_header

    All Administrator API requests and responses are described by an OpenAPI 3.0 document. This document can be obtained in the following ways:
    Requested from the API with GET /admin/swagger/integrationServer
    From the file system: Integration Server_directory\instances\instanceName\packages\WmAdmin\resources\wmadmin_swagger.json


    ------------------------------
    Developer EDI
    ------------------------------

    Original Message


  • 13.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 12 days ago

    That does not solve the issue of 3rd-party jar files. It lists the drivers (without version) for built-in JDBC pools of IS itself, but not WmART-based connections



    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


  • 14.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 12 days ago

    It gives me list of WmART-based connections related to JDBC , have you tried with your sever and port....it also provides a url to get some meta details as well



    ------------------------------
    Developer EDI
    ------------------------------

    Original Message


  • 15.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 11 days ago

    Well, this is what I get on a system that has no connections with JDBC adapter at all. So if on your system it also gives WmART-based connections, it seems to return both types. My (as it seems wrong) assumption had been that this service separates WmART and internal JDBC pools, as is usually the case.

    Can you post a screenshot what things look like on your end? Thanks.

    <BODY bgcolor="#dddddd">
<TABLE bgcolor="#dddddd" border="1">
<TR>
<TD valign="top"><B>driverAliases</B></TD>
<TD>
<TABLE>
<TR>
<TD><TABLE bgcolor="#dddddd" border="1">
<TR>
<TD valign="top"><B>name</B></TD>
<TD>MySQL Database Java Connector Driver</TD>
</TR>
<TR>
<TD valign="top"><B>url</B></TD>
<TD>http://localhost:5555/admin/jdbc/driver/MySQL+Database+Java+Connector+Driver/</TD>
</TR>
</TABLE>
</TD>
</TR>
<TR>
<TD><TABLE bgcolor="#dddddd" border="1">
<TR>
<TD valign="top"><B>name</B></TD>
<TD>Embedded Database Driver</TD>
</TR>
<TR>
<TD valign="top"><B>url</B></TD>
<TD>http://localhost:5555/admin/jdbc/driver/Embedded+Database+Driver/</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
</BODY>


    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


  • 16.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 11 days ago

    I guess it gives a combination of wm art connection and wm art jdbc connections,  you can still get some more data opening the url in screen shot.



    ------------------------------
    Developer EDI
    ------------------------------

    Original Message


  • 17.  RE: WmART and WmJDBCAdapter driver metadata retrieval

    Posted 12 days ago

    Well, then why not just write a small shell script that gathers those data? You can distribute with `scp`, run it with `ssh`, and collect back the results with `scp`.



    ------------------------------
    All the best,
    Christoph
    ------------------------------

    Original Message


Related Content