SAS Technical Support strongly recommends that you use Null Persistence as your preferred configuration when you use JBoss 4.3 EAP in a production environment. Choosing null-persistence offers the simplest solution with in-memory storage of queue data. The only real risk of losing data occurs when the middle-tier applications are shut down or they fail to function. In this situation, the system becomes inoperable. Therefore, loss of transient data on those queues is of less concern.

To configure messaging in order to use null persistence, follow these instructions:

Java Message System (JMS) Persistence Changes

1. Copy the null-persistence-service.xml file from the $JBoss-home-directory/docs/examples/jms/ directory to $your-SAS-server/deploy/jboss-messaging.sar.
2. Remove any other $your-database-persistence-service.xml files from the $your-SAS-server/deploy/jboss-messaging.sar directory.

JMS Messaging Authentication Changes

1. Create the following two files in the $your-SAS-server/conf/props directory:
   • messaging-users.properties
   • messaging-roles.properties
2. In both of the new files, add the following single line:
   guest=guest
3. In $your-SAS-server/conf/login-config.xml, replace the <application-policy> messaging stanza with the following:
   <application-policy name="messaging"> <authentication> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> <module-option name="unauthenticatedIdentity"> guest </module-option> <module-option name="usersProperties">props/messaging-users.properties</module-option> <module-option name="rolesProperties">props/messaging-roles.properties</module-option> </login-module> </authentication> </application-policy>

Operating System and Release Information