Searching BPEL process instances not only by conversationId
Ever tried to find an instance through the BPEL client API, but not by its converstationID? Sometimes it might be needed to search for an instance, not by it's unique identifier, but by some keyword of the payload.
The API that is used to invoke a process offers you to set custom key properties. They can be searched afterwards and also modified at runtime.
To set these key properties while invoking the process use the com.oracle.bpel.client.NormalizedMessage:setProperty(key, value) API. which allows you to set specific instance properties. For using the searchable ones, we provide static constants within the NM, named INDEX1, INDEX2, and INDEX3. Use them as key when setting a property - and there you go.
At runtime, you can use the bpelx:exec activity and inside the setIndex(int pIndex, String pValue) API.
For searching those instances afterwards use the com.oracle.bpel.client.Locator:findInstances( com.oracle.bpel.client.util.WhereCondition ) API, which encapsulates a prepared SQL statement. What is does behind the scenes is to join the cube_instance with the ci_indexes table, and make the join searchable through the API.
Check out the sample code below
To fill the message with the searchable property use
[..]
NormalizedMessage msg = new NormalizedMessage();
msg.setProperty(NormalizedMessage.INDEX1, "Clemens" );
[..]
WhereCondition searchForClemens = new WhereCondition(SQLDefs.CX_INDEX1 + " = ?");
searchForClemens.setString(1, "Clemens");
[..]
Locator mLoc = ...
IInstanceHandle[] foundInstances = mLoc.findInstances(searchForClemens);
[..]
3 Comments:
Harald you are right - I took the wrong method into the sample. It should be Locator:listInstancesByIndex( WhereCondition )
thx for noting
10:05 PM
you need to persist the instance in between - checkpoint();
9:39 AM
appearently there is a bug in 10.1.3.1 - a column missing for the view this API relies on.
here are the steps .
1) in bpelx:exec - use the setIndex(index, value) method ..
2) then use the API ..
furthermore run the following statement against the dehydration store..
create or replace view admin_list_cx
as select ci.cikey, domain_ref as ci_domain_ref, process_id, revision_tag,
creation_date ci_creation_date, creator ci_creator,
modify_date ci_modify_date, modifier ci_modifier,
state ci_state, priority ci_priority, title,
status, stage, conversation_id, metadata,
root_id, parent_id,
index_1, index_2, index_3, index_4, index_5, index_6,
ci.test_run_id
from cube_instance ci, ci_indexes cx
where ci.cikey = cx.cikey;
commit;
5:52 AM
Post a Comment
<< Home