•
•
1.
3. From the home page, go to Setup > Provisioning and Patching > Software Library.
4. Click Add.
5. In the dialog box that appears, enter a name (for example, swlib1), and the path where the folder created in step 1 resides: /path/to/swlib1.For more information, see Configuring a Software Library in Oracle Enterprise Manager Cloud Control Administrator's Guide
• One is to import the .opar file manually using the emcli tool after installing TSAM Plus using the TSAM Plus 12.1.1.1 installer;
1. Set up the emcli tool. For more information, see https://<Enterprise Manager console hostname>:<port>/em/console/emcli/download.By default, the Enterprise Manager for Oracle Tuxedo package is located in <TSAM Plus installation directory>/em/12.1.0.2.0_oracle.fmw.txdo_2000_0.opar.
1.
2. In the Self Update page, check if Connection Mode is Online; if not, click Connection Mode status to set online mode.Figure 1 Self Update Page
3. Figure 2 Plug-in Updates List
4. 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.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:
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.Before you can use Enterprise Manager for Oracle Tuxedo to monitor the Tuxedo domain targets, you must start the tlisten process before starting the Tuxedo domain so that Tuxedo Domain MBeans can register with the JMX agent embedded in the tlisten process. For MP domains in particular, you should start tlisten for every machine.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:
Note: Make sure that the host and port specified by the -l option are the same as the NLSADDR value specified in the UBBCONFIG file.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.
1. In beamgr.conf, configure the following:
• TRAP_HOST, which format is:Where the host_name is the Enterprise Manager agent host, and the trap_port is the Enterprise Manager agent listening port to be configured as monitoring property of Batch System target. Make sure the port number is not occupied by any process in the Enterprise Manager Agent located OS.
• TMAGENT, which format is:
2.
Note: If you are using Oracle Tuxedo 11.1.1.3.0 or 11.1.1.2.0, set the environment: SNMP_USER_EVENT=y before starting Oracle SNMP Agent.For more information, see Starting Oracle SNMP Agent in Oracle Tuxedo SNMP Agent Administration Guide.
Note: If your Enterprise Manager agent is located at the same machine as your Oracle Tuxedo domain, make sure the port number followed by the -p option is not equal to the port number configured in TRAP_HOST in beamgr.conf.After Oracle SNMP Agent is booted successfully, there should be two processes, tux_snmpd and <logical_agent_name>_trapd, running on the Oracle Tuxedo machine.Configuring the UBBCONFIG FileTo monitor and manage the Tuxedo domain monitoring targets, you must register the targets in the tlisten process by adding the NETWORK section and configuring the NLSADDR parameters in the UBBCONFIG file for the Tuxedo domain in SHM mode.Collection and calculation of certain metrics (such as Service Metrics and IPC Queue Metrics in MIB), consumes CPU time and potentially impacts Oracle Tuxedo performance. Oracle Tuxedo uses the EXT_MON OPTIONS parameter in the UBBCONFIG file RESOURCES sectionto to allow MIB performance sensitive metrics collection.Listing 2 shows an SHM mode UBBCONFIG file example supporting Enterprise Manager monitoring.After the tlisten process is successfully started, refer to online Oracle Tuxedo Documentation to load UBBCONFIG and boot up Oracle Tuxedo.If you are planning to manage and monitor Oracle Tuxedo Batch System, set the environment variable JESMONITOR=yes before starting the Tuxedo domain.
2. From the home page, go to Targets >Middleware.
3.
4.
5.
• Hostname: Mandatory parameter. Specifies the host where the Tuxedo domain master machine is running.
•
• 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 SECURITY value of the Tuxedo domain 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 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.
• 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.Figure 3 Domain Discovery Page
6. Click Discover Now.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.Figure 4 Successful DiscoveryIn conjunction with the step Configuring and Starting Oracle SNMP Agent (Optional), specify the port number set in beamgr.conf as Receive Port for SNMP Agent in the Monitoring Configuration page of Tuxedo Batch System target. Do the following steps:
2.
3.
4. Click OK.After the configuration settings are pushed to agent side, there should be a thread listening on this port at the monitoring Enterprise Manager agent side. If not, check the Oracle Management Agent metadata log file (gcagent.log) located in $EMSTATE/sysman/log.Click the Domain Home button on the page shown in Figure 4, the Tuxedo domain target home page is displayed, which allows you to view general information and perform administrative functions. From the left Target Navigation panel, you can easily navigate to other target home pages by expanding the list and selecting the desired target.
3. For example, you can modify the UBB parameters for a Tuxedo domain target by right-clicking the domain target name in the Target Navigation panel and then clicking Control > Modify UBB.Figure 5 Modify UBB PageFor more information, see Dynamic Resource Broker in Enterprise Manager for Oracle Tuxedo User Guide.