WebSphere brand IBM WebSphere Sensor Events, Version 6.2

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 cache.refresh.interval property for the System Agent has been met before trying to access the WebSphere Sensor Events server.
    Note: This property is configurable for time delays at startup and after updates. The default value is 60 seconds. Be aware of this delay because if an application tries to query the agent property information within that first minute, it cannot be successfully retrieved.
  2. 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 Sensor Events 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.
  3. 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.

  4. 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.
  5. Make sure that the DC Queue Manager is running.
    1. Open the WebSphere MQ explorer.
    2. Look for IBM®.DC.QM in the Queue Managers folder. If there is a green arrow next to the queue manager, then it is running.
    If the queue manager is not running, refer to the WebSphere MQ information center for troubleshooting topics.
  6. 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
    • AMITJ2EE
    • IBM_WSE_ALE_Application
    • IBM_WSE_Admin_Console
    • IBM_WSE_Bundles_Management
      Note: If you installed Bundle Repository Server remotely, you will not see this application.
    • IBM_WSE_Container_Tracking
    • IBM_WSE_Diagnostics
    • IBM_WSE_DockDoor_Receiving
    • IBM_WSE_EPCIS_Connector
    • IBM_WSE_Engine
    • IBM_WSE_Event_Monitor
    • IBM_WSE_Gateway
    • IBM_WSE_PVS_Console
    • IBM_WSE_RUC
    • IBM_WSE_RUC_BackendImpl
    • IBM_WSE_Server
    • IBM_WSE_Server_BIRT
    • IBM_WSE_Track_Trace
    • wberuntimeear
  7. Open the WebSphere Sensor Events Administrative Console to verify that it is accessible.
  8. Check for errors in the WebSphere Application Server and WebSphere Sensor Events log files. Refer to Log file locations and settings for information about where to find the log files.
  9. 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 Sensor Events, 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 Sensor Events. 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 Sensor Events 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.
  10. 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/
  11. 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 Sensor Events 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 IBMWebSphereSensorEventsDTService
        depend= 
        "MQSeriesServices/IBMHTTPServer6.1/IBMWAS61Service - PremisesNode"
      2. Go to Start > Control Panel > Administrative tools > Services.
      3. Select IBM WebSphere Sensor Events 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.
  12. 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.

  13. Check the log files for any failures in loading the bundles.
  14. Tune your database to improve performance.
  15. 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_WSE_PVSConsole.ear\ibmrfid_premises_pvsapp.war\config\ directory.
  16. 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'.
  17. If you are planning to use the Container Tracking use case, modify the message selector.
    1. Open the WebSphere Application Server administrative console.
    2. Navigate to Resources > JMS > Activation specifications > IBMCTTagReadAS.
    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'.
  18. Restart WebSphere Application Server.
  19. Verify the WebSphere Sensor Events installation. Choose R2 as your simulated test reader.
  20. If you plan to use WebSphere Business Events and you changed the default installation location for WebSphere Business Events, or you changed the default installation location for WebSphere Application Server, then you must set the following environment variables before running the WebSphere Business Events cmdline connector (cmdline script) or starting the WebSphere Business Events connectors (connectors script):
    • WBE_HOME - set this to the installation directory.

      For example, for Windows® operating systems:

      set WBE_HOME=C:\Program Files\IBM\WBE62

      For Linux® operating systems:

      export WBE_HOME=/opt/IBM/WBE62
    • WBE_WAS_HOME - set this to the WebSphere Application Server Network Deployment installation location. This is only needed if the default WebSphere Application Server installation location was not used.

    See the WebSphere Business Events Information Center for more information.

  21. Enable security for WebSphere Application Server.
  22. 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.
  23. Configure and verify the Location Awareness Services for WebSphere Sensor Events installation.
  24. For reporting, the browser runs only on the server with WebSphere Application Server by default. To modify the target URL for the reports, follow these steps.
    Note: Before running the commands, substitute the following symbolic parameters with your specific environment values.
    • %1 is WAS_HOME, such as C:\Progra~1\IBM\WebSphere\AppServer
      Tip: DOS short names are required for directories containing blanks.
    • %2 is name of the profile, such as AppSrv01
    • %3 is name of the server, such as server1
    1. Stop WebSphere Application Server.
    2. Uninstall the portlet with the following command:
      %1\profiles\%2\bin\wsadmin -conntype NONE
      -c "$AdminApp update isclite modulefile {-operation 
      delete -contenturi AtlasPortletsAdministrationReports.war -server
      %3}"

      If you receive an error at this point, call IBM Support to help resolve the issue.

    3. If no error occurs, save the changes using the following command:
      %1\profiles\%2\bin\wsadmin -conntype
      NONE -c "$AdminConfig save"

      If you receive an error at this point, call IBM Support to help resolve the issue.

    4. If no error occurs, delete the WAS_HOME\systemApps\AtlasPortletsAdministrationReports.war directory.
    5. Go to the directory where you have copied the installed driver and make a backup copy of the \WP\portlets\AtlasPortletsAdministrationReports.war file.
    6. Open the original file with a compressed file utility and edit the WEB-INF\ibm-portal-topology.xml file for the URL value. Search for the <url-link> element and change the value to match your server's host name. Specify a host name instead of using an IP address. For example: http://myHost:9080/AtlasReportingServlet/AtlasReportsServlet?cmd=init
    7. Save the changes and close the WAR file.
    8. Recheck the WAR file to make sure the changes were saved.
    9. Copy the changed WAR file to the WAS_HOME\systemApps directory.
    10. Install the portlet using the following command:
      %1\profiles\%2\bin\wsadmin -conntype NONE
      -c "$AdminApp update isclite modulefile {-operation 
      add -contents %1\systemApps\isclite.ear\AtlasPortletsAdministrationReports.war
      -contenturi 
      AtlasPortletsAdministrationReports.war -contextroot /AtlasPortletsAdministrationReports
      
      -MapWebModToVH {{.* .*  admin_host}} -server %3 -custom paavalidation=true}"

      If you receive an error at this point, call IBM Support to help resolve the issue.

    11. If no error occurs, save the changes using the following command:
      %1\profiles\%2\bin\wsadmin -conntype
      NONE -c "$AdminConfig save"

      If you receive an error at this point, call IBM Support to help resolve the issue.

    12. Start WebSphere Application Server.
  25. The default Location Awareness Services for WebSphere Sensor Events installation can support small scenarios, using between 100 and 200 tags. To use IBM Location Awareness Services for WebSphere Sensor Events 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

Check the WebSphere Sensor Events Support site for any product-related fixes.

If you need to uninstall the WebSphere Sensor Events and Location Awareness Services for WebSphere Sensor Events software, refer to Uninstalling WebSphere Sensor Events.


Library | Support | Terms of use

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