sxmb_moni, no messages

[Former Member]

Hi Frnz

When I am going to SXMB_MONI i am getting No messages available for selection. I didnu2019t find any messages there.

I gone through some threads and did some thing in SXMB_ADM.

The category for all these parameters are Runtime.

SXMB_ADM --> integration Engine Configuration --> Specific Configuration --> and added the following parameters,

1. Logging --> value -->1

2. Trace_Level --> Value -->3

3. Logging_Propogattion > Value> 1

4. Logging_Sync > Value> 1

5.Engine_typevalue-HUB

6.IS_URL--value-I didnu2019t find any value for this

And finally QRFC_RESTART_ALLOWED---value-1, for this I given category as MONITOR.

Even though I did all these I am getting the same message as

No messages available for selection

Please give me the ideas what to do

Thanks

Munna

[Former Member · Accepted solution]

Hi Munna,

Give IS_URL value as -> http://<hostname>:<port>/sap/xi/engine?type=entry.....(port will be like 8xxx)

When you send some msg from system A to XI, the msg has to past through Adapter engine(if you are not using proxy) before going to Integration engine for execution of mapping and other routing steps...in your case the msg got stucked in Adapter engine itself....thts why you are not able to see any msgs in SXMB_MONI

Check in communication channel in RWB....there you can find the error....rectify it....

Also check the entry in SXMB_ADM->Integration Engine Config

Role of Business System : Integration Server

Corresponding Integration Server : http://<hostname>:<port>/sap/xi/engine?type=entry

Regds,

Pinangshuk.

[Former Member · Accepted solution]

Thanks Pinangshuk.

i gone through SXMB_ADM->INTEGRATION INGINE CONF-

here i am seeing Role of Buss System: INTEGRATION ENGINE

corresponding integration server: its empty

while clicking the empty box its opening a wizard its showing the path http://startxi:8000/sap/xi/engine?type=entry

coming back ,in specific configuration data

category: its empty, what i have to give, when i use help button here i am showing archive,deletion,idoc,monitor,perf,rfcadapter,runtime,sa_cons,tuning.

what i have to select for this category.

Thanks

munna

[Former Member · Accepted solution]

Hi,

Give Roll of Business System -> Integration server

Corresponding integration server -> http://startxi:8000/sap/xi/engine?type=entry

In Specific Configuration:

Select category -> Runtime : Parameters............ Value.............Default value

engine _type Hub undefined

IS_URL http://startxi:8000/sap/xi/engine?type=entry

LOGGING 1 0

LOGGING_PROPAGATION 1 0

LOGGING_SYNC 1 0

Set this parameters....

Regds,

Pinangshuk.

[Former Member · Accepted solution]

Hi Pinangshuk

thanks a lot i cleared the issue. i am showing all the messages in SXMB_MONI. i defined all the parameters what u have mentioned.

rewarding points

thanks pinangshuk

[former_member200962]

The IS_URL should have the following format:

http://<FQDN>:<port_no>/sap/xi/engine?type=entry

After doing the changes do a cache ...and then send some message (test) ....then you will find an entry....you wont find entry for message that were processed before doing changes to SXMB_ADM (logging/ trace)

Regards,

Abhishek.

[Former Member]

Hi,

Check in the communication channel logs...may be the error might have occured there...as you mentioned there is no entry maintained for the IS_URL which is very important for sending messages from Adapter to integrationengine ...

once the data gets passed to integration engine then only you can see messages in moni...

looks like messages has not sent to integration engine itself....

HTH

Rajesh

[Former Member]

Hi Rajesh Thanks for ur reply

i checked the messages in message monitoring there for adapter engine its showing all the logs are success and in the integration engine it showing the status to be delivered.

any how it have to show whether the message is error or not in SXMB_MONI, but it is not at all showing msgs in SXMB_MONI.

and i am not seeing the communication channel monitoring in the component monitoring.so i am checking the status in message monitoring.