Deploying Enterprise Manager for Oracle Tuxedo

This chapter describes how to perform initial installation tasks and deploy your Enterprise Manager for Oracle Tuxedo on Oracle Enterprise Manager Cloud Control system.

This chapter contains the following:

•	Prerequisites

•	Deploying Enterprise Manager for Oracle Tuxedo on Management Servers

•	Deploying Enterprise Manager for Oracle Tuxedo on Management Agents

•	Typical Deploy Scenarios

Prerequisites

The following prerequisites must be met before you deploy the Enterprise Manager for Oracle Tuxedo.

•	Oracle Enterprise Manager Cloud Control 12.1.0.3 or higher is installed, Enterprise Manager Cloud Control 12c Management Agent is installed, and necessary post-installation steps are performed. For more information, see Enterprise Manager Cloud Control Documentation.

•	Enterprise Manager software library is set up. Follow these steps:

a.	Create a folder on the machine where Enterprise Manager is installed. For example, /net/<hostname>/scratch/aime/swlib1

b.	Log in to Enterprise Manager Cloud Control.

c.	From the home page, go to Setup > Provisioning and Patching > Software Library.

d.	Click Add.

e.	In the dialog box that appears, enter a name (for example, swlib1), and the path where the folder created in step a resides: /net/<hostname>/scratch/aime/swlib1.

•	Enterprise Manager for Oracle Tuxedo package is imported to Enterprise Manager server. You can choose one of the following ways:

•	Set up the emcli tool. For more information, see https://<Enterprise Manager console hostname>:<port>/em/console/emcli/download. Then run the following command:

emcli import_update -file=<Enterprise Manager for Oracle Tuxedo installation absolute path> -omslocal

By default, the Enterprise Manager for Oracle Tuxedo package is located in <TSAM Plus installation directory>/em/12.1.0.3.0_oracle.fmw.txdo_2000_0.opar.

Note:

The import process will not successful if any problems arise in the software library setup process.

or

•	From Enterprise Manager console, click Setup > Extensibility > Self Update in the upper right. Click Plug-in in the Type column and select Oracle Tuxedo in the list, then click Download.

Deploying Enterprise Manager for Oracle Tuxedo on Management Servers

Follow these steps to deploy Enterprise Manager for Oracle Tuxedo on management servers:

1.	Log in to Enterprise Manager Cloud Control.

2.	From the home page, navigate to Setup > Extensibility > Plug-ins.

3.	Click the Middleware folder to expand the list.

4.	Highlight Enterprise Manager for Oracle Tuxedo from the list and click Deploy on > Management Servers.

Deploying Enterprise Manager for Oracle Tuxedo on Management Agents

Before Enterprise Manager Cloud Control can discover Oracle Tuxedo Domain targets, you must deploy Enterprise Manager for Oracle Tuxedo on management agents. Do the following steps:

1.	Log in to Enterprise Manager Cloud Control.

2.	From the home page, navigate to Setup > Extensibility > Plug-ins.

3.	Click the Middleware folder to expand the list.

4.	Highlight Enterprise Manager for Oracle Tuxedo from the list and click Deploy on > Management Agents.

Note:

For more information, see the Plug-in Manager chapter in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Typical Deploy Scenarios

This section provides several typical deployment use scenarios to demonstrate how Enterprise Manager for Oracle Tuxedo is deployed in different circumstances.

Note:

For all the nodes involved in an Enterprise Manager for Oracle Tuxedo monitoring environment (including the machines on which Tuxedo applications, Enterprise Manager agents, Enterprise Manager OMS, and Enterprise Manager repository are running), it is highly recommended that you synchronize their clocks.

Basic Monitoring

Figure 2‑1 shows a typical Enterprise Manager for Oracle Tuxedo deployment scenario.

For performance and security considerations, if the Enterprise Repository agent supports the specific platform on which Tuxedo domains are running, it is recommended to deploy an Enterprise Repository agent on each physical machine that has Tuxedo domains monitored.

Figure 2‑1 Typical Enterprise Manager for Oracle Tuxedo Deployment Scenario

Remote Monitoring From Enterprise Repository Agent

Figure 2‑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.

Figure 2‑2 Remote Monitoring From Enterprise Repository Agent

Multiple tlisten Processes on One Physical Machine

In some circumstances, you may need to deploy multiple tlisten instances on a physical machine for the following reasons:

•	Security: Each tlisten process starts as a different user with different privileges.

•	Administration: Each tlisten process represents a different department.

Figure 2‑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.

Figure 2‑3 Multiple tlisten Processes Running On a Physical Machine

Multiple Agents and Clients Connecting to One tlisten Concurrently

A tlisten process with JMX agent embedded is able to interconnect with multiple Enterprise Repository agents concurrently. Figure 2‑4 shows a tlisten process running on "Machine 2" is connected and monitored by "EnterpriseManager Agent 1" and "EnterpriseManager Agent 2" concurrently.

In this scenario, you can separate Enterprise Repository agents and Tuxedo Domains related to a tlisten process into two groups ( for example, "EnterpriseManager Agent 1" monitors "Tux Domain 2" and "EnterpriseManager agent 2" monitors "Tux Domain 3").

You can also let "EnterpriseManager Agent 1" and "EnterpriseManager Agent 2" monitor both "Tux Domain 2" and "Tux Domain 3" at the same time.

Since JMX is a widely used and supported JRE standard, some third-partyJMX clients or JMX connectors are potentially supported by Enterprise Manager for Oracle Tuxedo, which makes Tuxedo monitoring and management functionalities more flexible.

Figure 2‑4 Multiple Agents and Clients Connecting to One tlisten Concurrently

Note:

In this scenario, once an active domain has been discovered by Enterprise Manager for Oracle Tuxedo, even if the domain is down afterwards, the Enterprise Manager for Oracle Tuxedo still can discover it (unless tlisten is rebooted).