I am working on an environment unfamiliar to me. There are a lot of reporting servers, some are names EDASERVE, some are not. WHere is the name set? I assume it's not on the reporting server itself, but on the client server. I'm looking for the configuration file that does this.

This message has been edited. Last edited by: Francis Mariani,

Hi Francis,
Isn't it in ODIN.cfg? We have the same...
EDASERVE is my local, there there are a bunch of different servers for DEV/IT/UAT/PROD
Tom

Tom, thanks for suggesting that, but I don't see the name.

In the Client Admin Console, Under Reporting Servers > Remote Services, I see three servers, one is named SERV1. When I navigate to the reporting server console for this server and view odin.cfg, I don't see the name SERV1 specified, I don't see it in any of the configuration files.

Hey Francis,
UGH, I do see them in mine. On the Reporting Server: Workspace --> Configuration File --> Communication - odin.cfg.
Maybe that file is generated by another setup.

Maybe Sir Chuck will chime in. Not my area of expertise...Sorry!

The content of the v7.7.05 odin.cfg file:

;-- config file generated on 01/09/2012 14:49:09

;HTTP Listener
NODE = LST_HTTP
BEGIN
  PROTOCOL = HTTP
  PORT = 8421
  CLASS = AGENT
END

;TCP Listener
NODE = LST_TCP
BEGIN
  PROTOCOL = TCP
  PORT = 8420
  CLASS = AGENT
END

;TCP Loopback Client
NODE = LOOPBACK
BEGIN
  PROTOCOL = TCP
  CLASS = CLIENT
  HOST = 127.0.0.1
  HTTP_PORT = 8421
  PORT = 8420
END

;FOCUS Database Server
NODE = FOCSU
BEGIN
  PROTOCOL = TCP
  CLASS = SUSERVER
  PORT = 8422
END

;FOCUS Database Client
NODE = FOCSU01
BEGIN
  PROTOCOL = TCP
  CLASS = SUCLIENT
  HOST = 127.0.0.1
  PORT = 8422
END

;JSCOM3 Listener
NODE = JSS
BEGIN
  PROTOCOL = TCP
  CLASS = JAVASERVER
  PORT = 8423
  AWT_HEADLESS = Y
  JVM_MAX_HEAP = 512
  FLEX_SUPPORT = 1
  JVM_INIT_HEAP = 256
END

The reporting servers can be defined from different perspectives.

From the web client
From the Reporting server

With the Web Client, a report request can be directed to different reporting servers

With the Reporting Servers, a report can get data from a different reporting server (hub-sub).

All are defined in an odin.cfg file, the web clients is under the WebFOCUSxx directory structure, the reporting servers is under srvxx/wfs/etc

Where are the client, reporting server and report caster installed, i.e., on the same machine or separate machines? Here, we’ve got the client installed on SERVER_A and report caster and reporting server on SERVER_B. If I add a server via Admin Console > Reporting Servers > Remote Services I also need to copy WebFOCUSxx/client/wfc/etc/odin.cfg from SERVER_A to the same name directory on SERVER_B so that report caster “knows” about the newly defined server. Viewing odin.cfg from the reporting server webconsole, you’re looking at srvxx/wfs/etc/odin.cfg as Waz has stated.

Thanks for the clarification - I was not aware that there are odin.cfg files on the reporting server as well as the client server. You do see the reporting servers in the Remote Services section of the Client Admin Console, but the odin.cfg file is not available to edit.

I assume the only way to look at the odin.cfg file on the client server is by logging into it.

Reporting Server:
The Reporting Server can have many defined data services. there is a DEFAULT data service that comes configured with the installation of the product. You can create additional data services as need and you give each one a unique service (NAME).

WebFOCUS Client:
The WebFOCUS Client can connects to a remote server. It comes configured with a default remote server call EDASERVE. If you look the setting for this Remote server you will see that the CLIENT property is not set. This means that this Remote Server will connect to the default data service running on the HOST and PORT specified. If you have multiple data services running you provide the CLIENT property with the name of the data service you want to connection to. An example is where my have your ondemand reports run on EDASERVE and your Report Caster Reports, InfoAssist Reports, or another application say for another department run on a different data service. This will all you to setup different setting for each data service like the maximum number of concurrent requests, memory limits, queue size, different profiles for one application vs another application. different profiles per application is cleaner and you can put the data connections for that application in that applications profile.

Report Caster:
Also can be configure for multiple remote server that can point to a specific data service on the Reporting Server(s).

Hope this helps.