getBPMProperty command

Use the getBPMProperty command to get the value of an IBM BPM custom property from the configuration repository.

The getBPMProperty command is run using the AdminTask object of the wsadmin scripting client.

Prerequisites

The following conditions must be met:

  • The command must be run on the deployment manager node.
  • If the deployment manager is stopped, use the wsadmin -conntype none option to run the command in disconnected mode.
  • If the deployment manager is running, you must connect with a user ID that has WebSphere Application Server configurator privileges. Do not use the wsadmin -conntype none option.

Location

Start the wsadmin scripting client from the deployment_manager_profile/bin directory. The getBPMProperty command does not write to a log file, but the wsadmin scripting client always writes a profile_root/logs/wsadmin.traceout log file where you will find exception stack traces and other information.

Syntax

getBPMProperty
-de deployment_environment_name
-name custom_property_name

Parameters

-de deployment_environment_name
A required parameter that specifies the name of the current deployment environment.
-name custom_property_name
A required parameter that specifies the name of an IBM BPM custom property.

Examples

Note: The examples are for illustrative purposes only. They include variable values and are not meant to be reused as snippets of code.
The following Jython example uses the getBPMProperty command to get the value of an IBM BPM custom property from the configuration repository:
wsadmin -user admin -password admin -lang jython
wsadmin>AdminTask.getBPMProperty(['-de', 'De1', '-name', 'ProcessCenter.BpdAutoTrackingEnabledDefault'])
Parent topic: Commands (wsadmin scripting)