Mapping Weblogic 7 to Websphere

Hello,
I want to Weblogic 7 A/S to websphere .How to do it?I don't have much idea abt the websphere?
Plz help.
Thanks in advance.

If u don't know answer better don't answer and don't
try to act smart.Try to behave like a professionalBefore commenting on his reply, try to read that question again. It doesn't make any sense.
I want to Weblogic 7 A/S to websphere.
What does this mean?!? I want to "what"?!?
Your question sounds unpreofeesional enough. Try defining your problem clearly.

Similar Messages

EJB communication between weblogic and websphere

Hello:
I have weblogic 7.1 instance running in machine A and websphere running in machine B. I want to make a call to the ejb deployed from weblogic to websphere. Any experience in this would be very helpful. Or pl. post the procedure.
Thx in advance.

I don't think that there is any magic here, although I've never tried it.
All you need is the compiled EJBHome and EJBObject interfaces in the
classpath of the calling EJB, get an InitialContext in the JNDI namespace of
the target EJB container using the name of the JNDI InitialContext Factory,
do a lookup on the bean making sure to do a PortableRemoteObject.narrow when
you are casting the Home stub with the vendor specific version of
PortableRemoteObject(and that may be the real trick), call the appropriate
create method, and you are rolling.
I guess the question becomes how to make sure that when you are calling
PortableRemoteObject.narrow on the Home stub, that you get the vendor
specific version for the EJB container and JNDI namespace from which you are
doing the lookup.
I guess the answer is, I'm guessing. Have you tried it?
bill
"nebs om" <[email protected]> wrote in message
news:30035468.1103738722864.JavaMail.root@jserv5...
Hello:
I have weblogic 7.1 instance running in machine A and websphere runningin machine B. I want to make a call to the ejb deployed from weblogic to
websphere. Any experience in this would be very helpful. Or pl. post the
procedure.
>
Thx in advance.

Weblogic vs Websphere

I know that this has been asked a few times but I couldn't find any recent comparisons.
So - my company is going to adopt a J2EE platform and wants to buy an appserver. We've narrowed it down to Weblogic 8.1 or Websphere 5.2
I know that early versions of Websphere got slated - but can anyone advise on how improved 5.1 is
Also we are mixed ability team with some newbies to Java. We want to adopt a uniform IDE.
Any comments on WSAD versus Weblogic Workshop. Are people using othe IDEs alongside either Websphere Server or Weblogic Server
I like the look of Workshop - but it clearly isn't as big as WSAD - and also Weblogic have introduced the concept of Java Controls which definitely isn't standards based. However our team leader thinks that this could be an easy entry point for less experienced Developers. Any comments on any of these products much appreciated

Hi,
I was looking for a comparison against the latest versions of Weblogic and websphere. I was looking at the string of posts and came to a conclusion that you were in the same situation months before and you have nailed your choice as weblogic. Could you please give me some information regarding that?
Basically am preparing a presentation with performance, scalability, features, ease of development, IDE effeciency, Integration abilities, Webservices capabilities, licensing cost and so on.

Weblogic and websphere colocated?

Has anyone ever had any experience running weblogic and websphere on the same machine? If so, what were your issues?
Thanks in advance.

Web sphere has a wide robust features which weblogic lacks some. Like the load balancing and admin console, clustering .
In Weblogic In many cases, code for applications deployed on WebLogic Server is arbitrarily structured and depends on the build process to make sense of it all. The implication of this is that existing code organization will very likely have to be changed as part of the migration effort. This may be very difficult (or even impossible) to accomplish while maintaining links to your code's history. Some organizations choose simply to archive their history and start fresh.
In WebSphere, Packaged with each module is an XML deployment descriptor that describes the organization of the components in the module and how they are configured at run time. hence applications can be migrated easily.

EJB3 or Spring+Hibennate? JBOSS, Weblogic or Websphere? Oracle or MySQL?

Dear all,
I know this is a question without real answer. However, today, January 2009, if I would build a idea JEE application from scratch, should I choose
EJB3 or Spring+Hibennate?
By the way, I would also ask two other questions. Should I choose Oracle or MySQL? Should I choose Tomcat, JBOSS, Weblogic or Websphere?
I assume that I don't have budget constraint but I really want to have the "best" updated one.
Thanks for any argument.
Pengyou

Dear all,
I know this is a question without real answer. However, today, January 2009, if I would build a idea JEE application from scratch, should I choose
EJB3 or Spring+Hibennate?
By the way, I would also ask two other questions. Should I choose Oracle or MySQL? Should I choose Tomcat, JBOSS, Weblogic or Websphere?
I assume that I don't have budget constraint but I really want to have the "best" updated one.
Thanks for any argument.
Pengyou

Weblogic and Websphere communication!!

Hi Friends,
I have an EJB HelloWorld deployed on both servers(Weblogic and Websphere) and these beens are accessible easily from their respective client servlets, which is the easy part.
Now what I want to try is access the bean's methods on Weblogic server from a bean on Websphere server and vice versa. This is where I want some ideas from the gurus please.
e.g. hello() method of the EJB (HelloWeblogic) in Weblogic server prints the message "Hello from Weblogic" and the hello() method of the EJB (HelloWebsphere) in Websphere server prints the message "Hello from Websphere". Now I want to know what do I need to do so that I am able to execute hello() of the HelloWeblogic EJB, from HelloWebsphere EJB and vice versa.
I am also new to EJB, but I think I am making my way slowly.
Any help/ideas/code samples would be really appreciated.
Please feel free to ask any questions.
Regards
Rajeev

As far as I can see the standard way would be to lookup
the ejbs-home in the others JNDI context. After that proceed
as you are used to.
Troubles (or some unlikely behaviours) could occur if your beans are
served by the same interfaces.
But Dynamic Stub loading via RMI should prevent you from any problems with non existing stub/skels, etc.
You could only run into problems when stub/skel-implementation-classes where named equally (by full qualifier) in both app-servers. This should never happen. (weblogic.SomeWLStubClass != ...websphere...SomeStubClass)
Read RMI-Specification for further details on dynamic class-loading in
the RMI process:
http://java.sun.com/products/jdk/1.1/docs/guide/rmi/spec/rmi-arch.doc.html
or j2ee-tutorial on how to resolve JNDI-Contexts.
Hope it helps!
Alexander Sack

Weblogic and websphere

hi
could anybody tell what is the basic difference between weblogic and websphere.
thanks
suru

Web sphere has a wide robust features which weblogic lacks some. Like the load balancing and admin console, clustering .
In Weblogic In many cases, code for applications deployed on WebLogic Server is arbitrarily structured and depends on the build process to make sense of it all. The implication of this is that existing code organization will very likely have to be changed as part of the migration effort. This may be very difficult (or even impossible) to accomplish while maintaining links to your code's history. Some organizations choose simply to archive their history and start fresh.
In WebSphere, Packaged with each module is an XML deployment descriptor that describes the organization of the components in the module and how they are configured at run time. hence applications can be migrated easily.

J2EE replaces BEA Weblogic, IBM WebSphere, Orion or JRun

BEA Weblogic, IBM WebSphere absolutely provide stronger ability to support enterprise applications.
I want to know whether J2EE can be used in deploying a commercial web site with multi-tier architecture. For example, to handle hundreds concurrent requests, to balance work load to some extent.
Thanks.

J2EE is a platform specification. And WebLogic, WebSphere, JRun etc. are vendor specific products that implement APIs from that platform standard.
It seems you are talking about the refrence implementation of J2EE that comes with J2EE SDK.
See http://java.sun.com/j2ee/faq.html Especially the answers therein to the two questions...
1. What is the purpose of the Reference Implementation?
2. Why don't you allow the binary Reference Implementation to be deployed or redistributed?

Connection Weblogic and Websphere MQ

Can anybody help me how to connect Weblogic and Websphere MQ?

If you are using the foreign JMS server then create the binding file for MQ. The binding file would contain host and port and other required details.
Weblogic could understand the configuration details in that.

Weblogic to websphere default bridge connection issues

I have done a standalone message sender client to websphere and it is working fine. But when i use the same parameters in a destination target in a messaging bridge on weblogic I get the following error
<1377118506218> <BEA-200043> <Bridge "Bridge-0" failed to connect to the target destination.
I have added the following jars to the folder D:\Oracle\Middleware\user_projects\domains\base_domain\lib in my machine(which i assume is the classpath of managed server)
1)sibc.jms.jar 2)sibc.jndi.jar 3)sibc.orb.jar
Weblogic Destination details :
<jms-bridge-destination>
<name>JMS Bridge Destination-0</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
<classpath></classpath>
<connection-factory-jndi-name>jms/queueConnectionFactory</connection-factory-jndi- name>
<initial-context-factory>com.ibm.websphere.naming.WsnInitialContextFactory</initial-context-factory>
<connection-url>iiop://192.168.56.1:2809</connection-url>
<destination-jndi-name>jms/Queue1</destination-jndi-name>
</jms-bridge-destination>
<jms-bridge-destination>
<name>JMS Source Destination-1</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
<classpath></classpath>
<connection-factory-jndi-name>ConnectionFactory1</connection-factory-jndi-name>
<connection-url>t3://localhost:7003</connection-url>
<destination-jndi-name>Queue1</destination-jndi-name>
</jms-bridge-destination>

Can you please paste little more logs. Apart from what you have pasted.

WebLogic with WebSphere MQ as an XA resource

I have been using WebLogic MDBs with WebSphere MQ as an external JMS provider. We just bought MQ Extended Client that would let external transaction managers do XA management with MQ. I have looked at IBM's document @
          http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf. This document indicates that Weblogic cannot be used to do XA with MQ; only three txn managers are mentioned - CICS, Encina, and Tuxedo.
          I don't believe that to be true because it says that it can be used with any XA compliant transaction manager. Is anyone aware of documents showing how to configure a WebLogic server (expecially MDBs) to use MQ extended client to do XA?

WL is an XA compliant TM, and many customers use it with MQ. For more information, you can start with this FAQ:
          http://e-docs.bea.com/wls/docs81/faq/interop.html#268632
          Also see the notes I've appended below.
          Finally, you can search this newsgroup - you will see that your question comes up quite a bit.
          Tom, BEA
          JMS Integration of Foreign Vendors with BEA WebLogic Server
          The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
          For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
          JMS Integration Overview
          - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
          - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
          - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
          - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
          - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
          - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
          - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          Integration with 8.1 Details
          A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
          http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
          This document refers to helpful new 8.1 features, which simplify integration. These include:
          http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
          http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
          And are also summarized here (under interoperability):
          http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          Also read the MDB documentation, which extensively covers integrating foreign vendors:
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
          Integration with 6.1 and 7.0 Details
          Read the "Using Foreign JMS Providers With WLS" white-paper:
          http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
          Note that this white-paper does not take into account 8.1 features.
          For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          Non-Java Integration Options
          - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
          http://e-docs.bea.com/wls/docs61/jcom.html
          http://e-docs.bea.com/wls/docs70/jcom/
          http://e-docs.bea.com/wls/docs81/jcom/
          - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
          http://e-docs.bea.com/wls/docs81/rmi_iiop/
          http://e-docs.bea.com/wls/docs70/rmi_iiop/
          http://e-docs.bea.com/wls/docs61/rmi_iiop/
          Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
          - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
          - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
          http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
          - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
          - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
          Notes on MQ Remote Capable XA Clients
          Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
          http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
          The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
          - Required on WLS where MQ objects are bound into JNDI:
          com.ibm.mq.jar, com.ibm.mqjms.jar
          - Required only if MQ objects are bound into JNDI on a different server:
          com.ibm.mq.jar
          If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
          Notes on Oracle AQ Integration
          If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
          http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
          Caveats:
          The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
          Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
          The solution doesn't seem to support transactions, it may be possible to extend it to do so.
          MDB Thread Pool Notes
          WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
          http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
          (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
          MDB Concurrency Notes
          Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
          Design Guide-Lines and Performance Tuning Notes
          The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
          http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

Weblogic or Websphere

Hi, We are planning to upgrade our Hyperion applications from 9.2.03 to 11x. We currently have Weblogic 8.1. we wnated to know, out of the two, Websphere or Weblogic, which one is better? has anyone experienced any advantages of one over the other?
Thanks

To clarify the restricted use license allows for use of Weblogic for 9.X and 11.X in a non-clustered environment for all Hyperion products not just Planning.
I'll plagiarize myself also:
"It is now documented in the 'Oracle Hyperion EPM System Release 11.1.1.2.0 - Start Here: Installation Documents and Readmes - English' in the specific document ''Oracle Enterprise Performance Management System (11[1].1.1.2.0) all Platforms and Languages 041009.doc'
For every major component you will find WebLogic Server Standard Edition (Oracle WebLogic Server 9.2) with the verbiage 'RL - Restricted use WebLogic Server Standard Edition (restricted to use for running Hyperion PRODUCTNAMEHERE only). WebLogic Server Standard Edition may only be used to host J2EE or Java application logic that is distributed as part of Hyperion PRODUCTNAMEHERE.'"
Regards,
John A. Booth
http://www.metavero.com

OIM on Weblogic Vs WebSphere

Hi All
What could be the reasoning for promoting OIM/Weblogic over OIM/Websphere. I want to suggest my client to go with OIM/Weblogic combination rather than websphere. What should be my strong points to promote OIM-Weblogic.
Please help.
Thanks

WebSphere trials only last 30 or 60 days, so unless your client gives you a full version, your dev images/environments will need rebuilds fairly often. There are lot more integration pieces that tie OIM and WebSphere together which can cause lots of problems because it integrates the security of websphere with the database for OIM.
WebLogic is just the logical choice.
-Kevin

WebLogic to Websphere migration issues

Hi,
We are migrating Java applications from BEA WebLogic 8.1 to WebSphere 6.1 as part of which we have come across few BEA WebLogice workshop specific files/features. It will be great if you could share your thoughts on possible solution/easy way of replacing these features also please share your opinin on the solutions we are thinking of.
- Issue 1: Page Flows are being used (*.jpf file) which were generated using Weblogic Workshop which is Proprietary Tool of Bea.
Soultion we are thinking of # 1: Page Flows can be replaced using Apache Beehive for page flows. As In this framework NETUI tags are being used so there will be only few changes in the jsps.
Limitations/Issues: Design view of Page flows can�t be seen. Code modifications will be there as there are few changes in page flows in Beehive and page flows in Weblogic 8.1. and also It works with JDK 1.5 and our target environment Supports JDK 1.4.
Soultion we are thinking of # 2: The other alternative can be replacing Page flows with struts.
Limitations/Issues: Java Page Flows are built on top of Struts. If we change the page flows to struts, then there will be quite a few changes in the code as config files, action classes, formbeans need be created and also netui tags in jsp should be changed to some other taglibs in struts. And again the design view of it can�t be seen in RAD.
Issue 2: There are few Control files like *.jcx, *.jcs, *.jws are being used in the code which are again Workshop generated. Class files will be generated if we build them in workshop but we need to migrate the development environment as well. We need to change it so that it can be compiled in RAD.
Soultion we are thinking of # 2: These controls are being used different purposes like database controls, email controls etc.
We are not able to find any proper way to directly create the same control in WebSphere. One way can be using Beehive controls and another way can be replacing it with Java code.
Limitations/Issues: In both solutions there will be lots of code changes. And again design view cant be seen in RAD.
Issue 3: There are few Process Definition (*.jpd) in the code. It�s again Bea Specific code.
Soultion we are thinking of # 1: We searched for a same tool in WebSphere (WebSphere Business Modeler) to create process definition.
Limitations/Issues: Learning it and recreating Process flows will again be same as rewriting of code.
Issue 4:
Message Broker Control are being used (created using Workshop). Based on the type of event generators used we are planning to recreate it.

Nagaraj_Mudigal wrote:
Hi,
We are migrating Java applications from BEA WebLogic 8.1 to WebSphere 6.1 as part of which we have come across few BEA WebLogice workshop specific files/features. Good Lord, why would you do that? Websphere is a big step back, IMO. Why not move up to WebLogic 10.3?
It will be great if you could share your thoughts on possible solution/easy way of replacing these features also please share your opinin on the solutions we are thinking of.Your instinct to get away from app server proprietary s/ware is a good one.
- Issue 1: Page Flows are being used (*.jpf file) which were generated using Weblogic Workshop which is Proprietary Tool of Bea.
Soultion we are thinking of # 1: Page Flows can be replaced using Apache Beehive for page flows. As In this framework NETUI tags are being used so there will be only few changes in the jsps.
Limitations/Issues: Design view of Page flows cant be seen. Code modifications will be there as there are few changes in page flows in Beehive and page flows in Weblogic 8.1. and also It works with JDK 1.5 and our target environment Supports JDK 1.4.OMG. 1.4? We're up to 6 now, with 7 on the way.
Soultion we are thinking of # 2: The other alternative can be replacing Page flows with struts.
Limitations/Issues: Java Page Flows are built on top of Struts. If we change the page flows to struts, then there will be quite a few changes in the code as config files, action classes, formbeans need be created and also netui tags in jsp should be changed to some other taglibs in struts. And again the design view of it cant be seen in RAD.I'd recommend Spring before Struts, but Struts 2 will do.
Issue 2: There are few Control files like *.jcx, *.jcs, *.jws are being used in the code which are again Workshop generated. Class files will be generated if we build them in workshop but we need to migrate the development environment as well. We need to change it so that it can be compiled in RAD.
Soultion we are thinking of # 2: These controls are being used different purposes like database controls, email controls etc.
We are not able to find any proper way to directly create the same control in WebSphere. One way can be using Beehive controls and another way can be replacing it with Java code.
Limitations/Issues: In both solutions there will be lots of code changes. And again design view cant be seen in RAD.Code changes no matter what you do.
Issue 3: There are few Process Definition (*.jpd) in the code. Its again Bea Specific code.
Soultion we are thinking of # 1: We searched for a same tool in WebSphere (WebSphere Business Modeler) to create process definition.
Limitations/Issues: Learning it and recreating Process flows will again be same as rewriting of code.I would prefer getting away from all these myself.
Issue 4:
Message Broker Control are being used (created using Workshop). Based on the type of event generators used we are planning to recreate it.I'd use JMS straight.
%

Weblogic and Websphere intergration

Hi,
I would like to make a call from EJB bean deploeyd on WLS8.1 to another
bean deployed on Websphere 6.0 but I have no idea how to do that.
When I do sth like that in EJB in WLS:
InitialContext tx = new InitialContext();
Object obj =
(Object)tx.lookup("corbaname:iiop:localhost:2809#comarch/test/ejb/BasicCalculator");
I get the following exception:
javax.naming.NameNotFoundException: Exception in lookup.:
`comarch/test/ejb/Basi
cCalculator' could not be found. Root exception is
org.omg.CosNaming.Nami
ngContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at
org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHe
lper.java:72)
at
org.omg.CosNaming._NamingContextStub.resolve(_NamingContextStub.java:
251)
at
weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:187)
at
weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:174)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at examples.HelloBean.hello(HelloBean.java:71)
BasicCalculator bean is deployed on websphere and websphere runs on
localhost.
What should i do to get it running?
Any help appreciated.

looser0 <[email protected]> writes:
BasicCalculator bean is deployed on websphere and websphere runs on
localhost.
What should i do to get it running?
Any help appreciated.This definitely works but there have been several patches to both
products to support things well. First of all check what name you
should actually use for websphere - I have a feeling that it has some
bizarre prefix on all of its names. Next make sure you are running
with WLS 8.1sp4. I don't know what version of WebSphere 6.0 you need -
I know there were fixes in WAS 5.1.3.
andy
--

Mapping Weblogic 7 to Websphere

Similar Messages

Maybe you are looking for