SAP EP – Netweaver Portal

Symptom

After upgrading the MDM Server and its repositories from MDM 5.5 SP6 to MDM 7.1, the portal MDM iViews show runtime errors.

Other terms

MDM 5.5 55 7.1 7.10 710 SP6 SP06 Upgrade iView portal content UWL Universal Worklist Workflow

Reason and Prerequisites

Reason
——
The version of portal content must match the version of back-end MDM Server.
The mapping of portal user to repository user does no longer work.
Prerequisites
————-
1. Portal shows content still running on MDM 5.5 SP6.
The MDM portal content can be originated from the shipped SAP MDM portal content, or any custom portal content developed on top of the shipped SAP MDM iView Templates.
Hint: it is necessary to make sure the MDM 5.5 SP6 iViews (and UWL, if used) are operational and show content originated from MDM 5.5 SP6 repositories (e.g. no runtime error in iView) before the upgrade – otherwise, after upgrading to MDM 7.1 the iViews can show the same error. For the next requirements, make a note of the repository user/password that was set in portal user mapping.
2. if there is portal content in SAP name space that was changed, then there is no automatic mechanism to protect the customer changes made in SAP name space: in the MDM 7.1 Portal Content Configuration guide is recommended the customer must use own name space (for example com.company.pct.mdm). SAP reserves the right to update any MDM Portal content in name space com.sap.pct.mdm.* and/or com.sap.mdm.*. Therefore, if there are such custom changes in SAP name space, then please make a note of them, and re-apply the change after upgrade (if the case).
3. upgrade the MDM Server and its repositories from MDM SP6 to MDM 7.1.
Hint: before upgrading the MDM 5.5 SP6 repositories, make sure all workflow jobs/tasks are closed/deleted – otherwise, after upgrading to SP6, the MDM Universal Worklist (UWL) can give errors when processing an MDM job/task in UWL.
4. after repository upgrade to MDM 7.1, the content of the repositories can be displayed and maintained using MDM Data Manager with the same repository users as mentioned above at no. 1.
5. the MDM 7.1 Java software component archive Name_<SP>_<Build>.sca files were downloaded from SAP Marketplace and they are available – for example:
MDMJAVAAPI01_36.sca – SAP MDM Java API
BPMDMTECHN01_36.sca – SAP MDM PCT Content for Technology (business package for technology)
BPMDMAPP01_36.sca – SAP MDM PCT Content for Application (business package for application).
6. required user access: portal system administration, software deployment manager (SDM), SAP Management Console.
7. Custom developed application using MDM Portal iViews custom events for communicating with MDM Portal iViews, need to have their code reviewed, since a fix implemented in 7.1 may require adjusting your custom code. For details, refer to SAP Note 1018470 describing the changed behavior.
Solution

Steps to follow
—————
After the prerequisites are fulfilled, please proceed with the following steps:
1. logon to JSPM, and Deploy all three SCA files from MDM 7.1 installation package, for example:
MDMJAVAAPI01_36.sca
BPMDMTECHN01_36.sca
BPMDMAPP01_36.sca
Hints:
The J2EE/Portal System Information shows the ‘550′ suffix for business packages. Since no new predefined content was shipped with business packages in MDM 7.1, the ‘550′ is retained to reflect this fact and has not been changed. The naming convention not using the ‘7.1′ notation has no adverse functional implications.
2. in SAP Management Console, restart the system of J2EE/Portal.
3. manual operations in portal after Upgrade:
3.1. if using UWL, then check if the MDM UWL Content Configuration xml file is activated:
logon to portal with admin access, navigate to System Administration -> Support -> Portal Runtime -> Application Console -> select com.sap.mdm.uwl, and refresh the service.
check the UWL Content Configuration file is activated:
navigate to System Administration -> System Configuration -> Universal Worklist Administration -> below Universal Worklist Content Configuration click on “Click to Manage Item Types and View Definitions” -> on the list of Current Configurations select the configuration named mdm.
If the tag <Actions> is visible, then the MDM 7.1 UWL configuration file is activated.
If the tag <Actions> is not visible, then:
from file BPMDMAPP01_36.sca, extract the file com.sap.mdm.uwl.sda,
from file com.sap.mdm.uwl.sda, extract the file com.sap.mdm.uwl.par,
Upload the com.sap.mdm.uwl.par file (System Administration -> Support -> Portal Runtime -> Administration Console -> Archive Uploader.
3.2. if it happened to change any portal content in SAP name space, then, as advised above at Prerequisites, the same change must be applied again.
3.3. Log onto the portal as a content administrator and navigate to Content Administration -> Portal Content -> Content Provided by SAP -> Specialist.
The MDM Application subfolder contains the iViews, pages, and so on, listed in this business package documentation.
The MDM Technology subfolder contains the system template.
Refresh the Portal Content folder to make sure that the imported iView and system templates are activated and cached. Otherwise empty pages are displayed or you cannot create system objects.
Now all software components are activated in the portal, their detailed version information is displayed in J2EE system information, and they are activated in J2EE/Portal runtime.
3.4. notify the users to delete the internet browser’s history and temporary internet files before logon to Portal.
4. in SAP Management Console restart the MDM 7.1 Server and reload the repositories.
Using the same repository user/password as mentioned above at Prerequisites no. 4., the record maintenance is possible using MDM Data Manager.
Now the MDM iViews and the UWL should display content from repositories without errors as it was before upgrade. Otherwise please create an OSS message to SAP in component EP-PCT-MDM (see attached SAP Notes what would be the required information).