Problems in Test Component Explorer

We are a team to prospect for SOA development and we have been using WebSphere Integration Developer (WID) 6.1.2 with all available FIXES till Sep/04/2008. We work with BPEL 1.1 generated by the integration between Modeler 6.1.2 and WID. However we have had problems while trying to work with Component Test Explorer, available tool for testing of BPEL process in this latest version of WID.
The problem is that the Component Test Explorer was unable to identify the existence of Human Tasks in a BPEL process, preventing the emulation of the Human Tasks.
After researching the Help of the Component Test Explorer, we realize the Human Tasks should be identified by it automatically, which in fact does not occur. As we have not had this kind of problem to try to use the Component Emulation, we would like to know if we need any extra configuration, not specified in the Help of the tool. Or if it is necessary some FIXME which has not been published yet. Or if Instalation Manager is not capable of searching automatically the site for updates from IBM yet.

Thanks for your attention,

Unfortunately, the core of the questions is not coming across.

o I Understand you are using the latest WID 6.1.2 with fixes
o I understand you are building BPEL processes that started life being modeled in Modeler
o I understand that you are using the Component Test part of WID to test

But I don't know what you mean when you say "unable to identify the existence of Human Tasks in a BPEL process". What errors were produced? Do you have screen shots or detailed descriptions of the symptoms of the errors? Do you have a Project Interchange file that you can share that will allow us to see the context?

Emulating human tasks
The Human Task Emulators tool is very similar to the Component Emulators tool. You choose the element to emulate and specify the emulation rules.
The explorer section shows all of the human tasks that are defined on the system, including stand-alone human tasks and inline human tasks. Inline human tasks are nested within their encompassing BPEL process. The details section contains the details of the human task emulator.
If you click the human task, the Emulator Rules screen for that human task appears.
25
To claim a task, select the Security tab and enter the user name and password of the user that will be claiming the task.
In the Security tab, you can also set the status for this human task emulator, similar to the component emulator. The decorator on the human task icon in the explorer section has a check mark to denote that the human task is being emulated.

I tried to recreate your problem ... but failed. When I built a sample process with an in-line human task, the task showed up as emulatable just fine. I have enclosed my simple PI file ... maybe you can test with this. If this works but yours doesn't, maybe post your PI file and we can see if there is something interesting about your environment.

I am running WID 6.1.2-20080615_0659

I also have tried this, as I have done it many times and was amazed that it wasn't working. It seems to work OK for me. I am also on WID v6.1.2. (although I have not put on any patches)

One thing to do is to verify that your human task has been invoked. Often this happens when a process takes a different path than expected and hence the human task is bypassed.

As you are using v6.1.2 you can use the fine grained trace facility to be able to view the path through your BPEL process to see why it hasn't invoked your human task. It's a great feature of WID and I highly recommend it.

Also check that you haven't set up any programmatic human task emulations which would cause your task to be automatically claimed and completed.

Following, I have enclosed the PI.

Thanks a lot!

Hi guys.

We have been doing tests in Test Component Explorer and we discovered which environment causes the failure that we reported previously. The failure occurs when BPEL is generated from Modeler, because Modeler creates the processes within the processes catalog what, in WID, become a package. Otherwise, test component explorer doesn't recognize processes which are inside the packages. We have reached this conclusion because we have taken a process built from Modeler and we extracted it from inside the package by hand and changed its XML files. So, it had its Human Tasks identified.
We also did the inverse way, including a process done directly in WID (which had its Human Tasks identified by test component explorer) within a package like Modeler would do. And now, the BPEL process has no more Human Tasks identified.
I would like to know if somebody has any information about if this bug has already been fixed, or if somebody knows how I can report this problem to IBM, in order to be analysed for them.