HP NonStop Server Guide for BEA WebLogic Server 9.2 Abstract This manual describes the installation, configuration, and management of the BEA WebLogic Server on HP Integrity NonStop™ NS-series servers. Product Version HP Integrity NonStop Server Toolkit for BEA WebLogic® Server 9.2 Supported Release Version Updates (RVUs) This publication supports H06.10 and all subsequent H-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 529891-001 HP Integrity NonStop Server Toolkit for BEA WebLogic Server 8.1 July 2005 529891-002 HP Integrity NonStop Server Toolkit for BEA WebLogic Server 9.
Legal Notices Copyright 2008 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop Server Guide for BEA WebLogic Server 9.2 Glossary Index Examples Figures Legal Notices What’s New in This Manual v Manual Information v New and Changed Information Legal Notice v v About This Manual vii Who Should Read This Manual vii Organization of This Manual viii Related Documentation viii Notation Conventions ix 1.
4. Configuring Persistent WebLogic Server Processes (continued) Contents 4. Configuring Persistent WebLogic Server Processes (continued) startgp.sh 4-6 startgp.tacl 4-6 Scripts to Start the WebLogic Server Process 4-6 stopgp.sh and stopgp.tacl 4-8 Using the Node Manager on the NonStop Server 4-8 Starting a Managed Server Through the Node Manager 4-9 nodemanager.sh 4-9 CPUselector 4-10 gname_load 4-11 jvm_load 4-11 managed_load 4-11 no_load 4-12 Configuring the Node Manager 4-12 Settings 4-12 Step 1.
8. Managing SQL/MX Tables for BLOB and CLOB Data Contents 8. Managing SQL/MX Tables for BLOB and CLOB Data Creating SQL/MX Tables 8-1 Providing Properties to the JDBC Driver 8-1 9. Sample Application WebLogic Server Sample Application 9-1 Running MedRec Application in the Installed WebLogic Server Location Running MedRec in Another Location 9-5 9-1 A. Script Options Usage check-wl-hpns.sh A-1 install-wl-hpns.sh A-2 uninstall-wl-hpns.sh A-3 Glossary Index Examples Example 4-1.
Contents HP NonStop Server Guide for BEA WebLogic Server 9.
What’s New in This Manual Manual Information HP NonStop Server Guide for BEA WebLogic Server 9.2 Abstract This manual describes the installation, configuration, and management of the BEA WebLogic Server on HP Integrity NonStop™ NS-series servers. Product Version HP Integrity NonStop Server Toolkit for BEA WebLogic® Server 9.2 Supported Release Version Updates (RVUs) This publication supports H06.10 and all subsequent H-series RVUs until otherwise indicated by its replacement publication.
What’s New in This Manual HP NonStop Server Guide for BEA WebLogic Server 9.
About This Manual This manual describes: • • • • • The BEA WebLogic Server for the HP Integrity NonStop NS-series servers. Installation of the BEA WebLogic Server 9.2 on HP NonStop servers. Possible configurations. The XA Resource Manager. Avitek Medical Records (or MedRec) sample application suite that is run with WebLogic Server. Who Should Read This Manual This manual is intended for users who want to: • • install and set up the WebLogic Server. administer the WebLogic Server after installation.
Organization of This Manual About This Manual Organization of This Manual Section Description Section 1, Introduction Describes the WebLogic Server features and enhancements on the NonStop server platform. Section 2, Installation Provides the URL for the installation instructions. Section 3, Migration Discusses migration from WebLogic Server 8.1 SP3 on the MIPs platform (TNS/R) or WebLogic Server 8.1 SP3 ® Itanium® Processor based platform (TNS/E) to WebLogic Server 9.
Notation Conventions About This Manual • • • • NonStop SQL/MX documentation, located at docs.hp.com iTP WebServer documentation, located at docs.hp.com SQL/MX Comparison Guide for SQL/MP Users, located at docs.hp.com Java documentation, located at docs.hp.com Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described.
Change Bar Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
1 Introduction This section describes the WebLogic Server features and enhancements on the NonStop server platform: • • • • • • The WebLogic Server for the HP NonStop Server on page 1-1 Server-Specific Features on page 1-2 Enhancements on page 1-2 Native Socket Multiplexer on page 1-3 High Level Architecture on page 1-6 SMP Systems and HP NonStop Servers on page 1-7 The WebLogic Server for the HP NonStop Server The WebLogic Server is a standards-based J2EE application server that provides a foundation
Server-Specific Features Introduction Server-Specific Features HP provides certain NonStop server-specific features to the WebLogic Server: • • • • An XA resource manager for the NonStop Transaction Management Facility (TMF) facility so that NonStop server resources can participate in global transactions coordinated by the WebLogic Server transaction managers. For more information, see Section 6, XA Resource Manager (XARM). A NonStop Server Toolkit for BEA WebLogic Server 9.
Native Socket Multiplexer Introduction • WebLogic Server 9.2 is available for the NonStop Server and depends on Java Standard Edition Version 1.5.0_02. The NonStop Server for Java 1.5 has been updated to conform to this. For more information, see Java documentation. Native Socket Multiplexer The WebLogic Server allows two mechanisms for network socket I/O: • • a pure Java socket reader implementation, and a platform-optimized native socket multiplexer.
Native Socket Multiplexer Introduction . Figure 1-1. Socket Reader Polling SR1 SR2 SR3 SP1 SP2 SP3 SP4 SP5 SP6 VST003.vsd Another aspect of the Java socket multiplexer implementation that impacts the overall performance of the WebLogic Server application is the kernel execute queue. The kernel execute queue is configured with threads that perform server internal functions and application request processing.
Native Socket Multiplexer Introduction . Figure 1-2. Single Thread Polling Native Socket Reader Thread N1 SP1 SP2 SP3 SP4 SP5 SP6 VST004.vsd Another advantage of the native socket implementation is the usage of the kernel execute queue. Unlike the pure Java multiplexer, the native socket polling threads are managed using a separate execute queue distinct from the default kernel queue.
High Level Architecture Introduction 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.
SMP Systems and HP NonStop Servers Introduction SMP Systems and HP NonStop Servers A WebLogic Server domain deployment on a traditional SMP system is presented in Figure 1-4. The Administrative Server, Managed Servers (part of a cluster), Managed Servers (independent of clusters), and Node Manager run on a single SMP machine. The threads of all Java Virtual Machine (JVM) instances can be scheduled on all the available processors. Fault tolerance is not built into SMP systems.
SMP Systems and HP NonStop Servers Introduction Figure 1-5. WebLogic Server Domain Representation on a NonStop Server Administrative Server CPU 0 Managed Server (independent of cluster) Managed Server (part of a cluster) CPU 1 Node Manager Managed Server (part of a cluster) CPU 2 Managed Server (independent of cluster) Managed Server (part of a cluster) CPU 3 Managed Server (part of a cluster) VST002.vsd The WebLogic Server instances are coupled and distributed across all the available CPUs.
2 Installation For information on how to install the BEA WebLogic Server 9.2 on HP NonStop servers, go to: www.hp.com/go/nonstop/wls92 HP NonStop Server Guide for BEA WebLogic Server 9.
Installation HP NonStop Server Guide for BEA WebLogic Server 9.
3 Migration There are no application changes required to migrate from WebLogic Server 8.1 SP3 on the MIPs platform (TNS/R) to WebLogic Server 9.2 on the Itanium® based NonStop servers (TNS/E). For general migration information, see H-Series Application Migration Guide. HP NonStop Server Guide for BEA WebLogic Server 9.
Migration HP NonStop Server Guide for BEA WebLogic Server 9.
4 Configuring Persistent WebLogic Server Processes • • • • • • Overview of Generic Processes on page 4-2 Considerations on page 4-3 ° ° ° ° Configuration on page 4-3 Automatic Restart on page 4-3 Sample Scripts on page 4-3 Managed Servers on page 4-4 Generic Process Attributes on page 4-4 Sample Shell Scripts and TACL Macros on page 4-6 ° ° ° ° startgp.sh on page 4-6 startgp.tacl on page 4-6 Scripts to Start the WebLogic Server Process on page 4-6 stopgp.sh and stopgp.
Configuring Persistent WebLogic Server Processes • • ° ° ° Overview of Generic Processes Step 5. Start Managed Servers Using the Node Manager on page 4-15 Step 6.
Configuring Persistent WebLogic Server Processes Considerations Considerations Configuration Only a member of the SUPER group can configure and start a generic process even though the process can run as any user ID. For security reasons, the WebLogic Server administrator user ID is not typically a member of the SUPER group.
Configuring Persistent WebLogic Server Processes • Managed Servers The scripts should avoid calling “sleep” for any significant period of time unless you modify the AUTORESTART parameter of the generic process to reflect the delay. For example, if a script delays for a failed start attempt of the generic process that takes two minutes, the generic process will continually restart the generic process.
Configuring Persistent WebLogic Server Processes Generic Process Attributes Table 4-1. Generic Process Attributes Table Attribute Consideration AUTORESTART A setting of 0 means the process will not be persistent. The sample scripts set the value to 10 to allow up to ten failures in 10 minutes. Reducing this value might help avoid hitting an infinite restart loop. CPU Use FIRSTOF to allow the process to run in a list of available CPUs.
Configuring Persistent WebLogic Server Processes Sample Shell Scripts and TACL Macros Sample Shell Scripts and TACL Macros Configuring a generic process requires using SCF, the Guardian command interpreter. Commands must be run by a member of the SUPER group. Four sample files are provided for the NonStop server. These sample files are: startgp.sh, startgp.tacl, stopgp.sh, and stopgp.tacl. Two of the scripts are Korn shell scripts and the other two are TACL macros.
Configuring Persistent WebLogic Server Processes Scripts to Start the WebLogic Server Process run -name=/G/adsvr ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${ADMIN_SERVER} -Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy" -Dweblogic.management.username=${WLS_USER} -Dweblogic.management.password=${WLS_PW} weblogic.
Configuring Persistent WebLogic Server Processes stopgp.sh and stopgp.tacl stopgp.sh and stopgp.tacl The script and macro have one required argument, the generic process name, and an optional delete argument if the generic process entry should be deleted. The script and macro attempt to run an ABORT PROCESS command to cause the generic process to stop. Because the process being stopped is the OSH process, running the ABORT PROCESS command does not cause the WebLogic Server process to stop.
Configuring Persistent WebLogic Server Processes Starting a Managed Server Through the Node Manager status of a Managed Server as FAILED_MIGRATABLE. In this case, restart the server using the console or weblogic.Admin utility. Starting a Managed Server Through the Node Manager When NativeVersionEnabled is set to false as required on the NonStop server, the Node Manager uses a shell script to start a Managed Server. By default that script is named nodemanager.
Configuring Persistent WebLogic Server Processes CPUselector current working directory. By default, the server environment file is named nmserver.env and must be located in $WL_HOME/common/nodemanager but both values can be changed in the nodemanager.sh script. If the file is present, the script invokes the file (for example, .nm-server.env). The script can then use the variable WLS_SERVER to selectively set the environment variables to be used by CPUselector. Example 4-1.
Configuring Persistent WebLogic Server Processes gname_load The variable WLS_LOADBAL_FUNC determines the load-balancing algorithm used to compute the loads. The next section describes how each load-balancing function computes the current load. The sections also identify the files and environment variables that are used. gname_load gname_load uses Guardian process names to calculate the current load.
Configuring Persistent WebLogic Server Processes no_load of processes being monitored is maintained in: "./NodeManagerLogs/NodeManagerInternal/MonitorProcessList" by default. The pid files are located in directories under "./NodeManagerLogs" with names of the form domain_server. The addition of WLS_CPUS helps the managed_load algorithm because different Managed Servers can specify a different CPU ordering. This feature helps in a multistart case because no servers will have started.
Configuring Persistent WebLogic Server Processes Step 1. Create a Machine and Associate Servers to it Step 1. Create a Machine and Associate Servers to it 1. Start an admin server for your domain: . ./my_env (loading your usual WL_HOME, JAVA_HOME, and so on) cd $WL_HOME/../user_projects/domains/rldomain ./startWebLogic.sh Access the GUI. For example: http://icebat4.txn.cpqcorp.net:7001/console 2. On the left pane: a. Click Machine folder. b. Click Configure a New unix Machine. c. Enter the machine name.
Configuring Persistent WebLogic Server Processes Step 4. Configure Managed Servers Startup Options 2. Edit nodemanager.properties to add: NativeVersionEnabled=false ReverseDnsEnabled=true PIDFileReadRetryCount=1 ScavangerDelaySeconds=300 3. Edit nodemanager.hosts to add the server where the admin resides: icebat4.txn.cpqcorp.net 4. Start the Node Manager: $WL_HOME/server/bin/startNodeManager.sh 5. In the output, check that new values for the properties are set. Step 4.
Configuring Persistent WebLogic Server Processes Step 5. Start Managed Servers Using the Node Manager Step 5. Start Managed Servers Using the Node Manager 1. From the Admin console GUI: a. Select a server and click Control tab. b. Click Start this server. 2. From the command line enter: .$WL_HOME/server/bin/setWLSEnv.sh java weblogic.Admin -url icebat4:7001 -username webogic -password weblogic START rlserver1 Step 6.
Configuring Persistent WebLogic Server Processes Starting the Node Manager from a Non-Default Location demo certificates, However, in this sample we have used successfully both true and false settings: rlserver 1: GUI, configuration, Keystore & SSL, Advanced option: "Hostname Verification = BEA Hostname Verifier" This means weblogic.security.SSL.ignoreHostnameVerification = false. rlserver 2: GUI, configuration, Keystore & SSL, Advanced option: "Hostname Verification = none" This means weblogic.security.
Configuring Persistent WebLogic Server Processes Shutting Down a WebLogic Server Application ./nodemanger.sh is used, which translates to $WL_HOME/server/lib/unix/nodemanager.sh. The nodemanager.sh script assumes CPUselector is in $WL_HOME/server/lib/unix as well by setting the variable DFLT_CPUSELECTOR to $WL_HOME/server/lib/unix/CPUselector. Change either the StartTemplate and/or nodemanager.sh as appropriate. For example, changing only StartTemplate changes the location where the nodemanager.
Configuring Persistent WebLogic Server Processes Shutting Down a WebLogic Server Application HP NonStop Server Guide for BEA WebLogic Server 9.
5 Configuring JTA Java™ Transaction API (JTA) elements of the configuration describe several attributes for controlling the WebLogic Server Transaction Manager. The JTA attributes can be changed if the TMF configuration is different for your application. This is an example highlighting some NonStop server-specific changes.
Configuring JTA HP NonStop Server Guide for BEA WebLogic Server 9.
6 XA Resource Manager (XARM) The XA Resource Manager (XARM) for the HP NonStop server is a software component specifically written for and tested with the BEA WebLogic Server. It is written in C and Java and implements the Java XA resource interface as defined in the Java™ Transaction API (JTA) specification.
XA Resource Manager (XARM) Configuring the WebLogic Server XA Resource Object XAConnection interfaces. Because of this, a JDBC/MX wrapper driver has been provided to support the XADataSource and XAConnection interfaces. The associated XA resource is a dummy resource because it ignores all the XA requests from the WebLogic Server transaction manager. This satisfies the WebLogic Server requirement that JDBC/MX be XA-aware.
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 LoadBeforeAppDeployments Determines whether a startup class is loaded and run before the server creates JMS and JDBC services or deploys applications and EJBs. If you specify true for this option, the server loads and runs the class before the prepare() phase in the 2phase deployment model. At this point, JMS and JDBC services are not yet available, and no applications or EJBs have been deployed.
XA Resource Manager (XARM) Configuring JDBC Connection Pools for SQL/MX Table 6-1. Java System Properties used by WLSNonStopTxHelper (continued) Property Name used in Property File Name when Specified with the -D Java Command Line Option maxthreads hp.nsk.xares.maxthreads Specifies the maximum number of threads that can concurrently take part in a transaction.
XA Resource Manager (XARM) Configuring JDBC Connection Pools for SQL/MX A wrapper driver has been written for JDBC/MX. The wrapper driver does not perform transaction management, but implements the XA interface. The XA resource implemented by JDBC/MX responds with XA_RDONLY, implying that no change was done to the underlying resource. The static XA resource manager protects changes to resources managed by JDBC/MX.
XA Resource Manager (XARM) Configuring 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.
7 Configuring JDBC Stores for JMS The WebLogic Java Messaging Service (JMS) Server can be configured to use a JMS JDBC store when the underlying JDBC connection pool uses NonStop SQL/MX 2.2 with ANSI tables as the database. The JMS database contains two system tables (generically called JMSState and JMSStore) that are generated automatically and are used internally by each JMS server.
Configuring JDBC Stores for JMS JdbcMxLobAdmin utility to create these triggers. The JDBC Driver for SQL/MX Programmer’s Reference Manual describes how to do this. Note. You cannot configure a transaction (XA) JDBC connection pool or JDBC TxDataSource to use with a JMS JDBC store. JMS must use a JDBC connection pool that uses a non-TxDataSource with a non-XAResource driver. For more information, see Section 8, Managing SQL/MX Tables for BLOB and CLOB Data.
8 Managing SQL/MX Tables for BLOB and CLOB Data • Creating SQL/MX Tables on page 8-1 ° Providing Properties to the JDBC Driver on page 8-1 Creating SQL/MX Tables WebLogic Server uses Large Objects (LOBs) in its application. LOBs are stored by SQL/MX in a special manner and can only be accessed by configuring a JDBC Connection Pool to use either the com.tandem.sqlmx.SQLMXDriver driver or the com.hp.nsk.xares.WLSTxSQLMXDataSource driver. See Configuring JDBC Connection Pools for SQL/MX in Section 6.
Managing SQL/MX Tables for BLOB and CLOB Data Providing Properties to the JDBC Driver HP NonStop Server Guide for BEA WebLogic Server 9.
9 • Sample Application WebLogic Server Sample Application on page 9-1 ° Running MedRec Application in the Installed WebLogic Server Location on page 9-1 ° ° Accessing MedRec from a Web Browser on page 9-3 Running MedRec in Another Location on page 9-5 WebLogic Server Sample Application MedRec is a sample reference application that demonstrates the BEA WebLogic Server features. For NonStop SQL/MX Version 2.2 Native Tables, the SQL/MX directory is medrec_sqlmx2.
Sample Application Running MedRec Application in the Installed WebLogic Server Location The prerequisite software and shell environment can be checked using the same script run during the installation. For example: ksh [130] $WL_HOME/server/lib/hpns/check-wl-hpns.sh To run MedRec in directories outside the installed WebLogic Server location, see Running MedRec in Another Location.
Running MedRec Application in the Installed WebLogic Server Location Sample Application The NonStop SQL catalog is created and populated the first time you start this sample application and the catalog name is put into files you can use to control the catalog. Subsequent starts of MedRec will keep the same catalog data. Also, the scripts that control the catalog are available in the directory db where you are running the application.
Running MedRec Application in the Installed WebLogic Server Location Sample Application Figure 9-1. Initial MedRec Screen HP NonStop Server Guide for BEA WebLogic Server 9.
Running MedRec in Another Location Sample Application Figure 9-2. MedRec Logon Screen Running MedRec in Another Location You might want to run MedRec outside the WebLogic Server installation directories if: • • you are not the user who installed WebLogic Server. you want to keep a clean set of MedRec files in the installed location so that other users can copy them for their private use. The standard mechanism for creating a private copy of MedRec is the Configuration Wizard, config.sh.
Running MedRec in Another Location Sample Application 2. Copy the medrec_sqlmx2 directory from the installed WebLogic Server samples to the directory you just created. For example: ksh [148] export WL_HOME=/usr/bea/weblogic92 ksh [150] cp -rp $WL_HOME/samples/domains/medrec_sqlmx2/* $MYMEDREC 3. Remove files that might be left over after MedRec was run in the installed WebLogic Server location. These files might interfere with the operation of your private copy of MedRec. The cleanMedRec_sqlmx.
Sample Application Running MedRec in Another Location Additional documentation for using MedRec with BEA WebLogic Server 9.2, including procedures for stopping the application, is available at http://e-docs.bea.com/wls/docs92/server_start/startquickref.html HP NonStop Server Guide for BEA WebLogic Server 9.
Sample Application Running MedRec in Another Location HP NonStop Server Guide for BEA WebLogic Server 9.
A Script Options Usage Script options are as follows: check-wl-hpns.sh check-wl-hpns.sh [-h] [-verbose] [-version} [-prereq] [-envonly] [-all] [-[no]java] [-[no]jdbc] [-[no]mx] [-[no]multicast] [-[no]os][-[no]qio] [-[no]tcpip] [-[no]userid] [-[no]weblogic]] -h Gives long help text. -all Checks all prerequisites including userid and multicast. -verbose Verbose mode. The default is non-verbose. -version Displays the version of the HP NonStop Server Toolkit. -prereq Reports prerequisite software.
Script Options Usage install-wl-hpns.sh -os Checks the version of the operating system. -tcpip Checks the TCP/IP. -userid Checks that the user ID for the OSS alias has an initial-directory. -weblogic Checks the installed WebLogic directory. The default is all tests except -multicast and -userid. The shell environment variables JAVA_HOME and WL_HOME must be exported before running this script. You might also want to export the JDBCMX_DIR variable. install-wl-hpns.sh install-wl-hpns.
Script Options Usage uninstall-wl-hpns.sh The shell environment variables JAVA_HOME and WL_HOME must be exported before running this script. You might also want to export the JDBCMX_DIR variable when it is not in its standard location. uninstall-wl-hpns.sh uninstall-wl-hpns.sh [-h] [-all] -h Gives long help text. -all Restores the WebLogic Server directories to the original BEA files. Removes the backup files and _HPNS* files.
Script Options Usage HP NonStop Server Guide for BEA WebLogic Server 9.2— 529891-002 A- 4 uninstall-wl-hpns.
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 OSM or TSM Low-Level Link. Guardian. An environment available for interactive or programmatic use with the HP NonStop™ operating system.
Glossary WLSNonStopTxHelper. WLSNonStopTxHelper. The startup class that has to be configured for every server in the domain. XA Resource Manager. The XA Resource Manager (XARM) for the NonStop server is a software component written in C and Java that implements the Java XA resource interface. XA resource objects. Objects that implement the XA resource interface. HP NonStop Server Guide for BEA WebLogic Server 9.
Index A AbandonTimeoutSeconds, JTA attribute 5-1 ABORT PROCESS command 4-8 Administration Server process type 4-2 script 4-6 alterMedRec.sh script 9-6 architecture 1-6 ASSOCPROC generic process attribute 4-5 auditfile property name 6-5 AUTORESTART generic process attribute 4-5 Configuring JDBC connection pools for SQL/MX 6-5 JDBC data sources for SQL/MX 6-8 JMS 7-1 JTA 5-1 NonStop server XA resource object 6-2 startup classes 6-3 config.
F Index Environment variables (continued) XARM_SYSLOG 6-3 execute queue 1-4, 1-5 F file store, creating 7-1 flag property name 6-4 G Generic process attributes ASSOCPROC 4-5 AUTORESTART 4-5 CPU 4-5 HOMETERM 4-5 NAME 4-5 OUTFILE 4-5 PRIORITY 4-5 STARTMODE 4-5 STARTUPMSG 4-5 STOPMODE 4-5 TYPE 4-5 USERID 4-5 Generic processes considerations 4-3 overview 4-2 gname_load function 4-11 H HOMETERM generic process attribute 4-5 hp.nsk.xares.auditfile, Java system property 6-5 hp.nsk.xares.
L Index L Large Objects 8-1 Load balancing CPUselector program 4-9, 4-10 gname_load function 4-11 jvm_load function 4-11 Load balancing managed_load function 4-11 no_load function 4-12 LoadBeforeAppActivation attribute 6-3 LoadBeforeAppDeployments attribute 6-4 LOBs 8-1 M Managed Server process type 4-2 managed_load function 4-11 maxPoolsize property name 6-8 maxStatements property name 6-8 maxthreads property name 6-5 maxtrans property name 6-4 MaxTransaction, JTA attribute 5-1 MedRec creating a private
R Index R RollbackLocalTxUponConnClose attribute 6-7 S Sample application, MedRec 9-1 Sample shell scripts overview 4-6 startgp.sh 4-6 stopgp.sh 4-8 Scripts Administration Server script 4-6 alterMedRec.sh 9-6 check-wl-hpns.sh A-1 cleanMedRec.sh 9-6 install-wl-hpns.sh A-2 Node Manager script 4-7 nodemanager.sh 4-9 startMedRecServer_NSSQL.sh 9-2 to start the WLS process 4-6 uninstall-wl-hpns.sh A-3 server root directory 6-2 ServerStart element 6-2 Shell variables for create_medrecdb.
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.
