Previous Topic: regproc—Registering ProceduresNext Topic: regsw—Registering Software


Example

In the following example, a procedure is registered from a Windows server command line, and made available for request through the Catalog. Since the procedure file, install1.cmd, does not reside in the current directory or in the system path, but on the target system, it is an external procedure and the full path is specified.

cadsmcmd regproc item="Software Test" version=0.45 task=install 
procedure=Install os=WINDOWS_32-BIT type=command enduser externalproc
file=install.cmd path=c:\test\swtest1 comment="Install Proc 1" 

In the following example the argument externalProc is coded. The path parameter is not used. The executable associated with the procedure conf_ext is expected to be the program configure.exe which is to be found at c:\myProcs\Prod.

regproc item=prod1 version=1.2/98 task=configure procedure=conf_ext os=WIN_NT type=executable externalProc file=c:\myProcs\Prod1

Also in the next example the path parameter is not used. The executable associated with the procedure act_ext is the program act.exe to be found within the %PATH% of the target systems.

regproc item=prod1 version=1.2/98 task=activate procedure=act_ext os=WIN_NT type=executable externalProc file=c:\myProcs\Prod1\act.exe

In the following example the path parameter is used: the executable associated with the procedure inst_ext is expected to be the program install.exe and it is to be found at c:\myProcs\Prod1 on the target systems.

regproc item=prod1 version=1.2/98 task=install procedure=inst_ext os=WIN_NT type=executable externalProc file=install.exe path=c:\myProcs\Prod1