WebSphere brand IBM WebSphere Sensor Events, Version 6.2

Post-installation steps

Before you begin
If you see errors with the installation, refer to General troubleshooting tips for possible resolutions to the problem.
Procedure
  1. 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
  2. Enable security for WebSphere Application Server.
  3. 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.
  4. Configure and verify the Location Awareness Services for WebSphere Sensor Events installation.
  5. 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.
  6. 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.