Create SCA files locally

[Former Member]

Hello,

Iu2019m trying to create SCA files locally on my development workstation. Is the only way to create SCA files to u201CDeployu201D from within NWDS? I havenu2019t found any SCA files in the workspace after a buildu2026.

Thank you,

Zach

[Former Member]

Pascal,

I do not have access to the SDM. When the deploy action is selected, I am asked for the password to the SDMu2026which I can not supply.

You mentioned that a SDA file will be created if developing using DCs. I created a new DC project and imported my Web Dynpro project with the wizard. After building there was no SDA file, there is a EAR file created when I u201Cdeployu201Du2026but that is also available with the Web Dynpro project.

Any suggestions?

Zach

[Former Member]

The best suggestion I can give you is to ask your administrator for the SDM password(s). That will make your life so much easier...

[Former Member]

The best suggestion I can give you is to ask your administrator for the SDM password(s). That will make your life so much easier...

[Former Member]

The best suggestion I can give you is to ask your administrator for the SDM password(s). That will make your life so much easier...

[Former Member]

Pascal,

Thank you for the response. In the NetWeaver help pages, it is mentioned that the SDM can deploy Software Deployment Units. It also defines SDUs as either SDA files or SCA files.

The following forum post () mentions the use of ear and zip files for deployment with SDM. I have found ear files in my NWDS projects. Should I be able to build the project and then deploy the generated ear file? If notu2026. Do I need to install a local copy of AS Java to locally deploy and then use the generated SDA file on the server of interest?

Kindest Regards,

Zach

EDIT:

When I say deploy, I am not referring to the tab/option in NWDS u201CDeployu201D. I would rather create an SDU equivalent file with NWDS and then manually use that file with the SDM.

Edited by: Zachary Shay on Nov 25, 2009 3:33 PM

[Former Member]

Why don't you want to use the Deploy option of NWDS?

Anyway, you can also deploy .ear files, etc. with SDM.

If you developing using DCs, you'll always have an SDA after building the DC (if the DC type has a deployable result).

[Former Member]

Why don't you want to use the Deploy option of NWDS?

Anyway, you can also deploy .ear files, etc. with SDM.

If you developing using DCs, you'll always have an SDA after building the DC (if the DC type has a deployable result).

[Former Member]

Why don't you want to use the Deploy option of NWDS?

Anyway, you can also deploy .ear files, etc. with SDM.

If you developing using DCs, you'll always have an SDA after building the DC (if the DC type has a deployable result).

[Former Member]

You don't even get SCA files when you deploy from NWDS. NWDS only deploys SDA's. SCA's are only assembled in the Assembly stage of a track and are thus only created on the NWDI server.

[Former Member]

You don't even get SCA files when you deploy from NWDS. NWDS only deploys SDA's. SCA's are only assembled in the Assembly stage of a track and are thus only created on the NWDI server.

[Former Member]

You don't even get SCA files when you deploy from NWDS. NWDS only deploys SDA's. SCA's are only assembled in the Assembly stage of a track and are thus only created on the NWDI server.