Use the configureBPMProcessPortal command to configure Process Portal.
You must specify a deployment target for Process Portal. In a multiple cluster configuration, specify the web cluster. The deployment target you specify is used as the default deployment target if you do not specify deployment targets for the application target and the messaging target.
If the application server is not running, supply the -conntype NONE option when running this command.
To specify a different deployment target for applications, specify either appServerName and appNodeName, or appClusterName. The default application target is the target specified for Process Portal.
To specify a different deployment target for messaging, specify either meServerName and meNodeName, or meClusterName. The default messaging target is the target specified for Process Portal.
The following example uses the configureBPMProcessPortal command to configure Process Portal on a stand-alone server, using the same server for applications and messaging.
AdminTask.configureBPMProcessPortal('[-nodeName myNode -serverName myServer -save true]')
$AdminTask configureBPMProcessPortal {-nodeName myNode -serverName myServer -save true}
The following example uses the configureBPMProcessPortal to configure Process Portal on a cluster, using separate clusters for applications and messaging.
AdminTask.configureBPMProcessPortal('[-clusterName myCluster -appClusterName myAppCluster
-meClusterName myMeCluster -save true]')
$AdminTask configureBPMProcessPortal {-clusterName myCluster -appClusterName myAppCluster
-meClusterName myMeCluster -save true}