WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Installing the Sensor Data Services for WebSphere Premises Server

Follow the steps in this topic to install the Sensor Data Services for WebSphere® Premises Server.

About this task
The Sensor Data Services for WebSphere Premises Server installs WebSphere Premises Server on top of an existing WebSphere Remote Server 6.1 installation.
Note: The installer panels refer to Sensor Data Services for WebSphere Premises Server as WebSphere Premises Server.
Procedure
  1. Check your hardware and operating system and make sure that they meet the necessary requirements.
  2. Make sure that you have completed all the prerequisite steps necessary for your environment and that you have already have an existing installation of WebSphere Remote Server.
  3. Install the prerequisite software fix packs for WebSphere MQ, DB2® for Linux®, UNIX®, and Windows®, and WebSphere Application Server.
  4. Verify that you have properly installed WebSphere Application Server before installing the Sensor Data Services for WebSphere Premises Server.
  5. Create the database.
  6. Run the installation program located in the root directory of the Sensor Data Services for WebSphere Premises Server CD appropriate for your operating system.
    • Windows setupwin32.exe
    • Linux setupLinux.bin
    Note: Make sure you run setupLinux.bin from a shell window.
  7. Choose the language for your installation.
  8. In the installation wizard Welcome panel, click Next to continue.
  9. Click 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. After you accept the licensing terms, the installation wizard checks for the product prerequisites.
  10. Select the installation directory for WebSphere Premises Server.
  11. The installation wizard prompts you to select either a Typical or Custom installation.
    • Select the Typical radio button if you are installing both WebSphere Premises Server and the Bundle Repository Server. Click Next to continue.
      Important: If you are installing both WebSphere Premises Server and Bundle Repository Server on the same server, choose to install both (Typical) when prompted. If you choose to install one and later want to install the other, then you will need to uninstall and reinstall the product.
    • Select the Custom radio button if you are installing either WebSphere Premises Server or the Bundle Repository Server. Click Next to continue.
      Important: If you want to install Bundle Repository Server on a server separate from WebSphere Premises Server, install Bundle Repository Server before installing WebSphere Premises Server.
  12. Choose a database type, either DB2 or Oracle, and click Next.
  13. Enter your database information. If you would like the installation program to run database scripts to create tables and populate data on the database you have provided, check Create and populate tables. This option is especially useful for remote databases, reinstallation on the same server, and clustered environments. Click Next.
  14. Choose your WebSphere Application Server installation location and profile and click Next.
    • Choose to install on an existing WebSphere Application Server profile by selecting one of the profiles available on the screen.
    • Choose to create a new profile for installation by selecting the box beside Create new WebSphere profile. This action brings up a WebSphere Application Server profile creation wizard.
      Note: If you are going to use any WebSphere Premises Server APIs or the Print, Verify, and Ship application, set the HTTP transport port to 9080 when you create the profile.
  15. Enter your WebSphere Application Server profile information and click Next.
    • If you have WebSphere Application Server security enabled, you are prompted for the administrator ID and password, which will be validated in order to continue with the WebSphere Premises Server installation.
    • If you do not have WebSphere Application Server security enabled, then you may proceed without filling in an administrator ID and password.
  16. Enter your Web server information or accept the defaults provided and click Next.
    Note: You are prompted for this information only if you chose to install the Bundle Repository Server.
  17. Browse to your WebSphere MQ installation directory and click Next.
  18. If you did not choose to install the Bundle Repository Server with WebSphere Premises Server, a panel prompts you to enter your Bundle Repository Server information.
  19. A summary panel displays your installation selections. Click Install to continue the installation process.
  20. When the installation is complete, another summary panel displays the installation status and prompts you to check the log files for any errors.
    install.log
    • Windows IBM_RFID_HOME\logs\install.log
    • Linux IBM_RFID_HOME/logs/install.log

    If you do see errors or exceptions in the installation log files, try reinstalling the product after changing the installer's input values by according to the install.log file. If you are still seeing errors after reinstalling WebSphere Premises Server, contact IBM® Support.

Results
When you have successfully completed the installation, your server should have the following products installed:

The installation also creates a bundle repository in your IBM HTTP Server document root path, IHS_HOME\htdocs\system_locale\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.

Post-installation steps

Before you begin
If you see errors with the installation, refer to Troubleshooting tips for possible resolutions to the problem.
Procedure
  1. Make sure that the WAS_HOME environment variable is set to point to the WebSphere Application Server installation directory. The default installation directories for WebSphere Application Server are:
    • Windows C:\Program Files\IBM\WebSphere\AppServer
    • Linux /opt/IBM/WebSphere/AppServer
    Important: If you have deployed WebSphere Premises Server remotely, you should log out from the target server and then log in again before continuing with the remaining post-installation steps in order to make sure that the WAS_HOME environment variable is applied correctly.
  2. Make sure that the correct file paths are specified for the edge alerts and heartbeat log files in the SystemAgent.

    See Log file locations and settings for the default installation locations of the edge alerts and heartbeat log files.

  3. Make sure that the delete filter for Data Capture and Delivery is set correctly in the SystemAgent. See Setting the delete filter for Data Capture and Delivery.
  4. Make sure that the IBM RFID and DC Queue Managers are running.
    • Windows Open the WebSphere MQ explorer and look for IBM.RFID.QM and IBM.DC.QM in the Queue Managers folder. If there are green arrows next to each queue manager, then they are running.
    • Linux Run the command dspmq in /opt/mqm/bin. This command tells you the current status of a queue manager.
    If the queue managers are not running, refer to the WebSphere MQ information center for troubleshooting topics.
  5. Make sure all WebSphere Application Server applications are running. Open the WebSphere Application Server administrative console, expand Applications, and click Enterprise Applications.

    The following applications should appear with green status arrows next to them:

    • AMITJ2EE
    • IBM_ALE_Application
    • IBM_Bundles_Management
      Note: If you installed Bundle Repository Server remotely, you will not see this application.
    • IBM_EPCIS_Adapter
    • IBM_Premises_Admin_Console
    • IBM_Premises_Diagnostics
    • IBM_Premises_Event_Monitor
    • IBM_Premises_DockDoorApp
    • IBM_Premises_PVSConsole
    • IBM_Premises_Server
    • IBM_Premises_Server_BIRT
    • IBM_SensorEvent_Engine
    • IBM_SensorEvent_Gateway
  6. Open the WebSphere Premises Server Administrative Console to verify that it is accessible.
  7. Check for errors in the WebSphere Application Server and WebSphere Premises Server log files. Refer to Log file locations and settings for information about where to find the log files.
  8. Open the config.ini file in the IBM_RFID_HOME\dts\configuration directory and update the server IP address, port number, bundle list file, and Data Capture and Delivery controller, as necessary.
    com.ibm.rfid.bundle.list.url=http://IP_address:port_number/bundleadmin/GetBundle?name=http://IBM_HTTP_Server_IP_address/bundles/bundlelists/dc_core4dts.txt

    This code specifies the URL used by the bundle loader to retrieve the list of bundles to load. If the Bundle Repository Server is on a separate server from WebSphere Premises Server, then replace the IP_address and IBM_HTTP_Server_IP_address values in this property with the IP address of the server hosting the Bundle Repository Server.

    The default port number is 9080. This port number is defined when you create your WebSphere Application Server profile.

    The bundle list should be set to the dc_core4dts.txt file.

    com.ibm.rfid.edge.config.url=http://IP_address:port_number/ibmrfidadmin/premises.sl?action=getconfig&edge=E2&version=6.1

    This code specifies the Data Capture and Delivery controller to use. For testing purposes, the configuration uses the default E2 controller, which is shipped as a sample Data Capture and Delivery controller with WebSphere Premises Server. The E2 controller loads the Simulated Reader to help verify your configuration before testing with a real reader. For a production environment, use the E0 controller.

    Note: This step and the next one help you associate WebSphere Premises Server to a local Data Capture and Delivery device that you can use to verify your installation. In a production environment you should use remote Data Capture and Delivery controllers. See Installing a remote Data Capture and Delivery controller for details on how to install them.
  9. Edit the dc_core4dts.txt file and provide the correct IP address of your Bundle Repository Server.

    The default is the localhost address, 127.0.0.1.

    PREFIX http://IP_address/bundles/
  10. If Data Transformation service is started as a service, stop it and complete the following steps as they apply to your topology and desired configuration.
    1. Stop the Data Transformation service.
      • Windows For Windows operating systems, stop the service by going to Start > Control Panel > Administrative tools > Services. Select IBM WebSphere Premises Server DT Service and click Stop.
      • Linux For Linux operating systems, run the ibm_dts_service stop command in the IBM_RFID_HOME/dts directory.
    2. Modify the startup sequence for WebSphere Application Server, IBM HTTP Server, WebSphere MQ, and Data Transformation service.

      Windows For Windows operating systems, if you are running WebSphere Application Server, IBM HTTP Server, WebSphere MQ, and Data Transformation service on the same server, you need to ensure that the Data Transformation service starts after WebSphere Application Server and WebSphere MQ when the computer is rebooted. By default, there can be a situation where Data Transformation service starts before the other applications, resulting in errors.

      1. Run this command.
        Important: The Sc.exe command-line utility syntax requires a space after the = (equal symbol). For more information on this tool, see the Microsoft® Web site.
        sc config IBMWebSpherePremisesServerDTService depend= 
        "MQSeriesServices/IBMHTTPServer6.1/IBMWAS61Service - PremisesNode"
      2. Go to Start > Control Panel > Administrative tools > Services.
      3. Select IBM WebSphere Premises Server DT Service, right-click and select Properties > Dependencies.

        Data Transformation service should show a dependency on the starting of the WebSphere Application Server, IBM HTTP Server, and WebSphere MQ services.

      Note: Setting this dependency also means that the Data Transformation service will stop if you stop any one of the WebSphere Application Server, IBM HTTP Server, or WebSphere MQ services. This dependency also assumes that all of these products are on the same server.

      Linux In a Linux environment, WebSphere Application Server and IBM HTTP Server are not automatically started when the computer reboots, but Data Transformation service and WebSphere MQ are automatically started. If all of the products are installed on the same server, the startup sequence can result in errors.

      To reduce the possibility of errors occurring, remove the ibm_dts_service from the automatic startup by issuing this command:

      chkconfig --level 35 ibm_dts_service off
  11. Restart the Data Transformation service manually.
    • Windows For Windows operating systems, run the dts.bat file in the IBM_RFID_HOME/dts directory.
    • Linux For Linux, run the dts.sh file in the IBM_RFID_HOME/dts directory.
    These commands start the Data Transformation service and display a Data Transformation prompt.
  12. Check the log files for any failures in loading the bundles.
  13. Tune your database to improve performance.
  14. If you are using the Print, Verify, and Ship example usage scenario, edit the contents of the pvsapp.properties file to point to the correct directory and host name for your IBM HTTP Server. Specifically, modify the following properties: premises.hostname, report.location.csv, and report.location.csv.url. The pvsapp.properties file is located in the \installedApps\profile_cell_name\IBM_Premises_PVSConsole.ear\ibmrfid_premises_pvsapp.war\config\ directory.
  15. If you are using the Print, Verify, and Ship example usage scenario, enable ALE.
    1. Open the WebSphere Application Server administrative console.
    2. Navigate to Resources > JMS > Activation specifications > ALEWrapperAS.
    3. Change the text in the Message selector field to ibmse='RfidInventory/TagReport' OR ibmse='RfidInventory/TagAggregationReport' OR ibmse LIKE '%/report/TagReport' OR ibmse LIKE '%/report/TagAggregationReport'.
  16. Verify the WebSphere Premises Server installation. Choose R2 as your simulated test reader.
What to do next

If you need to uninstall the WebSphere Premises Server software, refer to Uninstalling WebSphere Premises Server.


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.