MDM Portal Content deployment fail – MDM 7.1 SP02

July 1, 2009 at 5:04 pm

[] [] [] [] []

  1. Upgrade MDM 5.5 portal content from SP6 to MDM 7.1Symptom 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...
  2. How to find MDM 7.1 Portal Content build versionSymptom You would like to know the build number of the MDM 7.1 SCA portal software components (MDM_JAVA_API, BP_MDM_TECHNOLOGY, BP_MDM_APPLICATION .sca files) that: 1. You would like to install to your system...
  3. How to upload a MDM Portal iViews custom .PAR fileSymptom You have been requested by SAP support to upload a special customized .PAR file to your Portal environment. Other terms MDM, Portal, PAR, Custom Solution In order to upload the custom...
  4. MDM Portal iViews does not load large filesSymptom When trying to open large files (PDF, Word, Excel, Video, Music etc.) in MDM Portal iViews (either a Result Set or Item Details iView), the file is not accessisble and instead...
  5. MDM portal iViews – setting logging severitySymptom You would like to increase the logging severity for MDM Portal iViews component, but you can not locate the relevant location in the Visual Admin Log Configurator Other terms MDM, iViews,...
  6. MDM Portal iViews display issue with Arabic languageSymptom You have created an MDM Item details iView and trying to display it with Arabic as the display language. However, the iView is not displayed correctly. Other terms Arabic, Item Details,...
  7. Dates and numbers formatting – MDM standard iViewsSymptom Date and numbers format do not match the user regional setting Other terms Date, Currency, Real, MDM, Portal, iView Reason and Prerequisites MDM Standard Portal iViews formatting of dates and numbers...
  8. MDM Change tracker (Web UI) tuple limitations in 7.1 SP00/01Symptom When using MDM 7.1 SP00/SP01, after making changes to the tuple field for a specific record, The permanent ids within the change history table are populated inconsistently. This results in the...

Symptom
You are trying to update your MDM Portal content or the MDM Java API to MDM 7.1 SP02 Patch03 or a higher version and receive the following deployment error:
SDM has not calculated any deployment actions.
Possible reasons:
All selected archives have already been deployed before in the same or in a higher version.
Other terms
MDM, Portal, SRM-MDM, Content, SCA, SDM, JSPM, MDM_JAVA_API
Reason and Prerequisites
MDM Portal Content BP Application and BP Technology SCA files and the MDM Java API SCA have a SAP_MANIFEST.MF file in each of them. Because of a technical issue, the SAP_MANIFEST.MF files from earlier versions of these SCA files (7.1 SP02 P00 and P01) have the “release” property set to “7.10″ instead of “7.1″. This is why the JSPM and the SDM tools are not able to deploy the files (as it takes into account that the “7.10″ is in a higher version the “7.1″ which is of course not correct).
Solution
You can deploy the new Portal content and the new Java API without having to undeploy the old content and without using SDM (in NetWeaver 7.0) or JSPM (in NetWeaver 7.1), via the following procedure:
1. Put SCA files that you wish to deploy in an accessible location on the hard drive, where the path does not contain spaces or similar problematic characters. You will need full rights for these files in order to deploy them.
For example:
/tmp/deploy
Or
c:\tmp\deploy

2. Connect to the engine via telnet and logon as J2EE admin user:
telnet <HOST> 5<INSTANCE_NUMBER>08
For example:
telnet localhost 50408

3. Type:
deploy <DIR_WHERE_SCAs_ARE_PLACED> version_rule=all
For example:
deploy c:\tmp\deploy version_rule=all

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment