•
• Set up the emcli tool. For more information, see https://<Enterprise Manager console hostname>:<port>/em/console/emcli/download. Then run the following command:By default, the Enterprise Manager for Oracle Tuxedo package is located in <TSAM Plus installation directory>/em/13.1.2.0.0_oracle.fmw.txdo_2000_0.opar.
Note:
• 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.
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.
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.Figure 2‑1 shows a typical Enterprise Manager for Oracle Tuxedo deployment scenario.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.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.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").
Note: