File Adapter, file picked up, message does not show in SXMB

[Former Member]

I have setup up a sending file adapter and corresponding sender agreement.

The adapter activates, finds the file, pulls the file and deletes it per the communication channel setup. The log in the adapter framework says:

"Up and running: Last message processing started 15:03:55 2005-04-26 last poll interval started 15:03:55 2005-04-26"

As expected for a successful pull.

However, the message never shows up in the integration server. I cannot find it in SXMB_MONI and the expected outbound interface never sends any data. I am expecting that the failure is between the adapter engine and the integration engine. Any ideas what could be causing this?

Regards,

chris

[Former Member · Accepted solution]

Hi,

The polling of the File adapter is independent of the sender agreement. So after the processing of the file, if it does not find any proper outbound interface to which it should assign the file, it will not reach Integration Engine.

A detailed description of the processing can be found at

RWB--> message monitoring. U will find whether the message has been successfully deliverd to the location

http://<hostname>:8000/sap/xi/engine/?type=entry

If it crosses this stage it should be visble in sxmb_moni.

Hope this helps,

Regards,

Siva Maranani.

[Former Member · Accepted solution]

Fabulous Siva,

I went to the message monitoring and checked on the AF side, they all failed witha system error. The log looked as follows:

transmitting message to endpoint

http://UEP00:800/sap/xi/engine/?type=entry using connection AFW failed due to connection being refused.

We will look into the services to see what is going on.

Thanks so much!

Chris

[Former Member · Accepted solution]

Hi,

It looks like the port number is incorrect.

User tr: SMICM to determine the correct port number

Bill

[Former Member · Accepted solution]

Sorry Bill typo. The port is 8000 in the above post.

As for SMICM, I went to services are saw

there was HTTP active on 8000 forthe XI host.

Should there be a separate service for the adapter framework?

[Former Member · Accepted solution]

Hi,

Try enter the url using the browser:

http://UEP00:8000/sap/xi/engine/?type=entry

You should be prompted for userid/password. After entering a valid user, there should be a response indicating empty request. This is okay.

If the above works, this means the userid being used by the adapter is either invalid or has a wrong password.

I believe the userid used is XIAFUSER. Try logon to XI ABAP via SAPGUI, using XIAFUSER. If this works, then the configuration must have invalid entries for the XIAFUSER password.

Bill

[Former Member · Accepted solution]

Hi Bill,

Thanks for the options, we think we just figured it out.

The global config for the URL was entered with the slashes as such "\" not "/" in the intergration configuration . So it was http:
not http://.

So it was trying to connect to

http:
UEP00:8000\sap\xi\engine?type=entry

We used the correct method and are able to connect as you suggested.

We think this is the issue so we changed the global config. However, it is still using the wrong path, how do we get it propogated out into the CACHE?

Regards,

Chris

[Former Member · Accepted solution]

Correction, we were NOT able to connect in the web browser. It is trying to connect to client 000 instead of 100 when the logon failure shows. Are the pipelines client specific? If so, where is this setup?

[Former Member · Accepted solution]

Hi,

Once you changed the global config in SXMB_ADM, it used be used immediately. There is no cache involved.

You might try the following to do a full adapter cache refresh:

http://server:50000/CPACache/refresh?mode=full

The userid requested must be: xidiruser

Bill

[Former Member · Accepted solution]

Hello,

I found how to change url in System Landscape settings.

Thanks&Regards,

Dipali