![]() |
![]() |
![]() |
![]() |
![]() |
• Table 7‑1 shows the supported Oracle Tuxedo buffer types for user payload.
Table 7‑2 User Payload Data in MON_PAYLOAD Call path CORRELATIONID Tuxedo buffer type index, defined in weblogic.wtc.jatmi.StandardTypes To store the payload into the Hadoop file system, you must set the environments JAVA_HOME and library path before starting LMS. Additionally, the LMS -T option must not be set or set to 1.The format is <domain>_<machine>_<yyyymmdd>.payload. The new hadoop file is produced every day and there is no file size limit.TSAM Plus uses the Hadoop SequenceFile format (Hadoop 2.6 ver=6) to store the payload in HDFS. Each payload record includes the key and value data. The record (org.apache.hadoop.io.BytesWritable) can be parsed using the Java class com.oracle.tsam.payload.PayloadRecord.The record key class is org.apache.hadoop.io.LongWritable and the value class is org.apache.hadoop.io.BytesWritable. Both are stored as the record.
•
•
•
• You can specify the local file directory where the payload data will be stored using the LMS server CLOPT parameter in UBBCONFIG. For example, to store the payload data in the file at /u01/common/patches/oracle/payload, configure the following in the UBBCONFIG file:For more information, refer to Local Monitor Server in Oracle TSAM Plus Reference Guide.
1. From the TSAM Plus console top menu bar, click Management -> Global Parameters.
2. Specify the Hadoop URL where you want to store the user payload data. The Hadoop URL must include the hostname, port, and payload file directory. For example: hdfs://localhost:8080/tmp/tuxPayload/
4. Click Modify.
1. From the TSAM Plus console top menu bar, click Policy-> Tuxedo Monitoring Policy.
2.
4. In the Call path tab, select Enable to enable the call path metrics collection.
5. Click the Define Payload Collection button to configure payload collection rules.You can also narrow down the payload data collection scope by defining collection data creteria or result filter. For more information, see Defining Payload Collection Data Criteria and Defining Payload Collection Result Filter.
1. Go to the Data Criteria tab in the Define Payload Collection dialog. All the supported buffer types are listed in the drop down list.
Table 7‑3 Data Criteria Table
•
3. Once all the criteria expression entries are defined, click Submit to save your configurations.
• For the buffer type FML32/FML/VIEW32/VIEW/X_C_TYPE/X_COMMON, the field table definition files must be uploaded in the Data Management -> Field Tables Management tab page before defining the data criteria.Table 7‑4 lists the APIs for exporting the user payload data.
Table 7‑4 APIs for Data Export When using API for data export, you must include the following jar in CLASSPATH under $TSAMDIR/lib : CLASSPATH=payloadapi.jar:com.bea.core.jatmi_2.0.0.0.jar:com.oracle.tuxedo.tjatmi_12.1.3.0.jar:commons-cli-1.2.jarNote: for the field PAYLOADTYPE, 1 means request, 2 means replyjava.lang.IllegalArgumentException - if this enum type has no constant with the specified namejava.lang.NullPointerException - if the argument is nullListing 7‑1 shows an example that reads payload metrics from TSAM Plus database, and exports the data to a text file.Listing 7‑1 Payload API Sample 1Listing 7‑2 shows an example that reads payload metrics from Hadoop, and exports the data to an XML file.Listing 7‑2 Payload API Sample 2
• Set the CLASS PATH as follows:
•
•