Previous Topic: CcnfSetParameterInt - Modify the Value of an Existing Common Configuration Parameter (type string)Next Topic: OpenDetectedSoftwareOutputFiles


CcnfSetParameterStr - Modify the value of an existing Common Configuration Parameter (type string)

Valid on Windows and Unix

The CcnfSetParameterStr function modifies the value of an existing common configuration parameter of type string.

This common configuration parameter function has the format:

CcnfSetParameterStr(Parametername as string, Value as string) as boolean

Parametername

Name of a Common Configuration Parameter including its absolute path (for example, "itrm/rc/protocols/encrypt/dll")

Value

String value of Parametername

The return value of the function is a boolean. If successful, the function returns TRUE. If the function is not successful, an error is reported in the log file.

The correctness of the value is not verified.

Example: CcnfSetParameterStr function

This example uses a comstore parameter that is described in the chapter Mapping Between asm.cnf and comstore.xml in the Implementation Guide.

if CcnfSetParameterStr("itrm/usd/shared/nos", "newValue") then
Print("value of itrm/usd/shared/nos was modified" )
else
Print("CcnfSetParameterStr failed")
endif

Intellisigs Functions

When using custom Intellisigs, call the DMScript functions within your Intellisig script for reporting software records that are detected on the agent computer. DMScript provides built-in functions that write detected software records to an output file.

The Intellisig script must call the functions in the following order:

  1. OpenDetectedSoftwareOutputFiles
  2. CreateDetectedSoftwareProduct
  3. CreateDetectedSoftwareRelease
  4. CreateDetectedSoftwarePatch
  5. CreateDetectedSoftwareReleaseInstance
  6. CloseDetectedSoftwareOutputFiles