NonStop Server Guide for BEA WebLogic Server 9.2

HP NonStop Server Guide for BEA WebLogic Server 9.2—529891-002
9-1
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.
Running MedRec Application in the Installed WebLogic Server
Location
The easiest place to run MedRec is in the installed location which, by default, is
/usr/bea/weblogic92. However, running MedRec in the installed location changes
files in the installed directories, which can cause problems for other users who want to
run private copies of MedRec. Also, you need write access to the installation
directories.
Before you run MedRec or other applications with WebLogic Server, ensure that the
NonStop server is using the correct software prerequisites and your shell environment
has correct values.
Note that the MedRec sample application accesses the internet. If your server requires
a proxy to access the internet, edit the startMedRecServer_sqlmx.sh command
procedure to set -Dhttp.proxyHost, -Dhttp.proxyPort, and
-Dhttp.nonProxyHosts.
Set and export environment variables for use of NonStop Server for Java 5.0 and
NonStop TCP/IPv6. For example:
ksh [125] export JAVA_HOME=/usr/tandem/java
ksh [126] export PATH=$JAVA_HOME/bin:$PATH
ksh [127] export WL_HOME=/usr/bea/weblogic92
ksh [128] add_define =PTCPIP^FILTER^KEY class=map file=mykey
If your NonStop TCP/IPv6 process is not named $ZTC0, create a define so that
WebLogic Servers started by this shell use NonStop TCP/IPv6. For example:
ksh [129] add_define =TCPIP^PROCESS^NAME class=map file=\$ZSM1
It is recommended that you save these commands in a file, such as .profile.