PI Messages Are Not Delivered To SAP NetWeaver BPM

7/10/2019 PI Messages are not delivered to SAP NetWeaver BPM - Technology Troubleshooting Guide - SCN Wiki
Getting Started Store
Community WIKI SAP Community Welcome, Guest Login Register Search the Community
Technology Troubleshooting Guide / … / Process Orchestration
PI Messages are not delivered to SAP NetWeaver BPM

Created by Former Member, last modified on Jun 14, 2013
Sending a message from SAP NetWeaver PI to an SAP NetWeaver BPM process failed. The PI messages are not delivered to SAP NetWeaver BPM and hence the processes do not start.
Possible cause 1: The data type of the payload is not correct

The SAP NetWeaver PI message monitor displays the following error: Transmitting the message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found.
To find the error:
1. Log on to the SAP NetWeaver Administrator (http://<host>:<port>/nwa).

2. Choose SOA > Monitoring > Message Monitor.
3. Select the message, which is not delivered.
4. In the Message Details, choose Message Log.
5. Find the above mentioned error.
The payload that is used to send messages from SAP NetWeaver PI to SAP NetWeaver BPM is not of correct data type or does not match the data type of the SAP NetWeaver BPM process.
Description: A start event or an intermediate message event of an SAP NetWeaver BPM process is bound to a service interface. When a message is sent, it conforms to the message structure defined in
the corresponding WSDL. In Process Orchestration scenarios, the messages are sent by SAP NetWeaver PI receiver business component.
As SAP NetWeaver BPM processes and SAP NetWeaver PI content can be created independently, it is possible that the interface assigned to the receiver business component and the one that is
assigned to the SAP NetWeaver BPM process start or intermediate message event do not match.
Solution
Make sure that the interface that is associated with the receiver business component and the one that is associated with the start or intermediate message event are same.
Possible cause 2: The target URL in the receiver channel or the host name as part of the
URL is not correct
A: Sending a message from SAP NetWeaver PI to SAP NetWeaver BPM process fails. The SAP NetWeaver PI message monitor displays the following error: Transmitting the message to endpoint <local>
using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP:
TEXT/HTML; HTTP 404 Not Found.
https://wiki.scn.sap.com/wiki/display/TechTSG/PI+Messages+are+not+delivered+to+SAP+NetWeaver+BPM 1/6
B: Sending a message from AEX to the SAP NetWeaver BPM process via Java Proxy Runtime (JPR) fails. The SAP NetWeaver PI message monitor displays the following error: Transmitting the
message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException:
Connection refused: connect
To find the errors:

3. Select the message that is not delivered.
5. Find the above mentioned errors.
Description: In the SAP NetWeaver Process Orchestration scenario, reliability is provided by the Java Proxy Runtime (JPR). JPR knows how to deliver the message to SAP NetWeaver BPM. But SAP
NetWeaver PI needs the information that the message must be delivered to JPR and not to any other Web services. Therefore, the location of JPR must be provided in the receiver channel configuration.
The JPR location is provided as URL value for the receiver channel. For general information about the receiver channel, refer to the SAP NetWeaver PI documentation.
Solution
In the integration configuration builder, enter the correct URL in the target URL field of the receiver communication channels. Enter the URL as follows: http://localhost:
<port>/MessagingSystem/receive/JPR/XI
1. Open the integration flow that has a problem.

2. Choose the receiver channel (arrow to the receiver business system).
3. Go to the Adapter-Specific tab.
4. Enter the target URL in the format mentioned above.
In case of Swing-based UI
1. Choose Communication Component > Business Component > {Receiver Business System} > Communication Channel > {Channel associated with receiver business system}.
2. Choose the receiver channel.
3. Choose Parameters > General.
4. Enter the target URL in the format mentioned above.
Possible cause 3: No or invalid user credentials are used in the configuration

The SAP NetWeaver PI message monitor shows following error: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized.
To find the error:

No or invalid user credentials are used in the configurations of SAP NetWeaver PI or integration flow of the receiver channel.
Solution
Enter the correct user credentials in the authentication data of the receiver communication channel in the integration configuration builder. In addition of the correct user and password, also check whether
the appropriate roles are added to this user.
The following roles must be assigned to the user configured in the receiver channel:
SAP_XI_APPL_SERV_USER
SAP_BPM_TRIGGER_EVENT
Assigning roles

2. Coose Configuration > Security > Identity Management.
3. On the Overview tab, in the Search Criteria field, choose User.
4. Enter a few initial letters of user and choose Search.
5. Select the correct user from list.
6. On the General Information tab, in the Security Policy field, select Technical User.
7. Go to the Assigned Roles tab and add the roles that are mentioned above if they are not already assigned.
Setting user credentials in the receiver channel configuration
1. Open the integration flow that has a problem with sending the messages.
2. Choose the receiver channel (arrow to the receiver business system).
3. Go to the Adapter-Specific tab.
4. Enter the correct user name and user password.
In case of Swing-based UI
1. Choose Communication Component > Business Component > {Receiver Business System} > Communication Channel > {Channel associated with receiver business system}.
2. Choose the receiver channel.
3. Choose Parameters > General.
4. Enter the correct user name and user password.
Possible cause 4: The receiver interface of the integrated configuration does not match with
the process start/intermediate message event interface
SAP NetWeaver PI message monitor displays the following error: Unexpected uriID '/{http://sap.com/xi/Runtime/TestCase\}xmb_SS_Order_EO_In'. Found: BindingData 'null', interfaceMapping 'null'
interfaceDefinition 'null'.
To find the error:

Description: The SAP NetWeaver BPM process start or intermediate message event is bound to a service interface. When a message is sent, the message must conform to the message structure
defined in the WSDL. In process orchestration scenarios, the message is being sent by SAP NetWeaver PI receiver business component.
As the SAP NetWeaver BPM process and SAP NetWeaver PI content can be created independently, it is possible that the interface assigned to the receiver business component and the interface
assigned to the SAP NetWeaver BPM process start or intermediate message event do not match.
Solution
In the process composer, select the start/intermediate message event of the SAP NetWeaver BPM process and assign the appropriate interface.
Alternatively, you can change the interface that is assigned to the receiver business component of the respective integrated configuration builder.
In case the re-import/re-assignment of the service interface does not solve the problem, check, in the Enterprise Service Repository (ESR), whether the message type's namespace and its XML
namespace are harmonized. If they are not the same, change the XML namespace according to the general namespace. In the Developer Studio, connect again to the ESR and import the service
interface again. Check whether the XML namespace of the message type has been also updated in the Developer Studio. To do so, open the Enterprise Service Repository perspective in the Developer
Studio and double-click the message type. Compare the XML namespace with the target namespace. They need to be the same, now.
No labels
Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright Cookie Preferences Follow SCN

PI Messages Are Not Delivered To SAP NetWeaver BPM - Technology Troubleshooting Guide - SCN Wiki PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PI Messages Are Not Delivered To SAP NetWeaver BPM - Technology Troubleshooting Guide - SCN Wiki PDF

Uploaded by

Copyright:

Available Formats

7/10/2019 PI Messages are not delivered to SAP NetWeaver BPM - Technology Troubleshooting Guide - SCN Wiki

Getting Started Store

Technology Troubleshooting Guide / … / Process Orchestration

Possible cause 1: The data type of the payload is not correct

To find the error:

1. Log on to the SAP NetWeaver Administrator (http://<host>:<port>/nwa).

To find the errors:

1. Log on to the SAP NetWeaver Administrator (http://<host>:<port>/nwa).

1. Open the integration flow that has a problem.

Possible cause 3: No or invalid user credentials are used in the configuration

To find the error:

1. Log on to the SAP NetWeaver Administrator (http://<host>:<port>/nwa).

1. Log on to the SAP NetWeaver Administrator (http://<host>:<port>/nwa).

Setting user credentials in the receiver channel configuration

To find the error:

1. Log on to the SAP NetWeaver Administrator (http://<host>:<port>/nwa).

Contact Us SAP Help Portal

You might also like