Directory structure used for UDX deployment

A Db2® instance maintains one project directory for each set of files associated with one or more UDXs. During UDX deployment, files generated or copied during intermediate steps are stored in subdirectories of the project directory.

Directory structure used when deploying a UDX written in C++

Directory structure used when deploying a UDX written in C++
To deploy a UDX written in C++:
  •  1  On the client system, create a compressed file that contains the files that are needed by the UDX being deployed.
  •  2  During the upload step, the compressed file is decompressed and the files it contains are uploaded from the client system to the corresponding UDX project directory.
  •  3  During the compile step, the object files are created. To better organize your files, you will usually elect to create these files in a subdirectory of the project directory, for example, one named bin.
  •  4  During the link step, the library file (for C++, this is a shared object file) is created.
  •  5  During the promote step, the files used by the UDX are moved to the release directory.
  •  6  During the register step, information about the UDX and each of the files it references is stored in the database catalog. During deployment, a single UDX is registered. If several UDXs refer to the same library, these can be registered additionally without re-uploading, re-compiling, re-linking, and re-promoting the files.

Directory structure used when deploying a UDX written in Lua

Directory structure used when deploying a UDX written in Lua
To deploy a UDX written in Lua:
  •  1  On the client system, create a compressed file that contains the script file that is needed by the UDX being deployed.
  •  2  During the upload step, the compressed file is decompressed, and the script file it contains is uploaded from the client system to the corresponding UDX project directory.
  •  3  During the promote step, the script file is moved to the release directory.
  •  4  During the register step, information about the UDX and the script file it references is stored in the database catalog. During deployment, a single UDX is registered. If several UDXs refer to the same script, these can be registered additionally without re-uploading and re-promoting the script file.