| Author |
Message
|
| MaheshPN |
 Posted: Thu Jun 19, 2003 6:55 pm Post subject: Workflow and EIP |
 |
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi,
I want know if anybody have tried to connect MQSeries Workflow with EIP(Enterprise information Portal). What actually we achieve. I am not clear about how these two works together.
Any inputs will be appreciated.
Thanks,
Mahesh
IBM Certified Solution Expert - MQWorkflow |
|
| Back to top |
|
 |
| mphartman |
| Posted: Fri Jun 20, 2003 7:38 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2003
Posts: 7
Location: Iowa
|
| EIP, now called Information Integrator for Content (II4C) in 8.2, offers a product feature called Advanced Workflow (ADWF). ADWF uses a limited license version of WebSphere MQ Workflow (MQWF) as its workflow engine. It incorporates a visual builder in the system administration client and leverages II4C's privilege system to restrict access. Users use the provided eClient as the workflow client. It's geared towards simple workflows centered around federated folders (new in 8.2). It's not as flexible as full MQWF but is more feature-rich than Content Manager Document Routing. |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Fri Jun 20, 2003 7:08 pm Post subject: Workflow and EIP |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Thanks,
I want to know more about it like, Can we link our excisting applications/Processes running in MQSeries Workflow to EIP/II4C? If so how it can be done?
Thanks,
Mahesh |
|
| Back to top |
|
|
| Andy |
| Posted: Sat Jun 21, 2003 11:55 pm Post subject: |
|
|
Centurion
Joined: 14 May 2003
Posts: 122
|
Possible only if configure EIP to connect to Workflow runtime database. No other way I think.
_________________
 Andy |
|
| Back to top |
|
|
| mphartman |
| Posted: Sun Jun 22, 2003 6:43 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2003
Posts: 7
Location: Iowa
|
| I'm not certain I know what you mean by "link" but keep in consideration that the II4C administration database tracks aspects of the workflow like ACL and things it calls "Actions" that aren't in a regular MQWF workflow. I'm not sure you'd what to incorporate existing MQWF processes into II4C anyway especially if you already have a capable client. I don't see what you gain. Just my 2 cents worth. |
|
| Back to top |
|
|
|
|
