Deploying Server Code to SAS Enterprise Miner

If you follow the development strategy described in previous chapters, the source code for your extension node consists of multiple files. As a practical matter, it is most convenient for the purposes of development and deployment if all of the files reside in a single SAS catalog. Deploying the code is then just a matter of placing the catalog in a SAS library that is accessible by SAS Enterprise Miner.
The simplest method is to include your catalog in the SASHELP library. This is accomplished in one of three ways. The first way is to use PROC CATALOG. Suppose your catalog is named mylib.mycode. Start a SAS session and issue the commands:
proc catalog cat=mylib.mycode;
	copy out=sashelp.mycode;
run;
The second way is to manually copy and paste the catalog into the SASCFG folder. The exact location of this folder depends on your operating system and your installation configuration, but it is always found under the root SAS directory and has a path resembling the following: C:\Program Files\SAS\SASFoundation\9.2\nls\en \SASCFG.
The third way is to store the catalog in another folder and then modify the SAS system configuration file SASV9.CFG. The folder containing the catalog is then included in the SASHELP search path. The SASV9.CFG file is located under the root SAS directory: C:\Program Files\SAS\SASFoundation\9.2\nls\en.
The advantage of putting your code in the SASHELP library is that anyone using that server has access to it.
An alternative is to place your code in a separate folder and issue a LIBNAME statement. The library needs to be accessible when a project is opened. See Appendix 4: Allocating Libraries for SAS Enterprise Miner for details about the various ways this can be accomplished. For a shared platform installation, the catalog must reside on the SAS Enterprise Miner server. For a personal workstation installation, the catalog resides on the client, because the client and server are the same machine.
If you have more than one extension node, you can place the code for all of your extension nodes in a single catalog. However, when you are developing an extension node, it is probably better to keep that node's code in a separate catalog. That way, as you are developing or modifying the node's code, you do not have to interrupt the use of other extension nodes.