> > WebLogic RFID Enterprise Server Known Issues and Recommendations

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

WebLogic RFID Enterprise Server Known Issues and Recommendations

WebLogic RFID Enterprise Server 2.0 is the first release of the RFID Enterprise Server from BEA Systems. Previously, this product was the ConnecTerra RFTagAware Enterprise Server. You can now reach technical support through the standard BEA means. Select Support on the BEA Web site, at www.bea.com, for more information.

The following sections document known problems and workarounds in WebLogic RFID Enterprise Server 2.0.

 

Known Issues

The following section describes problems that were found in WebLogic RFID Enterprise Server 2.0. Entries include a description of the problem, and a workaround or solution where appropriate.

Tracking Number
Description and Workaround
CR277574
When starting the PointBase RDBMS, invoke the startPointBase and startPointBaseConsole scripts that are located in the WL_HOME\common\bin directory. Do not use the scripts that are located in the BEA_HOME\user_projects\domains\DOMAIN_NAME\bin directory.
CR286935
Uninstalling WebLogic RFID Enterprise Server does not remove the <domain-component-info> elements and their contents from the file BEA_HOME\user_projects\domains\DOMAIN_NAME\init-info\domain-info.xml.
If you remove Enterprise Server component deployments from the domain and then try to re-install them, you will not succeed.
Workaround or Solution:
Manually delete the <domain-component-info> elements and their contents from the domain-info.xml file that pertain to the WebLogic RFID Enterprise Server. Specifically, remove those named Reporting Service, Event Service and Data Exchange Service, Serial Number Assignment Service, and Edge Management.
CR287825
In the Master Data Administration Console, once a Master Data Type has entries associated with it, you cannot modify it in any way, including changing the field display order.
Workaround or Solution:
Export the Master Data Type, delete all its entries in the Console, change the sequence attribute in the Master Data Type Attribute Meta XML, and then re-import it.
CR289184
A FatalDataStoreException is thrown if you start WebLogic Enterprise Server before starting the database.
CR289605
In the Query Subscription Administration Console, when adding subscription parameters, the table displays 10 parameters per page; this is not configurable.
CR289618
CR291543
In the Query Subscription Administration Console, when selecting items from drop-down lists, if you select multiple items (this sometimes happens when using the mouse wheel), an exception is thrown.
Workaround or Solution:
Select only one item at a time. If possible, avoid using the mouse wheel when selecting items from drop-down lists.
CR290724
When capturing SGLN and GRAI tags with a company_prefix containing 12 digits, the EPC.REFERENCE field gets the value 0 instead of null.
CR284279
In this release of Enterprise Server, there is no QuickStart application, therefore, ignore the quickstart scripts located in the RFID_ENTERPRISE_HOME\common\bin directory.
CR281682
The FILTER_VALUE column is no longer in the Event repository. The filter value is only relevant when searching for tag EPCs; this release of Enterprise Server only allows searching on pure identity EPCs.
CR291842
When installing on UNIX, using a leading backslash (\) in the install directory path causes the Configuration Wizard to fail silently.
CR292047
In the Query Subscription Administration Console, to use authentication on a JMS destination, enter the relevant properties in the Naming Service Properties text field.
For example,
java.naming.security.authentication=auth
java.naming.security.principal=name
java.naming.security.credentials=cred
Caution: The values will be stored unencrypted in the database. Therefore, you must either ensure the security of your database or consider the JMS queue password unimportant, if revealed.
CR293031
If your PointBase database connection is lost, you must restart the Enterprise Server after restoring your database connection.
CR293561
When using an Internet Explorer browser to access the Reporting Service or Serial Number Assignment Service Consoles, highlighting an item in a drop-down list and then scrolling rapidly using the mouse wheel may cause an unexpected error.
Workaround or Solution:
Start a new browser session.
CR292759
The Configuration Wizard displays a list of all the JDKs found in BEA Home. When selecting a JDK for use with WebLogic RFID Enterprise Server 2.0, you must select a JDK version 1.5 or higher.
CR293614
When issuing a poll() request which includes Order By and Order Direction parameters, events will be ordered within each event group but not for the entire event list. The event list includes events grouped by Event Type.
CR279910
If you are using an Oracle database, before running the initEventServiceDatabase script, you must first uncomment this line in the BEA_HOME\user_projects\domains\DOMAIN_NAME\config\kodo.properties file:
#kodo.jdbc.DBDictionary: oracle (TimestampTypeName=TIMESTAMP)
CR294268
In the Reporting Service Console, Location Selection Criteria > Search Locations table, pressing Enter, Add, or Delete after putting values in the Value text fields results in losing the values.
Workaround or Solution:
Create the full number of search criteria rows before putting values in the text fields.
CR244182
In the Edge Server Administration Console, the wrong ECSpec Subscriber subscription properties page might be displayed after selecting an ECSpec Subscriber to edit.
Workaround or Solution:
Click Cancel on the ECSpec Subscriber subscription properties page. Then re-select the ECSpec Subscriber edit link.
CR288549
When you first access the Master Data Administration Console from the Enterprise Server Home page, you will see the following error messages:
<Oct 3, 2006 2:45:05 PM EDT> <Error> <netuix> <BEA-423266> <No setter for property :: encoding.>
<Oct 3, 2006 2:45:10 PM EDT> <Error> <netuix> <BEA-423137> <There was an error loading the requested URI /PortalConfig/home/HomePage.jsp.>
Subsequent accessing the Master Data Administration Console Home page displays the following error message:
<Oct 3, 2006 2:45:10 PM EDT> <Error> <netuix> <BEA-423137> <There was an error loading the requested URI /PortalConfig/home/HomePage.jsp.>
Workaround or Solution:
Disregard these messages; they have no effect on the application.
CR295191
In the Edge Server Administration Console, PLC Stack Light RFID devices always display an UP Device Status regardless of their actual state.
CR295240
If you are using Microsoft SQL Server 2005 and a Microsoft JDBC driver, the Configuration Wizard does not properly construct the connection URL (it lacks the database name component).
Workaround or Solution:
To use the Microsoft SQL Server 2005 JDBC driver, follow these steps:
  1. Download and install the driver from the MSDN Web site (follow the Microsoft instructions).
  2. Edit this file, C:\BEA_HOME\user_projects\applications\DOMAIN_NAME\kodo.ear\kodo.rar\META-INF\ra.xml, by adding ;databasename=<db_name> to the Connection URL (replace <db_name> with the actual database name).
  3. Edit this file, C:\BEA_HOME\user_projects\domains\DOMAIN_NAME\config\kodo.properties, by adding ;databasename=<db_name> to the Connection URL (replace <db_name> with the actual database name).
  4. Add sqljdbc.jar to the classpath in the following database initialization scripts: C:\BEA_HOME\user_projects\domains\DOMAIN_NAME\bin\initEventServiceDatabase C:\BEA_HOME\user_projects\domains\DOMAIN_NAME\bin\initSerialNumberDatabase
  5. Add sqljdbc.jar to the C:\BEA_HOME\user_projects\domains\DOMAIN_NAME\lib directory.
  6. In the WebLogic Server Administration Console, delete the existing credential map: navigate to Security Realms > myrealm > Credential Mappings, select the check box next to the existing credential mapping Resource Identifier, and click Delete.
  7. In the WebLogic Server Administration Console, create a new credential map (click New), with these fields (leave the other fields blank):

    8. Remote Host = Connection URL (the same value as in the ra.xml and kodo.properties files)

    Local User = rfiduser

    Remote User and Remote Password = database login username and password

  8. Restart WebLogic Server.

Note: These steps also apply to all other supported JDBC drivers that are not shipped with the product.
CR295481
Upon startup, the Enterprise Server displays multiple repeats of the following message in the console window:
<Oct 5, 2006 4:35:28 PM EDT> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name weblogic.wsee.mdb.DispatchPolicy. Dispatch policy weblogic.wsee.mdb.DispatchPolicy will map to the default WorkManager for the application bea_wls9_async_response>
Workaround or Solution:
Disregard these messages.
CR291322
When using Pointbase RDBMS as the enterprise data store, capture operations might yield the exception:
kodo.util.DataStoreException: Data exception -- row already exist in index I_EPC_M_URI on table EPC
Workaround or Solution:
This exception is harmless; you can ignore it.
CR296046
When configuring a SQL Server database for use with the Enterprise Server, select a case-insensitive collation option (for example, _CI), otherwise, the database initialization scripts will fail. For more information on collation options, see SQL Server Books Online.


  Back to Top       Previous  Next