In this scenario, you open an HTTP connection to the Device Manager server from the Data Capture and Delivery controller.
When the OSGi framework starts, the bundle loader is retrieved from
the Device Manager server and
installs the Device Manager client bundles
with their necessary prerequisites and the Data Capture and Delivery bundles
to the Data Capture and Delivery controller
using the HTTP connection. The bundle loader is referenced by the
osgi.bundles property in the configuration file.
About this task
Note: WebSphere® Premises Server 6.1.x
does not package or use Device Manager server with Data Capture and Delivery. This information
is only for existing infrastructure with Device Manager server.
Procedure
- Optional: Copy
the applicable contents from the sample_config.ini file
into your existing config.ini file.
Tip: This task facilitates a large scale deployment. If you
just want to do a quick test on one controller, you can skip this
step and use the instructions in step
6 for loading your configuration.
For
example, copy the initial bundle list and the basic settings. The
initial bundle list looks like:
osgi.bundles=bundlefiles/com.ibm.rfid.bundle.loader_version.jar@start
Also,
the device manufacturer might provide additional settings in the config.ini file.
If this is the case, these settings need to be merged with the contents
of the sample_config.ini file.
The following
settings are important for a
Device Manager server deployment:
com.ibm.rfid.bundle.list.url= http://host_name/http_path/dms18load.txt
com.ibm.rfid.edge.config.url=file:./empty.xml
com.ibm.rfid.edge.config.autostart=false
com.ibm.rfid.edge.config.interval= 30000
com.ibm.rfid.edge.config.bootstrap=true
com.ibm.rfid.edge.config.bootstrap.overrides=false
#
com.ibm.rfid.dms.agentext.config.manufacturer=Unknown
com.ibm.rfid.dms.agentext.config.modelextension=Edge
#the following line should remain commented out unless you want
#to define the DMS device name here
#com.ibm.rfid.dms.agentext.config.deviceidextension="staticExtension"
#For DMS notification need to set the OSGi HTTP server port
#If you change this value you need to adapt the notification port
#on the DMSserver
org.osgi.service.http.port=8777
- Modify the OSGiAgent.properties.template based
on your configuration and save the file as OSGiAgent.properties.bak.
Set the Device Manager server address
and device owner user ID (dmsuser) and password correctly.
Note: DevId
and Mod parameters are currently not supported.
- Make sure that all OSGiAgentTree.bin files
are deleted, including any backup files, such as OSGIAgentTree.bin.bak.
- Make a copy and then rename the OSGiAgent.properties.bak to OSGiAgent.properties.
- Start the OSGi framework.
- From an osgi prompt, install
the bundle loader.
Tip: This task facilitates
testing on one controller. If you followed the instructions for a
large scale deployment in step
1, then you can skip
this step.
For example:
osgi> install http://host_name/bundles/com.ibm.rfid.bundle.loader_6.0.0.v200703221650.jar
- Start the bundle loader bundle and verify that the Device Manager client bundles
are loaded and started correctly.
- Start the com.ibm.rfid.console.log bundle in order to see
debug log messages.
Results
The
Device Manager client should
now connect to the
Device Manager server.