Mozilla is an award-winning open source
cross platform Internet application suite including a web browser, e-mail client, address book, web page composer and chat application with extensive international support. Special features include: Profile Roaming,
and Accessibility features. For details please visit:
www.sun.com/software/solaris/browser/
Release Notes
What's new? (What's different from last version and why you should upgrade.)
What is different from the community version of Mozilla?
Installation Guide
Step by step installation instructions for Mozilla 1.4 for Sun Java™ Desktop System (Solaris Operating System Edition)
Troubleshooting Guide
Having technical difficulties? Consult the troubleshooting guide to find a solution.
Feedback
We want to hear from you!
Support
Mozilla 1.4 is covered by Sun Services' support offerings for the Solaris OS. If you already have a support contract for Solaris OS, you
are entitled to support.
For more information about Sun Services and its support offerings, visit http://sun.com/service/support/software
Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
California 95054 U.S.A. All rights reserved.
Sun, Sun Microsystems, Java, SunOS, OpenWindows, and Solaris are trademarks,
registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S.A.
and other countries. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. in the U.S.A.
and other countries. Products bearing SPARC trademarks are based upon an
architecture developed by Sun Microsystems, Inc.
How to install Mozilla 1.4 for Solaris OS - Web Start edition
After downloading Mozilla, perform the following steps to
install the application.
1. Use the following command to extract the files:
% unzip <installation package name>.zip
2. Change to the Mozilla installation directory:
% cd MOZinstaller
3. If there is no GTK2 library on your system, please perform steps 4
through 7
to install the library. Otherwise, go to step 8.
4. If you are not root already, become the root user by typing "su",
then type your root password.
5. Change to the GTK2 directory:
#
cd GTK2
6. Run the GTK2 library install script:
#
./GTK2install
7. Change to the Mozilla installation directory:
#
cd ..
8. Run the Mozilla 1.4 install script:
#
./installer
9. You will need to choose "Custom install" to install language
packages other than English.
10. Specify the directory to install Mozilla.
By default, a "Mozilla" directory will be created in
your home directory
and Mozilla will be installed there.
11. Select language packages which you want to install.
12. Follow the on-screen instructions to complete the installation
process.
Wait until you see the "Installation Summary" window
come up to inform
you whether the installation was successful.
13. Click "Exit" to close Installer.
14. To start Mozilla, change to the installation directory and run the
following program:
% ./mozilla &
If you do not have the GTK2 library on your system and directly run the
Mozilla installer
script as a common user, you will see these messages:
"Sun Mozilla 1.4 requires the GTK2 library, you can install GNOME 2.0
which includes GTK2
or install GTK2 only"
"To install GTK2 only, you should go to the GTK2 directory and run
GTK2install as root".
How to install Mozilla 1.4 for Solaris OS - SVR4 Packages
Make sure you have installed GNOME2 (which includes GTK2) or the
GTK2 library separately on your system.
1. Before unzipping the files make a directory to place the files
in, change to the new directory and unzip the files using the
unzip command.
% mkdir <new directory
name>
% cd <new directory name>
% unzip <installation package
name>.zip
2. If you are not root already, become the root user by typing "su",
then type your root password.
3. If you have GTK2 or GNOME2 skip to step 5
Change to the GTK2 directory:
#
cd GTK2
4. Run the GTK2 library install script:
#
./GTK2install
5. Install Mozilla by running the install script:
# ./mozinstall
Note - The Mozilla 1.4 packages will be
installed in
the /usr/sfw/lib/mozilla directory on your
workstation.
6 Install the language package
The installer prompts you with a list of languages which you can install, enter the number corresponding to the language package and hit enter.
Rrepeat this step for each language you want to add. Enter 0 and enter to continue the installation.
7. Exit superuser by typing "exit" at the prompt.
8. To start Mozilla, change to the installation directory and run the
following program:
% ./mozilla &
Upgrading from Mozilla1.2.1 to Mozilla1.4
Web Start - If you wish to keep
your old version of Mozilla then install Mozilla 1.4 in a separate
directory inside your home directory, the two can coexist.
Otherwise refer to the uninstall directions that came with Mozilla 1.2.1
SVR4 - If you installed
Mozilla 1.2.1 SVR4 packages (pkgadd version), you should remove Mozilla
1.2.1 first using pkgrm as root and then install Mozilla 1.4.
Note: When upgrading from an earlier version of Mozilla (to avoid incompatibility problem with previous versions) the Mozilla installer will prompt you to delete the install directory if it is not empty. Answer NO if you put your profile or other personal files in the install directory, otherwise the files will be deleted. Users who put profiles in the default location are not affected.
Migrating from Netscape 4.7x to Mozilla 1.4
If you decide to try out Mozilla 1.4 for Solaris OS, it will
not affect your ability to use Netscape 4.7x. Both these applications
can be running at the same time.
However, it is not recommended to use two
mail clients simultaneously.
Netscape 4.7x and Mozilla 1.4 for Solaris
write the user's information (preferences, cache files, bookmarks) into
different directories:
Netscape 4.7x - under a ~/.netscape directory.
Mozilla 1.4 for Solaris - under a ~/.mozilla directory.
During the migration of your Netscape 4.7x preferences such as
bookmarks, proxy servers and email setup, a copy of preference files,
email setup and local mail folder is made by default.
The copy of local
mail folders can waste lot of disk space and may be undesired. We offer
you two choices to control the behavior of local mail folder migration.
Option #1: Re-use the old local mail folders created using
Netscape 4.7x. In addition to saving disk space this allows one to
switch back and forth between Netscape 4.7x mailer and Mozilla mailer.
NOTE: There is a possibility of local mail folder data
corruption if Netscape 4.7x and Mozilla mailers are run at the same
time using the same shared local mail folders.
Option #2: (Default) Keep the local mail folders separate
from Netscape 4.7x and Mozilla 1.4 for Solaris to allow simultaneous
use of Netscape 4.7x and Mozilla mailers.
At the expense of extra disk
space and fragmenting the local mail folder, this option ensures that
you never lose any data stored in local mail folder.
The above choice is given to first time users of Mozilla 1.4 who
are migrating from Netscape 4.7x. System administrators and Enterprise
administrators can make this decision for their wider user base.
They
can change the default settings for their users and choose to allow
them an ability to override the default (or deny override) using the
following preference settings.
To set the choice to option #1 and disallow override ability to
your users, edit the file <Mozilla installation directory>/defaults/pref/mailnews.js
pref("mail.migration.copyMailFiles", false);
pref("mail.migration.copyMailFilesPopupWindow", false);
To set the choice to option #1 but allow override to users, edit
the file <Mozilla installation directory>/defaults/pref/mailnews.js
pref("mail.migration.copyMailFiles", false);
pref("mail.migration.copyMailFilesPopupWindow", true);
Migrating from Netscape 6 or 7 to Mozilla 1.4
You can safely install Mozilla 1.4 with Netscape 7. Mozilla can import user data from Netscape 7; If you wish to migrate from Netscape 7 to Mozilla, we recommend that you uninstall the Netscape 7 after you have both installed Mozilla and have migrated your user data.
Your Netscape 6 or 7 profiles will be available to Mozilla. However, sharing profiles between Netscape 6 or 7 and Mozilla can cause problems.
Mozilla automatically uses your Netscape profile unless you have multiple profiles, in which case Mozilla prompts you to choose a profile. To avoid accidentally opening Mozilla with your Netscape profile, create a new, extra profile using your Netscape's Profile Manager before installing Mozilla.
Note: Upgrading from netscape 6 or 7 (to avoid incompatibility problem with previous versions) the Mozilla installer will prompt you to delete the install directory if it is not empty. Answer NO if you put your profile or other personal files in the install directory, otherwise the files will be deleted. Users who put profiles in the default location are not affected.
Note: It is strongly suggested that you do not share profiles between Mozilla and Netscape 6 or 7
Adding Mozilla to Your Path
Determine where your PATH variable is set and add the Mozilla directory to your path,
so you can start Mozilla by typing "mozilla" in a terminal window.
The path may be set in the .dtprofile, .login, .bashrc or .cshrc file.
For bash shell:
export PATH=$PATH:<Mozilla installation directory>
For csh shell:
setenv PATH ${PATH}:<Mozilla installation directory>
Plugins
Download plugins,
and install in Mozilla's plugin directory
Mozilla's plugin directory
Mozilla will search for plugins in the following directories:
1) The default plugins directory is in <Mozilla installation directory>/plugins
2) The default user plugins directory is in $HOME/.mozilla/plugins
3) The user defined plugin directory could be set by an environment variable "env: MOZ_PLUGIN_PATH"
For example "export MOZ_PLUGIN_PATH=~/download/plugins"
Java
The Java Plugin is enabled in Mozilla 1.4 by default.
If it doesn't work, make sure there is a symbolic link in the plugin
directory, which points to:
SPARC:
$JAVA_PATH/plugin/sparc/ns610/libjavaplugin_oji.so
x86:
$JAVA_PATH/plugin/i386/ns610/libjavaplugin_oji.so
Note: copying the file instead of making the
symbolic link will cause Java to crash
Real Player
Macromedia Flash
A.
Install the Macromedia Flash Player system-wide, making it available to all users of the computer
1. You will need root access to the computer to install the Macromedia
Flash Player system-wide.
2. Copy the Macromedia Flash Player files, libflashplayer.so and flashplayer.xpt into
the Mozilla plug-in directory.
3. Restart Mozilla.
4. Verify the installation by typing about:plugins
in the location bar or by choosing Help > About Plugins.
You should see the Macromedia Flash Player listed as "Shockwave Flash
6.0"
B.
Installing the Macromedia Flash Player in
a User Account:
1. If you have not already used Mozilla from the user account,
launch Mozilla and close it.
This will create a preferences directory (.mozilla) in your home
directory.
2. Create a "plugins" directory in the Mozilla preferences
directory.
If the mkdir command reports the error "cannot make directory: File
exists", do not be alarmed.
This means only that the directory was already present and did not need
to be created.
3. Copy the libflashplayer.so and flashplayer.xpt into the
plug-in directory.
4. Restart Mozilla.
5. Verify the installation by typing about:plugins in the location bar or by choosing Help > About Plugins.
You should
see the Macromedia Flash Player listed as "Shockwave Flash 6.0"
Adobe Acrobat Reader
Solutions
Topic |
Problem |
Solution |
|
Installation |
|
|
Patches |
Warning: Required patches are not installed on the system |
Install the necessary patches. Latest patches can be found at:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage |
Patches |
Required patch 106300 does not install. |
This patch is a shared library patch for 64-bit C++. The package SUNWlibCx is required on the system. Install the SUNWlibCx package, or continue with patch installation without installing patch 106300. |
Startup |
|
|
Nothing happens |
No window appears when launching Mozilla from a remote machine. |
Set the DISPLAY environment variable to your machine's display.
For example, "setenv DISPLAY <host name>:0.0" |
Nothing happens |
No window appears
(You previously used Netscape 4.X) |
Mozilla 1.4 for Solaris tries to migrate your Netscape 4.X preferences the first time you launch Mozilla 1.4. A Netscape Communicator 4.X preference may not have been migrated correctly, causing the error. Try moving the ~/.mozilla directory to the ~/.mozilla.old directory. If that does not work, try moving the ~/.netscape directory to the ~/.netscape.old, then restart the application. |
Nothing happens |
No window appears when launched on
Solaris 2.6 |
Mozilla is not supported on Solaris 2.6
Only on Solaris 8 and later |
Wrong Browser |
Mozilla starts up a Netscape or FireFox window |
Start Mozilla with a parameter, for example "-P" |
Error |
On startup
Error message:
"Internal error: unavailable temporary resources." |
Perform the following steps to increase the swap space on your computer:
- Open a terminal window.
- Use the su command to switch to root.
- Type the following command:mkfile -v 100m swapfile_name
- Type the following command:swap -a swapfile_name
|
Error |
warning message appears on the shell output: Gdk-WARNING **: shmat failed! |
This message appears only if you run the mozilla -debug startup script. The message indicates that there is not enough shared memory for the application. The application still runs, but a little more slowly than usual. |
Display |
|
|
Icons |
Icons not displaying correctly |
Reset theme: View->Apply Theme, Select any theme , then restart mozilla |
Crash |
|
|
Solaris 9v4 |
Crash |
The gtk+-2.0 library on Solaris 9 update 4 has a bug that causes the browser to crash.
Please get patch 115738-03 or higher to fix it. |
Flash 6 |
Crashes when playing multiple Flash Movies |
Inside the
system file (/etc/system) add the following line
"set shmsys:shminfo_shmseg=your-number-here"
This will prevent crashes but the Flash files may still run slowly
|
Printing |
|
|
Resize |
Unable to print large page with landscape format |
1. Use scale only
2. Use Xprint system. About please refer to xprint.mozdev.org |
Language |
When printing non-western web page, empty blocks will sometimes be printed instead of the character. |
Add search path for the font: pref("font.directory.truetype.1", path)
the "prefs.js" file located in the ".mozilla" directory located in your home directory. |
Scripts |
|
|
Javascript |
Close window function does not close tab |
Change preferences setting in prefs.js:
pref("dom.allow_scripts_to_close_windows", true); |
Mail |
|
|
IMAP |
Some IMAP servers don't support mixed type folders. So, a folder on this kind of server can only store messages or sub-folders, but Mozilla mail supports mixed folders as the default. So, this will cause some problems when creating and deleting folders. |
Open Edit->Mail & Newsgroup Account Settings->Server Settings. Click "Advanced". Uncheck "Server supports folders that contains sub-folders and messages" |
Profile |
|
|
Loading |
Crashes when loading profiles
(You have run a previous version of Mozilla) |
The formats of some of the files in this directory have changed, causing compatibility problems. To fix this problem, perform the following steps:
- Open a terminal window.
- Type the following command: mv ~/.mozilla ~/.mozilla.old
- Restart the browser.
|
General |
Mozilla is behaving erratically |
Profile corruption can cause Mozilla to behave erratically. In this case create a new profile |
Plugins |
|
|
Java |
My Java 1.4.2 code gets into a deadlock while showing a modal dialog using inkoveAndWait()" |
The workaround is to use invokeLater call instead of inkoveAndWait call. |
Java |
How do I update pre-1.4.2 applets? |
The following is recommended:
- Pre-1.4.2 applets should be recompiled with J2SE1.4.2 using the default options (i.e. no -target 1.4.2).
- They should run correctly across all platforms (Solaris/Linux/Windows) provided that they do not depend on 1.4.2 APIs
|
Chat |
|
|
IP resolution |
Unable to resolve server address |
Use IP address instead |
Web Start Uninstall
If you installed Mozilla 1.4 using Web Start run:
% cd <installation directory name>
% ./uninstaller
SVR4 Uninstall
If you installed Mozilla 1.4 from SVR4 packages (pkgadd version), you should remove mozilla using pkgrm.
%pkgrm<installation package name>
Note: You must remove optional packages separately and you must be logged in superuser
X-printing
How to set up x-printing for Mozilla.
Xprt is the Xprint print server for version 11 of the X Window system for non display devices such as printers and fax machines.
Xprint is an advanced printing system which enables X11 applications to use devices like printers, FAX or create documents in formats like PostScript, PCL or PDF. It may be used by clients such as mozilla .
How do I configure Xprint on the client side?
There is an environment variable (env vars) which controls Xprint on the client side.
The environment variable ${XPSERVERLIST} contains a list of display identifiers
(separated by white space) to tell Mozilla where it can find the X-print servers.
Example:
%export XPSERVERLIST="littlecat:80 bigdog:72"
This instructs an application to look at display 80 on the machine"littlecat" and display 72 on the machine bigdog, to look for X-print servers.
How do I setup an Xprint Server?
On Solaris Xprint Server is installed by default.
Xprt [ -ac ] [ -audit level ] [ -pn ] [ -fp fontpath ] [ -XpFile file ] [ -XpSpoolerType spoolername ] [ : display ]
: display
The X server runs on the given display. If multiple X servers are to run simultaneously on a host, each must have a unique display number. Note that the standard X server (for video displays) typically runs on display :0
Example: To start an Xprint Server on display 99:
%Xprt :99
-fp fontpath
sets the search path for fonts. This path is a comma separated list of directories which Xprt searches for font databases.
Example:
%Xprt :99 -fp \
/usr/X/lib/X11/fonts/TrueType/,\
/usr/X/lib/locale/zh/X11/fonts/TrueType/ &
For more information about how to setup an Xprint Server, please refer to http://xprint.mozdev.org/docs/Xprt.html or refer to the man page ( "man Xprt" command on Solaris )
How to print web pages with non-western fonts from Mozilla.
Pages containing non-western fonts may not always print correctly, using TrueType printing will solve this problem.
What's TrueType printing?
Mozilla uses the FreeType library to translate True Type fonts into CID type 1 fonts. It then embeds the CID Type 1 font into the postscript file.
How to set up TrueType printing?
The paths for each font set need to be in the solaris.js file located :
defaults/pref/solair.js
You can add a path to search for new True Type fonts to the solaris.js file.
Below are the default settings
pref("font.directory.truetype.1", "/usr/X/lib/locale/zh/X11/fonts/TrueType");
pref("font.directory.truetype.2", "/usr/X/lib/locale/zh.GBK/X11/fonts/TrueType");
pref("font.directory.truetype.3", "/usr/X/lib/locale/zh_CN.EUC/X11/fonts/TrueType");
pref("font.directory.truetype.4", "/usr/X/lib/locale/zh_CN.GB18030/X11/fonts/TrueType");
pref("font.directory.truetype.5", "/usr/X/lib/locale/zh_TW/X11/fonts/TrueType");
pref("font.directory.truetype.6", "/usr/X/lib/locale/zh_TW.BIG5/X11/fonts/TT");
To add a new font path use the same format:
pref("font.directory.truetype.<number>", "<path/ folder location>");
I.E. for Korean
pref("font.directory.truetype.7", "/usr/X/lib/locale/ko/X11/fonts/TrueType ");
NOTE: This feature requires freetype2 library support.
Make sure you have FreeType installed and the path for "libfreetype.so" is available to the system.
If Mozilla can't find the libfreetype.so add the path:
export LD_LIBRARY_PATH=<location of libfreetype.so >
What to do if Mozilla crashes
If Mozilla crashes you can take the following steps to assist us debug.
Only
Sun Mozilla version 1.4 can do this. Mozilla version 1.2 and the community version cannot.
What is the core dump file?
The core dump file contains all the process information pertinent to debugging: contents of hardware registers, process status, and process data.
Where can I find it?
When a process crashes, the operating system writes out a core image to a file (called a core dump) . Usually the core dump file is written to the directory from which Mozilla was launched (provided it can be; normal access controls apply).
Why can't the core dump file be written?
There are two possibilities:
1. The process does not have write permission to the directory from which Mozilla was launched
Solution: Launch Mozilla from a directory in which you have write permission.
2. The core dump file exceeds the default permitted maximum size.
Solution: Remove the file size limit using: 'ulimit -c unlimited'.
What should I do with the core file?
Send it to us directly at mozillafeedback@sun.com or let us know where we can get it. Be sure to include your complete platform information.
You can get the complete information through: 'uname -a'
If it is hard to send the core file, you can examine the file and send us the results.
Solaris has the following tools that can be used to examine the core file:
/usr/bin/pstack ./core
/usr/bin/pmap ./core
/usr/bin/pldd ./core
Send the output in plain text format to mozillafeedback@sun.com
Mozilla - debug option
While it has limitations, running Mozilla with the debug switch may be helpful to administrators in diagnosing problems. Some error/warning messages which do not show in normal mode will be displayed in two scripts: debuginfo.sh and checkpatches.sh will run if you launch mozilla with '-debug'. debuginfo.sh prints out some system info and checkpatches.sh checks if all the patches mozilla needed have been installed.
Example:
bash-2.05$ /mozilla/mozilla -debug
------- Running Mozilla 1.4 debug mode-------
USER: robin
HOSTNAME: eri0 = dart
IP ADDRESS: eri0 = 129.158.217.225
HOSTNAME: eri0 = dart
IP ADDRESS: eri0 = 129.158.217.225
ARCH: sparc
FRAME BUFFER(S): unknown
SunOS RELEASE: 5.9
KERNEL ID: Generic_112233-12
MEMORY: 256MB
SWAP: 0.0MB total, 0.0MB used, 0.0MB available
LOAD AVERAGE:19, 1 user, :0.05, 0.01, 0.02
DNS DOMAINNAME:
ETHERNET ADDRESS: 0:3:ba:5b:97:f5
HOSTID: 835b97f5
Checking for recommended patches ...
** (mozilla-bin:10798): WARNING **: Size mismatch when converting text from input method: supplied length = 8
, result length = 6
** (mozilla-bin:10798): WARNING **: Size mismatch when converting text from input method: supplied length = 8
, result length = 6
** (mozilla-bin:10798): WARNING **: Size mismatch when converting text from input method: supplied length = 8
, result length = 6
.
Manually Implementing a Profile Server
This document assumes that you are implementing a Profile Server on a dedicated server, rather than on an existing server. We recommend using a dedicated Profile Server because it provides increased performance and minimizes interaction with other applications. This document provides instructions on how to implement Profile Server on either a Java Enterprise Web Server (version 6.1 or later) or a Java Enterprise Directory Server (versions 5.2). Since Profile Server does not rely on any proprietary features of Java Enterprise servers, other servers may work, but they have not been tested by Sun.
Which server type do I want to use?
You can store profile data on an HTTP, FTP or LDAP server. The server type you choose is largely based on your existing infrastructure and the need for administrative control over profile data. HTTP and FTP are relatively easier to setup, but do not have all of the administration features that LDAP has.
How do I Setup a HTTP Profile Server?
Enable "Remote File Manipulation" for the HTTP Profile Server.
- Start your Administration Server and navigate to the the Administration Server page.
- Change to the "Class Manager" view.
- Click Content Mgmt tab.
- Choose "Remote File Manipulation" in the left pane.
- Check the Yes item below the label with "Activate file manipulation commands".
- Apply the change.
Add rules for users of Profile Roaming
- Change to the "Server Manager" view.
- Click "Preferences" tab.
- Choose "Restrict Access" in the left pane.
- Edit the ACL file by adding access control rules
Note: be sure that the user has the privilege to access their directory where roaming access files are stored.
How do I setup a LDAP Profile Server
-
Stop the Directory Server.
- Add the Profile Server schema, shown in listing below, to your LDAP Server.
NOTE: Java Enterprise LDAP Server includes the schema by default.
show schema
# ns-mcd-li-schema.conf
#
# Profile Server schema
#
attribute nsLIPtrURL |
2.16.840.1.113730.3.1.399 |
ces |
attribute nsLIPrefs |
2.16.840.1.113730.3.1.400 |
ces |
attribute nsLIProfileName |
2.16.840.1.113730.3.1.401 |
cis |
attribute nsLIData |
2.16.840.1.113730.3.1.402 |
bin |
attribute nsLIElementType |
2.16.840.1.113730.3.1.403 |
cis |
attribute nsLIServerType |
2.16.840.1.113730.3.1.404 |
cis |
attribute nsLIVersion |
2.16.840.1.113730.3.1.405 |
integer |
attribute nsServerPort |
2.16.840.1.113730.3.1.280 |
cis |
objectclass nsLIPtr
oid 2.16.840.1.113730.3.2.74
requires
objectclass
allows
nsLIPtrURL,
owner
objectclass nsLIProfile
oid 2.16.840.1.113730.3.2.75
requires
objectclass,
nsLIProfileName
allows
nsLIPrefs,
uid,
owner
objectclass nsLIProfileElement
oid 2.16.840.1.113730.3.2.76
requires
objectclass,
nsLIElementType
allows
owner,
nsLIData
nsLIVersion
objectclass nsLIServer
oid 2.16.840.1.113730.3.2.77
requires
objectclass,
serverhostname
allows
description,
cn,
nsServerPort,
nsLIServerType,
serverroot
- Restart the Directory Server.
- Create a root entry under which you will store the profiles. You can store all the User Profiles under a single root entry this simplifies the setup and management of Profile Roaming. The root entry that you create can contain any object class, although you would typically include the object class "orgazinationalUnit"
- Set access controls for the root profiles entry, granting users both read and write access to the entry and its sub nodes. Read access lets users copy their profile data down to a local computer. In this way, you can use a single access control rule to grant authenticated access to all users, such as that shown in below.
Example: (target="ldap:///ou=Roaming,o=mcom.com")(targetattr!="nsLIPrefs")(version 3.0; acl "Roaming"; allow (all) userdnattr ="owner"; )
- Depending on what server you're using, you might also be able to set this ACL using a separate administrative tool.
- Under the profiles root, create a profile for each user by creating a nsLIProfile entry. Below shows an example of an LDIF that you can use to create a profile entry for a user called pete.
Example:
dn: nsLIProfileName=pete,ou=Roaming,o=myCompany
changetype: add
objectclass: top
objectclass: nsLIProfile
nsLIProfileName: pete
owner: uid=pete,ou=People,o=myCompany
- Create user entries that Browser will authenticate users against. You can create new entries for users, as in listing below, or you can replicate user entries from the corporate directory to the Profile server (recommended).
Example:
dn: uid=pete,ou=People,o=myCompany
changetype: add
objectclass: top
objectclass: inetOrgPerson
cn: pete
userpassword: myPassword
Profile Roaming Preferences
Profile Server includes a set of new Browser preferences that you can use to control many aspects of the feature. For example, you can set or lock preferences to enable the feature, set the location of the Profile server or corporate directory, define what files users are permitted to transfer to and from the server, and so on.
Profile Roaming preferences can be set in two places:
- On the Profile server, using Profile Server Control
- In Browser's Preferences window (set by the user)
The browser stores all Profile Server preferences in special file: "prefs.js" in the active user profile, along with other user preferences that are served through Profile Server.
The following table gives a full list of Profile Server preferences you can set. Note that if you are setting preferences on the server using Profile Server Control, you do not need to work with preferences directly. Instead, you can use the graphical user interface of the Profile Server Console.
Preference Setting |
What file the preference lets you allow or disallow to transfer. |
|
|
roaming.files.abook.mab |
Address book |
roaming.files.history.mab |
Collected address book |
roaming.files.bookmarks.html |
Bookmarks |
roaming.files.cookies.txt |
Cookies |
roaming.files.cookperm.txt |
Cookie permissions |
roaming.files.history.dat |
Browser history |
roaming.files.mimeTypes.rdf |
Help Application Setting |
roaming.files.panels.rdf |
Sidebar panel list |
roaming.files.localstore.rdf |
Windows setting |
roaming.files.liprefs.js |
User preference |
roaming.files.mailViews.dat |
Mail view setting |
roaming.files.training.dat |
Junk mail filter |
roaming.files.filter |
Mail filters |
|
Note: You can also use the graphical user interface of the Profile Server Console. |
Note: Some files have a tendency to become large such as address book, browser history.
If the transfer of this file adversely affects network performance, consider setting this preference to false on server side.
Advanced Features
Profile Server also supports the following features:
- Replication - For greater performance and data integrity, Profile Roaming is compatible with replicated LDAP servers. Simply point the Browser client to a replicated server; writing to the master server is handled automatically. (You can used the DNS round-robin technique to distribute load across replicated servers)
- Server Side Preferences - When reading a LDAP profile entry for Profile Roaming, The browser can also pull down preferences set by an administrator in the nsLIPrefs attribute