Integrate with websphere message broker

we plan to integrate Websphere Message Broker with E-business. We are looking at the different options like OMG, JMS node using OID , JMS node using weblogic app server etc.
Is there any difference between using OID and weblogic app server, other than from the configuration point.
is there is any comparsion between the different options available?

Hi;
Similar issue has been answered at -Steven Chan blog*
From blog:
Hello, RM,
I have not seen any Oracle-produced documentation along those lines. I don't think there are any Oracle teams that are investing in producing documentation for IBM WebSphere.
I would suggest contacting IBM to see whether they have produced any WebSphere-specific documentation.
Regards,
Steven
Referance:
http://blogs.oracle.com/stevenChan/entry/ebusiness_suite_release_1211_now_available
Ps: You can rise SR for your issue also
Regard
Helios

Similar Messages

Itegration with Websphere Message Broker and Customer Master IDOC

Hello All. I am new to this forum. I have a couple of questions.
What I am trying to do: I have to interface to SAP with Websphere Message Broker which has inbuilt nodes to interface with SAP using BAPI or ALE to send Customer Master Record (create/update/delete)
The questions I have:
1/ Has anyone done this? What did you use BAPI or ALE?
2/ When a Customer Master IDOC is sent to SAP, if successful, a return code is sent back by SAP. This indicates that SAP has received the IDOC successfully. However, our requirement is that we have to know whether the IDOC was successfully posted within SAP. I am of the opinion that this is manual task within SAP and it should not be the function of the middleware layer as its responsibility is only to successfully deliver the IDOC's. I would welcome opinions on this issue. Please let me know If there is a way to determine if the IDOC has been successfully posted in SAP.
3/ Is there anywhere where I can get an XML representation of the Customer Master Record. I want to see the structure and the available fields. How can I get this info from SAP?
Thank you

Hi;
Similar issue has been answered at -Steven Chan blog*
From blog:
Hello, RM,
I have not seen any Oracle-produced documentation along those lines. I don't think there are any Oracle teams that are investing in producing documentation for IBM WebSphere.
I would suggest contacting IBM to see whether they have produced any WebSphere-specific documentation.
Regards,
Steven
Referance:
http://blogs.oracle.com/stevenChan/entry/ebusiness_suite_release_1211_now_available
Ps: You can rise SR for your issue also
Regard
Helios

Connecting to Websphere Message broker from SAP

Hi
Iam working on Websphere Message Broker(WMB).
We have to integrate SAP system and WMB, to receive messages from SAP and forward them to other resource; taking the message from the resource and sending it back to SAP, along with the message status like success or failure.
We are using SAPAdapter which comes with WMB toolkit.
SAP will send messages in Batch.
I wanted to know the message format SAP send messages in batch mode. How to send message back to SAP from WMB? As far as i know if we use IDoc then only we can send message back to SAP, but if it is batch process, then how to do in this case?
People who worked on the integration between SAP and WMB, please throw some light on this issue.
I have gone thorugh many websites reading about ABAP, BAPI, ALE, RFC.....
It will be very helpful if someone can answer my questions.

Hi Nina,
first of all I guess there is no standard answer, to what kind of format / structure SAP uses and sends to WMB. It really depends on the individual case. Also important to know, which version of WMB you are using, v6.1 has significant changes regarding SAP adapter.
You may want to read some general WMB SAP connectivity information provided here:
     http://www.redbooks.ibm.com/abstracts/sg247137.html?Open (WMB Basics)
     http://www.redbooks.ibm.com/abstracts/sg247220.html?Open (WMB Middleware)
     http://www.redbooks.ibm.com/abstracts/sg246354.html?Open (WMB & SAP older)
regards
Marco

Trying to integrate with User Messaging Service adapter in SOA suite.Can it be possible through an JMS interface.

Trying to integrate with User Messaging Service adapter in SOA suite. Can it be possible through an JMS interface.
I have an JMS backend integrated to Oracle B2B. Is it possible to send an email protocol message using JMS interface to B2B where User messaging Service has been implemented. The adapters required for UMS have been deployed and the sdpmessaging jar files also have been added to the classpath. The only problem i face is i dont have an BPEL system to integrate where as in the forums it has been mentioned how to post a message using BPEL.
Please let me know if there is a way to integrate the adapter with JMS interface.
Thanks in advance
Deepak

If I remember correct, to use JCA adapter with SOA stack requires that adapter implement some Oracle API.
The Adapter SDK is a light-weight tool kit that enables rapid implementation and deployment --- http://www.oracle.com/technology/products/integration/adapters/pdf/DS_OracleASAdapter.pdf
http://download.oracle.com/docs/cd/B16981_04/current/acrobat/cct115dg.pdf
Mostly you will have to wrap your jca adapter to make it available in SOA suite/stack.
Other option is that you adapter provider would have given CCI interface or some custom interface which can be used for invoking adapter end-points.
Manoj

Will Flex 2 integrate with WebSphere Portal Server

I have a few questions in trying to argue the case for Flex 2
to a very large client:
Will Flex 2 integrate with IBM WebSphere Portal Server ?
Will Flex 2 integrate with WebSphere if not with Portal
Server ?
Does Flex comply to the JSR168 Portlet specification ?

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=wsrp_1 .html
http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=wsrp_2 .html
http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=wsrp_3 .html

Compare PI 7.1 with IBM Message Broker (WBI)

Hi,
I need some help on understanding the advantages and disadvantages of using PI 7.1 over Message Broker. (MB)
I would like to a kind of comparative study for both the produts.
Could any one help me to understand the two system in terms of
a. Scalability
b. Performance
c. Relability
d. Mantanability
f. System Management / Monitoring
Thanks & Regards,
Ashutosh Sharma

this thread deals with MB:
Re: Message Broker Technology
this thread deals with PI:
Demand for PI 7.1
MB:
http://help.sap.com/saphelpnw04s/helpdata/en/ac/56de4244782878e10000000a155106/frameset.htm
PI:
http://help.sap.com/saphelpnw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/frameset.htm

Error: The Message Broker is not initialized

In first step, I had created a domain with PointBase Pools. I have realized a small process with a Message Broker. Cool, it works.
Second, I had created a domain with Oracle Pool and like the first step, I had realized a small application.
With Oracle Pool, I have just the error message : "<The Message Broker is not initialized>"
Any ideas ? With the wizard, I have tested pools and created WLI tables.
I work with WLI SP4 and Oracle 9i.
Thx for your help !!

I resolved my problem.
In fact, When I have created a new domain with the wizard, I defined two server : one for console and wli and an other for ejb session witch is called by WLI EJB Control.
For a another test, I have created a new domain with a stand alone server.
After that, I add the server, pool and datasource with console admin and it works !! I have not the problem with message brocker.
I think my problem come from the wizard definition of a server who is not use by wli.

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sending data to Message borker.(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to save file in SAP fold

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

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]

Integration with Websphere 5.0 (EJB 2.0) problems

Hello all,
Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
Websphere 5.0 (using EJB 2.0).
I have been basically binding a PersistenceManagerFactory into JNDI via
start-up servlet, however got the exception bellow when I tried to create
PersistenceManagerFactory (in setSessionContext of the EJB).
<i>JDOFatalInternalException: Could not perform automatic lookup of EJB
container's javax.transaction.TransactionManager implementation. Please ensure
that you are running the application from within an <b>EJB 1.1</b> compliant
EJB container, and then set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
value to obtain the TransactionManager.</i>
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
5.0?
Thank you,
Petr

Petr-
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
Websphere. However, it should be noted that it is not as rigorously
tested internally at SolarMetric as some other application servers (E.g.,
JBoss and WebLogic). In short, integration is known to work, but it
might be a little more rough around the edges than for other application
servers (as shown in our misspelling of Websphere's TransactionManager
implementation name).
How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
javax.jdo.option.ConnectionFactoryName property (see
http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
This is often more appropriate for applications server usage, since it
allows you to configure pooling and other information from within the
application server's centralized configuration.
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
configuration we use for testing with IBM's drivers is:
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
They shouldn't behave differently (I am guessing that the app driver is
a type 2 driver or something), but it might be worth a shot to try using
the net driver. If this fixes the problem, please let us know, because
it will indicate that Kodo has a deficiency with one of IBM's drivers
that we should look into resolving.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
PM and start persistence operations. Note that you should also be able
to deploy Kodo as a Resource Adapter (which allows Kodo configuration
through the centralized Websphere configuration interface). However, I
doubt this is part of the issue.
So, in short, I recommend trying the following things:
1. Using the ConnectionFactoryName to use the DataSource defined for the
appserver, on the off chance this will fix it.
2. Using the net driver instead of the app driver.
3. Seeing if it will work with javax.jdo.option.Optimistic set to false
If none of these work, please let us know, and we will continue to
investigate other possible solutions.
In article <[email protected]>, Petr Bulanek wrote:
Hello Marc,
Very good guess. Pretty much the same code worked well without App server.
In that case, there obviously was no magic related to
TransactionManagerFactory initialization (see bellow).
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?
How do I tell Kodo to use existing Datasource managed by app server?
Here is the basic configuration (URL, class, etc):
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snet
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.
The new EESimpleConfiguration(true) construct seems to (by default) read
the kodo.properties file that is part of the project.
EEConfiguration conf = new EESimpleConfiguration(true);
conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
EEPersistenceManagerFactory pmf =
                    new EEPersistenceManagerFactory(conf);
InitialContext ic = new InitialContext();
ic.rebind(\"KodoPMF\", pmf);
Thank you,
Petr
Marc Prud\'hommeaux wrote:
Petr-
It looks like DB2 doesn\'t like our attempt to close the connection
without a rollback or commit. This is odd, since we have never
seen this happen in our stand-alone DB2 tests. Can you let us know
the connection details (driver, connectionURL, etc)?
In the meantime, one possible workaround may be to turn off
optimistic transactions (since this will cause the PM to
only use a single Connection); can you try to specify:
javax.jdo.option.Optimistic=false
Also, have you tried to run this code in a non-managed environment
(e.g., outside the application server)? I would be interested
to know if it is related to running within an appserver.
In article <[email protected]>, Petr Bulanek wrote:
Hi Abe,
Thank you for a speedo reply. You guys really are on the ball!!!
As you suggested, the
\\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
did the job (for others, please note that the proper package name should
contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
Unfortunately, I got another problem. When running a method containing
query (code bellow),
I get SQLException complaining about \\\'Invalid transaction state\\\'.
The method that executes the query is a stateless transactional Session
bean.
Thank you for your help,
Petr
--------------------------- DB2 - transaction state description
CLI0116E Invalid transaction state.
Explanation: There was a transaction in progress when SQLDisconnect was
called.
User Response: Call SQLTransact before calling SQLDisconnect.
--------------------------- Exception ------------------------------------
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
PARENTX.JDOCLASSX FROM PARENTX
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] executing statement <369367952>: [reused=1;params={}]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close:
com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close connection
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
exception when closing connection
[2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
Invalid transaction state. SQLSTATE=25000
atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
--------------------------- Failing code sample
try {
               PersistenceManager pm = factory.getPersistenceManager();
               Extent ex = pm.getExtent(Parent.class, false);
               Query q = pm.newQuery(ex, \\\"name==parName\\\");
               q.declareParameters(\\\"String parName\\\");
               Collection col = (Collection) q.execute(\\\"James\\\");
               Iterator iter = col.iterator();
               Parent pp;
               Collection ch;
               while (iter.hasNext()) {
                    pp = (Parent) iter.next();
                    System.out.println(pp);
                    ch = pp.getChildren();
                    Iterator it= ch.iterator();
                    while (it.hasNext()) {
                         System.out.println(it.next());
               q.closeAll();
               pm.close();
          } catch (Exception e) {
               System.out.println(e);
               throw new EJBException(e);
Abe White wrote:
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
EJB 2.0 is also supported. Sorry for the confusing error message.
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
WSAD
5.0?
Try these settings:
com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
     com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
     TransactionManagerMethod=\\\\
     com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

File to file with out message mapping and using variable substitution

Hi,
Can any one send me a scenario where we can have file to file scenario with out message mapping and where i can use variable substitution.
As of now i am using integrate configurations where i cant use variable substitution as the message does not reflect in integration engine. I need to populate time stamp between <filename><timestamp>.txt.pgp
I am as of now using configuration scenario.
The time stamp always writes before the last file extension.
Let me know your thoughts?
Thanks,
Chandra.

Hi Chandra,
u can use the Variable substitution even without IR contents also(Mapping....).
in the receiver communication channel just specify the path u want to access for a value...
eg: filename payload:mt_name,1,records,1,name,1
and in th file name give it as %filename%.txt... or vt ever ur requirement
Babu

Problem with Send using JMS Adapter with Websphere MQ

Hi,
We have two scenarios using JMS Adapter with MQ:
1. File->PI->MQ
This works fine and drop the file in MQ correctly.
2. MQ->PI->File
This gives an error reading from the queue: (see highlighted in the log below). It correctly connects to the queue name. But it fails with the message "Could not begin a AF transaction".
Our PI version is 7.0 SP 13
Websphere MQ Version 6.0.
Any idea what could be wrong?
Cluster Node Administration Information Availability Times
Cluster Node Details for Channel CC_JMS_MQ_Sender
Short Log
In the Last 4 Hours Server 0 15_92786
_Sucessfully connected to destination 'queue:///MMPP.PLM.FGH41? CCSID=37&targetClient=1'_
Line 1 / 1
Processing Details for Cluster Node Server 0 15_92786
Type
Time Stamp
Message ID
Explanation
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d Error while processing message '2e6206f0-7925-11dd-bc02-0003bae50b4d'; _detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ..._
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d XI message ID corresponding to JMS message with ID 'ID:414d512071736431202020202020202047d9462024028b02' will be created as a new GUID with value '2e6206f0-7925-11dd-bc02-0003bae50b4d'
Amith Dharmasiri

Checked the drivers installed in :
/usr/sap/<SID>/DVEBMGS<SYSNO>
/j2ee/cluster/server0/bin/ext/com.sap
.aii.af.jmsproviderlib
They are available and properly added to aii_af_jmsproviderlib.sda.
The drivers are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
These were installed per OSS note 747601.
Any other suggestions, why retrieving from MQ doesn't work?

Integrate with BEA Portal and Lotus Domino R5.0.12

Deal all:
I got a problem when I integrate with BEA Portal and Lotus Domino R5.0.12.
my environment is below:
- Domain Server :
Lotus Domino Server R5.0.12
BEA Personal Messaging API 4.3
(test successful on local host)
- Application Server:
BEA Weblogic 8.15
BEA Groupware portlets 2.5
I got connection successful message when I using "Domino Service Connection"
but I got "CZ: VERSION CONFLICT" error message when I add a new account by
Compoze_Groupware-Edit Account user interface.
Have anybody met the error message before... and know how to sovle the problem..
I appreciated any suggest or comment~~~
detail error message is below:
portlets.compoze.groupware.exception.ConnectionException: CZ: VERSION CONFLICT at portlets.compoze.groupware.controls.provider.SessionControlImpl.createSession(SessionControlImpl.jcs:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:381) at $Proxy19.createSession(Unknown Source) at portlets.compoze.groupware.controls.provider.GroupwareProviderControlImpl.updateAccount(GroupwareProviderControlImpl.jcs:4825) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:249) at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:85) at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224) at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:109) at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:207) at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54) at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:168) at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:46) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161) at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315) at $Proxy11.updateAccount(Unknown Source) at portlets.compoze.content.options.accounts.editAccount.editAccountController.saveChangesAccountAction(editAccountController.jpf:534) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1512) at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1447) at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:778) at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211) at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:608) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1504) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:674) at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527) at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1734) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1754) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:561) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:121) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:150) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:109) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:224) at com.bea.netuix.nf.ControlLifecycle$3.visit(ControlLifecycle.java:171) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:355) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:126) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:173) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:333) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:196) at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:772) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:150) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Hi,
The reason why you are seeing this exception is because there is a mismatch between the version of the WLPM API used by the portlets, with the version of the service that you have installed on you Domino server.
To explain a little, there are two sides to the API that is used to communicate with Lotus Domino:
1) the Java API side (used by the portlets that you have installed in the portal)
2) the Domino Service side (installed as a DSAPI filter in the HTTP task of a Domino Server)
Each Java API jar and Domino Service Executable are branded with a version number, which in your case does not match because the portlets came with one version of the Java API, and you have installed a non-matching version of the service on the Domino Service side (you probably extracted the executable for the service installation from the "BEA Personal Messaging API 4.3" bundle or installer).
The solution for this is to:
1) uninstall the Domino Service that you have plugged into the domino service
2) extract the Domino Service installer which was included with the portlet bundle. This is located in the "Program Files\compoze\groupware_portlets_bea-2.5\8.1\service\domino" directory if you ran the portlet installer, or in the "groupware_portlets_bea81-noinstall-25\groupware_portlets_bea-2.5\8.1\service\domino" directory if you used the "no-install" zip file.
As a tip, to quickly check whether the versions of the service and Java APIâ€™s that you are using are matching, perform the following steps:
1) hit the domino server with the following URL and notice the "service version": http://domino_service_url:http_port/compoze.czdo. This should be something like "Service Version: 3.6.102"
2)in your portal application (or in the portlet install bundle), open the harmony_portlets.jar file with winzip, then find the "compoze_products_information.properties" file. In this file, notice the "product.domino" version (e.g. product.domino = 3.6.102)
3) the two versions you have inspected must match in order for the connection between the portlet and service to succeed.
If you have verified that the "service" version and "java API" version (located in %portal_app_dir%/APP-INF/lib/harmony_portlets.jar, and you are still getting the exception, it is likely that there is a "harmony_portlets.jar" that included an old version of the Java API located somewhere in the portal server classpath. In this case, make sure that the only harmony_portlets.jar in the classpath is the one that was included with the portlet bundle that you have installed.
Regards,
Lev

Variable initialized with wrong message type

Hi,
I have a BPEL process variableA of Message type A as defined in the partnerlink WSDL file. This variable get initialized during operation A from the partnerlink. The WSDL has another message type B defined for another operation B.
During runtime when operation A is called variable A gets initialized with message type A, however when operation B is invoked with mesage type B variableA gets initialized again with the content of message type B even though it's defined to be of message type A. Below are the snippets from the WSDL and BPEL process file
WSDL file ..
<message name="MessageTypeA">
<part name="payload" element="mpx:MessageARequest"/>
</message>
<message name="MessageTypeB">
<part name="payload" element="mpx:MessageBRequest"/>
</message>
<portType name="MutilPort">
<operation name="A">
<input message="tns:MessageTypeA"/>
</operation>
<operation name="BA">
<input message="tns:MessageTypeB"/>
</operation>
</portType>
Process BPEL file
<variable name="VariableA"
messageType="tns1:MessageTypeA"/>
<variable name="VariableB"
messageType="tns1:MessageTypeB"/>
<pick name="Pick_2" createInstance="yes">
<onMessage portType="tns1:MutilPort" operation="square"
variable="VariableA" partnerLink="Multiplex">
<sequence name="Sequence_1">
<assign name="Assign_2">
<copy>
<from variable="VariableA" part="payload"
query="/ns1:MessageARequest/ns1:Operand1"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
<onMessage portType="tns1:MutilPort" operation="addition"
variable="VariableB" partnerLink="Multiplex">
<sequence name="Sequence_2">
<assign name="Assign_1">
<copy>
<from variable="VariableB" part="payload"
query="/ns1:MessageBRequest/ns1:Operand5"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
</pick>
Please can anyone shed some light on why and how this can happen and where is it going wrong.
Thanks,
Shishir

Looks like the destination which is used by your EG has default settings,
particulary the RedeliveryLimit param. If it is set to -1 (default setting)
WL will try to redeliver the message forever in case of any error. Just set
it to something else. You can also specify an ErrorDestination and hadle
error messages specifically in it.
Denis.
<Gunjan Shukla> wrote in message news:[email protected]..
Hi,
We are using WLI 8.1, in one of our applications I have a message broker
channel configured to listen to rawdata type messages. A jms event
generator is configured to publish messages, which are sent to a jms
topic, on this channel.
We have no control over type of messages sent by client applications, when
some client application sends an ObjectMessage instead of BytesMessage,
following error is thrown
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLW> <P931467> <cgServer>
<ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-004324CB0C4F26C12C0A> <000000> <Cannot publish non-BytesMessage to
channel of type RAWDATA>
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLI-Core> <P931467>
<cgServer> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <BEA1-004324CB0C4F26C12C0A> <BEA-489048> <Not a
BytesMessage>
server keeps throwing this exception and fills the logs and ultimately
server needs to be re-started.
Can somebody point me to whether its possible to catch these exceptions in
a process?
Or alternatively is it possible to somehow ignore the messages with
mismatched message type?
Any ideas are greatly appreciated.
Thanks and regards,
Gunjan

Error in JMS Adapter while communicating with WebSphere MQ 7.5

Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.

Problem solved after removing j2ee.jar file from classpath !

Integrate with websphere message broker

Similar Messages

Maybe you are looking for