Seeburger adapter monitoring

We are running Seeburger AS2 adapter with XI3.0.
All inbound messages that the adapter can handle are passed to XI and we have access to those from XI message monitoring.
From there we have alerting setup.
Whenever an external party presents a message with a bad certificate the AS2 adapter refuses the message.
We can see trace of that in the adapter monitor. But there is no message in error passed to XI. So nothing we could get in message monitoring.
We saw we have a logfile containing those errors on the server. We could setup a logfile monitor on this file and get errors in CCMS. And from there, we could trigger alerts. But that does not look very elegant.
Is there a best way to get Seeburger adapter error generating alerts ?

Hi,
If the check is happening in the Adapter then the Alerts needs to be raised by Adapter framework.
So you have to set up Alert rule for the Adapter framework.
The message goes to message montioring only if the adapter sends the date to the Adapter engine and then you can see the message in the message monitoring.
If the rejection is at AF levelt hen you need to check in the Communication Channel if you are getting the Error?
Regards
Vijaya

Similar Messages

Error in Seeburger Adapter

Hi Experts,
We are sending a message to a Partner, and i can see the message processed succesfully in the SXMB_MONI and also in the Runtime Workbench, but when i see in the seeburger adapter monitoring for the MDN's i noticed that the message was in Error MIC not verified # MIC values not verified sha1-null. At first i thought the error was related to certificate, but when the message was retried after some time it was sucessfully processed and we got positive MDN's also. Could you please let me know when exactly the Error comes? and what can be done to solve this issue.
Many Thanks.
Edited by: Ravi Kumar Nakerikanti on Aug 13, 2008 4:51 AM

Hi,
You have used the AS2 Message type MDN (Message Disposition Notification).
An MDN may optionally be signed, in which case the recipient can authenticate the sender of the MDN and check its integrity. A valid, signed MDN together with a valid MIC reported by the MDN can be used by the sender of the payload message
But here this validation is failed ...and have raised the error like
"MIC not verified # MIC algorithms not verified [LOC: com.seeburger.as2.component.MDNHandler.parseMDN]"
refer
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_AS2_Spoke_Unit_for_Trading_Partner_Integration.pdf
Thanks
Swarup

Integration of Seeburger Adapter in Solution Manager for Monitoring

Hi Experts ,
Can we Integrate the monitoring of Seeburger adapter into the Solution Manager dashboard under central PI Monitoring ?
We are using AS2, FTP and sSFTP seeburger adapters here.
Regards,
Kamal
Edited by: KAMAL KUMAR on Jan 11, 2012 2:33 PM

Hi,
check [this.|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/408e1501-fb8c-2e10-edba-f51f13cde64e?QuickLink=index&overridelayout=true]
Page 29 has useful information on adapter/channel monitoring.
-santosh.

Error in Seeburger Message Monitoring

Hi ,
I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file.
I m getting error in seeburger message monitoring with status as "Could not send ansynchrone MDN to partner - url not set!". can anybody tell me whats the reason behind it,where it went wrong.

Really didn't understand your scenario. That sentence makes no sense:
"I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file."
But what I understand from the error message you have provided...................
if you are using Seeburger AS2 adapter as Receiver Comm Channel..........then there is definitely some cofig error is settings for MDN acknowledgement.
Under Parameters Tab:
You must have set the following parameter
MDN Mode = "ASYNC"
And has not provided the following parameter just below it :
Receipt Delivery Address
This parameter should have value: the URL of your own AS2
server where the asynchronous MDNs are
to be delivered.
Hope this solves your problem.
Regards,
Suddha

Seeburger Adapter

Hi all,
I have installed a generic seeburger FTP adapter, but I dont have any VAN connectivity at present. Can I convert the EDI ANSI X12 format to xml with this installation or it requires VAN connectivity to do this.
In this case do we require the BIC mapper? if so how to work with BIC mapper?
In the communication channel, I am able to see the installed Seeburger FTP adapter but it does not show the transport and message protocol. Is this related to the Installation/setup of VAN connection.
Regards,
Nithiyanandam

Hello..
SeeBurger is a leading provider of global business integration solutions.
Market launch of the most successful EDI solution for the automotive industry in 1986.
the company today serves more than 7,000 customers in 42 countries and more than 15 industries through its flagship B2B Gateway and related products and services.
First company worldwide to receive certification for SAP R/3
Building a closer partnership with SAP.
Extended any-to-any-conversion.
The SEEBURGER Business Integration Converter (BIC) is an Any-To-Any Format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex,high performance XML-to-XML mappings or to interface to existing JDBC Data Sources.
Supported EDI formats include: ANSI, EDIFACT, INHOUSE, IDOC, XML Schema, XML DTD, CSV,Delimited Data, positional data, SWIFT, EANCOM and many more.
Mapping Designer, a graphical tool, easily defines data format conversions via drag and drop functionality, enabling easy integration between source and destination files. A central mapping reposiu00ADtory enables comprehensive support of versioning and deployment support, such as self-testing and auditing.
The SAP Exchange Infrastructure message format is based on XML, but it also can work with non-XML data using attachments. In some cases it may be necessary to convert the main XML document in a message, into a non-XML document. The use of BIC is very common in Business-to-Business scenarios where EDI standards are in use.
The Business Integration Converter (BIC) of Seeburger is based on Java JIT Technology and can be used for small real-time messages, as well as very large master data (i.e.Catalogs) batches.
BIC can convert outbound invoices from XML format (used in SAP XI) to an EDIFACT invoice. The conversion can be executed before the message is transmitted to the business partner. The other way around, once an EDIFACT message has been received from the business partner, it must first be converted to XML format, which is the format SAP XI supports.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. BIC will allow you to do the following
Once you install BIC, you need to do Import the Generator Mappings into the Project Explorer of BIC MappingDesigner.
You can find Generator Mappings as a ZIP file in the following location <BICMappingDesignerInstallationDirectory>\user\bicmd\Exchange and select the file prj_GeneratorMappings.zip.bicmd.
In MappingDesigner select File Import Generator Mappings Zip File prj_GeneratorMappings.zip.bicmd Clik on Add and OK.
Once Import is done you can see Generator Mappings in BIC Mapping Designer.
The SEEBURGER Adapter runs on the SAP WEB AS (J2EE Engine)
The SEEBURGER Adapter is integrated into the SAP Exchange Infrastructure over JCA (Java Connector Architecture)
Consequence :
Supply of the complete SEEBURGER EDI/B-to-B-Technology-Suite within SAP NetWeaver
Central File of Business Content (mappings, integration processes) in the Integration Repository of SAP XI
Central configuration and design by using the Tools of XI in the configuration
Central monitoring and alerting over SAP XI
Seeburger Solutions Overview
BIC Mapping Module
Functional Acknowledgement Solution
Operational Dashboard / Archiving
Invoice Solutions
Communication
The Business Integration Converter (BIC) from SEEBURGER is a converter for the implementation of data formats.
Following formats are available:
ANSI X.12 (American National Standards Institute)
CSV (Comma Separated Variable formats)
EDIFACT (all subsets)
INHOUSE (VDA, flatfiles, e. g. SAP IDoc)
SWIFT (banks)
TRADACOM (Trading Data Communications Standard)
XML (DTDs and SCHEMATA)
Able to classify messages into the following message types:
XML
EDIFACT
Ansi X 12
Tradacom
VDA
IDOC
Swift
Inhouse
XML Ansi X 12
XML EDIFACT
XML Tradacom
XML VDA
XML IDOC
Go through this links..
Some more..
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Reward Points if it is really useful to you.....
Thanks,
Satya Kumar..

Issue in receiver SFTP seeburger adapter

Dear all,
We have a proxy to sFTP scenario.
The target message is being delivered to a sFTP system using a receiver sFTP Seeburger adapter.
I have this error being shown in the receiver channel.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: >> Description: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>> Details: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMPONENT_ERROR>>Retryable: true>>Fatal: true, >> Description: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>> Details: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMPONENT_ERROR>>Retryable: true>>Fatal: true.
The Seeburger WorkBench monitoring has a 2 error entries which says
1. PUT command for file <TEMP_20110406_115127.TXT> is in progress.
2. "Error on send, will be retried"
Finally, the .txt file is partially written in the receiver system.
If anyone has any inputs/pointers to resolve this issue. Pls share the details.
regards,
Jack.

Hi Jack,
We are also facing the same problem with the seeburger SFTP adapter. If you find the solution , Plz let us know.
Thanks,
Soumya.

SFTP Seeburger adapter - Could not find channel for report handling between

Hello Friends ,
We have R3 -> PI-> SFTP scenario . The messages are transferred successfully and the file is successfully received at the receiving end . But when we do communication channel monitoring , we see errors in Receiver CC . The Reciever CC contains SFTP adapter (Seeburger) . Recently the Seeburger adapter is upgraded and the below error has started occuring then onwards .
Error Message which we see in CC monitoring for Receiver CC (SFTP) is as below .
Initiation of Transmission Report( job id: da405030-30c6-11df-8b6e-797b8921162c milestone: 290) failed! Exception occured: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) - com.seeburger.xi.connector.fw.ConfigurationException: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) [3/16/10 8:40 AM]
Could experts help me ...
Thanks for your time .
Regards,
Laxman Nayak .

Hi,
I also have the error you mentioned but we're implementing the Seeburger SFTP adapter for the first time.
I've requested transport acknowledgements in my ABAP proxy and have checked the 'Deliver transmission report' flag in the adapter but I don't know what else I must do.
Any help would be greatly appreciated.
Thanks,
Alan

Issue with AS2 Adapter monitoring

Hi All,
I am using Seeburger AS2 Adapter in our XI project we are able to post and retrieve
messages through AS2 communication,but we are facing the problem of monitoring the messages if any incoming messages failed in the AS2 adapter only due to some network failure or some other issue we are not able to track which message is failed and what payload it contains as in Adapter Monitoring or communication channel monitoring AS2 Adapter shows the only "Failed Session"
Do we have any application to monitor it in XI.
Regards
Gaurav

Hi Gaurav,
Have you tried Tcode SXMB_MONI . In this by giving some details about your scenario, it will give you the information about all the messages which are successful or not. Here you can see the payload af successful messages and error in failed message by clicking on the perticular message.
hope this will help.
regards
HONEY

Seeburger adapter configuration

At my client place they want to send an orders idoc as an EDI document to customer,,Can any one please tell me how to configure seeburger adapter & the mapping for edi.
Advanced Thanks
Kum

Hi sati,
First you need to instal Seeburger BIC and then you should generate the XSD structure of the all yor documents.In Sebbburger BIC mapping designer is generate thes type of all the mappings1)E2X----EDI to XML and X2E ---XML to EDI etc.Seeburger BIC mapping desigener can take care all the tranformatiom of EDI to XML and XML to EDI.once instalitation is finshed, then you can chek with BIC mapping desginer .
Seeburger adapter is the B2B EDI Adapter.Seeburger adapter is also many types adapters:
1)BIC Adapter
2)Split997 adapter
3)AS2 adapter.Based on your usage you have to configure thes adapter.for example
AS2 sender adapte configuration:
1)AS2
2)Asynchor MDN Setting:
a)SSL Certificates and Clint certifactes.
b)SSL host name:HTTP Timeout,MDN Retry interval and MDN Retry count
c)use proxy
AS2 Receiver adapter:
a)HTTP:server ,port ,url and http time out
b)proxy:
c)AS2:Compress,Sign.Encrypt,Sign MDN use proxy and Xi Message
Seeburger Adapter have more funcations:it is very good to Moniter Message.
1)Archiving
2)Message monitor
3)message Spliter
4)Mapping Variable
5)Resource manger
If you nedd any more information regarding the Seeburger ,send your maild then i will send the some more docs to you.
Regards,
Ramesh

Resend Message from Seeburger message monitoring

Hi friends,
I want to know that is there any possiblity of resending the message from Seeburger message monitoring tool.
One of the messages failed due to a problem in sender ID.
I want to resend this message. is it possible ?
Note: Message send out successfully from communcation channel to AS2 adapter.
Thanks
Sunil.

Hi Sunil,
Please let me know what error you can see in Seeburger Workbench.
In My view you can see the below type of error with State u201CError on send, will be retriedu201D
If Any Message failed in AS2 Adapter may be due to any reason
1. Wrong Sender/ Receiver ID
2. Wrong URL
3. Firewall rules are not in place
4. Partner Production site is down and you are unable to connect to him
Messages with above errors will appear with Success Flag in SXMB_MONI. But they will be caught by Seeburger Adapter and will be in the Error Status in SEEBURGER WORK BENCH
The only way to find/restart those messages is go to Runtime Work Bench Messages Monitoring --> Messages form Component (Adapter Engine) ---> System Error Status.
Any Message which failed in Seeburger Level can be seen only in Runtime Workbench.
Regards,
Rama.

Link to Communication Channel and Adapter Monitoring not opening

Hello All,
we are on PI 7.0. In teh RWB, we are not able to see the Communication Channnel Monitoring as well the Adapter Monitoring It is giving Page cannot be Displayed.
please tell us the way ahead.
Regards
Chakra and Somnath

Hi Somnath,
when the error occurs check the url of the page that cannot be displayed and verify if the hostname is correct.
It could be a problem of not right setting in exchange profile.
Also verify that you have enough authorization, trying to logon with PISUPER user if you can.
Hope it helps,
Regards,
Sergio

Error while opening Adapter Monitoring in Runtime Workbench

Hi,
I am unable to open Adapter Monitoring from
Runtime Workbench -> Component Monitoring -> Adapter Monitoring
When I tried to open, I am getting following message in the new window:
"The page cannot be displayed"
Please let me know where I can enable this option.
Thanks,
Yogi.

Hi,
Go thru this SAP Note- 768456,928862
Also this doc may help u-https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
Regards,
Moorthy

Error in File Adapter Monitoring

Hi,
I have created a Sender Communication Channel to pick the file:
The following error message is being displayed in Adapter Monitoring:
Sender Adapter v2622 for Party '', Service 'BS_TRD_PILOT_YOGS':
Configured at 2006-12-19 05:52:17 UTC
History:
- 2006-12-19 05:56:01 UTC: Retry interval started. Length: 60.000 s
- 2006-12-19 05:56:01 UTC: Error: Conversion of complete file content of 'OB10_input.xml' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 14: missing structure(s) before type 'E1EDK14'
- 2006-12-19 05:56:00 UTC: Processing started
- 2006-12-19 05:55:01 UTC: Error: Conversion of complete file content of 'OB10_input.xml' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 14: missing structure(s) before type 'E1EDK14'
- 2006-12-19 05:55:00 UTC: Processing started
Please anybody do the needful.
Thanks,
Yogi.

Hi Yogi,
Just go thru your source structure once again.Such type of errors usally come when your source structure is not proper adn also when the parameters for comm'n channel are not mentioned properly.
Usually the Content Conversion Parameters(recordset structure and recordset sequence fileds).
regards
Madhu

Mail Adapter Error occured in Adapter Monitoring....

Hi
I have done the Mail>XI>File senario.... the xi server is sometimes its picking up the mails but some times its not picking... i have give trasport protocol as IMAP4 and url as pop://ipaddress.... I have created the asyncronus message types...n i have given the quality service as Exactly Once... when ever the server is picking file from mail inbox its sending file to the destination directory successfully but in destination side i am getting only the complex tags like the following
<?xml version="1.0" encoding="UTF-8"?>
<ns0:File_Message_Type xmlns:ns0="http://mailtofiledemo.com/ravi"></ns0:File_Message_Type>
i am not getting any nodes inside those tags.... In adapter monitoring i am getting the following error:
error occured: [2006-06-05T05:44:06Z] 0 new messages found; no action takenexception caught during processing mail message; com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
I am using SquirrelMail(webmail) server... so please help me...
I have tried with pop3 alos but its not working
Thanks & Regards
Ravi Shankar B
Message was edited by: RaviShankar B

Hi,
Try giving POP3.
and correct address.. pop3://etc... Remember to give the name of the folder from where the message have to be picked.
Regards
Suraj
Message was edited by: S.R.Suraj

Error in Mail Adapter Monitor......

Hi....
I have done the mail adapter and i got following error in Adapter Monitor(Mail Adapter)
error occured: [2006-05-31T05:53:34Z] 0 new messages found; no action takenexception caught during processing mail message; com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
how to recover this....
I am using pop3 mail server
Thanks & regards
Ravi Shankar B

hi,
check if you don't have quality of service Best Effort - BE in your mail sender channel
if so change it to EO - Exactly Once
and activate and your channel once more
this setting will eliminate:
NO_RECEIVER_CASE_BE error
change this setting and let me know if it worked
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Seeburger adapter monitoring

Similar Messages

Maybe you are looking for