Fix Readme
Abstract
This article provides information about the available fix pack for IBM Product Master Version 12.0. The article includes links to installation and upgrade instructions, prerequisites, and a description of the enhancements.
Content
General description
This fix resolves the APARs and defects that are listed in the Problems fixed section.
| Release name | 12.0 IPM-FP002 |
| Build ID | ipm_12.0.2_202012080837_update_from_12.0.0_202005050151.tar |
| Release date | 10/12/2020 |
Problems fixed
This fix addresses the following APARs.
| APAR ID | Description |
|---|---|
| JR60913 | Attributes with value rule set as timestamp get updated for all subcategories for check-in or checkout of the parent category. |
| JR61125 | If a catalog item is added to a new category and a new required attribute is filled, while saving a NULLPOINTEREXCEPTION is thrown. |
| JR61486 | Standard error page for JSPS. |
| JR61583 | Change the Db2 Data Definition Language (DDL) for the CAX and ITX table creations with the compress no option. |
| JR61592 | Docstore maintenance report does not delete files. |
| JR61655 | Old version maintenance scripts path incorrect in the IBM Knowledge Center link. |
| JR61662 | Enhancement of documentation is needed in the WebSphere MQ section for configuring connectivity with WebSphere MQ with the IBM Product Master. |
| JR61870 | Need to save workflow twice while creating workflow and tab view inside the workflow using script API. |
| JR61979 | In the Persona-based UI, the Save button is not getting enabled while selecting the date value. |
| JR62023 | Problem with selections having the same name. |
| JR62024 | Workflow step UI queries IBM Product Master. |
| JR62034 | The open button is not visible on the Workflow overview portal screen after selecting the row to open. |
| JR62058 | Importing attribute collection is incomplete when secondary specs contain an ampersand (&). |
| JR62074 | Two versions of metadata-extractor-x.x.x.jar can cause issues. |
| JR62131 | ACM is not working on the custom tool in the Persona-based UI. |
| JR62193 | MDMREST application server fails to startup because of the tika-1.9.jar in the IBM WebSphere Application Server Version 9.0.x. |
| JR62346 | Documentation to enhance the description of how searchable filter operates on the multi-edit page. |
| JR62431 | Persona-based UI: Response time is too high when a relationship type attribute is searched in the Persona-based UI. |
| JR62489 | Persona-based UI: The audit history tab displays the incorrect value. |
| JR62494 |
Admin UI: JDK uses "iw" for Hebrew instead of the new ISO standard "he".
Note: The new Hebrew locale (he_IL) currently is only applicable to the company attributes page. In the next release, the support would get extended to the Persona-based UI.
|
| JR62501 | Default rich search results report not working for a localized attribute in the group. |
| JR62544 | An abrupt server page occurs when you click a collaboration area associated with a workflow. |
| JR62606 | Wrong maximum length (3000 chars) for the rich text attribute. |
| JR62607 | The grid shows raw data, which contains HTML tags. |
| JR62608 | Single-edit page rich text attribute is unreadable. |
| JR62609 | Rich text attribute length issue. |
| JR62631 | Sample silent response file is missing the JDBC URL data key, in the ce_was_nd_oracle.xml or ce_was_nd_db2.xml file. |
| JR62669 | The Label selection field is reverting back to the previous label. |
| JR62686 | The default view name is not getting displayed in the right pane drop-down list. |
| JR62729 | IBM docstore maintenance report is not running. |
| JR62772 | A verbose error message was encountered during the security scan. |
| JR62818 | Added documentation in the IBM Product Master Fix Pack 1 readme to include import of the mdm-env.zip and dammodel.zip file. |
| JR62947 | Performance fixes for the category. |
| JR63020 | Post-processing script validation issue on the Persona-based UI. |
| JR63062 | Persona-based UI: Collaboration single-edit page, UI breaks when an item is categorized in a category, which has mandatory secondary attributes of grouping type. |
| JR63112 | Persona-based UI: On save if there is a validation error, then in the multi-occurring string enumeration rule, the first value in the drop-down list is displayed in all the occurrences. |
| MDMCE-I-171, MDMCE-I-199, MDMCE-I-236 | Persona-based UI: Displays 'flag' fields as a drop-down list. |
| MDMCE-I-233 | Persona-based UI: Search grid does not remember the column width on changing the criteria. |
| MDMCE-I-37 | Persona-based UI: Related items tab shows to and from relationships however, the relationship attribute name can cause confusion. |
Release highlights
- Added support for expressions predicate type in the Rules engine.
- Implementation of redirection to linked or related items from Linked items or Related items tab for the Single-edit page.
- Implementation of the Flag Attribute as a radio button on the Single-edit page.
- Security Assertion Markup Language (SAML v2.0) support for the Persona-based UI and Admin UI with windows and form authentication methods.
- Operator-based product deployment with container images.
- Official support of the Microsoft Edge browser for both the Admin UI and the Persona-based UI.
- Magento connector support upgrade from version 2.0 to version 2.4. For more information, see Magento2 connector.
- Persona-based UI and custom sample library supports Angular version 8. For existing custom components, upgrade your custom sample library. For more information, see Upgrading the existing custom sample library.
- Authentication is mandatory for MongoDB, thus you need to correctly enable authentication for Digital Assets Management and Machine learning. For more information, see Enabling MongoDB authentication.
- Secure Sockets Layer (SSL) support is available for MongoDB. For more information, see Enabling SSL for MongoDB.
- Persona-based UI supports password strength check, password expiry, and user lockout features. For more information, see common.properties file parameters.
- Admin UI supports a password strength check feature while creating or updating user information. For more information, see common.properties file parameters.
-
Elasticsearch upgrade:
-
Starting IBM Product Master 12.0 Fix Pack 1 release, the Elasticsearch version is upgraded to version 7.7.0.
-
Post Installation instructions
- You need to import the latest mdmce-env.zip, vendorportal.zip, and dammodel.zip files.
- Entries of the Completeness Lookup Table need to be saved after the mdmce-env.zip file import.
- If you run the configureEnv.sh script with no overwrite option, the existing mdmce-roles.json file gets retained and needs manual merge. But if you run the configureEnv.sh script with overwrite option,
- Backup of the existing mdmce-roles.json file gets created.
- The new mdmce-roles.json file gets created from its default file.
- The mongodb_username and mongodb_password properties in the env_settings.ini file are now used for both Digital Assets Management and Machine learning.
Properties
Following is the list of new or updated properties,
- common.properties
- enable_password_expiry
- enable_user_lockout
- force_strong_password_for_users
Note: On an Oracle environment, if you toggle the value of this property, and then modify the password, you need to restart the Free Text Search service. - maximum_password_attempts
- maximum_password_age_for_users
- maximum_password_age_for_vendor
- password_strength_criteria
For more information, see common.properties file parameters.
- dam.properties
- mongo.database
- mongo.password
- mongo.username
For more information, see dam.properties file parameters.
- damConfig.properties
- dam_catalog_linkagefile_header
- dam_collab_linkagefile_header
For more information, see damConfig.properties file parameters.
- mass-edit.properties
- batch_size
For more information, see mass-edit.properties parameters.
- restConfig.properties
- category_max_limit
For more information, see restConfig.properties file parameters.
Following is the list of deleted properties,
- dam_linkagefile_header
- maximum_password_age
- password_strength_criteria
Known problems and limitations
Note: The following limitations are only applicable to the new Angular 2 or REST services-based Persona-based UI.
- Rich Text (Persona-based UI) - When you open a Rich Text pop-up window in an editable mode, by default 'b' (bold) icon is enabled which is not required.
- Rich Text (Persona-based UI) - If a Rich Text attribute has no content and is in readable mode, you can still click its icon.
- Left navigation for nested menu [Reports] (Translation) - When you click the Dashboard menu, the report names are not translated even though the translation is available for every report.
- Filter - Value for a filter is not getting cleared from the text box even if you click Clear, but the filter box gets closed.
- Select category - Category value selected from the drop-down list versus selected from the category pop-up window shows different display formats. Zeros get truncated in case of selection from the drop-down list.
- Specs definition tab - In the Category single-edit page, the Cross button is in the disabled mode as it's not editable.
Prerequisites
- IBM Product Master 12.0
- Hardware and software compatibility: For information, see System requirements for the IBM Product Master
Modifying the database schema
Database schema migration is required. For more information, see Database schema migration.
Note:
- In case of any docstore-related error, rerun the migrateToInstalledFP.sh (migration) script.
- For the GDS feature, you need to perform database schema migration.
Installation instructions
For more information, see Installing the product.
Uninstallation instructions
Delete the $TOP folder and reinstall the IBM Product Master 12.0.
Was this topic helpful?
Document Information
Modified date:
27 April 2022
UID
ibm16365833