Technical Requirements
The Installation Process
Configuring Tuxedo for Isis
Configuring WebLogic for Isis
The installation of Isis is a relatively straight forward
process. Firstly ensure that the machine you are installing
Isis on is capable of supporting the Isis application, the
requirement of that environment are discussed below in Technical
Requirements, next install the Isis product with the Isis installer and the finally configure
BEA WebLogic or Tuxedo to
work with Isis.
If you are having problems with your installation, please
feel free to contact Integral support, for details on contacting
support click here.
Before installing Isis, please ensure that the target machine
meets the following requirements:
· VGA monitor with minimum 800x600 resolution and 256 colors
· Approximately 100MB of hard drive space
· 128 MB of RAM or more preferred
While Isis is a lightweight application, the processing it
performs can be quite memory-intensive. During a typical Isis
session a user may be reviewing generated reports within Excel,
generating reports and monitoring several applications concurrently.
In order to ensure the best experience possible, ITS recommends
at least 128 MB of RAM.
· Windows 2000
· Office 97 or later
· Tuxedo 6.5 or later client libraries
Pre-configuration for Tuxedo and WebLogic applications.
Please note that some pre-configuration for Tuxedo or
WebLogic may be required to allow Isis to run successfully.
Please see the Configuring Tuxedo
for Isis and the Configuring
WebLogic for Isis sections below for further information.
top of page
This will begin the brief installation wizard that guides
the user through the process of installing Isis.
The following screens will appear as the next steps of the
wizard. They require no information from the user, but display
important information regarding Isis, and should be read through
completely before installing Isis.
This screen contains general information and any new information
regarding Isis that may have been documented after the creation
of this manual.
This screen contains the license agreement that the user must
accept as part of the process of installing Isis. While there
are no non-standard clauses in this agreement, it is recommended
that the user read this section thoroughly for their own protection.
This screen allows the user to select the location to install
Isis to. Once a location has been confirmed, the installer
will install Isis to the location specified. As part of the
installation process, several DLL files will be copied to
the Windows system directory and registered. This process
should take a matter of seconds, and once complete, Isis is
ready for use.
Note: It is not necessary to reboot once Isis has been
installed - the program is ready for use immediately after
installation.
Should any errors occur during the installation process, the
installer will allow the user to automatically remove any
files installed as part of the failed process. For more information
on general troubleshooting with Isis, or contact details for
Integral Support, please click here
.
Note: Selecting the About button on any of the installation
wizard screens will display information regarding Tarma Installer,
Integral's preferred installation package. For more information
regarding Tarma Installer, refer to http://www.tarma.com/products/tin/
top of page
Isis can manipulate log files created by standard Tuxedo server
functionality to provide detailed service execution time statistics.
In order to generate these log files, all Tuxedo servers to
be monitored in the Tuxedo application must be configured to
support txrpt. This requires the addition of two command line
option switches.
A bare-bones Tuxedo server entry within a UBBconfig file might
look as follows:
| ServerName |
SRVGRP=SVRGRP1 SRVID=21106 |
In order to support the generation of txrpt files, the entry
must be modified as follows:
| ServerName |
SRVGRP=SVRGRP1 SRVID=21106
CLOPT="-A -e StatLog -r" |
The three switches added (-A, -e and -r) have the following
effect:
| -A |
Ensures that Tuxedo server advertises
all available services. Typically this is the default
command line option (CLOPT) for a Tuxedo server. |
| -e |
Writes all error information (any
output sent to STDERR) to the file specified. (in this
case, StatLog) |
| -r |
Ensures that ServerName will produce
a record for each service call performed, and write that
information to STDERR. |
The changes required to the Tuxedo servers can also be done
dynamically through the use of the Tuxedo WebGUI console.
For information on how to dynamically change the options on
Tuxedo servers please see the
Please note that activating txrpt reports causes a line of
log data to be written on each Tuxedo service call. While
the performance degradation incurred through this write is
negligible, on production systems the size of these log files
can grow over time to be quite large. It may be worthwhile
using the same cleanup procedures used for the Tuxedo ULOGs
to ensure that these log files do not grow to an unmanageable
size.
top of page
Isis uses the WebLogic SNMP agent to gather information on
the production characteristics of the WebLogic system. In
order for Isis to gather this information, the WebLogic SNMP
agent will need to be enabled.
The WebLogic SNMP agent has been included with each version
of WebLogic from 5.1 onwards, however the method for running
the SNMP agent has varied between versions. For the full details
on how to run the SNMP agent please see the BEA documentation
for your version of WebLogic at edocs.bea.com,
however a brief description of what is required is also included
below.
WebLogic Server is often in protected
behind firewalls or other devices to ensure the safety of
the system from hackers. However, these device can also prevent
traffic on unusual ports (like SNMP) from getting through.
When you configure the SNMP agent for WebLogic it is important
to ensure that the Isis application can connect to the port
that the SNMP agent is running on, otherwise no data will
be able to be recorded.
Please note also that despite being part of WebLogic 5.1,
SNMP support was dropped in WebLogic 6.0 and did not reappear
until WebLogic 6.1. Because Isis requires SNMP to gather WebLogic
information, Isis cannot support WebLogic 6.0.
In the installation directory for WebLogic 5.1 you will
find a script file called startSNMPagent.sh or startSNMPagent.cmd
(depending if you are running Unix or Windows respectively).
You will need to modify this file to provide the ports that
you want the SNMP agent to connect to (for both WebLogic and
SNMP) and then run the file.
The SNMP agent will load and connect to WebLogic, Isis should
now be able to record data by connecting to the SNMP agent
on the port and IP address that you specified. If you are
having issues getting the SNMP agent to work, then please
see the BEA documentation at edocs.bea.com.
SNMP was not included as part of WebLogic 6.0, please
upgrade to WebLogic 6.1 to use Isis.
From WebLogic 6.1 and above, SNMP is configured through the
WebLogic Console. To turn on SNMP, run the WebLogic Console
and then select the domain --> configuration --> SNMP
off the left hand menu. From this screen you can now enable
WebLogic SNMP. If you are having issues getting the SNMP agent
to work, then please see the BEA documentation for your version
of WebLogic at edocs.bea.com.
top of page
|
