cancel
Showing results for 
Search instead for 
Did you mean: 

Doesn't have XI adapter on Adapter Engine Monitor

Former Member
0 Kudos

Hi Experts,

I am doing File2File scenario with J2SE->XI->J2SE direction. So that I created a communication channel(CC) with XI type and Receiver role. It have no error, the status of message is always "Waiting". The sender and receiver file adapter on J2SE also has no error.

I checked adapters on my XI server(in XIRWB), I don't see XI adapter in it. It has adapters like: BC,CIDX,FILE,JDBC... I dont' know why.

Have you got any ideas, please help me. Thanks very much.

thach vn

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

This message was moderated.

former_member187339
Active Contributor
0 Kudos

Hi,

Make sure you have a receiver j2se with the same service number and path....

Regards

Suraj

Former Member
0 Kudos

Hi S.R.Suraj,

I know how it is important, so they are same. Sure

Thank you.

former_member187339
Active Contributor
0 Kudos

Hi,

Its a strange problem then..

then lets start with basics..

1. Do a pinig test from XI box to the machine where j2se is installed. Is it successful?

2.Are you able to remotely log in to the machine from XI box?

3. Are you able to open the J2SE adapter engine home page from XI?

Is there any other interafce which uses XI Adapter asa areceiver in you XI environment (say for abap proxy etc). If so then is it working properly?

Regards

Suraj

Former Member
0 Kudos

Hi S.R.Suraj,

I tested some case that you suggested.Ping and open the J2SE home page successfully from XI server.

I only wonder about the part of configure of FileReceiver is XI.httpPort=1000 and XI.httpService=/file/test. When I run it via browser (http://host:1000/file/test), it have error "HTTP/1.0 501not implemented"

I think the problem is here. Have you got any ideas?

Regards,

vn thach

former_member187339
Active Contributor
0 Kudos

Hi,

I dont have any j2se servers configured here to check this...but i guess this error message is not an issue to worry about, as it is conveying that this type of request is not supported by the j2se server.

Regards

suraj

Former Member
0 Kudos

The response you see comes from the J2SE listener - the http command your browser sends is not implemented.

It indicates however that the http service is running on that port and ready to receive data from XI.

What you need to make sure is that your J2SE webUI is listening on another port than your adapters. If that is the case, log in to your J2SE webUI, check if your receiving adapter is Started (Initialized won't suffice) and check the logs if anything shows up.

Last item to check if also that fails:

On your XI box, issue the following command:

telnet host 1000

and see if you get a reply or a "connection refused".

Regards,

Stefan

Former Member
0 Kudos

Hope this discussion helps

Please check the reply by Vinod

Regards,

Manjusha.

Former Member
0 Kudos

Hi Manjusha,

I saw that thread. The fact that, in WebAdmin, it has already started. I also do that steps, the XI adapter doesn't exist in Adapter list.

I am using XI 7.0 SP18. Thank you.

vn thach

former_member200962
Active Contributor
0 Kudos

Please note that XI/ HTTP/ IDOC adapters (channels) are not available in RWB for monitoring...no matter what version of XI/ PI you are using....issue not related to SP/ Cache....

Regards,

Abhishek.

Former Member
0 Kudos

Hi Abhishek,

Thanks so much for your useful info.

vn thach

jyothi_anagani
Active Contributor
0 Kudos

Hi vn thach ,

This is the problem with your Java Stack. Ask your BASIS people to restart the java server. They can only solve your issue.

Thanks.

Former Member
0 Kudos

Hi Jyothi,

I restarted the XI server. It still doesn't work.

Thanks.

former_member187339
Active Contributor
0 Kudos

Hi,

Is your message reaching XI? That means is there entry in SXMB_MONI? If yes then there is no issue with the sender channel (else you can see the error in J2SE sender itself).

Now are you getting this error in Receiver side? If so then the message in moni will be going into automatic restart/error state. Is this the case?

Check whether the certificates (in strust transaction of XI) and credentials (in Receiver XI channel) are correctly used.

Regards

Suraj

Former Member
0 Kudos

Hi S.R.Suraj,

The message has already reached the XI. I checked in SXMB_MONI with payload same as XML file. Sender and Receiver adapter on J2SE has no error.

In SXMB_MONI, the Status is "Scheduled for outbound processing" and Q.Status is "Stop".

I have checked all parameters. Still not solve the problem.

Do you require more any detail info? I will post them

Thanks

vn thach

Former Member
0 Kudos

In SXMB_MONI, the Status is "Scheduled for outbound processing" and Q.Status is "Stop".

Check transaction smq2..You would be having an error message there

former_member187339
Active Contributor
0 Kudos

Hi,

Can you post teh error message which is there in MONI. It might have failed in Call adapter right?

Also confirm these

1. Credentials in Receiver channela re correct. If possible please provide the uid. This uid shoudl be a registered user in J2se receiver.

2. Strust transaction of XI is having the certificate in it.

Regards

Suraj

Former Member
0 Kudos

Hi Manjusha,

The message is "SYSFAIL". So, How will I do about that?

Please help me if you have the solution. Thanks

vn thach

Former Member
0 Kudos

Hi S.R.Suraj,

The message error in MONI is "SYSFAIL". OK, I will show you all info of the scenario config.

1. On J2SE that was installed in WinXP PC with IP is 10.10.1.25

1.1 On FileSender adapter like this(no error):

mode=FILE2XMB

XI.TargetURL=http://MyHost:8002/sap/xi/engine?type=entry

XI.User=PISUPER

XI.Password=abcd1234

XI.Client=001

XI.Language=EN

XI.QualityOfService=EO

XI.SenderService= BS_PlainJ2SE_Sender

XI.ReceiverService= BS_FileRecv

XI.Interface=MI_Material_toPPS_OB

XI.InterfaceNamespace=http://gml.com/xi/XI/Tutorials

file.type = xml

file.sourceDir=D:
Thach
Input

file.sourceFilename=xi_test.xml

file.processingMode=test

file.pollInterval=10

1.2 On FileReceiver adapter like this(no error)

mode=XMB2FILE

XI.httpPort=1000

XI.httpService=http://10.10.1.25:1000/file/test

file.createDir=0

file.targetDir=D://Thach/Output

file.targetFilename=output.xml

file.writeMode=create

file.writeMode=addTimeStamp

2. On XI ID like this

One Business system with name BS_PlainJ2SE_Sender. It has no communication channel(CC)

One Business service with name BS_FileRecv. It has 1 CC with name CC_File_Recv_Service. The detail config of this CC as:

. Adapter type: XI

. Role: Receiver

. Transport protocol: HTTP 1.0

. Msg protocol: XI3.0

. Addressing type: URL address

. Target host: 10.10.1.25

. Service number: 1000

. Path prefix: file/test

. Authentication type: Non-SAP system

. Username: SAP (account for J2SE adapter)

. Password: abcd

One Receiver Determination, Interface Determination, Receiver Agreement

No Sender Agreement (the tutorial says like that)

Both XI server and Local J2SE engine locate on LAN

Thank all of you for your interest.

vn thach

Edited by: vn thach on Jul 31, 2009 5:11 AM

former_member200962
Active Contributor
0 Kudos

SYSFAIL......what is the status of your Queue in SXMB_MONI?

Update:

Just checked one of your replies....you mentioned Queue is stopped....did you followed the procedure mentioned in the below thread:

Check for my reply in there

Regards,

Abhishek.

Edited by: abhishek salvi on Jul 31, 2009 8:57 AM

Former Member
0 Kudos

The message is "SYSFAIL". So, How will I do about that?

It could be an issue with the registration of queues.

As suggested by Abhishek, try restarting the entries in the queue.The message should hopefully pass through.

If it doesn't happen, please double click on the 'SYSFAIL' message line and see if you find a detailed error description.

Former Member
0 Kudos

Hi Abhishek and Manjusha,

I try to restart the message, It doesn't work.

The detail of error when I check in MONI: *CLIENT_RECEIVE_FAILED | 400 | ICM_HTTP_CONNECTION_FAILED*

Detail in Call Adapter:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>

<SAP:P1>400</SAP:P1>

<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>

<SAP:Retry>A</SAP:Retry>

</SAP:Error>

Regard,

vn thach

former_member200962
Active Contributor
0 Kudos

Check pt.2 of this blog: /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

I hope that all the receiver-related Configuration objects (Receiver CC, Agreement) are configured properly....all the details and the message structure are accurate and no information/ node/ tag is missing

Regards,

Abhishek.

Edited by: abhishek salvi on Jul 31, 2009 10:13 AM

Former Member
0 Kudos

Addition to what Abhishek has given

Refer this troubleshooting guide

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283&overrid...

Pg 54 ,55

Check point no:2 under Problem

XI is trying to send a message to the messaging system but fails with a

communication error, for example:

<SAP:P1>400</SAP:P1>

<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>

Following to it you will find the corresponding analysis and solution for point no:2

former_member187339
Active Contributor
0 Kudos

Hi,

IT seems you are not able to send message to receiver j2se adapter. There is some connectivity issue between XI and receiver J2SE.

Check whther the following url gives you some results or not:

http://10.10.1.25:1000/file/test

are you able to open the j2se url from XI machine? Recheck the ports and file path a;so the user shoudl not be locked in J2SE side

Regards

Suraj

former_member192295
Active Contributor
0 Kudos

Hi,

Check with your basis team, i think somewhere option is mising. That is the reason XI adapter not getting in list. They will sort out easily. Development level we don't have any option.