BPEL Task Object

Using the BPEL Worklist API, how do I retrieve a Task's type (i.e., the Task is an Assignment, Group Vote, Single Approver, etc.)?
I'm unable to find a method in oracle.bpel.services.workflow.task.mode.TaskType that provides me this.
Also, is oracle.bpel.services.workflow.task.model.Task.getSystemAttributes().getAssigneeUsers() the only available method to get users assigned to a task? Is there any other mechanism?
Any help is greatly appreciated!
Thanks!!

Do you mean the value stored in WFTASK.TASKDEFINITIONNAME ?
That is what we use as "Task Type"
We access it by .getSystemAttributes().getTaskDefinitionName(); off the oracle.bpel.services.workflow.task.model.Task object.
I'm not sure if there is another way to get the assignee users, as the way you mentioned is the way we get them too.

Similar Messages

Invoking BPEL Task Apis - Recommended approach

Hi all,
I am trying to invoke BPEL Task webservice APIs and am referring to this link . I have a few queries in this regard.
1. Workflow Service Clients - Best approach - It appears that there are many approaches to get a workflow service client and am confused which to proceed with.
i. wf_client_config.xml & use getWorkflowServiceClient to get the client
ii. Using a JAXB Object
iii. Using a Map
2. If I am to invoke the webservice, what are the setups required at my client end to invoke the webservice?
Thanks,
Srini

I added the jar files and I don;t get the exception anymore. I am able to login in as weblogic and the application works fine. When I login in as anyother user I get this error. Where is this pc.properties?
Warning: Could not locate file pc.properties in classpath
ORABPEL-30501
Error in authenticating user.
Error in authenticating and creating a workflow context for user jazn.com/pat.
Verify that the user credentials and identity service configurations are correct.
Thanks
Saru

Multiple SQL task objects inside a package object is not generating proper DTSX

I am programmatically adding multiple ExecuteSQLtask objects inside a package. I am specifying all the required properties to the ExecuteSQLtask objects. However, when I save the package object to dtsx, the package looses the properties of some
of the ExecuteSQLtask object.
In the below example, I have created 3 ExecuteSQL task objects using the function AddSqlTask. However, once you run it, one of the objects will loose its properties. What makes it more weird is the fact that sometimes, object 1 looses the properties,
some times, its object number 2. Its random. I know that these objects are COM objects. Is there something I need to careful of when setting the properties ? Why are the values lost when I save them to DTSX ?
using System;
using System.Collections.Generic;
using System.Configuration;
using System.Data;
using System.Data.SqlClient;
using System.Globalization;
using System.IO;
using System.Linq;
using System.Text;
using System.Threading;
using System.Threading.Tasks;
using System.Timers;
using Microsoft.SqlServer.Dts.Runtime;
using Microsoft.SqlServer.Dts.Runtime;
using Microsoft.SqlServer.Dts.Tasks.FileSystemTask;
using Microsoft.SqlServer.Dts.Tasks.BulkInsertTask;
using Microsoft.SqlServer.Dts.Runtime;
using Microsoft.SqlServer.Dts.Pipeline;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTask;
using Microsoft.SqlServer.Dts.Tasks.ExecutePackageTask;
namespace PackageCreator
class Program
static void Main(string[] args)
#region Package 1
Package package1 = new Package();
#region ConnectionString
AddSqlConnection(
package1,
ConfigurationManager.AppSettings["ServerHostName"],
ConfigurationManager.AppSettings["SqlServerDefaultDB"]
#endregion
AddSqlTask(package1, "P1 - Task1");
AddSqlTask(package1, "P1 - Task2");
AddSqlTask(package1, "P1 - TaskFinal");
#region Add Dependencies
package1.PrecedenceConstraints.Add(
package1.Executables[0] as TaskHost,
package1.Executables[1] as TaskHost
package1.PrecedenceConstraints.Add(
package1.Executables[1] as TaskHost,
package1.Executables[2] as TaskHost
#endregion
#endregion
#region Package 2
Package package2 = new Package();
#region ConnectionString
AddSqlConnection(
package2,
ConfigurationManager.AppSettings["ServerHostName"],
ConfigurationManager.AppSettings["SqlServerDefaultDB"]
#endregion
AddSqlTask(package2, "P2 - TaskFinal");
#region ExecutePackageTaskClass
Executable exec1 = package2.Executables.Add("STOCK:ExecutePackageTask");
TaskHost th = exec1 as TaskHost;
ExecutePackageTask myTask = th.InnerObject as ExecutePackageTask;
myTask.PackageID = package1.ID;
#endregion
#region Add Dependencies
package2.PrecedenceConstraints.Add(
package2.Executables[0] as TaskHost,
package2.Executables[1] as TaskHost
#endregion
#endregion
//new Ispac(package1, package1.ID).DeployAndRun();
SavePackage(package1);
SavePackage(package2);
var packageList = new List<Package>();
packageList.Add(package1);
packageList.Add(package2);
new IspacPackageCollections(packageList).DeployAndRun();
Console.Read();
private static void AddSqlTask(Package package, string component)
//Thread.Sleep(5000);
package.Executables.Add("STOCK:SQLTask");
ExecuteSQLTask executeSQLTask = (package.Executables[package.Executables.Count - 1]
as TaskHost).InnerObject
as ExecuteSQLTask;
executeSQLTask.Connection = package.Connections[0].ID;
executeSQLTask.SqlStatementSource = "insert into [dbo].[SupersetPackageDependencies] (Component) values ('" +
component + @"')";
private static void SavePackage(Package package)
string packageNetworkLocation = @""
+ ConfigurationManager.AppSettings["packageNetworkLocation"]
+ @"\" + package.ID + ".dtsx";
new Application().SaveToXml(
packageNetworkLocation,
package,
null
//new Application().SaveToSqlServer(
// package,
// null,
// "ANUPN8470P",
// null,
// null
#region AddConnectionManager
private static ConnectionManager AddSqlConnection(Package package, string server, string database)
return AddConnection(
package,
"OLEDB",
String.Format(
CultureInfo.InvariantCulture,
"Provider=SQLOLEDB.1;Data Source={0};Persist Security Info=False;Initial Catalog={1};Integrated Security=SSPI;",
server,
database)
private static ConnectionManager AddConnection(Package package, string type, string connectionString)
ConnectionManager manager = package.Connections.Add(type);
manager.ConnectionString = connectionString;
manager.Name = String.Format(
CultureInfo.InvariantCulture,
"{0} Connection",
type);
return manager;
#endregion
public static void AddExecuteSqlTask(
Package _package,
string _componentId
_package.Executables.Add("STOCK:SQLTask");
// Get the task host wrapper
ExecuteSQLTask executeSQLTask = (_package.Executables[_package.Executables.Count - 1]
as TaskHost).InnerObject
as ExecuteSQLTask;
#region Set required properties
executeSQLTask.Connection = _package.Connections[0].ID;
executeSQLTask.SqlStatementSource = "insert into [dbo].[SupersetPackageDependencies] (Component) values ('" +
_componentId + @"')";
#endregion
//return executeSQLTask;

Why you do not tell what properties get lost?
And why is the same get repeated (you want parallel?):
package1.Executables[0] as TaskHost,
package1.Executables[1] as TaskHost
package1.PrecedenceConstraints.Add(
package1.Executables[1] as TaskHost,
package1.Executables[1]
And why not to add them
like
package1.PrecedenceConstraints.Add(
package1.Executables[0] as TaskHost);,
package1.PrecedenceConstraints.Add( package1.Executables[1] as TaskHost
Arthur
MyBlog
Twitter

BPEL task priority

In short can BPEL tasks be prioritised?
In long..
I have a system I am trying to model with several thousand tasks some of which need to be processed in 10 seconds and some of which need to be processed in 10 hours.
I see that I can set the priority of tasks using some Java enbedded code and possibly this is the only way to do it. Have I missed anything? Is there any documentation or a blog or something which explains more about how the setPriority method affects the BPEL process queue?
I have also seen that there is a 'due' column on the activities tab of the BPEL console, can that be set somehow?
Many Thanks,
Chris

Can you just clarify what you mean by tasks. Is it a BPEL process, or is it a human task, or is it a partner link call.
If it is the latter then you can use pick and functionality with in human task.
If you want to ensure that the high priority services get attention in load, this can be done very eaily in OSB. If you have SOA Suite licenses then OSB is part of that license.
cheers
James

ADF-SOA integration getting class cast exception when creating a BPEL task

Hi,
We are creating a BPEL task programmatically using below code snippet
IInitiateTaskResponse tResponse = iTask.initiateTask(task);
when initiateTask() is called i keep getting below exception.
oracle.bpel.services.workflow.task.ejb.TaskServiceBean_399vcw_HomeImpl_1036_WLStub cannot be cast to oracle.bpel.services.workflow.task.ejb.TaskServiceRemoteHome.
Sometime restarting the servers(soa and wls) solves the issue but most of the time i get above exception. I have a integrated WLS server and a remote SOA server. i have done necessary JNDI configuration in my integrated server and global trust is created betwen both the servers.
Any pointers will help us in our development which is stuck because of this issue.

Mozakkir,
My name is Phil DeLaine and I work for one of Oracle's Gold Partners, TechDemocracy.
I saw your post about the SOA/BPEL integration issue.
Given the potential complexity of your situation, would it make sense to use one of our SOA experts to solve the problem and deliver your project?
Please let me know how we can help. You can reach out to me anytime.
Regards,
Phil
Phil DeLaine
Sales Director
TechDemocracy
(978) 758-3156 (Cell)
[email protected]
http://www.techdemocracy.com/
Our Successes:
1) We won the 2011 Oracle Titan Award for the Best Middleware Implementation. Our award winning solutions included SOA, IAM and BI.
2) We have been awarded with the highly prestigious Oracle ACE Director status for outstanding industry achievement and track record.
3) We sit on several Advisory Boards for Oracle Product Management (for Fusion Middleware Products).
4) We are an Oracle Center of Excellence Partner for SOA and IAM.
5) We are frequently invited to speak at a number of Oracle Customer Success forums such as Oracle's "OpenWorld".
6) We have been rated by Inc. Magazine as one of the top 10 fastest growing companies for 3 consecutive years.
7) We have won and successfully deliveried several projects at Fortune 100, 500 and 1,000 companies. (References Available)

BPEL Task Type

Using the BPEL Worklist API, how do I retrieve a Task's type (i.e., the Task is an Assignment, Group Vote, Single Approver, etc.)?
I'm unable to find a method in oracle.bpel.services.workflow.task.mode.TaskType that provides me this.
Any help is greatly appreciated!
Thanks!

Hi,
We worked on the base tables there you can find them.
--Khaleel

TS - Standard Task object type

Hi Gurus,
I am trying to assign the object type TS - Standard task for the tcode - PO13 (position), but i am getting the error as Standard task does not exist (ID of related object field). I have searched in R/3 to create TS - Standard task, but not available. Please suggest me where to be done.
Vijay.

Standard Task mainly used by Tech consultants in Workflows.
Inputs from SAP doc......
The standard tasks provided by SAP are generally used as steps in a workflow template. They are available as "modules" which you can use for your own developments.
If a workflow scenario only involves one standard task, it can usually be regarded as a minimal solution for showing the connection between application functionality and SAP Business Workflow. For differentiated workflow management, this standard task should be replaced by a customer-specific workflow task
Mohan

Update Short History in BPEL Task Form / Worklist

Hi all,
I'm currently facing a problem and hopefully to get some idea or solutions from here. It is about how to update the task:shortHistory. The reason to do this is due to I have to manually update the track history / short history in the task form from BPEL.
Currently while I tried to update the shortHistory(in one of the human task), it keeps throw me the error with some kind of zero node in the task:shortHistory. Just right before I assign or append the task:shortHistory, I did copy the global human task variable to the update task variable, so it should carry forward the existing shortHistory.
Below is the error from BPEL console:
<selectionFailure xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
-<part name="summary">
<summary>
XPath query string returns zero node.
According to BPEL4WS spec 1.1 section 14.3, The assign activity <to> part query should not return zero node.
Please check the BPEL source at line number "493" and verify the <to> part xpath query.
</summary>
</part>
</selectionFailure>
the <to> part query should be the task:shortHistory node, please help if you have any idea on this.
Thanks.
Jyno
Edited by: loneboy62 on Nov 11, 2009 10:28 PM

Make sure that your result varaible is al ready 'prepared'. It can not assign, because the variable does not coantins this element (only in the definition).
Solution 1: use the assign XML fragment to add this element in your variable.
Solution 2: Use a stylesheet to to create this 'empty' element.
Marc
http://orasoa.blogspot.com

Task object: Linking Opty to Account: on the NEW/create from LookUp

Hi,
The User creates a Task from the Account Detail page.
The Task page has the Opty field (LookUp).
On the LookUp, User clicks the NEW button to create a new Opty record.
The Opty page has the Account field (LookUp) -here is it possible to get the original Account Name into the Account field on the Opty page?
The standard facility is that the Account Name does not get picked up here.
I understand that the above process/flow is not in the standard model...
(the current solution is to ask users to create the task from the Opty Detail page, which reflects the actual intent as well; but a config solution to the above process would be helpful).

Hi,
Siebel pics up the relevent informaiton like account name or opportunity name automatically if that any record you create from with in the any record. And if you consider the normal sales practice, one create an opp first and then a follow up task for that opp.
Nisman

OTBI reporting on BPEL human workflow tasks

Hi,
Is it feasible to do OTBI reporting on BPEL tasks associated to application objects? I was searching around and could find no relevant material.
Thanks,
Srini

Learnt OTBI cannot report on BPEL tasks.

Workflow API: adding and accessing file Attachments to a Human Task

Hi there,
I am using the Workflow Services Java API (11.1.1) for SOA Suite to access and manipulate human tasks. I would like to be able to access and add file attachments to existing human tasks. I am using the methods provided in the AttachmentType interface.
When adding an attachment, the problem I am running into is that an attachment does created and associated with the task, however it is empty and has no content. I have attempted both setting the input stream of the attachment, as well as the content string and in each case have had no success.
I have successfully added and accessed an attachment using the worklist application, however when trying to access the content of this attachment through code I receive an object with mostly null/0 values throughout, apart from the attachment name.
As the API's are not overly rich in documentation I may well be using them incorrectly. I would really appreciate any help/suggestions/alternatives in dealing with BPEL task attachments.
Thanks
The code I am using resembles:
List attachments = taskWithAttachments.getAttachment();
for(Object o : attachments){
AttachmentType a = (AttachmentType) o;
String content = a.getContent(); +// NULL+
InputStream str = a.getInputStream(); +// NULL+
String name = a.getName(); +// Has the attachment name+
String mime = a.getMimeType(); +// Has the mime type+
long size = a.getSize(); +// 0+
Edited by: 855489 on May 2, 2011 4:23 PM
Edited by: 855489 on May 2, 2011 8:48 PM

I am also facing the same issue, using 11.1.1.6, anyone managed to solve this?
Regards
Venkat

Where the task payload is stored in the dehydration store

Hi All,
I wanted to get the taskPayload from the BPEL dehydration store. I have gone thru the WFTASK table but I didn't see any column which conains the taskpaylod.
I need this payload to do the following..
- Get the taskPayload
- Modify it so that I can get modifications in the BPEL process when I submitted the task back to BPEL.
Can the above be done from the bpel dehydration store? If yes please help me in finding the exact table for this task payload.
If not guide me how can I access and modify the task payload.
Thank you.

Payloads are generally stored as BLOBS. Here is a definition of all the tables. You can make the payload editable withing the human task if required, so you don't need to go to the DB.
Main tables used by the BPEL engine
cube_instance – stores instance metadata, eg. instance creation date, current state, title, process identifier
cube_scope – stores the scope data for an instance … all the variables declared in the bpel flow are stored here, as well as some internal objects to help route logic throughout the flow.
work_item – stores activities created by an instance … all BPEL activities in a flow will have a work_item created for it. This work item row contains meta data for the activity … current state, label, expiration date (used by wait activities) … when the engine needs to be restarted and instances recovered, pending flows are resumed by inspecting their unfinished work items.
document - stores large XML variables. If a variable gets to be larger than a specific size (configurable via the largeDocumentThreshold property via the domain configuration page) then the variable is stored in this table to alleviate loading/saving time from the cube_scope table.
audit_trail - stores the audit trail for instances. The audit trail viewed from the console is modelled from an XML document. As the instance is worked on, each activity writes out events to the audit trail as XML which is compressed and stored in a raw column. Querying the audit trail via the API/console will join the raw columns together and uncompress the contents into a single XML document.
audit_details - audit details can be logged via the api … by default activities such as assign log the variables as audit details (this behavior can be set via the auditLevel property on the domain configuration page). Details are separated from the audit trail because they tend to be very large in size … if the user wishes to view a detail they click a link from the audit trail page and load the detail separately. There is a threshold value for details too … if the size of a detail is larger than a specific value (see auditDetailThreshold) then it is place in this table, otherwise it is merged into the audit trail row.
dlv_message – callback messages are stored here. All non-invocation messages are saved here upon receipt. The delivery layer will then attempt to correlate the message with the receiving instance. This table only stores the metadata for a message. (eg. current state, process identifier, receive date).
dlv_message_bin – stores the payload of a callback message. The metadata of a callback message is kept in the dlv_message table, this table only stores the payload as a blob. This separation allows the metadata to change frequently without being impacted by the size of the payload (which is stored here and never modified).
dlv_subscription – stores delivery subscriptions for an instance. Whenever an instance expects a message from a partner (eg. receive, onMessage) a subscription is written out for that specific receive activity. Once a delivery message is received the delivery layer attempts to correlate the message with the intended subscription.
invoke_message – stores invocation messages, messages which will result in the creation of a instance. This table only stores the metadata for an invocation message (eg. current state, process identifier, receive date).
invoke_message_bin – stores the payload of an invocation message. Serves the same purpose the dlv_message_bin table does for dlv_message.
task – stores tasks created for an instance. The TaskManager process keeps its current state in this table. Upon calling invoking the TaskManager process, a task object is created, with a title, assignee, status, expiration date, etc… When updates are made to the TaskManager instance via the console the underlying task object in the db is changed.
schema_md – (just added via patch delivered to Veerle) contains metadata about columns defined in the orabpel schema. Use case driving this feature was how to change the size of a custom_key column for a cube_instance row? Changing the db schema was simple but the engine code assumed a certain length and truncated values to match that length to avoid a db error being thrown. Now, column lengths are defined in this table instead of being specified in the code. To change a column length, change the column definition in the table, then change the value specified in this table, then restart the server.
Column-by-column description:
table ci_id_range
- next_range (integer) – instance ids in the system are allocated on a block basis … once all the ids from a block have been allocated, another block is fetched, next_range specifies the start of the next block.
table cube_instance
- cikey (integer) – primary key … foreign key for other tables
- domain_ref (smallint) – domain identifier is encoded as a integer to save space, can be resolved by joining with domain.domain_ref.
- process_id (varchar) – process id
- revision_tag (varchar) – revision tag
- creation_date (date)
- creator (varchar) – user who created instance … currently not used
- modify_date (date) – date instance was last modified
- modifier (varchar) – user who last modified instance … currently not used
- state (integer) – current state of instance, see com.oracle.bpel.client.IInstanceConstants for values
- priority (integer) – current instance priority (user specified, has no impact on engine)
- title (varchar) – current instance title (user specified, no engine impact)
- status (varchar) – current status (user specified)
- stage (varchar) – current stage (user specified)
- conversation_id (varchar) – extra identifier associated with instance, eg. if passed in via WS-Addressing or user specified custom key.
- root_id (varchar) – the conversation id of the instance at the top of the invocation tree. Suppose A -> B -> C, root( B ) = A, root( C ) = A, parent( B ) = A, parent( C ) = B. This instance, instance at the top of the tree will not have this set.
- parent_id (varchar) – the conversation id of the parent instance that created this instance, instance at the top of the tree will not have this set.
- scope_revision (integer) – internal checksum of scope bytes … used to keep caches in sync
- scope_csize (integer) – compressed size of instance scope in bytes
- scope_usize (integer) – uncompressed size of instance scope in bytes
- process_guid (varchar) – unique identifier for the process this instance belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
- process_type (integer) – internal
- metadata (varchar) – user specified
table cube_scope
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- modify_date (date) – date scope last modified
- scope_bin (blob) – scope bytes
table work_item
- cikey (integer) – foreign key
- node_id (varchar) – part of work item composite key, identifier for bpel activity that this work item created for
- scope_id (varchar) – part of work item composite key, identifier for internal scope that this work item created for (note this is not the scope declared in bpel, the engine has an internal scope tree that it creates for each instance, bpel scopes will map to an internal scope but there will be other internal scopes that have no mapping to the bpel definition).
- count_id (integer) – part of work item composite key, used to distinguish between work items created from same activity in the same scope.
- domain_ref (integer) – domain identifier
- creation_date (date)
- creator (varchar) – user who created work item … currently not used
- modify_date (date) – date work item was last modified
- modifier (varchar) – user who last modified work item … currently not used
- state (integer) – current state of work item, see com.oracle.bpel.client.IActivityConstants for values
- transition (integer) – internal use, used by engine for routing logic
- exception (integer) – no longer used
- exp_date (date) – expiration date for this work item; wait, onAlarm activities are implemented as expiration timers.
- exp_flag (integer) – set if a work item has been called back by the expiration agent (ie. expired).
- priority (integer) – priority of work item, user specified, no engine impact
- label (varchar) – current label (user specified, no engine impact)
- custom_id (varchar) – custom identifier (user specified, no engine impact)
- comments (varchar) – comment field (user specified, no engine impact)
- reference_id (varchar) -
- idempotent_flag (integer) – internal use
- process_guid (varchar) – unique identifier for the process this work item belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
table document
- dockey (varchar) – primary key for document
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- classname (varchar) – no longer used
- bin_csize (integer) – compressed size of document in bytes
- bin_usize (integer) – uncompressed size of document in bytes
- bin (blob) – document bytes
- modify_date (date) – date document was last modified
table audit_trail
- cikey (integer) – foreign key
- domain_ref – domain identifier
- count_id (integer) – many audit trail entries may be made for each instance, this column is incremented for each entry per instance.
- block (integer) – when the instance is dehydrated, the batched audit trail entries up to that point are written out … this block ties together all rows written out at one time.
- block_csize (integer) – compressed size of block in bytes
- block_usize (integer) – uncompressed size of block in bytes
- log (raw) – block bytes
table audit_details
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- detail_id (integer) – part of composite key, means of identifying particular detail from the audit trail
- bin_csize (integer) – compressed size of detail in bytes
- bin_usize (integer) – uncompressed size of detail in bytes
- bin (blob) – detail bytes
table dlv_message
- conv_id (varchar) – conversation id (correlation id) for the message…this value is used to correlate the message to the subscription.
- conv_type (integer) – internal use
- message_guid (varchar) – unique identifier for the message…each message received by the engine is tagged with a message guid.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – identifier for process revision
- operation_name (varchar) – operation name for callback port.
- receive_date (date) – date message was received by engine
- state (integer) – current state of message … see com.oracle.bpel.client.IDeliveryConstants for values
- res_process_guid (varchar) – after the matching subscription is found, the process guid for the subscription is written out here. – res_subscriber (varchar) – identifier for matching subscription once found.
table dlv_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of delivery message payload in bytes
- bin_usize (integer) – uncompressed size of delivery message payload in bytes
- bin (blob) – delivery message payload
table dlv_subscription
- conv_id (varchar) – conversation id for subscription, used to help correlate received delivery messages.
- conv_type (integer) – internal use
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- process_id (varchar) – process identifier for instance
- revision_tag (varchar) – revision tag for process
- process_guid (varchar) – guid for process this subscription belongs to
- operation_name (varchar) – operation name for subscription (receive, onMessage operation name).
- subscriber_id (varchar) – the work item composite key that this subscription is positioned at (ie. the key for the receive, onMessage work item).
- service_name (varchar) – internal use
- subscription_date (date) – date subscription was created
- state (integer) – current state of subscription … see com.oracle.bpel.client.IDeliveryConstants for values
- properties (varchar) – additional property settings for subscription
table invoke_message
- conv_id (varchar) – conversation id for message, passed into system so callbacks can correlate properly.
- message_guid (varchar) – unique identifier for message, generated when invocation message is received by engine.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – revision tag for process
- operation_name (varchar) – operation name for receive activity
- receive_date (date) – date invocation message was received by engine
- state – current state of invocation message, see com.oracle.bpel.client.IDeliveryConstants for values
- priority (integer) – priority for invocation message, this value will be used by the engine dispatching layer to rank messages according to importance … lower values mean higher priority … messages with higher priority are dispatched to threads faster than messages with lower values.
- properties (varchar) – additional property settings for message
table invoke_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of invocation message payload in bytes
- bin_usize (integer) – uncompressed size of invocation message payload in bytes
- bin (blob) – invocation message bytes
table task
- domain_ref (integer) – domain identifier
- conversation_id (varchar) – conversation id for task instance … allows task instance to callback to client
- title (varchar) – current title for task, user specified
- creation_date (date) – date task was created
- creator (varchar) – user who created task
- modify_date (date) – date task was last modified
- modifier (varchar) – user who last modified task
- assignee (varchar) – current assignee of task, user specified, no engine impact
- status (varchar) – current status, user specified, no engine impact
- expired (integer) – flag is set if task has expired
- exp_date (date) – expiration date for task, expiration actually takes place on work item in TaskManaged instance, upon expiration task row is updated
- priority (integer) – current task priority, user specified, no engine impact
- template (varchar) – not used
- custom_key (varchar) – user specified custom key
- conclusion (varchar) – user specified conclusion, no engine impact

OWSM+ BPEL Asynch Process

Hi,
Need some inputs on " how to secure asynch BPEL Process using OWSM(10.1.3.0)"?
So far, I have created the server and the client agent - with simple log in the request and response pipeline(Server and Client).
Whenever the end asyn service is invoked; the OWSM logs the request and without waiting for the response from the end service , it creates an empty response message(as below)- for the server agent( The client agent does not show any response @ all).
Server Agent Reponse Pipeline log
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
<env:Body />
</env:Envelope>
Any help is apprecitated
Thanks,

Hi Edwin,
1.
i. Yes, I think I can get the required data from Task object, after it is updated.But I will need to update the Task object before sending request for complete task.
e.g.In the example of StockReviewSheet, if I need to save the info like, the Stock action buy or sell, entered by user in the input textfield, then I'll need to set that value to task variable.
Please confirm if correct.
ii.Secondly, there is some process, which initiated the task, waiting asynchronously for the task to complete. If we need to pass the response of the completed task (in the case of mentioned example, sell or buy AND number of shares entered by user, for a particular share) to the waiting process, then how to do it?
e.g.User1 submits the task(JSP1) and then later User2 completes the task(JSP2) with response as Yes or No
Then how the User1 will come to know of whether its Yes or No.As we have the values(Yes or No) in JSP2 (completeTask) but not in JSP1.
Above query (ii) is very important.Please help in this case.
iii. Also how this process waiting asynchronously(User1) is notified of task is complete?
2. Yes the IInstanceHandle API has the method to get the AuditTrail XML and related methods.
But the question is how to get instance of IInstanceHandle ?
We get IBPELProcessHandle isntance from IBPELDomainHandle and from the instance of IBPELProcessHandle we get array of IInstanceHandle objects. How to get the latest version of the IInstanceHandle from this array, as IInstanceHandle does not have any revisionTag related method to compare with and I do not have referenceID of the process to get IInstanceHandle directly.
Please mention the process in detail for getting reference of IInstanceHandle.
Thank You
Umesh

Task.toXML() creates xml that does not validate against WorklistTask.xsd

I am using the worklist API and I am using the toXML() function provided in the Task object to serialize my Task info to XML. It produces XML that looks alot like a "task" Element. But, it does not validate against the WorkflowTask.xsd schema. What is even more odd is that XML looks different than the xml I see when I look at the data in the BPEL Console.
For example, the first XML document below is from Task.toXML. notice that it's first child element is taskId. According to the xsd, that is not valid. The second xml document in this post is from the console. it appears to be valid.
Am I doing something wrong or should I just not expect the worklist api to produce valid xml? (correction: should I not expect the worklist api to xml that validates?)
<task xmlns="http://xmlns.oracle.com/pcbpel/taskservice/task"><taskId>0D7B97F1B138EE21E04017AC2B194357</taskId><title>Payment not posted by payee</title><isGroup>true</isGroup><acquiredBy/><owner>bpeladmin</owner><conclusion/><state>ASSIGNED</state><subState>ASSIGNED</subState><processId>ResearchRequestWorkflow</processId><processName>ResearchRequestWorkflow</processName><versionNumber>1</versionNumber><notm>1</notm><taskGroupId/><taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType><identificationKey>PAULA MERRILL, 2069</identificationKey><priority>3</priority><creator>bpeladmin</creator><creationDate>2006-02-23T14:53:08.000-05:00</creationDate><updatedBy>bpeladmin</updatedBy><modifyDate>2006-02-23T14:53:08.000-05:00</modifyDate><flexString1>1140724383057</flexString1><flexString2>PAULA MERRILL</flexString2><flexString3>PAULA MERRILL</flexString3><flexString4>PaymentId3489</flexString4><flexLong1>0</flexLong1><flexLong2>0</flexLong2><flexDouble1>0.0</flexDouble1><flexDouble2>0.0</flexDouble2><processVersion>1.0</processVersion><instanceId>2304</instanceId><domainId>default</domainId><approvers/><hasSubTasks>false</hasSubTasks><processOwner>bpeladmin</processOwner><pattern>SINGLE_APPROVAL</pattern><taskNumber>10240</taskNumber><systemString1/><systemString2/><systemString3/><versionReason>Task Created</versionReason><assigneeGroups>ResearchManager</assigneeGroups><payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee"><requester xmlns="http://www.pp.com/schema"><first>PAULA MERRILL</first><last>PAULA MERRILL</last><tax_id/></requester><payment_type xmlns="http://www.pp.com/schema" number="">insuranceauto</payment_type><record_info xmlns="http://www.pp.com/schema"><creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/><updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/></record_info><payment xmlns="http://www.pp.com/schema" id="3489"><bank_info bank_id="2" funds_model="RISK"/><payment_info><confirmation_number>5428</confirmation_number><amount formattedValue="77.00" value="77"/><payment_date>2006-01-06-05:00</payment_date><check_number>5851</check_number><funded>false</funded><merged>false</merged><network id="3" status="ACTIVE" type="C">MOORE</network><alert_on_completion>false</alert_on_completion><alert_number_days_before>0</alert_number_days_before><scheduled_info id="2278"><scheduled_for_date formatted="01/06/2006">2006-01-06-05:00</scheduled_for_date><scheduled_on_date formatted="01/06/2006">2006-01-06-05:00</scheduled_on_date><created_user_id>282950</created_user_id><updated_user_id>0</updated_user_id></scheduled_info></payment_info><payee_info id="24958" relationship_id="6004"><payee_account_number>JUNIT123</payee_account_number><nick_name>blahblah</nick_name><name>complexpayeenameforatest</name><address1>123 main street</address1><address2>c/o anybody</address2><city>Dark Cityrandomizer</city><state>CT</state><zip>06512</zip><network id="3" status="ACTIVE" type="C">MOORE</network></payee_info><customer_info id="2069"><name>PAULA MERRILL</name><customer_account_id>8</customer_account_id><customer_account_number>213</customer_account_number><customer_routing_number>111111111</customer_routing_number><address1>Ernest Hemingway Drive</address1><city>Springfield</city><state>IL</state><zip>62703</zip></customer_info><state_info><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number></state_info><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>0</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="22">Waiting for Decision</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="Mailed" id="11">Payment Sent</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number><record_info><creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info></state_history><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/><updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info><research_request>false</research_request></payment></payload></task>
When Im look at the same task in the BPELConsole, the task looks like:
<task>
<title>Payment not posted by payee</title>
<assigneeUsers/>
<assigneeGroups>ResearchManager</assigneeGroups>
<acquiredBy/>
<owner>bpeladmin</owner>
<payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee" >
<requester>
<first>PAULA MERRILL</first>
<last>PAULA MERRILL</last>
<tax_id/>
</requester>
<payment_type number="" >insuranceauto</payment_type>
<record_info>
<creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
<updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
</record_info>
<payment id="3489" >
<bank_info bank_id="2" funds_model="RISK" />
<payment_info>
<confirmation_number>5428</confirmation_number>
<amount formattedValue="77.00" value="77" />
<payment_date>2006-01-06-05:00</payment_date>
<check_number>5851</check_number>
<funded>false</funded>
<merged>false</merged>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
<alert_on_completion>false</alert_on_completion>
<alert_number_days_before>0</alert_number_days_before>
<scheduled_info id="2278" >
<scheduled_for_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_for_date>
<scheduled_on_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_on_date>
<created_user_id>282950</created_user_id>
<updated_user_id>0</updated_user_id>
</scheduled_info>
</payment_info>
<payee_info id="24958" relationship_id="6004" >
<payee_account_number>JUNIT123</payee_account_number>
<nick_name>blahblah</nick_name>
<name>complexpayeenameforatest</name>
<address1>123 main street</address1>
<address2>c/o anybody</address2>
<city>Dark Cityrandomizer</city>
<state>CT</state>
<zip>06512</zip>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
</payee_info>
<customer_info id="2069" >
<name>PAULA MERRILL</name>
<customer_account_id>8</customer_account_id>
<customer_account_number>213</customer_account_number>
<customer_routing_number>111111111</customer_routing_number>
<address1>Ernest Hemingway Drive</address1>
<city>Springfield</city>
<state>IL</state>
<zip>62703</zip>
</customer_info>
<state_info>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
</state_info>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>0</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="22" >Waiting for Decision</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="Mailed" id="11" >Payment Sent</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
</state_history>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
<updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
<research_request>false</research_request>
</payment>
</payload>
<conclusion/>
<state>ASSIGNED</state>
<subState>ASSIGNED</subState>
<processId>ResearchRequestWorkflow</processId>
<processName>ResearchRequestWorkflow</processName>
<processVersion>1.0</processVersion>
<instanceId>2304</instanceId>
<domainId>default</domainId>
<processOwner>bpeladmin</processOwner>
<taskId>0D7B97F1B138EE21E04017AC2B194357</taskId>
<versionReason>Task Created</versionReason>
<taskGroupId/>
<taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType>
<identificationKey>PAULA MERRILL, 2069</identificationKey>
<comments/>
<priority>3</priority>
<creator>bpeladmin</creator>
<updatedBy>bpeladmin</updatedBy>
<hasSubTasks>false</hasSubTasks>
<approvers/>
<pattern>SINGLE_APPROVAL</pattern>
<flexString1>1140724383057</flexString1>
<flexString2>PAULA MERRILL</flexString2>
<flexString3>PAULA MERRILL</flexString3>
<flexString4>PaymentId3489</flexString4>
<flexDouble1/>
<flexDouble2/>
<flexLong1/>
<flexLong2/>
<flexDate1/>
<flexDate2/>
<flexDate3/>
<attachment/>
<taskNumber>10240</taskNumber>
<creationDate>2006-02-23T14:53:08.955-05:00</creationDate>
<modifyDate>2006-02-23T14:53:08.955-05:00</modifyDate>
<isGroup>true</isGroup>
<versionNumber>1</versionNumber>
<notm>1</notm>
<expirationDate/>
<expirationDuration/>
</task>
Message was edited by:
gjacobi

I am using oracle.tip.pc.services.hw.task.impl.Task
that object has a toXML method.
To get that object, I am using the RemoteWorklistServiceClient.getWorlistTaskById method.
A word of caution. Not only am I still having the issue above (I had to hack my own WorkflowTask.xsd to make it validate) but I have noticed that the toXML() method actually returns different results when you think it would not. For example, I have something similar to the following code:
task.toXML()
task.toElement()
task.getPayload()
task.toXML()
The first and last toXML methods produce strings that do not match (it adds some empty elements to the end of the document). Weird. Very Weird.
Greg

Task outcomes

I'm using TaskQueryService in BPEL 10.1.3. I invoke queryTask method and obtain a list of Task.
I'd like to know which method I have to invoke to find task possible outcomes list.
Thans

You could also use the following method on TaskMetadataService.
* Get the outcomes for the given task object. The return value also contains
* the display values according to the locale specified.
* @param context The workflow context
* @param task The task object
* @param locale The locale of the users
* @return Map Map with key as outcome value and the value is the display value
* @exception TaskMetadataServiceException if an error occurs
public Map getOutcomes(IWorkflowContext context, Task task, Locale locale)
throws TaskMetadataServiceException;

BPEL Task Object

Similar Messages

Maybe you are looking for