Refer to the Exhibit.
Scenario : You have made the decision to migrate all your operations onto WebLogic Server. An
application has been chosen from each department for the initial phase of migration ?one from
each of Sales, Marketing, Accounts, and Customer Service. The applications will be deployed as
individual EAR files to a cluster of WebLogic Server 10.x instances, each with a pool of
connections to an Oracle 10g database that provides corporate and departmental data services.
The database team hopes to upgrade the database to use Oracle RAC (Real Application Clusters)
shortly, which will require you to configure multiple sets of connections. Connectivity to the existing
Service Engineer Dispatch system is via a JMS message bridge. When a service engineer calls in
with a report, a message is sent via JMS to the Customer Service application deployed in
WebLogic Server. The customer record in the Customer Service database must be updated with
details from the message. It is important that the message is not lost because the call
management system is not able to resend messages. To address this, the Customer
Service application is accessing a persistent JMS Queue using an XA compatible connection
factory.
The database security team insists that any use of the corporate Oracle database can be traced to
the individual user that made the request. How can this be achieved when using WebLogic JDBC
Data Sources?
A.
Set the Enable Credential Mapping property for the Data Source.
B.
Set Initial Capacity to zero, so each user creates a new connection.
C.
Set the value of user to {WLS_USER} in the Properties field.
D.
This can only be done using application code.
E.
This cannot be done because Data Sources connect using a single username.