IBM WebSphere Business Modeler Publishing Server Version 6.0.2 Interim Fix 1

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

Installing the interim fix

The installation wizard for Interim Fix 1 is very similar to the installation wizard used to install WebSphere Business Modeler Publishing Server Version 6.0.2. The biggest difference between the two wizards is the interim fix wizard will ignore any role assignments you make. Instead, WebSphere Business Modeler Publishing Server Version 6.0.2 will use the existing role assignments. For the other fields in the installation wizard, use the same values you used when you installed WebSphere Business Modeler Publishing Server Version 6.0.2. Consult the Installation Guide for more information on these values.

Before you begin installing the interim fix, make sure all of the prerequisite servers are running.

To install WebSphere Business Modeler Publishing Server Version 6.0.2 Interim Fix 1:

1. Backup the following databases on the Lotus Domino Server:
• WBICOLWIPComment.nsf
• WBICOLWIPModel.nsf
• WBICOLWIPUser.nsf
• WBICOLReleaseModel.nsf
• WBICOLReleaseUser.nsf
2. Windows: Extract the installable files to a directory with sufficient space. In that directory, double click the WBModeler-PubServer602-iFix1.exe file.
   Linux: Extract the installable files to a directory with sufficient space. In that directory, enter the following command: ./WBModeler-PubServer602-iFix1.bin
3. Select the language that the installation wizard will use.
4. In the Welcome panel, click Next.
5. In the License Agreement panel, accept the terms and then click Next.
6. 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.
   
7. Type the path to the WebSphere Portal Server installation and then click Next.
8. In the Server Administrator page, type the Profile Name, 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 of the user names and passwords, consult the following settings in the <Portal install root>\config\wpconfig.properties file:
• WasUserid
• WasPassword
• PortalAdminIdShort
• PortalAdminPwd
9. 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, click Next. Do not make any role assignments. The installation wizard ignores any role assignments you do because WebSphere Business Modeler Publishing Server Version 6.0.2 will use the existing role assignments.
9. In the Application Deployment page, verify that the correct WebSphere Application Server instance hosts the Draft and the Released portal applications and that the Help port is correct. Click Next.
10. In the Lotus Domino information page,
    • In the Domino Server Name field, type the name of the Lotus Domino server (such as domino1).
    • In the Domain field, enter the domain of the Lotus Domino server (such as yourcompany.com).
    • In the IIOP Domino Port field, enter the DIIOP task port of the Lotus Domino server. For Windows, use the default of 63148. For Linux, use 60148.
    • In the Domino Administrator User Name and Password fields, enter the user name and password of a Lotus Domino Server administrator. The wizard uses this information to log onto the server and perform the installation.

    Click Next. A window that asks about replacing or reusing the databases opens.

11. Click Reuse. The wizard starts installing the interim fix.
12. Important: If you see messages about replacing more recent files with older files, click No To All.
13. Click Finish.
14. Stop the applications in the following order:
1. WebSphere Portal Server
2. WebSphere Application Server
15. 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
27431,111,000	JR25093	Creates database connections and does not release them
88576,L6Q,000 85556,L6Q,000	JR25122	Performance publishing large models
55273.689.864	JR25122	Performance of check box responses
55791,689,864	JR25122	Address in use exceptions
39323,531,864	JR23700	Displaying organization structure

This interim fix includes the following fix which is associated with APAR JR25122:

• Errors on publishing are propagated to the client