Update the Properties Files
The JBoss version of the Connect UI is contained in the brickst-jboss.war file, which
is located in the Connect install directory (e.g.
C:\Connect\kc). This is a J2EE Web Application Archive
file that is deployed in JBoss.
The Connect UI embeds a copy of the crypto.properties files that contains the
crypto provider information.
Copy the properties file into the war file using the following commands:
unzip brickst-jboss.war WEB-INF\classes\crypto.properties
copy crypto.properties WEB-INF\classes\
zip brickst-jboss.war WEB-INF\classes\crypto.properties
The
unzip commands extract the properties files from the war file. The copy commands
overwrite the extracted files with the ones in the install directory. The zip
commands store the new properties files into the war file.
Install Software License Key
The brickstlicense.jar file must be stored in the war file:
unzip brickst-jboss.war WEB-INF\lib\brickstlicense.jar
copy import\brickstlicense.jar WEB-INF\lib
zip brickst-jboss.war WEB-INF\lib\brickstlicense.jar
Create Data Source Definition for Connect UI
Note: The Connect UI accesses the database through a J2EE
data source definition instead of managing its own database connection pool.
The Connect UI requires a J2EE data source to be defined by the JBoss application
server. Connect includes template data source files in the
import\jboss subdirectory of the Connect install
directory. There are three template data source files:
- connect-mssql-ds.xml
- connect-mysql-ds.xml
- connect-oracle-ds.xml
Copy one of these files (depending on whether you want to configure an Oracle,
SQL Server, or MySQL data source) to the JBoss deployment directory (typically
C:\jboss-4.2.3.GA\server\default\deploy). Then edit the
XML file (connect-mssql-ds.xml or connect-oracle-ds.xml) substituting the following
values:
- %DATABASE_SERVER% - with the name or address of the database server
- %DATABASE_NAME% - with the name of the database
- %USER% - user name for logging in to database
- %PASSWORD% - password logging in to database
Do not modify any other part of the data source definition file.
For an SQL Server data source, copy the JDBC Driver jar to the JBoss server
directory:
cd import
copy sqljdbc4.jar C:\jboss-4.2.3.GA\server\default\lib
For a MySQL data source, copy the JDBC Driver jar to the JBoss server
directory:
cd import\SQL2005_jdk\common
copy mysql-connector-java-5.1.13-bin.jar C:\jboss-4.2.3.GA\server\default\lib
For an Oracle data source, copy the JDBC Driver jar to the JBoss server directory:
cd import\Oracle11107_jdk6\common
copy ojdbc6.jar C:\jboss-4.2.3.GA\server\default\lib
copy orai18n.jar C:\jboss-4.2.3.GA\server\default\lib
Install Connect Authentication Module
The Connect UI uses container-managed authentication.
Thus, an authentication module needs to be defined in JBoss in order for
authentication to work with the Connect UI.
Install the Connect authentication module by copying the login-config.xml file to the
JBoss deployment directory:
cd import\jboss
copy login-config.xml C:\jboss-4.2.3.GA\server\default\conf
Modify JBoss Properties Service
Modify the properties-service.xml file in the
C:\jboss-4.2.3.GA\server\default\deploy directory:
- Search for the element that starts with <attribute
name="properties">
- Uncomment this element if it is commented out
- Add the following line to the text of the element:
"jndi.ds.prefix=java:"
The edited element should look like this:
<attribute name="Properties">
jndi.ds.prefix=java:
</attribute>
Deploy brickst.war to the JBoss Server
Deploy the brickst.war file to the JBoss application server by copying it to the
JBoss deployment directory:
copy brickst-jboss.war C:\jboss-4.2.3.GA\server\default\deploy\brickst.war
Note
that we rename the file to brickst.war in the deployment directory.
If the JBoss server is listening on port 8080 (the default), start Connect by opening
http://localhost:8080/brickst in a browser.