Filter
Top Products
17-25
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 17 Configuring Broadband Access Center
Managing DPE Feature Pack Extensions
Java JAR file manifests contain attributes that are formatted as name-value pairs and support a group of
attributes that provide package versioning information.
While Cisco BAC accepts extension JAR files that do not contain this information, we recommend that
you include a manifest with versioning information in the files to track custom RDU extensions.
You can view manifest information from the administrator user interface using the Servers > RDU >
View Regional Distribution Unit Details page.
Detailed information on the installed extension JAR files and the loaded extension class files appears
after the Device Statistics section. You can view manifest information from the RDU logs also.
Step 3 Create the JAR file for the custom extension point.
For example:
C:\>jar cm0vf manifest.txt removetimeservers.jar com
added manifest
adding: com/(in = 0) (out= 0)(stored 0%)
adding: com/cisco/(in = 0) (out= 0)(stored 0%)
adding: com/cisco/support/(in = 0) (out= 0)(stored 0%)
adding: com/cisco/support/extensions/(in = 0) (out= 0)(stored 0%)
adding: com/cisco/support/extensions/configgeneration/(in = 0) (out= 0)(stored 0%)
adding: com/cisco/support/extensions/configgeneration/
RemoveTimeServersExtension.class(in = 4038) (out= 4038)(stored 0%)
C:\>
Note You can give the JAR file any name. The name can be descriptive, but do not duplicate another
existing JAR filename.
Installing RDU Custom Extensions
After a Jar file is created, use the administrator user interface to install it:
Step 1 To add the new Jar file, see Adding Files, page 17-17.
Use the Browse function to locate the Jar file created in the procedure, Writing a New Class for RDU,
page 17-24, and select this file as the Source File; leaving the File Name blank assigns the same filename
for both source and external. The filename is what you will see through the administrator user interface.
Step 2 Click Submit.
Step 3 Return to the RDU Defaults page and note that the newly added Jar file appears in the Extension Point
Jar File Search Order field.
Step 4 Enter the extension class name in the Publishing Extension Point field.
The RDU returns an error if the class name does not exist within the jar file or if Cisco BAC detects any
other errors. This error occurs mostly when replacing a Jar file, if, for example, the class you set up is
not found in the replacement Jar file.
Step 5 Click Submit to commit the changes to the RDU database.
Step 6 View the RDU extensions to ensure that the correct extensions are loaded.