Maak een bestand datasource.properties die je database toegang bevat en

gebruik onderstaande springframework configuratie.

Zo kan je in ontwikkeling je lokale verbinding gebruiken en eens onder jboss gebruikt je applicatie de gedefiniëerde jndi name.

een voorbeeld config xml definition :

<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="http://www.springframework.org/schema/p"
xmlns:aop="http://www.springframework.org/schema/aop" xmlns:context="http://www.springframework.org/schema/context"
xmlns:jee="http://www.springframework.org/schema/jee" xmlns:tx="http://www.springframework.org/schema/tx"
xsi:schemaLocation="

http://www.springframework.org/schema/aop

http://www.springframework.org/schema/aop/spring-aop-2.5.xsd

http://www.springframework.org/schema/beans

http://www.springframework.org/schema/beans/spring-beans-2.5.xsd

http://www.springframework.org/schema/context

http://www.springframework.org/schema/context/spring-context-2.5.xsd

http://www.springframework.org/schema/jee

http://www.springframework.org/schema/jee/spring-jee-2.5.xsd

http://www.springframework.org/schema/tx

http://www.springframework.org/schema/tx/spring-tx-2.5.xsd">

<!-- your local connection config -->

<context:property-placeholder location="classpath:props/datasource.properties"/>

<!-- your local datasource -->

<bean id="local.datasource"
class="org.springframework.jdbc.datasource.DriverManagerDataSource"
p:driverClassName="${dataSource.driverClassName}"
p:url="${dataSource.url}"
p:username="${dataSource.username}"
p:password="${dataSource.password}"
/>

<!-- jndi lookup as configured in jboss datasource.xml will be picked up , when not present defaults to your local datasource -->

<jee:jndi-lookup id="jndi.datasource" jndi-name="${dataSource.jndiname}"
default-ref="local.datasource" />
</beans>


<!– A security constraint that restricts access to the HTML JMX console
to users with the role JBossAdmin. Edit the roles to what you want and
uncomment the WEB-INF/jboss-web.xml/security-domain element to enable
secured access to the HTML JMX console. –><

<security-constraint>
<web-resource-collection>
<web-resource-name>HtmlAdaptor</web-resource-name>
<description>An example security config that only allows users with the
role JBossAdmin to access the HTML JMX console web application
</description>
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>JBossAdmin</role-name>
</auth-constraint>
</security-constraint>

<login-config>
<auth-method>BASIC</auth-method>
<realm-name>JBoss JMX Console</realm-name>
</login-config>

<security-role>
<role-name>JBossAdmin</role-name>
</security-role>

2. Bewerk serverdefaultdeployjmx-console.warWEB-INFjboss-web.xml en haal <security-domain> uit commentaar:

<jboss-web>
<!– Uncomment the security-domain to enable security. You will
need to edit the htmladaptor login configuration to setup the
login modules used to authentication users.–>
<security-domain>java:/jaas/jmx-console</security-domain>
</jboss-web>

3. Bewerk serverdefaultconfpropsjmx-console-roles.properties

4. Bewerk serverdefaultconfpropsjmx-console-users.properties

5. Voor het beveiligen van de web-console vind je de respectievelijke files in

• serverdefaultdeploymanagementconsole-mgr.sarweb-console.warWEB-INFweb.xml
• serverdefaultdeploymanagementconsole-mgr.sarweb-console.warWEB-INFjboss-web.xml
• serverdefaultdeploymanagementconsole-mgr.sarweb-console.warWEB-INFclassesweb-console-roles.properties
• serverdefaultdeploymanagementconsole-mgr.sarweb-console.warWEB-INFclassesweb-console-users.properties

6. Een restart van JBoss kan nodig zijn om de wijzigen door te voeren.