| Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Microsoft Windows and Microsoft Windows x64 B14437-09 |
|
 Previous |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Microsoft Windows and Microsoft Windows x64 B14437-09 |
|
Previous |
This chapter describes issues with Oracle Sensor Edge Server. It includes the following topics:
This section describes installation and configuration issues regarding Oracle Sensor Edge Server. It includes the following topics:
Section 11.1.1, "Valid 10.1.3 OC4J in Correct Oracle Home Required for Oracle Sensor Edge Mobile"
Section 11.1.2, "OC4J 10.1.2 Must be Stopped if Installing Against It"
Section 11.1.4, "Oracle Sensor Edge Server Installation Fails"
Section 11.1.5, "Resolving the Reboot Issue for XML Configuration"
You must have OC4J 10.1.3 installed into the same Oracle home into which you are going to install Oracle Sensor Edge Mobile. Having OC4J in another location is not supported by Oracle Universal Installer.
After confirming that OC4J is installed in the proper place, you can install Oracle Sensor Edge Server products. To install any Oracle Sensor Edge Server products, you must first select Oracle Sensor Edge Server in the Installation screen. Subsequently, you will be able to install Oracle Sensor Edge Server, Oracle Sensor Edge Mobile, or both products.
If you install both products, you will be given the option of launching the Sensor Edge Welcome twice. Both products are trying to open the same Welcome page; opening either one opens the same page.
As noted in Oracle Sensor Edge Server Guide, you can install Oracle Sensor Edge Server along with OC4J 10.1.2 (versus the current 10.1.3 version). If you choose to install Oracle Sensor Edge Server with OC4J 10.1.2, ensure that OC4J is not running at the time. If OC4J 10.1.2 is running when you try to install Oracle Sensor Edge Server against it, the installation will fail.
The scripts included with Oracle Sensor Edge Server are for a simple, generic installations. Our testing is accomplished against such generic installations.
However, in enterprise environments, there may be many custom requirements and configurations that customers must design and implement themselves.
For this reason, please ensure that you are familiar with tablespace creation. To learn about database tablespace creation, see the Oracle Database SQL Reference and Oracle Database Concepts guides for your particular release.
Once you have set up your database (including the server, datafiles, and tablespaces across datafiles), you can modify Oracle Sensor Edge Server install scripts as needed.
create_edg_user.sql is used for SDS, and create_edg_sda_user.sqlis used for SDR.
These scripts must be modified to use newly-created tablespaces for specific customer requirements.
Under the create user command where you specify which tablespace the user is to use, change the line containing 'create user' in the .sql scripts, according to the manual.
When installing the Oracle Sensor Edge Server, do not select the Oracle Containers for J2EE 10.1.3.0.0 option from the companion CD Oracle Universal Installer (OUI); selecting this option along with the SES option causes the Oracle Sensor Edge Server installation to fail. The valid OC4J instance is installed using the Oracle Application Server CD-ROM (or DVD-ROM), not the companion CD OUI. For more information, see the Oracle Application Server Installation Guide appropriate to your platform.
Error messages regarding invalid jms.xml typically occur because of an abnormal termination of OC4J, an OC4J crash, or the IP address of the server running OC4J changes.
If you encounter OC4J JMS Server startup problems after an abnormal shutdown, first check that no other OC4J JMS Server is running and using the same persistence files. Remove any .lock files from the ORACLE_HOME/j2ee/instance_name/persistence directory and then try restarting again.
If problems persist, confirm that the jms.xml file is valid.
If problems still persist, remove the jms.state file from the persistence directory and try again. Removing this file may result in the loss of transaction information. See also the section entitled "Abnormal Termination", located in the "Resource Providers" in "Chapter 3: Oracle Enterprise Messaging Service (OEMS)" of Oracle Containers for J2EE Services Guide.
This section describes general issues encountered in Oracle Sensor Edge Server. It includes the following topics:
When using the API UTL_EDG.REMOVE_RULE, an error may be encountered. This API only works if your rule was created through other Oracle Sensor Edge Server APIs.
In this release, be sure to use the syntax ':event' instead of 'TAB.USER_DATA'.
The character set defined in the Server Locale overrides the characters set in the browser locale even when you switch the browser locale. For example, if you switch the browser locale to Japanese, the Server Locale is defined as traditional Chinese, the strings in the Navigation Tree of the SES Console (such as the Available Extensions, filters, devices, and device group nodes) and the error and confirmation messages render in traditional Chinese rather than in Japanese. To correct this problem, reset the Server Locale, or override the Server Locale-defined character set by overloading MsgTranslator methods to take locale. String literals in the SESConfig tree control must be non-static and fetched using Locale on each page request.
The Audio Event Type (which is the event supported by the Simple Audio Driver) has been reassigned from 207 to 104, and is now included in the group Generic Instructions to Devices (Event Types 100 - 199). Its Subtype remains 1 (Play audio jobs in the .xml file in the Datafield).
This section describes documentation issues regarding Oracle Sensor Edge Server. It includes the following topic:
Section 11.3.1, "Documentation for Oracle Sensor Edge Server Extensions"
Section 11.3.2, "Manually Deploying Sensor Data Streams Against an Existing Sensor Data Repository"
Once the server is installed, you can see documentation for extensions at: http://<host on which SES is installed>:<oc4j port>/edge/extensions. Or, see Oracle Sensor Edge Server information on Oracle Technology Network at: http://www.oracle.com/technology/products/sensor_edge_server/extensions.html.
Oracle Sensor Edge Server Guide omits a step in describing how to manually deploy Sensor Data Streams if you have already created a Sensor Data Repository. The procedure for manually deploying Sensor Data Streams if the Sensor Data Repository exists is as follows:
Use SQL*Plus to connect to the database as sysdba, by running sqlplus /nolog.
Run sqlplus; connect as sys/your_pwd@your_db as sysdba.
Run the script grant_edg_user.sql, located in Oracle_Home /edge/stage/sql/10.1.3.
Disconnect as sys and then reconnect to the database as the edge user.
Run the script edg_create_streams.sql, located in Oracle_Home /edge/stage/sql/10.1.3.
Follow the procedure described in "Connecting Oracle Sensor Edge Server to Sensor Data Streams".
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|