In this section:
After the repository is created, you should test the WebFOCUS Client and the ReportCaster configuration.
If you have problems with the verification, see Troubleshooting WebFOCUS and ReportCaster.
Make sure you have carried out the procedures in the preceding chapters before starting the Distribution Server.
Before starting or testing the Distribution Server, components it communicates with must be started. These include the following:
This section describes how to test the WebFOCUS Client.
Are the host name and HTTP port of the web server or application server. If you require SSL, use https instead of http.
The WebFOCUS Sign In page opens, as shown in the following image.
Note: If you receive a page not found error, ensure that your application server is started and that you have deployed the WebFOCUS application. For more information on configuring your application server, see Installing the WebFOCUS Client.
Note: If you receive an invalid user name or password error, ensure that the WebFOCUS repository has been created and contains initial table data.
The WebFOCUS BI Portal page appears, as shown in the following image.
You can change the default credentials using the Security Center facility. To do this, click Administration from the top menu and then click Security Center. For more information, see the WebFOCUS Security and Administration manual.
This section describes how to start and stop the ReportCaster Distribution Server.
To start the Distribution Server, use the following procedure:
When the Distribution Server starts, you receive output similar to the following, depending on which components you installed:
Console is listening on port: 8200 Reader ready Dispatcher ready Console ready
When the Console Ready line appears, the Distribution Server is started.
Note: The Distribution Server will start in Console mode if it cannot connect to the repository, or if your repository is for an earlier release. ReportCaster must use a valid 8.1 Repository.
To stop the Distribution Server, do the following:
netstat -a | grep 8200
Is the port for the Distribution Server.
If you receive a response that says LISTEN:
tcp 0 0 *:8200 *:* LISTEN
Then the Distribution Server has not yet stopped. Wait a few minutes and try again. If it still has not stopped, you can manually kill the process. To do this, sign in as root and issue
netstat -nlp | grep 8200
Then, kill the process that appears at the end of the line.
When running the Distribution Server in production, you should start it using the nohup command. This ensures that the Distribution Server remains running if you close telnet or SSH sessions. To do this:
nohup ./schbkr &
Output is written to an nohup.out file.
After the ReportCaster Distribution Server is started, test the ReportCaster configuration by accessing ReportCaster interfaces.
The ReportCaster Console opens, as shown in the following image.