Switch To Different Schema Connection With Existing Application

Question

Hi,
Currently, i want to connect my existing application to a different schema, how should i do it?
The situation is that i have two schema(call Database Connection in JDeveloper) that have exactly the same structure, as one is duplicated from anothe. My purpose of doing this is to use one of the schema for daily operation, while the other for testing.
I have tried with this method:
1. Right click on the Business Component project node and select Edit Business Component Project.
2. In the Connection Tab, i change the Connection Name to the new schema(which used for testing).
3. Then i open my .jsp page and sad to see the it's still retrieving data from the old schema.
Am i hitting it with the wrong tactic? Please lemme know if there's any way that i can solve my problem.
Thanks,
Sin Leng

Answer 1

Hi,
The code snippet provided above must be executed whenever an ApplicationModule is first used by a new session but only after
that ApplicationModule has been connected (otherwise the connection will not be available). Depending upon the type of client that
you are developing (Swing vs. servlet for example) the right place to put this code could vary. Further, if your ApplicationModule
and/or connection is pooled you must also be careful to reset this information whenever an ApplicationModule is serially reused
by different clients.
As of 9.0.3, the BC4J framework has provided a single hookpoint for all clients to manage session context on the middle tier. The
method is oracle.jbo.server.ApplicationModuleImpl.prepareSession(Session). This method is invoked whenever a session
(represented by a SessionCookie in the BC4J framework) uses an ApplicationModule which it had not referenced from a previous
request. The Session parameter is the ApplicationModule session context which BC4J will automatically update with the
userData context of the client side SessionCookie before prepareSession(Session) is invoked. This makes custom, client
side context available to the midtier. Further this method is invoked after BC4J has connected the ApplicationModule, so it is a safe
hookpoint for initializing custom DB session context as well as MT session context.
In order for BC4J to make the client side SessionCookie userData context availabe in prepareSession
the SessionCookie userData context must have been set before SessionCookie.useApplicationModule has been invoked. Please see
the javadoc for SessionCookie.getUserData() and or the pooling sample ($JDEV_HOME/BC4J/samples/Pooling) for more information
about acquiring a SessionCookie reference programmatically (so that you can initialize the SessionCookie userData). Other options
may be to set up the userData in a custom SessionCookieFactory. Please see the pooling sample for a sample custom
SessionCookieFactory implementation.
Hope this helps.
JR