Empty list when attempting Check-in of MDM_JAVA_API

[Former Member]

Hi,

In NWDI we are setting up a track for development of a custom Java EE

application which will use the MDM_JAVA_API in order to communicate

with an MDM system.

The product and Software component(SRM_JEE_MDM) have been

defined in SLD and the Software component has a buildtime dependency to

MDM_JAVA_API version 550.

In the NWDI system a track (ZSRMMDM7) has been create with a single

software component for development SRM_JEE_MDM. When this was added

four required software components were automatically added; SAP-JEE,

SAP_BUILDT, SAP_JTECHS and MDM_JAVA_API (version 550 , not 5.50). Exclude from

deployment is not checked for any of them.

In NWDI the root transport directory is /usr/sap/trans/JTrans and the

check-in directory for archives is set to inbox. Therefore the .SCA

files for the MDM_JAVA_API have been added to the

folder /usr/sap/trans/JTrans/CMS/inbox/. I've added both patch 2 and

patch 4 of this SCA with names MDMJAVAAPI05_2.SCA and

MDMJAVAAPI04_4.sca.

The system has been restarted after these files have been placed here

(even though I don't believe that is necessary)

When I go to the check-in for the track (ZSRMMDM7) I see the SAP-JEE,

SAP_BUILDT and SAP_JTECHS SCs which are also in the inbox folder on the

file system, but MDM_JAVA_API is not in this list and therefore I

cannot import the MDM_JAVA_API into the track so that the API is

available from NetWeaver developer studio.

I assume NWDI reads the SAP_manifest from each of the .SCA files in the

check-in folders and compares them with the track's required SCs. I've

added the manifest for MDM_JAVA_API patch 2 to this OSS.

I would assume the problem here is a wrong manifest and that therefore

NWDI doesn't match MDM_JAVA_API SCA file with the SC definition in the

track.

Manifest for MDM_JAVA_API patch 2

Manifest-Version: 1.0

ExportSC-Version: 20050426.1600

Softwarecomponent-Ppmsnumber: 01200615320200008198

keyvendor: sap.com

keyname: MDM_JAVA_API

keycounter: 1000.5.50.5.2.20070830112759

keylocation: SAP AG

release: 5.50

SP-Number: 5

SP-Patchlevel: 2

Softwarecomponent-Vendor: sap.com

Softwarecomponent-Name: MDM_JAVA_API

scacreationmode: LCR

Softwarecomponent-Version: 5.50

directory-sca: true

componentelement: <componentelement name="MDM_JAVA_API" vendor="sap.com" componenttype=

"SC" subsystem="NO_SUBSYS" location="SAP AG" counter="1000.5.50.5.2.20

070830112759" scvendor="sap.com" scname="MDM_JAVA_API" release="5.50"

servicelevel="5" patchlevel="2" deltaversion="F" scelementtypeid="0120

0615320200008198" componentprovider="SAP AG"/>

JarSL-Version: 20050901.1731

compress: false

Name: com.sap.mdm.tech.connector.sda/

keyname: com.sap.mdm.tech.connector

keyvendor: sap.com

keylocation: SAP AG

keycounter: 5.50.20070830111049.0000

Implementation-Title: com.sap.mdm.tech.connector

Implementation-Vendor-Id: sap.com

Implementation-Version: 5.50.20070830111049.0000

Specification-Title: SAP MDM Connector

Specification-Vendor: SAP AG

Specification-Version: 5.5.5.2

Implementation-Vendor: SAP

componentelement: <componentelement name="com.sap.mdm.tech.connector" vendor="sap.com"

componenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="5.

50.20070830111049.0000" scvendor="sap.com" scname="EP-PSERV" deltavers

ion="F" updateversion="LB-20070830112756" componentprovider="SAP AG" s

ervertype="P4" sourceserver="perforce4001.wdf.sap.corp:4001" changenum

ber="108456"/>

Name: com.sap.mdm.tech.mdm4j.sda/

keyname: com.sap.mdm.tech.mdm4j

keyvendor: sap.com

keylocation: SAP AG

keycounter: 5.50.20070830111049.0000

Implementation-Title: com.sap.mdm.tech.mdm4j

Implementation-Vendor-Id: sap.com

Implementation-Version: 5.50.20070830111049.0000

Specification-Title: SAP MDM Java API

Specification-Vendor: SAP AG

Specification-Version: 5.5.5.2

Implementation-Vendor: SAP

componentelement: <componentelement name="com.sap.mdm.tech.mdm4j" vendor="sap.com" comp

onenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="5.50.2

0070830111049.0000" deltaversion="F" updateversion="LB-20070830112757"

componentprovider="SAP AG" servertype="P4" sourceserver="perforce4001

.wdf.sap.corp:4001" changenumber="108456"/>

Regards

Dagfinn Parnas

[Former Member · Accepted solution]

Does the SCA contain a 'buildarchives' folder with .dcia files? If not, then it's not an SCA for NWDI usage.

[Former Member · Accepted solution]

Hi Pascal,

You are correct, there are no .dcia files inside the SCA.

Structure is:

com.sap.mdm.tech.connector.sda

com.sap.mdm.tech.mdm4j.sda

meta-inf\Manifest.mf

meta-inf\SAPManifest.mf

Do you know if there is a location (probably under service.sap.com/swdc) where you can download NWDI ready SCA files for SAP Application components ?

Regards

Dagfinn

[Former Member · Accepted solution]

If SCA's are NWDI ready, the necessary files should already be inside the SCA. Since this is not the case for this SCA, I don't think it's available. You'll probably have to follow the procedure in the weblog below, using External Library DC's to store the MDM jars in the DTR: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5592. [original link is broken] [original link is broken] [original link is broken]