Using the JaguarORB object
To create a CORBA-compatible client, you can use the JaguarORB
object instead of the Connection object to establish the connection
to the server. The JaguarORB object allows you to access EAServer from PowerBuilder clients in
the same way as C++ clients.
Two techniques
The JaguarORB object supports two techniques for accessing
component interfaces, using its String_To_Object and Resolve_Initial_References functions.
Using the String_To_Object function
works in the same way that the ConnectToServer and CreateInstance functions
on the Connection object do internally. The String_To_Object function
allows you to instantiate a proxy instance by passing a string argument
that describes how to connect to the server that hosts the component.
The disadvantage of this approach is that you lose the benefits
of server address abstraction that are provided by using the naming
service API explicitly.
If you want to use the EAServer naming
service API, you can use the Resolve_Initial_References function
to obtain the initial naming context. However, this technique is
not recommended because it requires use of a deprecated SessionManager::Factory create method.
Most PowerBuilder clients do not need to use the CORBA naming service
explicitly. Instead, they can rely on the name resolution that is
performed automatically when they create EAServer component
instances using the CreateInstance and Lookup functions
of the Connection object.
About the naming service
The EAServer naming service
is an implementation of the CORBA CosNaming component, which is
a collection of interfaces that provide support for object binding
and lookup. For more information about the CosNaming module, see
the EAServer interface repository
documentation. The interface repository documentation can be viewed
in a Web browser by connecting to your server with the URL http://yourhost:yourport/ir/ where yourhost is
the server’s host name and yourport is
the HTTP port number.