IECC

I am trying to use IECC so I can use ISM with ONBAR. I am having trouble with the IECC client finding my Informix database server machine. I am running NT 4.0 SP5 on the client and HPUX-11 with Informix 7.31 FC4. I have updated the hosts file on the client with the machine name and IP address and have updated the services file on the Unix box with the database service and the database server is up and running and I can access it through a TCP/IP connection. When the IECC trys to discover the database server it fails and it tell me to check the hosts file on the NT box. Does anybody have any guesses on what I should check?? Thanks Keith A. Lewis The Timken Company lewis@timken.com (330) 471-4119 (330) 471-4034 (FAX)

we have IECC running with IDS 7.31 FC2 it doesn't have problems in detecting servers placed on the same LAN it HAS problems, instead, when detecting severs on DIFFERENT LAN, because of a known problem; there is a work around, I'm copying here it for you as it came from Informix Support: Title : Making IECC console to view and monitor Database servers spread across the multiple subnets. IECC uses CORBA as a basic communication facility to monitor Database servers through Middle tier component "Server Agent". Since Visigenic ORB which is CORBA implementation used by IECC, doesn't span the multiple subnets by default, users need to go through custom setup. If the purpose is to monitor the subnet other than where IMC is running, set the OSAGENT_ADDR environment variable to point to the ip-address of host machine running the osagent in a subnet that user wants to monitor. One cannot see the servers in the current subnet with this arrangement. In order to observe server in more than one subnet one may need to go through following steps, which are in detail. In brief "one needs to maintain a file "agentaddr" at the location pointed by "VBROKER_ADM", containing a list of IP-address of all machines running osagent across the network, and this file should be made available to any single osagent within a network at its start up time, and IMC should set its OSAGENT_ADDR env variable to point to ip-addr of machine hosting this particular osagent." ---------------------------------------------------------------------------- --- Below listed are the steps needs to be followed.. 1. User can Select a particular machine as a representative machine (give preference to more reliable, resourcefull machine) hosting or targeted to host "Visigenic Osagent" module. Generally, each machine having "Informix Server Agent" install, also has "Visigenic Osagent" install. Keep note of IP-Address of this machine. 2. If "Visigenic Osagent" is already running on representative machine stop it (On NT, through Control Panel you can stop the "IECC Visibroker Osagent" service, where as on UNIX use "stopsa" utility). If this machine also has an "IECC Informix Server Agent" running, stop it the same way. 3. Get the IP-Addresses of all the host machines on the network( actually machines falling on the different subnet than the subnet where representative machine falls) running Visigenic "osagent" module and list one address per line in a file named exactly "agentaddr" (its a case sensitive on UNIX) on the representative machine (hostname in a string format can also be listed in this file). e.g., 555.55.5.555 666.66.6.666 4. On the representative machine, move "agentaddr" file in a directory pointed by "VBROKER_ADM" environment variable (Visibroker installation defines this variable automatically, you can choose to change the location), and start Visigenic osagent on this machine (make sure that VBROKER_ADM environment variable is set and available from the console you choose to run "osagent"). 5. If the machine selected to run Informix Management Console(IMC) is other than or apart from the representative machine then go to step 7. 6. By starting IMC binary on representative machine, user can Informix Database servers which it wasn't able to access through IMC earler. 7. If "Visigenic Osagent" module is running on this machine then stop it as explained in step 2. Set the "OSAGENT_ADDR" environment variable to the IP-Address of representative machine, and start IMC now (make sure IMC process has access to OSAGENT_ADDR environment variable). 8. Also confirm the setnet32 entry for the remote server does not have in the options field SA=2. The problem is that even if they are discovered, the connect will give the error. To get around this, you can delete the sqlhosts entry by using setnet32 or by simply removing SA=2 from the option field. Note : Whenever any osagent is added in the subnet other than representative machine's subnet, ip-addr of machine hosting that osagent needs to be added to the "agentaddr" file mentioned at step 3 and osagent needs to be restarted. You may have to reboot the machine once after setting VBROKER_ADM Lewis, Keith A. ha scritto nel messaggio <8hlqno$9mt$1@news.xmission.com>... > >I am trying to use IECC so I can use ISM with ONBAR. I am having trouble >with the IECC client finding my Informix database server machine. I am >running NT 4.0 SP5 on the client and HPUX-11 with Informix 7.31 FC4. I have >updated the hosts file on the client with the machine name and IP address >and have updated the services file on the Unix box with the database service >and the database server is up and running and I can access it through a >TCP/IP connection. When the IECC trys to discover the database server it >fails and it tell me to check the hosts file on the NT box. Does anybody >have any guesses on what I should check?? > >Thanks > >Keith A. Lewis >The Timken Company >lewis@timken.com >(330) 471-4119 >(330) 471-4034 (FAX) >