PQ69728: NLS EXTENSIONS TO PMI SPEC IN RESOURCE ANALYZER NEEDED | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description NLS extensions needed to allow NLS support of Resource Analyzer do not currently exist.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * PMI * **************************************************************** * PROBLEM DESCRIPTION: Unable to get NLS strings for * * custom PMI counters * **************************************************************** * RECOMMENDATION: * **************************************************************** The custom PMI modules need to add their NLS strings to the internal WebSphere pmi.properties file to surface it via PMIClient. This solution is not acceptable as there are many custom PMI modules and all need to update one file. The problem is fixed by using an separate NLS file for custom modules.Problem conclusion Problem fixed in PmiClient to support custom NLS strings via defect 155974. Following are the steps to write custom NLS file: For a custom module, PmiClient can output translated (NLS enabled) and friendly text for counter name and description. This can be done by providing a nls-properties file for the custom module. The following are the steps involved: 1. Create your nls properties file -under com\ibm\websphere\pmi\property directory -name the file as (for e.g): custom_pmi_moduleName.properties 2. Add key-value pair strings -for strings that you want to translate or provide a friendly text -begin the keys with custom_pmi_module Example: custom_pmi_moduleName.counter1.numReqs=Number of requests counter custom_pmi_moduleName.counter1.numReqs.description=Total number of requests processed by server. 3. JAR your properties file -for e.g: custom_pmi_moduleName.jar -this jar should have on file: com\ibm\websphere\pmi\property\custom_pmi_moduleName.properties 4. Copy this jar under WebSphere\AppServer\classes directory 5. PmiClient should automatically pickup your nls file and output the translated string from your nls fileTemporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ69728
IBM Group: Software Group
Modified date: Feb 4, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.