on 07-30-2009 9:47 AM
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
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
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
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.
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
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
Addition to what Abhishek has given
Refer this troubleshooting guide
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
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.