J2SE Local Adapter Engine

Hi,
We are using the local adapter engine to send and receive files from a FTP server. However, the outbound/receiver adapter is throwing this ugly Java/FTP exception:
Feb 28, 2006 1:02:58 PM  ...sap.aii.messaging.adapter.ftp.FTPCtrl [Thread-20] Info: ftp server returns reply '220 Service ready'
Feb 28, 2006 1:02:58 PM  ...sap.aii.messaging.adapter.ftp.FTPCtrl [Thread-20] Info: ftp server returns reply '230 User logged in'
Feb 28, 2006 1:02:58 PM  ...i.messaging.adapter.XMB2FileProcessor [Thread-20] Error: java.lang.Exception: ftp client test failed with 'com.sap.aii.messaging.adapter.ftp.FTPEx: User logged in'
As you can see the FTP server returns a nice 220 (Service ready for new user.) and 230 (User logged in, proceed.) response.
So how come the adapter throws an exception like this here? Can someone try to explain?
Tnx,
Roberto

Hi,
  Actually, your message is truncated so i can't view the complete message,
But i may suggest,
1. In the FTP server did you mention the read,write,append authorization to the userid you are refering in the sender file adapter? Typically i use guildftp as a ftp server and that has options for all these authorization.
2. Do you have any firewall or proxy installed locally,
3. Can you write the sender adapter settings and paste the error again as its truncated from the right side.
Regards,
Anirban.

Similar Messages

  • XI 3.0 -- Local Adapter Engine

    Hi all,
    I can sent the file of my local PC to the XI 3.0 by using the local adapter engine of XI 2.0.  But I can't do it by using the File Adapter Communication Channel in XI 3.0.
    In my XI 2.0 local adapter engine, I startup the RUN_ADAPTER.BAT in my local adapter engine folder. And create the file_inbound adapter: File_2_M47 as:
    <b>## file adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
    mode=FILE2XMB
    Integration Engine address and document settings (example, see docu)
    XMB.TargetURL=http://10.37.217.65:8000/sap/xi/engine?type=entry
    XMB.User=xiuser
    XMB.Password=xipass
    XMB.SenderBusinessSystem=FILE_SYSTEM
    XMB.SenderInterfaceNamespace=http://trevorecc5.com/xi/file
    XMB.SenderInterfaceName=ZMI_SO_IDOC
    XMB.ContentKind=B
    #XMB.ContentKind=T
    XMB.ContentType=application/xml
    #XMB.ContentType=text/xml
    #XMB.ContentType=text/plain
    XMB.QualityOfService=EO
    ##File Adapter specific parameters (example, see docu)
    file.sourceDir=C:/filetoidoc
    file.sourceFilename=.
    file.processingMode=setAttribute
    #file.processingMode=delete
    #file.processingMode=archive
    #file.archiveDir=c:/temp_archive
    file.pollInterval=20
    ##xml conversion properties if mode FILE2XMBWITHROWCONVERSION specified (example, see docu)
    #xml.fieldFixedLengths=15,25
    xml.processFieldNames=notAvailable
    xml.fieldSeparator=;</b>
    Note: The IP address (10.37.217.65 ) is my XI 3.0 server.
    I can send the file of my folder - C:/filetoidoc.
    I have configured the Comunication Channel in XI 3.0.
    And the related parameters like as:
    <b>Comunication Channel: CC_FILE_IDOC
    Service                : FILE_SYSTEM
    Adapter type           : File
                           : Sender
    Transport Protocol     : File System(NFS)
    Message   Protocol     : File
    Adapter   Engine       : Integration Server
    Source    Directory    : C:/filetoidoc
    File      Name         : .
    Quality   Service      : Exactly Once
    Poll      Interval     : 20
    Processing Mode        : Set to Read-Only
    Empty-File Handling    : Do Not Create Message
    Process   Sequence     : By Name
    File Type              : Binary
    Status                 : Active
    The sender comunication channel CC_FILE_IDOC has been assigned to the sender aggreement /File_System/ZMI_SO_IDOC/ of namespaces: http://trevorecc5.com/xi/file</b>
    But it can't work! 
    I don't know how to configure the file adapter Comunication Channel for my sending in XI 3.0.
    Any help is appreciated.
    Regards,
    Trevor
    Message was edited by:
            Trevor Zhang

    Hi,
    ><i>I think the XI 2.0 local adapter engine is more useful than the XI 3.0 comunication channel.</i>
    I ve never had the opportunity to work on XI 2.0 but the difference lies in the entire architecture of the Adapter Engine in XI 2.0 and XI 3.0
    While XI 2.0 had the adapter Engine as a J2SE  based engine, XI 3.0 is based on the J2EE framework and thereby allows more features including modules , and also supports different types of adapters and custom developed adapters as well.
    There is no real difficulty in configuring an adapter in XI 3.0 but ofcourse one should take in mind that the network level details should be beyong an XI developers job role.
    You need to look at the fact that the problem you are facing is not because XI 3.0 adapter has some problem, but rather because you seem to have network restrictions!!
    Regards,
    Bhavesh

  • Why my Local Adapter Engine not showed in SLD and Integration Directory?

    Hi guru,
    I have installed one Local Adatper Engine on Host B, then an XI is installed on Host A, but After I installed the local adapter engine and follow the standard configration step mentioned in this document:https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/307deae3-604e-2a10-feae-f016fb9cadd4.
    After the configuration is done, I restart the local adatper engine, but this local adapter engine is not showed in integration directory.
    what is the problem?

    The post-installation configuration steps are not complex, I exactly followed.
    what other reason could it be? have any guru configured local adapter engine before?

  • Decentralized Adapter Engine or Local Adapter Engine

    Hi Experts,
    I hv a doubt like what exactly we are achieving by installing a local Adapter engine?  Is this something to handle the firewall protocols? In one of the SAP material, it has been mentioned that aditional adapter engines may need to be installed "Close" (in a network sense) to the Business System? What does it mean?  What are the advantages over a centralized adapter engine?
    regards

    Vijaya Lakshmi,
    Every XI installation will install a default adapter engine and these are called as the Central / Local Adapter Engines. Most of the times this one Adapter Engine is more than sufficient.
    At times, when the load on your server is going to be high , you can install a Decentral Adapter Engines and these are nothing but seprate instances of your Adapter Engine that can pick data and send it to your Integration Engine.
    The need for a decentral Adapter Engine also arises when you have security restrictions, DMZ , etc in the landscape where one adapter engie is used for one particluar DMZ and another acts as the local adapter engine etc.
    Regards
    Bhavesh

  • Decentral Adapter engine or Local adapter engine requires separate databse?

    I'm installing De-central/Local adapter engine in my landscape. Does it requires a separate databse??
    My OS is AIX and Database is Oracle. Can someone give me the installation document for Decentral adapter engine.
    Thanks
    Sagar

    Thanks for the information.
    I've one more question, in de-central adapter engine post installation configuration.
    document says I need goto visual admin and do some settings, do I need start Visual admin in XI ?
    or De-central adapter engine will have its own Visual administrator and there only we need to do this post installation steps??
    -Sagar

  • Configuring a local adapter engine?

    Hi,
        I want to configure a local adapter engine and use it in my scenarios. Can anyone tell me how to go about it i.e. where can i find the installables for it, which files to download,service pack,etc. The XI server which i want to connect to has WAS 7.0 and ECC 6.00

    Hi Pragati,
    The local adapter engine is installed on any system that will run on WAS and while creating the Adapter in the Integration Directory select the adapter engine from your central or local adapter engine. 
    Regards.
    Praveen

  • System requirement for Local adapter engine installation

    Hi Guys,
    I have a requirement here where we are planning to install local plain J2SE adapter engine on various third party systems to pass the data from those systems to the PI system through http. Please can you let me know what are the requirements on the system to install local plain J2SE adapter on it in terms of memory, disc space, etc.
    thanks.

    Hmm.  100 MB disk space is required for the J2SE adapter engine installation.
    Memory depends on your scenario requirement. But in general a 1 GB RAM is sufficient.

  • Local Adapter Engine

    Hi All,
    Here we installed Local AE on both Sender and Receiver Systems but stuckup with configuring these Adapters.
    Step1:How to configure the SLD part if am working with Local AE's?
    Step2:How can XI recognize these Local AE's?
    Step3:In the Communication channels while defining the File Adapters,At the Adapter Engines option i have to choose Local AE instead of Integration Server.To get(display) this option (Local adapters) what all the connections are configurations need to be done at XI and Sender/Receiver?
    Any suggestions??
    Thanks,
    Kalyan.

    HI Kalyan,
    The Plain J2SE Adapter Engine is one of the PI messaging components responsible for message processing and protocol handling. This type of adapter engine was already available with XI 2.0 and merely requires a Java Virtual Machine to run. It can be used as a non-central adapter engine, but it hosts only a subset of the adapter functions and does not support standard security features such as security logs or integrated user management
    The Plain J2SE Adapter Engine does not access the exchange profile, because the connection data is kept locally. It does, however, register itself in the System Landscape Directory (SLD).
    for
    Technical Communication
    http://help.sap.com/saphelp_nw04s/helpdata/en/5e/f85141196ff423e10000000a155106/frameset.htm
    Adapters Running in the Plain J2SE Adapter Engine
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/a745d8823017b5e10000000a1553f6/frameset.htm
    <removed by moderator>
    regards
    kummari
    Edited by: Mike Pokraka on Jul 24, 2008 1:00 PM

  • Change decentral to local adapter engine

    How can I change the adapter engine from decentral to local?
    Thanks
    Mikie

    In any communication channel, u ll find an option called "Adapter Engine".
    There u ll see options like Integration Server, Ur decentral adapter engine name
    Regards,
    Prateek

  • Guide for J2EE Adapter Engine on WAS 6.40 with XI 3.0

    Hi all,
    we are currently struggling with our AE. We are going to migrate from Xi 2.0 to  XI 3.0, we run into problems while configuring our old J2SE AE (for which I have found a good PDF document on the SAP Service Marketplace).
    Now we would like to test/configure the J2EE AE on XI 3.0.
    But I cant find any guide for this on the SAP Service Marketplace. Does anyone know where to find this?
    Thanks
    Nesimi Buelbuel

    Hi Nesimi,
    There is a webinar replay of "Troubleshooting the J2EE Adapter Engine" at
    https://www.sdn.sap.com/sdn/webinar.sdn?res=/irj/servlet/prt/portal/prtroot/com.sap.sdn.wcm.compound.docs//library/uuid/47a9a361-0301-0010-d39a-dd40d34b2e9d
    Also make sure you check these links:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/configuring a local adapter engine.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/configuration guide - sap xi 3.0.pdf
    Regards,
    Sridhar

  • J2SE Plain Adapter - Continuous Operation

    Hi All,
    I would like to ask for your assistance in configuring the J2SE Plain Adapter Engine for continuous operation.
    This is the scenario:
    We currently have the db_receiver (jdb receiver) adapter up and running. The connection to the DB is ok and also the communication to XI is successful. However we would like now to have it permanently running as NT service to avoid running the run_adapter.bat and open the web browser, enter user and pass, etc, every time we need to use the adapter.
    Following the directions given by the Adapter.pdf document, under section u201CContinuous Operationu201D, the service SAPAdapterengine was successfully created, but now we have two doubts with regards to this:
    1-     The service mentioned above is not started right after the installation and every time we try to do it, the following message is displayed: The SAPAdapterengine service on Local computer started and stopped. Some services stop automatically if they have not work to do, for example, the Performance Logs and Alert service.
    2-     How the newly created service detects the configuration weu2019ve done for the db_receiver adapter in the very first time?
    Is there any extra step to link the service and the previous configuration made for db_receiver? Could you please give me or point me to some info source that explain the way the service works?
    Thanks in advance. Your help is highly appreciated.
    Kind regards

    Hi Diego,
    Have you had any luck in getting this to work. I am having the same issue, would really appriciate the help.
    Kind regards

  • How to register a file adapter in XI Server? [XI 3.0 / J2SE Plain Adapter]

    Hi,
    I am trying to register an outbound file adapter (J2SE Plain Adapter Engine) in the XI server to finally map the adapter to a communiction channel.
    What I tried is to activate the SLDaccessor service in the J2SE Plain Adapter Engine (as mentioned in Plain Adapter Docs -> Serive: SLDaccessor Service).
    After restarting the Adapter, the protocol in Plain Adapter Engine didn´t show any errors.
    Now my problem is where can I find in the "XI-Tools" (SLD, Configuration Builder, ABAP-based Server GUI) that the registration of the adapter did run properly?
    What I expected was that my file adapter would appear in the Integration Builder in my communication channel under the tab "Parameters" in the drop-down box "Adapter Engine". Unfortunately, it is not listed there.
    Furthermore, I do not exactly understand the benefit of registering the adapter in the SLD. What is the real advantage than establishing a connection between the adapter and the XI with the parameters XI.TargetURL etc.
    Regards,
    Kris

    Jason, thanks for your answer.
    Unfortunately, it is not running yet. The Adapter protocol states now:
    11:03:00 : No entry in SLD found for Bus.System 'WeissmannBuisSys1'
    The corresponding adapter configuration looks like:
    XI.SenderParty=
    XI.SenderService=WeissmannBuisSys1
    XI.Interface=OrderMI
    XI.InterfaceNamespace=http://www.foobar.de/sap/xi/test170604
    Can I at least assume that there has been a connection to the business SLD?
    If yes, I do have a Business System 'WeissmannBuisSys1' in SLD -> Business Landscape as well as in my Configuration Scenario under 'Business Systems'. Is this the right one to specify in the parameter XI.SenderService or will there be something else expected?
    Besides that, the corresponding documentation is somehow confusing to me:
    You can set the following arguments (except in mode FILE2XMBSTREAM) and use them to identify the adapter configuration during routing and mapping in the Integration Engine pipeline. You can also find an explanation about each argument there.
    - XI.SenderParty=<sender party name>
    - XI.SenderService=<sender service name>
    - XI.SenderInterfaceNamespace=<namespace URI>
    - XI.SenderInterface=<name>
    - XI.ReceiverParty=<receiver party name>
    - XI.ReceiverService=<receiver service name>
    You must set at least XI.SenderService and XI.Interface. The receiver is generally determined by routing in the Integration Engine. This specification is not mandatory.
    The XI.Interface mentioned in the last paragraph is not listed above in the parameters list. I assume XI.Interface == XI.SenderInterface.
    In the german documetation there is also another XI.InterfaceNamespace mentioned in the last paragraph which I assume is XI.SenderInterfaceNamespace.
    Regards,
    Kris

  • Unable to contact non-central adapter engine

    Hi All
    I install the local J2EE Adapter Engine, and configure the connection in exchange profile and set the SLD Data Supplier in Visual Admin
    and i could see my local adapter engine in adapter configuration.
    But in Runtime work bench ->component monitor->non-central adapter engine-> error:
    Ping Status:        status_image        HTTP request failed. Error code: "401". Error message: "Unauthorized [http://host:port/AdapterFramework/rtc]"
    how could i solve this?
    thanks in advance

    Hi , Lawrence
    There was a solution to this problem?
    Thanks
    Leôncio

  • How do you differentiate PCK and adapter engine

    how do you differentiate PCK and adapter engine?????

    HI Gabriel,
    the PCK is used,if you want to exchange Messages from or to XI. That means for that,you need on the sender or receiver Side a XI System. The one way is,that a XI sends the Native XML SOAP Messages via XI Adapter to the PCK.Then the message can be converted in some other formats,because the PCK has its own Adapter Engine. But there is no IDOC adapter.
    The second way ist,that for example you pick up XML Files with the PCK and transfer it to an XI system in the Native XML Format. With the PCK you can't do a File-to-File Transfer.
    The PCK is a standalone Application,which has its own Monitoring,Configuration and User Management.Instead of that, a decentral Adapter Engine is directly connected to an XI System and is configured centrally in the XI System
    PCK is a mini version of XI. It is used by smaller business partner (who cannot afford to install a full blown version XI) to exchange XI messages with large companies (having an XI installation).
    PCK has its own local Adapter engine.
    Check the following links:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3f9fc190-0201-0010-0cbd-87f50e404d91
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/34a1e590-0201-0010-2c82-9b6229cf4a41
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6f83d790-0201-0010-629d-ab5bf10c94e4
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
    http://help.sap.com/saphelp_glossary/en/6d/9c44b95c168e4cb500bb430ec193cc/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/99/115281baba404890d2561617a78409/content.htm
    /people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-1
    /people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-2
    Hope this helps.
    Cheers...
    Vasu
    <b>** REward Points if found useful **</b>

  • J2SE adapter engine and SSL testing

    Hi there,
    We are currently doing a B2B scenario whereby SAP XI sends a message to the J2SE adapter engine in the DMZ and then that sends the message via HTTPS / SSL to the receiving service....
    In order to test that the HTTPS / certificate etc worked I wrote a small Java application and dialled out of the network. I inserted the DER file into my CACERTS file on my local machine using the keytool as a "trusted certificate". The Java application worked 100% and did the SSL handshake fine and POSTED the data fine as well......
    Now I am no expert in the J2SE adapter engine but decided to try testing the same SSL connection using the J2SE adapter engine from my LOCAL machine with me dialled out onto the Internet.
    I logged into the J2SE adapter engine and imported the same DER file into the engine  (actually inserted into the "truststore.jks" file). I them went into the "Test Environment" of the J2SE adapter and have been trying to test.....
    I have a few questions:
    1. Do I have to use a P12 or PFX file for this sort of communication? Reason I ask is that with the Java application all I needed was the DER file?
    2. In the full blown scenario do I have to have SSL configured between XI and the J2SE adapter engine as well? Or can that stay as HTTP?
    My basic config for the test is roughly:
    WS.targetURL=https://someserver:4433/soap/someInbox
    WS.SOAPAction=CustomSoapAction
    SSLauthentication=true
    Do I really need the following two?
    SSLcertificate=somecert.p12
    SSLcertificatePassword=somepassword
    From my logic all I should need if the DER file loaded into the J2SE adapter which I have done......
    Has anyone done successfull SSL / HTTPS testing from the J2SE adapter engine using the "Test Environment"?
    Any advise would be greatly appreciated
    Kind regards
    Lynton

    Hi
    Not a answer to your question but why use the J2SE adapter engine in the DMZ and why not the J2EE Decentral Adapter Engine?
    Regards
    Bhavesh

Maybe you are looking for