Often I get complaints if the SAP Portal is still running. The portal seems to be slow, pages are empty. I know what is going on, I am developing the custom framework, fixing some bugs or adding new functionality. Deploying the portal application takes some time and you will notice it.
Well… my collegues love me once more. How? I am using Fiddler (and other HTTP watchers) and discovered there’s a neat functionality in it. It’s called “Autoresponder”. http://www.youtube.com/watch?v=h3DWqYXKarA
Ok, here’s the deal. Step by step this time to set everything up.
Get the files you will change a lot. In my case they are located in my portal application.
Copy and paste the files into a folder (e.g. d:\noel\fiddler)
Setup fiddler with autoresponder settings:
Go to Autoresponder > Add rule. Now you need to know the location of your css and js files while viewing as an end user:
Copy and paste the url of the css file into the rule definition
When Fiddler sees this file, it will be ‘replaced’ by the one you defined.
Step 4: Enable it
Change your local files as often as you like. No one will notice it!!!
Don’t forget to save your changes back to the origional source (portal project) when you are finished.
Noël Hendrikx – SAP Portal consultant @ Peppie Portals.
Specialized in Corporate branding SAP Portal / Adobe Interactive Forms.
UI Theming blog series