如何在Portal群集环境中修改wmm文件

近期为了客户的一个portal-sametime集成项目中，利用了portal自带的people finder portlet，其中查找人员的时候，需要显示更多LDAP信息的字段，需要手动的去修改一些wmm文件，详细地操作步骤就不再描述（）

 

 

Questions about modifying wmm files in a WebSphere Portal cluster

 Technote (FAQ)

Problem

You have seen the information in the WebSphere® Portal InfoCenter regarding the editing of Member Manager files on a federated node. However, you have additional queries regarding the configuration tasks that are used to check out the wmm files from the deployment manager for editing and then check them back in.

Solution

What follows is a list of frequently asked questions about modifying the wmm files.

Does the deployment manager manage the wmm files if the post-portal-federation task has not been run?
No. You must run the post-portal-federation task, and then the deployment manager will manage the wmm files. If you do not run this task, you may see errors in the cluster about missing wmm files.

Is the post-federation task a sub-task, or is it run explicitly?
It is run explicitly, as documented in the WebSphere Portal InfoCenter.

Do the check-in and check-out tasks actually modify the wmm files?
No, these tasks simply allow you to safely modify the files manually on one portal node, and then update the deployment manager with your modified files.

Which set of wmm files should you modify?
You should modify the wmm files in the /wmm directory on the portal node where you ran the configuration task:

WPSconfig check-out-wmm-cfg-files-from-dmgr

NOTE: This task extracts the files from the deployment manager's master repository and transfers them to the node on which the task was run.

What is the general order of the process to modify the wmm files in a cluster?

1. Run the WPSconfig check-out-wmm-cfg-files-from-dmgr on the portal node where you are going to be making the changes.
2. Modify the wmm files as needed. For example, this is where you would modify your "adminID" or "adminPassword" values if they change on the user registry.
3. Run the WPSconfig check-in-wmm-cfg-files-to-dmgr on the portal node where you made the changes.
4. Synchronize the cluster so that the other nodes in the cluster are updated with the modified wmm files.

 

但是修改完毕后，并没有生效，后来发现在群集下修改这些文件的步骤出错了，需要首先从dm中将这些配置文件check-out,然后修改完毕后再将这些文件check-in才可以。

 

 

 

How to add additional attributes/description to the People Finder Portlet

 Technote (FAQ)

Problem

How do you add a new Lightweight Directory Access Protocol (LDAP) attribute to WebSphere® Member Management (WMM) so that it will show up in the People Finder Portlet in IBM® WebSphere Portal?

In addition, you would like to add the description to the attribute when it shows up in People Finder portlet. New attributes are not currently available for searching and description missing for the attribute.

Solution

A. Update WMM to recognize the new field from your LDAP directory.

1. Map the new attribute in the wmmLDAPServerAttributes.xml file on the Portal server that hosts the People Finder Portlet:

Windows/UNIX: You can locate the file in the following directory:

wp_root/wmm/wmmLDAPServerAttributes.xml

i5/OS: You can locate the file in the following directory:

wp_user_root/wmm/wmmLDAPServerAttributes.xml
...
wmmAttributeName=""
pluginAttributeName=""
applicableMemberTypes="Person"
dataType="String"
valueLength="1024"
multiValued="false" />

2. Map the new attribute in the wmmLDAPAttributes.xml file on the Portal server that hosts the People Finder Portlet:

Windows/UNIX: You can locate the file in the following directory:

wp_root/wmm/wmmLDAPAttributes.xml

i5/OS: You can locate the file in the following directory:

wp_user_root/wmm/wmmLDAPAttributes.xml

...
wmmAttributeName=""
pluginAttributeName=""
applicableMemberTypes="Person"
dataType="String"
valueLength="1024"
multiValued="false" />

3. Map this attribute in the wmmAttributes.xml file:

Windows/UNIX: You can locate the file in the following directory:

wp_rootshared/app/wmm/wmmAttributes.xml

i5/OS: You can locate the file in the following directory:

wp_user_rootshared/app//wmm/wmmAttributes.xml

...
wmmAttributeName=""
applicableMemberTypes="Person"
dataType="String"
valueLength="1024"
multiValued="true" />


Note: In Portal 6 the wmmAttributes.xml file in located in the /wmm directory.

---

B. How to add the field to People Finder:

1. Navigate to the following directory:

WebSphere\PortalServer\installedApps\PeopleFinder_PA_1_0_6L.ear\lwppeoplefinder.war\PdirConfig 
 

2. Modify the apPDirConfig.xml file and add your new attribute field.

a. Find this section in the xml file:



b. Add your field as either the first entry or last entry (Note: Be sure that it is wrapped in the outer tags new+old stuff )

example:

...

String
No
Yes
physicalOfficeName




c. Save the file.

To add a description to the new attributes fields, you need to perform several more steps (Note: As a precaution, please make necessary backup copy of files requiring changes):

1. Navigate to the directory:

WebSphere\PortalServer\installedApps\PeopleFinder_PA_1_0_6L.ear\lwppeoplefinder.war\WEB-INF\lib

Note: In Portal 6, the lwppeoplefinder.jar does not exist. The file is lwp.peoplefinder.jsr168.jar.

Note: In Portal 6, the PeopleFinderUI.properties file is located in a different location from that of Portal 5. Under WEB-INF instead of going to the lib directory for the jar file, go to classes\nls.

2. Modify the apPDirConfig.xml file and add your new attribute field:

a. Using WinZip, open and extract the lwppeoplefinder jar file to a designated folder you have created.
b. Open the extracted directory and open the nls directory.
c. Modify the PeopleFinderUI.properties file and add your field information.

i. First find this section of the properties file:

##########################################################
# WebSphere Member Manager Attributes: Each active field in the directory
# should have a Short Name, Long Name, and a description
##########################################################

ii. Then add below as the first or last entry (repeat as necessary for more than one new field attributes)
fieldname = short name
fieldname_Long = long name
fieldname_Desc = description

example:
physicalOfficeName = Name
physicalOfficeName_Long = Physical Delivery Office
physicalOfficeName_Desc = Physical Delivery Office

d. Save and zip the file as lwppeoplefinder.jar and replace it in the directory:

WebSphere\PortalServer\installedApps\PeopleFinder_PA_1_0_6L.ear\lwppeoplefinder.war\WEB-INF\lib

i. Select all the folders that were extracted: com, META-INF, nls
ii. Using an archiving utility (example: Winzip), compress the folders into the file name, lwppeoplefinder.jar.
iii. Place the new lwppeoplefinder.jar back into the directory.

3. Restart the Portal server.


Note: In one reported case, the customer had to extract the lwppeoplefinder war file and then made the above changes. Afterward, the customer archived all extracted files and named it as "lwppeoplefinder.war", and then updated the portlet module for the changes to appear.