PI 7.11 JMS adapter using JNDI weblogic server issue

Hi SAP experts,
I have a scenario to integrate to a application using JMS adapters. we use SAP PI 7.11 version.
We have deployed JMS drivers successfully and We face issue here to connect to weblogic server
We are using JMS adapter using JNDI to connect to weblogic server version 10.3.
Can anyone help with the exact format to be used in JMS properties table and additional parameters table in JMS communication channel. Your quick help will be appreciated.
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up destination: AccrualDetailsQueue for profile:  ConnectionProfile of channel: CC_SND_JMS on node: 3010950 having object id: 673696a9fe8c39fdab32213f0930afb3: javax.naming.NameNotFoundException: Unable to resolve 'AccrualDetailsQueue'. Resolved ''<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination(JndiConnectorImpl.java:168)<br

Hi Padmini,
Refer to the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
It was very helpful to me, for configuring the additional parameters in the communication Channel JMS.
I leave you some screenshots of the settings that I did.
I seize the opportunity to ask you, where do I can get the drivers (.Jar) for Weblogic?
Regards.
Rodrigo.

Similar Messages

  • JCA Resource adapter deployment in Weblogic server

    Hi,
    I have deployed a resource adapter successfully in Weblogic server and works fine.My resource adapter has weblogic-ra.xml and ra.xml available under meta-inf folder.I have provided some properties in weblogic-ra.xml and ra.xml but unable to see the same properties when i open the resource adapter settings page in the the weblogic administration console
    I want to change resource adapter properties from weblogic adminstration console but dont see the properties which i used during deployment.
    Can someone help with identifying the issue or if i have to do something different.
    Appreciate any help.
    Thanks
    S

    Not sure what might be causing this behavior. Property values in ra/weblogic-ra.xml should be displayed on the console (http://machine:port/console). I think I have experienced similar issue only to realize that console only displays 10 properties and other properties are displayed after pressing Next link on the page.
    How many proprieties you have? What are getting displayed and what properties are not getting displayed?
    Manoj

  • How to avoid JMS validation when starting weblogic server

    Hi All,
    When starting up WebLogic server, it will validate JMS destinations one by one for deployed applications.
    If I don't connect the VPN, then these JMS destinations are not reachable, and WebLogic Server will spend a lot of time to try connecting to these JMS destinations.
    Thus it will take a lot of time to startup the WebLogic Server.
    How can I disable JMS validation when starting weblogic server?
    Thanks and Regards!

    Hi Daniel,
    By blank do you mean that the screen is black? Is it gray? Is it blue? The word "blank" is vague when trying to determine and isolate startup issues.

  • Win7 64-bit Forms 11.1.2.0 and JDeveloper 11.1.1.6 use same weblogic server

    Trying to make JDev 11.1.1.6 and Forms 11.1.2.0 use same weblogic server on Win 7 64-bit.
    Installed JDeveloper 11.1.1.6 studio generic. This installs a 32-bit JDK and weblogic 10.3.5. (Oracle, Why doesnt forms installer install weblogic like JDev does?)
    Installed 64-bit JDK 1.6.0_24
    Configured JDeveloper 11.1.1.6 and Weblogic 10.3.5 for 64 bit and to use new 64-bit JDK. Works great.
    Started up Oracle forms and reports installer and see that it wants to use all the defaults paths of JDevelopers Weblogic server - nice.
    However, I dont see a way to tell the forms installer the new path of the 64-bit JDK. The forms installer sees the older unused JDeveloper 32-bit JVM and complains.
    Like I said.. trying to use same weblogic server and not install two weblogic servers.
    Any ideas?

    This problem is caused by a Bug
    Bug 12669780: SUBVERSION "CONNECTION" FAILING FOR PROTOCOL SVN+SSH IN JDEV 11.1.2.0.0
    A patch is expected to be delivered soon

  • BEA Workshop for WebLogic Platform9.2  can use with weblogic server 9.1?

    Wanted to know whether BEA Workshop for WebLogic Platform9.2 can be used with weblogic server 9.1?. If it cannot be used then which ide we need to use to build the j2ee application to deploy on to weblogic server 9.1

    try http://edelivery.oracle.com
    accept the licenses and in the next screens
    "Select a Product Pack" select Oracle BEA
    and your platform (i.e. Windows)
    then select the media pack you want
    i.e. "BEA WebLogic Media Pack for Linux x86"
    and voila!
    "WebLogic Platform 10.2 for Microsoft Windows (32-bit)"
    (in the Platform includes WebLogic Server, Workshop for WebLogic, WebLogic Portal and WebLogic Integration)
    ./ydes

  • Integrated weblogic server Issue with Host name mapped to multiple IPs

    I am running very simple ADF application from Jdev 11g (11.1.1.3.0).
    Compilation was successful but weblogic server facing problem while starting.
    It is showing HostAName is mapped with Multiple IP Addresses.
    Please provide solution to fix the issue....
    log is,
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1 -Doracle.server.config.dir=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.security.jps.config=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\Users\Raja\AppData\Roaming\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
    <Dec 23, 2010 11:49:42 AM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
    <Dec 23, 2010 11:49:44 AM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Dec 23, 2010 11:49:46 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 23, 2010 11:49:46 AM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Dec 23, 2010 11:49:46 AM EST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Dec 23, 2010 11:49:46 AM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00001. Log messages will continue to be logged in C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
    <Dec 23, 2010 11:49:46 AM EST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
    <Dec 23, 2010 11:49:57 AM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Dec 23, 2010 11:50:14 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Dec 23, 2010 11:50:14 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 23, 2010 11:50:28 AM EST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Dec 23, 2010 11:50:28 AM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00001. Log messages will continue to be logged in C:\Users\Raja\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
    <Dec 23, 2010 11:50:28 AM EST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Dec 23, 2010 11:50:31 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:114b:ab6a:23b1:b44c:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.10.103:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:c48:60a:9d0d:7cda:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:0:5efe:c0a8:a67:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:95ca:d058:6a51:53e8:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Warning> <Server> <BEA-002611> <Hostname "Raja-PC", maps to multiple IP addresses: 192.168.10.103, fe80:0:0:0:114b:ab6a:23b1:b44c%12, fe80:0:0:0:c48:60a:9d0d:7cda%13, 2001:0:4137:9e76:c48:60a:9d0d:7cda>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 2001:0:4137:9e76:c48:60a:9d0d:7cda:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Dec 23, 2010 11:50:32 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Logger><error> ServletContainerAdapter manager not initialized correctly.
    Edited by: user1158476 on Dec 23, 2010 3:05 PM

    Thanks for reply...
    If you look at the last line of log there is some error message:
    <Logger><error> ServletContainerAdapter manager not initialized correctly.
    after this no further logs and web page not open in Browser.

  • Jms adapter publish to weblogic

    hi,
    my jdeveloper is 11.1.1.5 and my weblogic server is 10.3.5. now i want to publish one message to weblogic application 10.3.2. there is no soa server. for this how can i develop?

    Hi Upender,
    I think you'll have to create a JNDI for JMS Adapter and point the connection factory to the WLS 10.3.2 as described below.
    http://docs.oracle.com/cd/E21764_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
    Regards,
    Neeraj Sehgal

  • Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

    Hello
    I am trying to send some msg from Http client
    I configured JMS adapter as receiver
    Transport Protocol :WEBsphereMQ JMS provider
    Message  protocol :JMS1.x
    I have given the Ip  address  of my machine where I installed WEB Sphere MQ
    Server Port :1416
    Transport Protocol :WebSphere MQ
    JMS compliant: JMS-compliant
    In SXMB_MONI
    Http client sends message without any error.
    But while tracing I got message
    <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
    Can anybody tell me the solution..
    Thnaks

    Hi,
      I have not directly faced this but i may suggest ,
    1. What do you see in sxmb_moni, do you have a queue problem?
    2. see this File-to-File Scenario Stopped Working  the reply from Shravan and the last message.
    <i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
    3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Regards,
    Anirban.

  • Problem Encountered in JMS adapter using SEEBURGER module

    While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
    <b>1. The error encountered is</b> :
    Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3';  detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
    <u>SEEBURGER BICXIADAPTER</u> --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: <u>XML file should begin with white spaces or <. (Found char :U(Hex :85</u>). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
    <b>2. The targer PAYMUL xml is as follows</b> :
    ( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
    <u>PAYMUL XML</u>
      <?xml version="1.0" encoding="UTF-8" ?>
    - <LIST>
    - <S_UNA>
      <D_DELIMITER>:+.? '</D_DELIMITER>
      </S_UNA>
    - <S_UNB>
    - <C_S001>
      <D_0001>UNOA</D_0001>
      <D_0002>2</D_0002>
      </C_S001>
    - <C_S002>
      <D_0004>SAPDM</D_0004>
      <D_0007>ZZ</D_0007>
      </C_S002>
    - <C_S003>
      <D_0010>000000000000</D_0010>
      <D_0007>55</D_0007>
      </C_S003>
    - <C_S004>
      <D_0017>070201</D_0017>
      <D_0019>1150</D_0019>
      </C_S004>
      <D_0020>01945678912345</D_0020>
    - <S_UNH>
      <D_0062>1</D_0062>
    - <C_S009>
      <D_0065>PAYMUL</D_0065>
      <D_0052>D</D_0052>
      <D_0054>96A</D_0054>
      <D_0051>UN</D_0051>
      <D_0057>FUN01G</D_0057>
      </C_S009>
    - <S_BGM>
    - <C_C002>
      <D_1001>452</D_1001>
      </C_C002>
      <D_1004>01945678912345</D_1004>
      <D_1225>9</D_1225>
      </S_BGM>
    - <S_DTM>
    - <C_C507>
      <D_2005>137</D_2005>
      <D_2380>20070201</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <G_SSG4>
    - <S_LIN>
      <D_1082>1</D_1082>
    - <S_DTM>
    - <C_C507>
      <D_2005>203</D_2005>
      <D_2380>20070201</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <S_RFF>
    - <C_C506>
      <D_1153>ACK</D_1153>
      <D_1154>01945678912345</D_1154>
      </C_C506>
      </S_RFF>
    - <S_RFF>
    - <C_C506>
      <D_1153>AEK</D_1153>
      <D_1154>01945678912345</D_1154>
      </C_C506>
      </S_RFF>
    - <S_BUS>
      <D_3279>IR</D_3279>
    - <C_C551>
      <D_4383>UGI</D_4383>
      </C_C551>
      </S_BUS>
    - <G_SSG5>
    - <S_MOA>
    - <C_C516>
      <D_5025>9</D_5025>
      <D_5004>5000</D_5004>
      <D_6345>EUR</D_6345>
      </C_C516>
      </S_MOA>
      </G_SSG5>
    - <G_SSG6>
    - <S_FII>
      <D_3035>OR</D_3035>
    - <C_C078>
      <D_3194>ES921998500000000012</D_3194>
      <D_6345>EUR</D_6345>
      </C_C078>
    - <C_C088>
      <D_3433>ABNAES17000</D_3433>
      <D_1131>25</D_1131>
      <D_3055>5</D_3055>
      </C_C088>
      <D_3207>ES</D_3207>
      </S_FII>
      </G_SSG6>
    - <G_SSG7>
    - <S_NAD>
      <D_3035>OY</D_3035>
    - <C_C080>
      <D_3036>XYZ CORPORATION LTD</D_3036>
      </C_C080>
    - <C_C059>
      <D_3042>XX</D_3042>
      </C_C059>
      <D_3164>XX</D_3164>
      <D_3207>ES</D_3207>
      </S_NAD>
      </G_SSG7>
    - <G_SSG11>
    - <S_SEQ>
    - <C_C286>
      <D_1050>1</D_1050>
      </C_C286>
    - <S_MOA>
    - <C_C516>
      <D_5025>9</D_5025>
      <D_5004>5000</D_5004>
      <D_6345>EUR</D_6345>
      </C_C516>
      </S_MOA>
    - <S_DTM>
    - <C_C507>
      <D_2005>227</D_2005>
      <D_2380>2007-02-01</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <S_RFF>
    - <C_C506>
      <D_1153>AIK</D_1153>
      <D_1154>01901234567890</D_1154>
      </C_C506>
      </S_RFF>
    - <S_RFF>
    - <C_C506>
      <D_1153>CR</D_1153>
      <D_1154>01901234567890</D_1154>
      </C_C506>
      </S_RFF>
    - <S_FCA>
      <D_4471>13</D_4471>
      </S_FCA>
    - <G_SSG12>
    - <S_FII>
      <D_3035>BF</D_3035>
    - <C_C078>
      <D_3194>AT921998500000000011</D_3194>
      <D_6345>EUR</D_6345>
      </C_C078>
    - <C_C088>
      <D_3433>ABNAAT14000</D_3433>
      <D_1131>25</D_1131>
      <D_3055>5</D_3055>
      </C_C088>
      <D_3207>ES</D_3207>
      </S_FII>
      </G_SSG12>
    - <G_SSG13>
    - <S_NAD>
      <D_3035>BE</D_3035>
    - <C_C080>
      <D_3036>ABC CORPORATION 1</D_3036>
      </C_C080>
    - <C_C059>
      <D_3042>XX</D_3042>
      </C_C059>
      <D_3164>XX</D_3164>
      <D_3207>ES</D_3207>
      </S_NAD>
      </G_SSG13>
    - <G_SSG16>
    - <S_PRC>
    - <C_C242>
      <D_7187>11</D_7187>
      </C_C242>
    - <S_FTX>
      <D_4451>PMD</D_4451>
    - <C_C108>
      <D_4440>SENDERPN1</D_4440>
      </C_C108>
      </S_FTX>
      </S_PRC>
      </G_SSG16>
      </S_SEQ>
      </G_SSG11>
      </S_LIN>
      </G_SSG4>
    - <S_CNT>
    - <C_C270>
      <D_6069>2</D_6069>
      <D_6066>1</D_6066>
      </C_C270>
      </S_CNT>
    - <S_UNT>
      <D_0074>1</D_0074>
      <D_0062>1</D_0062>
      </S_UNT>
      </S_UNH>
    - <S_UNZ>
      <D_0036>1</D_0036>
      <D_0020>01945678912345</D_0020>
      </S_UNZ>
      </S_UNB>
      </LIST>
    <b>3. The module parameters for Seeburger inputs :</b>
    ( In receiver communication channel)
    <b>Processing Sequence</b>
    localejbs/CallBicXIRaBean               Local Ent Bean     x2e_bic_paymul
    SAP XI JMS Adapter/ConvertMessageToBinary     Local Ent Bean     convert_XI2Bin
    SAP XI JMS Adapter/SendBinarytoXIJMSService     Local Ent Bean     
                    exit
    <b>Module Key</b>
    x2e_bic_paymul     destSourceMsg     MainDocument
    x2e_bic_paymul     destTargetMsg     MainDocument
    x2e_bic_paymul     logAttID          ConverterLog
    x2e_bic_paymul     mappingName     See_X2E_PAYMUL_UN_D96A
    x2e_bic_paymul     newLine          true
    x2e_bic_paymul     saveSourceMsg     XMLEDI

    Hi,
    Check Below links,
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    Regards,
    Phani

  • Configuration of JMS  adapter Using WebSphereMQ

    Hi All
    I am trying Http to JMS scenario.
    I configured my JMS adapter as receiver
    Trasport protocol: Web sphereMQ JMS provider.
    Queue Connection Factory : com.ibm.mq.jms.MQQueueConnectionFactory
    Queue Java class : com.ibm.mq.jms.MQQueue
    IP address : 172.17.50.150Where I installed Web Sphere MQ
    In SXMB_MONI my http client sends msg without any error
    But In runtime work bench whn  I observe Adapter monitoring I got error as
    Receiver channel. Details: MQJMS2005: failed to create MQQueueManager for '172.17.50.150:QM_APPEL'
    PLZ ell me d coz
    Thanks

    Hi,
    for the configuration of a Websphere MQ JMS adapter, you will have to also give details like, Queue Manager Name, channel name, etc.
    Just check this link for the same,
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
    Provide all the correect details and it will hopefully work.
    Regards,
    Bhavesh

  • JMS adapter and Websphere MQ availability issue

    Hi,
    My customer uses XI 3.0 and JMS adapter to communicate with WS MQ.
    They have several MQ Server instances in separate physical machines, for availability purpose. 
    the intention is, in case of MQ Server failover, the secondary MQ Server try to connect with the XI-JMS adapter.
    The question is:
    Is this mechanism possible in an automatic way or is it needed some manual process or configuration of JMS adapter?. Also, is there any alternative more recommendable from the SAP XI adapter point of view?
    Thanks in advance,

    Thanks Bhavesh and Satya,
    Very helpful your answers.
    I have another question related with XI and JMS adapter. The scenario is several MQ nodes in separate physical machines sending and receiving messages to/from the same XI-JMS adapter (centralized).
    Is this supported by XI-JMS adapter confguration? If not, does anybody knows an alternative way to implement it?
    Thanks again in advance,

  • FTPs adapter setup on Weblogic Server

    Hi,
    I am trying to setup ftps adapter for BPEL PM 10.1.2.0.2. running on Weblogic Server 8.1. BPEL does support Ftps for this version but it seems weblogic doesnot support ftps. Will this mean that I cannot set it up on WLS.
    I have tired to make changes in weblogic-ra.xml file and included all the params required for ftps adapter setup but I always get an error - connot login, please check username and password.
    Please help me on this and suggest if any other alternatives are possible.
    Regards
    Arvind

    Hi,
    Any help on this ??
    Regards
    Arvind Aggarwal

  • What is the Use of Weblogic server in Jdeveloper

    Hi,
    I am using Jdeveloper 11.1.1.4
    I need the information about WTC, DataSource and Weblogic server.
    So anybody know the documentation link plz reply me,
    Regards,
    Ragu.

    Hi
    look into this ADF BC: named datasource in application module post

  • Which version of Workshop to use with WebLogic Server 10.0 for 64-bit Linux

    I've downloaded and installed the 64-bit version of WebLogic Server for Linux. It is running on a 64-bit Xeon RHEL 5 machine with 64-bit Sun JVM.
    During the install, I selected WebLogic Server and Weblogic Workshop but it appears that Workshop was not installed. Apparently, only the Runtime for Workshop was installed. I'm not really sure what good that does for me.
    We need to use the Workshop IDE to develop apps. Is there a 10.0 version of Workshop for 64-bit Linux?

    Hi Anup,
    Maybe you should be a bit more specific about what you want to do. Coherence is just Java and has been supported WebLogic for years in the same way most other third-party Java libraries and APIs are. I first started using Coherence about four or five years ago with WebLogic 8.
    JK

  • Upgrade Weblogic Server Issue

    Hi,
    I have an installation of oracle weblogic server 10.3.5.0 with ADF 11.1.1.5.0. I can upgrade weblogic server to 12.1.3.0 ?

    I have installed a fresh WebLogic Server 12.1.3, and then I'm using Reconfiguration Wizard to upgrade my weblogic domain to 12.1.3, but it's unfortunately, it's failed as below:
    2015-04-06 15:10:20,677 INFO  [1] com.oracle.cie.wizard.internal.wcf.WCFWrapper - Overriding task definition summary_gui
    2015-04-06 15:10:22,142 INFO  [13] com.oracle.cie.domain.info.DomainInformationImpl - initializing domaininformation object.
    2015-04-06 15:10:22,925 INFO  [13] com.oracle.cie.domain.DomainRegistryWrapper - need to initialize domainRegistrydocument object
    2015-04-06 15:10:22,939 INFO  [13] com.oracle.cie.domain.info.DomainInformationImpl - initializing domaininformation object.
    2015-04-06 15:10:45,975 INFO  [52] com.oracle.cie.domain.info.DomainInformationImpl - initializing domaininformation object.
    2015-04-06 15:10:46,075 SEVERE [52] com.oracle.cie.domain.info.DomainUtilsImpl - No reconfig template exists for template Oracle BI Composer Runtime:11.1.1.0
    2015-04-06 15:10:46,075 SEVERE [52] com.oracle.cie.domain.info.DomainUtilsImpl - No reconfig template exists for template Oracle BI-ADF Runtime:11.1.1.0
    2015-04-06 15:10:46,075 SEVERE [52] com.oracle.cie.domain.info.DomainUtilsImpl - No reconfig template exists for template Oracle JRF:11.1.1.0
    2015-04-06 15:10:46,077 SEVERE [52] com.oracle.cie.domain.WLSCoreReconfigurator - Reconfiguration failed
    com.oracle.cie.domain.ValidateException: CFGFWK-60971: The domain is not reconfigurable.
    CFGFWK-60971: The domain did not contain information necessary to determine how to reconfigure the domain.
    CFGFWK-60971: Refer to the upgrade documentation on how to proceed.
      at com.oracle.cie.domain.WLSCoreReconfigurator.run(WLSCoreReconfigurator.java:163)
      at java.lang.Thread.run(Thread.java:745)
    Caused by: com.oracle.cie.external.domain.info.DomainInfoException: No reconfig template exists for templates:
      Oracle BI Composer Runtime:11.1.1.0
      Oracle BI-ADF Runtime:11.1.1.0
      Oracle JRF:11.1.1.0
      at com.oracle.cie.domain.info.DomainUtilsImpl.validateReconfigurable(DomainUtilsImpl.java:128)
      at com.oracle.cie.domain.WLSCoreReconfigurator.run(WLSCoreReconfigurator.java:158)
      ... 1 more
    2015-04-06 15:10:46,081 SEVERE [52] com.oracle.cie.domain.WLSCoreReconfigurator - Reconfiguration Failed!
    Exception:
    CFGFWK-60971: The domain is not reconfigurable.
    CFGFWK-60971: The domain did not contain information necessary to determine how to reconfigure the domain.
    CFGFWK-60971: Refer to the upgrade documentation on how to proceed.
    com.oracle.cie.domain.ValidateException: CFGFWK-60971: The domain is not reconfigurable.
    CFGFWK-60971: The domain did not contain information necessary to determine how to reconfigure the domain.
    CFGFWK-60971: Refer to the upgrade documentation on how to proceed.
      at com.oracle.cie.domain.WLSCoreReconfigurator.run(WLSCoreReconfigurator.java:163)
      at java.lang.Thread.run(Thread.java:745)
    Caused by: com.oracle.cie.external.domain.info.DomainInfoException: No reconfig template exists for templates:
      Oracle BI Composer Runtime:11.1.1.0
      Oracle BI-ADF Runtime:11.1.1.0
      Oracle JRF:11.1.1.0
      at com.oracle.cie.domain.info.DomainUtilsImpl.validateReconfigurable(DomainUtilsImpl.java:128)
      at com.oracle.cie.domain.WLSCoreReconfigurator.run(WLSCoreReconfigurator.java:158)
      ... 1 more
    I think this error is caused by ADF runtime version 11.1.1.5.0 that I'm using, but i don't know how to fix it.

Maybe you are looking for