•
• You can find the connection URL in the persistence.xml file packaged in $TSAM_INSTALL_DIR/deploy/tsam.ear, and yes, the password is encrypted.The TSAM Plus installer does not support RAC, but the TSAM Plus database deployer supports inputting the database URL directly. You can deploy TSAM Plus to an RAC database using the following steps:
1. Choose Skip, I will deploy TSAM Plus to an existing database server after the installation when you specify the database type during installation.
2. Run DatabaseDeployer after the installation finished, for example:Double check your registry.xml file under $ORACLE_HOME (which contains the destination TUXDIR). Make sure you have read/write permission to the file, and ensure the correctness of the file content (for example, the host name, TUXDIR path, etc.).
1. Make sure you enter the correct WebLogic domain information as prompted, for example, localhost:7001, and the correct password to connect the domain.
2. If the issue still exists, refer to the installation log in uninstall directory under the TSAM Plus installation directory.When you create a WebLogic domain, choose Oracle JRF -11.1.x.x [oracle_common].Make sure your $HOME directory has been mounted correctly before uninstalling the Oracle TSAM Plus.You can configure a TPUSREVT server and subscribe to the user events triggered by TSAM Plus alert.I see a description of the Region-Group.mapping file when looking for ART monitoring information in TSAM Plus documentation, does it have anything to do with ART?Region-Group.mapping is the configuration file; it allows you to separate the ART application into multiple regions in TSAM Plus. Actually, this configuration file has no ART CICS impact. It is only used in TSAM Plus.TSAM Plus Agent uses the .TMIB (and ..DMMIB) services to get the Oracle Tuxedo configuration. You need to create ACLs for them.The default administrator user name is admin, and the password is the one you entered during installation.Once the LMS server is correctly configured in the UBBCONFIG file and the domain is booted up, the component tree is displayed automatically.Ensure the Auto Refresh option is enabled; if not, you need to refresh the tree manually.Check if the Auto Refresh option is enabled; if not, you need to refresh it manually.This problem may be caused by an invalid $DISPLAY environment variable value setting. Do one of the following:
•
• Run xclock to see if $DISPLAY is running. If xclock runs successfully, the $DISPLAY environment variable value setting is correct; otherwise, set a valid $DISPLAY environment variable value.You can click the browser Refresh button, or use IE 9.0 (or above) or Firefox instead.You need to define and enable a policy first. Refer to the Oracle TSAM Plus Console Users Guide for details.Tune the database storage properties in the Global Parameters page. For more information, see the Oracle TSAM Plus Console Users Guide.
•
1. Make sure all Enterprise Manager agents under OMS are running in Up status before you can successfully undeploy Enterprise Manager for Oracle Tuxedo.
2. Remove the MKS related environment variables from the PATH variable before deploying Enterprise Manager for Oracle Tuxedo.Make sure the directory of libjvm.so (under $JAVA_HOME) is included in the environment variable SHLIB_PATH, LIBPATH, or LD_LIBRARY_PATH.For information about JRE/JDK requirement, refer to Booting up the tlisten Process in Enterprise Manager for Oracle Tuxedo Getting Started Guide.Make sure the directory of libnet.so (under $JAVA_HOME) is included in the environment variable SHLIB_PATH, LIBPATH, or LD_LIBRARY_PATH.
• The With Oracle Tuxedo Authentication checkbox is selected.You can leave User Name/User Password/Application Password empty if the domain security setting is NONE.
• The host name and port number configured in tlisten process are same with the NLSADDR configured in TUXCONFIG, and they are reachable to BBL.The change in TUXCONFIG is collected by automatic discovery at 24-hour intervals. It requires 24 hours (at most), to show up.If there is no IPv6 connectivity between the Enterprise Manager Agent host and the target host, you should enforce IPv4 before starting the tlisten process by setting TMJMX_JAVA_OPTIONS as follows:It may be caused by inconsistent target collection interval settings. The metrics collection setting interval value for each target should be the same.Since Average Execution Time (microsecond) is sampling metrics, if there is no tpcall at that time, Unavailable is displayed, indicating 0.
1. Check if the target status is Up after domain discovery.The Oracle Tuxedo target status is decided by the Response metric value which has a default collection interval of 5 minutes. You can change the default collection interval on Enterprise Manager console.SQL> alter session set time_zone='<new time zone>';
• the collection interval for the SERVICE_STATISTICS metric of all targets in a domain are the same.
• the collection interval for the CLIENT_CONNECTION_NUMBER metric of domain and machine targets in a domain are the same.
• the collection interval for the domain metric DOMAIN_OPERATION_STATISTICS is the same as the machine metric MACHINE_OPERATION_STATISTICS within the domain.
•
• Set all the GWWS necessary environment variables before starting tlisten -j: SALTCONFIG, XSDFILES, XSDDIR, FLDTBLDIR32, FIELDTBLS32Yes, but for monitoring Oracle Tuxedo releases earlier than 12.1.1.0, you need to set the environment to SNMP_USER_EVENT=y before booting up the Oracle Tuxedo domain.
• The port set to Receive Port for SNMP Agent of domain target is not occupied before configuring it on Enterprise Manager console.
• tux_snmpd is started correctly.
• If the Oracle Tuxedo version is earlier than 12.1.1.0, the SNMP_USER_EVENT environment variable is configured to yes before booting up the Oracle Tuxedo domain.
• The Response metric collection interval for the Domain target is not less than 5 minutes.
• No error message containing SNMP in the Enterprise Manager agent log file (gcagent.log) located in $EMSTATE/sysman/log.
• If Oracle Tuxedo version is earlier than 12.1.1.0, the SNMP_USER_EVENT environment variable is configured to yes before starting tlisten.
• tlisten is running.
•
• EA_SM_SNMP_MIBFILE and BEA_SM_BEAMGR_CONF are set correctly before starting Oracle Tuxedo SNMP agent.
• tux_snmpd works correctly.
• tux_snmpd and <logical_agent_name>_trapd processes are running.
•
• In order to make the target machine available for Resource Broker domain deployment, one tlisten must be started with the -j option, and tlisten must be previously discovered by a local (on the same tlisten host) Enterprise Manager agent.
Note: You must use the full machine name when starting tlisten and deploying a new Enterprise Manager agent.In domain UBBCONFIG editor, why is the add (+) button beside an application package always disabled?If the machine has been added, check if the metadata information defined in the package Properties.xml matches the target machine. You can view the information by hovering the mouse cursor on an added machine in the Machine List panel or an application package in the Package List panel.Only the domains created by Resource Broker UBBCONFIG editor can be edited.
• The incident rule has been saved. After defining an incident rule, you must click Save in the Create Rule Set page for the changes to take effect.
• When defining the incident rule, Tuxedo Event Connector (PL/SQL Procedure) is selected as the action.
• The entire domain has been saved. After defining the deployment policy in domain UBBCONFIG editor, you must click Save in the Controls panel for the changes to take effect.The item displays in the Candidate Groups list only when you added the application package with the checkbox As Candidate checked.