Documente Academic
Documente Profesional
Documente Cultură
SmartMapper
Installation Guide
Software Release 5.3
January 2007
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY
(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE.
THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY
ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT,
THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING
DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE
TIBCO BusinessWorks SmartMapper Installation Guide ). USE OF THIS DOCUMENT IS SUBJECT TO
THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE
ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright
laws and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIB, TIBCO, Information Bus, The Power of Now, TIBCO Adapter, TIBCO BusinessWorks, TIBCO
Designer, and TIBCO Administrator are either registered trademarks or trademarks of TIBCO
Software Inc. in the United States and/or other countries.
EJB, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of
Sun Microsystems, Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of
their respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER,
NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE
RELEASED AT THE SAME TIME. PLEASE SEE THE README.TXT FILE FOR THE
AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM
PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL
ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
Copyright © 1999-2007 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Preface
Topics
Related Documentation
Typographical Conventions
• In large code samples, to indicate the parts of the sample that are of
particular interest.
• In command syntax, to indicate the default value.
Key Key name separated by a plus sign indicate keys pressed simultaneously. For
combinations example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.
Convention Use
[ ] An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
Convention Use
| A logical ’OR’ that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
bold code In command syntax, indicates the default parameter for a command.
font
For example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
In the next example, the command requires two parameters. The first parameter
can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters.
The first parameter must be param1. You can optionally include param2 as the
second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
For comments or problems with this manual or the software it addresses, please
contact TIBCO Support as follows.
• For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
• If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
Topics
• Introduction, page 2
• Installing Versions with Higher Version Numbers, page 4
• Installation Registry, page 5
Introduction
Installer Overview
The installer allows you to run in different modes. Each mode is supported on all
platforms.
• GUI mode
• Console mode
• Silent mode
GUI Mode
In GUI mode, the installer presents panels that allow you to make choices about
product selection, product location, and so on. When you invoke the installer by
double-clicking on the icon, GUI mode is used.
Console Mode
Console mode allows you to run the installer from the command prompt or
terminal window. This is useful if your machine does not have a Windows
environment.
Silent Mode
Silent mode either installs using default settings or uses a response file that was
saved during an earlier installation. Silent mode installs without prompting you
for information.
• If no response file has been recorded earlier and you invoke the installer with
the -silent argument, the default installation parameters are used.
• If a response file exists, and the installer is started with -options
responseFileName as an argument, the installer uses the values specified by the
user when the response file was generated.
The response file can be created by providing
-console -options-record /dir/responseFile at installation time.
For more information about installation options, see TIBCO Runtime Agent
Installation Guide, section Installation Options.
Supported Platforms
For the list of supported platforms and their versions, refer to the file readme.txt.
Manual steps must be performed to enable TIBCO applications to run in 64-bit
mode. See TIBCO Runtime Agent Installation Guide for details.
If you install a product and that product is already installed on your machine, you
cannot choose a different location from that specified above. If you wish to install
the product in a different location, you must completely remove the product from
the machine.
Installation Registry
Do not edit, modify, rename, move, or remove any of the registry vpd files.
The VPD files contain information about the TIBCO products installed on a
machine. They are updated each time a TIBCO product is installed or uninstalled.
When you start TIBCO Administrator, TIBCO Hawk or TIBCO Domain Utility,
the VPD files are checked for the list of installed software. For example, after you
install a TIBCO product and start TIBCO Administrator, the Installed Software
console in the TIBCO Administrator GUI is updated based on information in the
VPD files.
%SystemRoot%\vpd.properties
%SystemRoot%\vpd.properties.tibco.systemName
UNIX Platforms
If installation is performed by a regular user (non-root), the installation registry is
maintained in the following files in the user's home directory:
User_Home_Directory/vpd.properties
User_Home_Directory/vpd.properties.tibco.systemName
• On Solaris and HP-UX, in the root user’s home directory (which is /) as vpd
files.
• On Linux, in the /root directory as vpd files.
• On AIX, in the /usr/lib/objrepos directory as vpd files.
The installer uses an existing JVM if the version it requires is available on your
system. In that case, the bundled JVM is not extracted and significantly less disk
space is required.
On UNIX platforms the following disk space is required in the temporary area:
• On Solaris, 50 MB of free disk space in /var/tmp
• On HP-UX, 85 MB of free disk space in /var/tmp
• On AIX, 30 MB of free disk space in /tmp
• On Linux, 50 MB of free disk space in /tmp
If your system does not have sufficient free disk space in the above temporary
area, you can still run the installer with a different temporary area by using the
following option when starting the installer:
-is:tempdir /new_tmp
Installation History
The installer creates a file called TIBCOInstallationHistory.xml in the location
where the installation registry is created. Each time an installation or
uninstallation is performed, entries are appended to the file.
On Windows: %SystemRoot%\TIBCOInstallationHistory.xml
On UNIX: Users_Home_Directory/TIBCOInstallationHistory.xml
The file TIBCOInstallationHistory.xml therefore contains the record of all
installation and uninstallation activities of all products, features and components.
Topics
• Introduction, page 10
• Installing on Microsoft Windows, page 12
• Installing on UNIX, page 16
Introduction
The procedure for installing the BusinessWorks SmartMapper plug-in and the
Enterprise Server is the same. The only difference is the package name. The
Enterprise Server packages use eps in the package name.
For example, the plug-in package name for Microsoft Windows is
TIB_smartmapper-simple_n.n.n_win_x86.exe and the package name for the
Enterprise Server is TIB_smartmappereps-simple_n.n.n_win_x86.exe.
System Requirements
The following are the minimum disk space and memory requirements, excluding
database requirements:
• Free disk space: 35 MB
• Memory: 512 MB RAM.
More memory allocated to the cache can mean faster data access.
Installer Account
You must have administrator privileges for the machine on which TIBCO
BusinessWorks SmartMapper is installed.
If you do not have administrator privileges, the installer exits. You must then log
out of the system and log in as a user with the required privileges, or request your
system administrator to assign the privileges to your account.
If you install in the Execute mode, the installation registry is maintained in your
user home directory. If you install in the Install mode, the installation registry is
maintained in the %SystemRoot% folder.
When running in console mode you can move through the installation process as
described next:
Enter Key = Moves forward in the installer
2 = Goes back to previous screen
3 = Cancels the Wizard and exits the installation or uninstallation
4 = Redisplays the current screen
TIB_smartmapper-simple_n.n.n_win_x86.exe -options-record
C:\directoryPath\responseFileName
The response file does not record selections at the component level It does record
all other selections, for example, which products you wished to install.
Combining Options
You can combine the different available options. For example, to install in silent
mode using a response file, use:
Uninstalling on Windows
To uninstall:
1. Select Start>Programs>TIBCO>TIBCO Uninstaller.
2. Select TIBCO BusinessWorks SmartMapper and click Uninstall.
3. Login to TIBCO Administrator as an administrator.
4. Expand Application Management.
5. Click All Service Instances.
6. Click machine-name - TIBCO Administrator.
7. Click the Plug-ins tab.
8. Select the checkbox next to SmartMapper Admin Plug-ins.
9. Click Remove.
10. Click Done.
Installing on UNIX
Installer Account
TIBCO 5.x products can be installed by a regular (non-root) user and super-user
(root). Different users can install the same product at different locations.
Product dependencies at install time are resolved at user level through the
installation registry maintained at user's home directory. See Installation Registry
on page 5 for more information.
Windows Environment
A window environment such as CDE (that is, X Windows) is required to run the
installer in GUI mode. It is not required for a console installation.
% ./TIB_smartmappereps-simple_n.n.n_sol7_sparc.bin
% ./TIB_smartmappereps-simple_n.n.n_sol7_sparc.bin -is:javaconsole
-console
When running in console mode, you can move through the installation process as
described next:
% ./TIB_smartmappereps-simple_n.n.n_sol7_sparc.bin -silent
% ./TIB_smartmappereps-simple_n.n.n_sol7_sparc.bin -options-record
/directoryPath/responseFileName
The response file does not record selections at the component level It does record
all other selections, for example, which products you wished to install.
Combining Options
You can combine the different available options. For example, to install in silent
mode using a response file, use:
% ./TIB_smartmappereps-simple_n.n.n_sol7_sparc.bin -silent
-options responseFileName
Permissions
All TIBCO BusinessWorks SmartMapper users must have read, write, and execute
permissions for the following directories:
$TIBCO_HOME/smartmapper/n.n.n/bin
$TIBCO_HOME/smartmapper/n.n.n/logs
$TIBCO_HOME/tra/n.n.n/logs
For example, if TIBCO BusinessWorks has been installed in /opt/tibco, the user
who installed TIBCO BusinessWorks should execute the following commands:
Uninstalling on UNIX
To uninstall on UNIX, do the following:
1. You should be logged in to UNIX as root. If you are using a remote xterm
session, make sure you have set and exported the DISPLAY environment
variable. Example: export DISPLAY=myLocalHost:0.0. Make sure that you
are allowed access from remote session to display locally. Run the xhost+
command from your local machine to allow connections from the target
machine.
2. Navigate to the install-path/tibco directory.
3. Invoke TIBCOInstallationManager.
4. Select TIBCO BusinessWorks SmartMapper and click the uninstall button.
5. Login to TIBCO Administrator as an administrator.
6. Expand Application Management.
7. Click All Service Instances.
8. Click machine-name - TIBCO Administrator.
9. Click the Plug-ins tab.
10. Select the checkbox next to SmartMapper Admin Plug-ins.
11. Click Remove.
12. Click Done.
Topics
• Introduction, page 22
• Restarting the TIBCO Administrator Server, page 23
• Configuring BusinessWorks SmartMapper to Run in 64-Bit Mode, page 24
• Setting Up Tables for Databases, page 27
Introduction
To use the BusinessWorks SmartMapper model tables, you can either have a
storage system that is file-based, or you can use a database.
The following databases are supported:
• Oracle
• Microsoft
• DB2
See the TIBCO BusinessWorks SmartMapper readme.txt file to see which DBMS
versions the software supports
If you do not restart the TIBCO Administrator server, the SmartMapper console
may not load correctly in TIBCO Administrator and will not display in the TIBCO
Administrator GUI.
Since AIX and Linux platforms have 64-bit installers, after installing
BusinessWorks SmartMapper with these installers the software can be run
without modifying property files for executables.
HP-UX and Solaris platforms do not have 64-bit installers, and after installing
BusinessWorks SmartMapper on these two platforms you must change the
property files to enable them to run in 64-bit mode.
HP-UX on IA-64/Itanium
To modify BusinessWorks SmartMapper for HP-UX on IA-64/Itanium and enable
it to run in 64-bit mode, do the following:
1. Change directory to SM_HOME/bin
a. Copy the file adsmartmapper to adsmartmapper-bak
b. Copy the file adsmartmapper64 to adsmartmapper
c. Copy the file adsmartmapper.tra to adsmartmapper-bak.tra
2. Using a text editor, open the file adsmartmapper.tra and make the following
changes:
a. Find all occurrences of IA64N and replace with IA64W
b. In the property tibco.class.path.extended, find RV_HOME/lib and
replace it with RV_HOME/lib/tibrvj.jar
3. Save the file and exit the text editor.
HP-UX on PA-RISC
To modify BusinessWorks SmartMapper for HP-UX on PA-RISC and enable it to
run in 64-bit mode, do the following:
1. Change directory to SM_HOME/bin
a. Copy the file adsmartmapper to adsmartmapper-bak
b. Copy the file adsmartmapper64 to adsmartmapper
c. Copy the file adsmartmapper.tra to adsmartmapper-bak.tra
2. Using a text editor, open the file adsmartmapper.tra and make the following
changes:
a. Find all occurrences of PA_RISC2.0 and replace with PA_RISC2.0W
b. In the property tibco.class.path.extended, find RV_HOME/lib and
replace it with RV_HOME/lib/tibrvj.jar
3. Save the file and exit the text editor.
2. Using a text editor, open the file adsmartmapper.tra and make the following
changes:
a. In the property tibco.env.JVM_LIB_DIR, replace sparc with sparcv9
b. In the property tibco.env.JVM_LIB_PATH, replace sparc/client with
sparcv9/server
Solaris 10 on x86
To modify BusinessWorks SmartMapper for Solaris 10 on x86 and enable it to run
in 64-bit mode, do the following:
1. Change directory to SM_HOME/bin
a. Copy the file adsmartmapper to adsmartmapper -bak
2. Using a text editor, open the file adsmartmapper.tra and make the following
changes:
a. In the property tibco.env.JVM_LIB_DIR, replace sparc with amd64
b. In the property tibco.env.JVM_LIB_PATH, replace sparc/client with
amd64/server
Linux on x86
To modify BusinessWorks SmartMapper for Linux on x86 and enable it to run in
64-bit mode, do the following:
1. Change directory to SM_HOME/bin
2. Copy the file adsmartmapper to adsmartmapper-bak
3. Copy the file adsmartmapper64 to adsmartmapper
4. Copy the file adsmartmapper.tra to adsmartmapper-bak.tra
5. Using a text editor, open the file adsmartmapper.tra and make the following
changes:
— In the property tibco.class.path.extended, replace RV_HOME/lib with
RV_HOME/lib/tibrvj.jar
AIX on POWER
To modify BusinessWorks SmartMapper for AIX on POWER and enable it to run
in 64-bit mode, do the following:
1. Change directory to SM_HOME/bin
2. Copy the file adsmartmapper to adsmartmapper-bak
3. Copy the file adsmartmapper64 to adsmartmapper
4. Copy the file adsmartmapper.tra to adsmartmapper-bak.tra
5. Using a text editor, open the file adsmartmapper.tra and make the following
changes:
— In the property tibco.class.path.extended, replace RV_HOME/lib with
RV_HOME/lib/tibrvj.jar
Index
C R
console mode, installation 2 restart TIBCO Administration server 23
customer support ix
S
D
setting up tables — MS SQL DBMS 27
Disk Space Requirement in User's Home Directory 6 setting up tables — Oracle DBMS 27
setting up tables for DB2 28
setting up tables for MS SQL server 27
setting up tables for Oracle 23, 27
I silent mode, installation 3
support, contacting ix
Installation
History 7
Registry and History 5
installation history 7 T
Installer
Disk Space in Temporary Area 6 technical support ix
Installing
Versions with Higher Version Numbers 4
installing components separately 10
installing in console mode 2 U
installing in GUI mode 2
installing in silent mode 3 uninstalling on Windows 15, 19
installing on UNIX 16 UNIX Platforms 5
installing on Windows 12 UNIX, installation registry 5
installing TIBCO BusinessWorks SmartMapper
Plug-in on Windows 9
installing versions with higher version numbers 4
M
Microsoft Windows Platforms 5
MS Windows, installation registry 5