Kbase 18491: Configuring OrbixWeb to get the Apptivity CORBA demo running
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/01/1999 |
|
Configuring OrbixWeb to get the Apptivity CORBA demo running
DRAFT COPY - Currently under review and edit.
INTRODUCTION:
=============
Apptivity ships with Iona's OrbixWeb, but not with the OrbixWeb Java
Daemon and the appropriate tools to configure the OrbixWeb Java Daemon
and register the Naming Service names.
Because of former CORBA implementations the most examples provided
by Iona's OrbixWeb are based at the Basic Orb Adapter (BOA) with
no need of configuring the Java Daemon for Naming Service.
With OrbixWeb Version 3.1c01 downloadble as trial version from:
http://www.iona.com/products/internet/orbixweb/
also the Portable ORB Adapter (POA) is supported. With POA the Object
Management Group (OMG) beside the advantage of having a portable
solution fixed also problems regarding the object
activation/deactivation and object registration with the ORB. Using
POA can be recognized at the server code with a syntax like
orb.omg.CORBA.ORB orb.connect(object) instead of org.omg.CORBA.BOA
boa.obj_is_ready ().The Apptivity CORBA demo example Inventory
uses POA and CORBA Naming Service. Below a small incomplete
enumeration under what circumstances a communication error like
org.omg.CORBA.COMM_FAILURE: hostname/port may appear :
1.The OrbixWeb Java Daemon is not started -> Solution: run orbixdj.bat
2.The OrbixWeb Java Daemon hostname and daemon port number and the
CORBA Naming Service initial naming hostname and service port
number are different but not running on different hosts or ports
-> Solution : configure it for the same hostname , port number or
make sure the Naming Service really runs on the specified initial
naming hostname and service port number.
Example of lines inside the OrbixWeb.properties file after the right
configuration for host pcrwe2 and port 7570:
OrbixWeb.IT_NAMES_SERVER=NS
OrbixWeb.IT_NS_HOSTNAME=pcrwe2
OrbixWeb.IT_LOCAL_HOSTNAME=pcrwe2
OrbixWeb.IT_ORBIXD_IIOP_PORT=7570
OrbixWeb.IT_ORBIXD_PORT=7570
OrbixWeb.IT_NS_PORT=7570
3. The specified port is already used by an other process -> Solution:
use a free port.
4. The Name Service is not registered in the daemon's Implementation
Repository ->Solution: Register it using the putit command.
Example commands for registering Apptivity's CORBA demo
InventoryServer persistent as put.bat.
call putit -j NS IE.Iona.OrbixWeb.CosNaming.NS
call chmodit NS i+all
call chmodit NS l+all
call putit -j Inventory InventoryServer
call chmodit Inventory i+all
call chmodit Inventory l+all
5. The server's ORB looks at a different host and port for the Naming
Service than it's running on. -> Solution : Make sure the server
looks at the right host and port.
Example for starting the InventoryServer looking for the Naming
Service on host pcrwe2 port 7570 :
owjava -DOrbixWeb.IT_NS_HOSTNAME=pcrwe2 -DOrbixWeb.IT_NS_PORT=7570
-DOrbixWeb.IT_NAMES_SERVER=NS InventoryServer pcrwe2
The settings above are well tested. If you still get a
org.omg.CORBA.COMM_FAILURE for better trouble shooting set the default
diagnostic level higher using the OrbixWeb Configuration tool and
increase the display size of your command box from where you start the
server. With default diagnostic level value 255 it is possible to
trace every communication byte.