Public void init() throws PortletExceptionĬom.PortletServiceHome psh Private ParameterNamesProcessorSample iParamNamesProc = null Private PortletSiteAnalyzerLoggingServiceHome iSALogServiceHome = null If there is no replacement for a parameter name, the original key is returned to be written to the site analysis log entry as it is. The sample holds a static mapping of possible request parameter names to a more descriptive expression that you want to be used in site analysis log entries instead. Implementing a parameter names processor: The following code sample shows an implementation of the ParameterNamesProcessor interface. Restart the portal to activate the changes. If your portal runs in a cluster configuration, replicate your changes to the cluster. When you are done, click Save at the start of the page under Message(s).Ĭlick Save again when prompted to confirm your change.Create a new property named SiteAnalyzerJSRPortletLogger.isLogging and set its value to true.Select the property SiteAnalyzerJSRPortletLogger.isLogging and change its value to true.In the Resource environment providers page, elect the appropriate node or cluster from the scopes pull-down list, or clear the Show Scope selection drop-down check box and select one of the following options, depending on your portal environment: If your portal is installed in a cluster, select Browse Clusters and select the portal cluster.If your portal runs as a single server, select Browse Nodes and select the node.For WebSphere Application Server Version 7.0: Select the appropriate node or cluster from the scopes pull-down list, or clear the Show Scope selection drop-down check box and select one of the following options, depending on your portal environment:.For WebSphere Application Server Version 6.1: Select the appropriate node or cluster from the scopes pull-down list, depending on your portal environment.In the Resource environment providers page, make the appropriate selection, depending on your version of WebSphere Application Server and your portal environment: In the navigation click Resources > Resource Environment > Resource Environment Providers. where your_ is the name of your server and admin_port is the port that is assigned to the WebSphere Integrated Solutions Console. Start the WebSphere Integrated Solutions Console by entering the following URL in the URL location field of a web browser: If your portal is installed in a cluster, use the WebSphere Integrated Solutions Console of the Deployment Manager.If your portal runs stand-alone, use the local WebSphere Integrated Solutions Console.Select the appropriate WebSphere Integrated Solutions Console, depending on your environment: You set its property in the WebSphere® Integrated Solutions Console through the resource environment provider WP SiteAnalyzerLogService. To activate and use the portal site analyzer logger for standard portlets, proceed by the following steps:Īctivating the site analyzer logger for standard portlets: You enable the site analyzer logger for standard portlets by using the portal configuration service SiteAnalyzerLogService. Implementations of this interface are called by the site analytics framework before assembling the query string section of the request URI that is written to the site analysis log file. The ParameterNamesProcessor interface allows portlet developers to provide the PortletSiteAnalyzerLogger with a callback for processing request parameter names. This recommendation does not leave much space for meaningful parameter names in site analysis log entries. Request parameter names, in particular render parameter names that are encoded into portal URLs, should be as short in length as possible. It is valid for the request for which it was created, and it provides methods to query the logger state - enabled or disabled - and to create a site analysis log entry.Ĭom.siteanalyzer.ParameterNamesProcessor Portlets can retrieve an instance of this logger from the PortletSiteAnalyzerLoggingServiceHome. Portlets obtain this portlet service through a JNDI lookup.Ĭom.siteanalyzer.PortletSiteAnalyzerLogger This request type is either an ActionRequest, an EventRequest, a RenderRequest, or a ResourceRequest. This portlet service exposes methods to obtain a logger instance that is specialized on the specified request type. The following are main components of the site analysis logging framework for standard portlets:Ĭom.siteanalyzer.PortletSiteAnalyzerLoggingServiceHome Note: The procedures that are described in the following topic and subtopics work only for standard (JSR 168 or JSR 286) portlets. Logging custom details of business events for site analysisįrom a business point of view, you might want to log custom details of business events.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |