Home > IT Answers > AS/400 > DB Triggers and JPA

Question

Asked: Nov 8 2007 4:27 PM GMT
Asked by: Rdgrimes

DB Triggers and JPA

iSeries, AS/400, JPA, Spring, XFire, Toplink, Triggers, SQL Anywhere Studio/M-Business Anywhere/Avantgo

I have a physical file/table, on an iSeries, into which I drop a record containing UserID and Password. This action in turn fires a trigger that ends up calling the api QSYGETPH to verify the user's login credentials. This has been working for years under our previous architecture, wherein we inserted the record via SQL from a "normal" java program.

However, we recently switched our middleware architecture to Spring/XFire, using JPA with Toplink. Now, the record gets inserted, but the trigger doesn't fire. I have tried this with dao.persist, EntityManager.createQuery, and EntityManager.createNativeQuery. In all instances, the record gets dropped into the file, but the trigger doesn't execute. Yet, if I create a record manually with a utility like wrkdbf, the trigger works fine on the file.

Any help would be greatly appreciated.

R. Grimes

Subscribe to Alerts! Get questions and answers delivered to your Inbox.

Help

Answer Wiki (Improve, edit or add to this answer)

IMPROVE THIS ANSWER

View History

RATE THIS ANSWER

0
Click to Vote:

Last Answered: Nov 8 2007 5:47 PM GMT by WaltZ400

Seems to me if the trigger is working using another program or utility it isn't the trigger program logic that is wrong.

I would check the authority you might be adopting in the new application to see if that is the cause. We use trigger programs here but they all run under adopted authority to a user with all object authority.

Browse more Questions and Answers on AS/400, Development and Database.

Looking for relevant AS/400 Whitepapers? Visit the Search400.com Research Library.

RSS - Discussions Help

Discuss This Answer

You must be logged-in to discuss a question. Log-in/Register

Rdgrimes | Nov 8 2007 9:26PM GMT

I’m using the same connection User ID and Password as worked on the old non-jpa architecture. Also, since I can see the record getting dropped into the database, there is obviously no problem with my write authority. It’s the db’s responsibility to detect a inserted record and fire the trigger. But, this is acting as though an insert via jpa is operating under stealth.

R. Grimes

Rdgrimes | Nov 9 2007 11:38PM GMT

I finally gave up on using a trigger program. Instead I decided to write a java class that uses ProgramCall from the com.ibm.as400.access package. I have ProgramCall execute an iSeries CLP program that, in turn, calls QSYGETPH and QSYRLSPH to validate the user credentials and return a valid/not valid flag. This seems to work just fine for what I’m doing.