Does oracle have any recommendations on how passivation should be configured with multiple Application Modules? Is it considered safe to use to use the same persistent objects for multiple Application Modules?
Background:
I have an application with two application modules. They are not nested.
One is for a DB2 database and the other is for an oracle database. I have configured them both to use an oracle database for passivation using the jbo.server.internal_connection and jbo.pcol.mgr properties (figuring out I needed that second one to prevent the DB2 AM from running DB2 sql against the oracle DB was a challenge).
Initially, I also tried specifying different names for each AM's persistent objects by setting the jbo.control_table_name, jbo.txn_seq_name, and jbo.txn_table_name properties. This resulted in the only one AM's objects being created the and the second AM failing when it tried to insert into its objects that did not exist. Is this expected behavior?
Not defining different names for the persistent objects and allowing both AM's to use the same default objects seems to work okay. It looks like I can expect the sequence to prevent anything from colliding or conflicting?