Tip:
Highlight text to annotate it
X
Download from Jazz.net the RRDI package and extract the ZIP file. After doing so, open the launchpad.
When opening the launchpad at this point, under "Installation planning" there will be a section called "Validate environment".
The requirements for the RRDI software are quite in depth. You must pay attention to all the
operating system level values and properties that are required.
Click on "Specific Considerations if Installing on Linux".
This leads you to the "Additional steps required for the report server" on Linux systems page in the CLM Information Center.
The first step is to validate, using the "rpm" package, if "LibXp" and Open Motif
are the right versions in place on the operating system.
All of this is done as the "root" user.
Open a new terminal and login as "root".
Run the "rpm" query command.
Verify if the Open Motif package is installed and at the right level.
Looking at the package name and the package value required, it appears to be the right package installed.
The next step will be to look for the "libXp" package.
There does appear to be a "libXp" package installed.
Those requirements are met at this point.
Next step is to navigate to the "/usr/lib" directory.
Validate if you have the right "libXm" or symbolic link available for the environment.
Make sure that the "libXm" value is a 32-bit library.
To do this, do a listing of all the "libXm" files that exist in this directory.
You can see that you have the "libXm.so.4" as expected.
To find out if the "libXm.so.4" is the right library,
issue a file command against the particular file itself which will tell you the version of the file.
In this case, you are looking at a 32-bit library. This is what is expected for the RRDI software environment.
"libXm.so.4" is not the right name for a library
to support the RRDI software. You must create a symbolic link
from "libXm.so.4" to "libXm.so.3" so that the RRDI package recognizes the library.
Do a listing of the "libXm" values to confirm that the symbolic link is as expected.
Next is "libfreetype" file.
By using the "ls" command, confirm that "libfreetype.so" exists.
In an Oracle environment, this is the minimum requirement for the libraries for the RRDI software install.
The next task is to set up an environment variable called "LD_LIBARY_PATH"
You make sure that all the links that the RRDI software requires are reachable through this environment variable.
To do this, you can create a file called "setUpRRDI"
which is a file that will eventually be used as a source
to populate the "LD_LIBARY_PATH" environment variable. All you
put in this file is an export command for the "LD_LIBARY_PATH"
variable, which is equal to the "/usr/lib" directory at this time.
The "LD_LIBARY_PATH" will eventually be useful with a setup of the Oracle client.
Keep in mind that we might have to modify this path through other methods.
The source file created in this demonstration is only a suggestion.
You must understand how to manage all the environment variables and how to setup and start the application.
You must understand that all the libraries and
environment variables required to setup the RRDI environment are required when starting up the WebSphere Application Server that supports the
RRDI console interface. There are several methods to make sure that this is loaded. You can use the .bash profiles used
in the path for the converter to load the source files that will be created for the system environment and the Oracle environment.
Alternatively, you can source those files before you start the WebSphere
startup scripts within the scripts themselves or before your user starts the scripts. This is at your choice.
What is required is that these environment variables and these links be available before starting the application server.
After creating the setup RRDI file,
you can test the "LD_LIBARY_PATH" environment variable. Though, at this time there will
be no value in the "LD_LIBARY_PATH" since you have not set a path.
Here is an example of how you can source this file to setup "LD_LIBARY_PATH".
This command can be placed in the "startserver.sh" file or be included in the .profile
for the "root" user so that every time the user logs in it is available to the command line.