Adapter Module not working in Sender Communication Channel working in recie

Hi
I have written one adapter module. IF i give that Adapter Module in Sender Communication channel its not working. If i give that in Reciever Communication Channel its working. If i mention in both the channels then its working in sender communication channel also.But in only sender communication channel its not working in only reciever communication channel its working Can any one tell me why its happening
Thanks & Regards
Ravi Shankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B

hi
if its problem with my code why its working if i give the adapter module in both the communication channels?If i give in only sender communication channel the module is not invoking. its not showing any auditlogs.Can any one please help me
OUTBOUND is for sender
INBOUND is for reciever right.?
the following code i have written
public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          String SIGNATURE =
               "process(ModuleContext moduleContext, ModuleData inputModuleData)";
          Object obj = null;
          Message msg = null;
          String filename = null;
          AuditMessageKey amk = null;
          try {
               obj = inputModuleData.getPrincipalData();
               msg = (Message) obj;
               System.out.println("&&&&&&&&&&&&&&&&&" + msg);
               if (msg.getMessageDirection().equals(MessageDirection.OUTBOUND)){
                    amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.OUTBOUND);
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> etHostName: Module called"+ i++);
               }else{
                    File filename1 = new File("
10.7.1.43
XI
source","text.txt");
                    filename1.createNewFile();
                    amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> etHostName: Module called"+ i++);
               System.out.println("**************" + amk + "***********");
          } catch (Exception e) {
               Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> GetHostName: Error Module called");
               e.printStackTrace(System.err);
               ModuleException me = new ModuleException(e);
               throw me;
          // Read the channel ID, channel and the module configuration
          try {
               Hashtable mp = (Hashtable)inputModuleData.getSupplementalData("module.parameters");
               if(mp != null){
                    filename = (String)mp.get("FileName");
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,"Host >>>  Element Name is set to {0}"+filename );
               }else{               
                    Audit.addAuditLogEntry(amk,AuditLogStatus.WARNING,"HostElementName parameter is not set. Default used: HostName.");
                    filename = "FileName";
          } catch (Exception e) {
               e.printStackTrace(System.err);
               Audit.addAuditLogEntry(amk,AuditLogStatus.ERROR,"Cannot read the module context and configuration data");
               ModuleException me = new ModuleException(e);
               throw me;
          try {
               XMLPayload xmlpayload = msg.getDocument();
               DocumentBuilderFactory factory;
               factory = DocumentBuilderFactory.newInstance();
               DocumentBuilder builder = factory.newDocumentBuilder();
               Document document =
                    builder.parse((InputStream) xmlpayload.getInputStream());
               Element rootNode = document.getDocumentElement();
               if (rootNode != null) {
                    Element childElement = document.createElement("filename");
                    childElement.appendChild(document.createTextNode(filename));
                    rootNode.appendChild(childElement);
               // Transforming the DOM object to Stream object.
               TransformerFactory tfactory = TransformerFactory.newInstance();
               Transformer transformer = tfactory.newTransformer();
               Source src = new DOMSource(document);
               ByteArrayOutputStream myBytes = new ByteArrayOutputStream();
               Result dest = new StreamResult(myBytes);
               transformer.transform(src, dest);
               byte[] docContent = myBytes.toByteArray();
               if (docContent != null) {
                    xmlpayload.setContent(docContent);
                    inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               e.printStackTrace(System.err);
               Audit.addAuditLogEntry(amk,AuditLogStatus.ERROR,"Cannot read the module context and configuration data");
               ModuleException me = new ModuleException(e);
               throw me;
          return inputModuleData;
Best Regards
Ravi Shankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B

Similar Messages

  • File sender Communication Channel is not working

    Hi friends
    we  Created File sender Communication Channel and Activated but It is not picking up file
    1.  0 messages in Message Monitoring
    2. My Communication Channel not appearing in Communication Channel Monitoring also
    3. We have refreshed the cache and activated the channel.
    we chack with File name, Directory name and  path ....
    Friends have any idea
    Regards
       Viswanadh Vadde

    Perosnally, I would recommend setting a trace and letting the system telling you exactly why.
    Traces are used to analyze runtime errors.  By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments at class and method level.  This is done with the help of the log configurator service:
    Log onto the Java Admin Console
         Services
         Log Configurator
         Locations
         Choose the location (Java package) and the tracing level (severity)
    (for example, com.sap.aii.adapter.file)
         Root Location > com > sap > aii > File
         Set the severity and choose Copy Severity to Subtree

  • BIC Module Error in Sender Communication channel for EDI to File scenario.

    Hi Experts,
    We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
    Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
    Thanks & Regards,
    Abhishek

    Hi Abhishek,
    Is there any special character present in the EDI file?
    the parser is not able to parse the data.
    you can check the BIC conversion log for more information.
    Regards,
    Harish

  • Files not getting picked up using Sender Communication Channel frm MDM sy

    Hi Experts,
    XI sender communication channel is configured to pick up any files coming from MDM system from the following path
    /XXX/XXX/mdm/mds/XXX/XXX/Material_Master/Outbound/P33/P33_R3_PORT/Ready
    Earlier we had the scenario working properly that created idocs in R3 system.(MDM>XI>R3)
    Currently i tried to test the scenario again but i don't see an entry in the sxmb_moni or tried checking whether the sender communication channel is working properly it showed polling correctly in RWB.The files are already sitting in the the above path.XI should be picking it up but don't know what the problem is?
    I also tried a test in RWB>Integration Engine>Test Message  put the payload and it was able to create idocs in R3.So i concluded there is an error in picking up message from MDM.
    Is there any log available for the commmunication channel where i can see error info of whether any files picked up or not.
    Please suggest me what all can be done to to ensure the CC is picking up the files.
    Earlier responses highly appreciated.
    B'Rgds,
    Sudhansu

    Hi,
    In addition to the RWB channel check suggested by Aamir, you should also check if the channel is
    1) Active in ID
    2) Channel is not locked in VA, if it is locked then your status in RWB will show processing started but the files wont be picked up...for more details check the unlocking procedure mentioned in this thread:
    JDBC Sender Adapter -  NOT FETCHING RECORDS -PROCESSING STARTED
    The unlocking procedure is the same for FILE and JDBC....
    Regards,
    Abhishek.

  • File sender communication channel stop working

    Hi Guru,
    I have a file sender communication channel. It usually works good. But sometimes it just stop working. And In RWB, it shows no error. If I stop it and restart it in RWB, it immediately works again. This happens once a while. Any ideas?
    Thanks,
    Meiying

    Hi,
    option 1--
    Do some dummy changes and activate channel and try and perform cache refresh.
    If still not working then  stop and restart SFTP service,if still no luck then restart JAVA stack
    option 2
    try to put timeout value in the channel.
    Regards.
    Mastan

  • PI sender communication channel not reading files from NFS directory

    Hello,
    I have a sender communication channel configured to read file from NFS directory which is on ECC server. A program in ECC generates the file and puts it on the ECC server in the output directory. PI sender communication channel is supposed to pickup this file and process it. If I give the NFS path as the source directory, I am getting error: Configured source directory '//Server/DIR/OUT' does not exist. I tried putting '
    Server\DIR\OUT' too but same error. Do I have to add the NFS path of ECC into PI as logical path?
    Any suggestions?
    Thanks,
    Sangita

    Hello Sangita,
    Your ECC server is an external system, therefore you need to activate FTP service in that system and use the transport protocol FTP:
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    You can use NFS protocol when you have a local directory in XI server.
    Best Regards,
    .Luis Bernal.

  • Why is a sender communication channel not required for IDOC and PROXY ?

    Hello,
    In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
    Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..)  when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
    Though this might be a regular question, I am not able to find a proper reason.
    Please let me know the reason for the above request.
    Thanks & Regards.

    You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
    But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
    Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
    Regards,
    Raj

  • JMS Sender Communication  Channel problem

    Hi XI gurus!!
    I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
    In defaultTrace.XX.trc I see the following information and errors:
    #1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
    #1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
    {GenericConnectionProfileImpl
    {Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
    JmsMessageSelector=,
    ConnectionFactoryConstructor=null,
    ConnectionFactoryFactoryInvocation=null,
    ConnectionFactoryInvocations=[],
    DestinationConstructor=
    {ConstructorInvocation
    {className=null,
    invokeParams=[]
    DestinationInvocations=[],
    MessageInvocations=[],
    DestinationName=null,
    User=,
    Password=,
    isJmsSessionTransacted=true,
    InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
    LookupConnectionFactory=QueueConnectionFactory,
    LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
    SerializedConnectionFactoryPath=null,
    SerializedDestinationPath=null,
    Flags=0000000000000000000000000000000000000000000000000000100000000010
    #1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
    #1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    #1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
    Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
    BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
    Thanks

    HI,
    As per the trace details given please consider few of the below options....
    What do u see in adapter monitoring tool for JMS adapter?
    http://hostname:5XX00/mdt/amtServlet
    Did you follow the document on correlation of JMS messages?
    In communication channel You have to set
    Correlation ID -> XI conversationID
    XI message ID->GUID
    XI Conversation ID -> JMS correlation ID.
    Now in the custom J2EE application you should set
    jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
    This thread deals with the issue..
    JMS Queue monitoring
    Check  if the JMS Sender adapter EOIO is with serialized messages 
    Thanks
    Swarup

  • JDBC Sender Communication Channel Problem

    Hello everybody,
    I have a sender communication channel, it is with green Functioning status in channel monitor in runtime workbench, and the log says "Process started" for every pool as configured, but it doesn't return any data to XI, and there's data to be taken, the problem started a few hours cause it was working fine, I've already executed a Complete refresh cache in SXI_CACHE, and changed the channel from Active to Inactive in ID, and Stopped and Started it again in RW, it doesn't give any errors, but it doesn't bring back any data that should be, any suggestions or maybe any information on how to refresh totally those channels????, thanks in advance.
    Regard's
    Paul

    Hi Paul
    Check for JDBC adapter locks. cpa cache locks are not relevant to your problem.
    Moreover check with the visual admin logs as well. if you can get info about the issue you have
    Thanks
    Gaurav

  • Inactive Sender Communication Channel still processing Files?

    We de-activated the Sender Communication Channel of an interface. However, the file adapter keeps processing?
       Anybody know what is going on?
                    Thank-You.

    Hi Tom,
    1)  Check out Whether you have De-activated the Right Adapter.
    2) Refresh the Cache,
    a)Start transaction SXI_CACHE.
    b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
    c)Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.
    If you still face issue try this .
    Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
    To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
    Regards
    Agasthuri Doss

  • XI-Multiple instance scenario -File & SQL sender communication channels

    Hi
       i have a basic question regarding how file sender communication channel ( where we poll for a particular file pattern either using file/ftp types in a particular subfolder ) or a sql sender communication channel - ( selecting records from a sql source ) would work in a scenario with two active XI instances and j2EE file and sql adapter services running on both of the J2EE servers ?
    1. How would the file polling from both J2EE servers - avoid a conflict looking for the same file pattern ? Is there any inbuilt mechanism from SAP to make multiple instances work with the file polling - without a confict ?
    2. Simlar question for SQL sender type communication channel ?
    If SAP does have a mechanism to handle multiple instance scenarios for file and sql sender adapter based communication channels, is there a link/document on this ?

    Hi Karthik,
    Please see my comments.
    I am just wondering aloud - what will happen if we use a select for update clause in the sql sender adapter communication channel -
    Gouri: Yes you can use select + update. In fact that is the right way.
    will this ensure that polling from one J2EE instance will lock the selected records so that the second instance does not select the same set of records from the sql server ? Or should we not use a select for update and use a simple select statement ?
    Gouri: Yes. SQL DB will ensure that same data will not be picked by another node. As I mentioned earlier use serilizable option from advanced mode.
    -Gouri

  • Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

    Hello All,
    One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
    Is the (IDoc) Communication Channel from Sending system to XI required to configured?
    Many thanks in advanced!
    Jochen

    Hi Jochen,
    for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
    Thanks,
    Rajeev Gupta

  • How can One sender communication channel pick two file from two location

    Hello
    I have a requirement that how can One sender communication channel pick two file from two location.Both the file has same name...How to configure the one receiver communication channel.i dont have any IR,no mapping..Please help me...

    >
    Soumitra Sinha wrote:
    > Hello Vijay
    > I already done the adapter specific message attribute.i am getting the file name properly.but that is nothing to do with my req.i am again clearing my problem:
    > i have two folder   folder a,folder b.Both has the same file credit0002. i have two destination folder i have one sender and one receiver channel.I dont have any IR.How one sender channel can  pick file from two location and how one receiver channel can put in two location.please help me..
    Ok now I get your requirement.
    you cant achieve this -  how one receiver channel can put in two location if you dont have a dynamic configuration defined i.e Adapter specific attributes.
    easy way - involve IR mapping
    else
    have a adapter module to define your dynamic configuration.
    Ref: /people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules & /people/michal.krawczyk2/blog/2006/10/09/xi-dynamic-configuration-in-adapter-modules--one-step-further
    Set the dynamic directory/file name etc for your receiver adapter.

  • Sender Communication Channel Error

    Hi all,
    iam working on JDBC scenario.For this iam using party and business service.
    iam getting following error at jdbc sender communication channel.
    Error occurred while sending message: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.
    Erlier it worked fine.But now iam getting this problem.
    We are having some other channels which r working fine.
    any ideas......?
    Thanks,
    Sreedhar Goud.

    1. If you know the user, who having admin rights;
    1.Open the VA tool; ex: C:\usr\sap\X67\JC01\j2ee\admin --> click on "go.bat"
    2. Click on "New" button ( this is on Logon Dialog box)
    3. Enter "Display name"; and select "Direct Connection To a Dispatcher Node".
    4. Say "Next"
    5. Enter "User Name","Host" and "Port" and Save the data.
    6. Select User and click on "Connect"
    2. Did you forget the J2EE_ADMIN password? Just follow below steps:
    Just follow below steps:
    1.Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat
    Ex: D:\usr\sap\F02\JC00\j2ee\configtool --> configtool.bat
    2. "Switch to configuration mode" for that Click on "Pencil" icon;
    3. Click on "Pencil" icon means "Swith to Configuration Edit mode" then say "YES"
    4. cluster_data --> server --> cfg --> services -->
    click on "Propertysheet com.sap.security.core.ume.service
    select properties:
    ume.superadmin.activated = True
    ume.superadmin.password = <enter password >
    then say "OK"
    Click on "Pencial ICON.
    5. Save & restart Java Engine.
    Login with "Administrator"
    1. http://<host>:<Port>/useradmin/index.jsp
    2. Enter userid / Password as "Administrator / <password>
    3. it will ask change password just change it.
    Please follow steps one by one. it should resolve your issue.

  • Sender communication channel for  HTTP and IDOC

    Why the sender communication channel is not necessary for HTTP and IDOC

    Hi,
    Because they lie on ABAP stack ie on Integration Engine...so that they can process directly but other adapter lies on Adapter engine.
    Regards
    Hemant

Maybe you are looking for

  • How to MODIFY A CUSTOM TABLE  FROM A FLAT FILE

    Dear Friends,                  I have a requirement where i have to upload data from excel file to my custom table  so i have used a FM 'TEXT_CONVERT_XLS_TO_SAP' and i have collected data into a internal table , till here i am able to get data correc

  • Some pages don't render properly after Java update for OSX 10.6.8

    I can't seem to get T-mobile.com's website pages to render properly anymore. So far, this is the only website I'm having this issue with, though there could be more I'm not aware of. I go to www.t-mobile.com and this is what I get: I think I might be

  • How to use beans in java application server 8.1?

    i created a bean to use in a jsp page. then i copied the jsp page to "domains/domain1/docroot " directory and the class file to the "domains/domain1/lib/classes" folder. But now i can only access the jsp page the bean is not included in it. how can i

  • Rendering in flv, size problem

    hi everyone, i am using the after effect cs5 version, and when chosing the flv rendering format, the rendered area of my composition changes. hence, when imported in flash, the working area around the imported item is not the same than the compositio

  • Always new mail, in mutt

    I am experiencing a strange problem with mutt and muttng: I tried all the versions (cvs, snapshots, packages in current and unstable, without any change). Some mail folders (I use traditional mboxes) are marked as including new mail also after I read