Configuring Business Process Choreographer Explorer

Use this task to configure Business Process Choreographer Explorer using a script.

Before you begin

You have configured the business process container and human task container.

Why and when to perform this task

One of the following applies:

Steps for this task

  1. Change to the Business Process Choreographer directory and invoke the clientconfig.jacl script.
    On Windows systems, enter the following command:
    cd install_root\ProcessChoreographer\config
    ..\..\bin\wsadmin.bat -f clientconfig.jacl 
      ( [-username userName][-password password] | [-conntype NONE] )
        [-profileName profileName]
        [-hostName explorerVirtualHostname]
        [-explorerHost explorerURL]
        [-precompileJSPs { yes | no }]
        [-remoteNodeName nodeName]
        [-remoteServerName serverName]
        [-remoteClusterName clusterName]
        [-contextRootExplorer explorerContextRoot]
    On UNIX and Linux systems, enter the following command:
    cd install_root/ProcessChoreographer/config
    ../../bin/wsadmin.sh -f clientconfig.jacl 
      ( [-user userName][-password password] | [-conntype NONE] )
        [-profileName profileName]
        [-hostName explorerVirtualHostname]
        [-explorerHost explorerURL]
        [-precompileJSPs { yes | no }]
        [-remoteNodeName nodeName]
        [-remoteServerName serverName]
        [-remoteClusterName clusterName]
        [-contextRootExplorer explorerContextRoot]
    In a standalone server environment:
    • Include the -conntype NONE option only if the application server is not running.
    • If the server is running and global security is enabled, include the -user and -password options.
    • If you are not configuring the default profile, add the -profileName option.
    In a Network Deployment environment:
    • Run the script on the deployment manager node.
    • Include the -conntype NONE option only if the deployment manager is not running.
    • If global security is enabled, include the -user and -password options.
    • If you are not configuring the default profile, add the -profileName option.
    You can also provide the following parameters:
    node nodeName
    Where nodeName is the name of the node where Business Process Choreographer is to be configured. If you have only one node and exactly one server, this parameter is optional.
    server serverName
    Where serverName is the name of the server where Business Process Choreographer is to be configured. If you have only one node and exactly one server, this parameter is optional.
    cluster clusterName
    Where clusterName is the name of the cluster where Business Process Choreographer is to be configured. Do not specify this option in a standalone server environment, nor if you specify the node and server. This option cannot be used non-interactively.
    hostName explorerVirtualHostname
    Where explorerVirtualHostname is the virtual host where the Business Process Choreographer Explorer will run. The default value is default_host.
    explorerHost explorerURL
    Where explorerURL is the URL of the Business Process Choreographer Explorer. If this parameter is not specified for a non-cluster environments, a default value is computed, for example, http://localhost:9080. The value of this parameter is used for the EscalationMail.ClientDetailURL custom property of the Human Task Manager.
    precompileJSPs { yes | no }
    Determines whether Java Server Pages (JSPs) will be precompiled, or not.
    remoteNodeName nodeName
    Use this parameter and remoteServerName if you do not want to connect to the local Business Process Choreographer Explorer. Do not specify this parameter if you want to connect to the Business Process Choreographer server identified by the node and server parameters or the cluster parameter.
    remoteServerName serverName
    Use this parameter and remoteNodeName if you do not want to connect to the local Business Process Choreographer Explorer. Do not specify this parameter if you want to connect to the Business Process Choreographer server identified by the node and server parameters or the cluster parameter.
    remoteClusterName clusterName
    Use this parameter, if you do not want to connect to the local Business Process Choreographer Explorer and you do not specify remoteNodeName and remoteServerName. Do not specify this parameter if you want to connect to the Business Process Choreographer server identified by the node and server parameters or the cluster parameter.
    contextRootExplorer contextRootExplorer
    Where contextRootExplorer is the context root for the Business Process Choreographer Explorer. The default value is /bpc, which results in the default URL of http://host:port/contextRootExplorer. The context root must be unique within the WebSphere cell.
  2. The clientconfig.jacl script prompts you for any required information that was not provided as parameters.
  3. Optional: If you have problems with the configuration, check the log file written by the clientconfig.jacl script. This log is located in the profiles/profileName/logs/clientconfig.log file. This directory also contains a wsadmin.traceout file that might contain more information about the problem.

Result

Business Process Choreographer Explorer is configured and ready to use.

What to do next

Start Business Process Choreographer Explorer.
Related tasks
Starting Business Process Choreographer Explorer

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)