Skip navigation.

8.1 Supported Configurations: HP NonStop Server on MIPS

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

HP NonStop Server G06 on MIPS with 8.1 SP2

Provides full support for WebLogic Server and run-time only support for WebLogic Workshop and WebLogic Integration. WebLogic Portal is not supported. See below for Design and Development Tools support.


 

This section provides the following information:

Related Information

 

Configuration Requirements

Table 1-1 Requirements for 8.1 SP2 on HP NonStop server G06

Operating System Version and Patches

HP NonStopTM Kernel G06.20 SUT

NonStop SQL/MX 1.8.5, T1050G08, SPR AAV

HP NonStop server for JDBC/MX, T1225V30, PVU V30 AAE

NonStop TCP/IPv6, T1265G06, SPR AAD running in INET mode

HP NonStopTM Kernel G06.23 SUT

NonStop SQL/MX Release 2.0 MX Tables, T1050G10, SPR ABA

HP NonStop server for JDBC/MX, T1225V31, SPR AAJ

NonStop TMF, T8607G07, SPR AFQ

NonStop DP2, T9053G10, SPR APA

NonStop TCP/IPv6, T1265G06, SPR AAD running in INET mode

Chip Architecture and Minimum Processor Speed

MIPS (500 MHz recommended)

Hardware Family: Any HP NonStopTM S-series server S72000 or later processors

SDK

HP NonStopTM server for JavaTM 4.0, T2766V10 SPR AAE, based on the Java 2 Platform, Standard Edition (J2SE), SDK 1.4.1 Java version 1.4.1_05 Java 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot Server VM.

Design and Development Tools

The WebLogic Workshop IDE and WebLogic Integration Format Builder are not supported on HP NonStop server systems. HP 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 NonStop server, should be accomplished to the extent possible on the Workshop development system; use of JVM debug mode with the NonStop Java significantly degrades application performance and debugging effectiveness. HP NonStop server is also supported for the development and production deployment of WebLogic Server applications developed with other tools.

RAM

2 GB per processor required;
4GB per processor recommended

QIO must be configured to use KSEG2.

Performance Pack

Included

libmuxer.a

Node Manager

Included

Java

BEA jDrivers for Oracle

Not supported


 

SQL/MX Database Configuration

WebLogic Platform supports the SQL/MX database on NonStop server configurations, but not all WebLogic Platform components support the same versions: WebLogic Server supports SQL/MX 2.0 and SQL/MX 1.8.5; WebLogic Integration supports only SQL/MX 2.0.

This section provides important information about configuring the SQL/MX database for use with WebLogic Server and WebLogic Integration on HP NonStop server:

For detailed information, see BEA WebLogic Server and WebLogic Platform 8.1 SP2 Software on HP NonStop servers: Installation guide:

http://h71028.www7.hp.com/ERC/downloads/BEA%20WLS-WLP.pdf

 

Known Issues

This section provides descriptions of limitations that have been identified and, whenever possible, workarounds for them. Issues have been identified in the following areas:

WebLogic Server Limitations with SQL/MX 2.0

JDBC/MX driver version V31 is supported for use with SQL/MX 2.0. The following limitations apply to using SQL/MX 2.0 with WebLogic Server:

1: Database Cascade Deletes Are Not Supported

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

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

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

This problem may arise under two situations:

Situation (a): Automatic table creation for a CMP EJB using the deployment descriptor tag create-default-dbms-tables fails if the table has column names which are keywords in NonStop SQL/MX.

Workaround: The CMP deployment descriptor should not use SQL/MX keywords as table column names.

Situation (b): Automatic table creation for a CMP EJB using the deployment descriptor tag create-default-dbms-table fails if the table has a primary key column. NonStop SQL/MX 2.0 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.

Workaround: The table should be pre-created before the EJB is deployed so that the table schema exists when WebLogic Server checks for table information for the EJB.

3: Sequence Entities Are Not Supported

Problem: 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.

Workaround: The automatic key can be generated using NamedSequenceTable as the value of the generator-type in the automatic-key-generation section of the weblogic-cmp-jar.xml. 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</generator-type>
<generator-name>sequencetable</generator-name>
<key-cache-size>10</key-cache-size>

</automatic-key-generation>

Table schema :

CREATE TABLE SEQUENCETABLE (SEQUENCE INTEGER);

4: Deployment Error During Use of WebLogic 5.1-Style Deployment Descriptor

Problem: When an EJB has a WebLogic Server 5.1-style deployment descriptor, the EJB fails to deploy on the WebLogic Server. Any EJB that uses a WebLogic Server 5.1-style deployment descriptor fails to deploy. 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'>

Workaround: 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 BEA Web site.

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

Problem: 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 from string to integer), the SQL execution at runtime fails. Implicit type casting of data types is not supported in NonStop SQL/MX. 2.0.

Workaround: None

6: EJB-QL That Uses the SQL SUBSTRING Function Fails

Problem: 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.

Workaround: None

7: Container Managed Relationship Caching Cannot Be Specified

Problem: Container Managed Relationships (CMR) caching cannot be specified when using NonStop SQL/MX 2.0.

Workaround: None

8: Only the "default database type" Is Supported for CMP

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

Workaround: None

9: SQL/MX 2.0 Triggers Have Restrictions

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

Workaround: None

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

Problem: SQL/MX 2.0 does not support large objects (BLOBs and CLOBs) without the use of special additional tables.

Workaround: Special additional tables must be used. When a table contains a BLOB or CLOB column:

11: Restrictions on Use of Native SQL/MX Utilities

Problem: Native SQL/MX utilities (including mxci) cannot be used to insert, delete, or update data in tables that contain LOB columns.

Workaround: Use the JDBC/MX V31 driver to perform these operations.

WebLogic Server Limitations with SQL/MX 1.8.5

JDBC/MX driver version V30 is supported for use with SQL/MX 1.8.5. All the limitations described for SQL/MX 2.0 also apply to SQL/MX 1.8.5.

In addition, the use of SQL/MX 1.8.5 with WebLogic Server is affected by the following limitations:

1: Triggers Are Not Supported

Problem: SQL/MX 1.8.5 does not support triggers.

Workaround: None

2: Large Objects (BLOBs and CLOBs) Are Not Supported

Problem: This problem is manifested in the following ways:

3: Generated CMP Code That Uses the != Operator Fails

Problem: SQL/MX 1.8.5 does not support != as an inequality operator. Therefore, if the generated code for a CMP EJB contains != as an inequality operator, SQL execution fails during runtime.

Workaround: None

4: Any EJB-QL That Uses the ABS or LOCATE Function Fails to Execute

Problem: Any EJB-QL that uses either the ABS or LOCATE function fails to execute because the parameters of these functions for SQL/MX 1.8.5 are different from the parameters used by other databases supported by WebLogic Server.

Workaround: None

General Limitations with WebLogic Integration on NonStop server

This section describes general limitations that affect the use of WebLogic Server on a NonStop server configuration:

1: First Attempt to View Printable Graph of WLI Process Fails

Problem: The first time you try to view the printable graph of a WebLogic Integration process instance from the WebLogic Integration Administration Console, a server exception is displayed in the browser window. This problem is due to the fact that the NonStop server platform is headless.

Workaround: Try again. The printable graph is displayed but with icons that are less descriptive than those provided through the interactive process view graph. It is recommended that users print using the Interactive Process View.

2: Recovery of Already Committed Transactions Will Trigger Exception

Problem: When WebLogic Transaction Manager performs a recovery after a restart, it may try to redrive a second-phase commit of transactions that have already been committed and forgotten by the resources, but that are still present in the transaction logs. If the resource managers have already forgotten a transaction, they respond with an XAER_NOTA error code that WebLogic ServerTM ignores. Under some conditions, WebLogic ServerTM does not ignore this error code from the XA resources, and it throws an XAER_HEURHAZ exception. This behavior does not affect the outcome of these transactions, however, because the transactions are already committed and forgotten.

Workaround: None

3: Duplicate Attempt to Insert a Row into the Message Tracking Table

Problem: Occasionally, when a WebLogic Integration instance (configured to use SQL/MX as the data store) fails and is restarted, a duplicate attempt may be made, during recovery, to insert a row into the message tracking table. This attempt fails with a database unique constraint violation. This failure can be ignored because no data is lost.

Workaround: None

4: Message Broker Limitations

Problem: Filter values may not exceed 2000 bytes. This restriction may preclude the use of complex XML.

The rule name cannot exceed 140 bytes. It is derived from the consuming WebLogic Integration process type that invokes the dynamic subscription control. Its total length (in bytes) is:

5 + <length_of_process_type> + <length_of_the_control's_field_name>

This formula restricts the length of the process type name to:

135 - <length_of_the_control's_field_name>.

Workaround: None

5: Worklist Limitations

Problem: Worklist comments may not exceed 3950 bytes.

Workaround: None

6: B2B Limitations

The following limitations, for which there are no workarounds, apply to the use of B2B functionality:

WebLogic Integration Limitations with SQL/MX 2.0

The use of WebLogic Integration with SQL/MX 2.0 is affected by the following limitations:

1: Restrictions on Use of Internal Tables

Problem: For its internal tables, WebLogic Integration can only use SQL/MX 2.0 ANSI-tables; SQL/MX 1.8.5 is not supported for use with WebLogic Integration internal tables. A number of WebLogic Integration SQL objects have been modified for SQL/MX 2.0, principally because of the following SQL/MX 2.0 restrictions:

Workaround: None

2: AI Sample Adapter Is Not Available

Problem: The AI sample adapter, supplied with WebLogic Integration, is not available for use with SQL/MX.

Workaround: None

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

See 10: Large Objects (BLOBs and CLOBs) Require Use of Special Tables.

For More Information About Known Issues

For more information about known issues, see the Release Notes for the appropriate product:

 

Download and Installation Instructions

On the HP NonStop server, only WebLogic Server and WebLogic Integration are supported; no other components of the WebLogic Platform product are supported. This section provides instructions for users who plan to use (a) both WebLogic Server and WebLogic Integration 8.1 SP2 or (b) WebLogic Server 8.1 SP2. To install both WebLogic Server and WebLogic Integration, follow the download instructions for BEA WebLogic Platform 8.1 SP2. To install only WebLogic Server, follow the download instructions for BEA WebLogic Server 8.1 SP2.

Note: To successfully install BEA WebLogic Platform 8.1 SP2 or BEA WebLogic Server 8.1 SP2 on the NonStop server, you must download and install the NonStop Server Toolkit, as instructed in Downloading the HP NonStop Server Toolkit.

The following sections provide instructions for these tasks:

Before you begin, review all instructions.

Downloading BEA WebLogic Server 8.1 SP2 and the Supplemental JAR File

  1. Go to the BEA Downloads site:

    2. http://commerce.bea.com/showallversions.jsp?family=WLS

  2. On the Downloads site:
    1. Find WebLogic Server Package Installer.
    2. Find WebLogic Server/Express 8.1 with SP2.
    3. Select HP NonStop Kernel as your operating system.
  3. Download the WebLogic Server installation file: pj_server812_generic.jar.
  4. From the same download site, download the supplemental JAR file for HP NonStopTM server by selecting the link for it: platform81sp2_hpns_supp.jar. This JAR file contains HP NonStopTM server-specific modifications to the standard BEA WebLogic Server 8.1 SP2 files.
  5. Verify that you have write permission for the root directory on the NonStop server to which you plan to copy this software.
  6. Use ftp to copy BEA WebLogic Server 8.1 SP2 (pj_server812_generic.jar) and the supplemental JAR file (platform81sp2_hpns_supp.jar) to an empty directory on the NonStop server. If such a directory does not already exist, create one now:
    7. $ mkdir -p /usr/tandem/wlhpns/download81sp2
  7. Make a note of the directory in which the server and supplemental JAR files have been copied. This directory will be used in subsequent steps.
  8. Go to Downloading the HP NonStop Server Toolkit.

Downloading BEA WebLogic Platform 8.1 SP2 and the Supplemental JAR File

  1. Go to the BEA Downloads site: 
    2. http://commerce.bea.com/showallversions.jsp?family=WLP
  2. On the Downloads site:
    1. Find the WebLogic Platform Package Installer.
    2. Find WebLogic Platform 8.1 with SP2.
    3. Select HP NonStopTM Kernel as your operating system.
  3. Download the WebLogic Platform installation file: pj_platform812_generic.jar.
  4. From the same download page, download the supplemental JAR file for HP NonStopTM server by selecting the link for it: platform81sp2_hpns_supp.jar. This JAR file contains HP NonStopTM server-specific modifications to the standard BEA 8.1 SP2 files.
  5. Verify that you have write permission for the root directory on the NonStop server to which you plan to copy this software.
  6. Use ftp to copy BEA WebLogic Platform 8.1 SP2 (pj_platform812_generic.jar) and the supplemental JAR file (platform81sp2_hpns_supp.jar) to an empty directory on the NonStop server. If such a directory does not already exist, create one now:
    7. $ mkdir -p /usr/tandem/wlhpns/download81sp2
  7. Make a note of the directory in which the platform and supplemental JAR files have been copied. This directory will be used in subsequent steps.
  8. Go to Downloading the HP NonStop Server Toolkit.

Downloading the HP NonStop Server Toolkit

  1. Download the NonStop Server Toolkit (weblogic81sp2_hpns_v12.zip) from the "Resources" section of either of the following HP download sites:
  2. Use ftp to copy the downloaded file to the directory on the NonStop server that contains the supplemental JAR file (platform81sp2_hpns_supp.jar).

    3. For more information about WebLogic products on the NonStop platform, see:

http://h30163.www3.hp.com/NTL/library/Independent_Products/BEA_WebLogic_Products
  1. Go to Installing BEA WebLogic Server or WebLogic Platform 8.1 SP2.

Installing BEA WebLogic Server or WebLogic Platform 8.1 SP2

This section provides:

Installation Prerequisites

You must have already downloaded the following:

The HP NonStop server platform can be used with the NonStop SQL/MX database. The following table shows which versions of the NonStop SQL/MX database are supported by WebLogic Server 8.1 SP2 and WebLogic Integration 8.1 SP2.

This version of NonStop SQL/MX . . .

Is supported by the following WebLogic Platform component . . .

1.8.5, T1050G08, SPR AAV

WebLogic Server 8.1 SP2

2.0 MX Tables, T1050G10, SPR ABA

  • WebLogic Server 8.1 SP2

  • WebLogic Integration 8.1 SP2


 

If you are using the NonStop SQL/MX database, then you must have configured the database as specified in SQL/MX Database Configuration.

Installation Procedure

  1. Before starting the installation process, verify the following:
  2. Set and export the environment variables required for use with NonStop server for Java 4.0 and NonStop TCP/IPv6. Save the commands used for setting these variables in a file, such as your .profile.
    1. Set and export the following environment variables. For example:
      2. $ export JAVA_HOME=/usr/tandem/java
      $ export JREHOME=$JAVA_HOME/jre
      $ export PATH=$JAVA_HOME/bin:$PATH
      $ export WL_HOME=/usr/bea/weblogic81
      $ export JDBCMX_DIR=/usr/tandem/jdbcMx
      $ export JAVA_PUBLIC_LIB=/usr/tandem/java_public_lib

      $ add_define =PTCPIP^FILTER^KEY class=map file=mykey

      Note: The environment variables JAVA_HOME, JREHOME, PATH, and WL_HOME do not have default values. Set the variables to actual or intended locations before executing the check-wl-hpns.sh and install-wl-hpns.sh scripts.

    2. If your NonStop TCP/IPv6 process is not named $ZTC0, create a define to indicate the process name. For example, in the following add_define statement, the TCP/IP process name is $ZSM1. You must include an escape character before the $ that precedes ZSM1:
      3. $ add_define =TCPIP^PROCESS^NAME class=map file=\$ZSM1
  3. Prepare to install WebLogic Platform 8.1 SP2 or WebLogic Server 8.1 SP2 on the NonStop server:
    1. Go to the directory in which you downloaded the NonStop Server Toolkit file (weblogic81sp2_hpns_v12.zip):
      2. $ cd /usr/tandem/wlhpns/download81sp2
    2. Extract the files from the ZIP file:
      3. $ jar -xvf weblogic81sp2_hpns_v12.zip
    3. Set execute permission on the newly extracted shell scripts:
      4. $ chmod 755 *sh
    4. Verify that all necessary software is installed on the NonStop server:
      5. $ ./check-wl-hpns.sh

      Note: Use the -h option to see a complete list of options for this script. Resolve any errors produced by the check-wl-hpns.sh script before proceeding.

  4. Install WebLogic Platform 8.1 SP2 or WebLogic Server 8.1 SP2:
    1. Find the instructions for console-mode installation, for UNIX systems, in the BEA documentation:
      2. http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/console.html
    2. Follow the instructions in the section called "Starting Console-Mode Installation for .jar Installation Files":
  5. Install the NonStop Server Toolkit and supplemental JAR file by running the following script:
    6. $ ./install-wl-hpns.sh

    Note: Use the -h option to see a complete list of options for this script. If, earlier, you ran the installation script install-wl-hpns.sh with the -j n options, you now need to rebuild the JVM before proceeding.

  6. Access the documentation for running WebLogic Platform 8.1 SP2 and WebLogic Server 8.1 SP2 on the NonStop server from the NonStop Technical library at: 
    7. http://h30163.www3.hp.com/NTL/library/Independent_Products

    The documentation is available under "BEA WebLogic Products."

For More Information About Installation and Configuration

For more information about how to install and configure WebLogic Server 8.1 SP2 on HP NonStop server, see the following links:

http://h30163.www3.hp.com/NTL/library/Independent_Products/BEA_WebLogic_Products/WebLogic_Server__WLS__8_1
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ejb/DDreference-cmp-jar.html
http://h30163.www3.hp.com/NTL/legal.asp?redirect_page=/NTL/library/Independent_Products/BEA_WebLogic_Products

 

Back to Top Previous Next