Legal
Middleware Magic (middlewaremagic.com) is in no way affiliated with or a part of any companies. We are a completely independent Middleware Application Server community resource site.
Here at Middleware Magic we only wish to encourage the users to use of few Middleware Applications Servers and try to make the best out of these application servers.
Middleware Magic in no way encourages or give ideas to user of respective application servers to hack or for any malicious behavior.
Anything posted on Middleware Magic related to any security breaches regarding application servers is here purely to provide public awareness messages regarding the hack/BUG. This way we allow to keep our users updated about the issue/BUG, so that they can ask for a patch from their respective application server support team and keep their own application protected and help the application server team to keep their servers update to date.
Middleware Magic recognizes that certain words, names, and designations mentioned on this web site are the property of the trademark holder. We only use them for identification purposes only and do not have any intention to harm/hinder their reputation.
General
All applications, scripts, tips provided by Middleware Magic are tested and tried by the author and we make sure that they are 100% secure to use before they are made public. But as a policy, we over at Middleware Magic will not take any responsibility for these applications, scripts, tips provided on the site. Hence we would always suggest and encourage our users to test them before applying them in production.
By using applications, scripts, tips from Middleware Magic, we assume that you are using these applications, scripts, tips at your own risk and neither Middleware Magic nor the author will be responsible for any consequences and bear full responsibility of the risk of any harm that may occur to you or others (because of you) in any way whatsoever.
Copyrights
Of course you can use anything you find interesting on Middleware Magic in your own publications, as long as put in the proper references in your own publication.
Note
This Disclaimer is subject to change any-time without prior notice and any changes made will be effective immediately. If you have any questions or issues, please use the contact form to contact us.
November 14th, 2012 on 2:10 am
I have tried several times to send an email using your contact formular but I always got “Email could not be sent”. Is there any other way or email address which I can use for a contact and qustion ?
November 15th, 2012 on 1:16 pm
You can ask your questions in comments – this probably the easiest way.
November 16th, 2012 on 9:45 am
Hi Rene,
Middleware Magic blog is simply awesome ,i have got lot of inofrmation on WL from the posts here.
1>I need inofrmation on how do we configure Weblogic as webserver.
– I tried by giving the port as 80 in the console for the managed server and by the hostname the application has been accessed, now how do we configure say if we have 3/4 managed instances in same domain.
2> How can we configure compression and caching for Weblogic as Webserver.
– In case of Apache / IIS we can perform using the mod deflate and so on.
Any suggestions on the above questions will be really grateful.
Thanks,
Chetan K
November 16th, 2012 on 1:56 pm
http://middlewaremagic.com/weblogic/?p=2649
November 20th, 2012 on 3:41 pm
Hi Rene,
Thanks for the link.
Actually in my case i am having only one managed server which is acting as application server and webserver , to make this work i have modified the port as 80 and hence it is workign fine.
I need your suggestions on How to enable compression and caching for this weblogic as webserver which is running on port 80.
In case if we use Apache / IIS we can enable compression & caching at the webserver level.
I have verified this link :
http://middlewaremagic.com/weblogic/?p=5916
Here am stuck with and confused on how to enable compression & caching.
Thanks for all the help.
November 20th, 2012 on 6:50 pm
As Jay points out you can add a weblogic.xml file to your application (or use deployment plans) and set
the compress-html-template to true – http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#autoId10
For caching you could use the CacheFilter – http://docs.oracle.com/cd/E13222_01/wls/docs103/javadocs/weblogic/cache/filter/CacheFilter.html
The CacheFilter is registered like any other servlet filter. Define the filter in the web.xml file, and
specify the url-pattern of the page or pages to cache. Use initialization parameters in the filter
registration to define timeout criteria and other cache control values. For example, to cache the
response from a specific JSP page for 60 seconds, register the CacheFilter using elements similar to
the following:
The CacheFilterTest1.jsp page will execute the first time the URL is accessed by any client, and the
content of the HTTP response will be cached by the filter and used for all subsequent access requests for
60 seconds.