View Café Configuration Files and Troubleshooting

Configuration Files

View Café Plugin Configuration Files

Location: yourEbVirDir\PlugIns\ViewCafe\Components

Build.properties – Contains the version information for the installed View Café plugin components.

ClientGui.properties – Controls what menu items are displayed in the View Café applet. This file normally is not changed, but customers can use it to restrict what menu commands are made available to all users. It can also be used to create custom UI Profiles.

Document.properties – This file is never changed.

View Café Server Configuration Files

Location: C:\Program Files\Enterprise Informatics\eB\Shared\WebViewer

AppServer.properties – Defines the machine name and port settings for the View Café application service. This file is typically only modified if multiple NICs exist or the port upon which the View Café application pagesare monitored on conflicts with an existing application (see subsequent sections for details).

AppServerGUI.properties – Don’t modify.

AppService.ini – Don’t modify.

Build.properties – Don’t modify. You can use this for troubleshooting version mismatches between the View Café plugin and server.

CoreServer.properties - Defines the machine name and port settings for the View Café core service. This file is typically only modified if multiple NICs exist or the port upon which the View Café core server pagesare monitored on conflicts with an existing application (see subsequent sections for details). Core server logging is also configured in this file (see subsequent section for details).

CoreService.ini – Don’t modify.

DHService.ini – Don’t modify.

Document.properties – Don’t modify.

DocumentHandler.properties - Defines the machine name and port settings for the View Café document handler service, which is actually a custom service created by Enterprise Informatics. This file is typically only modified if multiple NICs exist or if alternate directories need to be configured for the View Café cache.

LicenseGUI.properties – Don’t modify.

LicenseManager.properties - Defines the machine name and port settings for the View Café license manager service. This file is typically only modified if multiple NICs exist or the port upon which the View Café license manager pages are monitored on conflicts with an existing application (see subsequent sections for details).

LicService.ini – Don’t modify.

View Café Plugin Web Pages

Location: yourEbVirDir\PlugIns\ViewCafe

ViewSelection.aspx - This is an asp.net web page that may have to be modified for customers requiring advanced 3D viewing. To enable 3D viewing you must replace all instances of viewcafe.jar with viewcafe3D.jar. When a client attempts to view after changing this setting the View Café applet should automatically download and install the required JRE 3D runtime.

Troubleshooting View Café Viewing Errors

Client Messages

The first thing to do when you can’t view is to gather data from the client. The first place to look is the Java console which can be accessed from the Java Icon in the System Tray:

Right click on the above icon and select the menu item that contains the word “Console”. This will bring up a text box with detailed information on why the operation failed. The customer can copy and past this information and send it to us.

Server Messages

There are two methods for gathering data on the View Café server. The first is to run the debugall.bat file which is located in C:\Program Files\Enterprise Informatics\eB\Shared\Webviewer. Run it from a command (DOS) prompt. Four separate command prompts should appear, looking something like this:

The above example indicates a successful start of the four View Café services. Note that the “Now destroying JVM” message is normal. Error messages will be displayed in the above dialogs either upon startup or when attempting to view a file. If one or more of the command prompts do not stay up, you will need to run a command from the command prompt individually for each one that did not stay up. The related commands are shown below:

AppService -debug

CoreService -debug

DHService -debug

LicService -debug

The following example shows output indicating that the license file is missing when running “licservice –debug”:

Debugging ViewCafe License Manager.

Now starting JVM

ControlHandler registered after JVM start

com.spicer.license.LicenseFileException: License directory .\Licenses does not e

xist

at com.spicer.license.LicenseManagerImpl.a(Unknown Source)

at com.spicer.license.LicenseManagerImpl.<init>(Unknown Source)

at com.spicer.license.LicenseManagerImpl.main(Unknown Source)

The second method for gathering data from the View Café server is to turn logging on for the View Café Core Service. This is done by changing the following line within the Coreserver.Properties file within the C:\Program Files\EnterpriseInformatics\eB\Shared\Webviewer directory:

# The following is useful when running the Core Server as a service. Look

# for corserver*.txt files in the directory containing the Core Server.

#OutputToFile=true // Uncomment this line to write log files

# The size of the log file be limited to a number of lines or

# age of entires. The log files are adjusted overnight.

TruncateDays=7

#TruncateLines=1000

As the inline comments indicate, uncomment the “OutputToFile” line so that coreservernnn.txt files are written containing logging information.

Monitoring View Café Services

License Monitor Page

You can see the current status of the View Café license service, including information regarding current connections and license usage. Point your browser to the machine name (or localhost) and the port setting indicated in the LicenseManager.properties file within your …\eB\Shared\Webviewer directory (i.e.

# Use this setting to change the port that the App Server Pages are monitored on.

Port=9090

A sample page is shown below:

AppService Monitor Page

You can also view AppServer information by pointing your browser to the application server port number indicated in the AppServer.Properties file:

# Use this setting to change the port that the App Server Pages are monitored on.

Port=9080

For example, will display the following:

You can click on the Core Server Name (i.e. Core Server 1 in the above example) to view information regarding clients that are currently connected:

There is also a “View log file” link in the above page that can view information contained in the Core Server log file.

Common Viewing Problems

Missing Markup Interface

By default the View Café markup interface is disabled. To enable it make the following change in the web.config file for your eB Virtual Directory (i.e. c:\inetpub\wwwroot\eB\web.config):

applicationSettings

...

<eB.PlugIn.ViewCafe.Properties.Settings

...

<value>markup</value>

</setting>

...

</eB.PlugIn.ViewCafe.Properties.Settings

...

</applicationSettings

Once the setting is enabled, you should see the following interface components in the View Café applet:

Note: If you still do not see the markup components it is possible that the currently logged on eB user does not have markup permissions.

Case Sensitivity for the UIProfile

If you get a blank gray screen when trying to view a file and the java console error text starts out with the following it is likely that the view/markup setting described in the previous section was entered in the wrong case. It must be specified in all lower case!

java.lang.NullPointerException

at com.spicer.c.cc.a(Unknown Source)

at com.spicer.client.bu.a(Unknown Source)

at com.spicer.client.ViewCafe.b(Unknown Source)

at com.spicer.client.ge.run(Unknown Source)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

Exception in thread "Thread-16" java.lang.NullPointerException

at com.spicer.c.en.a(Unknown Source)

at com.spicer.c.en.c(Unknown Source)

at com.spicer.c.ee.run(Unknown Source)

2010.01.27-18:23:44 (Error): API Error: assign(eb_cache_server,localhost)

java.lang.NullPointerException

at com.spicer.client.bd.f(Unknown Source)

at com.spicer.client.bd.h(Unknown Source)

at com.spicer.client.bd.a(Unknown Source)

at com.spicer.client.bi.a(Unknown Source)

Multiple NICs

When running multiple Network Interface Cards (NIC) on the same computer you must set the IP address for the appropriate card in the View Café Properties files, all located in C:\Program Files\Enterprise Informatics\eB\Shared\WebViewer (an example IP address of 10.213.2.22 is used):

AppServer.properties

...

RMIPort=1099

Name=//10.213.2.22:1099/AppServer

RefreshTime=15

...

CoreServer.properties

...

DocumentHandler.Name=//10.213.2.22:1099/DocumentHandler

LicenseManager.Name=//10.213.2.22:1099/LicenseManager

AppServer.Name=//10.213.2.22:1099/AppServer

...

DocumentHandler.properties

...

# Name and port for RMI

RMIPort=1099

Name=//10.213.2.22:1099/DocumentHandler

...

LicenseManager.properties

...

RMIPort=1099

Name=//10.213.2.22:1099/LicenseManager

...

You may also need to change the web.config file to indicate the specific NIC:

<value>PutYourIPAddressHere</value>

View Café with Windows Authentication

There was an issue when running windows authentication with View Café. If you get a “class not found” error, try pointing your browser directly to the ViewCafe.jar file (i.e. If you get a permission error then try enabling Integrated windows authentication as shown in the following illustration:

Security Settings Preventing the JRE from Being Installed

If you get the following error message in the Java Console

java.io.IOException: Server returned HTTP response code: 401 for URL:

at sun.net. Source)

at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

at sun.net. Source)

at sun.plugin.net.protocol.http.HttpURLConnection.checkCookieHeader(Unknown Source)

at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

at sun.plugin.net.protocol.http.HttpUtils.followRedirects(Unknown Source)

at sun.plugin.cache.CachedJarLoader.download(Unknown Source)

It is likely that the corporate security policy for the customer is not permitting the Java Runtime to be installed. If this is the case the customer will have to manually install the required Java Runtime.

Unable to View On Remote Client

If you are able to view within a Browser on the same machine where View Café is running but not on remote machines it may be due to the following incorrect setting on web.config:

Change:

<value>localhost</value>

</setting>

To:

</setting>

This was an issue with the 14.x installer but has been fixed in recent versions of eB.

Miscellaneous Error Messages in the Java Console

Java.lang.ExceptionInInitializer Error

If you see this error in your java console on the client. This is most likely a case of a missing or corrupt *.properties file in \wwwroot\eB1522\PlugIns\ViewCafe\Components\. It can also occur if the necessary mime types to not exist for the eB Virtual directory. The mime types are automatically defined when creating an eB virtual directory using the eB Web Manager tool, but may not exist if a customer manually created the directory. The required mime types are as follows:

.jarapplication/jar-archive

.propertiestext/plain

java.lang.NoClassDefFoundError: Could not initialize class com.spicer.client.bc

This is also due to missing mime types. For eB 14.5.1 running on Windows 2008 server you have to manually create the mime types.

java.rmi.UnmarshalException Error or

Exception in thread "AWT-EventQueue-2" java.lang.NoClassDefFoundError:

These messages typically indicate that the version of View Café in your virtual directory do not match the version on your View Café server. Make sure that the versions indicated in the following files match:

yourEbVirtualDir\PlugIns\ViewCafe\Components\Build.Properties (on the eB Web Server)

C:\Program Files\Enterprise Informatics\eB\Shared\WebViewer\Build.Properties (on the View Café Server)

java.lang.NullPointerException Errors

There are several possible causes for this error.

Missing Java 3D runtime.

If you specify viewcafe3d.jar in your yourEbVirtualDir\PlugIns\ViewCafe\ViewSelection.aspx file and the Java 3D runtime could not be automatically installed you will get this error. If you do not need to specifically view 3D vector files, change ViewSelection.aspx to just include ViewCafe.jar. If you do need to view 3D files then manually install the Java 3D runtime.

sdfd

com.spicer.serverapi.APIException: Could not contact cache server on machine

This is one of the few View Café error messages that provide meaningful information. Make sure that the eB Cache Manager exists in the eB SMC and that it is started. You may have to restart the eB Service Manager for it to show up.

Miscellaneous View Café Server Errors

This section describes possible solutions for error messages that show up on the View Café server. These error messages can be found either in the CoreService log files (see previous section) or in the command consoles when running the View Café services from the debugall.bat batch file.

java.lang.NoClassDefFoundError

This error will occur if either the jrepath or wrkdir setting in one or more of the View Café server ini files is incorrect:

Appservice.ini

Coreservice.ini

DHService.ini

LicService.ini

The eB Viewer Server installer makes sure that the values are correct, but a customer may have accidently modified them.

java.lang.RuntimeException: Native Error: Could not initialize file load library

This error is often caused when one or more image.exe processes are hung. Open Task Manager and kill all image.exe processes running on the View Café server.