EP vs IBM websphere

hi all,
Can i say that ibm websphere is a enterprise portal.
pls! give me appropriate answer.
warm regards.

Hi !
IBM websphere is not only a portal :
<a href="http://www-306.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS206-076">http://www-306.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS206-076</a>
But it can provides a portal :
<a href="http://www-306.ibm.com/software/info1/websphere/index.jsp?tab=landings/portalbuzz&S_TACT=103BEW01">http://www-306.ibm.com/software/info1/websphere/index.jsp?tab=landings/portalbuzz&S_TACT=103BEW01</a>
Fabien.

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

VisualAge RPG and crystal report + IBM Websphere Studio Dveloper client

Hi friends
My doubt is with regard to VisualAge RPG an alternative of java for AS400 servers yet iam posting here
I am trying to call Crystal report using VARPG The IDE used is IBM Websphere studio developer for iseries 6.0.
In VARPG GUI based windows application i am able to add Crystal Report Viewer (CRviewer.dll) to the ACtivex control object. I have to set the Report source and activate the Activex. The control has a property named ReportSource which is of numeric type. I tried to set the report source by calling openReport methox of Craxdrt.dll. I get a error as follows
0211 Error occurred while calling program or procedure OpenReport.
Cause . . . . . : The program attempted to call program or
procedure OpenReport, but was unable to access the program or procedure. If
the name is *N, the call was a bound call by procedure pointer.
Recovery . . . : Check the error log file FVDCERRS.LOG for more
information on the cause of the error. If the call was to a local
program, then the program could not be found, or the accumulated
parameters exceeded 1024 bytes in length. If not found, either specify
the full path name or make sure the program resides in a directory
listed in the PATH environment variable. Verify that the file
extension is correct. If no extension is specified, .EXE is assumed.
Is my way of calling crystal report is correct or i have to set the report source by any other way.
Thanks in advance
Ashokans

Vamsi
You ned to specify the location of the reports in the RAS server.
Follow these steps.
1. Go to the crystal configuration manager.
2. Click Crystal Report Application Server and stop the service.
3. Click the properties button.
4. Go to the parameters tab and from the option type select Server.
5. In the report directory text box, specify the director in which the reports are located.
6. Click ok and Start the Crystal Report Application Server
thats about it

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®

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

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

Apache Tomcat vs IBM Websphere

Hi,
In our current deployment, I am using Apache Tomcat as the Java Application Server that comes bundled with Hyperion Planning 9.3.1 suite of applications. The documentation also suggests Oracle Application Server, IBM Websphere and BEA WebLogic. Currently the application stack is Hyperion Planning only, with Financial Reporting for the reporting needs.
For our current situation, we have shortlisted between using the bundled Apache Tomcat or IBM Websphere. For comparison I wanted to know how stable Apache Tomcat is in general compared to websphere? How many concurrent users can it handle? Are there any specific limitations of Apache Tomcat that I should consider? Can someone list the major pros and cons of each?
Thanks in advance
Shehzad

I agree with Jake.. Tomcat can handle much more than a few users. Whether it can handle the load for your environment may depend on your usage pattern, size of forms, etc.
We typically use Tomcat for our Dodeca product that uses the Java API to talk to Essbase. It doesn't product 'forms' but rather just transfers data via XML between the client and server. With that product, we do have one customer that is serving appx 7,000 users on a single Tomcat server. In that case, however, the usage pattern is that field users log in daily (or sometimes weekly) and run a few reports (that retrieve data via XML).
Note that Tomcat has a configuration parameter in the server.xml file to set the max number of threads that can be spawned by the process. You may want to tune that parameter if you decide to run Tomcat in production (and absolutely be sure to give it more heapsize in the java options).
Tim Tow
Applied OLAP, Inc

IBM WebSphere App.Server 3.5 StdEd + Oracle 8i for repository ?

I want to install IBM WebSphere Application Server (WAS) 3.5 Std
but I don't have a DB to hold the repository.
One of the possible DB mentionned in the install doc is ORACLE
8i but I have no experience whatsoever with this line of
products.
I would like to hear of people running such a config.
Any tips, do's and don't ?
Is it a stable, recommended configuration to start with ?
E.G.:
WAS 3.5 standard on Win2000
+ ORACLE 8i as a repository DB
+ AS400 serving corporate data
Thanks for your help,
Frederic.
PS - I know DB2 is another possibility but I would like to skip
that one for some reasons.

Matt :
I eventually chose to keep the InstantDB repository because
someone told me it would be fine for a small web application.
One thing I am wondering about though : IBM doc mentions Oracle
8i but on the Oracle site they mention 9i only so
- where do you find the 8i ?
- is the 9i fine too ?
- what edition is acceptable ? the cost for the personal/pro
etc. licences do vary quite a lot so which is the cheapest
acceptable one ?
I am still looking for that info.
Any hint ?
Thanks !

Oracle BAM 10.1.3.4 and IBM WebSphere MQ 6.0, Enterprise Link Plan does not

Hello All,
1. I have a BAM 10.1.3.4 installation and a IBM Webspehere MQ client V6.0 installed in the same server
2. Have configured JmsAdmin appropriately to have a Topic Connection Factory and a Topic Pointing to a Queue in the Server
3. Have tested the client connectivity using ivtRun and MQIVP.class, they seem to work fine connecting to the channel and the topic.
4. I have configured an EMS for IBMWebSphereMQ in BAM with the below given parameters
Name:      BPEL_TO_BAM
Owner:      AMERICAS\Jai_Mani
Created:      12/1/2009 2:07:48 AM
Last modified:      12/1/2009 9:48:03 AM
Type:      IBM WebSphere MQ
Initial Context Factory:      com.sun.jndi.fscontext.RefFSContextFactory.
JNDI Service Provider URL:      file:/C:/JNDI-BOSS-DAO.
TopicConnectionFactory Name:      ivtTCF.
Topic Name:      ivtT.
JMS Message Type:      TextMessage.
Durable Subscriber Name (Optional):      .
Message Selector (Optional):      .
Client ID (Optional):      .
Name      Flow name      Type      Max size      Formatting
rawData.      rawData.      String      40000      (none).
5. I have a subscribe plan configured in to enterprise Link which has a EMSReceiever and a grid to display the messages
6. I have the "run forever" flag checked in the Receiver and go a head and post a message in the Queue configured in the server.
7. The plan does not display any messages in the grid.
All configuration on the MQ Server and Client side are proper but BAM EL Plan is not displaying the data in the grid.
Have also had turned on DEBUG on the servers and restarted BAM, they don't seem to throw any errors.
Kindly advice, what could be wrong in the Plan or EMS configuration which is causing this.
Thanks & regards,
Jai.

Is this working for you? What errors do you get in the logs (bam, EL)?

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.

SQL Server 2000 with IBM websphere 4.0

Hi,
I need to migrate existing Oracle DB to SQL server 2000.
Let me know how does SQL server 2000 connect with and talk to IBM websphere 4.0.
If you can also send me a sample architecture diagram.
Thanks
Alpana

Hello,
It seems you need to install i-net OPTA in IBM WebSphere 4.o to be able to connect to a SQL Server
2000 instance. Please read the following article for more information:
https://www.inetsoftware.de/products/jdbc-driver/ms-sql/configurations/websphere4
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

IBM WebSphere Community Edition

Hi, Has anyone tried IBM WebSphere Community Edition with any Hyperion product? WebSphere CE is based on Apache's Geronimo J2EE server. Any good / bad experience? Regards, Gerd

step 1: find the manual
step 2: read the manual
step 3: understand the manual
step 4: follow the instructions found in the manual
problem solved (though with IBM manuals I will have to practice caution there, they're not always good but mostly the bad parts are the obscure ones).

IBM WebSphere Connection

Hello.
I've been trying to add a server to the runtime tab of the Java Studio Enterprise 8. The location of the IBM Websphere installation directory is in another pc(our server pc). when i try to connect i would either get an null pointer exception or i cannot deploy my web applications on the server.
can anyone help me with this. thanks.

What have you specified for your installation directory?
As I remember it still needs the local installation of WebSphere server to access the remote server.

EP vs IBM websphere

Similar Messages

Maybe you are looking for