• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

Websphere and visibroker

 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
We are building a distributed web application where we need to make calls to some legacy systems.
We are using visibroker for making these CORBA calls to the legacy system. The legacy system is C based and situated at a remote location.These calls are working well if we use JDBC calls within our application. But our application also uses EJB.
The problem starts when we try and use both EJB & Visibroker in the same machine. When the PNS in the websphere starts, it clashes with the ORB pacakages of Visibroker.
I need help in any of these 2 directions,
1) Can anyone suggest how to make both the naming services(visibroker & PNS) run together so that i can avoid this problem?.
2) Is there anyway, i can use the component broker of IBM to be used to make my ORB calls to the legacy system?. I think ORBs are available with Websphere. My legacy software uses Visibroker for C++ ver 4.1.
This is quite urgent. Thanks for all your help. Waiting for your reply.
Cheers
Sriram
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to find a solution to very similar problem. We have a legacy system written in C++ with a visibroker (3.3) corba interface on top of it. It was BOA instead of POA. I am trying to call these CORBA objects from a servlet deployed in Websphere 4.0. The servlet is failing to locate the CORBA object of the legacy application. I have set the ORB properties as follows :
org.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB and org.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB. This same servlet works fine in Tomcat 3.2.3 but not websphere 4.0. This seems similar to the problem you are facing. If you have found solution to your problem, please let me know. My email is [email protected]
 
author
Posts: 3892
5
Redhat Quarkus Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unfortunately, this type of CORBA interoperability is only found in WebSphere Enterprise Extensions (http://www-4.ibm.com/software/webservers/appserv/enterprise.html). You can supposedly manage it through the features of the JDK 1.3, but the best way is through EE.

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
reply
    Bookmark Topic Watch Topic
  • New Topic