Accesing IBM WebSphere through SAP EP

Hi all
The scenario is that I have an application runnig in IBM Websphere Commerce Server.I need to access the application through my SAP EP 6.0
Could any one throw some light on how to go about it.
Thanks in advance,
Jayanthi

Hi Jayanthi,
i don't do it this way up to now, but i think it is a good solution:
There is a standard named WSRP (Web Service for Remote Portlets). With this you can publish Portlets from the Websphere Portal to the SAP Portal. I see in the Global Portal Scenario that SAP Portal can consume wsrp portlets, but this is enough for your scenario.
Best regards,
Patrick
my Website:
http://www.mindsquare.de

Similar Messages

How to Set Up SSO Between IBM WebSphere and SAP EP Using JAAS

Hi
I have read the article on SDN called "How to Set Up SSO Between IBM WebSphere and SAP EP Using JAAS", which is also the name of my posting.
The reason why I post this is that I've tried to follow the links in the PDF to get the file WebsphereEpSsoLib.zip but I get an error 403, which tells me that the file is not there.
Does anybody know where this file went or can somebody tell me an alternative place to get this file?
Jacob

Please open the associated whitepaper, and you can find the download link to the .ZIP file on page 4.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/ibm/how to set up single sign-on between an ibm websphere portal and the sap enterprise portal using jaas.pdf
Hope that works!
Elise

Difference Between IBM Websphere portal SAP Portal

Hi Everyone,
   Could anybody tell me whats the difference between IBM Websphere Portal and SAP Portal?
   And how IBM Websphere portal can be implemented in Netweaver Portal?
Regards
Sireesha.

Hi Michal,
   I Know that its both are different products.
   Actually my question is What can be done in the SAP portal and in the Websphere portal?
   How the organization would be benifited by implementing which portal ?
i.e, do's and don's in the both the portals.
Regards
Sireesha.

Posting of bank detail through IDOC from IBM Websphere

Hi
I am facing a problem during the seletion of the Basic IDOC type in the websphere .I trying to get the bankdetails of the business partner , for that I have selected the Basic Idoc type in the configaration of the IBM websphere BUPA_C_BANKDETAIL_ADD01.
But after the seletion when we try to connect its showing error like "Segment couldnot be read for the release 700"
I have checked with the release of the SAP also , it is 700 only .
Can anyone please help me out in this matter , its really urjent .
Thanks & Regards
Debasri Sarkar

Hi,
Have read the documentation for bapi BAPI_ACC_DOCUMENT_POST and check for documentation import parameter EXTENSIONIN 2
Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIO
Description
This enhancement structure can be used to transfer additional fields.
There are four fields available for each data record (VALUEPART1 - 4), which each contain 240 characters. A defined ABAP dictionary structure can be transferred in the field STRUCTURE, on the basis of which the field contents are read.
The accounting document can be supplemented and changed in an implemented BAdI ( ACC_DOCUMENT) before the active accounting component is called.
The class CL_EXM_IM_ACC_DOCUMENT is available as example implementation. Here, for each data record of the parameter that is transferred the ABAP dictionary structure is checked and the content of the fields VALUEPART1 to -4 is set in the structure. If the structure that is transferred contains a field POSNR, the associated lines of the accounting document are updated using the contents of the enhancement.
a®

Integrating SAP CRM with IBM Websphere Portal

Hi,
Is it possible integrate SAP CRM with IBM Websphere Portal??
if possible please share the knowledge you have..
Thanks in advance..
Naresh

P L E A S E D O N O T C R O S S P O S T I N D I F F E R E N T F O R U M S

Connecting different versions of MQ Ibm Websphere using PI 7.1

Hi Experts,
We are having one mq server which is installed on a third party system which we are currenlty using without having any issues.
the mq series is ibm websphere version 6.
we have these following jar files installed on pi.
<jars>
<jar-name>lib/com.sap.aii.adapter.lib_api.jar</jar-name>
<jar-name>lib/ojdbc14.jar</jar-name>
<jar-name>lib/client.jar</jar-name>
<jar-name>lib/msbase.jar</jar-name>
<jar-name>lib/mssqlserver.jar</jar-name>
<jar-name>lib/msutil.jar</jar-name>
<jar-name>lib/com.ibm.mq.jar</jar-name>
<jar-name>lib/com.ibm.mqjms.jar</jar-name>
<jar-name>lib/connector.jar</jar-name>
<jar-name>lib/CL3Export.jar</jar-name>
<jar-name>lib/CL3Nonexport.jar</jar-name>
<jar-name>lib/dhbcore.jar</jar-name>
<jar-name>lib/rmm.jar</jar-name>
</jars>
we are able to connect to this system sucessfully using jms.
the issue we are facing now is we have now another new mq server installed which we want to use
this is version ibm websphere 5.3.
we have gone through sap notes and found that these jar files need to be in place for 5.3
MQSeries 5.3
com.ibm.mq.jar
com.ibm.mqbind.jar
com.ibm.mqjms.jar
connector.jar (this file can also be retrieved from the SAP J2EE server directory)
by comparing with the jar files we currenlty have installed
this jar file is missing com.ibm.mqbind.jar for 5.3
we are unable to connect to this new mq server and facing the issues.(reciever jms)
the message in rwb is
Error creating JMS connection. JMS provider gave error message as MQJMS2005: failed to create MQQueueManager for 'Servername:Queuemangername' MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009, and error code as MQJMS2005.
we have gone through notes 1086303 and found that it might be due to wrong queuemanager name.
our mq team is saying that they have configured everything perfectly.
what we have is now 2 queries:
1. is this error caused due to the mqbind jar file missing.if so than we can tell our nw team to install that jar files.is it necessary as we have already jar files for version 6? will version 6 jar files be compatible if we install these new jar file which is missing as we dont want to mess the existing scenarios?
2. is there any other config we are missing on pi side so that we are 100 percent sure its not the error on pi side and some config is missing on jms side.
please advice.
many thanks.
regards
j

Hi Jyoti,
You say to choose between the possibility of a missing jar and other of a Queue manager. I think first and foremost get the missing jar file installed and secondly , try the following suggestions.
1) It appears that the MQ JMS server is refusing connections from the MQ JMS c=
lient. I suggest looking up "MQJMS2005" in the IBM documentation and also =
checking if the IBM specific connection string '147.149.178.44:BT.QM.IVASCT=
G' is correct.
2) I guess so because 2009 indicates a communication problem. It appears that the foreign JMS provider is restricting the number of conne=
ctions that can be made to it. I'd check the license restrictions/configura=
tion of the foreign JMS provider and ensure it allows the required number o=
f concurrent connections. The closure reason code 2009 should indicate what=
the problem is.
Regards
joel

Standard Services in IBM Websphere Portal

Hi,
We have a requirement wherein we need to have E recruitmtnt applications in IBM Websphere Portal.I have gone through few documents and i am not clear how to move forward.Could anyone suggest some best way to achieve this.
1.If we do Integration between SAP Portal and IBM websphere, can we get E Recruitment applications in Websphere Portal.If this is the way what might be the issues we are gong to face moving forward.(As suggested through SAP iView Integration Portlet i guess)
2.As E recruitment applications we are using is completely based on ABAP Webdynpro,is it possible to display these applications directly from ECC to IBM Websphere Portal.(As every WDA is associated with an URL, can we make use of this URL in Websphere)
3.Again E recruitment Portal content needs SAP Portal because some of the functions of the roles ( like Recruiter iview , Manager Iview etc are delivered as Portal Content).Can we achieve all these without SAP Portal.
I would be great if someone suggest me the right way.
Regards,
Anil

Closing the thread as no one replied

WebDynpro and IBM WebSphere

Hi everyone,
I've got the following scenario. We have a bunch of WD4A applications that we'd like to integrate with IBM WebSphere.
If we deploy them through portal, there won't be any WSRP support from the portal side and integration cannot be achieved.
What are the options then?
If we integrate them as simple iFrame, what happens to the theme? And what if we have multiple WD views interacting one another? Is the deployment of SAP Portal best practice?
Thank you.
Cheers

That's my point too.
However I'd like to know whether there's some official docs from SAP stating what the best practice would be.
In fact, if SAP portal isn't deployed, the only way integration can be done is via iFrame.
- What happens to the theme then? I think that there will be a discrepancy between SAP's and IBM's themes unless SAP's theme is tweaked manually to look like IBM's.
- What happens to inter-communicating WDynpros? I mean if we have two (or more) WebDynpro apps that need to exchange data and no SAP portal is in place?
- On the other hand, if we deploy SAP Portal and want to integrate SAP Portal with IBM WebSphere, I guess we'll be having tough time later on, because BSPs, WebDynpros, Pages, etc. don't support WSRP and cannot be consumed by WebSphere. Can anybody confirm this? Has anyone ever tried this scenario?
Thank you.

RFC in IBM Websphere server

Hi all,
I want to run a Java application that calls SAP RFC in an IBM Websphere server. Right now its working fine in Tomcat server.(I have installed JCO for Tomacat).
What all are the steps (intallations and configurations) I need to do in Websphere server.
I came across terms like SAPODA and JCO. Is SAP ODA neccessary??? or JCO installation alone will work?
Thanks in advance
George

u need only sapjco.jar file and dll files ..............
u put sapjco.jar file in ibm/sdp/6.0/portal/eclipse/plugins/eis.webtools.sap.6.0_0
here u copy that file.....
go to dynamic webproject, right click>properties>java build path-->add external
jars>add that sapjco.jar file and click okfinish..
now u write ur program..........
it works fine...........

JMS Receiver Adapter - com.ibm.websphere.naming.WsnInitialContextFactory

Hello experts,
I am trying to configure JMS Adapter to Access Websphere Application Server via JNDI. The configuration is as follow:
Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Connection Factory: jms/messageQueueCF
Server URL: iiop://ammtnode.iubs.intra:2809/
Queue Name: jms/EXT_INPUT_QUEUE
I deployed all required jar files but Iu2019m still unable to connect to WAS because adapter cannot initialize ORB:
javax.naming.NamingException: Failed to initialize the ORB
I wrote a small java class to check where the problem was:
============================================================================
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://ammtnode.iubs.intra:2809/");
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
Context jndiContext = null;
try {
jndiContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("jms/messageQueueCF");
Connection qConn = connectionFactory.createConnection();
Session qSession = qConn.createSession(false,Session.AUTO_ACKNOWLEDGE);
Queue q = (Queue) jndiContext.lookup("jms/EXT_INPUT_QUEUE");
MessageProducer producer = qSession.createProducer(q);
TextMessage message = qSession.createTextMessage();
message.setText(text);
producer.send(message);
producer.close();
qSession.close();
qConn.close();
} catch (Exception e) {
 e.printStackTrace();
============================================================================
I got the same error until I wrote this line:
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
And everything worked fine. Now I want to do the same in my JMS Receiver adapter but I donu2019t know how to introduce this line in the Initial Context Environment. I tried as JMS additional parameters and additional properties as well. However, nothing worked. Does anybody know what Iu2019m doing wrong?
Thank you in advance!

Here I post the entire error:
0#0#Warning##Java###Catching #1#com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection fact
oryjms/messageQueueCF, for profile: ConnectionProfile of channel: CC_I002_AMM_JmsReceiveron node: 5949650 having object id: 0
360697bc61b3666aba07a2708ca095a: javax.naming.NamingException: Failed to initialize the ORB
 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
 at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
 at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
 at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
 at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
 at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
 at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
 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:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class
com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:libra
ry:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
 at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
 at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
 at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
 at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
 at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
 at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
 ... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
 at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
 at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
 at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
 at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
 at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
 at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
 ... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
 at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
 at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
 at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
 at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
 at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
 at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
 ... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
 at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
 at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
 at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
 at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
 at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
 at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
 ... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
 at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
 at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
 at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
 at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
 at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
 at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
 at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
 at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
 at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
 at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
 at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
 at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
 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:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
 at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
 at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
 at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
 at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
 at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
 at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
 ... 19 more

JMS adapter fails to open IBM WebSphere MQ Manager V6 Remote Queue

Hello,
We are trying to connect to a Remote Queue with the SAP PI 7.0 SP9 JMS adapter to IBM WebSphere MQ V6 on Linux SLES9 x86_64.
We did deployed the JMS-adapter with the V6 native libaries on SAP PI.
In the Communication Channel we use the Adapter Type = JMS, Sender, Transport Protocol = WebSphereMQ(non-JMS).
The MQ Queue Manager is on the same server as SAP PI so we use localhost, Server Port, Queue Manager Name, Channel Name and JMS Queue Name
The <sid>adm user is a member of the mqm group.
When I check the RWB I see this fault message:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2008: failed to open MQ Queue at ...
and also
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2045
When we lookup the reason 2045 we get this explaination on MQ:
MQRC_OPTION_NOT_VALID_FOR_TYPE
We also have a type = Receiver Communication Channel on the same MQ Queue Manager that one is working fine.
Please advise!
Best regards,
Mike Laanen

Mike,
check whether the Queues are created and activated if it done. then check whether you have authorization for those queues.
Regards
Sreeram.G.Reddy

Calling an Abap Web Service from IBM WebSphere with a MYSAPSSO2 Cookie

Hello,
I have the following problem :
I have to develop a proof of concept between IBM Web Sphere 5.1 and SAP AS JAVA 7.0.
I have created an IBM sevlet in Web Sphere, I use a specific redirect from an SAP AS Java to call it, this way I can have a SAP Logon Ticket, and I manage to call an ABAP module function with JCO with SSO.
Scenario 1 : browser + authentication --> AS Java redirect servlet MYSAPSSO2 cookie -> IBM WebSphere servlet JCO -> Abap module function (ECC5)
This scenario works fine.
I have to do the same scenario with a Web Service and I don't know what to do.
I try to use jax-rpc handlers but I don't know how to pass my cookie from my servlet to my handler.
Scenario 2 : browser + authentication --> AS Java redirect servlet MYSAPSSO2 cookie -> IBM WebSphere servlet JCO -> Abap Web Service (ECC5)
Has someone already done that ?
Regards, Julien.

Julien,
Why are you using 5.1....go for 6.0 and its cake walk, i have integrated WebSphere 6.0 with R/3 uysing xi.....in a week.
Scenario changed to:--
Browser+ authentication --> WebSphere AS servlet request --> XI --> RFC/bapi --> abap webService
Hope that helps
Regards
Ravi

XI to IBM Websphere Default JMS Provider with JNDI

Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
 SAP XI: 7.0 SP8 , Sun JDK 1.4.2
 IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
 JMS Providers: Default Messaging Provider
 Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
 Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
Variant 1.
 Adapter type: JMS
 Type: Receiver
 JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
 JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
 JNDI Lookup Name of JMS Queue: jms/Queue
 Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
 JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
 As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
 "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
Variant 2
 The same settings as in Variant 1 above, were used and additionally the following settings were done:
 - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
 - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
 - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
 As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
 "No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

SSL connectivity for IBM WebSphere MQ to integrate with XI

Any information of SSL connectivity for IBM WebSphere MQ to integrate with XI???

Ravi,
Have you gone thru this SAP Note - 912314 - SSL support for IBM Websphere MQ/ MQ Series
raj.
[Give Support|http://www.sapfeedingknowledge.com/show_your_support|I'm Working here for Global cause]

JSP on IBM WebSphere Application Server 3.5.4

Hi, Could pls. someone suggest what is required to be done to get a JSP working on IBM WebSphere Application Server.
This is what I have tried so far:
One of the directories on the app server is
C:\WebServer\AppServer\hosts\default_host\examples\web
When I place a JSP in the above path, it works fine (http://localhost/webapp/examples/xyz.jsp in the browser).
Question:
Where is webapp (as it appears in the URL) defined?
Then, I go on to create new directories as follows
C:\WebServer\AppServer\hosts\default_host\MyApps
C:\WebServer\AppServer\hosts\default_host\MyApps\web
Place a working JSP in C:\WebServer\AppServer\hosts\default_host\MyApps\web. And when I enter http://localhost/webapp/MyApps/xyz.jsp or http://localhost/MyApps/xyz.jsp in the browser, the JSP can't be located.
What is required to be done (from mapping point of view) and where? Does anything pertaining to JSP need to be defined on the HTTP Web Server (not for JSP's I think). Where should I put the JSP file so that everything for the application could be grouped together and it will work as well.
I have gone through other postings on this issue on this forum but they have been of little help.
Any thoughts on how to get this working.
Thanks

I use IBM Visual Age 3.5 & 4 which contains a scaled down vesion of Websphere for running servlet and JSPs. I am very familiar with the intricacies of running web apps in in this scaled down environment. What I'm about to tell you may or may not apply to WAS but it should help you.
You can't simply add a directory under default_hosts and expect a new web app to appear. Websphere only recognizes web apps that are set up properly in the servlet_engine file. Each server has it on servlet_engine file located in the properties directory. For the default server, the file is named default.servlet_engine. In that file you must add a new <webspher-webgroup> element as a child element to <websphere-servelet-host name="default_host">. I added a web app to my server and it looks like this.
<websphere-webgroup name="second_app">
 <description>The second app</description>
 <document-root>$approot$/web</document-root>
 <classpath>$approot$/servlets$psep$$server_root$/servlets</classpath>
 <root-uri>/</root-uri>
 <auto-reload enabled="true" polling-interval="3000"/>
 <shared-context>false</shared-context>
</websphere-webgroup>I can't remember if it automatically creates the directory structure for you now or not, but at any rate, this web app will be stored in c:\WebServer\AppServer\hosts\default_host\second_app with the enclosed web direrectory as your location for JSPs.
One more thing to mention. For every web-app you create, there is a descriptor file similiar to the web.xml deployment descriptor you see in /WEB-INF for the servlet 2.2+ spec. In my case the file is name second_app/servlets/second_app.web_app. In the descriptor you would probably want to configure some settings specific to your web app such as servet registration, init parameters and which version of the jsp compiler to use.
Since IBM came out with WAS 3.5 before the Servlet 2.2 spec went mainstream for Servlet Containers, WAS's configuration is quite unconventional. But, I found that the documentation that comes with WAS explained all these configuration quirks quite well.
Hope this helps
Steve

Accesing IBM WebSphere through SAP EP

Similar Messages

Maybe you are looking for