Seeburger OFTP/ ISDN adapter

Hello,
Does anyone have an experience with configuring OFTP_ISDN adapter from Seeburger? I have a problem to configure an inbound channel (Sender) when the same dataset name can come from four different ISDN numbers (One MAIN ISDN MSN and three SUB ISDN MSN ). I can't use four channels because of conflict with the same dataset name and I don't know how to configure using one channel. Any help appreciated. Points rewarded. Pls urgent.
Regards,
Pavol Suba

Hi Pavol!
I don't have experience with this one, but only idea:
What about different dataset names? You will use the same structure, jsut with other names.
Or, what about creating 4 virtual sender services using the same structure?
You can also try to contact Seeburger company for a technical help. They're very friendly and helpful.
Peter
p.s. Ze zdravim v ceskom Nesse ak s tym fakt nemozes pohnut a chce sa ti, posli mi screenshoty CC do mailu (opytaj sa J dikana na moj mail). Robil som od Seeburgra AS2, tak mozno sa to bude podobat, mozno nie.. skusit mozme

Similar Messages

How to log inbound messages for Seeburger OFTP-Adapter

Hello,
we use the XI 3.0 SP9 with the Seeburger OFTP-Adapter to exchange EDI (ODETTE) Messages. At the moment we have the problem, that we don't see any inbound calls from our edi-partner in the logfiles of the oftp-Adapter. We can successfully connect to the ofpt-adapter by using telnet (as described in the documentation).
Do anybody know, how we can log the incoming calls?
Thanks!
Stefan

Hello Stefan,
the SEEBURGER Adapters are using the certified AdapterFramework Log Infrastructure. You can for example see the Logfiles with the J2EE Engine LogViewer.
First you have to make sure anything is logged: In the "Log Configurator" you find in the
|ROOT/Applications/Exchange Infrastructure/
category a child named
| .../AdapterFramework/ThirdPartyRoot/
under this subtree there is the
| .../SEEBURGER/
tree where you find the technical adapters (like OFTP). Define here an loglevel of INFO or DEBUG.
Then you can access the logs in the J2EE Administrator service "Log Viewer":
|Cluster/Server 0/usr\sap/
|..SID\DEVBMGS00\j2ee\cluster\server0\log
|....applications
|......com.seeburger.xi.oftp
|........oftp.log
You can also see this as a file on the system where the AF is installed (however it is better readable with the Log viewer):
/usr/sap/XIT/DVEBMGS00/j2ee/cluster/server0/og/applications/com.seeburger.xi.oftp
I have some screenshots which will make this more clear, please drop me an email so I can send them to you: [email protected]
Greetings
Bernd

SEEBURGER's VAN Adapter

Hi all,
Im wrking on an IDOC to EDIFACT format scenario. The reciever adapter is a SEEBURGER's VAN adapter.Can anyone pls help me with some documents on this?
Thanks in Advance.

HI,
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine as shown in the diagram below.
The FTP/VAN Adapter supports the following protocols:
IBMIE VAN, all report options.
GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
Sterling Commerce and Sterling IIB.
MCI EDI*Net.
The following FTP options are supported:
SSL, both IMPLICIT and AUTH_TLS support, server authentication.
All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
Active and Passive connection modes.
"KeepAlive" feature.
Binary, ASCII and custom transfer types.
Refer the below thresd which taks about the AS2 adapter configuration inroder to convert the EDI to XML message the similar configuration needs to be done in case of VAN/FTP adapter.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Seeburger adapters like FTP,OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
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.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
Seeburger provides the std mapping program which has to be deploy on to XI and we need to give it to module tab in adapter which does the conversion.
Here are the some of the std mapping program which is provided by seeburger.
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
We need to take the license from seeburger and we need to deploye the seeburger adapters then only we can see in adapter list on XI.
Thanks and Regards,
Chirag Gohil

Problems with Seeburger FTP Receiver adapter

Hello,
I am working on a scenario sending ORDERS05 Idocs to EDI vendors.
For this i have configured Seeburger Receiver FTP adapter with 2 modules to convert XML-EDI format. Since this is the test, I have pointed Seeburger to local FTP server with following settings
Hostname <Hostname of our FTP server>
Port <Port # of our FTP server>
Host Path/VAN partner id <some local directory of FTP server>
Payload mode: Maindocument.
At runtime i received following exception
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>> Details: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error in session: {type:FTPConnectionId}{binding:82ea8d3089dc3e898ae2e608d9d8487d}{channel:a52d1aaa8dd63ff59c2f590e78586a77}{toparty:TestEDIParty} CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionOpenConnectionError: Error while connection to remote host CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error while executing command QUOTE site system 1 CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true
Few questions related to this
1] can we use Seeburger adapter to generate EDI files on local FTP server
2] If not Seeburger can we use normal File adapter to do the same. I tried the same by configuring BIC module in File adapter so that it would convert XML to EDI format and was hoping file to be generated on FTP server. It generated one line XML file with following text "<info>Converted message locates in a attachment</info>". Any idea how to retreive attachments in File receiver adapter (as far as i know no attachments are supported in File receiver adapter).
Any idea how to generate EDI files with Seeburger FTP on test server?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
> 1] can we use Seeburger adapter to generate EDI files on local FTP server
Yes we can use.
> Any idea how to generate EDI files with Seeburger FTP on test server?
It is like a normal process, how to generate the EDI files in normal means without FTP. Check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
BIC
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
Regards
Ramesh

Dynamic filename creation with Seeburger's SFTP adapter

Hi Experts,
I read in one of the forum that Seeburger's SFTP adapter supports dynamic configuration.
My requirement is i need to dynamically create a file name and put it into a predefined folder(of a third party system) with SFTP adapter.
Can any one help me with some blogs/Materials on this?
Thanks,
Niranjan

HI,
Have you look into the blogs mentioned in below forum
How do we do File content conversion using SFTP SEEBURGER Adapter
Thanks
Swarup

SEEBURGER AS2: AS2 Adapter failure -- CryptoApiException: Access Denied.

Hi,
I am trying to send AS2 message to my partner by using Certificates and I am getting the following error at AS2 receiver adapter.Looks like it doesn't have User Credentials to access the certificates.But we provided all the details.We are not sure where it is going wrong.
2008-08-30 14:49:42 Error Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed:com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Access Denied., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Access Denied.
Can anyone please suggest us what is missing and where it is going wrong?
Regards
Stephano

Hi,
1) First of all create the Seeburger Certificates.
2) You have to deploy those certiates in your Visual Administrator.
After that in Interration Builder -
> Receiver Agreement -
> In Security Settings -
>
                   AS2 Sender Configuration -
> Signing Key -
>give the certificate name over there.
                   AS2 Sender Configuration -
> Encription Certificate & Authenitication Certificate is there
                   u have to give u r certificate names over there.
Thanks,
Satya Kumar

SEEBURGER AS2: AS2 Adapter failure - Cannot authenticate the user

Hello,
All was working fine but now I got these errors in an AS2 scenario. Sending a message via AS2. Also we don't receive any messages via AS2 anymore. This is the error when sending a message:
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure.
Please advice, many thanks!
Erik

Are you using the "Use Authentication" option in the communication channel? If yes, then ensure that the user provided is correct and is not locked. Also recheck the authentication certificate settings.
Regards,
Prateek

Seeburger X.400 adapter

Hi Experts,
I want material/links on seeburger X.400 adapter, I searched on SDN, but could not find any material for X.400 channel configuration.
In our landscape, client is thinking to install the X.400 adapter & so, I want to understand its configuration
Also, please let me know what is the Transport protocol supported by X.400 adapter?
-Supriya.

Hi Supriya,
Seeburger X.400 is actually a mailbox solution.actually X.400 /p7 is a protocol which the adapters uses for communication.
Any business partner sends or receives data through a mailbox and that has to be connected to PI thru X400 adapter. when trying to create a channel of type X400, the details of the VAN mailbox to poll or post the data need to be given.
x.400 is one of the communication mechanism/protocol used by SEEBURGER BIS.
regards,
Rohit

Seeburger - OFTP Adapter

Hi,
My Scenario is we have 7 different customers who will send orders and receive invoices through GXS mailbox. I have requested our trading partners to setup their trading partner relationships to the mailbox, which is in process.
I have built one common scenarion in IR and the configuration is yet to done in ID.
I have to use OFTP to poll the data from Mailbox and post them in R/3 as sales orders.
If i configure differnet(7) Oftp sender adapters and 1 receiver adapter, would this serve my purpose. I have gone through some documents (OFTP manuals), and as per them, wecan only poll data from mailbox using OFTP. how do we process data, do we need to configure one more receiver and one more file sender and IDOC receiver to post the data in ERP.
Please confirm as we gotto meet tight deadlines ;(
your help is highly appreciated.
Thanks,
Smith

Hi Madan,
There is a checkbox to enable alerts in the comm channel.
Refer to chapter 9 of the Seeburger Master Configuration Guide. It details how to set up the alerting.
Regards
Manish

Configuring a Seeburger FTP Receiver Adapter

Hello,
I am trying to build a scenario where SAP ECC 6 sends an invoice to a customer via EDI.
We are using ECC 6.0 and PI 7.0 and the Generic Seeburger EDI Adapters. The VAN is a GEIS EDISWITCH VAN (Eircom in Ireland).
I am able to successfully send an IDoc from ECC 6 and into PI where a Seeburger map converts the message to EDI-XML format. I can use a file adapter to create a file in normal EDI format. But I can't get the Seeburger FTP adapter to work with the VAN.
I have configured the correct IP, port, username and password but I keep getting the following message when the communication channel tries to send the message:
<h6>Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 501-Syntax errors in parameter. usage: %[recipient id]%[APRF] where either [recipient] or [APRF] can be omitted. (to change your current default SEND relationship). %% (places you in your 'HOME' TR). &['s'|'single'] ('get' command gets single file). &['m'|'multiple'] ('get' command gets multiple files). >> </h6>
The FTP session is expecting a PUT command with the recipient id and APRF as parameters but these are not getting passed. I suspect this is because I am not passing the correct variables to the receiver adapter but I don't know what variables it expects and where they should be specified. And I can't find the answers in the documentation.
Can anyone shed some light on what I need to do?
Thanks,
Ben

Hi Prateek,
Thanks for your comments. The channel is set to GEIS(GeMarkIII). There is nowhere to specify a directory or filename. The settings I have used are as follows:
Adapter Type: FTP (http://seeburger.com/xi)
Receiver
Transport Protocol: FTP
Message Protocol: GEIS/GeMarkIII
Adapter Engine: Integration Server
Host name: <IP address of VAN server>
port: 21
User Id: <Our mailbox number>
Password: <Correct password>
Host path/VAN Partner ID: <blank>
Script file: <blank>
Transfer type: ASCII
Connection mode: Passive
Use keep alive: <Not checked>
Security Mode: None
Proxy Mode: none
Resource ID: <blank>
Deliver transmission report: <not checked>
Payload mode: Attachment
Attachment ID: SeeburgerMain
Channel status: Active
Use dynamic attributes: <Checked>
Use non-empty attributes: <Checked>
Request displayed report: <Not checked>
Request dispatched report: <Not checked>
Report timeout (minutes): 720
Handle received reports: Refer reports to XI system
There is nowhere in the communication channel configuration that allows me to specify the receiver ID or the APRF. The documentation say this is read from the EDI data and the relevant fields are populated.
Any ideas?
Thanks,
Ben

Problem in SEEBURGE BIC mapping adapter

Hi experts
I am using SEEBURGER MAPPING adapter for file to idoc scenario .I have to convert an input flat file into xml using BIC mapping adapter.The problem is that when i am giving input file to convert into xml ,the conversion is failing with a error that a special character(?) occurs in the begining of file.when we r opening the file then we r not able to see any special character.The file is in UTF16 Little endian encoding. we r unable to find that how the spechial character is coming in the input files and how to debugg it.Plz guide me how to proceed.Is there any function in SEEBURGER to remove special character from the source file?
Regards
Neha

Hi Neha,
Seeburger is providing Modules (Configurable in CC module chain) described in SAPXI_SeeXIModules_en.pdf with additional functionality like Replace String,Start Local Up, Charset Conversion, zip and dynamic Configuration.
So if you have those modules installed you can use Replace String functionality to replace this string.
Regards
Naycho

Seeburger SFTP Sender Adapter Failure

Hello,
a SFTP sender channel causes the follow error when executing a poll cycle:
SFTP Adapter failure Details: while trying to invoke the method com.seeburger.uri.dt.sftp.schema.DtSFTPPollingResponse.setSuccessMessage(java.lang.String) of an object loaded from local variable 'e'
The server was pinged successfully so there should be no firewall issue. We are also able to logon to the server using a third-party SFTP client.
The error description is not very meaningful for tracking down the root cause.
Do you have any idea what could have caused this error?
Thank you.
Edited by: Guppenberger Florian on Jan 24, 2011 4:00 PM

For the Roll back error plz chk the below points.
1. Check the module parameters.
2. Make sure the sender agreement doesnt have any * 's.
Ex: The SA should not be like : | BS | SI_test_oa | * | *
SA should be like BS | SI_test_oa | |
3. If the input file has special chanracters , use the encoding .
If the above doesnt work, try to create a new communication channel and test it.
We also faced this error toomany times in the sender CC for sFTP advatco adapter.
Thanks,
Soumya.

How to test SEEBURGER EbXML Sender adapter

Dear All,
We are starting to implement ebMS adapter from SEEBURGER(as it is known adapter type as EbXM_HTTP). We will be using this as Sender adapter.
I am now analyzing the options to perform some basic tests(like unit testing with out the message being sent by real interface partner) with this adapter. I mean, I am thinking something like SOAPUI client tool which is one of the excellent tool for testing webserives, is there any EbXML client tool available or perhaps can we use SOAP UI tool to test the ebXML. If this is possible with SOAPUI, where to configure CPA details of the message and what will be end point?
Thanks in advance and any help would be highly appreciated.
Kind Regards,
Prasad.

Dear Both,
Thanks for your comments.
As for the PI/XI sending option, we basically should send test messages to ourselves as I understand it correctly.
In my investigation in found a client software called: M E C AS/2 under
http://www.mec-as2.org/
Does anybody have experience with this one?
Best Regards, Mathias.

Seeburger AS2 receiver adapter conf PI 7.1

Dear All,
I have seen a changed AS2 adapter on PI 7.1,the options are totally different than what we have in previous version of AS2 adapter.
I am looking for seeburger AS2 adapter documents and configuration steps for PI7.1 version.
Any inputs...
chirag
Edited by: Chirag Gohil on Sep 8, 2010 5:03 AM

AS2Receiver:
ModuleName: localejbs/ModuleProcessorExitBean
Type: Local Enterprise Bean
Module Key: Exit
-_Module Parameter_-
Module Key: Exit
Parameter Name: JNDIName
Parameter Value: deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
-_Parameters Tab_-
HTTP
Server - Computer with listening AS2 Server
Port - Port of the endpoint with listening AS2 Server
URL Path - Path to the endpoint with listening AS2 server
HTTP Timeout - Timeout in seconds for waiting for server's response
HTTP Keep Alive - If enabled, the HTTP session is re-used. This optimizes the performance.
Basic Authentication
User - User for basic authentication
Password - Password for basic authentication
Realm - Realm for basic authentication
Proxy
Proxy Server - Your proxy server
Proxy Port - The port of the proxy server
Proxy User - User for optional authentication
Proxy Password - Password for optional authentication
Proxy Protocol - Select either - HTTP 1.0 or -HTTP 1.1
AS2
Compress - Select this option if the payload is to be compressed
Sign - Select this if the payload is to be signed
Signing Algorithm - Select an algorithm which is applied for signing the payload; we recommend "SHA-12"
Encrypt - Select this, if the payload is to be encrypted
Encryption Algorithm - Select an algorithm that is used for encrypting the payload; we recommend "RC2/128" or "3DES"
MDN Mode - SYNC to request a synchronous MDN; ASYNC to request an asynchronous MDN; NONE if no MDN is required
Receipt Delivery Address - Enter the URL of the Asynchronous MDNs that are to be delivered (i.e. the URL of your own AS2 server)
MDN Timeout - Enter a time period (in min), after which an outstanding asynchronous MDN will be interpreted as an error. The value "0" means no timeout
Sign MDN - Select this option, if the MDN is to be signed
Message Subject - This text is sent to the server within the optional HTTP header "subject"
Content Type - The content type should be set. A random content type can be set, but we recommend one of the following
= "application/edifact" for EDIFACT files
= "application/edi-x12" for ANSI X.12 files
= "application/xml" for XML files
= "text/plain" for plain text files
= "application/octet-stream" for arbitrary binary files
Delivery transmission report - A special transmission report is delivered to the report channel

Seeburger sFTP receiver adapter error: Socket Write Error, EOF Received

Hello experts,
We have a sFTP to sFTP scenario for which we are getting below error every time the scenario is executed.
Error Messages are as follows:
Put File: Could not connect to remote host, Reason: Unexpected termination; software caused connection abort; socket write error[unknown cause].
Sometimes below error occurs :
Put File: Could not connect to remote host, Reason: EOF received from remote side [unknown cause].
Every time after restart of sFTP adapter on XI box, failed messages are sent successfully to receiver sFTP server.
There is no error for sender sFTP channel. This error occurs only for the receiver sFTP channel.
On receiver sFTP side, we are using Public key-private key authentication.
Can anyone please let me know what could be the cause of connection failure. ?
Thanks a lot in advance!
(I searched many threads on SDN but could not find anything relevant to this particular situation, so posting a separate question.)
Minal

Thanks Naveen for the reply..
I missed to mention that we are working on XI3.0 with SP19 and seeburger sFTP is 1.7.4
Looks like key exchange is working properly as after every restart of adapter all failed messages are processed successfully..
It is observed that if there is an idle time of 8-10 hours between last data transfer and current data transfer then this error occurs.
We have increased connection timeout and transmission timeout parameters also for sFTP properties in visual admin.
Thanks,
Minal
Edited by: Minal Vaidya on Oct 5, 2011 8:46 AM

Seeburger OFTP/ ISDN adapter

Similar Messages

Maybe you are looking for