XI Vs Tibco Vs Webmethods

Hi
One of our customer has 100+ interfaces both SAP to Non-SAP & Non-SAP to Non-SAP. All these interfaces are manually operated and tedius metodology
Now the customer would like to go for interface tools like SAP-XI, Tibco or Webmethods.
What are the factors were I can recommend a customer to select either of the interface technology.
Thanks & Regards
Madhu

Hi,
XI comes handy particularly incase of SAP-nonSAP interfaces where u can import standard integration content. Also XI has got sophisticated open standard adapter framework which is very easy to implement and custom logic can be implemented using Adapter module programming.
I guess mappings and adapters are as comparable with any other middleware product. Monitoring is better than any other middleware product.
I guess it lacks in ability to process huge messages but SAP is working on that. Also it does not have a messaging layer exposed by APIs like IBM MQ-Series. Also I guess it is not comparable to Tibco in terms of speed.Webmethods is particularly good if u have B2B kind of communication with their Trading Partners product.
Regards
Rajeev

Similar Messages

Migrating from TIBCO to SAP XI

Hi All,
One of the company are migrating from Tibco. Please suggest me,if there are any tools which would support a migration to XI and if there are any notes on the web stating where most people had issues migrating from Tibco.Please note One of the interfaces will use JMS, Please send me ur suggetions and some related documents too.Please respond <Read Rules of Engagement>
Thanks in Advance
Thanks,
Aravind.Pujari
Message was edited by: Prateek Raj Srivastava

HI,
Aslo see the below links
XI Vs Tibco Vs Webmethods
Re: Why XI ??
Differences between Tibco BW and how to do canonical mapping in XI
http://www.sap.com/solutions/netweaver/pdf/BWP_SB_ExchangeInfrastructure.pdf
XI integration with PSFT/Seibel ?
Performance statistics of SAP XI
/thread/154189 [original link is broken]
publish subscribe with XI
XI in SRM, CRM, MDM
XI implementation - xi implementation
Regards
Chilla

How to connect tibco ems with sap xi engine?

hi friends,
how to connect tibco ems with sap xi engine?
plz explain me in brief. if possible plz give some link.
thanks & regards
Ruban

Hi Ruban
refr this links
Re: XI 3.0 - Tibco integration
<b>IBCO -> XI SCENARIO -> Web Service</b>
http://dev.systinet.com/doc/ssc-60/primer/html/using.web.services.html
http://www.estrategy.gov/presentations/umd_e-gov_ent_arch/sld015.htm
General disadvantages of using web service
http://www.samspublishing.com/articles/article.asp?p=31555&rl=1
http://www.omg.org/news/whitepapers/CORBA_vs_SOAP1.pdf
Replace TIBCO with XI
Tibco & XI
XI integration with Tibco
<b>
Aslo see the below links</b>
XI Vs Tibco Vs Webmethods
Re: Why XI ??
Differences between Tibco BW and how to do canonical mapping in XI
http://www.sap.com/solutions/netweaver/pdf/BWP_SB_ExchangeInfrastructure.pdf
XI integration with PSFT/Seibel ?
Performance statistics of SAP XI
/thread/154189 [original link is broken]
publish subscribe with XI
XI in SRM, CRM, MDM
XI implementation - xi implementation
Thanks!!

XI in SRM, CRM, MDM

Hello. I am trying to clarify when a customer must buy XI (3.0) as a central HUB. I understand that SAP is building integration scenarios and mappings in XI 3.0 so companies may want this. I also undertand that SRM and CRM come with its own Integration Engine in order to communicate with other mySAP components. This does not entail configuring XI 3.0. Can somebody please confirm that:
1) for CRM and SRM, which comes with integration engines for SAP to SAP communication, XI 3.0 is not required. XI 3.0 is required only if you to create new integration scenarios, in which case you can also use Tibco or Webmethods if that is the EAI platform of choice.
2) You do not need XI 3.0 to generate a proxy, it could be done with WAS.
3) For MDM, you must buy XI 3.0.
thanks....

Hi Mark,
>>2) You do not need XI 3.0 to generate a proxy, it could be done with WAS.
if you want to use TCODE SPROXY to create a proxy on your
WAS then you have to use XI if you want to use web
services (caterd on the basiss of RFC for instance) then
you don't need XI
>>3) For MDM, you must buy XI 3.0.
In the Inbound scenarios a file is transferred using XI
(File Adapter) and loaded into MDM (then import manager
takes care of the rest)
>>1) for CRM and SRM, which comes with integration engines for SAP to SAP communication, XI 3.0 is not required. XI 3.0 is required only if you to create new integration scenarios, in which case you can also use Tibco or Webmethods if that is the EAI platform of choice.
there are many XI free delivered contents for CRM and SRM
so probably XI should be considered as a platform of
your choise if you want to integrate CRM even with
another SAP
(but I'm not sure if this is a must)
Regards,
michal

Replacing XI with other technology

Hi,
I am exposer to XI. I need to know Where exactly use XI and what kind of projects we will expect in XI. Is there any Replacement or Compitator for XI In real time what kind of work its have.

XI is a middle ware which sits in between two or more different softwares/systems to exchange the data (in form of messages) in their respective format. XI helps them send/receive the data in their respective formats.
XI.. MQ series...Tibco ... etc are all data exchange architectures. So they are all same.
And these needs to be installed according to requirement of the existing SLD systems. So EAI tool (XI/TIBCO/MQ/WEBMETHODS) installation depends on existing SLD systems.
Some of the urls where you can get some info about the middleware products XI, Biztalk, Webmethods etc are:
Re: SAP XI versus BizTalk
Re: Need of XI !!!!
scorecarding XI
Re: can i material to learn XI from basics
Re: XI role in interface!

Please advise the benefit of XI

Dear Sir,
Can you advise the benefit of XI ? I need to find the document
Best regards,
Vimol

Hi
in the market there are lot of integration tools
like Tibco , Biztalk , Webmethods ..have a look on the following comparison XI vrs all.
We concluded with the following; BizTalk should be used as the main integration engine between the different system landscapes and ALL external communication, and XI should be used as the integration engine for all data to/from our SAP system landscape. Depending on the integration scenario, we may use both.
BizTalk will not see any SAP systems, only web services exposed by XI or using IBM MQ depending on an async/sync integration scenario.
We believe that XI is better with integration from/to SAP, and;
- In future SAP will deliver out of box integration for the XI system (XI content) for Enterprise Services Architecture
- Several components in the NetWeaver stack are using XI for communication
We have a SAP system landscape with several 46C systems (IS/OIL, HR ...) and newer NetWeaver solutions.
BizTalk ******
Overall communication between SAP systems and BizTalk depending on the integration scenario and who is the initiator:
SAP 46C to BizTalk:
There are no good mechanisms available for sending data from 46C to BizTalk, we are using HTTP_POST with XML payload. Then you must use the iXML library on the SAP side, its ok, but you will spend, in my point of view, too many hours on XML programming that can be generated automatically.
BizTalk to SAP 46C - Which SAP adapter to use for BizTalk?
We started with SAP adapter from IWay, but that adapter gave us a lot of problems on the BizTalk server (pretty complex adapter with strange behaviour, and several integration scenarios stopped working for no reason at all (unstable)).
The SAP adapter from Microsoft is more stable than the previous,
SAP 640 to/from BizTalk:
I assume you can use the web service functionality on the SAP side in order to send/receive data, but I dont know whether 640 support asynchronous web service.
XI *****
The communication mechanism between different SAP systems and XI are much better than with BizTalk:
SAP 46C to XI:
Configure a sender communication channel with RFC adapter; basically the XI system will be RFC server so the only thing you have to do is to create a RFC port on the 46C system pointing to the XI system. In the Abap program, you can do normal function calls with destination (RFC port) AND the RFC call will automatically be translated to XML on the XI side.
Thus, you can forget all about the iXML library and XML rendering of the payload to HTTP.
Besides, you can choose to use sRFC, tRFC or even qRFC depending on the integration scenario and whether you want guaranteed delivery.
XI to SAP 46C:
More or less same as BizTalk using a SAP adapter, but string and table types are supported.
SAP 640 to/from XI:
This is a very nice situation, every 640 has a local integration engine, so the main integration engine (XI) can send/receive XML messages both async/sync. Another advantage is using the SPROXY transaction on the 640 system, generating automatically a proxy class being able to send/receive messages based on a message interface defined in XI (outside-in programming).
Finally *****
BizTalk and XI are at a conceptual level identical, two integration engines with the purpose of send/receive, route and do message transformation (mapping) using adapters to different technical systems.
SAP came late with XI, best integration engine, good enough. And for sure, I think SAP will come with very nice XI content in time (interface mappings between message interfaces business solutions) which is beyond BizTalk.
Regds
Abhishek

Question: Migration from Tibco BW to SAP XI

I have been actively involved in TIBCO BW projects as project co-ordinator for the past year. Now i am thinking of shifting into SAP XI. I am assuming that SAP XI has the same underlying concept as TIBCO BW. Is my assumption correct? If yes then how hard would it be for me to transfer from Tibco to SAP XI. Please provide appopriate justifications for your answers.
Thanks

Hi,
Its very tough to generlize like i remember my present case wherein we upgraded Webmethods landscape and we decided to reuse the existing mapping sheets, that was one Point.
Now it depends on the EAI tool existing in your case for reuseability.
Then,reusing the 3rd party files in intregation,
Re: XI ABAP Proxy problem
One similar thread i remember was,
SAP XI versus BizTalk
a discussion on xi and other middleware.
Plus intregation with webservices, RFID etc.(If needed in your case).
I know this is not a specific answer that i have given you, but sharing my thoughts.
Anirban.

XI vs TIBCO

Hi all,
I have learned XI.
And I want to know about the other existing middleware technologies like TIBCO, WebMethods, etc....
And how XI is better than them?

Hi Krishna,
Its good tht u have learnt XI but try to get some practical exposure to face some real time problem which will give u more knowledge.
But as you are interested in other middleware to compare with XI .Websphere is one very good example to start with .Its capabilites are some places better than XI and it can be mappped to SAP also .
However this issue is always debatable over which is better middleware but SAP XI is definitely better option considering when u have to have nay one system as SAP as it is SAP proprietry.It will take sometime to mature but still good contender for Middleware .For Websphere u can check the ibm standard silte for more info
Regards,

Usando GRC NFe com Outro Middleware (TIBCO)

Pessoal,
Estamos instalando o GRC NFe em uma empresa e por questões de segurança o PI não pode "sair" para internet.
Assim, ao invés de me comunicar com o SEFAZ, estou comunicando com o TIBCO (este é o nome do software).
Acordamos que o TIBCO teria que simular o SEFAZ para eu não alterar a solução standard e assim os caras tiveram que desenvolver interfaces identicas as da SEFAZ.
SOmente duas coisas ficaram diferentes:
1 - Para chamar os webservices do TIBCO eu não preciso usar o certificado digital instalado no PI
2 - Os Webservices que chamo não são os da SEFAZ, mas sim os do TIBCO, porém o SOAP Action é identico.
Concluímos todo o processo de configuração e agora iniciei os testes, porém já na primeira tentativa de envio de nota encontramos um problema
O Status de Serviço já está se comunicando com a SEFAZ perfeitamente e já está retornando a informação correta até o GRC.
O problema é que quando o lote com a nota vai ser enviado na chamada call adapter da interface BATSR_nfeRetRecepcaoSoapIn_SYNC_IB , portanto, BATSR_SOAP_RCV ele dá o seguinte erro:
SAP_Code area="INTERNAL"_AE_DETAILS_GET_ERROR
Error while reading from the secure store: ERROR_U: No service user password found for Adapter Engine
Error while reading access data (URL, user, password) for the Adapter Engine
Porém no TIBCO não é necessário usuário e senha para se conectar, portanto, deixei em branco. Repetindo, o Status Service está funcionando normalmente assim.
De antemão obrigado pela ajuda

Sim sim, o erro nao tem nada a ver com o fato de ser TIBCO, é algum erro de post-installation/configuração no Adapter Engine.
Verifique no SLD, technical systems process integration (ou exchange infrastructure, depende da versão) se vc vê a entrada do tipo Adapter Engine, e se ela está com os dados consistentes.
Verifique tb se o FM SAI_AE_DETAILS_GET finaliza com sucesso, e revise se o Exchange Profile foi mantido com os dados, em particular do Adapter Engine. Verifique se a SLDCHECk tb termina com sucesso.
Outra coisa, atualize o CR Content e o CIM Model do seu SLD para o ultimo disponível (6.x) de acordo com a nota 669669
Abs,
Henrique.

WebMethods 4.6 Integration with XI 3.0

Hi,
For my project, I am trying to integrate WebMethods 4.6 with XI 3.0 as a third party system.
My installation of XI is: Netweaver 2004S PI Usage.
One step required by WebMethods is registering the SLD with the WebMethods IntegrationServer.
Registering SLD on WebMethods IntegrationServer requires a tc_sec_core.jar. However, it seems like this file is available with Java WAS 6.20 and not the newer 6.40 or 7.00.
Copying tc_sec_core.jar from an older installation still fails on some java classes not being found.
We are posting the same query on WebMethods forums as well. Any advice on how to proceed will be greatly appreciated. Thanks

Hi Khian,
Did you get the problem fixed?
We have the same problem now. Can you help?
Thanks!
Jason

How to consume a TIBCO web-service in SAP PI

Dear All,
I have a scenario to consume a webservice provided by TIBCO.
A end to end scenario is configured in TIBCO (ws-TIBCO-ws). The WSDL file ganerated from TIBCO system is provided to me to consume in SAP PI.
TIBCO generated WSDL will be in a format (Type, Service, Binding, Port, Message). For SAP system to consume a webservice, WSDL format should be (Type, Message, Binding, Port, Service). So i changed the format and imported into External Definitions in ESR and configured the SYNCHRONOUS end-to-end scenario(saop-PI-soap) in SAP PI. I have generated a wsdl from sender agreement and tested it using SOUP UI.
In SOAP UI response it throws following error.

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: .
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Also let me know whether we can consume a TIBCO generated WSDL in SAP PI or not (because first we will hit TIBCO endpoint url which in turn internally hits the target system url from TIBCO )
If this is possible, Please provide your valuable inputs
Regards
Koti Reddy

Hi Koti - The soap action is case sensitive.
What is the soap version of the wsdl?
If you try to make a request to a SOAP 1.2 webservice with a SOAP 1.1 request then you may get this error too..
to check the your webservice soap version - open the wsdl and check for the namespace
SOAP 1.1 uses namespace http://schemas.xmlsoap.org/wsdl/soap/
SOAP 1.2 uses namespace http://schemas.xmlsoap.org/wsdl/soap12/
source - http://forum.spring.io/forum/spring-projects/web-services/45083-server-did-not-recognize-the-value-of-http-header-soapaction
please share the wsdl as that may help in providing you more information.

Migration from webmethods to SAP PI 7.1

Hi All,
I need some information on migrating webmethods to PI 7.1.
We have our interfaces currently working in webmethods which call webservices in SAP.Currently legacy systems call SAP webservices through webmethods which we would like to migrate to PI 7.1.
Could I get some information on how to proceed with this?
1.Could I get the overview
2.Can I import the same structure and mappings into SAP PI?
3.Do I need to recreate the mappings or use the same from webmethods ..if they are XSLT mappings?
4.Can I use the mapping transformation done in webmethods ?
Any thoughts would be of great help
Thanks,
C

> I need some information on migrating webmethods to PI 7.1.
> We have our interfaces currently working in webmethods which call webservices in SAP.Currently legacy systems call SAP webservices through webmethods which we would like to migrate to PI 7.1.
>
> Could I get some information on how to proceed with this?
>
2 years back i worked on one migration project from WebMethods to SAP PI 7.1
> 1.Could I get the overview
> 2.Can I import the same structure and mappings into SAP PI?
> 3.Do I need to recreate the mappings or use the same from webmethods ..if they are XSLT mappings?
> 4.Can I use the mapping transformation done in webmethods ?
>
> Any thoughts would be of great help
1)Only XSLT Mapping program can be reused in PI7.1,most of the times without change, sometimes it required change when you have java functions in XSLT Mapping.
Adjust your XSLT mapping programs compatible to without using XML TOOL kit option in Operation mapping.
2) To understand the web methods flow , you should have some basic /medium level of knowledge , then you can easily understand the mapping logic implemented in Web Methods.
3) When you developing interface use Web methods for only mapping logic, donu2019t try to implement the same design what developed in Web Methods. Think PI prospective. The way web methods execute interface is differ compare to PI (execution process).
4)If any java services existing in current web method interfaces, you canu2019t use the same as java mapping program in PI,in web methods we can perform state full operation from java services in web methods. But in PI it is strictly avoided performing state full operation like retrieving the data/sending data to Data base using Java map.
5) If your client forcing you to use XSLT mappings then only use, else implement the same logic using GUI mapping in PI.
6) Connecting to SAP systems and non SAP system use Adapters in PI,it is very easy . Follow standard way of communication using PI ,donu2019t try to copy from Web METHODS.
Thanks and Regards,
Raja Sekhar

Webmethods to SAP PI

Hi All,
we have a requirement to replace/migrate the existing interfaces in web methods to SAP PI. Could you please provide me with details of how do we go about doing this implementation and what are the measure that we need to consider when we go in for this migration.
Is there a possibility of using the existing details in webmethods as such in PI, or should we completely create new interfaces in PI understanding the existing interface logic.
Also I have seen few blogs showing we need to use the webMethods XI Adapter, do we need to apply some patches when we are using it in PI 7.1
Please provide your inputs.
Regards,
Nithiyanandam

refer my blog,let us know still you need any info.
/people/rajasekhar.reddy14/blog/2010/06/16/points-to-remember-while-working-on-migration-projects-web-methods-sap-bc-to-sap-xipi
Regards,
Raj

File port query File transfer from SAP R/3 to Webmethods using Unix Script

SAP drops the files in the /sapio/ directory and triggers an unix script using File port partner destination.
Unix script will perform a secure copy of files to Webmethods server.
If in unix script, error occurs then an RFC function will be called to send an error notification to a person.
Queries
1) How is the unix script triggered using the File port partner destination ?
2) What is the unix command to invoke a report which sends the error notification mail ?
3) Does SCP command to copy files to webmethods work , if the unix script is placed in /sapio/ directory ? Or whether
any connection need to be established between SAP and Webmethods server ?

Hello,
Since you want to transfer Article Master, it should be a Retail System. So you should use Message Type ARTMAS. For fullbuild, you can use transaction WDBM and for changes, you can use WDBU. For changes, you can enable change pointers for required fields using BD64.
Thanks,
Venu

Error while using webmethod JMS provider with JNDI

Hi,
I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc.
While activated the adapter short log shows: Adapter has not provided any status information about this channel"
In the detailed log following error message is displayed: "Obtained connection factory: null#"
#1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
#1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
#1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
#1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
#1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
#1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

Hi,
Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
Regards,
Srini

XI Vs Tibco Vs Webmethods

Similar Messages

Maybe you are looking for