As you all know that sessions are always bind to the login users but you can do the following configuration in WebSphere Application Server to initialize a session for an anonymous user as well.
1. Login to WAS console and select Resources > Resource Environment Providers.
2. Click WP NavigatorService > Additional Properties > Custom Properties.
3. Click New to create new custom properties.
4. In the Name field, type public.session and in the Value field, type true.
6. Click OK to confirm the changes.
7. Save the configuration.
8. Restart portal server.
You can also fire an event for an anonymous user using portlet wiring. To get that property we are supposed to do following configuration changes.
1. Login to WAS console and select Resources > Resource Environment Providers.
2. Click WP PortletServiceRegistryService > Custom Properties.
3. Add a new property with name as "com.ibm.wps.propertybroker.standard.service.PropertyBrokerServiceWrapper.com.ibm.portal.propertybroker.standard.anonymous.page.support"
4. Set the value to true.
5. Save the configuration.
6. Restart portal server.
1. Login to WAS console and select Resources > Resource Environment Providers.
2. Click WP NavigatorService > Additional Properties > Custom Properties.
3. Click New to create new custom properties.
4. In the Name field, type public.session and in the Value field, type true.
6. Click OK to confirm the changes.
7. Save the configuration.
8. Restart portal server.
You can also fire an event for an anonymous user using portlet wiring. To get that property we are supposed to do following configuration changes.
1. Login to WAS console and select Resources > Resource Environment Providers.
2. Click WP PortletServiceRegistryService > Custom Properties.
3. Add a new property with name as "com.ibm.wps.propertybroker.standard.service.PropertyBrokerServiceWrapper.com.ibm.portal.propertybroker.standard.anonymous.page.support"
4. Set the value to true.
5. Save the configuration.
6. Restart portal server.
No comments:
Post a Comment