IBM BPM, V8.0.1, All platforms > Administer applications and processes in the runtime environment > Manage processes and their components > Administer BPEL processes and human tasks > Administer BPEL process and task templates

Stopping and starting process and task templates using administrative scripts

Use an administrative script to stop and start all templates that belong to an application, as an alternative to the administrative console for stopping and starting process and task templates individually.

The following conditions must be met:

• If WebSphere administrative security is enabled, and your user ID does not have operator or administrator authority, include the wsadmin -user and -password options to specify a user ID that has operator or administrator authority.

• Run the script in connected mode, that is, the application server must be running. Do not use the wsadmin -conntype none option.
• If you are not working with the default profile, use the wsadmin -profileName profile option to specify the profile.

The following steps describe how to use an administrative script to stop and start the process and task templates that belong to an application.

Procedure

1. Change to the Business Process Choreographer subdirectory where the administrative script is located.
   

   cd INSTALL_ROOT/ProcessChoreographer/admin

   cd INSTALL_ROOT/ProcessChoreographer/admin

   cd INSTALL_ROOT\ProcessChoreographer\admin

2. To stop the process and task templates.

    INSTALL_ROOT/bin/wsadmin.sh -f bpcTemplates.jacl 
                               -stop  application_name

   

    INSTALL_ROOT\bin\wsadmin -f bpcTemplates.jacl 
                            -stop  application_name

   

    INSTALL_ROOT/bin/wsadmin.sh -f bpcTemplates.jacl 
                               -stop  application_name

   Where:

   -stop application_name

   Stops all templates that belong to the named application.

   Existing instances of the process templates continue to run until they end normally, but you cannot create new instances from the stopped template. If the process is a subprocess, the creation of new instances depends on whether the subprocess is a peer or a child of the calling process.

   If the process template is part of a process application, the business process definition (BPD) cannot start new instances of the BPEL process, and therefore it cannot run to completion.

3. To start the process and task templates.

    INSTALL_ROOT/bin/wsadmin.sh -f bpcTemplates.jacl 
                               -start  application_name

   

    INSTALL_ROOT\bin\wsadmin -f bpcTemplates.jacl 
                            -start  application_name

   

    INSTALL_ROOT/bin/wsadmin.sh -f bpcTemplates.jacl 
                               -start  application_name

   The templates belonging to the application start. You can use Business Process Choreographer Explorer to start process instances from the process templates, and work with task instances associated with the task template.

Administer BPEL process and task templates

Related concepts:
BPEL process administration—frequently asked questions
Authorization roles for BPEL processes
Authorization roles for human tasks
Lifecycle management of BPEL subprocesses