|
|
Description and Workaround
|
|
|
When using Enterprise Server with a non-Sun JVM, a ClassNotFoundException may be thrown referencing one or more of the following classes:
com.sun.org.apache.xerces.internal.dom.DocumentImpl;
com.sun.org.apache.xerces.internal.dom.ElementNSImpl;
com.sun.org.apache.xerces.internal.dom.TextImpl;
com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl;
A patch is available from your BEA representative to address this issue.
|
|
|
Accessing the EPCISServlet (used for capture of EPCIS events via HTTP) fails unexpectedly in some circumstances, including access over a WAN.
A patch is available from your BEA representative to address this issue.
|
| |
The Dwell report does not work with releases of PointBase prior to 5.4. To optimize query performance the Dwell Report uses a SQL function (COALESCE) that is not supported in PointBase releases prior to 5.4.
Upgrade to PointBase 5.4 or use a database that is supported in a production environment.
|
| |
A new column has been added to the EPCIS_EVENT table. If you are upgrading from Enterprise Server 2.0.0 to 2.0.1, and using the same database, this column can be added using one of the following SQL statements:
- Oracle:
ALTER TABLE epcis_event ADD(timezone_offset varchar2(10));
- PointBase
ALTER TABLE epcis_event ADD timezone_offset VARCHAR2(10);
When you install Enterpriser Server 2.0.1 from scratch, the column is created from the database initialization scripts.
|
|
|
When using the manual initialization scripts to initialize an Oracle database, some columns are incorrectly initialized as datatype DATE instead of TIMESTAMP.
To correct this problem, use the following SQL commands to set the columns to the correct data type:
alter table epcis_event modify(event_time TIMESTAMP, record_time TIMESTAMP); alter table subscription modify(current_run_started TIMESTAMP, initial_record_time TIMESTAMP, last_successful_run TIMESTAMP);
This problem does not occur when you use the Configuration Wizard to create the database.
|
|
|
The eventTimeZoneOffset field has been added to events in order to comply with Proposed Specification for EPCIS 1.0 (November 27, 2006). Although the specification states that it is required, it is being treated as optional in Service Pack 1 in order to provide backwards compatibility with the Enterprise Server 2.0 release.
On capture, if this field is included it is stored in the database. If the field is not included an attempt is made to derive it from the eventTime field. If it cannot be derived from the eventTime field, the local server's offset is used.
This field is always included in query and subscription results, though it may be empty if there is no value in the database (for events captured in a previous release of RFID Enterprise Server).
|
|
|
EPC-matching parameter names and meanings have changed in Service Pack 1 to match the Proposed Specification for EPCIS 1.0 (November 27, 2006). These changes include:
- MATCH_epc and MATCH_childEPC have been combined as MATCH_epc. Queries including this parameter return any ObjectEvent, AggregationEvent, or TransactionEvent where an EPC in the epcList or childEPCs field matches one of the EPC pattern(s) or URI(s) specified.
- MATCH_anyEPC has been added. Queries including this parameter return any ObjectEvent, AggregationEvent, or TransactionEvent where the parentID or any EPC in the epcList or childEPCs field matches one of the EPC pattern(s) or URI(s) specified.
The following parameters from the 2.0 release of Enterprise Server are preserved for backwards compatibility:
- MATCH_childEPC is retained and returns AggregationEvents whose child EPC list contains an EPC field matching one of the pattern(s) or URI(s) specified.
- MATCH_epc is renamed MATCH_objectEventEPC and returns ObjectEvents where one of the EPC fields matches one of the EPC pattern(s) or URI(s) specified.
|
|
|
Some steps can be taken to optimize the performance of Microsoft SQL Server with Enterprise Server.
- When using SQL Server 2005 it is recommended that Service Pack 2 be applied, as it addresses some known performance issues with SQL Server.
- Run the following script. The script creates one non-clustered index and statistics, which improves the performance of the database:
CREATE NONCLUSTERED INDEX [_dta_index_uri_epc]
ON [epc]
(
[uri] ASC,
[epc_id] ASC
)
INCLUDE ( [company_prefix],
[epc_class],
[pure_identity_uri],
[reference],
[scheme],
[serial_number]) WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF,
IGNORE_DUP_KEY = OFF, ONLINE = OFF) ON [PRIMARY]
CREATE STATISTICS [_dta_stat_uri_epc] ON [epc]([epc_id], [uri])
|
|
|
Enterprise Server EPCIS xsds and wsdl have been updated to conform to the Proposed Specification for EPCIS 1.0 (November 27, 2006).
Users who have created a Web services client using these files will need to recompile/recreate their client to be compatible with the Service Pack 1 release. The most significant changes are as follows:
- In BusinessScope.xsd, CorrelationInformationType and BusinessServiceType have been changed to CorrelationInformation and BusinessService, respectively.
- In StandardBusinessDocumentHeader.xsd, StandardBusinessDocumentHeaderType and StandardBusinessDocumentType have been changed to StandardBusinessDocumentHeader and StandardBusinessDocument, respectively.
- In EPCIS.xsd, eventTimeZoneOffset has been added to the definition of EventListType. It differs from the specification in that it includes the attribute minOccurs='0' for backwards compatibility with the previous version of Enterprise Server.
- In EPCIS-query.xsd, QueryTooLargeException was removed from the definition of QueryResultsBody.
- In EPCIS.wsdl, the value of the name attribute of wsdl:port was changed from EPCglobalEPCISService to EPCglobalEPCISServicePort and the values of the targetNamespace and xmlns:impl attributes were changed from urn:epcglobal:epcis-wsdl:xsd:1 to urn:epcglobal:epcis:wsdl:1.
- In EPCIS-masterdata.xsd, the definition of AttributeType is restricted due to a limitation in a third-party product. While the specification suggests that both of the following formats should be supported, only the first format is supported in this release:
<attribute id="urn:epcglobal:epcis:mda:description">some text here</attribute>
<attribute id="urn:epcglobal:epcis:mda:description">
<foo>bar</foo>
<foo2>bar2</foo2>
</attribute>.
|
|
|
If the account used by Enterprise Server to log in to the database server has DBA privileges, then the applications will stop working.
Make sure the account used by Enterprise Server to access the database does not have DBA privileges.
|
|
|
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.
|
|
|
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.
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.
|
|
|
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.
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.
|
|
|
A FatalDataStoreException is thrown if you start WebLogic Enterprise Server before starting the database.
|
|
|
In the Query Subscription Administration Console, when adding subscription parameters, the table displays 10 parameters per page; this is not configurable.
|
|
|
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.
Select only one item at a time. If possible, avoid using the mouse wheel when selecting items from drop-down lists.
|
|
|
When capturing SGLN and GRAI tags with a company_prefix containing 12 digits, the EPC.REFERENCE field gets the value 0 instead of null.
|
|
|
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.
|
|
|
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.
|
|
|
When installing on UNIX, using a leading backslash ( \) in the install directory path causes the Configuration Wizard to fail silently.
|
|
|
In the Query Subscription Administration Console, to use authentication on a JMS destination, enter the relevant properties in the Naming Service Properties text field.
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. |
|
|
|
If your PointBase database connection is lost, you must restart the Enterprise Server after restoring your database connection.
|
|
|
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.
Start a new browser session.
|
|
|
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.
|
|
|
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.
|
|
|
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)
|
|
|
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.
Create the full number of search criteria rows before putting values in the text fields.
|
|
|
In the Edge Server Administration Console, the wrong ECSpec Subscriber subscription properties page might be displayed after selecting an ECSpec Subscriber to edit.
Click Cancel on the ECSpec Subscriber subscription properties page. Then re-select the ECSpec Subscriber edit link.
|
|
|
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.>
Disregard these messages; they have no effect on the application.
|
|
|
In the Edge Server Administration Console, PLC Stack Light RFID devices always display an UP Device Status regardless of their actual state.
|
|
|
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).
To use the Microsoft SQL Server 2005 JDBC driver, follow these steps:
- Download and install the driver from the MSDN Web site (follow the Microsoft instructions).
- 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).
- 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).
- 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
- Add
sqljdbc.jar to the C:\BEA_HOME\user_projects\domains\DOMAIN_NAME\lib directory.
- 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.
- In the WebLogic Server Administration Console, create a new credential map (click New), with these fields (leave the other fields blank):
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
- Restart WebLogic Server.
| Note: |
These steps also apply to all other supported JDBC drivers that are not shipped with the product. |
|
|
|
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>
Disregard these messages.
|
|
|
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
This exception is harmless; you can ignore it.
|
|
|
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.
|
