BlipNet Administrators Guide
Table Of Contents Getting Started .......................................................................................................... 1 Introduction to BlipManager ........................................................................................ 4 General information about views .................................................................................. 6 BlipManager Views ..................................................................................................
Table Of Contents Diagnostics.............................................................................................................. BlipNode does not connect to the BlipServer ................................................................ Problem when connecting to LAN access service in BlipNet ............................................ Problem when connecting to the OPP server in BlipNet ..................................................
Installing BlipNet Getting Started Follow these steps to get started: 1. Install BlipNet. Please refer to the InstallationGuide.html for a description of the installation process. 2. Start the BlipManager. a. Windows: Go to “Start->Programs->BlipNet->BlipManager”. b. Linux: Go to ”Main Menu->Programs->BlipNet->BlipManager” or from a xterminal execute following file: /opt/blipnet/ blipmanager.bin (default location). 3. Login to the BlipManager. a.
BlipNet Administrators Guide 5. Change Administrator password. When the BlipManager is started, it is recommended to change the administrator password. This is done by: a. In the menu bar select “File->Properties”. b. In the BlipServer Properties window select the tab called “User Accounts”. c. Select “Administrator” from the list and click on the “Edit” button and change the password. Make sure to remember this password. d. Click the “OK” button. 6. Specify a default Bluetooth Passkey.
Installing BlipNet 7. Connect the BlipNodes to the LAN and connect power. The BlipNodes will appear in the configuration view tree to the left in the BlipManager main window. Initially the BlipNodes will pop up in the “Unconfigured” configuration group folder. 8. Apply a configuration to a BlipNode. Assuming that the BlipNode shall be used for Bluetooth terminals to access the Internet, follow the steps: a. Right click on a BlipNode and select “Properties”. b. The window “BlipNode Properties” will appear.
BlipNet Administrators Guide Introduction to BlipManager The BlipNet system can be administered from the BlipNet management tool called BlipManager.
Installing BlipNet The figure above illustrates the BlipManager main window, which is split in two sub-windows. A sub-window showing a configuration view which includes a tree of BlipNet components and a sub-window showing detailed information of the items in the tree. The Tree is updated automatically. This means that for example when a new terminal is connected it will be shown in the Configuration View tree automatically and removed automatically when it is disconnected.
BlipManager Views General information about views BlipManager Views The BlipManager has 3 different views that all shows the status of the BlipServer components in different ways. In all views you can right click a component for a pop-up menu with different actions for the selected. BlipServer The BlipServer Icon represents the BlipServer that your BlipManager is currently connected to.
BlipManager Views 3. Properties Allow you to change the BlipServer properties. For more information read BlipServer Properties Configuration Only shown in configuration view. Represents a configuration group that can contain a number of BlipNodes that are assigned to that configuration. Right Click Actions 1. Add New BlipNode Add a new BlipNode to the BlipServer and assign it with the selected configuration. 2. Properties Brings up the Configuration Properties.
BlipNet Administrators Guide 7. Properties Brings up the Properties for the BlipNode. For more information read BlipNodeProperties Terminal Represents a Bluetooth Terminal. The icon will represent the Class of Device type of the Bluetooth Terminal. Right Click Actions 1. Disconnect Disconnects the Bluetooth Terminal from the BlipNode 2. Delete Only possible on not connected Terminals in Terminal view.
BlipManager Views Configuration View Shows The BlipServer Configuration Groups with the BlipNodes belonging to each group. You can move BlipNodes between different configuration groups using Drag'n'Drop. In the Menu you can choose to show empty configuration groups which will make the view display configurations groups even if no BlipNodes are attached to it. Bluetooth Terminals will be show as children to BlipNodes when a Bluetooth connection exits between them.
BlipNet Administrators Guide BlipNode View Shows the BlipNode structure. This is especially useful if you have wireless BlipNodes as the Tree will illustrate the Wireless Topology. All BlipNodes shown as direct children to the BlipServer are BlipNodes connected to the Server through Ethernet. A BlipNode show as a child to another BlipNode is a wireless BlipNode meaning that the wireless BlipNode is connected to the BlipServer with a Bluetooth PAN connection through the parent BlipNode(s).
BlipManager Views Terminal View The Terminal view displays all the Bluetooth Terminals that the BlipServer has registered in its database. Terminals that are not currently connected to the BlipServer are presented with ghosted gray icon. In the detailed pane you can choose to sort the terminals after Last Connected which gives you an easy way to monitor the connectivity of you terminal clients.
BlipNode Properties General In the General window in BlipNode Properties it is possible to configure the primary settings of a BlipNode. Additionally, information about the status, Bluetooth address, IP address of a BlipNode is displayed. Name The first text field contains the friendly name of the BlipNode. This is the name shown on the GUI on a connecting device. Status The status of the BlipNode. Status possibilities are; Not Connected, Connected, In use by application, Software upgrade in progress.
BlipNode Properties Bluetooth Address The Bluetooth address of the BlipNode. IP address The IP address of the BlipNode. Automatically retrieved using DHCP. Configuration In this list box the configuration of the BlipNode can be selected, see section General about BlipNode Configuration for further information. Groups This list shows the groups the BlipNode is a part of. The BlipNode can be inserted/removed from groups by clicking in the corresponding checkboxes.
BlipNet Administrators Guide Allowed Terminals In the Allowed Terminals window in BlipNode Properties it is possible to make a list containing terminals that are disallowed on the specific BlipNode. If the checkbox “Enable local terminal blacklisting on this BlipNode” is unchecked all terminals will be allowed to connect. This is the default and recommended setting. By checking this checkbox, terminals can be added to a disallowed list by clicking the “Add” button.
BlipNode Properties Power Control In the Power Control window in BlipNode Properties it is possible to specify the power levels of the BlipNode. BlipNode requirements Hardware Power control is possible when using BlipNode L1 hardware, which is a power class 1 Bluetooth device (+20 dBm ). Power control is not possible when using BlipNode S1 hardware or older, which are power class 2 Bluetooth devices (+4 dBm). Software BlipNode software version must be BlipNode_R3A or newer.
BlipNet Administrators Guide Inquiry, Paging and Default Power This is the power level of the BlipNode used when transmitting. This means when making inquiry and paging. If a connected remote device has not increased or decreased the data transmit power, this power level also indicates the data transmit power. Max Data Power A connected remote device using power control can maximum increase the BlipNodes data transmit power to this power level.
BlipNode Properties Wireless Control The wireless control pane allows you to monitor and configure the wireless properties of a BlipNode. A wireless BlipNode is a BlipNode that is connected to the BlipServer through a Bluetooth Connection via other BlipNodes instead of using the Ethernet. In this Windows it is possible to add a list of wireless BlipNodes that this BlipNodes that this BlipNode should connect to. TIP.
BlipNet Administrators Guide Advanced The Advanced window for a BlipNode contains a series of features that have been categorized as advanced features; normally a user will not need to change anything in this window. BlipNode Log Configuration The BlipNode has a built in log system. This feature has been made because it can improve the quality of our support in situations where a BlipNode fails to operate as expected.
BlipNode Properties When enabled, trace will be stored in a buffer internally in the BlipNode. BlipNode Server Configurations The BlipNode has two servers running internally (FTP Server, Telnet Server). These servers are accessible via LAN only. A FTP server is used for the software upgrade. Default the FTP server is disabled and no software upgrade can be made. When the “Auto update of BlipNodes is enabled” the BlipServer will temporarily overrule this setting. A telnet server can be used for maintenance.
BlipNet Administrators Guide Version Info In the Version Info window in BlipNode Properties it is possible to see the hardware version of the BlipNode and the versions of the different software on the BlipNode. HW Version The hardware version of the BlipNode. SW Version The version of the application SW on the BlipNode. FTP Server Version The version of the FTP server SW on the BlipNode. Boot SW Version The version of the boot SW on the BlipNode.
BlipNode Properties 21
BlipServer Properties Server Info The BlipServer Properties - General window displays status and version information of the BlipServer. BlipServer Name In the text field at the top of the General window it is possible to enter the name of the BlipServer. Host Name The host name of the machine hosting the BlipServer. When running the BlipManager locally on the same machine as the BlipServer the host name is localhost (127.0.0.
BlipServer Properties The actual number of connected BlipNodes on this BlipServer. License Information Displays information about your BlipNet License. If no valid license file is loaded on the BlipServer, the pane will display an error message shown above.. You can upload the license file you have received from BLIP Systems by clicking the Select Button and browse to your received license file.
BlipNet Administrators Guide BlipNode Configurations Via the BlipNode Configurations window it is possible to define Configuration Groups and to assign BlipNodes to specific Configuration Groups. A Configuration Group is a set of BlipNodes sharing the same basic configuration. The BlipNodes do not share the exact same configuration. E.g. the friendly name can vary, and BlipNodes in the same Configuration Group does not necessarily have to belong to the same BlipNode Group.
BlipServer Properties Add BlipNodes to a specific Configuration Group. Remove BlipNodes from a specific Configuration Group. A configuration wizard will help to guide you through the different configurations when trying to add a new, edit or duplicate a Configuration Group. A BlipNode with no Configuration Group will automatically be assigned the "Unconfigured" group.
BlipNet Administrators Guide BlipNode Groups A BlipNode Group is a logical name for a collection of BlipNodes. The BlipNodes in a BlipNode Group may have different configurations. A BlipNode Group name can for example be a location (e.g. “Reception”) or an application Name (e.g. “Laptop Detector”). An application developer can use the BlipNode Group name to retrieve the BlipNodes assigned to this particular group from an application.
BlipServer Properties Advanced The BlipServer Advanced Settings contains a series of features, which usually not will have to be edited. The different settings in the BlipServer Advanced window are described below. Configure BlipServer Logging The BlipServer has a built in log system. This feature has been made because it can improve the quality of our support in situations where BlipNet application developers have problems using the BlipServer API.
BlipNet Administrators Guide Log to Socket: This feature enables Ericsson Bluetooth Networks to view logging information online. This checkbox should only be used in co-operation with Ericsson Bluetooth Networks. Configure Obex File Storage Root Path In these text fields the Obex storage root folders for the Object Push Profile (OPP) Server and File Transfer Profile (FTP) Server can be set.
BlipServer Properties If you should have a version of the software older than BlipNode R1A (BlipNet 0.5), please contact BLIP Systems for specific upgrade information. BlipServer IP Address The IP address of the BlipServer which the BlipNodes will try to connect to. When a BlipNode boots, it sends out a broadcast signal. The BlipServer will catch this signal a create a connection to the BlipNode for configuration a monitoring.
BlipNet Administrators Guide User Accounts In the BlipServer Properties - User Accounts window everything about user accounts on the BlipServer can be configured. The BlipManager operates with the term “User account” at two levels. There is a user account for: The administrator Applications To make it possible for an application to connect to the BlipServer a user account for the application must exist.
BlipServer Properties Allowed BlipNodes From this window the allowed BlipNodes to connect to the BlipServer can be controlled. The BlipNodes connects to the BlipServer via UDP broadcast and by default all BlipNodes will be allowed connection to the BlipServer. It can be desirable to have several BlipServers on the LAN. By specifying the allowed BlipNodes on the BlipServer, it can be controlled which BlipNodes that are allowed to connect to a certain BlipServer.
BlipNet Administrators Guide Security Use the Security Settings to control the access to the BlipNet System. The Bluetooth passkey is the PIN code a user will have to use to make a secure relation between the users Bluetooth device and BlipNet. The creation of this secure relation is called “Pairing” or “Bonding”. A Bluetooth device shall be either in non-bondable mode or in bondable mode. In bondable mode the Bluetooth device accepts paring – i.e.
BlipServer Properties In the security window of BlipServer Properties it is also possible to expire Bluetooth bondings. When applying “Expire Bluetooth bonding on all devices” all “bonds” created by the default Bluetooth Passkey will be deleted. To delete the bonding to a terminal with a specific Bluetooth Passkey, the Bluetooth Passkey for the specific terminal must be deleted.
BlipNet Administrators Guide Terminals Use the Terminals window to control the terminals on the BlipServer. This window displays all the Bluetooth terminals known by the BlipServer. When a Bluetooth connection is established between a BlipNode and a Terminal it will automatically be added to this list. The List shows the following information for each Terminal: 34 Name Address Last Connected Allowed The last known Bluetooth Friendly name of the terminal. The Bluetooth Address Shows either 1.
BlipServer Properties 3. Never: A Bluetooth connection can never be established between this terminal and a BlipNode. Note1: This policy is applied both when the terminal is establishing the connection and when connection is being established from the BlipNet API. Note2: This Policy is independent of the Bluetooth Passkey settings. If a Pairing is needed and a wrong PIN Code is specified, the transaction will fail. Pin Code Mobility Specifies the Bluetooth Passkey.
BlipNet Administrators Guide The dialog gives two methods for adding terminals to BlipNet.: 1. Search for Bluetooth terminals by selecting a BlipNode and Press Search. The Results will be shown in the list. 2. Manually enter Terminal Bluetooth Addresses in Address Field. The Entered addresses will be shown in the list. To add Terminals, multi-select the terminals from the window that you want to add then press the OK button.
BlipServer Properties Remove Pressing the Remove Button will delete the Selected Terminals from the System including all information like description and PIN Code. Edit The Edit Button will bring up a Dialog showing the Terminal Properties.
BlipNet Administrators Guide Mobility Settings Here it is possible to enable or disable the BlipNet Mobility Service.
BlipServer Properties Mobility Zones This page allows you to configure the BlipNet Mobility Zones. Please read BlipNet Mobility Service for general introduction to this Service. The Window lists the created Mobility Zones.
BlipNet Administrators Guide The Zone Name and Zone Comment defines the name of the Zone. A good idea is to specify a physical location. This makes it easy to determine the locations of connected terminals in the BlipManager tree view. To each zone it is possible to assign a number of BlipNodes. Normally you would only have one BlipNode in each Zone, but if you have high penetration of Bluetooth devices or the need for more bandwidth to each device in a Zone you can add extra BlipNodes.
BlipServer Properties If the Search interval is very high it will take longer time for a newly powered on device to be connected and also the handover process will take more time because the BlipServer will not do the hand over to a BlipNode in a new Zone before the Terminal has been discovered in that Zone.
Terminal Properties General The Page shows information about the selected Bluetooth Terminal. BlipNet Mobility Specify here if this terminal is subscribed to the BlipNet Mobility Service. To use this service, the terminal must support the Bluetooth PAN Profile. For more information please read BlipServer Properties -> Mobility Service.
Terminal Properties 1. Always: The Terminal is always allowed to connect to the BlipServer. 2. Default: Depends on the System default setting in BlipServer Properties -> Bluetooth Security. Only if "All Bluetooth Terminals have Access" is enabled, the terminal will be allowed to connect. 3. Never: A Bluetooth connection can never be established between this terminal and a BlipNode.
BlipNode Configurations General about BlipNode Configurations Using the BlipManager it is possible to assign BlipNodes to a BlipNode Configuration. It is possible to specify such a BlipNode Configuration using a configuration wizard. For more information about the configuration wizard see section Making a new BlipNode Configuration. The BlipManager has a set of pre-defined standard configurations.
BlipNode Configurations Server Node This pre-defined BlipNode configuration includes all BlipNet Bluetooth Services, i.e. LAN Access, PAN NAP, FTP and OPP server. This means that all these services are available simultaneously on BlipNodes with this configuration. Seven devices can be connected to the BlipNode simultaneously. BlipNodes with this configuration can be used for both outgoing and incoming connections. BlipNodes with this configuration can be used for the BlipNet mobility solution.
BlipNet Administrators Guide OPP Server The Object Push Profile (OPP) server configuration facilitates the exchange of business cards and reception of objects such as images, messages, etc. The BlipServer stores all retrieved objects in the OPP storage root folder and applications can subscribe to notification events from the BlipNet API when new objects are received. A BlipNode can be used as an OPP server and it is able to receive objects without writing any specific application.
BlipNode Configurations folder /opt/blipnet/Obex/OPP. However, this folder can be changed, see the BlipServer Properties - Advanced section. If the OPP server should answer with your business card (instead of the BlipNet Business card) when requested from OPP clients, follow the steps described below: 1. Create a business card, e.g. by using Microsoft Outlook. The official site of vCard is www.imc.org/pdi/, where the format is described. 2.
BlipNet Administrators Guide Unconfigured When a new BlipNode is connected to the LAN and the BlipNode has not previously been configured, the BlipNode will automatically be assigned the empty configuration called “Unconfigured”. A BlipNode having the “Unconfigured” configuration is not active.
BlipNode Configurations Making a new BlipNode Configuration A new configuration can be created in two ways, either by creating a new configuration from the default template or by duplicating an existing configuration. “New” button In this case a new clean configuration is made. “Duplicate” button By clicking on one of the standard configurations and then clicking on the “Duplicate” button a new configuration is created based on the same settings as the standard configuration.
Configuration Wizard Configuration Name In the first step of the configuration wizard the name of the configuration shall be inserted. The configuration name must be unique. Two configurations cannot have the same configuration name.
Configuration Wizard BlipNode Accessibility The second step in the configuration wizard is the BlipNode Accessibility step. Via this window settings regarding accessing the BlipNode can be configured. Discoverable If checked, the BlipNode will be discoverable (other Bluetooth devices can discover the BlipNode). Inquiry Access Code Configures the Access Code that the Bluetooth Radio will listen for during inquiry scan. This must always be set to General Inquiry Access Code (GIAC).
BlipNet Administrators Guide devices to perform master/slave switch. If this setting is not used and if the BlipNode acts as access point, only one connection at the time will be supported. This is a special feature, which should normally be avoided, because if a terminal without support for master/slave switch connects to the BlipNode, the BlipNode is blocked for further connections until this device is disconnected.
Configuration Wizard Bonding. accept allowed.
BlipNet Administrators Guide BlipNode Services The 3th step in the “Configuration wizard” is the “BlipNode Services” step. This window is used to configure which services the BlipNode shall advertise towards connecting terminals.
Configuration Wizard To configure the settings for a service click on the corresponding "Configure" button. Information Server This checkbox is only changeable if the LAN access profile is checked. It must be checked if some kind of WEB or WAP server is available on the LAN connected to the BlipNode.
BlipNet Administrators Guide BlipNode Services LAN Access Profile Settings Service Name This is a free text string, which will be shown as the name of the service on the GUI on a connecting device. The Service Name parameter is a short user-friendly name for the service; for example “Corporate Network”, “Conference#1”, etc. Service Description This is a free text string, which might be shown on the GUI on a connection device. The Service Description attribute is a longer description of the service.
Configuration Wizard WAP Over Bluetooth Settings The WAP over Bluetooth service can be used when the BlipNet is used with special “WAP Over Bluetooth” enabled terminals. Bluetooth Networks has developed WAP over Bluetooth software for several Sony-Ericsson terminals. With this software it is possible to run a WAP session over Bluetooth. By writing an application it is even possible to make WAP push functionality over Bluetooth.
BlipNet Administrators Guide The home page of the WAP service available via the BlipNode. Require Authentication Cannot be changed, the authentication settings for LAN Access is used for WAP Over Bluetooth.
Configuration Wizard Personal Area Network Profile Settings Service Name This is a free text string, which will be shown as the name of the service on the GUI on a connecting device. The Service Name parameter is a short user-friendly name for the service; for example “Corporate Network”, “Conference#1”, etc. Service Description This is a free text string, which might be shown on the GUI on a connection device. The Service Description attribute is a longer description of the service.
BlipNet Administrators Guide Personal Area Network Protocol Settings In the PAN profile two types of filtering can be made. They are Network Protocol Type filtering and Multicast Address filtering. Network Protocol Type filtering is filtering of Ethernet frames dependent on the Network Protocol Type. Multicast Address filtering is filtering of multicast Ethernet frames dependent on their destination multicast address.
Configuration Wizard In most network scenarios it is not necessary to configure a BlipNode with PAN filters. If filtering is wanted by a connected PAN device, it can configure the BlipNode remotely with specific PAN filters.
BlipNet Administrators Guide Object Push Server Settings Service Name This is a free text string, which may be shown as the name of the service on the GUI on a connecting device. Supporting object formats It can either be chosen to accept any type of objects or to only accept specified object formats. When only specific object formats must be accepted, following object formats can be chosen: Business Cards Calendar Items Notes Messages This includes both vCard 2.1and vCard 3.0 formats.
Configuration Wizard This checkbox must be checked if authentication of connecting devices must be performed. If this checkbox is checked also encryption of traffic will be made. If the security level (specified in the BlipNode Accessibility window) is “Link Level” or “No Security”, the checkbox is grayed out and can then not be enabled or disabled.
BlipNet Administrators Guide File Transfer Server Settings Service Name This is a free text string, which may be shown as the name of the service on the GUI on a connecting device. Require Authentication This checkbox must be checked if authentication of connecting devices must be performed. If this checkbox is checked also encryption of traffic will be made.
BlipNet Mobility BlipNet Mobility Service The BlipNet mobility service enables seamless wireless network connectivity for Bluetooth enabled devices. The mobility service automatically connects to subscribed devices when they enter BlipNet coverage, and automatically hands over terminals from zone to zone as they move around. The BlipNet mobility service is based on the Bluetooth PAN profile which is basically a wireless Ethernet bridge.
BlipNet Administrators Guide Discoverable and Connectable Modes: If you are using only devices supported by the Mobility Service, the BlipNodes can be set non-discoverable and non-connectable for added security. This will ensure that other devices cannot detect and connect to the BlipNodes. Master/Slave switching: If the BlipNodes are discoverable and connectable, master/slave switching should be set to Required. Otherwise, an incoming connection could block the BlipNode for use by other devices.
Wireless BlipNodes About Wireless BlipNodes BlipNet allows BlipNodes to be connected to the BlipServer through other BlipNodes instead of Ethernet. Below is shown a setup with wireless BlipNodes. The BlipServer will instruct 'BlipNode - 2' to establish a Bluetooth PAN connection to 'BlipNode - Stairs'.
BlipNet Administrators Guide There are some important things to notice about Wireless BlipNodes 1. Wireless BlipNodes must not be connected to the ethernet. 2. A Wireless BlipNode offers the same functionality as a Ethernet BlipNode but have a maximum of 6 active connections as one is used for the Backbone connection. 3. The Bluetooth bandwidth for wireless BlipNodes are limited compared to BlipNodes connected through Ethernet. Use wireless BlipNodes with care.
Howto Using the BlipNode Groups Concept The BlipNode Group is a logical term which has been introduced to be able to distinguish groups of BlipNodes from each other in an application without knowing the Bluetooth address of the BlipNode. Using this concept, an application becomes independent of e.g. hardware replacements. From the BlipManager it is possible to create a BlipNode Group and to assign BlipNodes to this group.
BlipNet Administrators Guide Configuration of BlipNet for BlipNet API applications When writing an application on top of the BlipNet API, certain configurations must be made in the BlipManager. The following is a short checklist: 1. Create a “User account” for the application. Creating a “user account” includes defining a login and a password, which can be used by the application when connecting to the BlipNet API.
Diagnostics Diagnostics When connecting terminals, problems might occur due to: Wrongly configured DHCP servers Wrongly configured terminals Wrongly configured BlipServer The most common problems are: BlipNode does Problem when Problem when Problem when Problem when not connect to the BlipServer connecting to LAN access service in BlipNet connecting to the OPP server in BlipNet pushing objects to the OPP server in BlipNet pushing from BlipNet to an OPP server device 71
BlipNet Administrators Guide BlipNode does not connect to the BlipServer If a BlipNode is attached to the LAN where the BlipServer is running and the BlipNode is not found by the BlipNet within approx. 30-60 seconds, something is wrong. Every time the BlipNode is switched on, it will search for a BlipServer. This search will be repeated every 30 seconds. By looking at the BlipManager Main window, it can be verified whether the BlipNode is connected to the BlipServer or not.
Diagnostics b. There is more than one BlipServer on the net and another BlipServer has “stolen” the BlipNode. Solution: Use the white list in all BlipServers on the LAN to specify which BlipServer the BlipNode belongs to. c. The BlipNode has outdated software which is not compliant with the current BlipServer. The software package distributed with BlipNet 1.0 is able to upgrade BlipNet 0.5 BlipNodes. If the BlipNode is older than this, it must be upgraded to 0.5 first.
BlipNet Administrators Guide Problem when connecting to LAN access service in BlipNet Before going through this procedure please make sure that the correct configuration is used. Either the “LAN Access”, the “LAN Access and Object Push Server” configuration or another suitable custom configuration must be used. If the problem remains then the procedure to find the problem depends on what the problem appears to be from the terminal side. From the terminal side the following might happen: 1. 2. 3. 4.
Diagnostics Problem when connecting to the OPP server in BlipNet Before going through this procedure please make sure that the correct configuration is used. Either the “Object Push Server”, the “LAN Access and Object Push Server” configuration or another suitable custom configuration must be used. If the problem remains then the procedure to find the problem depends on what the problem appears to be from the terminal side. The following problems and solutions are known: 1.
BlipNet Administrators Guide Problem when pushing objects to the OPP server in BlipNet If pushing objects to the OPP server in BlipNet fails, there are some possible problems and solutions. The following problems and solutions are known: 1. A lack of disk capacity on the BlipServer. Check the disk capacity on the machine on which the BlipServer is running. There must be enough disk capacity for incoming objects. 2. The object format of the object being pushed is not supported.
Diagnostics Problem when pushing from BlipNet to an OPP server device If pushing from a BlipNet to a terminal having the OPP service fails, several possible reasons exist. Problems might occur at different levels in the push phase. Before going through this procedure please make sure that the correct configuration is used. Either the “Object Push Client”, the “T68i WAP Terminals” or another suitable custom configuration must be used.
Terminology Terminology BlipNode Group A BlipNode Group is a logical name for a collection of BlipNodes. The BlipNodes in a BlipNode Group may have different configurations. A BlipNode Group name may, for example, be a location (e.g. “Reception”) or an application name (e.g. “Laptop Detector”). An application developer can use the BlipNode Group name to retrieve the BlipNodes assigned to this particular group from an application.
Terminology communicate with one master at a time. A slave can normally only be connected to one Bluetooth device (a master) at a time. User Account A set of credentials consisting of a login and a password. Two types of accounts exist, an administrator account and an application account. An application using the BlipNet API must register in the API with a user account.
Index A Allowed BlipNodes ................................35 B BlipNode Properties ..............................22 Bluetooth bondings ...............................36 Bluetooth Passkey ................................36 Bonding ..............................................36 Bonds .................................................36 C Configuration Groups ............................26 E Expire Bluetooth ...................................36 F Firm Ware ...........................................
