Sunday, October 26, 2008
Monday, October 20, 2008
My Wife blog
Friday, October 03, 2008
WebSphere Portal V6.1.0.1 Beta
Here's a simple way to get people started to test / pilot WebSphere Portal.
IBM WebSphere Portal 6.1 Beta, Its the NEW beta 1, release of WebSphere Portal V6.1.0.1 Beta. It is available on VM Suse image. Just load the VM image and start the server. As simple as that.
IBM WebSphere Portal 6.1 Beta, Its the NEW beta 1, release of WebSphere Portal V6.1.0.1 Beta. It is available on VM Suse image. Just load the VM image and start the server. As simple as that.
Thursday, October 02, 2008
Configuring WebSphere Portal for site analysis logging
I have been missing in action for quite a while. My connection was limited because my previous company block most of the blogging sites. I have just join a new company and partial of my time will be located in Denmark. What suppose to be a Lotus Domino job turns out to be more working on WebSphere Portal. Luckily I have previous experience to let me carry out my task.
The portal implementation here is still on going. Thus one thing I can for see is that they will need statistic on the number of logons and pages access. By default WebSphere site analysis logging is not enable. Thus I took the initiative to enable the logging.
1) Open WebSphere admin console
2) In the navigation open the Resources section
3) Click Resource Environment Providers.
4) In the Resource Environment Providers frame make the following selection, depending on your environment:
* If running standalone, select Browse nodes and select the node.
* If installed in a cluster, select Browse Clusters and select the cluster.
5) Select the service to which you want to make changes. In this case select "WP SiteAnalyzerLogService"
6) Click Custom Properties. More info can be found here.
7) Restart the server to make the changes become effective.
Awstats can be use to present the generated logs in more friendly manner. There is an article here describing the steps.
Alternate to this, you can use third party tools. If your company policy allows, free site tracker can be used too. I have been using Google Analytics for some sites, it is easy to setup and it does provide detail informations.
The portal implementation here is still on going. Thus one thing I can for see is that they will need statistic on the number of logons and pages access. By default WebSphere site analysis logging is not enable. Thus I took the initiative to enable the logging.
1) Open WebSphere admin console
2) In the navigation open the Resources section
3) Click Resource Environment Providers.
4) In the Resource Environment Providers frame make the following selection, depending on your environment:
* If running standalone, select Browse nodes and select the node.
* If installed in a cluster, select Browse Clusters and select the cluster.
5) Select the service to which you want to make changes. In this case select "WP SiteAnalyzerLogService"
6) Click Custom Properties. More info can be found here.
7) Restart the server to make the changes become effective.
Awstats can be use to present the generated logs in more friendly manner. There is an article here describing the steps.
Alternate to this, you can use third party tools. If your company policy allows, free site tracker can be used too. I have been using Google Analytics for some sites, it is easy to setup and it does provide detail informations.
Subscribe to:
Posts (Atom)