QUICK LINKS

Support
Issue Tracker
[Services]
Questions
[uAchieve 4.5 Applications]
[uAchieve 5.0 Application]
[uAchieve 5.1 Application]
Transferology
TES
[Training & Conferences]
Accessibility

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Information for installing the u.select Connector 4.3.x on JBoss

1. Add JDBC Driver to classpath

You must have a JDBC driver in the server's classpath in order for the u.select Connector to connect to the database.

Copy their desired JDBC driver into the /JBOSS_HOME/server/default/lib directory.

2. Add Log4j framework to classpath

Not necessary

JBoss sites don't have to do anything, since Log4j is automatically provided.

3. Configure Data Source

You must configure a JNDI Data Source for your redLantern database. The data source specifies a database and user the u.select Connector will use to access the redLantern database. For the specific redLantern tables that will be accessed by the u.select Connector, see Required DARS Tables or Required u.achieve Tables depending on your redLantern Degree Audit product.

Keep these points in mind when defining a data source in JBoss:

  • JBoss data sources are defined in xml configuration files llocated in the /JBOSS_HOME/server/default/deploy directory.
  • The xml configuration file name must match this file spec: *-ds.xml
    • As an example, you could use a file named: ceg4-ds.xml

Example Oracle data source

The following shows an example JBoss data source definition for an Oracle database. (note the jndi-name must be "EDAG_DARS"):

Example JBoss Data Source Definition for Oracle
<datasources>
<local-tx-datasource>
   <jndi-name>EDAG_DARS</jndi-name>
   <connection-url>jdbc:oracle:thin:@localhost:1521:XE</connection-url>
   <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
   <user-name>thepassword</user-name>
   <password>theuser</password>
</local-tx-datasource>
</datasources>

Example SQL Server data source

The following shows an example JBoss data source definition for a SQL Server database using the JTDS driver. (note the jndi-name must be "EDAG_DARS"):

Example JBoss Data Source Definition for SQL Server using the JTDS driver
<datasources>
<local-tx-datasource>
   <jndi-name>EDAG_DARS</jndi-name>
   <connection-url>jdbc:jtds:sqlserver://localhost/dars35</connection-url>
   <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
   <user-name>thepassword</user-name>
   <password>theuser</password>
</local-tx-datasource>
</datasources>

Example DB2 data source

The following shows an example JBoss data source definition for a DB2 database. (note the jndi-name must be "EDAG_DARS"):

Example JBoss Data Source Definition for DB2
<datasources>
<local-tx-datasource>
   <jndi-name>EDAG_DARS</jndi-name>
   <connection-url>jdbc:db2:yourdatabase</connection-url>
   <driver-class>COM.ibm.db2.jdbc.app.DB2Driver</driver-class>
   <user-name>thepassword</user-name>
   <password>theuser</password>
</local-tx-datasource>
</datasources>

Keep in mind, you must always supply the correct values for your database in these elements: <password>, <user-name>, <connection-url> and <driver-class>

4. Deploy u.select Connector

Copy cas4.properties to /JBOSS_HOME/server/default/conf/ directory

Copy ceg4-ds.xml to /JBOSS_HOME/server/default/deploy/ directory

Copy ceg4.war to /JBOSS_HOME/server/default/deploy/ directory

Start JBoss if it isn't already started.

JBoss will automatically create the /JBOSS_HOME/server/default/deploy/ceg4/ directory structure

  • No labels