IBM WebSphere Business Modeler Publishing Server Version 6.0.1 Interim Fix 4

This interim fix applies to version 6.0.1 of WebSphere Business Modeler Publishing Server.

Installing the interim fix

Attention: If you have performed any role assignments using the administration of WebSphere Application Server or WebSphere Portal Server, these assignments are not preserved if you install Interim Fix 4. In the installation wizard, reusing role assignments means that the role assignments used when installing version 6.0.1 or Interim Fix 2 will be reused. Do not install this interim fix if you want to preserve the role assignments that were made in WebSphere Application Server or WebSphere Portal Server.

Some of the issues addressed by this interim fix require an update to WebSphere Business Modeler. Anyone who publishes to WebSphere Business Modeler Publishing Server must apply WebSphere Business Modeler Interim Fix 5 or later to their installation of WebSphere Business Modeler. Modeler Interim Fix 5 addresses the following issues:

PMR Number	Related APAR Identifier	Description
08842	JR23983	Fixes the displaying of while loops contents and other elements that contain diagrams (including sub-processes) larger than their parent process.

To install WebSphere Business Modeler Publishing Server Version 6.0.1 Interim Fix 4:

1. Backup the following databases on the Lotus Domino Server:
• WBICOLWIPComment.nsf
• WBICOLWIPModel.nsf
• WBICOLWIPUser.nsf
• WBICOLReleaseModel.nsf
• WBICOLReleaseUser.nsf
2. Double click the 6.0.1-WB-MPubServer-IF0000004.exe file.
3. In the Welcome panel, click Next.
4. Type the path to where WebSphere Business Modeler Publishing Server is installed and then click Next.
   
   Important: If the installation directory is not correct, the installation will fail without providing any warning or message about the failure.
   
5. Type the WebSphere Application Server administrator user name and password and the WebSphere Portal Server administrator user name and password. Click Next. If you are not sure what to type here, consult the following settings in the <Portal install root>\config\wpconfig.properties file:
• WasUserid
• WasPassword
• PortalAdminIdShort
• PortalAdminPwd
6. In the next page, select whether to reuse the role assignments from the previous installation (version 6.0.1 or Interim Fix 2) or to re-create the role assignments. Role assignment is where you assign users and groups to the administrator and publisher roles.
   
   Important: Replacing role assignments means that all existing role assignments are deleted and replaced with the role assignments you do later in this procedure. It is highly recommended that you select to keep the existing role assignments if at all possible.
   
   If you select to keep the existing role assignments, the wizard starts installing the interim fix. Skip steps 6 through 8 and go to step 9. If  you select to replace the role assignments, the LDAP Server Information page opens so that you can perform steps 6 through 8.
   
   Note: The last sentence in the panel is truncated. The full text reads:
   Ensure that you assign at least one user as an administrator and one user as a publisher.
   
7. In the LDAP Server Information page, provide the following information:
• In the LDAP URL field, type the URL and port number of the LDAP server. For example, type: ldap://Publishingserver.ibm.com:389
•  In the Server Bind DN field, type the user ID used to bind to the LDAP server. Consult the LDAPBindID setting in the wpconfig.properties file. For example, type: uid=wpsbind,cn=users,dc=ibm,dc=com
• In the Server Bind Password field, type the password of the LDAP bind ID. Consult the LDAPBindPassword setting in the wpconfig.properties file.
• In the Naming Attribute Holding User ID field, type the name of the prefix that precedes the user ID in the LDAP server database (such as cn or uid). The value of this parameter varies according to the type of LDAP server that you are using. Consult the LdapUserPrefix setting in the wpconfig.properties file.
• In the Naming Attribute Holding Group ID field, type the name of the prefix that precedes the group ID in the LDAP server database (such as cn or uid). The value of this parameter varies according to the type of LDAP server that you are using. Consult the LdapGroupPrefix setting in the wpconfig.properties file.
• In the Base of Search field, type the suffix that the LDAP server starts its search for the users.
• In the DN Attribute ID field, type the name of the distinguished name attribute ID. For example, type: uid
• If you filter the users returned from the LDAP query, in the Search Filter field, type an LDAP query.

Click Next.

8. In the Role assignment page, there are two fields with trees. The field on the left contains a tree of users and groups and the field on the right contains a tree of roles. Assign a user to the administrator role:

a. In the tree of users and groups, select the user node. The node changes to a expandable folder.

b. Expand the folder to see the users in contains.

c. Select a user for the administrator role.

d. In the tree of roles, select the Administrator node.

e. Click the > button to put the selected user in the role. The Administrator node changes to an expanded folder and contains the user you selected. The user is now an administrator.

f. Assign the users or groups you want to have administrator or publisher rights to the administrator or publisher roles. Assign at least one user as an administrator and one user as a publisher. The same user can perform both roles.

Tip: Use the >> to move all users or groups into a role. Use the < button to remove a user or group from a role.

9. Click Next. The wizard starts installing the interim fix.

10. Click Finish.
11. Stop the applications in the following order:
1. WebSphere Portal Server
2. WebSphere Application Server
12. Restart the applications in the following order:
1. WebSphere Application Server
2. WebSphere Portal Server

Updates and fixes

This interim fix includes the following fixes. The PMR and APAR numbers associated with each fix have been included.

PMR number	APAR number	Description
08842	JR23983	Fixes the displaying of while loops contents and subprocess bigger than their parent process. Important: You must install the corresponding WebSphere Business Modeler Interim Fix JR23938 to publish project implementing this fix.
55273,689,864	JR24193	Performance enhancements for checkboxes
24,037,033,000	JR24464	Fix task highlighting
18243,111,000	JR24472	Fix republishing authorization
18110,111,000		Performance enhancements
93,908,004,000		Field added to the install to allow users to apply a filter to the users/groups

Interim fix 4 includes the fixes of previous interim fixes.

The fixes in interim fix 3 are:

PMR number	APAR number	Description
55274,689,864	JR24194	Performance enhancements to publishing projects, viewing projects, and viewing users and groups

The fixes in interim fix 2 are:

PMR number	APAR number	Description
80054,227,631	JR23920	Fixes installation problem where roles could not be assigned to certain groups.
39520,531,864	JR23978	Improves performance in administering users and groups: Setting groups as the default view instead of users in the Users and Groups portlet Displaying the list of projects

In addition, the Welcome page now identifies the latest interim fix that has been applied. The fix for JR23552 in interim fix 1 has been enhanced so that the exported comments file contains the full path of the elements.

The fixes in interim fix 1 are:

PMR number	APAR number	Description
84178,999,000	JR23552	Updates the exported comments file to identify which element had its comments exported
39326,531,864	JR23617	Adds content that was missing from the Organization tab for diagrams
84042,999,000	JR23694	Updates the sorting of elements in the Project Tree to conform with the sorting used by WebSphere Business Modeler
39323,531,864	JR23700	Fixes the display of organization diagrams

This interim fix includes the following fixes, all of which are associated with APAR JR23661:

• Some connections were missing arrows.
• If the client's Windows is set to a Chinese locale, the attachment table removed the first character of an attachment name.
• Files attached to project elements could not be downloaded from the Released portal.
• Updates to Korean text.