In this section:
There are two ways to run the installation utility:
Caution: When updating Developer Studio from a previous release, either apply a service pack installation or completely uninstall the older product before running the full installation. To uninstall Developer Studio, use the Uninstall option in the WebFOCUS XX Developer Studio program group. If you manually delete Developer Studio directories, you may leave files and registry settings that could affect future installations. If prompted to reboot after uninstalling, do so before reinstalling.
The Developer Studio installation can automatically configure one of the following for you:
This document assumes IIS listens on port 80 and Tomcat listens on port 8080. If you change the defaults, substitute accordingly.
You can manually configure a different application server, as explained in Configuring the Web Server or Application Server.
When installing WebFOCUS and Developer Studio on the same machine, do the following:
The Developer Studio installation program will detect that WebFOCUS is already installed and allows you to select and use the WebFOCUS configuration or install Developer Studio with its own configuration. If you select to use the WebFOCUS configuration, the install program will not provide options to automatically configure a web or application server. In this case, you do not need to configure a web or application server for Developer Studio if one is already configured for WebFOCUS on the machine. Developer Studio will use the existing WebFOCUS environment, including the web or application server configuration. All products can coexist and use the WebFOCUS environment through Developer Studio or a browser.
If you choose to create a separate configuration for Developer Studio, you must select the Advanced Configuration option and specify a unique alias for /ibi_apps, /ibi_help, and port for the Developer Studio Reporting Server to avoid conflicts with the WebFOCUS configuration (this should also be done when selecting the option to have multiple installations of Developer Studio).
Follow this procedure to install Developer Studio.
Note: You must be an administrator to the Windows machine to run the installation.
You may receive the Developer Studio installation on a CD or through an Internet download.
The installation begins with a Welcome window.
The license agreement appears.
If an earlier version of the same release of Developer Studio is already installed, you will be prompted to either Update or perform a Full Install.
If you choose Update, the installation begins immediately after selecting the existing version that will be updated, and your older version is replaced. When updating, be sure to reload the web application.
The following image shows the Setup Type dialog box with the Update selection highlighted.
When the Update option is selected (this is the default), the Select existing install to update section displays the installations of Developer Studio that are detected and can be upgraded.
Note: For more information on upgrades, see Upgrade Installation Requirement.
If you choose Full Install, you will be prompted for the product serial number and installation/configuration options.
The following screen shows the Software Registration dialog box.
You are also prompted for the product serial number if no earlier version of Developer Studio is found.
For a CD installation, the serial number can be found on the back of the CD case. It is based on your license agreement and controls the software edition that is installed.
Note: If you wish to use Visual Discovery or a network installation, ensure you have the correct license.
If you type a valid serial number, the Registration Confirmation window opens.
A window appears, describing Developer Studio requirements.
The Select Program Folder window opens, as shown in the following image.
You can change the Program Folder name by adding a suffix. Changing the default name will also change the folder name where Developer Studio will be installed. For example, if the default folder name is WebFOCUS 81 Developer Studio, the product will be installed in a directory with the name...\DevStudio81.
The Choose Destination Location window opens, as shown in the following image.
Accept the default value or click Browse to select a different directory.
Accept the default value or click Browse to select a different directory.
A list of components and options appears, as shown in the following image.
The following installation options appear. If an option is already installed or unavailable, it is grayed out:
Note: This option is not enabled if version 6 or higher is already installed.
Note: This option is not enabled if a supported version of Tomcat is detected.
The following configuration options appear:
Enabling this option through Developer Studio provides a single-user license applicable only to the Developer Studio user and functions against the local Developer Studio environment or against licensed WebFOCUS environments.
This feature must be licensed separately for use in multi-user WebFOCUS environments. This also applies when Developer Studio and WebFOCUS are installed on the same PC.
WebFOCUS RStat includes:
For additional information on WebFOCUS RStat, see the Using WebFOCUS RStat for Predictive Analytics manual available from the Information Builders Technical Documentation library site.
The WebFOCUS RStat software is not included in the Developer Studio package. You can download WebFOCUS RStat from the Customer Support site.
The configuration options are not available if WebFOCUS is detected and you choose to use the WebFOCUS Configuration, if you perform a network installation, or if you install the Managed Reporting Developer edition or Report Developer edition. If WebFOCUS is detected, Developer Studio uses the existing WebFOCUS environment. For a network installation or Managed Reporting Developer edition, you must connect Developer Studio to a WebFOCUS environment after installation.
To manually configure a different application server, deselect the configuration options and refer to Configuring the Web Server or Application Server.
The Start Copying Files window appears.
The installation may take some time.
Note: If you choose the Tomcat connector (plug-in) option and receive a message that says Unable to Create Filter, some manual configuration is required. To do this, open the Internet Services Manager, right-click your website, and choose Properties. On the ISAPI Filters tab, determine if a Jakarta or ServletExec filter appears. If neither appear, click Add and add the isapi_redirect.dll file using the filter name Jakarta. For more information, review the remainder of this chapter and then see Configuring Microsoft IIS to Use the Tomcat Connector (Plug-in). Also, be aware that you cannot use the Tomcat plug-in if ServletExec ISAPI is installed.
You can install multiple versions of Developer Studio on the same machine without being required to upgrade to an existing version. This allows each Developer Studio installation to have its own configuration.
WebFOCUS environments that have already been configured with an earlier version of Developer Studio will be reused. Additionally, any applications that are available on the local PC will also be shared, and accessible by all versions.
Note: Developer preferences and settings will not be preserved when you perform an upgrade installation.
For more information on installing Developer Studio, see Running the Installation and ensure that the following steps are performed so each Developer Studio installation has its own configuration.
For example, if you have 8009 and are installing 8104, name one environment localhost8009, that uses the /ibi_html and /ibi_apps aliases for this configuration, and rename the latest localhost environment to localhost8104. This environment should already have the /ibi_apps alias that was specified for this environment during the installation. If not, update the values as needed.
When you switch between multiple versions of Developer Studio, it is necessary to register the files of the release that you will be using each time you launch the product. Before running the utility that registers these files, you must ensure that you have privileges to run a file called regsvr32.exe, and that the Path System variable is configured properly on your Windows machine so the system files that are located in the Windows\system32 can be accessed.
You can switch between multiple versions of Developer Studio by running a utility called thisfoci.bat. You can also switch between multiple version of Developer Studio 8 by setting a command line switch in the shortcut of the main executable file.
Confirm that you have administrative privileges on your machine, and perform the following steps to ensure that the Path System variable is configured properly.
The Path System variable for your User ID displays, as shown in the following image.
regsvr32.exe is located in your system32 folder. If it is configured properly, your Path System variable should include the following:
Is the drive where your Windows folder resides.
Is where regsvr32.exe is located.
You can configure the Path System variable properly by doing the following:
Is the location of the Windows folder on your machine. This includes the drive and path. It is usually the C drive. For example, C:/Windows.
Follow the steps below if you have installed multiple versions of Developer Studio. For example, if you have installed Developer Studio 7.7 and Developer Studio 8.
Follow the steps below if you have installed multiple versions of Developer Studio 8.
The Properties dialog box opens.
The following image shows an example of this command line switch.
Set this command line switch for each version of Developer Studio that you install. Each time you launch the product from this shortcut, the DLL files will register properly.
After installation, the Developer Studio directory structure is created. The default location is:
The following are some of the main subdirectories. The actual directories may vary based on your license:
Contains applications and data. By default, this is the APPROOT directory where WebFOCUS looks for application files. Sample files are provided in the \ibinccen and \ibisamp directories.
Contains a backup of the cgivars.wfs file. If your main cgivars.wfs configuration becomes corrupt, you can use this backup file to replace a corrupt version.
Contains the graphical front-end components for creating WebFOCUS applications.
Contains WebFOCUS Client configuration files. Many of these files were installed with the WebFOCUS Reporting Server in previous versions. However, the main communications file odin.cfg is still installed under the srv81\wfs\etc directory instead.
Contains the install.cfg that holds information about the installation.
Contains the embedded Derby database files.
Contains webpage components that provide local processing, web-based tools, and other features.
Contains space for logs.
Contains Magnify data and sample applications.
Legacy folder that contains local map tiles, which were used when rendering maps using OpenStreetMap® data.
Contains links for sample applications.
Contains a WebFOCUS Reporting Server installed and configured for Developer Studio.
Contains space for local processing.
Contains reporting and maintain templates.
Contains tools and files for additional configurations.
Contains the WebFOCUS web application.
If you installed Tomcat, the default location is:
If you are using Tomcat and IIS together, the Tomcat plug-in (connector) is installed in:
C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector
Developer Studio creates the installation log file in the following location:
This log file provides information about the Developer Studio installation. If you contact Customer Support Services with an installation problem, have this file available.
If you license the Visual Discovery feature, the following log is created by its installation:
The Developer Studio development tools require certain components installed with the WebFOCUS Reporting Server. Therefore, a Reporting Server is always installed with Developer Studio even when one is already installed, or if you use Developer Studio for remote processing.
This server is configured for Developer Studio and installed within the Developer Studio directory structure. On the Start menu, it is under Programs, Information Builders, WebFOCUS 81 Developer Studio, and WebFOCUS 81 Server for DevStudio.
Note: By default, the server only starts with security OFF and can only be started by the user who installed Developer Studio. To change these defaults, see WebFOCUS Reporting Server Security and User IDs.
If you install Developer Studio on the same machine as WebFOCUS, be sure to configure the server installed for WebFOCUS and not the server installed with Developer Studio. The server installed for WebFOCUS should be started before Developer Studio. Otherwise, Developer Studio starts the server installed with Developer Studio instead.
In this section:
If you are not using Tomcat, proceed to Verifying Developer Studio.
If you installed Tomcat with Developer Studio, the installation is done silently and uses default settings.
If you change defaults, substitute accordingly in procedures and examples. You also need to update the Developer Studio connection settings so it knows the correct Tomcat HTTP port if you change the default. See Tomcat Ports.
If you need any of these web applications, you can download a full version of Tomcat from the Apache Tomcat website at http://tomcat.apache.org.
This secures access to the Tomcat web applications and restricts connections by remote IP addresses or hosts.
Restriction to localhost only connections is done by configuring <catalina_home>\conf\server.xml and adding an entry for address="127.0.0.1" to the segment <Connector port="8080"…/>. For example:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> <Connector port="8080" maxHttpHeaderSize="8192" address="127.0.0.1" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
<catalina_home>\Jakarta Isapi Redirector
If you decide to upgrade your current WebFOCUS Developer Studio installation, you must clear the cache and then recycle your application server after the upgrade process is complete. For example, if you are using Apache Tomcat, the cache can be cleared by manually deleting any subdirectories that correspond to the context roots that you deployed (for example, \ibi_apps, \ibi_html, and \rcaster), which are located in the following directory: