2  modify    hibernate config file  hibernate.cfg.xml

                     <property name="hibernate.connection.datasource">data  source  jndi</property>
                    <property name="hibernate.connection.username">name</property>
                     <property name="hibernate.connection.password">password</property>
                     <property name="hibernate.session_factory_name">HibernateSessionFactory</property>  
                      <property name="connection.autocommit">false</property>
                    <property name="net.sf.hibernate.transaction.JTATransactionFactory">net.sf.hibernate.transaction.WebSphereTransactionManagerLookup</property>
                      <property name="show_sql">false</property>
                     <property name="dialect">org.hibernate.dialect.Oracle9Dialect</property>

              注意：如果是非事务性数据源  那么在hibernate.cfg.xml  必须设置 <property name="connection.autocommit">false</property>
                      为false
                           
     3   create  datasource   jndi  on  was
             如果是非事务性数据源，在建立数据源时，也要设置为非事务性数据源。
      4    config  custom service  bean  on Websphere
             was console >servers> application server > server1>manage>custom service >new
       5 start Server

// Allow to use ibm jdk extensions
grant codeBase "file:${was.install.root}/java/ext/-" {
permission java.security.AllPermission;
};
// Allow to use ibm tools
grant codeBase "file:${was.install.root}/java/tools/ibmtools.jar" {
permission java.security.AllPermission;
};
// Allow to use sun tools
grant codeBase "file:/QIBM/ProdData/Java400/jdk14/lib/tools.jar" {
permission java.security.AllPermission;
};
// Allow to use sun tools (V5R2M0 codebase)
grant codeBase "file:/QIBM/ProdData/OS400/Java400/jdk/lib/tools.jar" {
permission java.security.AllPermission;
};
// WebSphere system classes
grant codeBase "file:${was.install.root}/plugins/-" {
permission java.security.AllPermission;
};
grant codeBase "file:${was.install.root}/lib/-" {
permission java.security.AllPermission;
};
grant codeBase "file:${was.install.root}/classes/-" {
permission java.security.AllPermission;
};
// Allow the WebSphere deploy tool all permissions
grant codeBase "file:${was.install.root}/deploytool/-" {
permission java.security.AllPermission;
};
// Allow the WebSphere deploy tool all permissions
grant codeBase "file:${was.install.root}/optionalLibraries/-" {
permission java.security.AllPermission;
};
// Allow Channel Framework classes all permission
grant codeBase "file:${was.install.root}/installedChannels/-" {
permission java.security.AllPermission;
};
grant codeBase "file:${user.install.root}/lib/-" {
permission java.security.AllPermission;
};
grant codeBase "file:${user.install.root}/classes/-" {
permission java.security.AllPermission;
};

如果节点上有一些服务器程序需要许可权，而这些许可权在 server.policy 文件和 server.policy 文件中未定义为缺省值，那么更新 server.policy 文件。缺少许可权将创建 java.security.AccessControlException 异常。缺少的许可权在异常数据中列示。


然后重新启动服务器

The createEJBStubs tool

Even though the Just-In-Time deployment feature will, in many cases, dynamically generate the RMI-IIOP stub classes that are required for invocation of remote EJB interfaces, there remain some cases where these stub classes are not dynamically generated. For EJB 3.0 clients not running inside a WebSphere feature-pack-upgraded web container, EJB container, or client container, it is necessary for you to generate the stub classes with the createEJBStubs tool, then make the generated stubs available in the client environment's classpath. Typically you would accomplish this by copying the generated stubs to the location where the client's business interface class resides.

To summarize, the createEJBStubs tool must be used to generate client-side stubs for the following environments:

* "Bare" Java SE clients, where a Java SE JVM is the client environment
* WebSphere Application Server container environments without the EJB 3.0 feature pack applied
* Non-WebSphere application server environments