Follow the steps in this topic to install WebSphere® Sensor Events and its
prerequisite middleware.
Before you begin
Stop all WebSphere Application Server profiles
before you run the installer.
Important installation tips: - When specifying installation
paths, make sure the directories contains only US English ASCII characters.
Also enter only US English ASCII characters in directory paths in
properties files.
- Enter
a password that meets the password rules of the target machine. A
password that is not valid will cause installation to fail.
Procedure
- Check your hardware and operating system and make sure that they meet the necessary
requirements.
- Make sure that you have completed all
the prerequisite steps necessary
for your environment. If you would like to modify the path
used by the deployment wizard, follow the steps in Changing the deployment wizard path before launching
the installation program.
- Make sure your database is encoded for
UTF-8.
- If you plan to use DB2® as
your database server, and you would like to use an existing database,
make sure that database was created with the option to Enable
database for XML (Code set will be set to UTF-8). If your DB2 database was not created with
that option, you will need to delete and recreate that database if
you want to use it.
- If you are using Oracle, make sure that the database was created
with the Unicode AL32UTF8 character set.
The installer will create a database for you, but you have
the option to install one manually as
well.
- If you have a Windows® operating system and you are running
Terminal Server and Terminal Server Licensing, run the change
user /install Windows command
before starting the WebSphere Sensor Events installation
program.
If you do not issue this command and you have
those Windows components
installed, the installation may fail because the installer cannot
write to the vpd.properties file. To see if you
have Terminal Server and Terminal Server Licensing installed, navigate
to . When you have successfully issued the command, the
response is User session is ready to install applications. or Install
mode does not apply to a Terminal server configured for remote administration. if
the command was not needed. For more information, refer to the Windows Server
2003 Product Help.
- Run the installation program located in
the root directory of the first WebSphere Sensor Events disk
appropriate for your operating system.
If
you have a Linux® operating
system, make sure you run LinuxSetup from a new
shell window.
WindowsSetup.exe
LinuxSetup
When you run the installation program,
the deployment wizard is temporarily installed on your hard drive.
It will uninstall itself when the installation is complete. When the
deployment wizard installation completes, it automatically launches
and guides you through the installation of the product and its prerequisite
software. It may take a few minutes to begin.
You can also run
the installation program in silent mode. Refer to Installing silently for further instructions.
- Select the radio button beside the I
accept both the IBM and the non-IBM terms statement if
you agree to the license agreement and click Next to
continue.
- When the Welcome panel appears you can either:
- Click Next to continue installing the
product.
- Or, if you would like to change the default path used for
the deployment package, follow the instructions in Changing the deployment package path before continuing
with the next steps.
- On the Select Tasks panel, click Next to
install the product and to choose the database type.
- Choose to use either DB2 or Oracle as your local or remote database.
- If you choose DB2 and
do not have it installed on your server, then the installer will install
it for you if you want it installed locally. If you already have DB2 installed on your local server,
then the installer will recognize that it is already there and check
to make sure it meets the requirements.
- Choose Oracle if you have an existing installation of that
database that you would like to use.
- Choose to install WebSphere Sensor Events only
and click Next. If you would like
to install both WebSphere Sensor Events and IBM® Location Awareness Services for WebSphere Sensor Events, refer
to Installing WebSphere Sensor Events and Location Awareness Services for WebSphere Sensor Events. If you would like
to install Location Awareness Services for WebSphere Sensor Events on
top of an existing WebSphere Sensor Events installation,
refer to Installing Location Awareness Services for WebSphere Sensor Events.
- Click Next to install
the required Bundle Repository Server.
Note: If you do not install
Bundle Repository Server on your
local server, then you need to install the prerequisite middleware
on the remote server before installing
Bundle Repository Server. Make
sure that you have purchased a separate license for the required middleware
that you install on a remote server. Also, you will need to modify
the
WebSphere Sensor Events SystemAgent
to reflect the correct location of your
Bundle Repository Server.
- On the Specify Target Computers panel for
your database server, specify the target computer for DB2 or your existing Oracle database and click Next.
- For a local server installation for DB2 or
an existing installation of Oracle, the default value is localhost.
You can either keep this value or change it.
- If you are installing the product and DB2 on separate servers, specify the fully qualified
host name, operating system, user ID, and password of the server where DB2 should be installed.
- If you are installing the product on one server and using an existing
Oracle installation on another server, specify the fully qualified
host name, operating system, user ID, and password of the server where
Oracle is installed.
- Optionally, use the Test connections button
to test access to the remote target computer. Firewalls can have an
adverse effect on the installation even though the connection test
result is successful.
- On the Specify Target Computers panel
for WebSphere Sensor Events,
specify the target computer for WebSphere Sensor Events and click Next.
- For a local server installation, the default value is localhost.
You can either keep this value or change it.
- If you are installing WebSphere Sensor Events and its
required middleware on a remote server, specify the fully qualified
host name, operating system, user ID, and password of the server where
it should be installed.
- Optionally, use the Test connections button
to test access to the remote target computer. Firewalls can have an
adverse effect on the installation even though the connection test
result is successful.
- On the Specify Target Computers panel for Bundle Repository Server, specify
the target computer for Bundle Repository Server and click Next.
- Enter your database configuration information.
Restriction: If
you install DB2 remotely on
a Windows operating system,
be sure that your WebSphere Sensor Events server
and the remote server have the same drive letter for the DB2 installation. For example, if you want to
use drive F on your remote server for the DB2 installation, then your WebSphere Sensor Events server
should also have a drive F.
- Enter the necessary information for WebSphere MQ and click Next.
If you are installing on a Windows operating system, you are prompted
to enter the installation directory for WebSphere MQ or accept
the default installation directory.
If you are installing on a Linux operating system, you are prompted for
a password.
- Enter your WebSphere Application Server configuration
information and click Next.
Important: - If you have an existing version of WebSphere Application Server that is
6.1.0.0 or later (but not the required version 6.1.0.23), and you
want the installer to update your WebSphere Application Server version,
then you must have WebSphere Application Server stopped
before deploying the WebSphere Sensor Events installation.
- WebSphere Application Server security
is not enabled by the installer. You must set up and configure security
separately.
- If you are going to use any WebSphere Sensor Events APIs
or the Print, Verify, and Ship application,
make sure that the profile you choose to use has the HTTP
transport port set to 9080.
- If you do not plan to install WebSphere Application Server and the WebSphere Application Server profile
path on the default drive (such as the C drive on Windows operating systems),
you can change the installation directory on the Installation tab
and the profile path on the Advanced tab. Make
sure your WebSphere Application Server profile
path reflects the correct drive location for your installation.
- Enter your IBM HTTP Server configuration
information and click Next.
- Enter the installation
directory for the WebSphere Application Server Web server
plug-ins.
The default value in this panel creates a
new Plugins directory in the WebSphere directory.
If you choose to use an existing directory for your plug-ins, make
sure that the existing directory does not already contain any files.
If it does, then the installation could fail.
- Enter the configuration information
for WebSphere Business Events.
- Enter the installation directory for WebSphere Sensor Events.
Reminder: If you changed the default
installation path for WebSphere Application Server, make
sure that you modify the installation path for WebSphere Sensor Events to match
the WebSphere Application Server path.
- Enter the configuration information for Bundle Repository Server.
- On the Summary Panel, confirm your choices. The summary provides a list of tasks that you selected and an
estimated time for their completion.
- To start all installation and configuration tasks, click Deploy
all.
- If you only want to start a specific task, click Deploy
task, but make sure that the tasks you choose are in the
correct sequence on the panel. For example, you cannot deploy WebSphere Sensor Events before
deploying DB2 if you do not
already have a database installed.
Click Back to make any changes. After
you start the deployment, you have the option to click Stop
Deployment if you need to stop the installation before
it is finished. Once all deployment tasks are complete,
the Deployment Status screen indicates if the deployment was successful.
- Insert the second WebSphere Sensor Events DVD when
prompted.
- When the installation is complete, check the
log files for any errors. From the Deployment wizard,
you can view detailed messages or the master log. Click Master
log and select Save as... to save
the log file. The logs can be found in deployment_wizard_installation_dir/logs,
where deployment_wizard_installation_dir is the
installation location of the Deployment wizard.
C:\Program Files\SolutionFiles\logs
opt/SolutionFiles/logs
- Click the X at the top, right-hand side of
the panel to exit the wizard. The wizard displays some
messages:
- A prompt for whether you want to save changes. If you plan to
run the wizard again, click Yes. Otherwise,
click No.
- A prompt for whether you wish to exit. Click Yes to
exit the wizard.
Results
When you have successfully completed the installation, your
server should have the following products installed:
- WebSphere Sensor Events in this
default location:
C:\Program Files\IBM\RFID
/opt/IBM/RFID
- WebSphere Application Server
- WebSphere MQ
- IBM HTTP Server
- WebSphere Business Events
- DB2 Workgroup Server Edition (if you
selected to install it)
- a Bundle Repository Server (installed
either locally or remotely)
The installation also creates a bundle
repository in your IBM HTTP Server document
root path, IHS_HOME\htdocs\en_US\bundles.
For example, the path for a Windows operating
system may be C:\Program Files\IBM HTTP Server\htdocs\en_US\bundles.
This repository stores all the device application bundles for OSGi
Equinox for management by the Bundle Repository Server.
What to do next
Complete the Post-installation steps.