on 03-08-2006 12:55 PM
Hi
I have reinstalled the XI-Server and implemented a simple File-to-File scenario with and without BPM but neither one worked. The file wasn't deleted from the server.
no messages appear in sxmb_moni
Maybe a problem with the adapter engine?
What should I check?
Hi GOkhan,
Can you go to the RunTimeWorkbech--> Adapter Monitoring and check if your File Adapters are displayed there. Check the status of your File adapter and let us know.
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there only JPR in there ?
All the adapters should be listed there..including FIle..IDOc..rfc..etc...
Pls make sure all the post install steps have been done correctly.
steps to check for are :-
the relevant basis content has been imported and the CPACahce has been refreshed.
Also in the Component Monitoring of RWB, make sure the Adapter Engine component is in Green Status.
Thanks,
Renjith
Hi,
If you need some documentation on XI settings to check if your Adapters have been properly installed, I would suggest these links,
Regards,
Bhavesh
Hi Gokhan,
Please go thru the following links and clear all your doubts regarding a File-to-File Scenario.
Communication channel:
http://help.sap.com/saphelp_nw04/helpdata/en/65/b11c409ce22402e10000000a1550b0/frameset.htm
Receiver agreement:
http://help.sap.com/saphelp_nw04/helpdata/en/56/02e63f48e58f15e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c1/5194426b44c56ae10000000a155106/frameset.htm
Sender agreement:
http://help.sap.com/saphelp_nw04/helpdata/en/db/73e03fc2269615e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/22/522041cfb7f423e10000000a155106/frameset.htm
For detailed info, I would suggest that you go through these weblogs:
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
And if this is the first time that you are trying the BPM, I would suggest that you try a simple scenario, get a hang of BPM and then move on to the advanced scenarios that you are trying.
This is a good blog for starters on BPM,
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Also, this info on theoretical info on BPM can also help you understand how to use BPM better,
http://help.sap.com/saphelp_nw04/helpdata/en/78/62373f58502e48e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
For a blog on how to use Synch / Asynch Bridge, I would suggest this link,
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi
If u want anymore help with anything else please do reply back.
Regards,
abhy
Message was edited by: Abhy Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey guys
First of all, you are great and pretty quick.
My first problem/mistake:Importing the XI Content for Software...
Afterwards, the file could be sent but not written.
I found out that the URL of the Business System XI had the wrong URL.
"http://localhost:8000/sap/xi/engine?type=entry"
I used the protocol "htto" which is not available
Thanks.
Hi Gokhan,
I would also suggest that you go through Michal's weblog, Question 3 under Adapters,
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.