The next step is to configure the Eclipse IDE so it knows about Oracle WebLogic Server's installation, the domain we created, and PrimeFaces' shared library.
First, we're going to tell Eclipse where to find WebLogic's runtime environment:
$MW_HOME/oepe/eclipse
Or open the shortcut created by the installation process.
/opt/packt/workspace
on the Workspace Launcher screen.server
, click on the Runtime Environment entry and then the Add... button.12c
in the filter field, select the entry Oracle WebLogic Server 12c (12.1.2) and click on Next.$MW_HOME/wlserver
—and the other fields should be filled automatically:Now we're going to set up the PrimeFaces shared library, so we can reference it from our projects:
shared
to filter the entries, and click on Shared Libraries.primeSL.war
file, or find it using the Browse... button.MANIFEST.MF
file will be shown along with the JAR files that compose the shared library:In order to start and stop the server from within Eclipse, along other actions such as package, deploy, and debug applications using the environment, we must inform the IDE about WebLogic's configured domain and server. To accomplish this, perform the following steps:
server
in the Filter field; now double-click on the Servers entry./$DOMAIN_HOME
—and click on Finish. Here's the final configuration:We left the Local server type on this screen, meaning that OEPE has direct access to the server. If you need to connect to a development server, for instance, Remote is the way to go. Remember that OEPE still needs to access WebLogic Server's modules and libraries to compile your projects, so a local copy of it must be present, even though you will deploy them to a remote server.
18.189.171.193