The command line-to-DFC program enables you to send DFC calls from within a shell script or from other types of applications that are not designed to use the normal DFC routing function commands. The function called must be listed in the file.
ims54cmdlinedfc -cluster.name clusterName -cluster.server clusterServer -domain.type domainType -domain.name domainName -env.snmp.port snmpPort -env.trap.port trapPort -file fileName -dfc.function dfcFunctionName -dfc.flavor dfcFlavor -dfc.args[arg1,arg2,arg3,...]
clusterName – name of the cluster that receives the DFC call.
clusterServer – name of the e-Biz Impact server on which the cluster is running.
domainType – type of the domain under which the cluster is running. The default value is “Impact.”
domainName – the name of the domain under which the cluster is running. The default value is “Impact.”
snmpPort – the SNMP port to which the cluster publishs telemetries. The default value of is 161.
trapPort – the SNMP trap port to which the cluster publish alerts. The default value is 162.
fileName – name of an NNConfig style file that can optionally contain all or some command line arguments, and in which the command line argument takes precedence over a value in the file.
dfcFunctionName – name of the DFC function to call.
dfcFlavor – flavor of the DFC to call. The default value is “0.”
arg1, arg2, arg3..... – optional list of string arguments to the DFC function, and if provided on the command line, the -dfc.args key and its values must be the last arguments on the command line.
To run these command use the ims wrapper scripts, see “Using
wrapper scripts” in chapter 1 of the e-Biz Impact
Command Line Tools Guide.
Returns 0 for initialization failure and 1 otherwise.
| Copyright © 2005. Sybase Inc. All rights reserved. | ||
