How to prevent SDA file version differences from causing a Portal restart

[Former Member]

We have recently installed NWDI 7.0 and are now testing a deployment to our 6.0 Enterprise Portal using the 6.40 SAP_JTECHS, SAP_BUILDT and SAP-JEE libraries. The Portal has had several required patches applied recently in the form of SDA files which are not yet available as SCA files yet.

When we tested a deployment, NWDI recognized the version differences of several SDA files in the SAP_JTECHS and SAP-JEE libraries and replaced the newer versions on the Portal with the older versions on NWDI. The SAP-JEE library changes then caused the Portal to restart without warning.

Unfortunately we have been unable to find a way to get the new SDA file versions into NWDI so we can deploy successfully. NWDI allows us to check-in and import SCA files but not SDA files. Since our Portal is on release 6.40, the SDA files are assempled into SCA files very infrequently (every 3 to 4 months?) if ever.

How can we 1) import the new SDA versions into NWDI without an available SCA file or 2) prevent NWDI from pushing the older SDA files to the Portal and causing the restart?

[Former Member]

Our SAP consultant contacted the NWDI development team and provided an answer. The solution is to take the SAP_BUILDT file originally imported into NWDI and extract new SAP_BUILDT, SAP_JTECH and SAP-JEE libraries and

metedata files, then check-in and reimport these files into the track. The metadata apparently instructs the SDM to not compare the libraries between NWDI and EP so the EP patches are no longer overlayed by NWDI.

The good news is that we can now deploy to our Portal without patch differences being synchronized by NWDI and causing a Portal restart. The bad news is that our build libraries are now different from the runtime libraries which adds a small risk of runtime failures. NWDI's inability to import patches is a process gap that SAP needs to address so that there is a way to keep the libraries in synch.