3
Setting Up a Development Environment 3-1
3
Setting Up a Development Environment
Oracle provides all of the JSP tag libraries, schemas, and base Java classes that you need to develop a console extension. Because an Administration Console extension is a
collection of XML files, Java classes, JSPs, and other standard Web-related resources, you can use any text editor or Integrated Development Environment to develop your
extension.
The following sections describe setting up an environment for developing Administration Console extensions:
■
Section 3.1, Set Up the Classpath Optional
■
Section 3.2, Import Tag Libraries Into IDEs Optional
■
Section 3.3, Create a Directory Tree for the Extension
■
Section 3.4, Configure Preferences to See UI Control Labels
3.1 Set Up the Classpath Optional
If you are creating Apache Struts classes or Beehive Page Flow classes for your extension, you need a set of Apache classes in your classpath. If you are adding nodes
to the NavTreePortlet, you need a set of Oracle classes.
To add these classes to your classpath, run the following script: WL_HOME\server\bin\setWLSEnv.cmd
or WL_HOME\server\bin\setWLSEnv.sh
where WL_HOME is the directory in which you installed WebLogic Server. Instead of using Oracles script, you can add to your environments classpath all of the
JAR files in the WL_HOMEserverlibconsoleappwebappWEB-INFlib directory.
3.2 Import Tag Libraries Into IDEs Optional
If you are using Oracles JSP templates to create JSPs in your extension, you must use JSP tags from the JSP Standard Tag Library JSTL, the Oracle Administration Console
Extension Tag Library, and the Apache Beehive Page Flows Tag Library.
WebLogic Server installs a version of these tag libraries, which you can make available to your IDE. Alternatively, you can download your own copy of these standard tag
libraries. For more information, see Section 2.3, JSP Templates and Tag Libraries.
3-2 Oracle Fusion Middleware Extending the Administration Console for Oracle WebLogic Server
3.3 Create a Directory Tree for the Extension
An Administration Console extension is a portion of a Web application and its resources must be organized into a directory structure that satisfies the requirements
for standard Java EE Web applications. In addition, the WebLogic Portal framework, Apache Struts, and Apache Beehive require configuration files to be in specific
locations.
To start working on your Administration Console extension, create a directory tree that matches the skeletal structure in
Table 3–1 .
Table 3–1 Directory Tree for an Administration Console Extension
Directory Description
root-dir The root directory of your extension. Oracle
recommends that you do not create files in this directory.
The name of the directory has no programmatic significance. Choose a name that is meaningful to
you. When specifying URIs in your extension, the
forward slash character by itself represents this root directory.
root-dirWEB-INF This directory must contain a file named
netuix-extension.xml . This XML file functions
as your extensions deployment descriptor. If you use Apache Struts, you must locate your Struts
configuration file in this directory. root-dirWEB-INFclasses
If your extension uses a message bundle, your properties files must be in this directory.
If your extension uses custom classes, your package structure must start in this directory. For example, if
you packaged your class files in a package named com.mycompany.extension
, then create the following directory structure in the classes
directory: commycompanyextension. Then save your compiled class files in this extension directory.
optional root-dirWEB-INFsrc If your extension uses custom classes, Oracle
recommends that you save your pre-compiled Java source files in a package structure that starts in this
directory.
When you archive your extension, you do not include this src directory.
recommended root-dirext_jsp Oracle recommends that you save all of your
extensions JSP files below a directory named ext_ jsp
. Creating a separate directory for your JSPs shields
content developers from needing to learn about other support files such as the Portal framework XML files.
If your extension contains many JSPs, consider creating subdirectories below ext_jsp.
If you follow this recommendation, URIs for your JSPs will start with ext_jsp. For example, ext_
jspmyContent.jsp The directory named root-dirjsp is reserved. The
root directory of your extension must not contain a directory named jsp.
Setting Up a Development Environment 3-3
If you are extending the Administration Consoles Look and Feel, your root directory will contain additional subdirectories. See
Chapter 5, Rebranding the Administration Console.
3.4 Configure Preferences to See UI Control Labels
