Hi,
yes, i deployed the datasource. This is the content of the datasource.
my db2-service.xml
<?xml version="1.0" encoding="UTF-8"?>
| <!-- ==================================================================== -->
| <!-- ConnectionManager setup for default IBM DB2 -->
| <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
| <!-- ==================================================================== -->
| <server>
| <!-- Database Connection for ISIP Database -->
| <mbean
code="org.jboss.resource.connectionmanager.LocalTxConnectionManager"
name="jboss.jca:service=LocalTxCM,name=DB2ISIPDS">
| <!-- Include a login module configuration named DB2DbRealm.
| Update your login-conf.xml, here is an example for a
| ConfiguredIdentityLoginModule:
|
| <application-policy name = "DB2DbRealm">
| <authentication>
| <login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
| <module-option name =
"principal">yourprincipal</module-option>
| <module-option name =
"userName">yourusername</module-option>
| <module-option name =
"password">yourpassword</module-option>
| <module-option name =
"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DB2ISIPDS</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
| NOTE: the application-policy name attribute must match SecurityDomainJndiName, and
the
| module-option name = "managedConnectionFactoryName"
| must match the object name of the ConnectionManager you are configuring here.
| -->
| <!--uncomment out this line if you are using the DB2DbRealm above
| <attribute
name="SecurityDomainJndiName">DB2DbRealm</attribute>
| -->
| <depends optional-attribute-name="ManagedConnectionFactoryName">
| <!--embedded mbean-->
| <mbean code="org.jboss.resource.connectionmanager.RARDeployment"
name="jboss.jca:service=LocalTxDS,name=DB2ISIPDS">
| <attribute name="JndiName">DB2ISIPDS</attribute>
| <attribute name="ManagedConnectionFactoryProperties">
| <properties>
| <config-property name="ConnectionURL"
type="java.lang.String">jdbc:db2:isip2</config-property>
| <config-property name="DriverClass"
type="java.lang.String">COM.ibm.db2.jdbc.app.DB2Driver</config-property>
| <!--set these only if you want only default logins, not through JAAS -->
| <config-property name="UserName"
type="java.lang.String">my db-user</config-property>
| <config-property name="Password"
type="java.lang.String">my db-user-pw</config-property>
| </properties>
| </attribute>
| <!--Below here are advanced properties -->
| <!--hack-->
| <depends
optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper</depends>
| </mbean>
| </depends>
| <depends optional-attribute-name="ManagedConnectionPool">
| <!--embedded mbean-->
| <mbean
code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool"
name="jboss.jca:service=LocalTxPool,name=DB2ISIPDS">
| <attribute name="MinSize">0</attribute>
| <attribute name="MaxSize">50</attribute>
| <attribute name="BlockingTimeoutMillis">5000</attribute>
| <attribute name="IdleTimeoutMinutes">15</attribute>
| <!--
| criteria indicates if Subject (from security domain) or app supplied
| parameters (such as from getConnection(user, pw)) are used to distinguish
| connections in the pool. Choices are
| ByContainerAndApplication (use both),
| ByContainer (use Subject),
| ByApplication (use app supplied params only),
| ByNothing (all connections are equivalent, usually if adapter supports
| reauthentication)-->
| <attribute name="Criteria">ByContainer</attribute>
| </mbean>
| </depends>
| <depends
optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
| <depends
optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
| <attribute
name="TransactionManager">java:/TransactionManager</attribute>
| <!--make the rar deploy! hack till better deployment-->
| <depends>jboss.jca:service=RARDeployer</depends>
| </mbean>
|
|
| <!-- Database Connection for PSM Database -->
| <mbean
code="org.jboss.resource.connectionmanager.LocalTxConnectionManager"
name="jboss.jca:service=LocalTxCM,name=DB2PSMDS">
| <!-- Include a login module configuration named DB2DbRealm.
| Update your login-conf.xml, here is an example for a
| ConfiguredIdentityLoginModule:
|
| <application-policy name = "DB2DbRealm">
| <authentication>
| <login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
| <module-option name =
"principal">yourprincipal</module-option>
| <module-option name =
"userName">yourusername</module-option>
| <module-option name =
"password">yourpassword</module-option>
| <module-option name =
"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DB2PSMDS</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
| NOTE: the application-policy name attribute must match SecurityDomainJndiName, and
the
| module-option name = "managedConnectionFactoryName"
| must match the object name of the ConnectionManager you are configuring here.
| -->
| <!--uncomment out this line if you are using the DB2DbRealm above
| <attribute
name="SecurityDomainJndiName">DB2DbRealm</attribute>
| -->
| <depends optional-attribute-name="ManagedConnectionFactoryName">
| <!--embedded mbean-->
| <mbean code="org.jboss.resource.connectionmanager.RARDeployment"
name="jboss.jca:service=LocalTxDS,name=DB2PSMDS">
| <attribute name="JndiName">DB2PSMDS</attribute>
| <attribute name="ManagedConnectionFactoryProperties">
| <properties>
| <config-property name="ConnectionURL"
type="java.lang.String">jdbc:db2:psm</config-property>
| <config-property name="DriverClass"
type="java.lang.String">COM.ibm.db2.jdbc.app.DB2Driver</config-property>
| <!--set these only if you want only default logins, not through JAAS -->
| <config-property name="UserName"
type="java.lang.String">db2admin</config-property>
| <config-property name="Password"
type="java.lang.String">db2admin</config-property>
| </properties>
| </attribute>
| <!--Below here are advanced properties -->
| <!--hack-->
| <depends
optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper</depends>
| </mbean>
| </depends>
| <depends optional-attribute-name="ManagedConnectionPool">
| <!--embedded mbean-->
| <mbean
code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool"
name="jboss.jca:service=LocalTxPool,name=DB2PSMDS">
| <attribute name="MinSize">0</attribute>
| <attribute name="MaxSize">50</attribute>
| <attribute name="BlockingTimeoutMillis">5000</attribute>
| <attribute name="IdleTimeoutMinutes">15</attribute>
| <!--
| criteria indicates if Subject (from security domain) or app supplied
| parameters (such as from getConnection(user, pw)) are used to distinguish
| connections in the pool. Choices are
| ByContainerAndApplication (use both),
| ByContainer (use Subject),
| ByApplication (use app supplied params only),
| ByNothing (all connections are equivalent, usually if adapter supports
| reauthentication)-->
| <attribute name="Criteria">ByContainer</attribute>
| </mbean>
| </depends>
| <depends
optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
| <depends
optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
| <attribute
name="TransactionManager">java:/TransactionManager</attribute>
| <!--make the rar deploy! hack till better deployment-->
| <depends>jboss.jca:service=RARDeployer</depends>
| </mbean>
| </server>
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133119#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...