In this section:
After installing the WebFOCUS Reporting Server, verify that it runs properly by performing tests and viewing the Web Console as explained in this section.
There are several security levels in which you can start the WebFOCUS Reporting Server. For a description of these levels, see Introducing WebFOCUS and ReportCaster Installation.
Note: When the installation program completed, you had the option to start the WebFOCUS Reporting Server, so it may already be running.
How you start the WebFOCUS Reporting Server depends on the security level, as follows:
From the Start menu, select Programs, Information Builders, WebFOCUS 81 Server, and then Start Security ON.
From the Start menu, select Programs, Information Builders, WebFOCUS 81 Server, and then Start Security OFF.
Note: If you want to use any other security mode (for example, security OPSYS or security PTH), you must configure the security mode in the Reporting Server Web Console page. For more information, see the Reporting Server Online Help (Select Server Security, then Server Security Overview/Security Providers or Configuring Authentication).
Security DBMS and Security LDAP require configuration before they can be used. For more information on these security modes, see the Server Administration manual.
Note: If you see an error in the server command window related to JSCOM3, you will fix this in How to Verify or Enable the JSCOM3 Listener.
The Web Console provides an interface for configuring, monitoring, and testing the WebFOCUS Reporting Server. You will use the Web Console, sometimes referred to as the Server Console, to test the installation and become familiar with administrative features.
To access the Web Console and test the server:
From the WebFOCUS Reporting Server machine, select Start, Programs, Information Builders, WebFOCUS 81 Server, and then Web Console.
From a remote machine, type the following path in Internet Explorer:
Is the hostname or IP address of the machine running the WebFOCUS Reporting Server.
Is the HTTP port you specified during the installation. This is normally one more than the TCP port. The default is 8121. This is the port of the LST_HTTP node in drive:\ibi\srv81\wfs\etc\odin.cfg.
The Web Console home page appears.
If you receive a message similar to the following
'admin_id' has no valid member
you probably did not type your correct Windows password during installation and the server is running in safe mode. To correct this error, click fix now to bring up the Access Control page. Then on the left, under Users and Server Administrator, click your user ID, and choose Properties. Provide and confirm your Windows password, and click Apply and Restart. When the server restarts, click the Home icon in the upper-left corner.
A sample report will display.
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. You can optionally click Properties if you wish to change any default settings. To continue, proceed to Stopping the WebFOCUS Reporting Server.
If the Start option appears, then JSCOM3 did not start. JSCOM3 cannot start unless your search PATH contains the jvm.dll file for your Java release. The jvm.dll file is installed with the JDK/JRE in the jre\bin\client directory.
The exact JDK directory varies depending on your Java release. For a different JDK release, substitute accordingly. If JSCOM3 does not start, add this directory to your 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.
Note: If you plan to install WebFOCUS Client on the same machine, you can install WebFOCUS Client first. You can then complete this procedure after the WebFOCUS Client installation completes.
If you are using a different JDK, substitute accordingly.
Note: Use semicolons (;) to separate paths. Do not include spaces between the semicolons and the paths.
JSCOM3 listening on tcp port 8123
Note: In some environments, you need to reboot before the server finds the jvm.dll file.
There are three ways to stop the WebFOCUS Reporting Server.
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 copies of the Windows system 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.