Alert Rules for Non-Central Adapter.

[former_member192375]

Hi,

Please could you assist on how to setup alert rules for errors happening on a Non-Central Adapter Engine.

We are currently getting alerts for Channel communication error from the PI Central Adapter Engine, but we have a Non-Central Adapter that is situated in our DMZ for communications with the external companies. When channel or message errors occur on this Non-Central Adapter Engine we require an alert rule to be triggered and linked to a Alert Category in the ABAP stack so that we can pro-actively respond to issues on this NON-Central adapter Engine.

Your assistance in this regard will be greately appriciated.

Regards

Willie Hugo

[former_member192375]

Hi,

All the normal monitoring in RWB is working for channels and messages that is happening on the additional Non-Central Adapter.

I have setup the an Alert Rule to be * for Adapter, so essentially all adapters, all channels and for all interfaces.

At this stage I have only two alert categories, one for the Integration Engine and one for the Adapter Engine.

We are getting alerts for errors happening on the Central Adapter Engine, but we are not getting Alerts for errors occurring on the Non-Central Adapter, although we are able to see the errors in the RWB.

Please can you assist with how it would be possible to get alerts into the Alert Framework from the Non-Central Adapter.

Regards

Willie Hugo

[Former Member]

Hi,

if your non-central J2EE adapter engine is connected to your integration server and has registered in your PI SLD then you will get the alerts from the normal alert rule for adpater engine. in componenet monitoring-non central adapter engines your adapter engine should be showing. Also in integration directory you have configured some channels for this non-central adapter engine. In that case if an error happen in any of the communication channel in non-central adpater engine, an alert will be captured by the regular alert rule for adapter engine and alert will be there in SALRT table in ABAP.

in alert rule, where did the alert occur just mention adapter engine. no additional configuration would be required. probably to test just use an alert rule with out any interface filter, just give * and do not check the "suppress multiple alerts" option since it will block alerts until the first is cofirmed.

But this will not work if you are using a plain J2SE adapter engine. this is not integrated to the normal alert framework.

regards,

francis