HP NonStop Server Platform Guide for WebLogic Server Abstract This manual describes the installation, configuration, and management of the BEA WebLogic Server 7.0 SP1 on HP NonStop™ servers. Product Version HP NonStop Server Toolkit for BEA WebLogic Server 7.
Document History Part Number Product Version 525779-001 HP NonStop Server Toolkit for BEA WebLogic Server 7.
HP NonStop Server Platform Guide for WebLogic Server Glossary Index What’s New in This Manual v Manual Information v New and Changed Information Legal Notice v Figures Tables v About This Manual vii Who Should Read This Guide vii Organization of This Manual vii Related Documentation viii Your Comments Invited viii Notation Conventions viii 1.
3. Configuring Persistent WebLogic Server Processes Contents 3. Configuring Persistent WebLogic Server Processes Overview of Generic Processes 3-1 Considerations 3-2 Configuration 3-2 Automatic Restart 3-2 Sample Scripts 3-2 Managed Servers 3-3 Generic Process Attributes 3-4 Sample Shell Scripts and TACL Macros 3-5 startgp.sh 3-5 startgp.tacl 3-6 Scripts to Start the WebLogic Server Process 3-6 stopgp.sh and stopgp.tacl 3-6 nodemanager.sh 3-7 Shutting Down a WebLogic Server Application 3-8 4.
Figures Contents Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 6-1. WebLogic Server on NonStop Server Architecture 1-3 WebLogic Server Domain Representation on a 4-Way SMP Machine 1-4 WebLogic Server Domain Representation on a NonStop Server Sample Pet Store Screen 6-6 Tables Table 3-1. Table 5-1.
Contents HP NonStop Server Platform Guide for WebLogic Server —525779-001 iv
What’s New in This Manual Manual Information WebLogic Server for the HP NonStop Server Platform Guide Abstract This manual describes the installation, configuration, and management of the BEA WebLogic Server on HP NonStop™ servers. Product Version HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Part Number Published 525779-001 June 2003 Document History Part Number Product Version Published 525779-001 HP NonStop Server Toolkit for BEA WebLogic Server 7.
What’s New in This Manual HP NonStop Server Platform Guide for WebLogic Server —525779-001 vi Legal Notice
About This Manual This guide describes: • • • • • The BEA WebLogic Server (WebLogic Server) for the HP NonStop server platform How to install the HP NonStop Server Toolkit for BEA WebLogic Server 7.
Related Documentation About This Manual Related Documentation This guide should be used in conjunction with: • • • • • • • The BEA suite of documentation on WebLogic Server located at http://edocs.bea.com/platform/docs70/index.
General Syntax Notation About This Manual General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type.
General Syntax Notation About This Manual Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted.
1 The BEA WebLogic Server for the HP NonStop Server The WebLogic Server for the HP NonStop Server Specific Enhancements High Level Architecture Differences Between SMP Systems and HP NonStop Servers The BEA WebLogic Server (WebLogic Server) is a standards-based J2EE application server that provides a foundation for building applications, and includes: • • • • • • • • • • • • Load balancing Fault tolerance Web services Network transparency Legacy integration Transaction management Security Multi-threading
The BEA WebLogic Server for the HP NonStop Server Specific Enhancements Section 5, XA Resource Manager (XARM) for further information about the XA resource manager. • • • An HP NonStop Server Customization Kit for WebLogic Server containing: ° A Java XA resource object adapted specifically for the WebLogic Server so that NonStop server resources can participate in WebLogic Server global transactions.
The BEA WebLogic Server for the HP NonStop Server High Level Architecture patch level 3. The NonStop server for Java Version 3.1 has been updated to conform to this. Refer to Java documentation for more information. High Level Architecture The WebLogic Server provides standards-based access to NonStop server resources protected by TMF. The XA resource object facilitates transactional access of NonStop server resources within the scope of the WebLogic Server global transaction.
The BEA WebLogic Server for the HP NonStop Server Differences Between SMP Systems and HP NonStop Servers The Administrative Server, Managed Servers as part of a cluster, Managed Servers independent of clusters, and Node Manager all run on a single SMP machine. The threads of all these Java Virtual Machine (JVM) instances can be scheduled on all the available processors (see Figure 1-2). Fault tolerance is not built into these systems.
The BEA WebLogic Server for the HP NonStop Server Differences Between SMP Systems and HP NonStop Servers The WebLogic Server instances are distributed across all the available CPUs (which are loosely coupled). A JVM and all its threads run within the CPU where the JVM was started, so, when a CPU is lost, only WebLogic Server instances running on that CPU are affected. WebLogic Server instances on other CPUs are not affected.
The BEA WebLogic Server for the HP NonStop Server Differences Between SMP Systems and HP NonStop Servers HP NonStop Server Platform Guide for WebLogic Server —525779-001 1 -6
2 Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Overview Install Prerequisite Software on the HP NonStop Server Copy Software to the HP NonStop Server Install BEA WebLogic Server 7.0 SP1 Install HP NonStop Server Toolkit for BEA WebLogic Server 7.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Copy Software to the HP NonStop Server Copy Software to the HP NonStop Server 1. The HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 is an Independent Product for HP NonStop servers. It is delivered on a single CD and is not packaged as part of a full Operating System release.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Copy Software to the HP NonStop Server uninstall-nsxarm.sh Script that removes the XA resource manager, T2783. The script includes rebuilding the JVM. install-wls-hpns.sh The main installation script for HP NonStop Server Toolkit for BEA WebLogic Server. wls-silent-default.xml Sample file for silent install of BEA WebLogic Server. 3. Run check-wls-hpns.sh to check that your NonStop server is running the prerequisite software.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Copy Software to the HP NonStop Server c. View the prerequisite software that will be checked by using the -h option of the check-wls-hpns.sh script: /usr/tandem/wlshpns [123] ./check-wls-hpns.sh -h usage: check-wls-hpns.sh -h [-h] Give long help text Check that this system has the prerequisite software needed to run the HP NonStop Server Toolkit for BEA WebLogic Server. Required software includes: Operating System = G06.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Copy Software to the HP NonStop Server Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Install BEA WebLogic Server 7.0 SP1 5. The userid used to verify that WebLogic Server installation is correct must be able to create SQL/MP aliases with mxci. This is needed to run the SQL/MX form of the Pet Store sample application. This test requires write access to the MPALIAS table, which should be allowed only for a restricted group of users.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Install HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 12. Set the correct values for the environment variables WL_HOME and JAVA_HOME in the following shell script: setWLSEnv.sh 13. Set the correct values for the environment variables BEA_HOME, WL_HOME, and JAVA_HOME in the following shell scripts: startNodeManager.sh startWLS.sh 14. Set the correct execution mode on the three files just modified: $ chmod +x $FILES 15.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Install HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Example: To install the HP NonStop Server Toolkit using an existing WebLogic Server installation in the standard location: cd /usr/tandem/wlshpns ./install-wls-hpns.sh -p $PWD Example output from an install is: /usr/tandem/wlshpns [125] ./install-wls-hpns.sh -p $PWD install-wls-hpns.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Install HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 /usr/bea/weblogic700/samples/server/src/petstore/src/apps/petstore/ src/docroot/index.jsp_HPNS /usr/bea/weblogic700/samples/server/src/petstore/src/apps/petstore/ src/schema/ /usr/bea/weblogic700/samples/server/src/petstore/src/apps/petstore/ src/schema/create_petdb.sh /usr/bea/weblogic700/samples/server/src/petstore/src/apps/petstore/ src/schema/dropalias.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Install HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 /usr/bea/weblogic700/server/lib/hpns/extras/startServer.sh /usr/bea/weblogic700/server/lib/hpns/extras/stopAdmin.sh /usr/bea/weblogic700/server/lib/hpns/extras/stopManaged.sh /usr/bea/weblogic700/server/lib/hpns/extras/stopOneManaged.sh /usr/bea/weblogic700/server/lib/hpns/extras/wls-silent-cluster.xml /usr/bea/weblogic700/server/lib/hpns/install-wls-hpns.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Install HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 /usr/bea/user_projects/hpns/samples/server/config/petstore/ config.xml_HPNS.0 /usr/bea/user_projects/hpns/samples/server/config/petstore/ petstoreServer/petstoreServer.log /usr/bea/user_projects/hpns/samples/server/config/petstore/ pointbase.ini Changing Pet Store in user_project to use NonStop SQL/MX ... Pet Store will use NonStop SQL/MX.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 Description of Installed Files vprocs for /usr/tandem/nssjava/jdk131_v31/bin/oss/posix_threads/java GMT Binder timestamp: 15MAY2003 00:26:44 Version procedure: T8432G09_30APR20031CRTLMAIN Version procedure: T0083V31_16JUN2003_jdk131_V31AAQ Version procedure: T2783V10_30JUN2003_08May2003 Version procedure: T1225V21_16JUN2003_JDBCMX Version procedure: T5819D46_30MAY2003_AAQ_25APR2003 Native Mode: runnable file install-nsxarm.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 For T2821 JavaLibList_ref A sample listing of libraries linked into the JVM used as a check that the rebuilt JVM is correct. nsxarm.jar Archive of the Java classes that implement the XA resource manager. first.sh Shell script for extracting a small set of installation files from the pax files. This is described in the Readme file for the Independent Product’s CD. For T2821 Directory /usr/bea/weblogic700/server/lib/hpns/ README.
Installing the HP NonStop Server Toolkit for BEA WebLogic Server 7.0 SP1 For T2822 Directory /usr/bea/weblogic700/samples/server/config/petstore/ startPetStore_NSSQL.sh Script that starts the HP NonStop SQL/MX form of the Pet Store sample application. swapPetStore.sh Swaps between the SQL/MX and PointBase forms of the Pet Store sample applications. whichPetStore.sh Reports what form of the Pet Store sample application is currently in use. config.
3 Configuring Persistent WebLogic Server Processes Overview of Generic Processes Considerations Configuration Automatic Restart Sample Scripts Managed Servers Generic Process Attributes Sample Shell Scripts and TACL Macros startgp.sh startgp.tacl Scripts to Start the WebLogic Server Process stopgp.sh and stopgp.tacl nodemanager.
Configuring Persistent WebLogic Server Processes Considerations generic process mechanism cannot be used to directly start and monitor the WebLogic Server application server process. Instead, a program called OSH starts as the generic process. The OSH process runs a shell script that starts and waits for the WebLogic Server process. If the WebLogic Server process later fails, the shell script and OSH process also fail. The $ZPM will restart the generic process.
Configuring Persistent WebLogic Server Processes Managed Servers where a shell process is being started. In a typical installation, this requires changing scripts in the WebLogic Server home directory, too, or using the files from a different location.
Configuring Persistent WebLogic Server Processes Generic Process Attributes ° The WebLogic Server administration server is not able to use the WebLogic Server node manager to start managed servers.
Configuring Persistent WebLogic Server Processes Sample Shell Scripts and TACL Macros Table 3-1. Generic Process Attributes Table Attribute Consideration STARTUPMSG This attribute is limited to 128 characters. The sample scripts use “-c script <->>stdout 2>>stderr”. In this example, -c tells OSH to run script, <- causes OSH to ignore stdin, >> directs output to stdout, and >>2 directs output to stderr.
Configuring Persistent WebLogic Server Processes startgp.tacl startgp.tacl startgp.tacl is a TACL macro that must be copied to the Guardian namespace and converted to an EDIT file using CTOEDIT. As with startgp.sh, the macro needs to be updated to reflect the process to be started and must be run by a member of the SUPER group.
Configuring Persistent WebLogic Server Processes nodemanager.sh nodemanager.sh The node manager can be used to start managed servers. On NonStop servers, native process control is not used. The node manager must be started by using: weblogic.nodemanager.nativeVersionEnabled = false The node manager invokes, by default, a shell script named nodemanager.sh to start the managed server.
Configuring Persistent WebLogic Server Processes Shutting Down a WebLogic Server Application Server domains share the node manager, all managed servers will influence the CPU selection. To avoid this situation, use a different node manager for each domain. Both algorithms are dependent on being able to accurately calculate the current load of the system. However, managed_load depends heavily on the information contained in the files maintained by the node manager.
4 Configuring JTA Java™ Transaction API (JTA) elements of the configuration describe several attributes for controlling the WebLogic Server transaction manager. If the TMF configuration is different for your application, the JTA attributes can be changed. This is an example with some NonStop server-specific changes.
Configuring JTA HP NonStop Server Platform Guide for WebLogic Server —525779-001 4 -2
5 XA Resource Manager (XARM) Configuring the WebLogic Server XA Resource Object Configuring the XA Resource Manager Error Output Destination Configuring the WLSNonStopTxHelper as a Startup Class Configuring the JDBC Connection Pools for SQL/MX Configuring the WebLogic Server Data Sources for SQL/MX Additional Considerations for JDBC Access to SQL/MX DataBases The XA Resource Manager (XARM) for the HP NonStop server is a software component specifically written for and tested with the BEA WebLogic Server.
XA Resource Manager (XARM) Configuring the WebLogic Server XA Resource Object Configuring the WebLogic Server XA Resource Object To configure the NonStop server XA resource object into a WebLogic Server, you must define a startup class. A startup class is a special class that implements the T3StartupDef interface. This startup class is loaded by the WebLogic Server as part of the WebLogic Server startup.
Configuring the XA Resource Manager Error Output Destination XA Resource Manager (XARM) Configuring the XA Resource Manager Error Output Destination You can control the destination of the XA Resource Manager error output by configuring the following environment variables: Name Description XARM_SYSLOG Set to Y to log the XA resource manager error output to the Event Management Service (EMS). Set to N to disable logging the error output to EMS. The default setting is Y.
XA Resource Manager (XARM) Configuring the WLSNonStopTxHelper as a Startup Class The Startup class has no arguments. The arguments for specifying various options are specified in the startup script as Java system properties or by using a properties file. Table 5-1. Java System Properties Used by WLSNonStopTxHelper Property Name Used in Property File Name when Specified with the -D Java Command Line Option name hp.nsk.xares.
XA Resource Manager (XARM) Configuring the JDBC Connection Pools for SQL/MX Table 5-1. Java System Properties Used by WLSNonStopTxHelper (continued) Property Name Used in Property File Name when Specified with the -D Java Command Line Option enabletrace hp.nsk.xares.enabletrace Enables or disables tracing of the XA operations by the XA resource manager. Valid values are true and false. Default value is false. tracefile hp.nsk.xares.tracefile If set to null, tracing is disabled.
XA Resource Manager (XARM) Configuring the JDBC Connection Pools for SQL/MX a WebLogic Server transaction are JDBC/MX resources pools, the WebLogic Server transaction manager does not write a transaction log during the commit processing. This provides better performance and reliability as the transaction log is protected with TMF audit trails. The following is a sample configuration element for the JDBCConnectionPool using the wrapper drivers.
XA Resource Manager (XARM) Configuring the JDBC Connection Pools for SQL/MX KeepXAConnTillTxComplete Tells the WebLogic Server not to close the connection until the global transaction is complete. This attribute must be set in the JDBCConnectionPool for the WebLogic Server to invoke the setTransactionIsolation method. When generating primary keys using a named sequence table, the WebLogic Server sets the transaction isolation level on the JDBC connection to TRANSACTION_SERIALIZABLE.
Configuring the WebLogic Server Data Sources for SQL/MX XA Resource Manager (XARM) Properties The Properties field is useful only with the XADataSource driver. The property names and the various acceptable values are provided the following table. Property Name Description maxStatements Has the same meaning as specified in the JDBC specification. Valid value is greater than or equal to zero (>=0). Zero (0) disables statement caching.
XA Resource Manager (XARM) Additional Considerations for JDBC Access to SQL/MX DataBases To configure non-transactional data sources, a connection pool using the default JDBC driver, or the wrapper JDBC driver can be specified.
XA Resource Manager (XARM) Additional Considerations for JDBC Access to SQL/MX DataBases commit or rollback the transaction, the WebLogic Server calls the JDBC driver to perform the commit/rollback. The JDBC/MX driver ignores this request because the transaction is managed externally to the JDBC driver.
6 Pet Store Sample Application Running Pet Store Sample Application Running Pet Store Application in the Installed WebLogic Server Location Running the PointBase Form of Pet Store Running the SQL/MX Form of Pet Store Accessing Pet Store from a Web Browser Running Pet Store in Another Location Running Pet Store Sample Application Pet Store is a sample reference application that demonstrates the WebLogic Server features.
Pet Store Sample Application Running the PointBase Form of Pet Store Running the PointBase Form of Pet Store To run the PointBase form of Pet Store, use the startPetStore.sh script: ksh [128] cd $WL_HOME/samples/server/config/petstore ksh [129] . ./startPetStore.
Pet Store Sample Application Running the SQL/MX Form of Pet Store 59:# export CATSCH=’wls.petstore’ 61:# export SQLVOL=’$data10.petdb’ Then rerun Pet Store with ... . ./startPetStore_NSSQL.sh ksh [142] . ./startPetStore_NSSQL.sh Using existing settings for Pet Store sample application ... Pet Store uses SQL/MP catalog $data.user Changing catalog-schema in /usr/bea/user_projects/hpns/samples/server/config/petstore/ startPetStore_NSSQL.sh ... Dropping SQL/MX aliases for SQL/MP tables (if any) ...
Pet Store Sample Application Running the SQL/MX Form of Pet Store /usr/bea/user_projects/hpns/samples/server/stage/petstore/serverclasses: /usr/bea/user_projects/hpns/samples/server/stage/common: /usr/bea/weblogic700/server/lib/nsxarm.jar: /usr/bea/weblogic700/server/lib/wlsnsxarm.jar -Dweblogic.Name=petstoreServer -Dbea.home=/usr/bea -Dweblogic.management.username=weblogic -Dweblogic.management.password= weblogic -Dweblogic.ProductionModeEnabled= -Djava.security.
Running the SQL/MX Form of Pet Store Pet Store Sample Application Also, the scripts that control the catalog are copied to the directory where you are running the application. If you are running in the installed WebLogic Server location, this is: $BEA_HOME/user_projects/hpns/samples/server/config/petstore/schema create_petdb.sh Shell script to create and reload the NonStop SQL catalog for Pet Store. dropalias.sql Input file to mxci to drop NonStop SQL/MP aliases. dropcatalog.
Pet Store Sample Application Accessing Pet Store from a Web Browser Accessing Pet Store from a Web Browser From a web browser, view the initial Pet Store at this URL: http://machine:7001/petstore/index.jsp Figure 6-1 shows a sample Pet Store screen. Figure 6-1. Sample Pet Store Screen Running Pet Store in Another Location You might want to run Pet Store outside the WebLogic Server installation directories if: • • You are not the user who installed WebLogic Server.
Pet Store Sample Application Running Pet Store in Another Location BEA’s standard mechanism for creating a private copy of Pet Store is the Configuration Wizard, dmwiz.sh. To run this wizard on the NonStop server, see the BEA documentation on running the Wizard in Console mode. Another way to run a private copy of Pet Store is to copy existing sample files and change values in them. 1. Create your own directories samples/server, that is, directory server containing directory samples.
Pet Store Sample Application Running Pet Store in Another Location Changing petstore/startPetStore.sh Changing petstore/startPetStore_NSSQL.sh Old string = 7001 New string = 20001 Changing examples/config.xml Changing petstore/config.xml_BEA Changing petstore/config.xml_HPNS Old string = 7002 New string = 20002 Changing examples/config.xml Changing petstore/config.xml_BEA Changing petstore/config.xml_HPNS Old string = Dhp.nsk.xares.name=petstore New string = Dhp.nsk.xares.
Pet Store Sample Application Running Pet Store in Another Location other copies of Pet Store, please check the port values in /h/user/mywls/samples/server/config/petstore/config.xml : 275: 295: 324: ListenPort="20001" ListenPort="20002" Arguments="port=20001" Please check the XA resource name in /h/user/mywls/hpns/samples/server/config/petstore/schema/create_petdb.sh 72: -Dhp.nsk.xares.
Pet Store Sample Application Running Pet Store in Another Location HP NonStop Server Platform Guide for WebLogic Server —525779-001 6- 10
Glossary CIIN. A command file in the SYSnn subvolume that is read and executed by the startup HP Tandem Advanced Command Language (TACL) process after system load if the CIIN file is specified in the CONFTEXT file and enabled in the Compaq TSM client software. Guardian. An environment available for interactive or programmatic use with the HP NonStop™ Kernel operating system.
Glossary XA resource objects.
Index A AAREADME_xarm.txt file 2-12 AbandonTimeoutSeconds, JTA attribute 4-1 ABORT PROCESS command 3-6 Administration server process type 3-1 script 3-6 alterPetStore.sh script 2-14 architecture 1-3 auditfile property name 5-5 AUTORESTART generic process attribute 3-4 B BEA WebLogic Server definition 1-1 implementation 1-1 BEA WebLogic Server 7.0 SP1 installation 2-6 C CATSCH shell variable 6-5 CheckpointIntervalSeconds, JTA attribute 4-1 check-wls-hpns.
G Index G I Generic process attributes AUTORESTART 3-4 CPU 3-4 HOMETERM 3-5 NAME 3-4 OUTFILE 3-5 PRIORITY 3-4 STARTMODE 3-4 STARTUPMSG 3-5 STOPMODE 3-5 TYPE 3-5 USERID 3-5 Generic processes considerations 3-2 overview 3-1 install script example 2-8 Installation BEA WebLogic Server 7.0 SP1 2-6 delivered files 2-2 HP NonStop Server Toolkit for BEA WebLogic Server 7.
K Index K KeepXAConnTillTxComplete attribute 5-7 L libNonStopXARM.a file 2-12 Load balancing functions jvm_load 3-7 managed_load 3-7 LoadBeforeAppDeployments attribute 5-3 NonStop server-specific features HP NonStop Server Customization Kit 1-2 XA resource manager 1-1 nsxarm.jar file 2-13 O OSH process 3-2 OUTFILE generic process attribute 3-5 P M makealias.in file 2-14 makealias.
R Index Property names (continued) tracefile 5-5 R README.txt file 2-2, 2-13 S Sample shell scripts nodemanager.sh 3-7 overview 3-5 startgp.sh 3-5 stopgp.sh 3-6 Scripts administration server script 3-6 alterPetStore.sh 2-14 check-wls-hpns.sh 2-2, 2-13 cleanPetStore.sh 2-14 create_petdb.sh 2-14, 6-5 first.sh 2-13 for Pet Store 6-5 install-nsxarm.sh 2-2, 2-12 install-wls-hpns.sh 2-3, 2-7, 2-13 mcast_test.sh 2-13 node manager script 3-6 nodemanager.sh 2-13 startgp.sh 2-13 startPetStore.
W Index W weblogic700sp1_hpns_supp.jar file 2-13 weblogic.Admin utility 3-8 whichPetStore.sh script 2-14, 6-1 WLSNonStopTxHelper 5-3 WLSNonStopTxHelper startup class 5-2 wlsnsxarm.jar file 2-13 wls-silent-default.
X Index HP NonStop Server Platform Guide for WebLogic Server —525779-001 Index -6
