You are creating a new theme and skins, making changes to your theme and skin jsp's, and want to see those changes immediately on portal?
You can do this by forcing application server and reflect your changes immediately.
For this, you will require to enable automatic JSP reloading..
Here you go....
1) Open file "ibm-web-ext.xmi", located under
2) Find the following entry in above file
<?xml version="1.0" encoding="UTF-8"?>
<com.ibm.ejs.models.base.extensions.webappext:WebAppExtension xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.ejs.models.base.extensions.webappext="webappext.xmi" xmi:id="IBM_WPS_Ext" reloadInterval="3" reloadingEnabled="false" fileServingEnabled="true" directoryBrowsingEnabled="false" serveServletsByClassnameEnabled="false" preCompileJSPs="false">
3) Make reloadingEnabled value to true
4) Save the file and
5) Restart portal server.
After making these changes, you should be able to see your theme and skin change immediately...
Important :- To see changes to your JSP's that is being included by another(parent) JSP, you should make a change(you can simply enter and save jsp) to parent JSP to tell the sever that reload parent as well.
For example:- you can see that, head.jspf is included in your default.jsp
<%@ include file="./head.jspf" %>
Now, if you are making changes to head.jspf, and want to see your changes, you will also require to make a change in parent jsp, which is default.jsp.
Enable automatic JSP reloading should be done for testing and development purpose only and should always be disabled for Production environment for performance issues.