It is possible to run Cargo Tracker on WebLogic with any Maven capable IDE or without an IDE. In the following instructions we will outline how to do so specifically with NetBeans. The instructions should be generally helpful with running the application any other way using WebLogic such as in another Maven capable IDE like IntelliJ. Note that we currently do not recommend Eclipse due to it’s weak support of Maven. For detailed reasons why this is the case, please look here.
The first step to running Cargo Tracker on WebLogic is properly installing and configuring the application server. For GlassFish this is a trivial matter of unzipping the downloaded distribution anywhere in the file system. For WebLogic the instructions are more involved. We have outlined the instructions that should work for Cargo Tracker below.
Make sure you have JDK 8+ installed. The version of WebLogic that supports Java EE 7 is WebLogic 12.2.1. It requires JDK 8.
Download WebLogic 12.2.1 from here. You will need to download the Generic installer (784 MB) for Cargo Tracker. Unfortunately you will not be able to use the Quick Installer (211 MB) for Cargo Tracker due to a bug. In the future it may be possible to use the simpler Quick Installer. You can use your downloaded copy of WebLogic for free using at OTN license.
Please unzip the zip file. You will find a jar file that is the graphical installer for WebLogic.
Using the JDK’s java executable (not the one for the JRE), run java -jar fmw_220.127.116.11.0_wls.jar. Make sure you are running with admin rights. The installer GUI should start momentarily.
Accept all the defaults for the “Welcome”, “Auto Updates” and “Installation Location” screens. On the “Installation Type” screen, make sure you choose installation type “Complete with Examples”. This will make the rest of the setup for this project far simpler for you.
The installation will take a few minutes after you hit “Install” on the “Installation Summary” screen. On the “Installation Complete” screen make sure to keep the “Automatically Launch Quickstart Configuration Wizard” option selected before you hit “Finish”. This will launch the domain configuration wizard which makes setting up the domain far easier than doing it manually.
On the “Configuration” screen you’ll need to enter a username and password. You can enter the username/password as weblogic/weblogic1. You should accept all the rest of the defaults on this screen and subsequent screens. Once the wizard is done it will exit and WebLogic will be ready to use.
The Cargo Tracker NetBeans instructions with GlassFish largely applies to WebLogic. In this section we will focus on the differences instead of repeating what is common. It will help to open those instructions on another browser tab and flip back and forth with this page.
For the prerequisites there is obviously no need to install GlassFish if you are using WebLogic. NetBeans 8.1 is still best suited for Cargo Tracker. You should follow the NetBeans instructions to download the project. The initial NetBeans setup will differ however.
Do not setup GlassFish in NetBeans - we will setup WebLogic instead. After starting NetBeans go in the ‘Services’ tab, right click ‘Servers’ and hit ‘Add Server’.
Cargo Tracker includes support for running the application using the Cargo Maven plug-in. As a result you can get the application running simply by entering “mvn cargo:run” in the project directory. Under the hood the Cargo Maven plug-in downloads GlassFish, installs the application server and runs the application against it. This is provided as a convenience quick start of the application that requires minimal effort - certainly avoiding application server setup or an IDE. This is possible because GlassFish can be installed and run by simply unzipping a distributable. Unfortunately a similar minimalist quick start with WebLogic is not currently possible due to it’s more involved installation and configuration. As a result we do not currently support running Cargo Tracker using WebLogic via Cargo. Note that Cargo as such does support running against pre-installed and configured WebLogic remote instances. Such support is primarily intended for operational automation rather than the quick start mechanism more relevant for this project.