Generating an SCA from two SDAs?

[Former Member]

I am currently deploying two SDA libraries in Netweaver. These SDAs are built using the Netweaver IDE, and are sent to customers to deploy via the SDM remoteGui tool.

What I would prefer is to distribute a singe SCA that contains both SDAs, so that only one file needs to deployed via the remoteGui tool.

But how do I generate an SCA?

[Former Member · Accepted solution]

Hi,

If you are using NWDI, SCA files are created in the assembly phase for a determined Software Component, but I suppose that is not your case.

I recommend you to use NWDI, but you can try the following way to generate the SCA:

SCA files are files intended to deploy several SDAs and the structure of the file is simple:

- There is a folder named "deployarchives" with all SDAs

- Other folder with name "meta-inf" contains two files, Manifest.mf and Sap-manifest.mf, with information about the software component. If your SDAs don't belong to a Software Component, this folder meta-inf is not useful.

SCAs are intendend to deploy an entire Software Component.

To construct the file you must compress this two folders in a ZIP file. After that you can rename te file to .sca extension.

I hope this help.

Best Regards,

Jorge Linares

[Former Member · Accepted solution]

Thanks for the information on the structure of an SCA.

I am currently building an SDA manually using my own custom ant task (SAP provides a ant task that supposedly does something similar but I cannot find any documentation on its use), so I know how to generate SAP_MANIFEST.MF file (at least for an SDA).

I guess I will need to do something similar for an SCA, although I'm not sure yet what specific properties are required. My NetWeaver install does not have any .sca files so if you can post an example SAP_MANIFEST.MF from an .sca that would be appreciated.

Edited by: Geoffrey Elgey on May 19, 2008 1:22 PM

[Former Member · Accepted solution]

Hi,

Example of SAP-MANIFEST.MF (From SC SAP_JTECHF). I have reduced the number of SDAs to 2.

Manifest-Version: 1.0
TCSpra-Version: 20051021.1600
pr_buildarchivedir: 
pr_deployarchivedir: DEPLOYARCHIVES/CBSapi.sda;DEPLOYARCHIVES/SAPmdi.sda
keyname: SAP_JTECHF
keyvendor: sap.com
keylocation: SAP AG
keycounter: 1000.7.00.6.0.20060119105400
pr_cmskeycounter: 20060119105400
pr_softwarecomponentname: SAP_JTECHF
pr_softwarecomponentvendor: sap.com
pr_release: 7.00
pr_servicelevel: 6
pr_updateversion: 645_VAL_REL.060119
pr_type: SC
pr_deltaversion: F
pr_owner: Make
pr_patchlevel: 0
skipnwdideployment: true
componentelement: <componentelement  name="SAP_JTECHF" vendor="sap.com" componenttype="S
 C" subsystem="NO_SUBSYS" location="SAP AG" counter="1000.7.00.6.0.2006
 0119105400" scvendor="sap.com" scname="SAP_JTECHF" release="7.00" serv
 icelevel="6" patchlevel="0" deltaversion="F" updateversion="645_VAL_RE
 L.060119" componentprovider="SAP AG"/> 
JarSL-Version: 20050426.1600
compress: true

Name: DEPLOYARCHIVES/CBSapi.sda/
keyname: tc.CBS.API
keyvendor: sap.com
keylocation: SAP AG
keycounter: 7.0006.20050929162903.0000

Name: DEPLOYARCHIVES/SAPmdi.sda/
keyname: com.sap.mdi
keyvendor: sap.com
keylocation: SAP AG
keycounter: 7.0006.20050509171002.0000

Best Regards,

Jorge Linares

[Former Member · Accepted solution]

Thanks for the example SAP_MANIFEST.MF from an SCA file.

I hand-crafted an SCA that included two SDAs as per above but only one seems to be deployable.

It would be nice to have a reference document for the SCA layout.