Installation

With the free open source application server JBoss and the free open source database MySQL on Windows, you can install RADRunner as follows:

Some versions (3.2.4 and 3.2.5) of JBoss have a bug that prevents RADRunner from executing (technical details). JBoss versions 3.2.3 and earlier are OK, but those are longer available on the JBoss web site. Hence we recommend that you return to an earlier version of JBoss, 3.0.8, which we currently use for production installations, or a version higher than 3.2.6RC2.

1. Download JBoss, and unzip to install (typically into C:\JBoss)
2. Download MySQL, and double-click to install (typically into C:\mysql)
   Make sure to choose a Max version, since RADRunner uses database transactions
3. Download a recent JDBC driver for MySQL, and extract from the zip the file mysql-connector-java-*-bin.jar into C:\JBoss\server\default\lib
   Make sure that the file is placed directly in this folder, and not into a sub-folder created by the unzip utility
4. Double-click on install_radrunner.bat to create a database and install RADRunner to JBoss
   This script carries out the following actions:
   • Create a MySQL database called radrunner with no username and password
   • Install a MySQL data source in JBoss
   • Deploy RADRunner to JBoss

To start JBoss, and hence the RADRunner application, double-click on radrunner.bat. Once JBoss has fully initialized, a message of the form "Started in Nm:NNs:NNNms" will appear in the JBoss console window. You will then be able to access the RADRunner login page by entering into a browser the following URL:

http://localhost:8080/radrunner/RMLogin.jsp

To stop JBoss, close the JBoss console window.

To avoid the need for a JBoss console window, you can install JBoss as a Windows Service. First set a Windows environment variable JBOSS_DIST to your JBoss installation folder via Start/Settings/Control Panel/System/Advanced/Environment Variables. Then download one of the many free service creation tools available (for example, ServiceInstaller), and use it to create a service with the following settings, replacing the variables enclosed in % marks with the appropriate environment variable values on your system:

With IBM WebSphere and DB2 on Windows, you can install RADRunner as follows:

1. Use DB2 Control Center to create a database in DB2, noting a user/password combination for it
2. Use the WebSphere Administrator's Console to create an application server with the following Java Virtual Machine (JVM) system properties (replace all text in <> with your own text):
   • com.rolemodellers.jdbc.url=jdbc:db2://<server name>/<DB2 database name>
   • com.rolemodellers.jdbc.driver=COM.ibm.db2.jdbc.net.DB2Driver
   • com.rolemodellers.jdbc.username=<DB2 database username>
   • com.rolemodellers.jdbc.password=<DB2 database password>
   • com.rolemodellers.jdbc.useClob=true
   • com.rolemodellers.jdbc.maxPlaywrightLength=1000000
   • com.rolemodellers.jdbc.useCreateTableAppendText=false
   • com.rolemodellers.rim.mappingModel=http://localhost/radrunner/castor/mappingModel.xml
   • javax.naming.Context.INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
   • java.naming.provider.url=iiop://<server name>:900
   • java.security.policy=<RADRunner installation package>\SecurityPolicy\rm.policy
3. Extract radrunner.ear, and use the WebSphere Administrator's Console to install it to this application server
   • When prompted for a Data Source, use any - SampleDataSource, for instance. Nothing will be written there.
   • There is no need to re-generate deployment code - you can specify either Yes or No when prompted.

You will then be able to access the RADRunner login page by entering into a browser the following URL:

http://localhost/radrunner/RMLogin.jsp

Note that this configuration is using DB2 to store application data.  Your IBM licence may or may not cover this usage of DB2, so it is necessary to check before installing RADRunner in a production environment with the above configuration. You may prefer to use a different database.

if you are running a different operating system from Windows, the only change required to the above configurations is to set the Application Directories appropriately (the default values are Windows-specific).

If you wish to use a different application server from those above, or have other requirements (such as to use an HTTP proxy server, or to configure Java 2 security more precisely), see the detailed instructions given below which cover the more general case.

We have tried to make the RADRunner installation instructions as helpful and comprehensive as possible. Any feedback will be welcomed - either positive or negative. In particular, we would be interested to hear of people's experiences with deploying RADRunner on other application servers than the ones above.

RADRunner requires a database which supports:

• Some form of long text data type
• Transactions.

Long Text Support

Transaction Support

RADRunner provides 2 options for using a relational database. Both of these require some system properties to be specified - see System Properties for details of how to do this.

Firstly, you can specify that RADRunner should bypass the application server and access the database directly. This is done via the system properties:

1. com.rolemodellers.jdbc.useInternalConnectionPool=true
2. com.rolemodellers.jdbc.driver=databaseDriverClassName
3. com.rolemodellers.jdbc.url=databaseUrl
4. com.rolemodellers.jdbc.username=databaseUsername
5. com.rolemodellers.jdbc.password=databasePassword

In this case, RADRunner implements its own internal connection pooling and transaction management, and any database driver and application server can be used. There is no performance or security penalty to using this approach, but it means that the standard J2EE configuration mechanisms for the data source are not available via the application server. RADRunner can still be used to configure some basic parameters, via the system properties:

1. com.rolemodellers.jdbc.connectionTimeout=timeoutInMilliseconds
2. com.rolemodellers.jdbc.connectionPoolInitialSize=initialSize
3. com.rolemodellers.jdbc.connectionPoolReapInterval=reapConnectionsEverySoManyMilliseconds
4. com.rolemodellers.jdbc.transactionManagerReapInterval=reapTransactionsEverySoManyMilliseconds

If this approach is used, configure settings via the relational database management system itself, not the application server. With DB2, for instance, it may be necessary to increase both the maximum number of agents on the instance and maximum number of applications on the database, depending on how heavy the usage is from RADRunner.

This approach is the default, and is recommended with WebSphere.

Secondly, a Data Source can be set up in your application server, and its JNDI name referenced from RADRunner. This is only recommended with application servers where the Transaction Manager can be accessed via JNDI (such as, for example, JBoss and WebLogic). The approach will also work with WebSphere, for example, but is not recommended since the implementation is necessarily low-level and may not be portable across different versions of the application server.

However, RADRunner creates transactions which span multiple servlet requests, and this is only possible if:

1. Your database driver supports JDBC 2. The recent releases of most major databases do this.
   
   and
   
   
2. The transaction manager implementation in your application server allows a suspended transaction to be resumed by a different thread. This is not mandated by the Java Transaction API specification - however, it is supported by JBoss and some versions of WebSphere, for example.

If you are not sure about either of these with your database and application server, please contact us for support.

All that is required in RADRunner to set up this first option is to assign the system property com.rolemodellers.jdbc.dataSource to the JNDI name of your Data Source - see System Properties for details of how to do this.

The means of setting up a Data Source is specific to your application server. With JBoss, an appropriately customised XML file should be placed in the deploy directory. With WebSphere, it can be done from the administration console.

However RADRunner accesses the database, it uses a single table to store all data. The default format of this table is:

  CREATE TABLE RM_PLAYWRIGHT_OBJECT (
    RMPO_WORLD VARCHAR(100) NOT NULL,
    RMPO_ID VARCHAR(41) NOT NULL,
    RMPO_NAME VARCHAR(100) NOT NULL,
    RMPO_CLASS_ID VARCHAR(41),
    RMPO_CLASS_NAME VARCHAR(100),
    RMPO_SUPERCLASS_ID VARCHAR(41),
    RMPO_SUPERCLASS_NAME VARCHAR(100),
    RMPO_EMAIL VARCHAR(100),
    RMPO_PASSWORD VARCHAR(100),
    RMPO_TYPE VARCHAR(100) NOT NULL,
    RMPO_PLAYWRIGHT CLOB(100000) NOT NULL,
    RMPO_CREATED TIMESTAMP NOT NULL,
    RMPO_LAST_UPDATED TIMESTAMP NOT NULL
    )

The name of this table, the column prefix, names of all the columns, and the lengths of most columns can be specified using the system properties:

  com.rolemodellers.jdbc.table
  com.rolemodellers.jdbc.columnPrefix
  com.rolemodellers.jdbc.worldColumn
  com.rolemodellers.jdbc.idColumn
  com.rolemodellers.jdbc.nameColumn
  com.rolemodellers.jdbc.classIdColumn
  com.rolemodellers.jdbc.classNameColumn
  com.rolemodellers.jdbc.superclassIdColumn
  com.rolemodellers.jdbc.superclassNameColumn
  com.rolemodellers.jdbc.emailColumn
  com.rolemodellers.jdbc.passwordColumn
  com.rolemodellers.jdbc.typeColumn
  com.rolemodellers.jdbc.playwrightColumn
  com.rolemodellers.jdbc.createdColumn
  com.rolemodellers.jdbc.lastUpdatedColumn
  com.rolemodellers.jdbc.maxWorldLength
  com.rolemodellers.jdbc.maxNameLength
  com.rolemodellers.jdbc.maxEmailLength
  com.rolemodellers.jdbc.maxPasswordLength
  com.rolemodellers.jdbc.maxPlaywrightLength

It is also possible to control database-specific aspects of the table creation via the system properties:

  com.rolemodellers.jdbc.useCreateTableAppendText
  com.rolemodellers.jdbc.createTableAppendText

If com.rolemodellers.jdbc.useCreateTableAppendText is set to true, the value of com.rolemodellers.jdbc.createTableAppendText is appended to the SQL CREATE TABLE statement. For example, with MySQL com.rolemodellers.jdbc.createTableAppendText can be set to "Type = InnoDB" in order to enable transaction support (with the Max version of MySQL). You can also use this setting to specify such details as the tablespace to be used, disk quotas, block size, and so on.

Alternatively, you can create the table yourself outside of RADRunner, in order to exercise full control over its properties - file placement, for example. If you create the table itself, it is advisable to create:

• a unique index on the id column
• a non-unique index on the email and password columns

Otherwise RADRunner will create the table and indexes the first time it starts up, using the defaults assigned to the schema with which it accesses the database.

See System Properties for details of how to set up all the above system properties, and I/O Bottlenecks for some guidelines on setting up a database for RADRunner.

Download the software from the GigaSpaces web site instead of from Sun.

JSpaces requires by default that the following downloadable jars (which it supplies) will be available on your HTTP server under directory lib (e.g., at URL http://localhost:8080/lib):

• GigaRayTrace-dl.jar
• GigaSpaces-ext-dl.jar
• JSpaces-dl.jar
• create-dl.jar
• jini-examples-dl.jar
• mahalo-dl.jar
• reggie-dl.jar
• space-examples-dl.jar

It is also necessary to add the GigaSpaces file JSpaces-dl.jar to the EAR file (without a path).

This replaces the need to make the JSK downloadable jars available via HTTP.

It is necessary to explicitly create a JavaSpace before starting RADRunner, using the supplied utility createSpace. The name of the space should then be assigned to the RADRunner system property com.rolemodellers.rim.worldName - the default assumed by RADRunner is RoleModellers.

This is not necessary with the JSK, which creates a JavaSpace of the name that you specify when the services are initialized.

It is necessary to start the GigaSpaces server before starting RADRunner. This can be done either by executing a command line, or (on Windows) by setting up the GigaSpaces server to run as an operating system service.

With the JSK, the RMI daemon must be started from the command line to run the services.

RADRunner loads various classes dynamically, so it is necessary to enable Java 2 Security. You must specify a security policy file somewhere on your network. This could be based on an example file supplied with the application server - for example, WebSphere supplies the file WebSphereInstallationRoot\properties\java.policy.  Alternatively, a sample security policy file rm.policy which could be used with either JBoss or WebSphere is included in the RADRunner installation package, under directory SecurityPolicy.

If you are using Jini, it is necessary to ensure that the security policy file for the application server grants the necessary permissions to the Jini codeBase (on top of any default permissions that should be granted for that application server). Then include in the file the following additional lines:

    grant codeBase "${com.rolemodellers.jini.codeBase}/-" {

        permission java.security.AllPermission;

    };




grant {

    permission java.net.SocketPermission "${com.rolemodellers.jini.codeHost}:*",
"connect,accept,resolve";

    permission java.net.SocketPermission "127.0.0.1:*",
"connect,accept,resolve";

    permission java.io.FilePermission "${com.rolemodellers.rim.logPath}/-",
"read,write,delete";

    permission java.io.FilePermission "${com.rolemodellers.rim.sessionPath}/-",
"read,write,delete";

    permission java.io.FilePermission "${com.rolemodellers.rim.outPath}/-",
"read,write,delete";

    permission java.io.FilePermission "${com.rolemodellers.rim.inPath}/-",
"read,write,delete";

};

Various system properties must be set in the JVM of the application server on which RADRunner is deployed. This can be done in one of 2 ways:

1. In the application server itself, by adding properties of the form -DpropertyName=propertyValue to the command line. It  may also be possible to specify system properties from a dialog within the administration console (as with WebSphere). If this approach is taken, the application server configuration should be exported and backed up for future use - for example, with WebSphere this can be done via the tool XMLConfig.
2. By editing the EAR file. The EAR contains a file radrunner-ejb.jar, which itself contains a properties file, com/rolemodellers/openapi/RMRimProperties.properties.  This approach would allow the updated EAR to be deployed on multiple application servers in the same environment with minimum additional effort.
   
   If you wish to use the second approach, it will be necessary to edit radrunner.ear.  This can be done with any common zip file tool - on Windows, you could use WinZip, for example. Open radrunner.ear, then open the file radrunner-ejb.jar within it. Extract RMRimProperties.properties into a new, empty directory on your hard disk - a sub-directory com\rolemodellers\openapi will be created by the extraction process, and the file placed in it.  Leaving radrunner-ejb.jar open, edit the file to set properties as required. Then add the original directory you created to radrunner-ejb.jar - with WinZip you would use the command "Add with wildcards" with "Include subfolders" checked, and specify a filename of *.*.  This will ensure that the properties file has the correct path inside the jar. Close radrunner-ejb.jar, choosing "Yes" when asked if you wish to update radrunner.ear, then close radrunner.ear.

The properties that must be set are all those specified in DATABASE (if you are using a database persistence option),  JINI (if you are using a Jini persistence option) and APPLICATION DIRECTORIES, plus:

1. proxySet, proxyHost and proxyPort:
   If no HTTP proxy is used on your network, make proxySet=false, and do not set proxyHost and proxyPort.
   If an HTTP proxy is used on your network, make proxySet=true and set proxyHost and proxyPort appropriately.
   
2. The JNDI properties for the application server you wish to use - for example:
   (with WebSphere)
   javax.naming.Context.INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
   java.naming.provider.url=iiop://<server name>:900
   (with JBoss)
   java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
   java.naming.provider.url=jnp://localhost:1099
   java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
   
   If these are not set appropriately for your application server, RADRunner will not be able to look up references via JNDI (for example, to EJBs or Data Sources), and you will not be able to log in. Make sure that any JNDI properties not appropriate to your application server are deleted or commented out in the EAR file.  

Other properties that may need to be set are:

1. If you wish to change the default name of your Playwright world from "RoleModellers", set com.rolemodellers.rim.worldName=worldName.
2. com.rolemodellers.rim.bossEmail and com.rolemodellers.rim.bossPassword, to change the default username and password for the Boss user from the standard values.
3. log4j.configuration, if you wish to customise the logging carried out by RADRunner and the application server does not itself use log4j (see Logging) 

If you are using Jini, you may need to set further properties for Java 2 Security:

1. If Java 2 security is not enabled by default in the application server, set java.security.manager (no value required).
2. java.security.policy=policyFileLocation (a file path relative to the working directory of the application server). If the security policy file is placed under \\myServer\rim as suggested above, set this working directory to \\myServer\rim, and policyFileLocation to the name of the policy file created (e.g., rm.policy).
3. In certain application servers, other properties may also be required to enable Java 2 security - for instance, with WebSphere it is also necessary to specify enableJava2Security=true and was.home=WebSphereInstallationRoot.

With regard to these latter security properties, note that in certain application servers it is necessary to specify security settings in the command line that starts up the application server JVM, rather than in the EAR or via an administration console. With JBoss, for example, a line such as the following could be added to the standard bin directory file run.bat:

set JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager -Djava.security.policy=\\serverName\rim\rm.policy -Dcom.rolemodellers.jini.codeBase=http://serverName:serverPort/jini -Dcom.rolemodellers.jini.codeHost=serverName -Dcom.rolemodellers.jini.worldHost=serverName

Such a line should be executed just before the application server is started - for instance, in the JBoss run.bat file it should be added just before the line:

%JAVA% %JAVA_OPTS% -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %ARGS%

The remaining system properties found in com/rolemodellers/openapi/RMRimProperties.properties are optional, and control a variety of settings ranging from the transaction timeout to the number of items displayed at a time in different web pages:

# RADRunner JVM System Properties File

# The default configuration is a Windows installation with database persistence on JBoss with no HTTP proxy.
# You may need to over-ride, change, enable, or disable the following properties before deployment.

# File system locations for Role-Interaction Machine I/O
com.rolemodellers.rim.logPath=C:\\radrunner\\rim\\log\\
com.rolemodellers.rim.sessionPath=C:\\radrunner\\rim\\session\\
com.rolemodellers.rim.outPath=C:\\radrunner\\rim\\out\\
com.rolemodellers.rim.inPath=C:\\radrunner\\rim\\in\\

# The URL prefixes by which these locations can be accessed via HTTP -
# replace "localhost:8090/rim" with your host name, port and path
com.rolemodellers.rim.logUrlPrefix=http://localhost:8090/rim/log/
com.rolemodellers.rim.sessionUrlPrefix=http://localhost:8090/rim/session/
com.rolemodellers.rim.outUrlPrefix=http://localhost:8090/rim/out/
com.rolemodellers.rim.inUrlPrefix=http://localhost:8090/rim/in/

# Snapshot access protocol
com.rolemodellers.rim.snapshotProtocol=file

# Persistence - database
com.rolemodellers.rim.persistenceMechanism=Jdbc
com.rolemodellers.jdbc.useInternalConnectionPool=true
com.rolemodellers.jdbc.username=
com.rolemodellers.jdbc.password=
#MySQL
com.rolemodellers.jdbc.driver=com.mysql.jdbc.Driver
com.rolemodellers.jdbc.url=jdbc:mysql://localhost/radrunner
com.rolemodellers.jdbc.useClob=false
com.rolemodellers.jdbc.maxPlaywrightLength=0
com.rolemodellers.jdbc.useCreateTableAppendText=true
com.rolemodellers.jdbc.createTableAppendText=Type = InnoDB
#DB2
#com.rolemodellers.jdbc.driver=COM.ibm.db2.jdbc.net.DB2Driver
#com.rolemodellers.jdbc.url=jdbc:db2://SERVER_NAME/radrunner
#com.rolemodellers.jdbc.useClob=true
#com.rolemodellers.jdbc.maxPlaywrightLength=1000000
#com.rolemodellers.jdbc.useCreateTableAppendText=false
#com.rolemodellers.jdbc.createTableAppendText=

# Persistence - Jini
#com.rolemodellers.rim.persistenceMechanism=Javaspace
#com.rolemodellers.jini.codeBase=http://localhost/jini
#com.rolemodellers.jini.codeHost=localhost
#com.rolemodellers.jini.worldHost=localhost

# Java 2 Security - used with Jini
java.security.manager=
java.security.policy=C:\\JBoss\\server\\default\\conf\\server.policy
# Java 2 Security - WebSphere only
enableJava2Security=true
was.home=C:/WebSphere/AppServer

# JNDI - JBoss 3.0.0
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
# JNDI - WebSphere 4.0.3 and 4.0.4
#javax.naming.Context.INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory

# HTTP Proxy
proxySet=false
#proxyHost=192.168.0.1
#proxyPort=6588

# Email - set these properties to enable sending email from a Role
mail.host=validSmtpHost
user.name=validSmtpUserName

# Playwright World
com.rolemodellers.rim.worldName=RoleModellers
com.rolemodellers.rim.bossEmail=boss@rolemodellers.com
com.rolemodellers.rim.bossPassword=byron
com.rolemodellers.rim.automationInterval=60000

# Commercial licensing - leave blank for evaluation
com.rolemodellers.rim.licensedActors=
com.rolemodellers.rim.licenseKey=

# Logging
log4j.configuration=log4j.xml
com.rolemodellers.rim.logSuffix=csv
com.rolemodellers.rim.logger=com.rolemodellers.message.RMLog4JLogger
# Comma-Separated Variable [default] - for import into spreadsheet or database
com.rolemodellers.rim.logPattern=%-6r,%d{ISO8601},%15.15t,%-5p,%40.40c{3},%m%n
com.rolemodellers.rim.logThreadPattern={0},{1},
# Human readable
#com.rolemodellers.rim.logPattern=%-6r %d{ISO8601} [%15.15t] %-5p %40.40c{3} - %m%n
#com.rolemodellers.rim.logThreadPattern='{'{0}:{1}'}'

# You may need to change the port number to that used by your application server
com.rolemodellers.rim.mappingModel=http://localhost:8080/radrunner/castor/mappingModel.xml

# Locale
com.rolemodellers.rim.language=en
com.rolemodellers.rim.country=GB

# Do you want to see all Action steps on screens, including the automated ones?
com.rolemodellers.rim.showAutomatedSteps=false

# The maximum size in bytes of files uploaded to the server
com.rolemodellers.rim.maximumUploadSize=1000000

# The properties in the next set are usually left alone

com.rolemodellers.rim.usePseudoSessions=false
com.rolemodellers.rim.sessionTimeout=1200000
com.rolemodellers.rim.nestedSeparator=.
com.rolemodellers.rim.persistenceTimeout=1000
com.rolemodellers.rim.bossName=RADRunner Boss Actor
com.rolemodellers.rim.fortyTwoObjectName=RADRunner 42 Role
com.rolemodellers.rim.fortyTwoClassPropertyName=42 Type
com.rolemodellers.rim.fortyTwoBossPropertyName=Boss
com.rolemodellers.rim.fortyTwoInstancePropertyName=42
com.rolemodellers.rim.roleBatchSize=8
com.rolemodellers.rim.actionBatchSize=8
com.rolemodellers.rim.actionStepBatchSize=8
com.rolemodellers.rim.playwrightSuffix=xml
com.rolemodellers.rim.dateInputFormat=dd.MM.yyyy HH:mm:ss
com.rolemodellers.rim.countSymbol=#
com.rolemodellers.rim.sumSymbol=+
com.rolemodellers.rim.cacheStylesheets=true
com.rolemodellers.jdbc.connectionTimeout=60000
com.rolemodellers.jdbc.connectionPoolInitialSize=10
com.rolemodellers.jdbc.connectionPoolReapInterval=300000
com.rolemodellers.jdbc.transactionManagerReapInterval=300000
com.rolemodellers.jdbc.table=RM_PLAYWRIGHT_OBJECT
com.rolemodellers.jdbc.columnPrefix=RMPO_
com.rolemodellers.jdbc.worldColumn=WORLD
com.rolemodellers.jdbc.idColumn=ID
com.rolemodellers.jdbc.nameColumn=NAME
com.rolemodellers.jdbc.classIdColumn=CLASS_ID
com.rolemodellers.jdbc.classNameColumn=CLASS_NAME
com.rolemodellers.jdbc.superclassIdColumn=SUPERCLASS_ID
com.rolemodellers.jdbc.superclassNameColumn=SUPERCLASS_NAME
com.rolemodellers.jdbc.emailColumn=EMAIL
com.rolemodellers.jdbc.passwordColumn=PASSWORD
com.rolemodellers.jdbc.typeColumn=TYPE
com.rolemodellers.jdbc.playwrightColumn=PLAYWRIGHT
com.rolemodellers.jdbc.playwrightColumnType=LONGTEXT
com.rolemodellers.jdbc.createdColumn=CREATED
com.rolemodellers.jdbc.lastUpdatedColumn=LAST_UPDATED
com.rolemodellers.jdbc.maxWorldLength=100
com.rolemodellers.jdbc.maxNameLength=100
com.rolemodellers.jdbc.maxEmailLength=100
com.rolemodellers.jdbc.maxPasswordLength=100
com.rolemodellers.jdbc.escapeCharacter=\
com.rolemodellers.jdbc.useEscapeProcessing=false
com.rolemodellers.jdbc.defaultTableXmlElementName=rows
com.rolemodellers.jdbc.rowXmlElementNameFormat=row{0,number,#}

# You should not need to change the following properties

com.rolemodellers.rim.loopLimit=1000000
com.rolemodellers.rim.generatedNameFormat={0} {1,number,#}
com.rolemodellers.rim.descriptionFormat={0} in {1}
com.rolemodellers.rim.useActionSteps=true
com.rolemodellers.rim.maintainRoleBoundary=false
com.rolemodellers.rim.idSeparator=:
com.rolemodellers.ejb.localContext=comp/env/ejb
com.rolemodellers.ejb.globalContext=comp/env/com/rolemodellers/ejb
com.rolemodellers.jini.transactionTimeout=1200000
com.rolemodellers.jini.stressCheckInterval=0
com.rolemodellers.jini.stressLimit=100
com.rolemodellers.jini.stressDelay=500
com.rolemodellers.jini.javaspaceFetchSize=1000
com.rolemodellers.jdbc.statementTimeout=10
com.rolemodellers.jdbc.dataSourceReference=jdbc/RMDB
com.rolemodellers.jdbc.maxTypeLength=100
com.rolemodellers.jdbc.dataSource=com/rolemodellers/jdbc/RMDB
com.rolemodellers.xml.exportFilenameFormat={0}_{1}_{2}.xml
com.rolemodellers.xml.schemaPrefix=xsd
com.rolemodellers.xml.schemaUri=http://www.w3.org/2001/XMLSchema
com.rolemodellers.xml.schemaInstancePrefix=xsi
com.rolemodellers.xml.schemaInstanceUri=http://www.w3.org/2001/XMLSchema-instance
com.rolemodellers.xml.schemaInstanceType=type
com.rolemodellers.xml.attribute=@
com.rolemodellers.xml.replaceWhitespace=_

# Database drivers

com.rolemodellers.jdbc.mysql=com.mysql.jdbc.Driver