IBM WebSphere Business Modeler Publishing Server Version 6.0.2 Interim Fix 3
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 3 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 uses the existing role
assignments. For this reason, the LDAP page and the role assignment page do not
open in the wizard. For the other pages 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 3:
- Backup the following
databases on the Lotus Domino Server:
- WBICOLWIPComment.nsf
- WBICOLWIPModel.nsf
- WBICOLWIPUser.nsf
- WBICOLReleaseModel.nsf
- WBICOLReleaseUser.nsf
- Windows: Extract the installable files to a directory with sufficient space. In that directory, double click the
WBModeler-PubServer602-iFix3.exe file.
Linux: Extract the installable files to a directory with sufficient
space. In that directory, enter the following command:
./WBModeler-PubServer602-iFix3.bin
- Select the language that the
installation wizard will use.
- In the Welcome panel, click
Next.
- In the License Agreement
panel, accept the terms and then click Next.
- 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.
- Type the path to the
WebSphere Portal Server installation and then click Next.
- 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
Click Next.
- 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. The
wizard starts installing the interim fix.
- Important: If you see messages about replacing more recent files with older files,
click Yes To All.
- Click Finish.
- Stop the applications in
the following order:
- WebSphere
Portal Server
- WebSphere
Application Server
- Restart the applications in
the following order:
- WebSphere
Application Server
- 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
|
|
56624,689,864 |
JR25551 |
Administration portals are not displaying the entire user name |
|
56687,689,864 |
JR25593 |
Group user access not working |
|
44661,500,000 |
JR25474 |
Unable to publish projects with attachments |
|
56666,689,864 |
JR25524 |
Out of memory exceptions |
This interim fix also includes the following fixes which are associated with APAR
JR25603
- The Model Elements portlet can now display diagrams in swimlane layouts. If
a diagram has been opened in one or more swimlane layouts in WebSphere
Business Modeler 6.0.2, a publisher has the ability to publish some or all
of the swimlane layouts for the diagram. For more information on this
publishing functionality, refer to the WebSphere Business Modeler 6.0.2
help. To support displaying swimlane layouts, when the Model Elements
portlet displays a process diagram, you can select the diagram layout using
the Layout type field. The default layout type is free-form layout.
Note: If the Layout type field does not list the swimlane
layout that you want, the layout type was not published.
- Business services and business service objects are new elements in
WebSphere Business Modeler 6.0.2. They are publishable and are contained in
the external model catalog. Business services are model representations of
WSDL files and business service objects are model representations of XSD
files. For more information on these elements, see the WebSphere Business
Modeler Publishing Server documentation.
- Replacement of view switching buttons in the administration pages for tabs
that read "<portal name> portal user administration" and "<portal
name> portal data administration"
- The Descriptions fields in Attributes portal can now contain active
hyperlinks
Interim fix 3 includes the fixes of previous interim fixes.
Notes
This interim fix contains new untranslated content in the user interface and
in the help system. A later interim fix will provide translations for this
content.
Previous interim fixes
The fixes in interim fix 2 were:
|
PMR number
|
APAR number
|
Description
|
|
55791,689,864 |
JR24737 |
Access rights fail for Active Directory if the DN contains an
escaped comma
Permission on groups being pushed to users in large active directory
implemenations
Performance improvements in authorization pages |
|
56349,689,864 |
JR25422 |
Improved permission page performance on non set elements |
|
56428,689,864 |
JR25422 |
Memory usage improvements |
|
56433,689,864 |
JR25422 |
Persistence for user profiles with back slash (\) in the name |
This interim fix also includes the following fixes which are associated with APAR JR25422:
- Performance improvement for deleting projects
- Changes to publish to allow it to continue should in the event of a corrupt element
- Consistency of user profiles database keys (case sensitivity)
- Additional check on database records should they contain empty strings
- Clean profile trees before saving
- Performance improvements on project deletion
- Improved LDAP query to handle NamingException
- Improved LDAP query for names with strange chatracters including back and forward slashes
- Improved tracing
The fixes in interim fix 1 were:
|
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