Configuring Java LiveUpdate

Article:TECH101689  |  Created: 2006-01-10  |  Updated: 2013-09-23  |  Article URL http://www.symantec.com/docs/TECH101689
Article Type
Technical Solution


Environment

Issue



Configuration and introduction to Java LiveUpdate (JLU).

 


Solution



Introduction
LiveUpdate is the Symantec technology that permits an installed Symantec product to connect to a Symantec LiveUpdate server over the Internet, or to your local LiveUpdate server (LiveUpdate Administration Utility 1.x or LiveUpdate Administrator 2.x) on your Intranet, and check for program and other updates such as virus definitions.

Java LiveUpdate (JLU) is a LiveUpdate client that is used with many Symantec products.  Unlike the Windows LiveUpdate client software or LiveUpdate Engine (LUE), JLU can run on several different platforms (Linux, Mac, etc). 

When updates are available, JLU (Java LiveUpdate) downloads them to your computer and installs them, keeping your Symantec software up to date. All updates downloaded via LiveUpdate are secured with digital signature verification technology so that you can be sure we only install content that has been authenticated.

Certain types of content may require a subscription and so Java LiveUpdate will only download subscription content if a valid subscription is found on your machine.

 

Prerequisites
Java LiveUpdate requires a minimum Java Runtime Environment (JRE) of v1.1.8 or higher in order to run. We recommend a minimum JRE version of v1.2.2 or higher.



Installing\Uninstalling Java LiveUpdate
Java LiveUpdate should only be installed by a Symantec product.
Manual installation is not supported at this time.

By default, Java LiveUpdate gets its configuration information from the liveupdate.conf file.
You can specify a different configuration file with the –c command-line switch.

Example:
java -classpath jlu.jar LiveUpdate -c /home/james/liveupdate.conf

The following are the locations of liveupdate.conf:
 

  • SPARC\Linux
    /etc/liveupdate.UNIX conf
     
  • Linux
    /etc/liveupdate.conf
     
  • Windows
    \Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\liveupdate.conf
     
  • Macintosh
    /etc/liveupdate.conf

    PARAMETER (Case Sensitive)

    DESCRIPTION

    USAGE

    workdir

    The full path to a working directory for LiveUpdate's file operations. The default /tmp directory will still be used for some operations, i.e. extraction of compressed files.

    REQUIRED! Working directory on client machine. JLU creates a local package directory under the specified working directory. If the working directory doesn't exist, JLU creates it and uses the working directory itself as the local package directory. The local package directory will be removed when JLU exits, unless the -k command line switch is specified.

    hostfile
    The full path to a legacy host file (Liveupdt.hst) that is generated by the LiveUpdate Administration Utility
    If a host file is specified, all of the transport-related entries in liveupdate.conf are ignored, and the information from the specified host file is used instead.

    logfile
    The full path to the log file that JLU (Java LiveUpdate) uses to log events and errors.
    Full path to a log file which Java LiveUpdate will use to log actions and errors. If this setting is omitted, no log file will be created.

    jar

    The full path to the JLU .JAR file.

    If this file is omitted, JLU looks for its JAR file in the LiveUpdate subdirectory that is immediately under the Symantec directory. The location of the Symantec directory is specified by the BaseDir parameter in the Symantec Shared section of the Symantec global configuration file /etc/Symantec.conf. JLU returns an error immediately if it cannot locate its JAR file.

    urls

    The URLs of external Symantec server support.

    By default, JLU ignores the URL= lines in the TRI file. If this parameter is 1 (true), JLU uses the URL= lines in the TRI file when it uses HTTP to download packages. This parameter and the URL= lines are ignored if FTP is specified as the protocol.

    proxy

    The name of a proxy server.

    For example: proxy=addr:port, where the port number is optional. The default port is 80. Addr is the TCP/IP address of the proxy server and :port is the TCP/IP port on which the proxy server is listening. This setting is not suppoted for FTP.

    proxyusername

    The user name to use when you log on to the specified proxy server.

    This setting is needed only if your proxy server requires a logon user name. This setting is not suppoted for FTP.

    proxypassword

    The password that is associated with the specified proxyusername account.

    This setting is needed only if your proxy server requires a logon password. This setting is not suppoted for FTP.

    maximumLogFileSize

    The maximum allowed log file size, in kilobytes (KB).

    JLU discards older log entries once the log file exceeds the specified maximum size. The default log file size is 1024 KB.

    AllowConfigurationOverride

    The setting that is used to tell JLU to use the -c command line switch and hostfile setting.

    If this parameter is set to anything other than TRUE in the shared liveupdate.conf file, JLU ignores the -c switch and host file setting.

    hosts//url

    The URL of a LiveUpdate server.

    You may specify a nonstandard port for HTTP servers and a package directory for both FTP and HTTP servers. JLU supports up to 10 servers, numbered 0 through 9. This setting replaces the following JLU 1.10 settings:
    protcol, host, packagedir, login, password

    hosts//access

    The local or mapped directory to access for updates.

    The path may be a full local path or a UNC share.

    hosts//login

    The user name to use when logging on to a LiveUpdate server using FTP.

    This optional setting is ignored for all other transports.

    hosts//password

    The password to use when logging on to a LiveUpdate server using FTP.

    This optional setting is ignored for all other transports.

    connectionTimeout

    The connection time in milliseconds that JLU will wait when it attempts to connect to a LiveUpdate server.

    The default value prior to JLU 3.5 is 60000 (60 seconds). The default value from JLU 3.5 or above changes from milliseconds (60000) to seconds (60).

    connectionReadTimeout

    The connection timeout in milliseconds that JLU will wait for responses from the LiveUpdate server once a connection has been established.

    The default value prior to JLU 3.5 is 30000 (30 seconds). The default value from JLU 3.5 or above changes from milliseconds (30000) to seconds (30).

    PREFS_CUSTOM_CONTENT

    The status of custom content.

    If set to 1, custom content is enabled. If set to 0, custom content is disabled. This setting is disabled by default.

    LOTS/LOTS_HTTPS_URL

    The URL from which to download the LOTS file for custom content.

     

    LOTS/LOGIN

    The logon that is used to download the LOTS file (if authentication is required) for custom content.

    This entry is encrypted by JLU.

    LOTS/PASSWORD

    The password that is used to download the LOTS file (if authentication is required) for custom content.

    This entry is encrypted by JLU.

    LOTS/UPDATE_LOTS_FILE

    The parameter that determines when to copy a LOTS file.

    If this parameter is set to OPTIONAL, a LOTS file is copied only if it is more recent than the one on the client. This allows custom content processing to proceed regardless of download errors, providing that a LOTS file already exists.

    If this is set to YES (the default), the LOTS file on the client is always overwritten with a new copy.

    If this set to NO, the LOTS file on the client is never overwritten.

    extlog/host#/url=syslog://
    [: ]

    The host address and port of the system log to which JLU sends logs.

     

    extlog/host#/url=sgs

    The URL that is used to send logs to Symantec Gateway Security (SGS).

    This entry may be included only one time in the configuration file.

    extlogdest=extloghost#[,extlog/host#]

    The list of active external logging services.

    This setting enables specified external logons if the list is not empty.

    enableSyslogLocalization

    The parameter that determines whether to enable localized messaging in the syslog.

    If this parameter is set to YES, localized messages are enabled. The default value is NO.

    maxZipFileSize

    The maximum allowed size of the catalog file in bytes.

    Default value is 600KB.

    maxTriFileSize

    The maximum allowed size of the tri, sig and grd files.

    Default value is 10MB.

    maxPackageSize

    The maximum allowed size of the package file.

    Default value is 700MB.

    maxPackageContentSize

    The maximum allowed size of the package contents.

    Default value is 700MB.




Debugging Java LiveUpdate

There is a Java command line that will run LiveUpdate once, and produce additional debug information that is echoed to screen and added to liveupdt.log:

$ cd /opt/Symantec/LiveUpdate
$ java -classpath jlu.jar com.symantec.liveupdate.LiveUpdate -d

Note that on some distributions, an additional dash may be required before the "classpath" option.



Additional Information
Java LiveUpdate (JLU) is installed into the /opt/Symantec/LiveUpdate folder. You should not attempt to install JLU from this location as this may leave JLU in an unusable state. If you have done this, you should remove JLU from the system and reinstall JLU from a different folder.

If several Symantec products are installed on multiple partitions on the same machine, only one instance of JLU may be running at the same time across these partitions. If you run more that one copy of JLU at the same time, you may encounter issues when JLU attempts to write to its log file.

When entering JLU host information in the host configuration list, always start with host 0. If you start with host 1, for example, and skip host 0, this will result in no host information being sent to JLU. You may enter up to 10 hosts (0-9).

You may encounter issues when running JLU v2.0 on Windows 2003 on 64-bit platforms. This version of JLU shipped prior to the release of Windows 2003, and so we have not tested JLU v2.0 on the final release code from Microsoft.

When entering host information for HTTP connections, you may use directory names with spaces, however the spaces must be represented using the "%20" character sequence. For example:
"http://machine.domain.com/directory5/directory6 with spaces/"
can be entered as
"http://machine.domain.com/directory5/directory6%20with%20spaces/"

Parameters are case sensitive.  For example, "ConnectionReadTimeOut" will be ignored as the correct value is "connectionReadTimeout".




 

 




Legacy ID



2006021007250213


Article URL http://www.symantec.com/docs/TECH101689


Terms of use for this information are found in Legal Notices