NWDI Server and Runtime System Do Not Share a Transport Directory 

For various reasons, the transport directory of the runtime system may not be available as a share for the NWDI transport directory. This may be for security reasons or be caused by the physical distance between the NWDI server and the runtime system.

This appendix describes a method for delivering the replacement components to the runtime system despite this restriction. This requires you to make manual copies of files at certain points in the process. You can use operating system utilities (ftp, cp, or copy) to make these file transfers.

You must intervene in the process at the following times:

...

       1.      During a JSPM import into a J2EE system that acts as a DEV/CONS system within an NWDI track (see Start of the Support Package Import Process), JSPM copies all SCAs into the directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME). These files must be copied into the corresponding directory on the NWDI server manually.

       2.      After the assembly of the modified software components in the NWDI track (see Importing Support Packages into Follow-On Systems), the modified SCAs are available in the directory $(TRANSDIR)/EPS/in/assembled on the NWDI server. These files must be copied into the corresponding directory on the corresponding server of the J2EE runtime system manually.

For more information, see the following topic:

Maintenance of an NWDI-Driven System Landscape