SonicMQ JMS -- XI -R/3

Hi ,
I have this error in my sender SonicMQ JMS adapter
Error while processing message '146d35e0-0bc4-11dd-c864-0017a4772010'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ...
Any idea on what this might be??
Mudit

Hi Jai,
Here is one solution from forum which was helpful for me when i was facing the same problem... See if it helps you...
Check the Queue, by double clicking the Queue id in the SXMB_MONI/SMQ2. Then try to execute the LUW of that. Probably, you can see this error in the Queue Monitor itself "JCO Failure.."..
If so go to SM59->
- Go to TCP/IP Connections-> AI_RUNTIME_JCOSERVER->double click
- Test the RFC destination. If connection is failure then it should be fixed. You may need to delete the entry and recreate the same . Still error may be required to restart the server.
If so, it may be because of Java Virtual Memory problem, no of parallel processes assigned in the Visual Admin..
Also have a look at these threads...
Problem in executing ABAP Proxy
Systems error- restart not possible
Regards,
Abhy
Message was edited by: Abhy Thomas

Similar Messages

Latest Versions of SonicMQ JMS Provider supported by PI71

Hello Experts,
I have a query on PI-JMS Adapter, where SonicMQ-JMS Provider will be used. As per the below link :
http://help.sap.com/saphelp_nwpi71/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
I do know that the version of SonicMQ supported by PI7.1 is 3.0.
But can anyone please tell me which all are the versions of SonicMQ (uptoV7.5) been supported by PI7.1??
Thanks,
Santanu

Download Firefox 3.6.19 from here:
* http://www.mozilla.com/en-US/firefox/all-older.html
* Save the File on your Desktop
Uninstalling Firefox
* https://support.mozilla.com/en-US/kb/Uninstalling%20Firefox
Installing Firefox on Windows --- Install the Downloaded Firefox 3.6.19 version
* https://support.mozilla.com/en-US/kb/Installing%20Firefox%20on%20Windows
Check and tell if its working.

Doubts in JMS Sender adapter configuration (SonicMQ JMS Provider)

Hi All,
I am doing a TIBCO--> XI integration using JMS sender adapter. Adapter status is as follows..
"Sender channel. Details: (No detail information set.)".
XML Msg in TIBCO-ems queue which JMS adapter access is as follows.....
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Studdetails xmlns:ns0="http://abc.com/xi101/XSLTmap">
 <Records>
 <student_ID>
 <fname>abc</fname>
 <lname>efg</lname>
 <DOB>11/09/1980</DOB>
 <marks>
 <science>90</science>
 <maths>78</maths>
 <lang>80</lang>
 </marks>
 </student_ID>
 </Records>
</ns0:MT_Studdetails>
My Queries...
what will be the Msg selector entry for my JMS sender Adapter? Is it MT_Studdetails???
My sender adapter is green in RWB Adapter Monitor, but I am not able see my msg in SXMB_MONI. why it is so??
regards,
Raks

Hi,
Did you follow the how-to guide available at SAP Marketplace to deploy the JMS Adapter. If so, i believe the information given in that guide is incomplete.
Once you have installed the JMS Driver, you must deploy the Java libraries on the J2EE server so that the JMS adapter can access the required Java classes at runtime.
If you use MQSeries 53x.xxx, you must enter the following JAR files in aii_af_jmsproviderlib.sda.
com.ibm.mq.jar
com.ibm.mqbind.jar
com.ibm.mqjms.jar
connector.jar (use the JAR file from the J2EE client directory)
and if ur question is, "Where do I get the Java Library from "
The required Java libraries are product-specific and can be obtained from either the product vendor or other providers.
And i guess the 4 jar files should be enough. Just remember to add these 4 jar files to 'provider.xml' file inbetween the <jars>..</jars> tag.
Follow the instructions as per the guide,
https://websmp205.sap-ag.de/~sapdownload/011000358700003994312004E/HowTo_ConfigExtAdapters.pdf
But just remember to have all the 4 jar files in aii_af_jmsproviderlib.sda
Regards,
Abhy

Errors on JMS communication Channel sonicMQ JMS Provider netweaver2004s

After deploying supplier specific jar's Sonic_Client.jar into aii_af_jmsproviderlib.sda.
I get the following error in the communication channel monitoring.
Channel CC_SONIC_RECEIVER is errornous, hence it cannot be started. See error messages ( Error during channel initialization; exception trace: java.lang.ClassCastException
 at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:372)
 at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 ...) before. Reconfigure it or restart the JMS service!
Any suggestions about the cause...

yes the drivertool.bat does it for me
<?xml version="1.0" encoding="UTF-8"?>
<provider-descriptor>
 <display-name>com.sap.aii.af.jmsproviderlib</display-name>
 <component-name>com.sap.aii.af.jmsproviderlib</component-name>
 <major-version>7</major-version>
 <minor-version>0</minor-version>
 <micro-version>6</micro-version>
 <provider-name>sap.com</provider-name>
 <references>
 <reference type="library" strength="weak">jms</reference>
 <reference type="library" strengh="weak">com.sap.aii.messaging.runtime</reference></references>
 <jars>
 <jar-name>sonic_Client.jar</jar-name><jar-name>sonic_XA.jar</jar-name></jars>
<
At this moment i am receiving the following error on the communication channel
Exception caught by adapter framework: The JMS channel with channel ID f055fe2451203cd5b39d81c7647b281e is errornous. Details:Error during channel initialization; exception trace: javax.jms.JMSException: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:2600 at progress.message.jimpl.JMSExceptionUtil.createJMSException(Unknown Source) at progress.message.jimpl.Connection.(Unknown Source) at progress.message.jimpl.QueueConnection.(Unknown Source) ... [104] progress.message.client.ENetworkFailure: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:260

How to configure a full JMS Sender Adapter Scenario

Hi guys,
I have to do a JMS -> PI (7.1) -> File scenario, I never used JMS Adapter, and I'd like to tell you what I have done, and what I think is missing.
First I went to the NetWeaver Administrator ->Configuration Management ->Infrastructure ->JMS Server Configuration-> Create ->JMS Queue.. and I created a new Queue from a Virtual Provider (SAP JMS Provider).
The first thing I didn't know how to configure it is which transport protocol I have to choose in the CC adapter (SonicMQ JMS Provider, WebSphere MQ, etc..)
But I also don't know is if there's something missing on the NWA, to create, modify, etc. I read this slide: (https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0) where was shown how to create a SAP standard queue, and I also read all the documentation from help.sap.com (all the JMS basics and explanation) but I still don't know how to fully configure the CC and how to trigger the messages.
Please, if you need further information I can give it.
Thanks in advance.
Juan

Hi,
did you try this blog from William?
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Regards,
Michal Krawczyk

JMS Internal Error at Server Client Adapter!JMS Service is not started

Hi
Can any one tell me how to trouble shoot for following errors:
Failed to Create Connection! Reason: Response from the server could not be reached.
JMS Internal Error at Server Client Adapter!JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310
We are trying to send the request from SONICMQ JMS to R/3 and trying to post the response to Sonic Queue. but we are facing some problems for JMS adapter .
but in JMS sender and receiver adapter i gave different IP and port for listen the SONIC queue. why it is showing in different IP here? this message got from logviewer.
regards
Rambarki...

Rambarki,
What is the error displayed on the Adapter Monitoring pages?
Generally the correct error descriptions for connectivity issues are found on adapter monitoring UI than any other.
Other possible reasons could be :
JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310 This might be issue with your network settings i.e. XI server is unable to reach the specified IP on specified port.
Regards,
Amol

XI JMS adapter after JMS provider reboot

Hi All,
I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
In JMS adapter we have folloving settings and we are connected straight into queue:
Transport Protocol = SonicMQ JMS Provider
General JMS Settings:
Transactional JMS Session is in use
Delivery Mode of Message Producer = Persist JMS messages..
+ Queue user & pw
Error Handling Settings:
Wait After Message Error(msecs) = 60000
Wait Before Reconnect(msecs) = 60000
Does anyone ran into this earlier?
Thanks in advance.
-Kimmo

Hi Saravana,
It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

JMS Channel Settings

Hi,
I have to configure a JMS sender channel (SonicMQ) and the client has provided me with a JNDI name jmsqueues/default/<QueueName>
Can anyone please tell me in which section of the JMS channel should i include this information?
QueueConnectionFactory Java Class or Queue Java Class
Thank you,
Pankaj.

>
> If I select SonicMQ JMS Provider in channel then i do not get the JNDI section. However if I select Access JMS Provider with JNDI I do get the JNDI section where I can enter the value as jmsqueues/default/<QueueName>
>
> SAP Note 802754 tells that Many JMS providers allow to access the JMS provider server using JNDI
> Does it mean I can connect to sonicMQ using JNDI option in channel?
>
i think you can connect .
> Do I need to perform some additional setting within PI to use JNDI to connect to SonicMQ?
>
as per my knowledge additions setting not required.,
Regards,
Raj

JMS protocol with AXIS Adapter

Hi,
I need to configure the sender AXIS adapter to access SonicMQ JMS queues via Open LDAP. I looked at the AXIS Adapter documentation and no examples are provided to access SonicMQ via OpenLdap.
I do see the documentation to access the JMS providers directly by specifying the URL as "jms://ABCD"
but what i am looking for is to access the JMS objects via LDAP. The standard SAP JMS Adapter has the functionality to access JMS via LDAP. but i need to use AXIS adapter for WS-Security
Any help is greatly appreciated
Thanks
Chandra

Hi Chandra,
As far as I know, this is not directly supported via SOAP Axis Adapter. But one question which I would like to ask is are you trying to configure WS Security using Axis Handlers or you are trying to use the WS Security provided by SAP PI i.e. configuring Security Profile in the Sender Channel?
If you are trying to do it with Axis Handlers may be you can try using the Adapter modules specified in this link which can be used tto call Axis Handlers. <http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm>. Although documentation says that this is supported for SOAP adapter but you can still try as the message returned is still a valid AF message.
Best Regards,
Pratik

UTF16LE and UTF16BE - JMS channel

HI,
My scenario is IDOC -> PI -> JMS. From PI, I am sending as a text message in UTF-8 format to MQ.
I have set the below parameters in the JMS channel:
1.CharacterSet ID(CCSID) for non ASCII Names -1208
2.Used the bean localejbs/AF_Modules/MessageTransformBean* to convert the xml to text message and given the Transform.ContentType as text/plain;charset=utf-8
The requirement here is I have to send the text message in UTF16LE or UTF16BE format to JMS instead of UTF-8.
could you provide the CCSID code for UTF16LE / UTF16BE and also the values to be given in Transform.ContentType .
Thank you very much in advance!
Kiruthi

>
> If I select SonicMQ JMS Provider in channel then i do not get the JNDI section. However if I select Access JMS Provider with JNDI I do get the JNDI section where I can enter the value as jmsqueues/default/<QueueName>
>
> SAP Note 802754 tells that Many JMS providers allow to access the JMS provider server using JNDI
> Does it mean I can connect to sonicMQ using JNDI option in channel?
>
i think you can connect .
> Do I need to perform some additional setting within PI to use JNDI to connect to SonicMQ?
>
as per my knowledge additions setting not required.,
Regards,
Raj

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
"ERROR CALLING THE RESTART ADAPTER"
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
# *************************************************************************************************************
#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
# *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
# uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
# uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
# *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards,

Adapter Engine Error

Hi,
i am working on MQ-XI-BW Scenario.i have configured JMS Adapter in Plain J2SE Adapter Engine.But the status is red with a message
"javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'BWXI:TEST.QMGR'
 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
 at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
 at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
 at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:382)
 at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
 at java.lang.Thread.run(Unknown Source)"
My class path looks fine.i am on SP9. there is an OSS note with similar error. But the Pre requisite is given as SP5.
what could be the reason behind this issue?
When i try to refresh the central integration server cache in ID using Env->Cache Notifications, i am getting a message
 http connection to "http://bwxi:8200/CPACache/invalidate" returns the status code "401" in response
This particular URL is not accepting any user and password. Do i need to set the user name and password somewhere so that i can have access to this?
Please help me out.
Regards
Sathya

Hi Amol,
 Thanks a lot.I am not very confident in my configuration.Could you please verify the configuration parameters once?
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
XMB.SenderBusinessSystem=MQSeries
XMB.SenderService=BS_MQ
XMB.SenderInterfaceNamespace=http://xitest
XMB.SenderInterfaceName=MI_Out_File
XMB.ReceiverBusinessSystem=MTX
XMB.TraceLevel=1
XMB.LoggingLevel=1
XMB.QualityOfService=EO
XMB.QueueId=ABCDEFABCDEF
XMB.ContentType=text/xml
URL of XI IS to send the messages to
XMB.TargetURL=http://bwxi:8000/sap/xi/engine?type=entry
XMB.User=XIISUSER
XMB.Password=Mind2005
XMB.Client=100
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=MUSR_MQADMIN
JMS.QueueConnectionFactoryImpl.password=Mind2005
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
#JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
#JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
#JMS.QueueImpl.classname= progress.message.jclient.Queue
#JMS.QueueImpl.constructor=java.lang.String SampleQ1
uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
#JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String CH_BWXI
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String TEST.QMGR
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String LQ
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Regards
Sathya

RFC Questions

RFC support EOIO?
Or
RFC Support only BE?.
Or
RFC support BE and EO?.
Which is correct?.

RFC supports all the three BE,EO,EOIO but no qrfc.
Adapter Types and Attributes
Adapter Type
Transport Protocol
Message Protocol
Quality of Service
Attachments
Acknowledgments
Attributes in Message Header
IDoc
Sender Adapter:
●     tRFC
●     File
Receiver Adapter:
●     tRFC
IDoc-XML
EO, EOIO with qRFC
No
System acknowledgments
(not at sender)
System error acknowledgments
Application acknowledgements
Application error acknowledgements
RFC
RFC
RFC-XML
BE, EO, EOIO
No
See below
Sender
Plain HTTP
HTTP(S) 1.0
XI payload in HTTP body
BE, EO, EOIO
No
Receiver
System acknowledgments
System error acknowledgments
Sender
Receiver
SAP Business Connector (BC)
HTTP(S)
RFC XML with envelope
IDoc-XML
BE, EO
No
See below
File/FTP
●     File system (NFS)
●     File transfer protocol (RFC 959)
File transfer protocol using SSL/TLS (RFC 4217)
·         File
·         File with content conversion
BE, EO, EOIO
Yes
(Sender)
See below
Sender
Receiver
JDBC
JDBC 2.0
Sender Adapter:
JDBC 2.0
Receiver Adapter:
●     XML SQL format
●     Native SQL format
BE, EO, EOIO
No
See below
JMS
·         SonicMQ JMS Provider
·         WebSphereMQ (non-JMS)
·         Access JMS Provider with JNDI
·         (Read) JMS Provider Administered Objects from File
·         Access JMS Provider Generically
JMS 1.x
EO, EOIO
No
See below
Sender
Receiver
SOAP
Sender Adapter:
●     HTTP
Receiver Adapter:
●     HTTP(S)
●     SMTP(S)
SOAP 1.1
BE, EO, EOIO
Yes
(sender, receiver)
See below
Sender
Receiver
Marketplace
·         HTTP(S)
·         JMS Sonic MQ 3.5
MML
BE, EO
Yes
(sender, receiver)
See below
Mail
Sender Adapter:
●     IMAP4
●     POP3
Receiver Adapter
●     IMAP4
●     SMTP
·         IXALL
·         XIPAYLOAD
BE, EO, EOIO
Yes, for XIPAYLOAD
(sender, receiver)
See below
Sender
Receiver
RNIF20
·         HTTP 1.1
·         HTTPS
RNIF 2.0
EO
No
See below
Sender
Receiver
(for those replying to two actions)
RNIF11
·         HTTP 1.1
·         HTTPS
RNIF 1.1
EO
No
See below
Sender
Receiver
(for those replying to two actions)
CIDX
·         HTTP 1.1
·         HTTPS
RNIF 1.1
EO
No
See below
Sender
XI
HTTP(S) 1.0
·         XI 2.0
·         XI 3.0
BE, EO, EOIO
Award points if useful.
No

What kind of protocals used in XI

Hi,
What kind of protocals are used in XI generally.

Hi,
Usually that depends on adapter which you are using
refer this,
Adapters
Purpose
Adapters enable the PCK to communicate with different systems.
Features
Adapters are used to connect the PCK both to SAP Exchange Infrastructure and to other systems.
The PCK provides a variety of adapters for this purpose. You can use these adapters to convert XML and HTTP-based messages to the specific protocols and formats of these systems and the other way around.
The PCK provides adapters, which you can use to do the following, depending on how they are configured:
Communicate with SAP systems using the RFC interface (RFC adapter)
Enable data exchange with the SAP Business Connector (SAP Business Connector adapter)
Exchange data with systems by using a file interface or an FTP server (file/FTP adapter )
Access databases using JDBC (JDBC adapter)
Communicate with messaging systems using the JMS API (JMS adapter)
Integrate remote clients or Web service providers using the SOAP adapter (SOAP adapter )
Connect e-mail servers to the PCK (mail adapter)
Exchange data with SAP Exchange Infrastructure (XI adapter)
In the adapter configuration, you specify whether an adapter is located at the inbound channel (sender adapter) or at the outbound channel (receiver adapter) of the PCK.
Adapter Types and Attributes
Adapter Type Transport Protocol      Message Protocol          Quality of Service
RFC     RFC     RFC-XML     BE, EO, EOIO
SAP Business Connector (BC)     HTTP(S)     RFC XML with envelope
IDoc-XML     BE, EO
File/FTP     File system (NFS)
File transfer protocol/file transfer protocol using SSL/TLS     File
File with content conversion     BE, EO, EOIO
JDBC     JDBC 2.0     Sender adapter:
JDBC 2.0
Receiver adapter:
XML SQL Format
Native SQL Format
     BE, EO, EOIO
JMS     SonicMQ JMS Provider
WebSphereMQ (non-JMS)
Access JMS Provider with JNDI
(Read) JMS Provider Administered Objects from File
Access JMS Provider Generically     JMS 1.x     EO, EOIO
SOAP     Sender adapter:
HTTP
Receiver adapter:
HTTP(S)
SMTP(S)     SOAP 1.1     BE, EO, EOIO
Mail     Sender adapter:
IMAP4
POP3
Receiver Adapter
IMAP4
SMTP     IXALL
XIPAYLOAD     BE, EO, EOIO
XI     HTTP(S) 1.0     1.     XI 2.0
2.     XI 3.0     BE, EO, EOIO
reg,
suresh

So hard to deploy a JDBC driver

My PI7.1, I use the "netwaver Administrator" CM->Application Resources to deploy the jdbc driver of postgre, it told me the deploy is OK, but the "Status" of the driver is "Unknown".
And when I try to invloke a channel which uses this postgre JDBC driver, it throws exceptions: can not find class org.postgresql.Driver
What should I do !!! I grep much time in the forum but did not find any clue yet

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1138877
FYI~~
Summary
Symptom
This note describes the procedure for deploying 3rd party drivers on PI 7.1 using JSPM.
Other terms
JMS, JDBC, 3rd Party, Drivers, JSPM, com.sap.aii.adapter.lib, provider.
Reason and Prerequisites
When connecting to 3rd party software using JDBC and JMS adapters, external drivers need to be provided.
These 3rd party drivers need to be bundled in com.sap.aii.adapter.lib.sda provided by the adapter engine installation.
Prior to PI 7.1 this was done using the SDM tool, however, in PI 7.1 JSPM is used to deploy com.sap.aii.adapter.lib.sda.
This note described the steps for deployment using JSPM.
Solution
For the JMS Driver only
Prepare the JMS provider file as follows:
1. Copy the external drivers from the provider directory to a separate directory.
For example the SonicMQ driver file is called client.jar and is located in the lib subdirectory of SonicMQ installation directory.
2. Open the driver file with a zip program and remove the standard JMS classes. These are located in directory javax/jms.
3. Save the modified driver file.
For the JDBC Driver and the JMS Driver
Add the modified driver files to the lib directory of the archive com.sap.aii.adapter.lib.sda with the help of a zip program.
Then to modify the provider.xml file in the server directory of the archive com.sap.aii.adapter.lib.sda, proceed as follows:
1. Extract provider.xml using a zip program and edit it as follows:
a. For each external driver file that needs to be bundled in com.sap.aii.adapter.lib.sda, add the line <jar-name>lib/driver-jar</jar-name> in the <jars> section.
If you want to install the SAP DB JDBC driver and the SonicMQ JMS driver, this section looks like this:
<jars>
<jar-name>lib/sapdbc.jar</jar-name>
<jar-name>lib/client.jar</jar-name>
</jars>
b. Return the changed provider.xml to the archive.
Make sure that the original directory server\ is retained under Path in the zip archive.
2. Add all external driver jars that you have defined in provider.xml to the lib directory in the archive com.sap.aii.adapter.lib.sda.
3. Use the JSPM tool to deploy com.sap.aii.adapter.lib.sda.
a. To start JSPM, run 'go' from the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/ directory.
b. Log on with the AS Java username and password.
c. Select 'HotFixes' option as the package type.
d. Place the com.sap.aii.adapter.lib.sda in Inbox directory.
This will be mentioned in the Select Package Type dialog.
By default this is
<HOST>\sapmnt\trans\EPS\in.
e. Select Next.
f. If no applicable development component(s) are found in the Inbox directory then:
i. Check to see if the Inbox directory is correct and has the com.sap.aii.adapter.lib.sda.
For more information on this refer to 'Detecting and Changing the JSPM Inbox Directory' section of the JSPM documentation.
ii. JSPM does not allow to deploy an SCA/SDA with the same version (release, SP-level, patch-level) as an already deployed component.
In such a case, the com.sap.aii.adapter.lib.sda will not be listed in the Specify Queue dialog box.
To force the deployment of an such SCA/SDA ignoring version rule run the 'go' command as follows:
go -config=/jspm/forceMode=true
-config=/jspm/deployVersionRule=updateAll
For more information on this please refer to SAP Note 1123333.
f. Select the hot fixes to deploy. In this case sap.com/com.sap.aii.adapter.lib and press Next.
g. For more information about deployment procedure, refer to JSPM documentation.
FAQs
Q1. Where can I find JSPM documentation?
Ans. Link to the JSPM User Guide on SAP Help Portal:
help.sap.com -> Documentation -> SAP NetWeaver -> SAP NetWeaver 7.0 (2004s) -> choose a language -> SAP Library -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management by Key Capability -> Solution Life Cycle Management by Key Capability -> Software Life Cycle Management -> Software Maintenance -> Java Support Package Manager
Q2. Where can I find more information on JSPM?
Ans. Refer to SAP Note 891983
Q3. I am unable to see any SCA/SDA in the Specify Queue dialog box.
OR
I get the message "No applicable development component(s) found in the Inbox directory"
OR
How do I force the deployment of a component ignoring version rules ?
Ans. Refer to SAP Note 1123333.
Q4. Where can I find more information on the JMS Adapter?
Ans.Refer to SAP Note. 856346.
Q5. Where can I find more information on the JDBC Adapter?
Ans. Refer to SAP Note. 831162
Q6. Which external driver files do I need to bundle in the com.sap.aii.adapter.lib.sda?
Ans. Refer to JMS and JDBC Adapter notes mentioned above.
Q7. What are some of the things that have changed with respect to the adapter lib from XI 30 to PI 7.1?
Ans. The library name has changed from aii_af_jmsproviderlib.sda (releases 3.0/7.0) to com.sap.aii.adapter.lib.sda (release 7.1).
The component name has changed from com.sap.aii.af.jmsproviderlib (releases 3.0/7.0) to com.sap.aii.adapter.lib (release 7.1).
Even the directory structure has changed. The com.sap.aii.adapter.lib.sda (release 7.1) has a lib directory in which all the external drivers need to be placed.
This was not present in aii_af_jmsproviderlib.sda (releases 3.0/7.0) and the external drivers were placed in the root directory of the archive
Q8. Can I use the DriverTool (provided with XI 3.0) to bundle the jars in com.sap.aii.adapter.lib.sda?
OR
Is there a new DriverTool for bundling the external jars in com.sap.aii.adapter.lib.sda?
Ans. No. Due to the changes mentioned above, the DriverTool provided with XI 3.0 cannot be used to bundle external drivers in com.sap.aii.adapter.lib.sda.
No. There is no new tool for bundling the external jars in com.sap.aii.adapter.lib.sda. This needs to be done manually as described in the steps above.

SonicMQ JMS -- XI -R/3

Similar Messages

Maybe you are looking for