Procedure
- 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:
- Enable
security for WebSphere Application Server.
- 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.
- Configure
and verify the Location Awareness Services for WebSphere Sensor Events installation.
- 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.
- Stop WebSphere Application Server.
- 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.
- 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.
- If no error occurs, delete the WAS_HOME\systemApps\AtlasPortletsAdministrationReports.war directory.
- Go to the directory where you have copied the installed
driver and make a backup copy of the \WP\portlets\AtlasPortletsAdministrationReports.war file.
- 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
- Save the changes and close the WAR file.
- Recheck the WAR file to make sure the changes were saved.
- Copy the changed WAR file to the WAS_HOME\systemApps directory.
- 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.
- 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.
- Start WebSphere Application Server.
- 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.