IPD Error

 4 Replies
 0 Subscribed to this topic
 45 Subscribed to this forum
Sort:
Author
Messages
Sameera
Advanced Member
Posts: 30
Advanced Member
    Getting the following error when trying to connect to the 'SQL Query' node in IPD, Any idea to sort this issue ?

    SQL Ver - SQL 2008 R2

    Activity started: Start  (Run Id: 1)
    Executing Start Activity...
    Variables in Process:

    Activity completed: Start

    Activity started: SQLQuery1540  (Run Id: 1)
    SQL Query SQLQuery1540: Query string SELECT * FROM LTM2.EMPLOYEE
    SQL SQLQuery1540: Using JDBC connection String Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver, URL: jdbc:sqlserver://BI3-LTMTEST:1433;databaseName=LTM, User: LTMuser
    SQL Query SQLQuery1540: Query string SELECT * FROM LTM2.EMPLOYEE
    SQLQuery1540_RETURN_MSG = SQL SQLQuery1540: JDBC Driver com.microsoft.jdbc.sqlserver.SQLServerDriver not found in classpath. Please add jdbc driver to Lawson Process Server classpath.
    SQLQuery1540_RETURN_CODE = -1
    Variables in Process:
    lastReturnMessage = SQL SQLQuery1540: JDBC Driver com.microsoft.jdbc.sqlserver.SQLServerDriver not found in classpath. Please add jdbc driver to Lawson Process Server classpath.
    lastErrorCode = 1
    lastOutputData = java.lang.Exception: SQL SQLQuery1540: JDBC Driver com.microsoft.jdbc.sqlserver.SQLServerDriver not found in classpath. Please add jdbc driver to Lawson Process Server classpath.
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgSQL.executeQuery(FgSQL.java:455)
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgaSQLQuery.startActivity(FgaSQLQuery.java:115)
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgActivity.execute(FgActivity.java:742)
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgProcess.run(FgProcess.java:2178)
    at com.lawson.bpm.designer.runtime.LocalFlowRunner.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

    lastInformationCode = -1

    Thanks
    Sameera
    Srini Rao
    Veteran Member
    Posts: 149
    Veteran Member
      Why you are using the SQL Query node? I prefer to use Landmark Transaction node.
      Woozy
      Veteran Member
      Posts: 709
      Veteran Member
        Sameera - Based on the error, it appears that IPA can't find the driver in the classpath.  If you are running the flow locally in IPA designer, you need to point to the driver on your local machine via Designer preferences under "External Jars".  If you are running it on the server, you need to make sure the drivers are included in the server classpath - unfortunately, I can't guide you on the server side stuff.

        Srini Rao - I use SQL extensively in my flows, particularly flows that are "batch" rather than "action" related.  SQL provides much greater performance and flexibility when using multiple tables with complex join relationships, and it is possible to perform logic within the query itself rather than querying the data and then manipulating with javascript.  The filter functionality within Landmark nodes is painful and can be deadly slow in some cases.  I use Landmark nodes if I am querying a single business class, performing an update, or querying for derived fields that are difficult to duplicate using SQL. It's just a matter of determining which node works best for the situation.
        Kelly Meade
        J. R. Simplot Company
        Boise, ID
        Sameera
        Advanced Member
        Posts: 30
        Advanced Member
          Hi Srini

          Thanks for the reply. I also prefer to use SQL node because of the flexibility compared to Transaction node


          Thanks
          Sameera
          Sameera
          Advanced Member
          Posts: 30
          Advanced Member
            Hi Kelly

            Thanks a lot for the info. I also agree with you regarding the SQL node. It's very easy to work with it.

            I tried following discussion & it works for me. 

            https://www.lawsonguru.co...low/ipa-sqlqry-node/
            (refer document shared by Dave Lis)

            Thanks
            Sameera