In this section:
After installing the WebFOCUS Reporting Server, you should verify that it runs properly by starting the server and viewing the Web Console as explained below. You can then use the Web Console to configure adapters.
There are several security levels in which you can start the WebFOCUS Reporting Server. For a description of these levels, see Security and User IDs for WebFOCUS and ReportCaster.
export EDAEXTSEC=OPSYS export EDAEXTSEC=PTH export EDAEXTSEC=OFF
The Workspace Manager starts. The following is an example of the message displayed:
Starting Workspace Manager in /home/iadmin/ibi/srv81/wfs Logging startup progress and errors in /home/iadmin/ibi/srv81/wfs/edaprint.log
For a list of options for the edastart command, type the following:
Note: If you see an error related to JSCOM3, you can troubleshoot this in How to Verify or Enable the JSCOM3 Listener.
The Web Console, sometimes referred to as the Server Console, provides an interface for configuring, monitoring, and testing the WebFOCUS Reporting Server. To access the Web Console and test the server, do the following:
Is the host name or IP address of the machine running the WebFOCUS Reporting Server.
Is the HTTP port you specified during the installation. The default is 8121. This is the port of the LST_HTTP node in /install_directory/ibi/srv81/wfs/etc/odin.cfg.
The Web Console home page displays.
The procedures and steps to administer the server, configure adapters, and create metadata (synonyms, Master Files, and Access Files) are accessible from the Web Console Help. They are also available in the Server Administration manual.
To access these instructions, do the following:
The Web Console Help appears.
JSCOM3 is a listener installed with the WebFOCUS Reporting Server that is used when the server creates Active Technologies for Adobe® Flash® or Flex® software, graphics, accesses data sources through JDBC, or launches other Java processes. It normally uses the fourth port used by the server. By default, this is port 8123. Although not all WebFOCUS functionality requires JSCOM3, it is a good idea to ensure it is available.
The Java Services Agents page opens.
If the Stop option appears, then JSCOM3 is started.
If the Start option appears, then JSCOM3 did not start. JSCOM3 cannot start unless it finds certain native files in JRE directories. The server can find these file automatically if you set a $JAVA_HOME environment variable as explained in Preliminary Installation Instructions. If you set $JAVA_HOME in your .profile, log off, log back on, and restart the WebFOCUS Reporting Server. If JSCOM3 still does not start, refer to the Server Installation WebFOCUS Reporting Server DataMigrator Server manual to manually to set your shared library path.
If you are planning to run the Active Technologies for Flash or Flex software, ensure that enough memory is allocated to the JSCOM3 service for Java to compile Flash or Flex files. Perform the following steps to set the maximum Java heap size:
The Java Services Configuration pane opens.
Note: 1024 Mb (1Gb) should be a sufficient value, although this can depend on how much memory is available on the machine that is hosting the server.
A page appears where you can configure the JSCOM3 listener. You can click through the tabs to see additional options.
To generate graphics, JSCOM3 must either use the headless option or a DISPLAY variable.
Is the host name needed to access the X Windows Server. The server must also accept the connection, which may require using the xhost command.
You can stop the WebFOCUS Reporting Server using the Web Console or as follows:
After installation, the WebFOCUS Reporting Server directory structure is created. The default directory is /ibi and contains three subdirectories:
Contains space for applications and sample data.
Contains space for server profiles.
Contains the server.
Under srv81 are the EDAHOME (home) and EDACONF (wfs) subdirectories:
It contains the following subdirectories:
Contains executable and libraries files.
Contains catalog-related files.
Contains documentation files.
Contains error message, documentation, and additional server files.
Contains graphics and template files.
Contains National Language Support files.
Contains internal files.
EDACONF contains the following subdirectories:
Contains server instance-specific configuration files and utilities.
Contains server instance-specific catalog files.
Contains deferred output and control files.
Contains temporary files and is not created until you start the server.
Contains configuration files.
Contains space for internal processing in some environments.
Contains test files generated during the configuration process.
Contains user-generated temporary files.