cancel
Showing results for 
Search instead for 
Did you mean: 

Importing .sca file into Eclpise

Former Member
0 Kudos

Hello Experts,

I need to import .sca file provided into Eclipse. I have gone through some of the discussions on SDN wherein it is said to create some config in SLD.

Got very confused on how to import it in Eclipse. Can someone please help me on this?

This is really very urgent.

Thanks in advance

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member189220
Active Contributor
0 Kudos

Hello BRM Fresher,

The SCA are SAP archives which are created accordingly the Software Component Model paradigm.

1.

When you would like to import SCA in eclipse, there is no guarantee you will be able to use everything from this SCA. So, it is better to use NWDS instead of eclipse.

2.

In NWDS one can import ONLY archives like SCAs, EARs and so on, which have been exported before from the NWDS. In case it is necessary to make changes in SAP SCA, then it is better to use NWDI (where you will create development configuration and import this SCA with it in the NWDS). More details (and references to the help documentation) in this SAP KBA:

2473044 - Assembly in CMS & export in NWDS are they compatible?

Regards,

former_member189220
Active Contributor
0 Kudos

Hello again,

In case you do not want to use DI DTR as versioning repository system, the SAP NWDS does allow to use CVS as a Development Repository.

Using CVS as Development Repository

However, if you import the SCA from such a CVS repository you need to ensure the source code is structured as it is required by the AS Java (with regards to deployment descriptor, METADATA, SAPMANIFEST and so on).

You need to ensure you have built the SCAs, to be deployed to the AS Java, with all of the required build libraries.

Both of the above 2 points could be avoided, with the usage of the NWDI. The NWDI CBS does not support other repository but only DI DTR. Hence, with the usage of CVS and NWDS (or GIT repository and another IDE), you need to ensure the presence of proper build libraries in the relevant Build Tool (f.e. per4ce, Maven and etc.)

Regards,