| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 38.1 | Some answers | NUTS2U::LITTLE | ATG/EOS/Object Infrastructure/me | Wed May 14 1997 13:37 | 63 |
| Hi Ewan,
Let me see if I can answer some of these for you.
> 1. Managed to answer this one....
Good, because I don't have an answer for it. ;-)
> 2. I have installed ObjectBroker 2.7 on Windows NT 4.0. There does
> not appear to be an OLE Network Portal like there is on Windows 3.11.
> It may now simply use the DCOM service of NT. As such, what is the
> process for creating OLE/DCOM/ActiveX applications on Windows NT 4.0
> to communicate with OLE-aware ObjectBroker services on Digital Unix
> boxes?
The Network Portal has been replaced with the ObjectBroker Desktop
Connection product. ObjectBroker servers no longer need to be OLE
aware as the Desktop Connection (DTC) provides a transparent
bidirectional bridge between COM/OLE and CORBA.
> 3. We need to look at the CORBA/DCOM Bridge (i.e. ObjectBroker
> Desktop Connection). Given we have licenses for the base ObjectBroker
> product, how much is it? How soon can we get it? What licensing do
> we need? Does it only run on Windows NT/95? Can it run on a separate
> box(es) which acts as a gateway? Can the separate gateway box be
> Unix, or is it restricted to Windows NT/95?
Check with Digital product management (Dan Gilfix) for dates for
Digital. I believe the product is supposed to be released next month.
It only runs on Windows NT and Windows 95. In a way it can be run on a
separate gateway box, but only to the extent that it appears to be a
COM/OLE server/client and could use DCOM to access the remote system.
The design center is certainly much more along the lines of a bridge
per system.
> 4. We need a definition of the new features in ObjectBroker 3.0
> (especially with respect to multi-threading servers, IIOP support,
> and object to implementation instance binding in C++). Is it
> available yet? If not, can we get a Beta copy of it and the
> documentation for appraisal?
I'm afraid I can't help you with this one.
> 5. We want to use direct VB bindings on Visual Basic 4.0 or 5.0. Is
> there any reason why we can not do this? I know that the official
> line is to support VB 3.0, but this is forwardly compatible with VB
> 4.0/5.0, so it should work, provided we only use the VB 3.0 features.
> Can we get official confirmation on this?
I'm assuming you mean direct CORBA VB bindings? If so, I can't help
you. On the other hand if you are referring to the Desktop Connection,
then VB sees the remote CORBA object simply as an OLE object and can
intereact with it just as it would any other OLE object.
> Hope you can help. Many thanks
Hope the above helped.
Regards,
Todd Little
BEA Systems, Inc.
Desktop Connection Team
|
| 38.2 | | SEND::SLAVIN | | Wed May 14 1997 13:49 | 67 |
|
You should be asking ObjectBroker questions in one of the OBB notes
files SEND::OBJECTBROKER or SEND::OBJECTBROKER_Development.
But in any case I'll answer them here. SOmeone from the Desktop team
will have to answer the parts specific to that. ObjectBroker and
ObjectBroker Desktop Connection are 2 separate products.
> 2. I have installed ObjectBroker 2.7 on Windows NT 4.0. There does
> not appear to be an OLE Network Portal like there is on Windows 3.11.
> It may now simply use the DCOM service of NT. As such, what is the
> process for creating OLE/DCOM/ActiveX applications on Windows NT 4.0
> to communicate with OLE-aware ObjectBroker services on Digital Unix
> boxes?
ObjectBroker only supports the client for OLE Network Portal on Windows3.1.
ObjectBroker V3.0 will be the last OBB version that supports the OLE
Network Portal as a client or as a server. So I would not start using it
now. OBB V3.0 is also the last version of OBB that supports DDE and VB.
The Desktop uses a different programming model than the OLE Portal and
they are not meant to be used together. The desktop is meant to
replace the Portal. Especially in light of the fact that the OLE
portal is going to go away.
> 3. We need to look at the CORBA/DCOM Bridge (i.e. ObjectBroker
> Desktop Connection). Given we have licenses for the base ObjectBroker
> product, how much is it? How soon can we get it? What licensing do
> we need? Does it only run on Windows NT/95? Can it run on a separate
> box(es) which acts as a gateway? Can the separate gateway box be
> Unix, or is it restricted to Windows NT/95?
ObjectBroker Desktop Connection is not yet shipping. Pricing information
is not yet available. It is a separate product from ObjectBroker with
a separate license. Someone on the Desktop should answer these other
questions.
> 4. We need a definition of the new features in ObjectBroker 3.0
> (especially with respect to multi-threading servers, IIOP support,
> and object to implementation instance binding in C++). Is it
> available yet? If not, can we get a Beta copy of it and the
> documentation for appraisal?
ObjectBroker V3.0 has a new ObjectBroker-DECmessageQ asynch
programming ability. This is the major new feature for V3.0.
IIOP is planned for the ObjectBroker Bryce release due out late this
year -- fall / winter. ObjectBroker Bryce has IIOP as the major new
feature. There is no threading in ObjectBroker Bryce. I do not know
what you mean by "object to implementation binging in C++" --- C++
bindings have been supported since ObjectBroker V2.6. We are not yet
siging up Beta customers. If you are interested, contact Dan Gilfix
the Digital product manager, in order to get a Digital customer
considered for field test. A1VAX::GILFIX.
> 5. We want to use direct VB bindings on Visual Basic 4.0 or 5.0. Is
> there any reason why we can not do this? I know that the official
> line is to support VB 3.0, but this is forwardly compatible with VB
> 4.0/5.0, so it should work, provided we only use the VB 3.0 features.
> Can we get official confirmation on this?
ObjectBroker V3.0 will not work with any VB version excpet VB3.0. We
know that it will not work at all. In order to support these versions
a re-write of the bindings would have been required, however,
OBB V3.0 is also the last version of OBB that supports DDE and VB
bindings.
|
| 38.3 | Visual C++ DLL query | KERNEL::SMITH | | Thu May 15 1997 07:52 | 13 |
| Many thanks for both your replies, i will contact Dan on behalf of the
customer with a view to getting them on Field Test.
would it be possible for someone to describe the procedure for
construction of the C/C++ DLL required for use by the VB application.
What versions of Visual C++ compiler can they use/will be supported ?
They are stuck in between waiting for the Desktop connection product
and using VB 4.0 (and maybe 5.0) at the moment.
thanks
ewan
|
| 38.4 | | SEND::KONKUS | Loren Konkus | Thu May 15 1997 09:47 | 15 |
| >would it be possible for someone to describe the procedure for
>construction of the C/C++ DLL required for use by the VB application.
Using the desktop connection product, you don't construct a new C/C++
dll for a VB app. There is one shared dll that implements all the
COM and OLE Automation views of your corba objects.
Probably the best bet would be for you to scan the online help, which
describes this process in detail. It's pretty easy though. Basically,
you run a gui app (or type a command line) to expose a corba idl
through the bridge. That creates all the appropriate type libraries,
header files, windows registry entries, etc. that are necessary for
the com and automation views of your corba objects. Then just write
your VB app...
|
| 38.5 | C/C++ DLL without DTC | KERNEL::SMITH | | Tue May 20 1997 06:25 | 8 |
| What if you didn't have the DTC product and in the meantime were stuck
with VB 4.0 and 5.0 - can you describe the procedure they would use for
contruction of the C/C++ DLL ?
This is so they they can test for some fallback capability.
Thanks
ewan
|
| 38.6 | | RECV::SLAVIN | | Tue May 20 1997 11:04 | 6 |
|
> What if you didn't have the DTC product and in the meantime were stuck
> with VB 4.0 and 5.0 - can you describe the procedure they would use for
> contruction of the C/C++ DLL ?
>
There is no way to use VB 4.0 or VB 5.0 with the ObjectBroker VB bindings.
|