cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP --> BPM -->CRM--> BPM -->DWH

Former Member
0 Kudos

hi All,

i have a scenario:

Empsystem -


> XI -


> DWH

CRM

Empsystem to XI -- HTTP

XI to CRM is a synchronous call via SOAP

and XI to Datawarehouse is a JDBC connection.

I have done the required design and made the async-sync bridge and done with the configurations also.

but when i test it using a HTTP client and then monitor the processed XML messages it gives the processed succesful flag. but when i go to SXMB_MONI_BPE and try to monitor the process selection using my BPM, i m getting the message:

"No work items exist"

What does this imply?

Deepti

Accepted Solutions (0)

Answers (1)

Answers (1)

prateek
Active Contributor
0 Kudos

Have u created two receiver determination

1. Empsystem sender and BPM receiver

2. BPM sender and DWH receiver

Another design posibility would be the use of SOAP lookup /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function

Regards,

Prateek

Former Member
0 Kudos

We will require 3 receiver determination in this case , right?

1. Empsys to BPM

2. BPM to CRM

3. BPM to DWH

prateek
Active Contributor
0 Kudos

2nd and 3rd can be combined in single receiver determination step

Regards,

Prateek

Former Member
0 Kudos

yeah, but why is the message i have mentioned coming when i want to check my BPM in SXI_MONI_BPE--> process selection

Deepti

prateek
Active Contributor
0 Kudos

Perform the following

1. Check BPM by pressing F7 for ur integration process

2. Goto sxi_cache and check status of ur BPM. Ot should be 0 not 99. If its 99 then refresh the cache

Regards,

Prateek

Former Member
0 Kudos

Hi,

In message monitoring, when you scroll towards right hand side, there are inbound & outbound columns.

When you click on PE in these columns, does it take you to the BPM (Work Flow) log?

Regds

Pushkar

Former Member
0 Kudos

Thanks for all your replies.

The issue was with the server, the user "WE_BATCH was locked , hence my outbound interface was still in scheduled state.

Once that was unlocked, the issue is solved and the data was updated in the DB.