IBM WebSphere Business Modeler Publishing Server Version 6.0.1 Interim Fix 2

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

Installing the interim fix

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 1a or later to their installation of WebSphere Business Modeler. Interim Fix 1a addresses the following issues:

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

1. Double click the 6.0.1-WB-MPubServer-IF0000002.exe file.
2. In the Welcome panel, click Next.
3. 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.
    
4. 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
5. 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

   Click Next.

6. 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:
   1. In the tree of users and groups, select the user node. The node changes to a expandable folder.
   2. Expand the folder to see the users in contains.
   3. Select a user for the administrator role.
   4. In the tree of roles, select the Administrator node.
   5. 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.
   6. 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.

7. When you have finished assigning users, click Next. The wizard starts installing the interim fix.
8. Click Finish.
9. Stop the applications in the following order:
   1. WebSphere Portal Server
   2. WebSphere Application Server
10. 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.

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.

Interim fix 2 includes the fixes of interim fix 1. The fixes in interim fix 1 are:

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.