Show TOC Start of Content Area

Background documentation createsda  Locate the document in its SAP Library structure

Use

By using this command, a Software Delivery Archive (SDA) is created based on a given Java EE-compliant archive. An SDA is a component uniquely identified by its name, vendor, location and counter. It may contain dependencies to other SDAs, defined by the vendor and the name of the referenced components. The origin archive must be one of the following Java EE types: J2EE, single-module or library.

Syntax

Syntax

createsda -name|-n DCName -vendor|-v DCVendor -location|-l buildLocation -counter|-c versionNumber -type architveType [-dependencies|-deps DCName] [-mfentries name] [-nocompression] [-softwarecomponentname|-scn SCName] [-softwarecomponentvendor|-scv vendorName] [-extensionsettings property] sourcefilename targetfilename

Options

 

-name|-n DCName

The name of the development component (DC).

-vendor|-v DCVendor

The vendor of the DC.

-location|-l buildLocation

The build location of the DC.

-counter|-c versionNumber

The version of the DC.

-type architveType

The Java EE type of the original archive. Possible values are:

      J2EE

      single-module

      library

[-dependencies|-deps DCName]

A comma-separated list of dependencies to other DCs. A referenced DC is defined by its vendor and name. Each dependency must be given in the following format:

<component vendor>:<component name>.

[-mfentries name]

A comma-separated list of manifest entries. Specify each entry in one of the following formats:

      <attribute entry>:<attribute name>:<attribute value>

for a given manifest entry

      <attribute name>:<attribute value>

for a manifest main entry

[-nocompression]

The resulting SDA is not compressed.

[-softwarecomponentname|-scn SCName]

The name of the associated software component (SC).

[-softwarecomponentvendor|-scv vendorName]

The vendor of the associated SC.

[-extensionsettings property]

A comma (,) separated list of properties that influence the behavior of the packaging tool. Specify each property in the following format: <property name>:<property value>

Arguments

 

sourcefilename

The name of the original SAP Java EE-compliant archive to be converted.

targetfilename

The name of the resulting SDA.

Note

Do not type the file extension.

Description

Creates a SDA based on a given Java EE-compliant archive.

Example

A SDA of type J2EE has to becreated based on the given Java EE application testapp.ear. The resulting SDA is named testappsda.ear and contains a reference to one other DC.

createsda –n tc/bl/testapp –v test.com –l testfactory –c 2 –type J2EE –deps test.com:tc/bl/testlib testapp.ear c:\result\testappsda

End of Content Area