How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM

[Former Member]

Hello everybody,

We assemblied a sca file in NWDI when we finished development.

But when we used RemoteGUI to deploy the SCA file in another NetWeaver2004s engine.The Deploy order is wrong.The SDM doesn't first deploy the Library,EAR.It deployed the SDA ordering by the letter order ,not the dependence order.

For example,there are two SDA in the SCA file, one's name is <b>d_lib</b>,another name is <b>a_ear</b>.The a_ear depend on the d_lib.When SDM deploy the SCA,it first deploy the a_ear,not d_lib.

How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM?

[Former Member]

Make sure your DC's have the correct Deploy-time dependency (check the Used DC definitions).

[Former Member]

Hi Pascal,

Thanks for you help.

It's sure that our DC's have the correct Deploy-time dependecy when we created the DCs in the NWDS.

And i found a post message in the forum,

But i didn't understand the answer ?how to configure the SAP_MANIFEST.MF file?

[Former Member]

You don't configure the SAP_MANIFTEST.MF file, it is automatically written by the DC build based on the DC metadata. I'd check:

1. There really is a deploy-time dependency from a_ear to d_lib

2. After build there should be some entry in the SAP_MANIFEST file of the a_ear that indicates ( dependencylist: <dependency keyname="d_lib" keyvendor="your.dot.com" /> or something similar)

3. Are there warnings regarding dependencies in the build log or a_ear?

Regards,

Marc

[Former Member]

Hi Marc,

Thanks for your help.

I found the SAP_MANIFEST file of the Object,the content is:

Manifest-Version: 1.0

Ext-SDM-SDA-Comp-Version: 1

softwaretype: J2EE

JarSAP-Version: 20041217.1600

JarSAPProcessing-Version: 20060104.1634

deployfile: sda-dd.xml

keyname: om/base/ear

keyvendor: pjs.com

keylocation: NWD_omv1.2_C

keycounter: 5199

componentelement: <componentelement name="om/base/ear" vendor="pjs.com" componenttype="

DC" subsystem="NO_SUBSYS" location="NWD_omv1.2_C" counter="5199" scven

dor="praxisolution.com" scname="OM" deltaversion="F" updateversion="LB

-20070813122826" componentprovider="NWD"/>

dependencies: <dependency dependencyType="GLOBAL" Specification-Title="om/library"

Implementation-Title="om/library" Implementation-Vendor-Id="pjs.com" /

>

dependencylist: <dependency keyname="om/library" keyvendor="pjs.com" />

JarSL-Version: 20060518.1400

compress: true

<b>But I don't the 3rd point:

Are there warnings regarding dependencies in the build log or a_ear?

Where is the log?I just used the NWDI to assembled the SCA file?</b>

[Former Member]

Hi,

well, both the "dependencies" and the "dependencylist" entries point to some "om/library" which I assume is your d_lib. So that looks good and checking the build log is not necessary.

(To find the build log anyway: Go to the CBS WebUI and navigate to the appropriate build space and DC. In the lower pane there's a tab "Build Status" which should have a link for the request and the build log.)

Given that the dependency is listed in the SAP_MANIFEST I'm baffled as to what the problem is. If the Library was created using default NWDI means the provider.xml in there should be created by the build and the name should exactly match the reference here...

Regards,

Marc

[Former Member]

Hi,

In the SCA file i couldn't find the <b>Provider.xml</b>.And my NWDI's version is 700,the NW version is 2004s SP10.

Thanks your help!

[Former Member]

Hi,

the provider.xml is the runtime descriptor for a J2EE Library (comparable to the application-j2ee-engine.xml for J2EE Applications/EARs). There should be one in the SDA (not SCA) of your library.

As far as I know this behaviour that the provider.xml for libraries is created by the build was already in 6.40/NW04.

Regards,

Marc

[Former Member]

Hi Marc,

Thanks for your help!

I found the Prodiver.xml,and the content is:

<?xml version="1.0" encoding="utf-8" ?>

- <provider-descriptor>

<display-name>om/library</display-name>

<component-name>om/library</component-name>

<description />

<major-version>7</major-version>

<minor-version>00</minor-version>

<micro-version>0</micro-version>

<provider-name>pjs.com</provider-name>

- <jars>

<jar-name>pjs.com_omwcalist_{wcalist_dao}WcalistPackage.jar</jar-name>

<jar-name>pjs.com_omlog_equipdao~daoPackaged.jar</jar-name>

<jar-name>pjs.com_omnotification_{notification_dao}NotificationPackage.jar</jar-name>

<jar-name>pjs.com_ombase_daodaoPackaged.jar</jar-name>

<jar-name>pjs.com_omlogarea_areadaopackaged.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}PostPackage.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}SpecialtyPackage.jar</jar-name>

<jar-name>pjs.com_omtask_daopackaged.jar</jar-name>

<jar-name>pjs.com_omgradeproject_gradedaopackagSDA.jar</jar-name>

<jar-name>pjs.com_omlogrecon_lredaopackaged.jar</jar-name>

<jar-name>pjs.com_omsafe_excepreportExcepReportPackage.jar</jar-name>

<jar-name>pjs.com_omsaferecord_daoapi.jar</jar-name>

<jar-name>pjs.com_omlogelog_elogdaopackaged.jar</jar-name>

<jar-name>pjs.com_omsys_daopackaged.jar</jar-name>

<jar-name>pjs.com_ombasevind_basedaopackaged.jar</jar-name>

<jar-name>pjs.com_omlog_searchpersondao~SearchPersonSDA.jar</jar-name>

<jar-name>pjs.com_omplacard_daoplacardPackaged.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}PersonPackage.jar</jar-name>

<jar-name>pjs.com_omsbillrecord_daosbillRecordPackaged.jar</jar-name>

<jar-name>pjs.com_omdutyperson_dao~DutyPersonSDA.jar</jar-name>

<jar-name>pjs.com_omrpt_daoRptSDA.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}EquipmentPackage.jar</jar-name>

<jar-name>pjs.com_omlogtype_logdaopackaged.jar</jar-name>

<jar-name>pjs.com_omsafe_{proeval_dao}ProEvalPackage.jar</jar-name>

<jar-name>pjs.com_ompersonpost_daopackaged.jar</jar-name>

<jar-name>pjs.com_omlog_searchlogdao~SearchSDA.jar</jar-name>

<jar-name>pjs.com_ompublic~packaged.jar</jar-name>

<jar-name>pjs.com_omspellgroup_daodaoPackaged.jar</jar-name>

<jar-name>pjs.com_omlog_personlogdao~packaged.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}RlogPackage.jar</jar-name>

<jar-name>pjs.com_omschedule_dao~ScheduleSDA.jar</jar-name>

<jar-name>pjs.com_omreport_rptdaopackaged.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}RecordClassPackage.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}ReqpPackage.jar</jar-name>

<jar-name>pjs.com_omlog_shiftclassdao~ShiftClassSDA.jar</jar-name>

<jar-name>pjs.com_omverify_recorddao~RecordPackage.jar</jar-name>

<jar-name>pjs.com_omunit_dao~UnitSDA.jar</jar-name>

<jar-name>pjs.com_omdatadefine_defdaopackaged.jar</jar-name>

<jar-name>pjs.com_omheader_dao~HeaderSDA.jar</jar-name>

<jar-name>pjs.com_omspell_spedaopackaged.jar</jar-name>

<jar-name>pjs.com_omlogrecd_lcddaopackaged.jar</jar-name>

<jar-name>pjs.com_omlog_searchequip_dao~SearchEquipSDA.jar</jar-name>

<jar-name>pjs.com_omcompany_comdaopackaged.jar</jar-name>

<jar-name>pjs.com_ommac_easyformdao~daoJAR.jar</jar-name>

<jar-name>pjs.com_omdeclare_decdaopackaged.jar</jar-name>

<jar-name>pjs.com_ompost_{post_dao}FunlcodePackage.jar</jar-name>

<jar-name>pjs.com_omlogevent_levdaopackaged.jar</jar-name>

<jar-name>pjs.com_omclient_dao~ClientSDA.jar</jar-name>

<jar-name>pjs.com_omlogdep_ldedaopackaged.jar</jar-name>

<jar-name>pjs.com_omlogceqp_lceqdaopackaged.jar</jar-name>

<jar-name>pjs.com_omrptinfo_rptdaopackaged.jar</jar-name>

</jars>

</provider-descriptor>

I checked it and didn't find any error! What can i do?

[Former Member]

Wow, lots of jars.

Well, the <provider-name> and <component-name>/<display-name> of the library match the information in the SAP_MANIFEST of the ear as far as I can tell, so I would assume that deployment should pick up the library first and then the ear.

Is there some hint in the deployment log why the order isn't kept? Otherwise I would assume some bug in deployment and open an OSS message.

Regards,

Marc