cancel
Showing results for 
Search instead for 
Did you mean: 

How to access monitoring error logs in mapping

former_member208396
Participant
0 Kudos

Hello Experts,

I have created one SOAP to JDBC Sync scenario where I am sending SOAP messages from Altova Tool and accessing MS SQL server in receiver side.

In my scenario I just want to access sxi_monitor error logs in message mapping to configure it in response message which needs to be sent to Altova tool as a proper response as an example: Suppose I am trying to add one ID filed=123 to MS SQL sever and ID as 123 already exists in database. So as a Primary Key element it is getting failed in call adapter step which I can see in SXI_MONITOR T-Code but Altova is not getting proper response saying "Key element already exists" So I just want to read error message in MONI and want to configure relevant error message(say "key already exists in DB") to response to JDBC towards SOAP sender.

Please help..!!

Regards,

Vishnu

Accepted Solutions (1)

Accepted Solutions (1)

former_member183816
Active Participant
0 Kudos

Hi VIshnu,

PI Scenarios  generates two kinds of error.

  1. Application error
  2. System error

In case of Application error from receiver application, you can use fault message type and fault mapping in PI to send the error back to client.

In case of System errors from receiver application, there is no standard way to send the error back to client. That's why we use alerts.

Referred from section Types of errors


Basically, you need to map your jdbc fault message to soap fault message. You will find a fault message tab in service interface, also a fault mapping tab in operation mapping. Use that.

I am not sure if there is any standard JDBC fault message type in PI but for soap fault they have a standard fault message type which you can use.

So you need to explore following things in order to achieve your requirement,

1. How to capture jdbc faults in PI?

2. How to configure/map fault message in PI? (it's simple)

3. There is a possibility that your fault mapping won't kick in, if PI is generating system error for this case.


Answers (0)