This topic describes how to import resource data into Location Awareness Services for WebSphere® Sensor Events.
Location Awareness Services for WebSphere Sensor Events provides an application that acts as an intermediary component between an enterprise's legacy systems and Location Awareness Services for WebSphere Sensor Events to allow information about tagged items (people or assets) to be imported into Location Awareness Services for WebSphere Sensor Events and, subsequently, to be updated or deleted. The application reads records from comma-separated values (CSV) files that are provided by the existing enterprise application and forms a Java™ Message Service (JMS) request. The application sends the JMS request to Location Awareness Services for WebSphere Sensor Events through the messaging engine and then logs the responses in a log file.
When you are importing a large amount of tags in a production or test environment, make sure that the server you are using is capable of monitoring the tags. For example, to monitor more than 200 tags, you need a server with a fast I/O subsystem.
If you are importing a large amount of tags, such as 3000, only use the create action for test scenarios or for an initial load. On a smaller server, update or delete items using the Classes/Items Manager portlet.
If you set the action in the properties file to create instead of createUpdate, then you can import using a x100 server with a standard disk drive with the following statistics:
If you use the AtlasIntegrator application with the action set to createUpdate on a faster I/O subsystem, then you can import with the following statistics: