cancel
Showing results for 
Search instead for 
Did you mean: 

connection from portal : portal system object : system template : MDM

Former Member
0 Kudos

Hi MDM-ers,

how are you doing?

my issue is a basic portal System template creation ( from a EP7.0 portal : SP13)

i am following the MDM Business Package Guide for MDM 5.5 SP05

section 1.2 Creating Portal System Objects for MDM

lists the tasks to create a system in the folder

the MDM System Template does not list any repositories in the dropdownlist once i enter the parameter:

MDM Server : AUSYDSAP07

password : <blank> / for user Admin

i can successfully log on using the MDM Data Manager to the selected repository

please guide me forth.

with respect,

amit

here are the errors logged

-


error 2007-12-18 15:34:11:265 at com.sap.mdm.commands.GetRunningRepositoryListCommand.execute(GetRunningRepositoryListCommand.java:52)

n/a System.err sap.com/irj AUSYDSAP09 Server 0 0_49125

error 2007-12-18 15:34:11:265 at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:112)

n/a System.err sap.com/irj AUSYDSAP09 Server 0 0_49125

error 2007-12-18 15:34:11:265 Caused by: com.sap.mdm.internal.protocol.manual.ServerException: File failed a crc check

n/a System.err

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member206107
Active Participant
0 Kudos

Hi Amith,

It is a crc check error.

The version of MDM Business package and the MDM server you are trying to connect are different.

Say if the version of MDM server is 5.5.46.25 (You can check the version of the mdm server in the mdm console. Focus on Root node ie., SAP MDM Server and you can find the version detail of the mdm server in the right hand side pane ie., MDM Servers) and the Business package you have deployed may belong to some other version say 41.65.

So please use the MDM business package content from the same version of MDM.

And follow the procedure given below to re-deploy the new business package.

Using the Software Deployment Manager (SDM) undeploy the following MDM

components, if they are contained in the Undeployment folder:

&#56260;&#56508; com.sap.pct.mdm.appl.packages.mdm_550

&#56260;&#56508; com.sap.pct.mdm.tech.packages.mdm_550

&#56260;&#56508; com.sap.pct.mdm.tech.systems

&#56260;&#56508; com.sap.pct.mdm.tech.wizards

&#56260;&#56508; com.sap.pct.mdm.appl.masteriviews

&#56260;&#56508; com.sap.mdm.tech.connector

&#56260;&#56508; com.sap.mdm.tech.mdm4j

&#56260;&#56508; com.sap.mdm.uwl

&#56260;&#56508; com.sap.mdm.uwl.config

3. Logon to the Portal as a system administrator and choose System Administration &#56256;&#56431;

Support &#56256;&#56431; Portal Run time &#56256;&#56431; Administration Console.

Remove the following archives, if they are there:

&#56260;&#56508; com.sap.pct.mdm.appl.masteriviews

&#56260;&#56508; com.sap.pct.mdm.tech.wizards

&#56260;&#56508; com.sap.pct.mdm.tech.sytems

&#56260;&#56508; com.sap.mdm.uwl

4. Using the SDM import the following files at once:

a. MDMJAVAAPI05_.sca

b. BPMDMTECHN05_.sca

c. BPMDMAPPLI05_.sca

Check the deployment logs to make sure the packages were imported successfully.

5. After deployment, restart J2EE/Portal using SAP Management Console.

6. Choose System Administration &#56256;&#56431; Support &#56256;&#56431; Portal Runtime &#56256;&#56431; Application Console

and refresh the services of application com.sap.mdm.uwl.

Now all the above software components are activated in the portal and their detailed version

information is displayed in J2EE system information.

All the best.

Warm regards,

Arun prabhu S