test

Project WebSynergy Milestone 4 Administration Guide

Chapter 11 Troubleshooting

This chapter contains troubleshooting information for some of the issue that you may face when you are working with WebSynergy.

Troubleshooting for the Issues Related with Installation

If you are deploying WebSynergy on an existing installation of GlassFish, you need to determine the install location of GlassFish. If GlassFish is installed at the root directory, you can deploy WebSynergy either at the root directory or at the user directory. If GlassFish is installed at your user directory, you must install WebSynergy at the same user directory.

In the scenario involving JDK, GlassFish, and WebSynergy; WebSynergy is at the top layer, GlassFish is in the middle layer, and JDK is in the bottom layer. When you are using the GlassFish WebSynergy bundle, you need to determine the install location of JDK. If JDK is at the root directory, you can install the bundle either at the root directory or at your user directory. If JDK is installed at the user directory, you need to install the bundle at the same directory.

Note –

It is a good practice to have your GlassFish installation dedicated only for running WebSynergy.

Suppose you have JDK 1.5 installed in the root directly and you have installed JDK 1.6 in your user directory. Because WebSynergy often works better on a more recent JDK version, you might want to override the installation at the root directory.

ProcedureTo Reset the JAVA_HOME Variable to the User Directory

  1. Type the following commands in a terminal window:

    export JAVA_HOME JDK-install-dir
export PATH=$JAVA_HOME/bin:$PATH

  2. To verify the change, type the following command:

    echo $JAVA_HOME

    The new directory should be listed.

ProcedureTo Set the JAVA_HOME Environment Variable to the User Directory on Non Solaris Operating Systems

  1. Open the GlassFish-install-dir/config/asenv.conf/asenv.bat file.

  2. Set the AS_JAVA variable to the JDK 1.6 user installation.

  3. Reinstall the WebSynergy bundle and start the domain.

Troubleshooting for Issues Related with Accessing the HTTP Instance

You can access the HTTP instance for the WebSynergy installation on your machine at http://localhost:8080/. In case you are installing WebSynergy on a remote machine, you access the HTTP instance at http://<machine-name>:8080/.

Troubleshooting for Issues Related with User Activities

Users may face some issues when they are working with WebSynergy. Workaround for those issues are discussed in this section.

ProcedureTo Create a Private Page

If your user account has only public pages and you want to add a private page to it, follow the below procedure.

  1. Choose Control Panel from the welcome dock.

  2. Click on My Pages under My Account.

  3. Click on the Private Pages tab.

  4. Specify a name for the page and click on the Add Page button.

Troubleshooting for Issues Related with Installing Plugins

The property called auto.deploy.dest.dir is essential for installing plugins. If you are failing to install plugins, the reason can be that the property is not defined properly. GlassFish defines the hot deploy folder as a folder called autodeploy inside of the domain folder in which your server is running. By default, this is in <Glassfish Home>/domains/domain1/autodeploy. JBoss defines the hot deploy folder as a root folder inside of the particular server configuration you are using. By default, this is in <JBoss Home>/server/default/deploy. WebLogic defines this folder inside of the domain directory. By default, this is in <Bea Home>/user_projects/domains/<domain name>/ autodeploy.

You will first need to determine where the hot deploy folder is for the container you are running. Consult your product documentation for this. Once you have this value, there are two places in which you can set it: the portal-ext.properties file and in the Plugin Installer portlet.

To change this setting in the portal-ext.properties file, browse to where WebSynergy was deployed in your application server. Inside of this folder should be a WEB-INF/classes folder. Here you will find the portal-ext.properties file. Open this file in a text editor and look for the property auto.deploy.dest.dir. If it does not appear in the file, you can add it. The safest way to set this property is to define the property using an absolute path from the root of your file system to your application server's hot deploy folder. For example, if you are using GlassFish, and you have the server installed in /java/glassfish, your auto.deploy.dest.dir property would look like the following:


auto.deploy.dest.dir=/java/glassfish/domains/domain1/autodeploy

Remember, if you are on a Windows system, use forward slashes instead of back slashes, like so:


auto.deploy.dest.dir=C:/java/glassfish/domains/domain1/autodeploy

Save the file and then restart your container. Now plugins should install correctly.

Common Questions

The following are some commonly asked questions about WebSynergy software.

Question:

What databases does WebSynergy support?

Answer:

HSQL, MySQL, Microsoft SQL, and Oracle 10g.

Question:

What is the recommended JDK version to use with WebSynergy?

Answer:

JDK 1.6.0_07 later. Also make sure that Ant 1.7.0 is installed on the machine on which you are installing WebSynergy.

Question:

What can I do if the Compose link does not working in the Mail portlet?

Answer:

Click the compose window twice to activate the window.

Question:

What size image should I use for my site logo?

Answer:

It is recommended that your site logo be no larger than 50 x 50 pixels.

Question:

What is BSOJ?

Answer:

BSOJ stands for big screen of junk (text characters). You may sometimes encounter this when some error has occurred in the WebSynergy user interface. If you encounter a BSOJ, the workaround is to log out of WebSynergy, close your browser, then reopen the browser and log in again.

Question:

What is the recommended amount of memory (RAM) to use with WebSynergy?

Answer:

It is recommended that the machine on which a WebSynergy server is running has a minimum of 2GB RAM. Client machines connecting to a WebSynergy site should have a minimum of 1GB RAM.

Question:

What Web browser is recommended for use with WebSynergy?

Answer:

Firefox 2.x or 3.x are recommended and are the test bases on which WebSynergy has been most extensively tested. Microsoft Internet Explorer is know to have some incompatibilities with WebSynergy.

Question:

On what port does WebSynergy run?

Answer:

By default, WebSynergy runs on port 8080. The port can be changed later, but the WebSynergy installation program runs on port 8080, so this port must be free before you start the installation process. If upgrading from a previous WebSynergy installation, be sure to stop any running GlassFish domains before proceeding.

Question:

How to create a custom portlet bundle?

Answer:

You can use Add Application to add portlets and widgets to a page. You can add portlets and widgets to the public pages and private pages of Communities and Organizations and propagate those Communities and organizations to production environment. the portlets and widgets thus bundled with a Community or an Organization can be considered as custom portlet bundles.