Displaying provadmin help fp

You can get help for the provadmin command either with or without a target.

The availability of the provadmin targets in Fulfillment Provisioning are : alarm, asyncsim, ca, caperf, caperfpmf, cart, catalog, cesrouter, checkpoints, driver, eventdictionary, fc, gate, fp, fpstatistic, fpstats, mapping, password, provtest, queue, runtimestatistics, sample, socreator, streams, telnetsim, workflow.

The usage of the above targets is described in the Fulfillment Provisioning User's guide.

The following shows the usage of help of the Fulfillment Provisioning target and typical output from the command: 

provadmin color=true help fp
Usage: provadmin [param=value,...] <command> <target> [param=value,...]

  global parameters:

 	hostname:	application host (default localhost)
  adminport:	application admin port (no default)
	 debug:		true or false (default false)
	 trace:		true or false (default false)

  valid commands and parameters for target "fp":

	install fp [ configpath=<value> ]
            [ adminport=<value> ]
            [ memorysize=<value> ]
            [ nameserviceport=<value> ]
            [ buildtype=<value> ]
            [ nodename=<value> ]
            [ nogui=<value> ]
            [ debugfilter=<value> ]
            [ lockedObjectHashSize=<value> ]
            [ language=<value>]

	remove fp [ nodename=<value> ]
			[ savelog=<value> ]
			[ saveconf=<value> ]

	start fp [ nodename=<value> ]
			[ buildtype=<value> ]

	stop fp [ nodename=<value> ]
			[ stopcoordinator=<value> ]

	display fp [ nodename=<value> ]

	getadminport fp [ nodename=<value> ]

	getallports fp [ nodename=<value> ]

	<==Commands==>
	install		Install the Fulfillment Provisioning application
	remove		Remove the Fulfillment Provisioning application and save configuration files
	start		start the application engines
	stop		stop the application engines
	display		display the state of the application engines
	getadminport	get the administration port number
	getallports	get the coordinator, web and JNDI ports

	<==Parameters==>
	configpath:	 configuration files will be loaded
			 from this directory 
			 (default $SW_HOME/distrib/kabira/kpsa/samples/prov/conf)
	adminport:	 set web server port (randomly generated by default)
	memorysize:	 size of shared memory in MB (default 512)
	nameserviceport: port to use for name service (default random)
	buildtype:	 build type of components to be loaded, must be
			 PRODUCTION or DEVELOPMENT (default PRODUCTION)
	nodename:	 Fulfillment Provisioning node name (default javel)
	nogui:		 whether Fulfillment Provisioning has to install/start GUIs (default false)
	debugfilter:	 debug trace level
	stopcoordinator: whether KIS coordinator is also stopped (default false)
	savelog:	 whether log files are saved (default true)
	saveconf:	 whether configuration files are saved (default true)

	lockedObjectHashSize:	allows the configuration of the
				"node\ObjectServices" ->
				"lockedObjectHashSize" registry value,
				before starting the node.
 language: Specifies which language to use for event dictionary
					 (default en), list of available languages depends on which package language is
					 installed in the TIBCO_HOME
				  location.

	<==Notes==>
	These are the configuration files loaded 
	from configpath upon install.

	fp.kds: Deploy specification. If a
							 custom fp.kds is not found in the configuration path and no 
							 fp.kds is found, then 
							 $SW_HOME/distrib/kabira/kpsa/deploy/fp.kds
							 is used.

	provisioning.bpmn	BPMN file for the main flow. 
It searches for the provisioning.bpmn file if the provisioning.bpmn file is not found

	*.def</codeph>: Fulfillment Provisioning Catalog definition files. 
These files are created using the Fulfillment Provisioning Catalog application.

	>*.xml and *.bpmn</codeph>: XML files for ProductOrderFlows. 
The <codeph>cpr.def</codeph> file references these <codeph>*.bpmn and *.xml</codeph> files.

	Upon installation, these files will be loaded 
	into the ./javel/conf directory.

	It is highly recommended to use a checkpoint directory which is not
	under the runtime node : the directory would be deleted upon Fulfillment Provisioning
	remove. Definition of checkpoint directory can be set in file
	./javel/conf/chpointconfig.ini (entry 'checkpointDirectory').
	Default checkpoint directory is $SW_HOME/checkpoints.

When used without a target, provadmin displays help for all targets.