IBM BS029ML Self Help Guide - Page 133
Reading portal runtime logs, wmmWASAdmin.xml
![]() |
View all IBM BS029ML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 133 highlights
Note: The base (root) portal and portal admin user ("wpsadmin") must be configured in the default realm. Note: Each of the wmmnode entries in wmmur.xml must correspond to a nodeMap entry in wmm.xml. This is how WMM ties the realm definition of user populations in this file with general WMM configurations together. Make sure the location of this pointer in the cluster configuration is correct. In order for the admin user to be able to access the virtual portals configured with the realms defined, we recommend adding the admin user "wpsadmin" to every realm, as shown in the example. wmmWASAdmin.xml When the security is enabled with realm support, the normal way of controlling the access to the Administrative Console of WebSphere Application Server is through file wmmWASAdmin.xml. After a console user is added through the administrative console, you have to manually add an entry for that user into this file. This file only contains users, not groups. This means that there is no equivalent support for console groups using this file. The format of this file is shown in Example 4-11. Example 4-11 wmmWASAdmin.xml Although one can use a plain-text password in this file, we strongly recommend encrypting the password using the WMM utility called wmm_encrypt.bat/.sh. An alternative to this approach of manually modifying the file wmmWASAdmin.xml using an editor is using the utility updateWmmWASAdminRegistry.bat/.sh. IBM TechNote 1246919 had documented the usage of this utility. The second entry for the same user ID wasadmin allows using the short user ID when starting the application servers and logging in on the Administrative console. 4.3.5 Reading portal runtime logs In WebSphere Portal Version 6, the runtime activities are recorded in the application server's Java Virtual Machine (JVM) logs, that is, SystemOut.log and SystemErr.log. For any problems reported during runtime, these logs should be reviewed first. During WebSphere Portal configuration activities, when either using the configuration command-line utility (WPSconfig.sh/.bat) or the graphic configuration wizard, all the information is captured to ConfigTrace.log. When something unexpected happens, these are the files to be reviewed for clues. When diagnostics traces are enabled, trace.log should be reviewed with the reference Chapter 4. WebSphere Portal security 119
![](/manual_guide/products/ibm-bs029ml-self-help-guide-6d3dd71/133.png)