Originally published at developer.com
At last yearís BEA World many portal developers were excited to hear that the WLS Administration Console is now portal-based. As developers, we all know that what excites us doesnít always excite those who hold the purse strings, and customizing an application that is only used by IT generally falls pretty close to the bottom of the budget approval list. At least until there is a really good reason for it. So, my first foray into customizing the WLS Administration Console didnít come about until 9.2, and was limited to changing color schemes.
For those of you looking for approval to customize your console, the driver for the project this article is based on came from a case where multiple BEA domains were running installed on the same physical machine. When the maintenance team would log in to the various consoles they would occasionally make an update to the wrong domain. Doh! For those who have done support, this comes as no big surprise. Many service activities are scheduled in off hours. Off hours are defined as when most users are off the applications and most IT folks are off their par because it is too late at night. The only visual cue as to which console you are logged into is some subtle text showing the user name and domain name.
The solution for this was to color-code the header in each Administration Console. While this sounds fairly straight-forward to the average portal developer, there are a few things that made it a bit of a challenge. First, the Administration Console application is compiled (as it should be), so cracking it open was a bad option as this could have upgrade implications. Second, even if one were to crack open the Administration Console portal (weíve all made a similar call and regretted it at the next upgrade), the application under WEBLOGIC_HOME affects all domains rather than individual domains. Finally, the steps described at http://e-docs.bea.com/wls/docs92/console_ext/rebrand.html leave out a couple of minor pieces that are only obvious to portal developers. To make a long story short (which is only ever said when it is already too late) I came up with the following steps that worked for this effort.
(If you donít already have a portal development environment, download the latest from http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/products/weblogic/portal/.)
Create a new workspace for Eclipse for your customization project. For old-time Eclipse developers, this may sound odd. I thought it odd that the BEA best practice is a new workspace for each related group of projects and at first stuck to my old ways of one workspace for all projects. Then I made a change to the wrong project and stopped being so obstinate. Since there are similar types of projects from one group to the next, it is an easy mistake to make and thus the smart recommendation not to. Long story etc.
In your new workspace, create a new Java project named console-extension. While it doesnít matter what you name your project, this name makes it easier to remember what it is for and to reference documentation related to console customization. Next, import [WEBLOGIC_HOME]\samples\server\medrec\console-extension into your new project. If you are unfamiliar with Eclipse imports, this is done with the File System option in the Import dialog. Once we have this tree in, we want to trim the branches that we donít want to change by deleting the following:
All in \workspace\console-extension\framework\skins\xray EXCEPT the following:
All in \workspace\console-extension\framework\skins\xray\images
All in \workspace\console-extension\framework\skins\xray\css
All in \workspace\console-extension\framework\skeletons\xray
All in \workspace\console-extension\images
Now we want to add some files for our use. First, create a skeleton.properties file in †\workspace\console-extension\framework\skeletons\xray and add the following:
jsp.search.path: ., ../default
Then do the following imports (all files in the path for each):
[WEBLOGIC_HOME]\server\lib\consoleapp\webapp\framework\skins\default\images to /console-extension/framework/skeletons/xray/images
[WEBLOGIC_HOME]\server\lib\consoleapp\webapp\images to /console-extension/images
[WEBLOGIC_HOME]\server\lib\consoleapp\webapp\framework\skins\default\css\ to \workspace\console-extension\framework\skins\xray\css
Next, open /console-extension/framework/skins/xray/skin.properties and delete the following (spread in groups through the file):
theme.plain.search.path: plain/images, images
theme.alert.search.path: alert/images, images
theme.wlsmodules.search.path: wlsmodules/images, images
theme.wlstoolbar.search.path: wlstoolbar/images, images
theme.wlsbreadcrumbs.search.path: wlsbreadcrumbs/images, images
theme.wlschangemgmt.search.path: wlschangemgmt/images, images
theme.wlsworkspace.search.path: wlsworkspace/images, images
theme.wlsnavtree.search.path: wlsnavtree/images, images
theme.wlsmessages.search.path: wlsmessages/images, images
theme.wlsstatus.search.path: wlsstatus/images, images
theme.wlsquicklinks.search.path: wlsquicklinks/images, images
(note that if you want to customize any of the above UI elements for your own application leave the ones you need).
Open netuix-extension.xml and delete the following: default-window-icon="window-icon.gif" and default-window-icon-path="/console/images/"
To change our header appearance we need to change two files. First, open /console-extension/framework/skins/xray/css/body.css and change the value of background-color: for .bea-portal-body-header; Then, grab an image editor and change the color in /console-extension/framework/skins/xray/images/banner_bg.gif to the same value. For ascetics, you may wish to edit /console-extension/framework/skins/xray/images/banner_logo.gif as well.
Finally, save everything, then right-click on the console-extension project and select Export. Export as a JAR file to domain-dir/console-ext directory (or to a handy local location to later be uploaded to the domain-dir/console-ext directory). If you made any of your changes in the file system rather than in Eclipse, be sure to refresh your project before exporting or you will get errors.
The example below uses the color value of FFCC33 to replace the default:
While there may be some simpler paths to achieving this, this particular approach was the fastest solution that should have little or no impact to future upgrades within the 9.x WebLogic Server series. If most of these steps seem daunting, you can grab the workspace from here (PLEASE CREATE LINK TO workspace.zip) and find the values you want to change.
Scott Nelson is a Professional Services Principal Portal Consultant by day and a blogger with a sense of humor by night. This article illustrates the former. To confirm the latter for yourself, visit http://fuq.fywservices.com/.
© 2013 Scott Nelson dba FYW Enterprises