Before starting tlisten, you must set the
tlisten environment variable
SHLIB_PATH/LIBPATH/LD_LIBRARY_PATH and include the
libjvm library path. For windows platforms, you only need to set
JAVA_HOME. For HP platforms, you need to set
LD_PRELOAD to include the
libjvm.so directory.
Listing 1 shows examples of environment variable settings on different platforms:
|
Note:
|
LD_PRELOAD is only used for tlisten to start embedded JMX agent. It should not be set when building Tuxedo applications.
|
To start tlisten, use the following command:
When the tlisten process is started correctly, you can view the message “
RMI connector server successfully started and
Started the embedded JMX agent successfully” in ULOG.
jmxaddr specifies the address of RMI connector of embedded JMX agent. If the address has been occupied by another process, an error message is printed into ULOG and JMX agent fails to start up.
Table 1 lists the
jmxaddr adress formats.
|
•
|
tlisten acts as the Tuxedo-side monitoring and management agent . It receives monitoring and management requests from Enterprise Manager and dispatches these requests to corresponding Tuxedo services.
|
|
•
|
tlisten creates a Tuxedo context for each JMX connection. If a monitored Tuxedo domain enables authentication and authorization, tlisten provides the credentials attained from Enterprise Repository when it attaches a Tuxedo domain.
|
|
•
|
tlisten also forwards job requests from Enterprise Repository agent to MIB service. Enterprise Repository agent creates a new JMX connection for every job request, and releases the connection after the job finishes. Accordingly, tlisten creates a Tuxedo context for each job request.
|
Listing 2 shows an SHM mode
UBBCONFIG file example supporting Enterprise Manager monitoring.
|
3.
|
Click Middleware Features > Tuxedo Summary.
|
|
•
|
Hostname: Mandatory parameter. Specifies the host where the Tuxedo domain master machine is running.
|
|
•
|
Port: Mandatory parameter. The port number specified by tlisten -j option.
|
|
•
|
Application Password: Optional parameter. Specifies the Tuxedo application password Enterprise Manager agent uses to connect to the Tuxedo domain. You must input this parameter if the Tuxedo domain SECURITY value is one of following: APP_PW, USER_AUTH, ACL, or MANDATORY_ACL; otherwise, leave the field blank.
|
|
•
|
User name: Optional parameter. Specifies the Tuxedo user name Enterprise Manager agent uses to connect to the Tuxedo domain. You must input this parameter if the Tuxedo domain SECURITY value is one of following: USER_AUTH, ACL, or MANDATORY_ACL; otherwise, leave the field blank.
|
|
•
|
User Password: Optional parameter. Specifies the Tuxedo user password Enterprise Manager agent uses to connect to the Tuxedo domain. You need to input this parameter if the Tuxedo domain SECURITY value is one of following: USER_AUTH, ACL, or MANDATORY_ACL; otherwise, leave the field blank.
|
|
•
|
Use SSL: Optional. This option refers to SSL mechanism between Enterprise Manager and JMX agent in the tlisten process.
|
|
•
|
With Tuxedo Authentication: If this box is unchecked, Tuxedo security related information is ignored and only tlisten and the Tuxedo Home targets are discovered. Leave this box checked if you want to discover the Tuxedo domains monitored by the tlisten process.
|
|
•
|
Monitoring Agent: Mandatory option. It is recommended you select the one residing on the same physical machine with tlisten.
|
If only one domain is being monitored by tlisten, you will get a list of discovered targets; otherwise, select the domain on the page that appears and enter the parameters specific to the domain, then click
Discover Now again.
|
3.
|
Click Add Targets Manually >Add Non-Host Targets by Specifying Target Monitoring Properties.
|
If the SECURITY parameter of the Tuxedo domain is
APP_PW, Enterprise Manager agents provide a Tuxedo application password for authentication. If the
SECURITY parameter is
USR_AUTH,
ACL or
MANDATORY_ACL, Enterprise Manager agents provide application password, user name, and user password for authentication; meanwhile,
AUTHSVR must be configured in the
UBBCONFIG file.
Solution: you should run manual discovery again if this scenario occurs.
tlisten startup options provide keystore location/password to enable SSL.
|
•
|
Reboot tlisten after keystore change if tlisten is active.
|
|
•
|
The trust store given by javax.net.ssl.trustStore, if such option is set in the WLS startup script, startWebLogic.sh, or WLS startup system property.
|
Where, $MW_HOME is the Oracle Enterprise Manager installation directory.
|
Note:
|
The default password for $MW_HOME/jdk16/jdk/jre/lib/security/jssecacerts and $MW_HOME/jdk16/jdk/jre/lib/security/cacerts is changeit.
|
If AgentTrust.jks exists, you should import your public key into
AgentTrust.jks; otherwise, copy
TuxedoTrust.jks to
$ORACLE_HOME /sysman/config/montrust/ and rename it to
AgentTrust.jks.
|
•
|
tuxedo is the CA certificate alias
|
|
4.
|
Reboot tlisten/EM Agent/OMS after keystore/ trustore is changed
|
Figure 1 shows a typical Enterprise Manager for Oracle Tuxedo deployment scenario.
Figure 2 shows a scenario where Enterprise Repository agent is monitoring Tuxedo domains remotely. This deployment topology is useful for platforms supported by Tuxedo rather than by Enterprise Repository agent.
|
•
|
Security: Each tlisten process starts as a different user with different privileges.
|
Figure 3 shows how to deploy multiple
tlisten processes on a physical machine. Please note that each
tlisten process is able to interconnect with different Enterprise Repository agents respectively, no matter if it is running locally or remotely.
A tlisten process with JMX agent embedded is able to interconnect with multiple Enterprise Repository agents concurrently.
Figure 4 shows a
tlisten process running on "Machine 2" is connected and monitored by "EnterpriseManager Agent 1" and "EnterpriseManager Agent 2" concurrently.
