4.6.2 Deploying the Connect UI in Oracle WebLogic 10 R3

Update the Properties Files

The WebLogic version of the Connect UI is contained in the brickst-weblogic.war file in the Connect install directory (e.g. /opt/connect/kc). This is a J2EE Web Application Archive file that is deployed in WebLogic.

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-weblogic.war WEB-INF/classes/crypto.properties
cp crypto.properties WEB-INF/classes/
zip brickst-weblogic.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-weblogic.war WEB-INF/lib/brickstlicense.jar
cp import/brickstlicense.jar WEB-INF/lib
zip brickst-weblogic.war WEB-INF/lib/brickstlicense.jar

Install JSF Libraries in WebLogic

The Connect UI uses Java Server Faces (JSF) but WebLogic 10 R3 does not install JSF libraries by default. In this section we add the JSF 1.2 libraries to the WebLogic deployment. See the following web page for more details: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webapp/configurejsfandjtsl.html

To install JSF 1.2, follow these steps:

In the WebLogic Server Administration Console, navigate to the Deployments page using the left hand, Domain Structure menu.
Click the Install button at the top of the Deployments table.
Using the directory browser, navigate to the /opt/bea/wlserver_10.3/common/deployable-libraries directory. Then select the jsf-1.2.war file and click the Next button
In the "Install Application Assistant" screen, make sure that the "Install this deployment as a library" button is selected. Then click the Next button.
Click the Next button on the Optional Settings page.
On the "Review your choices and click Finish" screen, make sure that the "Yes, take me to the deployment's configuration screen" option is selected. Click the Finish button.
On the "Settings for JSF (1.2,1.2.3.2)" page set the Deployment Order to 99 so that it is deployed prior to auto deployed applications. Then click the Save button.

Note: There is another step that is needed for this to work. For some reason, even with the steps above classes in the jsf-api.jar are not found during application deployment. The only way for this to work is to put the javax.jsf_1.2.0.0.jar (the jsf-api.jar) from jsf-1.2.war in the domains shared library. This requires a restart of the server.

Create Data Source Definition for Connect UI

Note: Beginning with Connect 10 R3, the Connect UI accesses the database through a J2EE data source instead of managing its own database connection pool.

For a SQL Server data source, WebLogic needs to have the drivers installed before the data source is created. Copy the JDBC Driver jar to the WebLogic server directory:

cd import
cp sqljdbc4.jar /opt/bea/wlserver_10.3/server/lib

Next, edit the WebLogic startup script /opt/bea/wlserver_10.3/common/bin/commEnv.sh to add the SQL Server jar file to the WebLogic class path.

Add this line after the definition of WEBLOGIC_CLASSPATH to append the SQL Server jar file:

WEBLOGIC_CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${WL_HOME}/server/lib/sqljdbc4.jar"

Then save the file and restart the WebLogic Server Domain.

For an Oracle data source, WebLogic already includes the Oracle JDBC Driver jars.

The Connect UI requires a J2EE data source to be defined in the WebLogic console. Define the data source by following these steps.

Go to Services > JDBC > Data Sources, click new, and follow the wizard to create a data source with this jndi name : jdbc/BRICK_STREET_SOFTWARE_CONNECT_DS.
- For an Oracle data source, the Database Type should be "Oracle" and the Database Driver should be "Oracle's Driver (Thin) Versions: 9.0.1,9.2.0,10,11".
- For an SQL Server data source, the Database Type should be "MS SQL Server" and the Database Driver should be "Microsoft's MS SQL Server Driver (Type 4) Versions:2005".
In the "Transaction Options" screen, uncheck "Supports Global Transactions".
In the "Connection Options" screen, specify the server name, database name, user name, and password as appropriate.
In the "Test Database Connection" screen, click the "Test Configuration" button to verify that the classpath and other settings are correct.
In the final screen, select the deployment targets for the new data source and click Finish.

Install Connect Authentication Module

Beginning with Connect 10 R3, the Connect UI uses container-managed authentication (where the application server implements user authentication instead of the Connect application). Thus, an authentication module needs to be defined in WebLogic in order for authentication to work with the Connect UI.

Define the authentication module by executing the following steps:

Stop the Weblogic Domain
Copy import/weblogic/connect_auth.jar to /opt/bea/wlserver_10.3/server/lib/mbeantypes
Restart the Weblogic Domain
In the Administration Console, navigate to Security Realms > myrealm > Providers. Click New. Choose the ConnectAuthenticator type and name it "ConnectAuthenticator". Click OK.
In the Administration Console, navigate to Security Realms > myrealm > Providers. Click DefaultAuthenticator and change the Control Flag to SUFFICIENT. Click Save.
In the Administration Console, navigate to Security Realms > myrealm > Providers. Click ConnectAuthenticator and change the Control Flag to SUFFICIENT. Click Save.

Deploy brickst.war to the WebLogic Server

Deploy the brickst-weblogic.war file to the WebLogic application server. Note that you rename the file to brickst.war before deploying it.

If the WebLogic server is listening on port 7001 (the default), start Connect by opening http://localhost:7001/brickst in a browser.