Sure, just be sure all your file names are like xxx-service.xml. You can also put both db configs in one db2-service.xml file
david jencks On 2002.07.09 10:15:23 -0400 [EMAIL PROTECTED] wrote: > Hi > > I'm trying to deploy multiple db2 services using JBoss 3.0.0 > > When I copy the example db2-service.xml and drop it into the deploy > directory everything is ok > > > <?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> > > <mbean code > ="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name > ="jboss.jca:service=LocalTxCM,name=DB2DS"> > > <!-- 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=DB2DS</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=DB2DS"> > > <attribute name="JndiName">DB2DS</attribute> > <attribute name="ManagedConnectionFactoryProperties"> > <properties> > <config-property name="ConnectionURL" type > ="java.lang.String">jdbc:db2:mydatabase</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">myuser</config-property> > <config-property name="Password" type > ="java.lang.String">mypassword</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=DB2DS"> > <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:name=JaasSecurityManager</depends> > > <attribute name > ="TransactionManager">java:/TransactionManager</attribute> > <!--make the rar deploy! hack till better deployment--> > <depends>jboss.jca:service=RARDeployer</depends> > </mbean> > </server> > > > I then take another copy of this file and change it as per the following > (changing the DB2DS to MYDS) > > <?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> > > <mbean code > ="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name > ="jboss.jca:service=LocalTxCM,name=MYDS"> > > <!-- 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=DB2DS</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=MYDS"> > > <attribute name="JndiName">MYDS</attribute> > <attribute name="ManagedConnectionFactoryProperties"> > <properties> > <config-property name="ConnectionURL" type > ="java.lang.String">jdbc:db2:anotherdatabase</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">myUser</config-property> > <config-property name="Password" type > ="java.lang.String">myPassword</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=MYDS"> > <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:name=JaasSecurityManager</depends> > > <attribute name > ="TransactionManager">java:/TransactionManager</attribute> > <!--make the rar deploy! hack till better deployment--> > <depends>jboss.jca:service=RARDeployer</depends> > </mbean> > </server> > > > > When I deploy this i get a message > > " [MainDeployer] Deployment of package: > file:/tmp/install/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/test.xml > is waiting for an appropriate deployer." > > > Is it possible to deploy multiple database services in this way and if so > what am I doing wrong? > > Any help would be appreciated > > > Ian > > > > > > > > > > This E-mail transmission may contain confidential or legally privileged > information that is intended for the addressee only. Any views or > opinions > presented are solely those of the author and do not necessarily represent > those of CNM Limited. If you are not the intended recipient you are > hereby > notified that any disclosure, copying, distribution or reliance upon the > contents of this E-mail is strictly prohibited. If you have received this > E-mail transmission in error, please notify the sender immediately, so > that > CNM Limited may arrange for its proper delivery. Please then delete the > message from your inbox. > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Stuff, things, and much much more. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
