I configured everything well, at least I think. I did a test is generated so that a critical event and then I tried to see if the event had been written about DB2, but it did not work.
I tried looking at the log file:
and find a common mistake:
013-02-06T10:14:37: Error: E-GJA-000-000: ngjava: G_JDBC: pool-1-thread-15: java.sql.SQLException: Simulated transaction error
* at com.ibm.tivoli.netcool.integrations.jdbc.GWJdbcNullPreparedStatement(GWJdbcNullPreparedStatement.java:595)*
* at com.ibm.tivoli.netcool.integrations.jdbc.GWJdbcBatchProcessor(GWJdbcBatchProcessor.java:491)*
* at com.ibm.tivoli.netcool.integrations.jdbc.GWJdbcBatchProcessor(GWJdbcBatchProcessor.java:323)*
* at java.util.concurrent.ThreadPoolExecutor$Worker(ThreadPoolExecutor.java:897)*
* at java.util.concurrent.ThreadPoolExecutor$Worker(ThreadPoolExecutor.java:919)*
* at java.lang.Thread(Thread.java:736)*
How can I fix?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-02-13T13:04:01Z by ChristianSmith
Pinned topic Gateway JDBC don't write
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-13T13:04:01Z at 2013-02-13T13:04:01Z by ChristianSmith
ChristianSmith 270001FRB32 PostsACCEPTED ANSWER
Re: Gateway JDBC don't write2013-02-13T13:04:01Z in response to SystemAdminYou've not configured your Gate.Jdbc.Driver property to point to the DB2 driver class. You're currently using the default built in Null JDBC driver, which simply discards all it's data and simulates errors. It's used internally for testing.
The manual gives details and examples, including example settings for DB2: