iseemedia ImageServer 5.1 Readme

Table of Contents

System Requirements

Hardware requirements
Operating systems
Additional requirements

Installation

Windows installation notes
Solaris installation notes
Linux installation notes
General installation notes

ImageServer Examples

Enhancements from Release 4.6

General Issues

Cache
Concurrent Threads
Accessing Network Drives from the ImageServer NT Service

Known Issues

Contacting iseemedia

System Requirements

Hardware requirements

  • Minimum Intel-based P4

  • Minimum 512 MB RAM recommended, 2 GB for active servers

  • Minimum 256 MB hard disk space for the server and software plus additional space for server components

  • Additional space may be required for images

Operating systems

  • Microsoft Windows 2000 Server with SP4

  • Microsoft Windows 2003 Server

  • Sun Solaris 8 or 9 (SPARC platform edition)

  • Red Hat Linux AS 3.0 (x86 editions)

  • SuSE 9.0 or 9.1 (x86 editions)

    • Note: This release does not support the ImageServer on the Apple Xserve Platform 10.4. This platform will be tested for compatibility shortly, please contact iseemedia for further information


Additional Requirements

To use the Java versions of the Zoom Viewer, the Java applets and the ImageServer must be served from the same IP address. This Java security measure allows a Java applet to communicate only with the computer from which it originates.

Installation

The iseemedia ImageServer comes with 2 CD-ROMS. The Program CD contains the installation for the actual ImageServer. The Supplementary CD contains all of the documentation for the ImageServer as well as the installation for the all of the ImageServer Tools.

Before installing the ImageServer, check iseemedia's website for information that was not available when this guide was completed. It may contain information you will need for installation.

We recommend that the ImageServer is installed from the CD. Installing from the CD will ensure that the ImageServer utilities are copied onto your drive as part of the installation process in the ImageServer directory.

  1. Insert the CD-ROM. The installer should automatically launch. If you have autorun turned off, locate install.exe on the CD-ROM and double-click the file to begin the installation process.

  2. The License Agreement dialog appears. Accept the License Agreement to continue the installation and click Next.

  3. Enter your licensee name, the company name and the license key provided by iseemedia in the User Information dialog. Without a valid license key, the functionality of the server will be limited to the Remote Administration Licensing page. Click Next to continue.

  4. The next dialog is the Host and Port Settings dialog. The installer extracts the IP address from the system (please verify that the address is correct). The default ImageServer port is 8087 and the default ImageServer administration port is 8088. Please note that changing the IP address after installation requires you to reinstall the ImageServer. Click Next to continue.

    While the server port can be changed, the remote administration port should not be changed as administrators use this port to remotely administer the server. The user name is "Administrator" and the default password is blank. Once the ImageServer is installed, you can change the default password.

  5. The Memory Settings dialog allows you to set the ImageServer's Java Heap memory. The amount should be set to a maximum of 80% of free system memory. If other applications are running, make sure to take into account how much memory they are using. It is not recommended to run other applications at the same time as the ImageServer. Setting this to a high value can result in server instability as the JVM cannot allocate enough resources. Setting the value too low can result in inefficiencies and cache being cleared too quickly. The default value is based on a 512 MB system with the ImageServer as the only application. The maximum heap size is 2 GB.

  6. Enter the number of processors running on your machine. Click Next to continue.

  7. Choose a destination folder or accept the default location. Click Next to continue.

  8. You now have the option of installing additional components such as Verifi Color Correction, SVG demo and the Image Upload Manager. Enable the checkboxes next to the component.

  9. Review the install settings and click Install to install the ImageServer. The installation will take several minutes to complete.

Windows installation notes

  • When installing on the Windows platform, the ImageServer is automatically installed as a Windows 2000 (or NT) service and thus must be installed from an account with Administrator level privileges.

  • Once the ImageServer has been successfully installed, you can:

    • Verify the Welcome Page and test basic server functionality at: http://ServerIP:8087.

    • Configure the server remotely at: http://ServerIP:8080/is.

    Note: Replace ServerIP with the IP address provided during installation. For more information regarding the Administrator's Management Console and other aspects of the ImageServer, please see the Documentation on Disk 2.

Solaris installation notes

  • When installing on the Solaris platform, you must be logged on with superuser privileges before beginning the installation process. Either log on as "root" or use "su -" from another login account.

  • When you are ready to begin the installation, insert the CD-ROM and wait for Solaris to mount it.

  • From a console window, type the following commands to start the installer:
    # cd /cdrom/cdrom0/solaris
    # sh ./install.sh

  • The installer will extract the JRE and all required resources. This process could take a few minutes depending on the speed of the system.

  • Once the installation of the ImageServer is complete, start (assuming the default installation path) the ImageServer by typing:
    # cd /usr/local/imageserver
    # ./imageserverctl start

    Use ./imageserverctl stop to stop the server.

    To start the application server (assuming the default installation path), type:
    # cd /usr/local/imageserver/appserver
    # ./appserverctl start

    Use ./imageserverctl stop to stop the ImageServer or ./appserverctl stop to stop the Application Server..

Linux installation notes

  • Before you can begin the installation process, you must be logged on with superuser privileges. Either log on as "root" or use "su -" from another login account.

  • When you are ready to begin the installation, insert the CD-ROM and wait for Linux to auto-mount it. If your version of Linux does not support CD auto-mount, enter the following command from a terminal window:
    # mount /mnt/cdrom

  • From a Terminal window, type the following commands to start the installer:
    For Red Hat Linux AS 3.0:
    # cd /mnt/cdrom/install
    # sh ./install.sh

    For SuSE 9.0 or 9.1:
    # cd /mnt/dvd
    # sh ./install.sh

    The installer will extract the JRE and all required resources. This process could take a few minutes depending on the speed of the system.

  • Once the installation is complete, start (assuming the default installation path) the ImageServer by typing:
    # cd /usr/local/imageserver
    # ./imageserverectl start

    Use ./imageserverctl stop to stop the server.

    To start the application server (assuming the default installation path), type:
    # cd /usr/local/imageserver/appserver
    # ./appserverctl start

    Use ./appserverctl stop to stop the Application Server.

  • When installing the ImageServer on Linux, the default IP address is 127.0.0.1. The installation will not automatically enter your IP address. This must be done manually.

General installation notes

Follow the Setup instructions. As you go through Setup, please note the following:

  • The Virtual Memory of your computer should be set to at least the same size as the RAM of your computer. We recommend that you set the Virtual Memory to double the size of the RAM of your computer.

  • To complete the User Information screen, you will need your license key. If you are installing the ImageServer from a CD, you will find the license key on the CD jewel case. If you have downloaded the server from the web, you should have already received a license key.

  • For Windows only: In the Host Information screen, the Host Name and IP Address should not include http:// at the beginning or a slash at the end. They should be in the following format: 255.255.255.255 or yourdomain.com. Your IP Address should be a static address. You can check this by going into your Network Settings in the Control Panel, click on TCP/IP properties and make sure that 'Specify an IP Address' is selected. Obtain the IP Address from your network administrator.

  • In the Host and Port Settings screen, specify the ports of the ImageServer and the Administrator's Management Console. Note that server ports are specific to each machine. The default values appear in the boxes but these values can be changed. It is not recommended changing the Administration Ports. Be sure that the port numbers you use do not conflict with ports already in use.

  • In the Destination Folder screen, choose the location of the server files. If you want to install the ImageServer in a folder other than the one displayed in the path, click Browse to locate the folder you want.

  • If you are reinstalling the ImageServer on the Windows NT platform, you must make sure you stop the ImageServer Service from the Control Panel.

  • If you are reinstalling the ImageServer on the Solaris /Linux platform, you must make sure you terminate the ImageServer process. Use the 'imageserverctl stop' command.

  • During installation on Unicode operating systems, the delimited path for installation must only include full Latin characters.

ImageServer Examples

This section contains example pages that use the ImageServer and the Java Applets. Feel free to copy and paste the HTML source into your web pages by right-clicking on the example page and selecting View Source. Otherwise, you can copy the complete files into your web server directory.

Enhancements from Release 4.6

  • Internal changes to the ImageServer for increased performance and reliability.

  • Streamlined installer

  • Solaris 8, 9 and Red Hat AS 3.0 are supported

  • Java JRE 1.4.2 for Windows, Solaris and Linux is now used for running the ImageServer

  • The threading model and the socket architecture have been upgraded to take advantage of the 1.4.2 JVM advances.

  • Xvfb is no longer required under Solaris and Linux

  • New 5.0 Customizable Java Viewers are included.

  • Color Correction support module for Kodak Polychrome Graphics Verifi Internet Color Matching is included.

  • Application server added with plugable architecture for non-disruptive upgrades.

General Issues

Cache

Cache size can be configured by referring to the ImageServer User's Guide under Server Settings.

The cache size specifies how much memory the ImageServer can use for storing image data in memory. Using the cache greatly increases overall performance. For Universal Viewing, enabling the cache can result in performance that is 10 to 100 times faster versus non-cache use. A low cache setting can therefore reduce the ImageServer performance. However, a high cache setting can cause Out of Memory errors, which can be confused with specifying incorrect startup arguments (See Garbage Collection section). The recommended cache setting is about 80% of the assigned memory during the installation.

Concurrent Threads (applies only to the Extended Enterprise edition)

The concurrent threads setting should equal the number of processors resident on your computer plus one. This number is based on the ImageServer running on a dedicated system. If there are other servers or applications running on the same system as the ImageServer, the number of concurrent threads should be reduced. This has changed from the previous version of the ImageServer.

Accessing Network Drives from the ImageServer 2000 Service

Accessing Network Drives from the ImageServer 2000 Service may require additional settings in the Windows Services control panel. These additional settings would be the username and password which are necessary to gain access to the network drive.

For more information on accessing network drives, refer to the Windows documentation on Services or see the knowledge base article "Accessing Network Drives Created in Services Under Windows NT (Q149984)" on the Microsoft website or visit http://support.microsoft.com/support/kb/articles/Q149/9/84.asp.

Known Issues

  • When using Internet Explorer for viewing the Administration pages, please pay attention to the following:

    • a blank field next to the Images dialog on the Policies screen will be displayed when only one Watermark image is selected to be displayed.

  • Ensure that you do not allow anonymous users to view images when you are adding new users. Allowing anonymous viewing will not launch the authentication dialog.

  • In the Policies screen, the Maximum Resolution setting displays a watermark image, overlay or no image up to the percentage specified. Selecting "Do not display", regardless on of the Maximum Resolution setting, will not display an image using Universal Viewing.

  • When typing a URL address in the browser window, be careful not to enter invalid or bad filenames. Doing so may result in the following:

    • the Welcome Page will display a Zoom Viewer window. This window signifies that an error has occurred. Check your URL address.

    • the "File Download" dialog will appear. When this dialog is displayed, either save the file or open. The file can opened by any text editor. Once the file is opened, you will be given information as to the errors that occurred.

  • Editing the Properties file is not recommended. Doing so may result in errors occurring with the operation of your ImageServer. If you chose to edit the Properties file, make a backup copy of it first.

  • The default template directory is hard coded and cannot be edited. To change the template, choose one of the Universal Viewing templates provided. If you choose an invalid template filename, no error message is displayed. Check to make sure the filename specified is a valid one.

  • For Solaris and Linux users, certain extreme load conditions, where UV and CVT images are used, can cause a disruption to your server. These load conditions may cause the following error to occur:
    libthread panic: cannot create new lwp (followed by system specific details)
    Extreme load conditions may also cause a Java "outofmemory" message which can cause your server to become unresponsive.

    Contact your iseemedia Sales Engineer, upon receiving this error message, for information on expanding your server capabilities.

  • When saving images, ensure that there are no spaces in image filenames. The ImageServer will not display these images if the filename contains spaces.

  • On Linux, during the download of Image Authoring Manager or Image Navigator there is a known Java VM issue that causes installers to occasionally hang while waiting for the external program to complete. You may try the download at a later time or download the installer file from the appropriate link at the bottom of the server installer page. Another alternative is to install directly from the CD.

  • On Linux, a red X appears in the Universal Viewer on the first initial image display. Clicking on the viewer displays the next zoomed image. This issue does not occur with CVT or Java requests.

    This issue only occurs for those performing minimal Linux server installs without the Graphical Internet package. The Graphical Internet package includes the compat-libstdc++-7.3-2.96.110.i386.rpm for Red Hat 8.0 and compat-libstdc++-7.3-2.96.118.i386.rpm for Red Hat 9.0. compat-libstdc++-7.3-2.96.110.i386.rpm provides backwards compatibility with Red Hat Linux 7.3 C++ libraries and compiler.

    To resolve this issue:
    For Red Hat 9.0: Install compat-libstdc++-7.3-2.96.118.i386.rpm, located on Disk 1.
    Reboot the system.

  • The INVERT and AUTOFIX CVT commands may produce different results on Windows 2000 Server.

  • Additional server installations on the same hardware platform may limit or disable the ImageServer 5 platform from functioning. We do not certify or guarantee functionality when hardware resources are being shared with other
    applications. We strongly recommend dedicated hardware for this Enterprise product.

  • The ImageServer does not deliver nor request progressive JPEG images.

  • The JTL command returns what appears to be a corrupt image when showing the edges. Tiles on the right and bottom of the image will have the last row or column of the real image data copied to successive empty pixels to fill in the 64x64 pixel expanse.

  • Universal Viewing 2 will not be displayed properly on Netscape 4.75. Use Internet Explorer instead.

  • The SVG Demo has the username and password hard-coded. If you've changed the username or password for administrating the ImageServer then change the following file:

    Windows:
    C:\Program Files\iseemedia\ImageServer\appserver\webapps\SVGDemo\WEB-INF

    Linux:
    /usr/local/imageserver/appserver/webapps/SVGDemo/WEB-INF

    Note that the actual location may be different, depending where you installed the ImageServer.

    Look for the following lines:

    <context-param>
    <param-name>zisUserName</param-name>
    <param-value>Administrator</param-value>
    <description>User name for requests to image server that require authentication</description>
    </context-param>
    <context-param>
    <param-name>zisPassword</param-name>
    <param-value/>
    <description>Password for requests to image server that require authentication</description>
    </context-param>

    Change to:

    <context-param>
    <param-name>zisUserName</param-name>
    <param-value>myusername</param-value>
    <description>User name for requests to image server that require authentication</description>
    </context-param>
    <context-param>
    <param-name>zisPassword</param-name>
    <param-value>mypassword</param-value>
    <description>Password for requests to image server that require authentication</description>
    </context-param>

  • When replacing image files that reside on the ImageServer, the ImageServer must be restarted in order for the updated files to be viewed correctly.

  • When using the BLUR filter command, the filter command will not be applied to all of the pixels at the edge of the effect. The size of the region will decrease with the spatial size of the filter operation.

    • Image Upload Manager

  • When creating users from the Administrator's Management Console to be used with the Image Upload Manager, ensure that only Latin characters are used. Double-byte characters may not be recognized correctly.

  • When uploading a file to the image folders, files with the same name will be overwritten. This feature is present to allow published images to be updated. Updates are done between when the ImageServer shutdown and restarted.

  • Ensure that "Allow Server Administration" is set to "Yes" under the Group setting in the Administrator's Management Console.

  • Uploading images may halt based on network timeouts. Discuss with your system administrator about decreasing your network latencies and throughput limits.

Contacting iseemedia

Please contact one of the iseemedia offices below for consumer, business, reseller or OEM sales information and service. If you require technical support or other information, please click Customer Care.

How can we help you today?
Please select the department you would like to contact:

Sales Contact
For sales information on iseemedia Products.


Customer Service
For sales and customer service on iseemedia Products.


Technical Support
For technical help and information on iseemedia Products.


Investor Contact
For investor information on iseemedia.

© 2004 iseemedia Inc.