BEA 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:
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 BEA classes.
To add these classes to your classpath, run the following script:
WL_HOME is the directory in which you installed WebLogic Server.
Instead of using BEA's script, you can add to your environment's classpath all of the JAR files in the
If you are using BEA's JSP templates to create JSPs in your extension, you must use JSP tags from the JSP Standard Tag Library (JSTL), the BEA 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 JSP Templates and Tag Libraries.
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 J2EE 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.
The root directory of your extension. BEA 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.
This directory must contain a file named
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
If your extension uses custom classes, BEA recommends that you save your pre-compiled Java source files in a package structure that starts in this directory.
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 you follow this recommendation, URIs for your JSPs will start with
BEA recommends that you save all of your extension's portal book files (
BEA recommends that you save all of your extension's portlet files (
If you are extending the Administration Console's Look and Feel, your root directory will contain additional subdirectories. See Copy and Modify the Sample Look and Feel: Main Steps.
WebLogic Server provides a Look and Feel that reveals the labels of the Administration Console's extension points. You use these labels to specify where you want your extension to display.
|Note:||If you plan only to create a Look and Feel extension or add a portlet to the desktop, you do not need to deploy the development Look and Feel.|
To use this Look and Feel:
devlaf-1.1.jarfile and save it in
domain-rootis the root directory of any WebLogic Server domain in your development environment.
Each labeled control displays the value of its
definitionLabel in brackets () next to its user-visible title. In a separate pair of brackets, the control displays whether it is a book or a page. See Figure 3-1.