Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/WLS AppScoped DataSource"

m (Password Encryption Error)
m (Replacing page with '== How to use Application Scoped Data Sources in WebLogic with EclipseLink JPA ==')
Line 1: Line 1:
== How to use Application Scoped Data Sources in WebLogic with EclipseLink JPA ==
== How to use Application Scoped Data Sources in WebLogic with EclipseLink JPA ==
This how-to describes the use of application scoped data-sources within a WebLogic Application Server (version 10.3). These steps are necessary as the WebLogic container does not initialize application scoped data sources before the JPA bootstrapping is performed. Without these steps EclipseLink will be provided a null data-source and will throw an exception during its initialization.
The configuration involves a few simple configuration steps:
# Define the new data-source in a *-jdbc.xml configuration file. (EAR)
# Add the JDBC module to the WebLogic Application Configuration (EAR)
# Configure the JPA persistence unit to use the application scoped data source (EJB)
=== 1. DataSource Definition ===
An application scoped data source can be specified by providing a <name>-jdbc.xml file within the META-INF folder of your application's EAR. The following illustrates how the file might be defined. The important part of this configuration is the <scope>Application</scope> within the jdbc-data-source-params section.
The framework for the this <name>-jdbc.xml file can be generated by creating a globally scoped datasource on the WebLogic administration page, not associating it with a server and adding the <scope> element manually.
<source lang="xml">
<?xml version = '1.0' encoding = 'windows-1252'?>
<jdbc-data-source xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      <!-- For WebLogic 10.3 before load14 (Feb 2009) -->
      <!-- For WebLogic 10.3 post load14 (Feb 2009) must be transactional -->
      <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
=== WebLogic Application Configuration ===
In the EAR you will have /META-INF/weblogic-application.xml where the JDBC module needs to be defined. This simply registers the data source defined in step 1 for use in your application.
<source lang="xml">
=== JPA: persistence.xml ===
In the persistence.xml's definition of the persistence-unit you will need to specify an additional fully qualified '''"javax.persistence.jtaDataSource"''' property so EclipseLink can lazily look up the application scoped data source.
This additional property '''"java:/app/jdbc/SimpleAppScopedDS"''' is the workaround for the following issue [http://bugs.eclipse.org/246126 246126].  Please retain the original <jta-data-source> element for future compatability when this workaround is no longer required.
<source lang="xml">
<?xml version="1.0" encoding="windows-1252" ?>
<persistence xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
  version="1.0" xmlns="http://java.sun.com/xml/ns/persistence">
  <persistence-unit name="employee" transaction-type="JTA">
      <property name="eclipselink.target-server" value="WebLogic_10" />
      <property name="javax.persistence.jtaDataSource" value="java:/app/jdbc/SimpleAppScopedDS" />
In this example a JTA data source is being used so the property required is '''javax.persistence.jtaDataSource'''. If however you are using a non-jta-data-source then you should use the '''javax.persistence.nonJtaDataSource''' property to specify the JNDI name to use.
===Timeout or Data Source does not exist Error===
If you get a '''java.sql.SQLException: Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source Connection1 does not exist." in either EclipseLink, Kodo or OpenJPA then verify that your '''<driver-name>''' in your *jdbc.xml config is transactional.
===Password Encryption Error===
If you get the following '''invalid pad byte''' exception when deploying your EAR to WebLogic then check that you are using the latest ''AES'' encryption instead of ''3DES''.  You can regenerate your encrypted password by creating a temporary globally defined datasource and viewing the *jdbc.xml file generated on your domain config directory.
Feb 20, 2009 11:46:01 AM EST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1235148360979' for task '20'. Error is: 'com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.'
com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at com.rsa.jsafe.JA_PKCS5Padding.a(Unknown Source)
at com.rsa.jsafe.JG_BlockCipher.decryptFinal(Unknown Source)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:113)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
<source lang="xml">
Don't use
    <password-encrypted>{3DES}...=</password-encrypted> <!-- before load 12 -->
    <password-encrypted>{AES}...=</password-encrypted> <!-- after load 12 -->
*See [[EclipseLink/Examples/JPA/WebLogic_Web_Tutorial|WebLogic EAR Application Tutorial]] on the JPA examples page.
*Base bug for full fix in WebLogic Server release (Farallon 8b) is being tracked by [http://bugs.eclipse.org/246126 246126].

Revision as of 16:43, 24 March 2009

How to use Application Scoped Data Sources in WebLogic with EclipseLink JPA