cancel
Showing results for 
Search instead for 
Did you mean: 

ccBPM Receive Step not Working

Former Member
0 Kudos

Hello,

I have a very simple integration process in which the asynch. receive step is not working.

I can see in SXMB_MONI that the outbound interface is correctly routed to the receiver (the ip) and abstract interface. The error description that I get from SMQ2 is that; the process definition contains no receive steps for the message I am sending to the integration process.

This is very strange because in the integration directory I have declared a receiver and interface determination for the integration process and its corresponding abstract interface.

Many Thanks.

Edited by: Roberto Viana on Feb 23, 2009 8:40 AM

Edited by: Roberto Viana on Feb 23, 2009 8:41 AM

Accepted Solutions (1)

Accepted Solutions (1)

JoelTrinidade
Active Contributor
0 Kudos

Hi,

Recreate the required interfaces.

Rgds

joel

Answers (4)

Answers (4)

prateek
Active Contributor
0 Kudos

If you are very sure that you have configured the scenario correctly in IR, then just delete and reimport the Integration Process in ID. Then run the scenario again. Before running, make sure that there are no entries in smq2 and you have deleted all open BPM instances using SWWL transaction.

Regards,

Prateek

Former Member
0 Kudos

Gents,

Many thanks for you suggestions, however, the problem with the receiver step stiil there

Please advice what/where else to check???

I have checked all directory settings and everything looks fine, cache also ok, integration process and integration scenario all over again redeployed... Situation unchanged.

Once again; I am using an own defined SOAP envelope and I am passing this via JMS to PI ccBPM.

Below you see a sample of the message i am trying to read in my ccBPM:


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
	<soapenv:Header>
		<my_own_Header>
			<CorrelationID>String</CorrelationID>
			<MessageID>String</MessageID>
		</my_own_Header>
	</soapenv:Header>
	<soapenv:Body>
		<My_Payload>
			<value1>xxxxxx</value1>
		</My_Payload>
	</soapenv:Body>
</soapenv:Envelope>

Former Member
0 Kudos

Gents,

The problem was solved by deleting the whole Integration Process and recreating it in the repository. However, I still cannot explain what was causing the problem before...

Many thanks to all!

Roberto

Former Member
0 Kudos

Hi

Check the below

- If you use the Co-relations correctly

- check if cache is correct in SXI_CACHE for your BPM

Regards

Vishnu

former_member200962
Active Contributor
0 Kudos

Hi,

This problem can be due to:

1) Interface mis-match between the one included in the design in IR and the one configured in the ID.

2) Cache is not updated.

3) Check for any older versions fo your BPM in transcation SWWL....if there are any instances with errors then delete the instances....

4) Go to transaction SXI_CACHE and check the return code for your BPM...it should be 0.....

Regards,

Abhishek.

former_member181985
Active Contributor
0 Kudos

I think in Receiver Determination, you need to provide the correct Message Interface(for the inbound Message interface, IP) name which you are using for the receive step in IP.

Edited by: Praveen Gujjeti on Feb 23, 2009 2:23 PM