WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Installing WebSphere Premises Server and Location Awareness Services for WebSphere Premises Server

Follow the steps in this topic to install WebSphere® Premises Server, Location Awareness Services for WebSphere Premises Server, and their prerequisite middleware.

Before you begin
Restriction: Location Awareness Services for WebSphere Premises Server must be installed on a Windows® operating system on the same server as WebSphere Premises Server.
Important: 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.
Important: Enter a password that meets the password rules of the target machine. A password that is not valid will cause installation to fail.
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. 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.
  3. If you would like to use an existing DB2® 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.

    The installer will create three databases for you, but you have the option to install databases manually as well.

  4. If you are running Terminal Server and Terminal Server Licensing, run the change user /install Windows command before starting the WebSphere Premises Server 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 Control Panel > Add or Remove Programs > Add or Remove Windows Components. 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.

  5. Run the installation program located in the sat_installer directory of the WebSphere Premises Server disk for Windows.

    Location Awareness Services for WebSphere Premises Server is only supported on Windows.

    • WindowsSetup.exe

    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.

  6. 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.
  7. 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.
  8. On the Select Tasks panel, click Next to install the product and to choose the database type.
  9. Choose to use DB2 as either your local or remote database. If you do not have DB2 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.
  10. Choose to install WebSphere Premises Server and Location Awareness Services for WebSphere Premises Server and click Next. If you would like to install only WebSphere Premises Server, refer to Installing WebSphere Premises Server. If you would like to install Location Awareness Services for WebSphere Premises Server on top of an existing WebSphere Premises Server installation, refer to Installing Location Awareness Services for WebSphere Premises Server.
  11. 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 Premises Server SystemAgent to reflect the correct location of your Bundle Repository Server.
  12. On the Specify Target Computers panel for your database server, specify the target computer for DB2 database and click Next.
    • For a local server installation for DB2, 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.
    • 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.
  13. On the Specify Target Computers panel for WebSphere Premises Server including Location Awareness Services for WebSphere Premises Server, specify the target computer 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 Premises Server including Location Awareness Services for WebSphere Premises Server and their 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.
  14. On the Specify Target Computers panel for Bundle Repository Server, specify the target computer for Bundle Repository Server 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 Bundle Repository Server on a remote server, specify the fully qualified host name, operating system, user ID, and password of the server where it should be installed.
      Remember: You must install the required middleware on the remote server before installing Bundle Repository Server.
    • 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.
  15. Enter your database configuration information.
    • If you already have a database server installed, enter the correct user ID and password for that database server. If you are installing DB2, enter a user ID and password to be created.
      Remember: Enter a password that meets the password rules of the target machine. A password that is not valid will cause installation to fail.
    • 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 6.1.0.1 tables and click Next. This option is especially useful for remote databases, reinstallation on the same server, and clustered environments.
    • If you have already created your database manually with the scripts provided, select Do not change the database. The database creation is required for the successful installation of WebSphere Premises Server.
  16. Enter the installation directory for WebSphere MQ or accept the default installation directory and click Next.
  17. Enter your WebSphere Application Server configuration information and click Next.
    Restriction: Location Awareness Services for WebSphere Premises Server can only run properly when WebSphere Application Server is installed with the default paths provided by the installer. The installation directory, the name of the profile, the path of the profile, and the ports of this profile must not be modified. Otherwise, Location Awareness Services for WebSphere Premises Server fails.
    Important:
    • 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 Premises Server 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.
  18. Enter your IBM® HTTP Server configuration information and click Next.
  19. Enter the required information for DB2 Universal Database Enterprise Server Edition Client.
  20. Enter the installation directory for WebSphere Premises Server.
  21. Enter the configuration information for Location Awareness Services for WebSphere Premises Server.
    Note: If you would like to install the samples, but your language is not in the S-1 group in DB2, then you should choose -nosamples in the installer panel and manually install the samples instead.
  22. Enter the configuration information for Bundle Repository Server.
  23. 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 Premises Server 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.
  24. Insert the Location Awareness Services for WebSphere Premises Server CD when prompted.
  25. 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
  26. 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 and components installed:

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.

Post-installation steps

Before you begin
If you see errors with the installation, refer to Troubleshooting tips and General 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.
    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.
    1. Open the WebSphere MQ explorer.
    2. 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.
    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
    • AtlasAlertHandlerEJBEAR
    • AtlasEMailSampleServiceEAR
    • AtlasEventSubscriberEAR
    • AtlasImportEAR
    • AtlasReportingServletEAR
    • 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 by going to Start > Control Panel > Administrative tools > Services.
    2. Select IBM WebSphere Premises Server DT Service and click Stop.
    3. Modify the startup sequence for WebSphere Application Server, IBM HTTP Server, WebSphere MQ, and Data Transformation service.

      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.
  11. Restart the Data Transformation service manually by running the dts.bat file in the IBM_RFID_HOME/dts directory.

    This command starts the Data Transformation service and displays 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.
  17. Configure the Spatial Management Client for Location Awareness Services for WebSphere Premises Server.
    1. Change directory to the Spatial Management Client root directory in IBM HTTP Server (for example, C:\Program Files\IBM\HTTPServer\htdocs\en_US\Tracking GUI).
    2. Go to the xml directory and edit the prefsV3.xml file.
      1. Replace localhost with the IP address or the fully qualified host name of your server in the <host> element.
        Note: The value you specify for the <host> element and the value you use to browse to the Spatial Management Client must be identical.
      2. Save your changes.
  18. Enable security for WebSphere Application Server.
  19. Synchronize the DB2 server time and WebSphere Application Server time prior to running your configuration because location events use the DB2 server time for event creation, but Common Event Infrastructure (CEI) events use the WebSphere Application Server time for event creation.
  20. Configure and verify the Location Awareness Services for WebSphere Premises Server installation.
  21. The default Location Awareness Services for WebSphere Premises Server installation can support small scenarios, using between 100 and 200 tags. To use Location Awareness Services for WebSphere Premises Server in a production environment or to use it with more tags, tune your ATLASDB database for additional buffer pools, and add more hard drives to avoid bottlenecks.
What to do next

If you need to uninstall the WebSphere Premises Server and Location Awareness Services for 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.