Monitoring Performance Prerequisites The user account you use should be assigned to one of the Process Integration monitoring

roles. For more information about which roles allow you to view monitoring information, see Monitoring Roles . Context When you want to obtain statistical data about the performance of message processing in the Adapter Engine, you can use the performance monitor. Within this monitor, the performance is gauged by measuring the amount of bytes processed over a given time period. The performance details provided by the monitor are useful for administrators who need to now the amount of time spent by messages at various points of their life cycle in Adapter Engine. These points ! nown as measuring points" are at the following stages of message processing# $essage is put in the %ueue. $essage is retrieved from the %ueue. &all to a module in the Adapter Framewor .

The performance monitor allows you to choose the time period for which you want to measure the message processing. 'ou can also choose whether you want to see information for all processed messages, or only for messages with common parameters such as the sender or receiver component, interface, or %uality of service.'ou can also download this data as an E(cel sheet and save it locally. Procedure

1. )aunch the *+) http#,,-host.#-port.,pimon.

eg#http://192.168.10.1 !: 0000/"imon

2. &hoose

$onitoring

Adapter Engine

Performance $onitoring .

/. &hoose the period of time for which you want to see the performance data. 0. &hoose the aggregation interval. If you want to obtain larger amount of details about the performance of message processing in the Adapter Engine you should choose longer aggregation interval.

5. 1ptionally, choose Advanced 2election and enter the parameters of the

messages for which you want to see the performance data.

The parameters you can specify are inbound and outbound channel, sender and receiver party and component, interface and interface namespace, server node, %uality of service, and direction.

6. &hoose 3o .
4. To download the data to an E(cel sheet, perform the following substeps. o o &hoose E(port. To download the overview of messages in the aggregation intervals, select 1verview from the dropdown list. In the E(port to E(cel popup screen, clic the lin and choose the local path and save the E(cel sheet. &hoose 2ave. o To download the detailed information of messages in a particular aggregation interval, select an interval in the topmost table, and choose 5etailed 5ata from the dropdown list. In the E(port to E(cel popup screen, clic the lin and choose the local path and save the E(cel sheet.

#$/P$: %&P #$ 'rou(les)ooting *uide:

a list of common errors,problems in 2AP 6I and their possible resolutions. This 3uide will help you troubleshoot your integration scenarios in 2AP 6I,PI. This is in no way an e(haustive list. 'ou can add your points,ideas to this list. Please feel free to post your inputs using the comments form at the end of this article. Cac)e +"date Pro(lems : *se transaction 26I7&A&8E to update the Integration 5irectory cache. Alternatively, you can use the following *+)s to update the &PA cache. *se 6I5I+*2E+ to refresh the cache. For complete cache refresh 9 http#,,:hostname;#:port;,&PA&ache,refresh< mode=full For delta cache refresh 9 http#,,:hostname;#:port;,&PA&ache,refresh<mode=delta If this does not solve the issue, chec transaction 2)5&8E&> to ensure that connection to 2)5 is available. If the connection fails, chec the configuration in the transaction 2)5API&*2T. $a e sure that the password maintained is correct and the maintained service user is not loc ed.

?ow in the Integration +epository go to Environment &lear 2)5 5ata &ache. Also go to Integration 5irectoy and clear the cache using menu Environment &lear 2)5 5ata &ache. 1pen the 6I 2tart Page and clic on Administration. 1n the +epository tab, choose &ache 1verview. +efresh the cache using the buttons,icons on the right. *se 6I5I+*2E+ to refresh the cache. &arry out cache refresh in the same way on the 5irectory and +untime tabs. If you are facing cache update problems in your @P$ !say you have modified the @P$, but when e(ecuted old version of the @P$ is pic ed up instead of the new one", run the transaction 2WF76I7&*2T1$IAI?3 and press FB carry out automatic @P$,Wor flow &ustomiCing. Routing ,rrors ?17+E&EIDE+7&A2E7@E or ?17+E&EIDE+7&A2E7A2'?&

This means no receiver could be found. &hec your +eceiver 5etermination. Activate and update cache. Asysnchronous messages can be manually restarted. T117$A?'7+E&EIDE+27&A2E7@E

$ore than one receiver found. &hec your I5 configuration to ensure that there is e(actly one receiver for the synchronous message. $ultiple receivers for synchronous interfaces are not permitted. Ma""ing ,rrors E&17&1$$*?I&ATI1?7FAI)*+E

&hec whether +F& destination AI7+*?TI$E7E&12E+DE+ is correctly configured ?17$APPI?3P+13+A$7F1*?5

Ensure that mapping program e(ists and is activated. If it e(ists then update the cache. E6&EPTI1?75*+I?37E6E&*TE

This error occurs due to erroneous 6$) formatting. &hec your mapping program and ensure that you supply valid input data. Messages stuc- in queues &hec the %ueues using transactions 2$FG !outbound",2$FH !inbound". +esolve the displayed errors. 'ou can cancel the messages from 26$@7$1?I. E(ecute )*W if necessary and avoid deleting entries manually. Con.ersion ,rrors

*nable to convert the sender service 6666 to an A)E logical system

This error occurs in case of scenarios with I5oc adapters. Whenever you use business systems, ma e sure that the corresponding logical system name is maintained in the 2)5. 1pen your business system in the Integration 5irectory. 2witch to &hange mode. Access the menu path 2ervice Adapter 2pecific Identifiers. &lic the button that says I&ompare with 2ystem )andscape 5irectoryJ and chose Apply. 2ave and activate your change list. In case of business services, you can manually type a logical system name in the Adapter 2pecific Identifiers if re%uired. This name should match the corresponding logical system name defined in the partner 2AP systemJs partner profiles. ,rrors on t)e out(ound side 2ometimes the lin between 2AP 6I and the target system !say E+P" goes down and messages fail on the outbound side. It may not be possible to restart them from using +W@ or the transactions li e 26I7$1?IT1+,26$@7$1?I. In such cases, you can follow the procedure outlined in the following article 9 /ealing 0it) errors on t)e out(ound side. As I said, this is not an e(haustive list. Feel free to add troubleshooting tips that you may have encountered while wor ing with 2AP 6I. *se the comments form below to add your ideas.