Importing Applications Created with Previous Releases of SAP NetWeaver Developer Studio

Importing Standard Java EE Applications

For standard Java EE application on development component (DC) structure, proceed as follows:

1. Generate SOA configuration for connectivity data in the EJB Module DC or Web Module DC.

   For more information about SOA configuration for connectivity, see Configuring Groups of Web Service Clients .

2. Remove the following redundant DC dependency from the EJB DC or Web DC: tc/bi/mctech .

   Old SOA configuration for connectivity build extension DC for generating *.cfgar file.

3. Remove the following redundant DC public part from the EJB DC or Web DC: mcjar .

   Old SOA configuration for connectivity public part used to package the *.cfgar file into the EAR archive.

4. Add the following DC dependencies from the EJB DC or Web DC to enable the Service Component Description Language (SCDL) files generation:

   • bie/sca/scdl/gen

     The generic SCDL generation procedure.

   • bie/sca/scdl/gen/mc

     Utility DC used by the SCDL generation contributors to generate SCDL references in a unified way.

   • bie/sca/scdl/gen/util

     Utility DC used by the SCDL generation contributors to share/reuse common technical implementations.

   • bie/sca/scdl/contributors/mc

     Contributor DC, which generates the Service Groups metadata in the SCDL file.

   • bie/sca/scdl/contributors/sa for EJB DCs only.

     Contributor DC, which generates SCDL data for EJBs annotated with @UsedReferences (SA use case).

   • bie/sca/scdl/contributors/ejb for EJB DCs only.

     Contributor DC, which generates SCDL data for EJBs annotated with @WebServiceRefs , @WebServiceRef (JAX-WS proxies consumed in EJB use case).

   • bie/sca/scdl/contributors/web for Web DCs only

     Contributor DC, which generates SCDL data for Servlets annotated with @WebServiceRefs , @WebServiceRef (JAX-WS proxies consumed in Web use case).

   Those DCs could be found in software component COMP_BUILDT.

5. Add the following entities only to the EJB DC public part ejbjar :

   EJB DC Name

   Composite Descriptor Entity

   Composite Descriptor Entity Description

   Composite Entity

   EJB DC Name

   Xlf2Prop Descriptor Entity

   Xlf2Prop Descriptor Entity Description

   Xlf2Prop Entity

6. Add the following entity only to the Web DC public part war :

   Web DC Name

   Xlf2Prop Descriptor Entity

   Xlf2Prop Descriptor Entity Description

   Xlf2Prop Entity

7. Build the EJB DC or Web DC and check in the EJB jar file or Web jar file that is produced there for the following existing files:

   • *.composite - only one file with this extension should exist in the META-INF folder of the jar.

   • sca-contribution.xml - only one file with this extension should exist in the META-INF folder of the jar.

8. Add in the EAR DC a dependency to the following DC: bie/sca/contributionxml/gen.

   Build extension DC that generates the sca-contribution.xml file in the EAR archive under ./META-INF folder.

9. Build the EAR DC and check in the produced archive for the following files:

   • sca-contribution.xml - only one file with this extension should exist in the META-INF folder of the EAR archive.

   • *.composite - only one file with this extension should exist in the META-INF folder of the module jar.

   • sca-contribution.xml - only one file with this extension should exist in the META-INF folder of the module jar.

10. Deploy and run the application in SAP NetWeaver Administrator.

Importing SAP Applications

For SAP application DC structure (for example, Galaxy, Web Dynpro, Service Adaptation, and so on), proceed as follows:

1. Generate SOA configuration for connectivity data in the SAP proprietary DC.

   For more information about SOA configuration for connectivity, see Configuring Groups of Web Service Clients .

2. Remove the following redundant DC dependency from the SAP proprietary DC: tc/bi/mctech

   Old SOA configuration for connectivity build extension DCfor generating *.cfgar file.

3. Add the following DC dependencies from the EJB DC to enable the SCDL files generation:

   • bie/sca/scdl/gen

     The generic SCDL generation procedure.

   • bie/sca/scdl/gen/mc

     Utility DC used by the SCDL generation contributors to generate SCDL references in a unified way.

   • bie/sca/scdl/contributors/mc

     Contributor DC, which generates the Service Groups metadata in the SCDL file.

   Those DCs could be found in software component COMP_BUILDT.

4. Depending on the use case you have to add a DC dependency from the SAP proprietary DC to one of the following contributor DCs:

   • bie/sca/scdl/gen/util

     Utility DC used by the SCDL generation contributors to share or reuse common technical implementations (SA use case).

   • bie/sca/scdl/contributors/sa

     Contributor DC, which generates SCDL data for EJBs annotated with @UsedReferences , @SDOService (SA use case).

   • bie/sca/scdl/contributors/glx

     Contributor DC, which generates SCDL data for Galaxy processes (Galaxy use case).

   • bie/sca/scdl/contributors/wd

     Contributor DC, which generates SCDL data for Web Dynpro AWS Models (Web Dynpro Connectivity use case).

   Those DCs could be found in software component COMP_BUILDT or in an own Software Component for Galaxy and Web Dynpro use case.

5. Build the SAP proprietary DC and check in the produced deployable archive for the following files:

   • *.composite - only one file with this extension should exist in the META-INF folder of the EAR archive or SDA archive.

   • sca-contribution.xml - only one file with this extension should exist in the META-INF folder of the EAR archive or SDA archive.