Siebel Business Process Framework: Task UI Guide > Deploying Tasks >

About Task Deployment

A deployment scheme is used to move task objects from the repository to the run-time environment. After you have designed a task in Siebel Tools, you deploy the task by publishing it using Siebel Tools, and then activating it in the run-time client application. The processes for task design and task deployment occur separately. This topic contains further information about deploying tasks in the following topics:

• About Deploying Actions Using Siebel Tools
• Deploying Tasks Using Application Deployment Manager
• Migrating Tasks Between Environments

For more detail on deploying tasks, see Deploying Tasks from Siebel Tools. For more information about deploying tasks for mobile clients, see Setting Up Tasks for Running on Mobile Clients.

About Deploying Actions Using Siebel Tools

You can use the buttons on the WF/Task Editor toolbar (shown in Figure 16) to perform deployment actions in Siebel Tools.

Figure 16. WF/Task Editor Toolbar

The buttons on the WF/Task Editor toolbar are (from left to right in Figure 16):

• Publish/Activate. Publishes and then activates the task.

  Use this button to activate a task only for debugging on a thick client. Because the activation is performed directly in the Siebel database from a Siebel Tools session, an application client that is currently running cannot see the activated task in its cache until you restart the client.

  To use the Publish/Activate button, you must set the VerCheckTime configuration parameter to -1 in the [Workflow] section of the application's .CFG file.

  ...
  [Workflow]
  VerCheckTime = -1
  ...

  NOTE:  Do not use the Publish/Activate button when you are running or testing your task flows in a server environment. Instead, use the Publish button to publish the task flows, then go to the application client, and activate the task flows using the Activate button in the task deployment view.

• Publish. Publishes the task to the run-time environment.
• Revise. Creates a new version of the task.
• Expire. Sets the status of the task to expired.

For more information about the actions performed by these buttons, see Deploying Tasks from Siebel Tools.

To show the WF/Task Editor toolbar

• From the View menu (in Siebel Tools), choose Toolbars > WF/Task Editor Toolbar to display the WF/Task Editor toolbar.

Deploying Tasks Using Application Deployment Manager

You can use the Siebel Application Deployment Manager (ADM) to deploy the task. ADM is a tool that streamlines the process of deploying enterprise customization data (such as views, responsibilities, assignment rules, tasks, and Workflow processes and policies). It also allows you to migrate this data from one Siebel application environment to another.

A task deployment package in ADM includes the repository file (SRF), tasks, subtasks, and their run-time settings (such as activation and expiration times). For information on how to deploy and migrate tasks using ADM, see the Siebel Application Deployment Manager Guide.

Migrating Tasks Between Environments

After you have configured a task in your development environment, you need to move it to a testing or production environment. As with the standard Siebel applications, you can use one of the following three ways to accomplish this migration:

• Archive Files. Using the features of Siebel Tools, you can export objects from the repository to an archive file (SIF), and then import objects from the archive file back into the repository using Siebel Tools. Use archive files when you want to back up sets of objects or migrate these objects. You can include individual objects (such as business components, applets, views, and tasks) or entire projects in archive files. For more information on how to export and import archive files, see Using Siebel Tools.
• REPIMEXP. You can use the Repository Import and Export (REPIMEXP) utility for bulk migration of repository objects, including task definitions. REPIMEXP is a command-line utility found in the BIN directory of your Siebel installation. Type repimexp /help in a command prompt to view your usage options.

  NOTE:  If you use REPIMEXP you cannot pick and choose which tasks to migrate. To select a single task or only certain tasks for migration, use the ADM migration option.

• ADM. The Siebel Application Deployment Manager (ADM) is a tool that streamlines the process of deploying and migrating enterprise customization data, including tasks, from one Siebel application environment to another. This process includes migrating from a development environment to a testing environment, and from a testing (or development) environment to a production environment. For information on how to migrate tasks using ADM, see the Siebel Application Deployment Manager Guide.

NOTE:  Before migrating data, make sure that all data required for the task is also present in the target environment. For example, if your task requires custom entries in the list of values (LOV) table, make sure that these are present and active.