In this section:
ReportCaster configuration parameters are managed within the ReportCaster Console Configuration tab. For additional ReportCaster configuration information, see the ReportCaster manual.
Several scripts allow you to change Distribution Server configuration settings. The Distribution Server cannot start unless it can connect to the repository. If you cannot start the Distribution Server, use these scripts to correct connection settings. The scripts are installed in:
The following scripts are available:
Changes the DB Name parameter. This parameter is only needed when using a DB2 repository on z/OS..
Changes the password used to access the repository.
Changes the user ID used to access the repository.
Changes the JDBC class used to access the repository driver. See Additional WebFOCUS Repository Topics and Tasks for information on this value.
Changes the JDBC URL used to access the repository. See Additional WebFOCUS Repository Topics and Tasks for information on this value.
To run a script, execute it at a shell prompt with the first argument being the value you wish to set.
Warning: If a value contains a semicolon (;), you must place that value between quotation marks.
If during the installation you typed the wrong user ID and password to access the repository, you can change them as follows.
Is the correct user ID to access the repository.
Is the correct password to access the repository.
The other scripts (for example, repurl, repclass) are executed in the same fashion. If your URL or CLASS contains a semicolon (;), place the URL or CLASS between quotation marks when running the scripts.
The size of the ReportCaster log report is limited by the amount of memory available to the Java VM. When the memory of the Java VM is exceeded, a Java OutOfMemoryException error occurs.
To control the size of the log report, you can set the following ReportCaster Server Configuration tool parameters:
If the ReportCaster Distribution Server experiences a Java out of memory error, you must increase the amount of memory (heap size) available to Java on the Distribution Server. This is done by passing parameters on the Java command line, as follows:
java -Xms<initial heap size> -Xmx<maximum heap size>
java -Xms256m -Xmx512m
You must restart the Distribution Server to enable this change.
The Distribution Server Failover feature allows you to configure a backup Distribution Server that can resume ReportCaster operations when there is an interruption (planned or unplanned) in the primary Distribution Server service. The primary Distribution Server is monitored to verify that it is operational. If there is an interruption in service, the failover Distribution Server is triggered to take over the role of the primary server.
The Workload Distribution feature allows ReportCaster to distribute scheduled jobs across multiple Distribution Servers, providing an efficient and fast way to process large numbers of ReportCaster schedules. Multiple Distribution Servers can be installed on one or more hosts. One instance is designated as the Workload Manager, while the others are designated as Workers. The WebFOCUS Repository will be shared by the Workload Manager and the Workers. Workload Distribution is set up through the ReportCaster Configuration tool. All servers will share one set of configuration information, and the Workload Manager will push any configuration changes to the Workers.
For your application of ReportCaster, you can configure either Failover or Workload Distribution, or both at the same time. The following procedure includes instructions to configure both, but notes when to skip to the appropriate steps if you are only configuring one or the other.
To configure distribution server failover:
The Secondary Distribution Server dialog box opens, as shown in the following image.
To configure workload distribution:
The Workload Distribution dialog box opens, as shown in the following image.
Repeat this step for each Worker Distribution Server instance that you want to add.
Support for UTF-8 can be added to the Distribution Server by adding -Dfile.encoding=UTF8 to the Distribution Server Java command. If the Distribution Server is being run from the command line, modify the schbkr script file and add -Dfile.encoding=UTF8 to the Java command.
When the ReportCaster Distribution Server is installed as a stand-alone server, on a machine that is separate from the WebFOCUS Client, you must perform additional manual steps to ensure that configuration changes made through the WebFOCUS Administration Console are available to ReportCaster. This is because the stand-alone Distribution Server does not have access to the WebFOCUS configuration files being updated by the console. This is especially important when configuring external security for WebFOCUS, since your ReportCaster jobs may not run properly if the Distribution Server is not using the same security settings as the WebFOCUS Client.
The recommended procedure is to make changes to WebFOCUS, as per the documentation, and then test them with a web browser. When the settings are verified, perform the following steps to ensure that the configuration is available to ReportCaster:
ReportCaster encryption can be enabled to secure communications between the ReportCaster application and the ReportCaster Distribution Server. For more information, see Distribution Server Settings in the ReportCaster manual.
By default, the Axis Servlet only accepts HTTP requests. If you use ReportCaster Web Services in an SSL environment, you will need to manually configure the Axis Servlet to accept HTTPS requests. To do so, add a second AxisServletListener with the name https to axis2.xml and specify the port parameter for both listeners. The axis2.xml file is located in the ibi/WebFOCUS81/webapps/webfocus/WEB-INF/conf folder.
The following code is an example of a second AxisServletListener.
<transportReceiver name="https" class="org.apache_1_6_2.axis2.transport.http.AxisServletListener"> <parameter name="port">8443</parameter> </transportReceiver>
For more information, see
In order for ReportCaster to distribute graphs, you must either set DISPLAY or use the headless option. This is similar to the Server Side Graphics configuration discussed in Verifying and Troubleshooting Server Side Graphics (PCHOLD).
The procedure for distributing graphs will depend on whether you have an X Windows Server.
To distribute graphs, do one of the following:
Add a line to export the DISPLAY variable. For example:
#!/bin/ksh export DISPLAY=localhost:0 CLASSPATH=/usr/local/drivers/ojdbc15.jar: /home/wf81/ibi/WebFOCUS81/ReportCaster/lib/SCHScheduler.jar export CLASSPATH java ibi.broker.SCHScheduler /home/wf81/ibi/WebFOCUS81/ReportCaster
If you do not have an X server, you can set the headless Java option when the Distribution Server starts. However, this does not support GIF graphs or the older GRAPH32 engine. To set this, edit the following file:
This is current file.
#!/bin/ksh . /users/mktrgm/ibi/WebFOCUS81/ReportCaster/bin/classpath "/users/mktrgm/installsoft/JavaJDKLinuxx64/jdk1.8.0_45/bin/java" -Dreportcaster.home=$DSINSTALL -Dcaster.service=false -DDSINSTALL_PROD=$DSINSTALL_PROD ibi.broker.SCHScheduler $DSINSTALL $CMD_LINE_ARGS
Place the headless option after the java command as shown in the following example.
#!/bin/ksh . /users/mktrgm/ibi/WebFOCUS81/ReportCaster/bin/classpath "/users/mktrgm/installsoft/JavaJDKLinuxx64/jdk1.8.0_45/bin/java" –Djava.awt.headless=true -Dreportcaster.home=$DSINSTALL -Dcaster.service=false -DDSINSTALL_PROD=$DSINSTALL_PROD ibi.broker.SCHScheduler $DSINSTALL $CMD_LINE_ARGS