Websphere to Weblogic Migration

Hi,
I am looking for some guidelines and document which can provide adequate information on doing the J2EE Application Migration from Websphere Application Server 6.1.x to Weblogic 10.x version.
Thanks in Advance
Sachin

Guys:
The link provided caters to Websphere Studio to WebLogic 8.1. My requirement is migration from WebSphere 5.x to WebLogic. My current architecture is as follows:
1. Front End: JSP (Ver 1.2), XSL, XML
2. Middle Layer: EJB (EJB Ver 2.0) (Stateless Session Beans) (Deployed in IBM WebSphere 5.0)
3. RDBMS: Oracle 9i Enterprise Edition - Release 2.
4. Modal View Controller architecture (MVC)
5. Number of JAR files: 137
6. One WAR File
7. Appserver OS: W2K.
All the files needs to be migrated to WebLogic 8.1 including the deployment descriptor.
Is there any tool for this conversion? Any white paper, proof of concept, document on steps, approach, risks, mitigation,etc will be helpful.
Thanks in anticipation
Best Regards
Pichu
[email protected]
Refer to
http://www-106.ibm.com/developerworks/websphere/librar
y/techarticles/0311_chaland/chaland.html
"Stephen New" <[email protected]> wrote:
Hi,
Does anyone know of any articles/papers aboutmigrating a J2EE application
from
IBM's WebSphere to BEA WebLogic Server?
I am currently doing a migration from WebSphere 4.xto WebLogic Server
8.1 and
am hoping to learn from other people's experiences.
Thanks,
Stephen.

Similar Messages

Migrating from OIM on WebSphere to WebLogic

Can anyone provide any insight on the possibility of migrating OIM from WebSphere to WebLogic. Are there differences in the database that would make this a difficult task?
The "Upgrading to 11gR1" does not list this as a possible path.

In this section of the documentation http://download.oracle.com/docs/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm#CACFJBJE it has listed WebSphere on the left for 9.x version, and WebLogic on the right for 11g. And since 9.x and 11g use different tables specific to the application server, the migration of data from 9.x should not matter for those. The 11g will use it's own tables specific to the app server and migrate just the required OIM data that isn't specific to the previous app server. That is why you must complete all tasks in the queues prior to migration.
-Kevin

Weblogic migration: 8.1.6 to 10.3 - Recommendations

Hi all,
We are starting an analyze to weblogic migration from 8.1.6 to 10.3. There are many web applications, ejb modules, data sources and connection pools deployed. I´d like to receive from you the main points that I have to consider prior to migrate the server and redeploy the components.
Initially I think I need to recompile the source codes using the 10.3 weblogic api.
Thanks in advance.

Please follow the below upgrade guide for weblogic server 10.3: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/upgrade/index.html
If you face any issues in upgradation process, please post it here.
Regards,
RC2
http://crkthoughts.blogspot.com

Java Websphere and Weblogic

Can any one explain or what type of applications are being developed by
java websphere and weblogic ,also is there any sample project or source
url please inform me?
Thanks
Arun

websphere and weblogic are j2ee container implementations by IBM and BEA respectively. They are ment to host j2ee application complient to the j2ee spec. You can develop any kind of applications on these servers as long as they comply to j2ee spec. Both these servers provide various extensions to j2ee such as tools and APIs to make development for these server easier.

Weblogic Migration, JDBC doesn't support XA issue

We are doing Weblogic Migration from WLS10.3.2 to WLS10.3.6 and Java from jdk1.6.0_26 to jdk1.7.0_07
we are facing the following error for two modules which sends email but few other modules sending email are working fine :
javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
*[Wed Apr 10 08:40:03.069,<gzd4qc>] DEBUG (WorkRequestServiceImpl:sentEmailNotification) - Remote Exception occurred : javax.transaction.TransactionRolledbackException: BEA1-0020971AAD25AA29B1E3: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource*
In Weblogic10.3.6, if we change the Datasource --> Transaction from one-phase commit to Logging Last Resource,
this issue is getting resolved.
But all the modules were working fine with one-phase commit in Weblogic10.3.2
Could you kindly help us to fix this issue and problem in migration.

Hi Joe,
We have changed the driver to XA ( Oracle's Driver (Thin XA) for instance connections; Versions:9.0.1 and later )
and we are getting the below issue in below case
CASE:
I will start a transaction and it gets connected to the Database through
the datasource in weblogic server and then it updates the data into the database which was given from the screen
Issue:
Caused by: java.sql.SQLException: Connection closed
at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:213)
at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:84)
at weblogic.jdbc.wrapper.ResultSetMetaData.preInvocationHandler(ResultSetMetaData.java:61)
at weblogic.jdbc.wrapper.ResultSetMetaData_oracle_jdbc_driver_OracleResultSetMetaData.getColumnCount(Unknown Source)
Hence i think i cannot go for XA driver....
It is working for Non XA driver with Logging Last Resource
As per your note
Logging Last Resource is an excellent way to engage one non-XA
resource in a global transaction, with complete safety. The LLR resource is used for logging the
XA transaction, and is committed as the first part of the second phase of the commit. As such it
can be managed XA-wise whether that succeeds or fails.
Can i keep as LLR itself
Will there be any impact for my applications for below transaction scenarios ?
One case
I will start a transaction and it gets connected to the Database through
the datasource in weblogic server and then it updates the data into the database which was given from the screen
Another case
I will start a transaction and it gets connected to the Database(2) through the datasource(2) in weblogic server and it
reads the data from database(2) and then it updates the data(which was read) into database(1)
I am also using EJB 3.0 version ( transaction-type - Container and Bean. Session-type - Stateless )
Note the changes
Previous Datasources details
X datasource points to a my db - Non XA driver with one phase commit
Y datasource points to a other db - Non XA driver with one phase commit
Issue :
javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
[Wed Apr 10 08:40:03.069,<gzd4qc>] DEBUG (WorkRequestServiceImpl:sentEmailNotification) - Remote Exception occurred : javax.transaction.TransactionRolledbackException: BEA1-0020971AAD25AA29B1E3: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
Changed Datasources details
X datasource points to a my db - Non XA driver with LLR
Y datasource points to a other db - Non XA driver with one phase commit
Working
Can you please provide ur advise . thanks
Thanks and Regards
K.Vickram

What is the best Connection option from WebSphere to Weblogic?

What is the best Connection option from WebSphere to Weblogic?
          We are trying to send XML messages from Websphere to WLS to active some
          services....
          any pointers, suggestions?
          Thx
          VJ


Hi,
One of my clients has an environment similar to yours with an internal pair of F5s and a pair used for the access from the internet.
I am only going to focus on the method using an F5 Load Balancer and SSL Offloading. the setup of the F5 will not be covered in detail but a reference to the documentation to support SharePoint and SSL Offloading will be provided
Since you arte going to be using SSL Offloading you do not need to extend your WebApps to use separate IIS WebSites with Unique IP Addresses
Configure the F5 with SSL Offloading
Configure a Internal AAM for SSL (HTTPS) for each WebApp that maps to the Public HTTP FQDN AAM Setting for each WebApp
Our environment has an additional component we require RSA Authentication for all internet facing Sites. So we have the extra step of extending the WebApp to a separate IIS WebSite and configuring RSA for each extended WebSite.Reference:
Reference SharePoint F5 Configuration:
http://www.f5.com/featured/video/ssl-offloading/
-Ivan

Porting portlets from WebSphere to Weblogic Portal Server

How to Porting portlets from WebSphere to Weblogic Portal Server can any one help
me by providing the suitable steps , or material to know how to go about it.
Thanks in advance

To be in same page, iam running the client program using the IBM jre and using all the websphere client jars set in classpath. This program conatins intial context factory as "com.ibm.websphere.naming.WsnInitialContextFactory" and provider url as "iiop://hostname:portnumber" it contacts the EJB bean method which is hosted on the weblogic server on the "hostname" machine. When it tries to contact i get the errror as
"javax.naming.NameNotFoundException: Context: , name: java.iecc.env.ejb.elf.client_new(My JNDI name): First component in name java.iecc.env.ejb.elf.client_new not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]"

Websphere and weblogic version

hi everybody,
Can anyone please say me the free version of websphere and weblogic that supports the
oracle waveset/sunIDM8.1version.
Please anyone help me out from this issue.
Thanks,
Tarun.

From: http://docs.oracle.com/cd/E19225-01/820-5592/820-5592.pdf
Here are the supported application servers that can be used with Sun IDM 8.1 (see below).
Of course, instead of Sun IDM 8.1 you should utilize Oracle Waveset 8.1.1 and then apply the latest patch, which is 8.1.1.8. This is the latest possible version and contains all possible fixes and enhancements.
Note: If you run the latest patch version of Sun IDM 8.1 (8.1.0.15) it also supports (from the 8.1.0.15 Rel Notes):
IBM WebSphere 7.x application server can now be used with Identity
Manager. (ID-13555125) 8.1.0.15
If you have any additional questions please let me know.
==========
Application Servers
The application server you use with Identity Manager must be Servlet 2.2-compliant and
installed with the included Java platform (unless noted as follows). Identity Manager requires
Java SE Development Kit (JDK) 5 or 6 on the following application servers, if the application
server supports these versions.
■
Apache Tomcat 5.5.x, 6.0.x
■
BEA WebLogic Server 9.1, 9.2, 10
■
IBM WebSphere 6.1
■
JBoss Application Server 4.2
■
Oracle® Application Server Enterprise Edition 10g Release 3 (10.1.3)
■
Oracle Application Server Standard Edition 10g Release 3 (10.1.3)
■
Sun Java
TM
System Application Server 9.1 (GlassFish
TM
v2 UR1, v2 UR2, v2.1 32-bit and
64-bit)
■
Sun Java System Application Server Platform Edition 8.1, 8.2, 9.0
■
Sun Java System Application Server Enterprise Edition 8.1, 8.2
■
Sun Java System Application Server Standard Edition 8.2
Note–
■
If your current application server does not support JDK 5, please check with your vendor to
examine the implications of upgrading to one that does before installing Identity Manager.
■
Identity Manager requires a JDK that correctly handles the 2007 adjustments to U.S.
Daylight Savings Time (DST). You must install any relevant DST patches for the JDK
version you are using. For Sun JDK 5, Update 15 contains the necessary DST fixes. All
versions of Sun JDK 6 contain the necessary DST fixes.
■
You can run Identity Manager on BEA WebLogic application servers with all
WebLogic-supported 5 JDKs.
==========

Migrating from Oracle Application Server or WebSphere to WebLogic Server

Does anyone know of any documentation about migrating applications from WebSphere 6.1 or OAS 10.1.3.3 to WebLogic 10.3tp? I found some old (circa 2005) documents, but I doubt they will help much.
Thanks,
Leona

Please refer to the following url:
http://www.sun.com/migration/sunonetools.html
This should give u a head start on what needs to be done and how,. WIth respect to webserver , i guess you can use it or leave it depending on the architecture you require to deploy your solution.
Hope this helps !

[OIM] Migrate from WebSphere to WebLogic

Hi people,
I would like to migrate our OIM implementation from WAS to WLS, is that possible? Is there some documentatition to achieve this goal?

If you only transfer configuration the chances of something breaking are minimal.
On the other hand if you need transactions as well things get a bit more complex.
In either case a full regression test is always a must as there always is the risk that a supporting jar or even dll (if one windows) in the app server is of slightly different version which introduces a change of behavior.
Best regards
/Martin

OAS - Weblogic Migration

Hi
Now we have below applications running in OAS.
1) Apex applications with reports
2) Forms applications
We want to migrate to Web Logic or Oracle Web Tier.
1) We can migrate apex applications to Oracle Web Tier, But If we want to run reports Is there any plugin to run reports. With weblogic we can install forms and reports, but without weblogic is there any option to run reports just with Oracle Web Tier with any other plugins/utilities.
2) If the above option does not work then we need to use Web Logic, With forms and reports plugins we can run these applications but how to run the Apex applications in Web Logic?
3) We have forms in OAS where we call one form directly and this form will call other forms during working with the application.How to migrate this application to weblogic. Is this need to be deployed as an application...
Can you pls let me know the best option to run all these application in the latest versions.
Thanks in Advance.
Sree

Hi Stoigniew Sztank,
I am working on migrating Enterpirse application developed using Struts, Ejb2.0, JMS. Its been deployed on OAS 10G and Websphere, but I need to deploy the application on Weblogic 10.3. It seems you have migrated a J2ee application from OAS 10G to Weblogic 10.3. Please can you list me the steps that you followed to migrate the application.
As per my understanding follwing things needsto be taken care of:-
1) Weblogic Descriptor files:
1.1 Weblogic.xml:- we added security roles and ejb-reference-description for the ejbs.
1.2 Weblogic-ejb-jar.xml for all the ejbs used in the application.
1.3 Weblogic-application.xml
1.4 Resource Adapter
2) JMS queue set up
3) JDBC set up
It would be a great help if you can let me know what are the steps to migrate the application.
Thanks and Regards
Deepak Dani

Which is better,websphere or weblogic?

Our company want to establish a network serving for PC ,wap ,pda and so on using j2ee.but I don��t know which is better Between Websphere application server and Weblogic.
Who can tell me in detail?

Something to start with:
WebSphere
1. WebSphere covers more platforms.
2. WebSphere has a better supportline (IBM know this stuff)
3. Having DB2 as a database, you might want to use WebSphere, since it has a lots of advantages of using both the database and AppServer from the same Vendor.
WebLogic:
1. WebLogic is a more possisioned appserver
2. I 'believe' weblogic is more up to date with java versions and technologies
regards
Andreas

Weblogic Migration / orion-ejb-jar.xml

What is the best way to create the orion-ejb-jar.xml when migrating from Weblogic? This could be a utility that converts the weblogic deployment descriptors or a tool that helps me quickly create a new orion-ejb-jar.xml.
I have quite a few so a manual process is less desirable.
Thanks!

Hi,
Im not aware of any tool, but here's a whitepaper on switching from WL to 9iAS,
http://otn.oracle.com/tech/migration/content.html
http://otn.oracle.com/products/ias/pdf/weblogic_migration.pdf
Hope this helps,
Neelesh Shastry
OTN Team @ IDC

Re: Using Websphere MQ & Weblogic 7.0 MDBs....

          Sridhar,
          It interest me to to know how you got on with this.
          Thanks,
          Ranjit
          "Sridhar Krishnaswamy" <[email protected]> wrote:
          >
          >We would like to keep Websphere MQ and Weblogic on separate machines
          >and still
          >take advantage of XA. My understanding (from reading the BEA Whitepaper
          >on configuring
          >foreign JMS Providers) is that it is not possible to configure the Weblogic
          >MDBs
          >in 'Container Managed Transaction Mode', because of the limitations of
          >MQSeries
          >(until version 5.2) supporting XA only in bindings mode, which means
          >that the
          >QM Manager where the MDBs connect to have to be on the same machine.
          >
          >
          >It looks like Websphere MQ 5.3 CSD03 does not have this limitation, i.e.
          >it provides
          >an 'Extended Transactional Client' that eliminates the need for the Queue
          >Manager
          >to be on the same machine as WLS. I am struggling to configure the setup,
          >because
          >there is not much information available and the only manual I got from
          >IBM talks
          >only about configure their own AppServer, Websphere.
          >
          >Does anyone have experience with configuring MDBs getting messages from
          >a MQ Queue
          >Manager on a different machine as a Container Managed Transaction? If
          >so, any
          >pointers would help.
          >
          >Thanks,
          >Sridhar


          Hi,
          We use WebLogic 7.0 and MQSeries running on separate servers. I created the .bindings
          file with the JMSAdmin tool and create a jndi dir to store the file in the WebLogic
          domain. I also configured the classpath in the startup script for Weblogic.
          To get the MDB's to work, you define the path of the .binding file in the weblogic.xml
          file. See below classpath and xml. I never tried to look at the file through
          the jndi tree. I did not implement code to do this such as the startup class.
          It hasn't been necessary, everything works great. I'm still looking into using
          the ETC....IBM says your can't but this thread says you can. Hope this helps.
          Jennifer
          classpath info:
          $DOMAIN_HOME/lib/fscontext.jar:$DOMAIN_HOME/lib/providerutil.jar:$
          DOMAIN_HOME/lib/com.ibm.mqjms.jar:$DOMAIN_HOME/lib/com.ibm.mq.jar
          weblogic-ejb-jar.xml
          <ejb-name>SynchronousMessageControllerMDB</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>RPCS.REQUEST.TO.RPCS</destination-jndi-name>
          <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
          <provider-url>file:/opt/weblogic/apps1/rpcs/rpcsDomain/jndi</provider-url>
          <connection-factory-jndi-name>RPCSQCF</connection-factory-jndi-name>
          <jms-polling-interval-seconds>60</jms-polling-interval-seconds>
          </message-driven-descriptor>
          "Jean-François Malaise" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have the same problem but with a little difference: I don't use a start-up
          >classe
          >but configur a foreign JMS Server (I use Weblogic 8.1) and I point our
          >provider
          >url to the directory where .bindings are (That file was created by the
          >JSMAdmin
          >tool of Websphere MQ).
          >I added the CLASS_PATH of MQ jars in the StartManagedServer.sh script.
          >The problem is: when I would like to see the JNDI tree, I have the foolowing
          >message
          >instead the tree: "Access denied". I have verified the file access (we
          >used Solaris
          >8.0) for the file .binding and they are corrects.
          >
          >Is someone had already have the problem and can help me?
          >
          >"K.V.Subrahamnyam" <[email protected]> wrote:
          >>
          >>
          >>
          >>Hi Guys,
          >>
          >>Hi Guys,
          >>Attached my startup class.i can connect to MQ through that.but how i
          >>can connect
          >>through MDB.
          >>Please help me in setting up my MDB to connect to MQ series.I've followed
          >>the
          >>same way as in jmsproviders pdf document.I've one weblogic startup class.in
          >>the
          >>startup class can i give any jndi name?where it stores jndi information?how
          >>it
          >>invokes MDB?what is the provider url and connection factory jndi anme
          >>we've to
          >>give in the weblogic-ejb-jar.xml.
          >>
          >>Please provide me the exact information.I heard that if we can copy
          >.bindings
          >>file from MQ Server to WebLogic server (as both are on different machines)
          >>and
          >>point our provider url to the directory where .bindings file copied.is
          >>it the
          >>correct way.i cannot get MQ server access.how i can do it?
          >>
          >>Tom Barnes <[email protected]> wrote:
          >>>You could try contacting BEA customer support,
          >>>a support person recently got the MQ extended client working
          >>>for another customer. (Her name is Jane Sampson.)
          >>>The main thing seemed to be that you
          >>>need to make sure that all required MQ jars are in
          >>>the server class path:
          >>>
          >>>Required on WLS where MQ objects are bound into JNDI:
          >>>
          >>>%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>%MQ_JAVA_LIB%\com.ibm.mqjms.jar
          >>>
          >>>Required only if MQ objects are bound into JNDI on a different server:
          >>>
          >>>%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>
          >>>For the jmsadmin.bat classpath, all that seems to be necessary is:
          >>>
          >>>%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>%MQ_JAVA_LIB%\com.ibm.mqjms.jar
          >>>
          >>>If that doesn't work try, dumping them all in:
          >>>
          >>>set MQ_JAVA_INSTALL_PATH=C:\PROGRA~1\IBM\WEBSPH~1\Java
          >>>set MQ_JAVA_LIB=%MQ_JAVA_INSTALL_PATH%\lib
          >>>set MQJMS_CLASSPATH=%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\com.ibm.mqbind.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\com.ibm.mqjms.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\com.ibm.mqetclient.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\fscontext.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\connector.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\jms.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\jndi.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\jta.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\ldap.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\providerutil.jar
          >>>
          >>>
          >>>In addition, I doubt the startup class you
          >>>are using is required anymore - instead, leverage
          >>>the new "foreign vendor" integration features
          >>>built into 8.1 (configured via console).
          >>>
          >>>http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          >>>
          >>>Tom
          >>>
          >>>Leong Dong wrote:
          >>>
          >>>> "Sridhar Krishnaswamy" <[email protected]> wrote:
          >>>...
          >>>>
          >>>> Sridhar,
          >>>>
          >>>> I am currently trying to configure the MQ 5.3 extended transactional
          >>>client to
          >>>> work with MDB's on WLS 8.1, and is getting the following error:
          >>>> [EJB:010196]'javax.jms.JMSException: MQJMS1068: failed to obtain
          >XAResource'
          >>>Linked
          >>>> exception = 'javax.transaction.xa.XAException: client connection
          >not
          >>>XA enabled'
          >>>>
          >>>> I am using a Startup Class to set up the JNDI objects, as described
          >>>in the "Using
          >>>> Foreign JMS Providers with WebLogic Server" document. This worked
          >>>fine with MQ
          >>>> 5.2 in "bindings" mode, but not with MQ 5.3 in extended client mode.
          >>>>
          >>>> Any suggestions you can offer is greatly appreciated.
          >>>>
          >>>> Thank you in advance,
          >>>> Leong
          >>>
          >>
          >

Using Websphere MQ & Weblogic 7.0 MDBs....

          We would like to keep Websphere MQ and Weblogic on separate machines and still
          take advantage of XA. My understanding (from reading the BEA Whitepaper on configuring
          foreign JMS Providers) is that it is not possible to configure the Weblogic MDBs
          in 'Container Managed Transaction Mode', because of the limitations of MQSeries
          (until version 5.2) supporting XA only in bindings mode, which means that the
          QM Manager where the MDBs connect to have to be on the same machine.
          It looks like Websphere MQ 5.3 CSD03 does not have this limitation, i.e. it provides
          an 'Extended Transactional Client' that eliminates the need for the Queue Manager
          to be on the same machine as WLS. I am struggling to configure the setup, because
          there is not much information available and the only manual I got from IBM talks
          only about configure their own AppServer, Websphere.
          Does anyone have experience with configuring MDBs getting messages from a MQ Queue
          Manager on a different machine as a Container Managed Transaction? If so, any
          pointers would help.
          Thanks,
          Sridhar


          We would like to keep Websphere MQ and Weblogic on separate machines and still
          take advantage of XA. My understanding (from reading the BEA Whitepaper on configuring
          foreign JMS Providers) is that it is not possible to configure the Weblogic MDBs
          in 'Container Managed Transaction Mode', because of the limitations of MQSeries
          (until version 5.2) supporting XA only in bindings mode, which means that the
          QM Manager where the MDBs connect to have to be on the same machine.
          It looks like Websphere MQ 5.3 CSD03 does not have this limitation, i.e. it provides
          an 'Extended Transactional Client' that eliminates the need for the Queue Manager
          to be on the same machine as WLS. I am struggling to configure the setup, because
          there is not much information available and the only manual I got from IBM talks
          only about configure their own AppServer, Websphere.
          Does anyone have experience with configuring MDBs getting messages from a MQ Queue
          Manager on a different machine as a Container Managed Transaction? If so, any
          pointers would help.
          Thanks,
          Sridhar

Websphere to Weblogic Migration

Similar Messages

Maybe you are looking for