+

Search Tips   |   Advanced Search

Portal, V6.1

 

Prerequisites for Document Conversion Services

This section describes the prerequisites for running Document Conversion Services in WebSphere Portal. A knowledge of these prerequisites can assist you in preventing, identifying, and correcting problems related to Document Conversion Services.

 

Prerequisites for Document Conversion Services in non-Windows platforms

To be able to perform document conversions in a non-Windows platform, perform the following steps whenever you start the Portal server from a new terminal window:

  1. Ensure that the oiexport directory is in the PATH as portal_server_root/shared/app/oiexport:$PATH.

    For example, export PATH = portal_server_root/shared/app/oiexport:AppServer_root/java/jre/bin:$PATH

  2. Export LD_LIBRARY_PATH /LIBPATH/ SHLIB_PATH to point to the oiexport directory and the graphics library. This environment variable is different for different platforms, as detailed in the table below:

    Platform Library path variable
    AIX LIBPATH
    HP-UX SHLIB_PATH
    Linux LD_LIBRARY_PATH
    Solaris LD_LIBRARY_PATH

    For example, in case of Linux, the command could be export LD_LIBRARY_PATH = portal_server_root/shared/app/oiexport:/usr/X11R6/lib

 

Prerequisites for viewing images in non-Windows platform

To view the images in non-Windows platforms, configure as per the following steps:

  1. Connect to the non-Windows machine from your Windows machine using PuTTY or any other Telnet client.

  2. The oiexport directory should be in the PATH as portal_server_root/shared/app/oiexport:$PATH.

    For example, export PATH = portal_server_root/shared/app/oiexport:AppServer_root/java/jre/bin:$PATH

  3. Export LD_LIBRARY_PATH /LIBPATH/ SHLIB_PATH to point to the oiexport directory and the graphics library. This environment variable is different for different platforms, as detailed in the table below:

    Platform Library path variable
    AIX LIBPATH
    HP-UX SHLIB_PATH
    Linux LD_LIBRARY_PATH
    Solaris LD_LIBRARY_PATH

    For example, in case of Linux, the command could be export LD_LIBRARY_PATH = portal_server_root/shared/app/oiexport:/usr/X11R6/lib

  4. Now connect to another non-Windows machine through XBrowser.

  5. Start the XBrowser and enter the host.name. Once you login successfully, type echo $DISPLAY at the prompt. This will give you <machine-ip>:0.0,, where <machine-ip> refers to the ip of the machine from where XBrowser has been started.

  6. In the same Telnet/ssh session where you have exported PATH and LD_LIBRARY_PATH/LIBPATH/SHLIB_PATH type the command export DISPLAY=<machine-ip>:0.0. This value will be the same as the value you get in the previous step.

  7. Change directory to the location where the xclock and xhost files are present, for example, /usr/X/bin.

  8. Type the command ./xclock &.

  9. Type ./xhost + on the non-Windows machine through which you are connected through XBrowser. This will give you the message access control disabled, clients can connect from any host.

    Changing directory is required because by entering the commands xclock& or xhost+, the error message command not found is displayed.

  10. The Xclock popup comes up on the desktop of the non-Windows machine to which you are connected through X-Browser.

  11. Change directory to AppServer_root/bin.

  12. Restart the server.

  13. Bring up a fresh browser, such as Internet Explorer or Mozilla, and try viewing the file containing images.

The above steps are given to start the X server using XBrowser. To start the X server using Exceed or X virtual frame buffer (Xvfb), perform the following steps:

  1. Start Exceed.

  2. Connect to the UNIX or Linux machine using PuTTY and then type export PATH.

  3. Type export LD_LIBRARY_PATH/LIBPATH/SHLIB_PATH.

  4. Type export DISPLAY.

  5. Type echo $DISPLAY on the machine to which you have connected using Exceed or Xvbf.

  6. Enter xclock & (if xclock appears on the desktop of the non-Windows machine to which you are connected through Exceed or Xvfb, then X server is running).

  7. If xhost + {xhost + <IP>} appears, this means conversion works for this particular IP and only + means for all machines.

    When using UNIX, launch WebSphere Portal from the console or an X Server-enabled client with the same privileges (xhost+) as the console. The graphical conversions require access to an X-Windows server, since they require access to the Xm, Xt and X11 libraries. Also the DISPLAY
    environment variable must be set to the account that Portal is running under. Note that the DISPLAY must be valid at the point that Portal is started. Otherwise, telneting to a machine and starting Portal from there does not work. You will need to start Portal from an X terminal.

For Linux and Solaris platforms, refer to the following section.

In case of Linux and Solaris When using OutsideIn version 8.1.0 and later, the X server dependency has been removed for Linux and Solaris platforms. For these platforms, perform these steps:

  1. Set preferoitrendering to true in the export.cfg file, located in the path portal_server_root/shared/app/export.cfg. An example is given below: 

    # SCCOPT_RENDERING_PREFER_OIT
   preferoitrendering true

    When this option is set to true, Outside In will use its internal graphics rendering code to produce bitmap output files whenever possible. This option enables Outside In to render images without using the operating system's native graphics subsystem (X11 on UNIX and Linux). This option has an effect only if Outside In has been installed with support for both native graphics and internal graphics output solutions.

  2. Install libXm.so.3 and ln -sf /usr/X11R6/lib/libXm.so.3.0.2 /usr/X11R6/lib/libXm.so.2.0.1.

  3. Use the command find / -name *.ttf to locate the fonts folder on your machine. Set GDFONTPATH to point to the fonts folder. For example, 

    export GDFONTPATH=/opt/IBM/WebSphere/AppServer/java/jre/lib/fonts

  4. Verify the environment variable GDFONTPATH includes one or more paths to the fonts folder.

    Only TrueType fonts (*.ttf or *.ttc files) are supported. If the variable GDFONTPATH is not found, the current directory is used. If fonts are called for and cannot be found, HTML Export will exit with an error. When copying Windows fonts to a UNIX system, the font extension for the files (*.ttf or *.ttc) must be lowercase, or the fonts will not be detected during the search for available fonts. OutsideIn does not provide fonts with any Outside In product.

  5. Change directory to AppServer_root/bin

  6. Restart the server.

  7. Open a Web browser, such as Internet Explorer or Mozilla Firefox, and try to view the file containing images.

 

Visual C++ libraries are required for Windows 2003

To run Document Conversion Services on Windows2003, download Visual C++ libraries included in the Visual C++ 2005 SP1 Redistributable Package available from the Microsoft download site. There are three versions of this package, x86, x64, and IA64 for the 86 - bit, 64 - bit, and 64 - bit Itanium-based systems, respectively.

You need to search the Microsoft download site for the files vcredist_x86.exe, vcredist_x64.exe, or vcredist_IA64.exe. The required version of each of these downloads is the 2005 SP1 Redistributable Package or newer.

 

Parent topic

Configure WebSphere Portal

 

Related concepts


Configuration task properties
Planning for IBM Tivoli License Compliance Manager
Configure portal behavior

 

Related tasks


Configure security
Configure search in a cluster
Set a remote spellchecker
Connecting to existing database domains
Adding features to an administration installation