There are different ways to configure Flux to run inside WebLogic. You can use one of the above techniques, or you can use the following technique. Each is valid. You should determine which technique best fits into your architecture.
- Startup Class. Flux can be configured as a startup class in WebLogic. This technique is particularly convenient in WebLogic, since WebLogic will initialize and configure Flux automatically when the server starts. Similarly, when WebLogic shuts down, Flux will shut down.
When configuring Flux to use a WebLogic data source for obtaining database connections, it is recommended that you use the actual WebLogic data source name, not a “resource reference” pointing to the data source. There has been a report of an inexplicable error when using a resource reference, not the actual data source, with WebLogic 6.1.
The Flux Operations Console (flux.war) can be deployed just like any WAR file in WebLogic. Just follow the deployment instructions for your version of WebLogic to quickly and easily deploy the flux.war file to your WebLogic Server.
If the Flux engine is running standalone (outside of WebLogic) but you have configured Flux to look up a WebLogic data source using JNDI, you will need to include some additional JAR files on the Java class path when starting the engine. Find your WebLogic version below for the specific names of the JAR files you will need to include.
Include the following JAR files on the Java class path: weblogic.jar, xbean.jar.
Include the following JAR file on the class path: wlfullclient.jar. This JAR is generated by running the following command (from $WL_HOME/wlserver_10.3/server/lib):
java -jar wljarbuilder.jar
In order to avoid classpath and classloader conflicts with Weblogic-provided classes and packages, servlets utilizing Flux 8.0 require a weblogic.xml deployment descriptor placed in the WEB-INF directory of the deployed project. The XML is as follows.
weblogic.xml Expand source