Operating System Version and Patches

HP Integrity NonStop^TM Server H06.10 SUT or higher

NonStop SQL/MX Release 2.2, T1050H22 or higher

vproc Details : T1050H22_10APR2006_ACO_221_0410

NonStop Server for JDBC/MX, T1275H50

vproc Details : T1275H50_23DEC2005_JDBCMX_1220

NonStop TCP/IPv6, T1265H01, running in INET mode

vproc Details : T1265H01_10APR2006_H01_SAM_AAX_0

NonStop XARM License File, T2921H13

vproc Details: T2921H13 1DEC2007 AAA

Chip Architecture and Minimum Processor Speed

Intel Itanium (1.6 GHz)

Hardware Family: Any HP Integrity NonStop^TM NS-series servers

SDK

HP NonStopTM Server for JavaTM 5.0, T2766H50, based on the Java 2 Platform, Standard Edition (J2SE), SDK 1.5.0 Java version (build 1.5.0_02-b09 Java 2 Runtime Environment, Standard Edition (build 1.5.0_02 05.04.07-18:23 IA64, mixed mode) Java HotSpot Server VM.

vproc Details :

  Binder timestamp: 04MAY2007 18:39:06

  Version procedure: T2766H50_06JUN2007_jdk150_AAS_04May2007

  Version procedure: T8432H01_05MAY2006_CCPLMAIN

  TNS/E Native Mode: runnable file

RAM

4 GB per processor required

QIO must be configured to use KSEG2.

Performance Pack

Included

libmuxer.a

BEA Product Support

• WebLogic Server 9.2

• WebLogic Workshop 9.2 (runtime)

Design and Development Tools

The WebLogic Workshop IDE is not supported on HP Integrity NonStop Server systems. HP Integrity NonStop Server is supported for the production deployment of applications developed in the WebLogic Workshop IDE. Debugging of applications developed in the WebLogic Workshop IDE, for deployment on HP Integrity NonStop Server, should be accomplished to the extent possible on the Workshop development system; use of JVM debug mode with the NonStop Server for Java significantly degrades application performance and debugging effectiveness. HP Integrity NonStop Server is also supported for the development and production deployment of WebLogic Server applications developed with other tools.

Database Cascade Deletes Are Not Supported.

NonStop SQL/MX 2.2 does not support cascade deletions on a table. As a result, any Container Managed Persistence (CMP) EJB that relies on the database cascade delete feature to delete the data from the SQL/MX database fails.

The deployment descriptor of an EJB should not contain db-cascade-delete in its weblogic-cmp-jar.xml. This enables WebLogic Server to delete rows using explicit SQL delete statements.

Automatic Table Creation for EJB Container Managed Persistence (CMP) May Fail.

Automatic table creation for a CMP EJB using the deployment descriptor tag create-default-dbms-table may fail in two situations:

1. If the table contains column names that are keywords in NonStop SQL/MX.

2. If the table includes a primary key column. NonStop SQL/MX 2.2 expects the primary key column to be qualified as NOT NULL NOT DROPPABLE. However, automatic table creation does not generate the NOT NULL NOT DROPPABLE clause.

1. Make sure the CMP deployment descriptor does not use SQL/MX keywords as table column names.

2. Make sure the table is created before the EJB is deployed so that the table schema exists when WebLogic Server checks for table information for the EJB.

Sequence Entities Are Not Supported

Sequences/Identity columns are not supported in NonStop SQL/MX. Hence, automatic key generation for an EJB in WebLogic Server using sequences is not supported.

The automatic key can be generated using NamedSequenceTable as the value of the generator-type specified in the automatic-key-generation section of the weblogic-cmp-jar.xml file. The schema for the table name specified in the generator-name should have one column sequence of type Integer.

The following code shows a sample entry:

<automatic-key-generation>

<generator-type>NamedSequenceTable</g enerator-type>

<generator-name>sequencetable</genera tor-name>

<key-cache-size>10</key-cache-size>

</automatic-key-generation>

Table schema:

CREATE TABLE SEQUENCETABLE (SEQUENCE INTEGER);

Deployment Error During Use of WebLogic 5.1-Style Deployment Descriptor

When an EJB has a WebLogic Server 5.1-style deployment descriptor, the EJB fails to deploy on WebLogic Server. The doctype for a 5.1-style descriptor is as follows:

<!DOCTYPE weblogic-rdbms-bean PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN' http://www.bea.com/servers/wls510/ dtd/weblogic-rdbms-persistence.dtd '>

Convert the 5.1-style deployment descriptor to a WebLogic Server 7.0 (or later) style deployment descriptor. Some of the changes required are conversion of the pool-name tag to data-source-name and conversion of the attribute-map to a field-map. WebLogic Server provides a DDConverter utility to convert the beans from earlier versions of WebLogic Server. For further documentation about how to use the DDConverter utility, see the documentation at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ejb/implementing.html#DDConverter

Certain CMP-Generated Code That Assumes Implicit Type Cast Conversion Fails

Certain instances of CMP-generated code based on the assumption of implicit type cast conversion fail. If the CMP-generated code assumes implicit type cast conversion (for example, conversion from string to integer), the SQL execution at run time fails. Implicit type casting of data types is not supported in NonStop SQL/MX 2.2.

None

EJB-QL That Uses the SQL SUBSTRING Function Fails

Any EJB-QL that uses the SQL SUBSTRING function fails to execute because the parameters of the SQL/MX SUBSTRING function are different from the parameters used by other databases supported by WebLogic Server.

None

Container Managed Relationship Caching Cannot Be Specified

Container Managed Relationship (CMR) caching cannot be specified when using NonStop SQL/MX 2.2.

None

Only the "default database type" Is Supported for CMP

For CMP, no database types other than the default type are supported.

None

SQL/MX 2.2 Triggers Have Restrictions

The use of SQL/MX 2.2 triggers is affected by several restrictions:

• The trigger action must comprise just one statement.

• The trigger action statement cannot be a call to a Java Stored Procedure.

• "BEFORE"-type triggers can be used only to inspect or modify data, or to return SQLState or vendor error code information.

None

Large Objects (BLOBs and CLOBs) Require Use of Special Tables

SQL/MX 2.2 MX Tables supports large objects (BLOBs and CLOBs) only with the use of special additional tables.

When a table contains a BLOB or CLOB column: These special tables must be pre-created for both production and development mode by users of WebLogic Server. The JdbcMxLobAdmin utility is the recommended facility for pre-creating tables that contain BLOB or CLOB columns, as well as for creating the special tables used to store the LOB data. The names of these tables must be specified to the JDBC/MX driver as properties in the Java options.

Restrictions on Use of Native SQL/MX Utilities

SQL/MX 2.2 utilities, including mxci, cannot be used to insert, delete, or update data in tables that contain LOB columns.

Use the JDBC/MX V32 driver to perform these operations.

SQL/MX 2.2 does not support ROWNUM

None

SetAutoCommit Property cannot be changed when a transaction is active in JDBC/MX.

None

SQL/MX 2.2 does not support save points on a table.

None

Commit method does not throw the `HeuristicRollbackException' in the following scenario mentioned below:

• xa1.setException(xid,XA_COMMIT_OP,XAException.XA_HEURRB,"HeurRollback"); xa2.setException(xid,XA_COMMIT_OP,XAException.XA_HEURRB,"HeurRollback");

• xa1.enlist();

• xa2.enlist();

• tm.commit();

Instead, In NSK it throws the `HeristicMixedException'.

Nodemanager ssh and rsh features are not available on NonStop

None

Nodemanager command nmKill() is not supported on NonStop.

Identify the process using the ps command and issue an OS Kill command to kill the process.

WebLogic Server

BEA WebLogic Server Known and Resolved Issues:

http://download.oracle.com/docs/cd/E13222_01/wls/docs92/issues/known_resolved.html

Installation and Configuration

BEA Products Installation and Configuration Release Notes:

http://download.oracle.com/docs/cd/E13179_01/common/docs92/relnotes/relnotes.html