Installing Multiple WebFOCUS Instances on the Same Machine

Topics:

You can run multiple copies (instances) of WebFOCUS on the same machine, if necessary. To do this, install WebFOCUS multiple times, making sure to change default locations, program folders, and ports.

This section provides an overview. Detailed information varies depending on your web server and application server.

Installing Additional WebFOCUS Instances

No special steps are required to install and configure the first instance of WebFOCUS. If WebFOCUS is already installed and you just wish to add a second instance, you can keep the existing instance as is. However, if no WebFOCUS instances have been installed yet, you may wish to use non-default locations and names for all instances.

When installing a second WebFOCUS instance, keep the following in mind:

  • When installing the second WebFOCUS Reporting Server, do not choose to update an existing installation or create a new configuration. Instead, run a completely new installation.

    If a WebFOCUS Reporting Server is already installed, select No if prompted to replace the existing installation. If multiple WebFOCUS Reporting Servers are installed, select the New Installation/Configuration option to not upgrade any of them.

    Note: It is possible to use the same WebFOCUS Reporting Server with two instances of WebFOCUS Client.

  • Place the components for each instance in a different directory. Some WebFOCUS components must be installed in an \ibi\ directory, so use root directories such as:
    C:\wfTest\ibi
    C:\wfDev\ibi
  • Change the default program folders when installing additional instances. For example, add some text to the end of the default names.
    • WebFOCUS 82 Server - Test
    • WebFOCUS 82 Server - Dev
    • WebFOCUS 82 - Test
    • WebFOCUS 82 - Dev
    • ReportCaster 82 - Test
    • ReportCaster 82 - Dev
  • Change the default ports for the WebFOCUS Reporting Server and ReportCaster Distribution Server, so that each instance uses a different set of ports.

  • When specifying the web server host name, be sure to use the correct port and the exact host name you will use for the website. If this is a separate port, provide the correct port. If this is a virtual host name, be sure to use the name you will set up in the DNS, including the domain.
  • For the WebFOCUS repository, create a separate instance.
  • If you are using IIS, ensure you are using a server operating system.
  • Do not choose any of the automatic web server or application server configuration options for additional WebFOCUS instances. You must manually configure all but the first WebFOCUS instance you install.

Install WebFOCUS components, keeping these points in mind. For details, see Installing the WebFOCUS Reporting Server and Installing WebFOCUS Client.

Configuring Multiple Web and Application Servers

Each instance of WebFOCUS requires a separate web server, website, or application server instance. You can set up each web server or application server instance to either listen on a separate port or use a virtual host name. Your options depend on whether you use Apache Tomcat with or without Microsoft IIS.

  • Apache Tomcat Stand-alone

    When using Tomcat as both the web server and application server, you run two separate instances of Tomcat and set them up to listen on different ports. For example, you could access one WebFOCUS instance at:

    http://hostname:8080/ibi_apps/WFServlet

    and the other WebFOCUS instance at:

    http://hostname:9080/ibi_apps/WFServlet

    To create a second Tomcat 8.0 instance, you can copy the Tomcat directory structure, set unique ports, and create a new service using the tomcat8.exe //IS//Tomcat8Test option. You must then edit the registry values for the new service so they are similar to those for the default service, but specify the new instance paths.

  • Microsoft IIS with Apache Tomcat

    Microsoft IIS can be used as the web server, while Tomcat can be used as the application server. This can involve IIS listening on separate ports or using the HTTP host header (virtual host name) feature.

    When using virtual host names, you configure the DNS server so that multiple host names resolve to the same machine. When IIS receives a request for a webpage or other resource, IIS can determine which host name was used when the request was made by looking at the HTTP host header. IIS then uses the host name to determine which website was requested.

    For example, if you are using virtual host names, you could access one instance of WebFOCUS at:

    http://www.wfDevhost.com/ibi_apps/WFServlet

    and the other WebFOCUS instance at:

    http://www.wfTesthost.com/ibi_apps/WFServlet

    Although different host names are used, they both resolve to the same machine and are received by the same IIS web server.

    For Tomcat with IIS, you run two separate instances of Tomcat and set them up to listen on different ports. You then create two IIS websites and ensure that each IIS website sends servlet requests to a different Tomcat instance. You can configure the two IIS websites to either use different ports or virtual host names.

    To create a second Tomcat 8.0 instance, copy the Tomcat directory structure, set unique ports, and create a new service using the tomcat8.exe //IS//Tomcat8Test option. You must then edit the registry values for the new service so they are similar to those for the default service, but specify the new instance paths. This will be explained in a forthcoming technical memo.

WebFOCUS

Feedback