SBM ModScript Reference → Programming SBM ModScript → Setting Script Application Paths

Setting Script Application Paths

When you write scripts that call applications or DLLs outside of SBM, you can create an optional ScriptAppPath registry setting that contains a semicolon-separated list of directories that store executable files and DLLs that are called in SBM ModScripts. If ScriptAppPath is not found, the path list in the standard Windows environment variable PATH is used. Optionally, you can place DLLs and executables in the companyName/productName/bin directory on your SBM Web server.

To create the optional SBM registry setting on a Windows Web server:

  1. Launch the Registry Editor on the Web server.
    Note: If your system uses multiple Web servers, the registry setting must be added to each.
  2. Navigate to the HKEY_LOCAL_MACHINE/Software/TEAMSHARE/TEAMTRACK directory.
  3. Add a new string value called ScriptAppPath.
  4. Modify the setting and add the directory in which the executable or DLL you are calling in your script is stored. Multiple directories should be separated by semi-colons.
    Note: ScriptAppPath conforms to the same syntax as the Windows environment variable PATH. Folder paths are separated by semicolons, environment variables are surrounded by '%' characters, and spaces do not need to be escaped or quoted. Unlike path, any quotes in ScriptAppPath are interpreted literally as part of the folder name.

Related Topics

Calling Functions in a DLL from SBM ModScript

Ext.NewTaskWait( appName, arg1, arg2, ... )

Ext.NewTask( appName, arg1, arg2, ... )

Ext.CmdLineWait( cmdLine )

Copyright © 2007–2017 Serena Software, Inc. All rights reserved.