This chapter contains the following topics:
Before you can use Oracle Tuxedo, you must configure it using a DCL script. This script must be run each time the machine is rebooted. The Oracle Tuxedo system administrator may put the DCL script into the start-up environment so that when the machine is rebooted the script will be executed.
Use the following procedure to remove Oracle Tuxedo from a machine.
Note: | This procedure removes all the files and directories under the Oracle Tuxedo installation directory. It does not remove temporary files, which are not part of the Core package and may have been created after installation. Temporary files may have to be removed manually using the delete command. |
dest_dir.bin
directory, where dest_dir
is the directory you specified during installation.Note: | Uninstall Oracle Tuxedo after the vps_daemon has stopped. Uninstall procedure will remove all files installed, including files changed after installation. For example: |
Note: | SYSREGIIOP.RDP SYSREGTGIOP.RDP SYSTEM.RDP TLISTEN.PW RM WEBGUI.INI SNMP.INI vps_init.txt |
Before using Apache Non-commerce Server for OpenVMS with Oracle Tuxedo, you must configure certain directories and their URL mappings.
Suppose Apache Non-Commerce Server is already installed on your system.
Because it will run the TUXADM.EXE
cgi-bin script, the Web server must have access to the relevant logical names. If Oracle Tuxedo is installed as SYSTEM, then no further configuration is necessary. However, if Oracle Tuxedo is installed in a specific group, then Apache Non-commerce Server must run under the same group. Otherwise, Apache Non-commerce Server will not have the proper variables set up in its environment.
You must do the following steps:
DocumentRoot
value with the name of the directory where the file webguitop.html is located. In a standard Oracle Tuxedo installation, this is '/tuxroot/udataobj/webgui
'.
Add alias '/java' to the local directory, '/tuxroot/udataobj/webgui/java
', and set attributes to this directory.
Add script alias 'CGI-BIN' to the local directory, '/tuxroot/bin
', and set attributes to this directory.
The following example will show you how to set up the Web console application.
Suppose Oracle Tuxedo is installed on DKA100:[TUXEDO].
Before you begin, make sure that:
Run APACHE$MENU.COM
. The Apache menu appears as follows:
1. Configure the Secure Web Server
5. Run OpenSSL Certificate tool
6. Convert directory tree to Stream_LF
7. Start up an Apache instance
8. Shut down an Apache instance
9. Show status of an Apache instance
10. Add a node to CSWS in a cluster environment
Select option 9 to show the existing Apache instances:
Registered Apache Instances
1. SWS APACHE$COMMON:[CONF]HTTPD.CONF
2. csws sys$sysdevice:[APACHE$WWW.CONF]httpd.conf
3. Exit
For example, select the first instance to deploy the Tuxedo Web console application as follows:
Modify APACHE$COMMON:[CONF]HTTPD.CONF
Replace DocumentRoot value
Original:
DocumentRoot "/apache$root/htdocs"
<Directory "/apache$root/htdocs">
…
</Directory>
New:
DocumentRoot "/tuxroot/udataobj/webgui"
<Directory "/tuxroot/udataobj/webgui">
…
</Directory>
Add alias '/java'
Alias /java "/tuxroot/udataobj/webgui/java/"
<Directory "/tuxroot/udataobj/webgui/java">
Options Indexes
AllowOverride None
Order allow,deny
Allow from all
</Directory>
Add scriptalias 'CGI-BIN'
ScriptAlias /CGI-BIN/ "/tuxroot/bin/"
<Directory "/tuxroot/bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
The Tuxedo web console application is now ready.
For this release please note the following considerations:
The link qualifier "/THREADS_ENABLE
" is required to build multi-threaded Oracle Tuxedo applications. Applications built without /THREADS_ENABLE
may be unreliable or have unexpected behavior. Single threaded Oracle Tuxedo applications do not use this qualifier.
In multi-threaded Oracle Tuxedo applications, each thread has its own mailbox to communicate with other processes. In order to accelerate receiving messages, four requests are queued in each mailboxes. This means that every thread requires four BIOs.
Note: | When BIOLM quota is exhausted, the process is in RWINS state. BIOLM size should be at least greater than 4 times the number of threads in process. |
Oracle Tuxedo for OpenVMS only supports the static XA switch MQRMIXASwitch
.
In certain cases, setting tcpnodelack
can improve network performance. Do the following steps:
Buildmqadapter
does not support the XCBINDIR
environment variable. the binary is created in the local directory if the '-o
' option not supplied.
If MAXSERVICES
value is very large and requires a heap size that exceeds the system-defined heap size, some servers cannot boot. In order to support maximum MAXSERVICES
value 1048575
, please modify the sysgen pql_mpgflquo
parameter to 740,000
.
The tpusr.da
t file is required for AUTHSVR.
All environment variable values must be in upper case.
By default, the maximum allowable size of any single event is 64K bytes. It can be changed using the VPS_MAX_PAGES_PER_IO
environment variable setting as follows:
Maximum size = (512*VPS_MAX_PAGES_PER_IO)
.
According to OpenVMS documentation, the logical and symbol length range is [1,255]
.
Oracle Tuxedo applications register tpterm()
to be called during normal process termination. In multi-threaded processes, DECthreads
provides a special thread to execute this routine. Because the default stack size is less than tpterm()
requires, stack overflow occurs.
To resolve this issue, apply patch VMS831H1I_PTHREAD-V0200
.
When the TMTRACE
environment variable is set, the application crashes due to a c compiler issue. When /pointer=long=argv
is specified, argv
is not always NULL
terminated.
To resolve this issue, use c compiler v.7.3, and rebuild the application. Otherwise do not set TMTRACE
.
If you compile a dynamic library with a warning message, dlopen
fails and displays a “key not found” error message. To resolve this issue, apply patch VMS831H1I_LIBRTL-V0100
.