CMS Transport to Consolidation System Issue

[Former Member]

Hi All,

I am following the below steps to transport the SCA files from DEV

System to Consolidation System.

1) I have released the Applications successfully from NWDS after the

Build is Successful.

2) Then , I logged onto the CMS of NWDI.

3) I have imported the Applications under the Consolidation Tab.

4) All the Imports finished successfully.

5) After that, under the Assembly Tab I created an SCA File. The

Assembly is also successful and all are showing Green Color in the

details of the SCA File.

6) Then, under Approve tab, I approved the Request.

But when I checked in the Deployment of the Consolidation system, there

are no PAR files /SCA File available.

We have also checked in the File System of the Consolidation System,

but there is no SCA File exists.

But It exists in NWDI System CMS Folder.

Kindly let us know why our application (SCA File) is not moved to the consolidation

system.

Thanks & Regards||

Ashok Kumar M.

[Former Member]

closing this.

[Former Member]

Ashok,

I suggest also this:

1. Check SDM log of your cons system. It will shoow you what happened during the deployment of SCA to cons.

2. SCA files have simple zip format. Rename to zip and open the one you have in CMS transport directory to see what you have assembled. If looks good try to deploy it to cons directly via SDM and see what happens. If deployed OK, re-check your runtime system settings in CMS landscape. Make sure checkbox "Disable automatic deployment" are cleared for dev and cons rts.

Regards,

Slava

[Former Member]

Hi,

My SCA doesn't contain any SDA Files. All are EP DC Portal Application Modules and some External Library DC's and Java DC's.

The SCA File contains all the above applications in a ZIP Format. we tried to redeploy 4 times, but still the applications are not getting deployed.

And the Option "Disable auomatic Deployment" Checkbox is Unchecked.

Please let me know what other settings I have to check or make changes?

Thanks &Regards||

Ashok Kumar M.

[Former Member]

These are all DC types without deployable results, thus they do not generate an SDA.

You need to wrap External Library DCs in J2EE Library DCs.

Java DCs can be basically be wrapped in any other DC with a deployable result.

Instead of Portal Application Module, you should use Portal Application Standalone.

You can find all DC types here:

<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/d7/fc139ba1549047a5372ad3c0d540ea/frameset.htm">Types of Development Components</a>

[Former Member]

Hi,

I could find the issue:

Issue 1:

1. Message Server http Port should be : 81xx

xx -instance number - I have done the changes and this is resolved now.

Issue 2:

2. NWDI and Runtime do not share Transport Directory:

http://help.sap.com/saphelp_nw70/helpdata/en/44/621848cea86d11e10000000a1553f6/frameset.htm

We do not share the transport directory of NWDI and Runtime systems,so NWDI is not able to deploy the files now.

I would like to share the tranport directory in my case.

1.which is the transport directory of NWDI and Runtime System?

NWDI File System:

/usr/sap/JTrans

/usr/sap/trans

Runtime systems /usr/sap/trans should be mapped with which one of the above file system in NWDI?

Regards,

Ashok

[Former Member]

Does your SCA contain any SDA's? Are you using DC types with deployable results?