Deploying the Flux War File in Weblogic

The Flux war file consists of a stand alone implementation of the Flux Operations Console. Engines and agents will need to be started externally if the Operations Console is deployed using only the war file. This guide will briefly go over installing the Flux war file in Weblogic.

The process is relatively straight forward using the Weblogic Administration Console. For those just getting to know Weblogic, it comes packaged with a default administration console that is accessible by first launching the Examples server and then clicking “Start Admin Console” from the welcome page (the default username and password is weblogic).

From the Administration Console, first click the “Deployments” link located in the left section of the screen. Now, you will want to establish a lock on the server by clicking the “Lock and Edit” button. Once you have secured a lock, the “Install” button should no longer be grayed out at the stop of the Deployments screen, click it. The Install Application Assistant should appear.

Now you will have to go through the process of actually setting up the Flux war file. First, locate your flux.war file, click the radio button to the left of it, and select Next. Ensure that the “Install this deployment as an application” radio button is selected and then press Next. Now, you will be presented with a screen concerning security and source accessibility. Select “DD only” and “Use defaults,” then click Finish.

All that’s left to do is to commit the changes and start the application. You can apply the changes you’ve made by clicking the green “Activate Changes” button that appears where the “Lock and edit” button used to be. Then from the Deployments screen, check the Flux checkbox, click the “Start” button at the top, “Start all requested” from the drop box, and then “Yes”.

The war should now be successfully deployed. You can check by going to localhost:{weblogicport}/flux. The default port for Weblogic is 7001 try:
http://localhost:7001/flux