In this section:
Review the following tips when troubleshooting App Studio.
Since Tomcat runs as a service, Tomcat Java settings and other parameters are written into the registry. They can be configured through the Apache Tomcat Properties window. You can launch this from the Start menu by selecting All Programs, Information Builders, Tomcat, and Tomcat Configuration Utility.
If you need to adjust the Java release, click the Java tab to change where Tomcat looks for Java components. Be aware that Tomcat 8.0 requires Java 7 or later.
Note: Tomcat 8.0 requires Java 7 or later. If Tomcat 8.0 is configured to use Java 6, JSP page compilations will fail. To fix this, update the paths to point to the jvm.dll file of a supported Java version.
If the App Studio installation configured Tomcat for you, the Tomcat Java VM memory settings are automatically increased. This is done because default application server Java VM memory options may not be sufficient for some WebFOCUS features. If you need to troubleshoot further or if you manually install Tomcat or another application server, you may need to manually increase the Java VM memory options.
The most common Java VM options you need to set involve the size of the Java heap and stack, which determine memory availability for Java programs and the Java VM. Errors can occur if not enough memory is available, and the heap size impacts performance, since it determines how often garbage collection occurs.
The following are the most common Java VM options related to memory settings. Replace the ### with the size you wish to set:
Sets the maximum Java heap size. It is common to make this 1/4 of the system RAM.
Sets the initial Java heap size. It is common to make this 1/8 of the system RAM.
Sets the Java thread stack size. You do not need to set this unless you are fine tuning your environment.
The size is normally set in megabytes, for example:
Optimum sizes vary depending on your total memory, the needs of your application, how many other processes require memory, the type of Java VM, and other considerations. A good starting place is to set the minimum to 1/8 of the total RAM and set the maximum to 1/4 of total RAM.
Where to set these and other Java VM options depend on your application server.
If you close App Studio and then cannot restart it, you may need to manually stop the underlying focshell.exe process. To do this:
Note: You can click the Image Name column to sort by name.
You should be able to restart App Studio if no focshell.exe processes appear.
As of App Studio Release 8.1 Version 03, developers can use Chrome™, Firefox®, Internet Explorer®, or the internal viewer when running reports. To use Chrome or Firefox, the product requires registration of the IBIWebBrowserDrivers_dotnet_35.dll .NET module that is included with the product.
To register this file, .NET version 4.0 is required. This version of .NET is preinstalled on most machines. If your machine does not have this .NET version, it will be installed during the App Studio installation process and the module needed to support multiple browsers will get registered.
In a few cases, on Windows 8.1 machines where the registration of the module fails, the developer will not be able to switch browsers. To address this issue, the developer must register the required module manually. To do this, open a Command Window, with the option Run as administrator, and run the following commands:
%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\RegAsm C:\ibi\AppStudio81\bin\ibiwebbrowserdrivers_dotnet_35.dll /u
A message should display that the file unregistered successfully.
A message should display that the file registered successfully.
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.