Create a JMS Model Defining the JMS Datastores
24.7 JMS Standard Properties
This section describes the JMS properties contained in the message header and how to use them. In Oracle Data Integrator, pseudo-columns corresponding to the JMS Standard properties should be declared in accordance with the descriptions provided in Table 24–3 . The JMS type and access mode columns refer to the use of these properties in Oracle Data Integrator or in Java programs. In Oracle Data Integrator, some of these properties are used through the IKM options, and the pseudo-column values should not be set by the interfaces. For more details on using these properties in a Java program, see http:java.sun.comproductsjms . Table 24–3 Standard JMS Properties of Message Headers Property JMS Type Access ReadWrite Description JMSDestination JMS String R Name of the destination topic or queue of the message. JMSDeliveryMode JMS Integer RW set by IKM option Distribution mode: 1 = Not Persistent or 2 = Persistent. A persistent message is never lost, even if a router crashes. When sending messages, this property is set by the JMSDELIVERYMODE KM option. JMSMessageID JMS String R Unique Identifier for a message. This identifier is used internally by the router. JMSTimestamp JMS Long R Date and time of the message sending operation. This time is stored in a UTC standard format 1. JMSExpiration JMS Long RW set by IKM option Message expiration date and time. This time is stored in a UTC standard format 1. To set this property the JMSEXPIRATION KM option must be used. JMSRedelivered JMS Boolean R Indicates if the message was resent. This occurs when a message consumer fails to acknowledge the message reception. JMSPriority JMS Int RW Name of the destination topic or queue the message replies should be sent to. JMSCorrelationID JMS String RW Correlation ID for the message. This may be the JMSMessageID of the message this message generating this reply. It may also be an application-specific identifier. 24-10 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator Table 24–4 lists the optional JMS-defined properties in the JMS standard. 1: The UTC Universal Time Coordinated standard is the number of milliseconds that have elapsed since January 1st, 197024.7.1 Using JMS Properties
In addition to their contents, messages have a set of properties attached to them. These may be provider-specific, application-specific user defined or JMS Standard Properties . JMS properties are used in Oracle Data Integrator as complementary information to the message, and are used, for example, to filter the messages. JMSType JMS String RW set by IKM option Message type label. This type is a string value describing the message in a functional manner for example SalesEvent, SupportProblem. To set this property the JMSTYPE KM option must be used. Table 24–4 Standard JMS Properties of Message Headers Property JMS Type Access ReadWrite Description JMSXUserID JMS String R Client User ID. JMSXAppID JMS String R Client Application ID. JMSSXProducerTXI D JMS String R Transaction ID for the production session. This ID is the same for all the messages sent to a destination by a producer between two JMS commit operations. JMSSXConsumerTX ID JMS String R Transaction ID for current consumption session. This ID is the same of a batch of message read from a destination by a consumer between two JMS commit read operations. JMSXRcvTimestam p JMS Long R Message reception date and time. This time is stored in a UTC standard format 1. JMSXDeliveryCoun t JMS Int R Number of times a message is received. Always set to 1. JMSXState JMS Int R Message state. Always set to 2 Ready. JMSXGroupID JMS String RW ID of the group to which the message belongs. JMSXGroupSeq JMS Int RW Sequence number of the message in the group of messages. Table 24–3 Cont. Standard JMS Properties of Message Headers Property JMS Type Access ReadWrite DescriptionParts
» Oracle Fusion Middleware Online Documentation Library
» Terminology Using This Guide
» Concepts Knowledge Modules Introduction
» System Requirements and Certifications
» Using External Tables Technology Specific Requirements
» Using Oracle Streams Technology Specific Requirements
» Connectivity Requirements Installation and Configuration
» Creating an Oracle Physical Schema
» Setting Up an Integration Project
» Reverse-engineer an Oracle Model
» Setting up Changed Data Capture
» Designing an ETL-Style Interface
» Troubleshooting Oracle Database Errors Common Problems and Solutions
» System Requirements and Certifications Technology Specific Requirements
» Creating a File Physical Schema
» In the Models accordion, right click your File Model and select New Datastore.
» In the editor toolbar, click Reverse-Engineer.The Columns Setup Wizard is
» Click OK when the columns definition is complete. From the File main menu, select Save.
» In the Definition Tab, enter the following fields:
» Go to the Files tab to describe the type of file. Set the fields as follows:
» In the toolbar menu, click Reverse Engineer COBOL CopyBook.
» Click OK. COBOL Copybook reverse-engineering
» Create an ODBC Datasource for the Excel Spreadsheet
» Define the Data Server, Physical and Logical Schema for the Microsoft Excel
» Run the customized reverse-engineering
» Select the Microsoft Excel Driver .xls driver.
» Name the data source: ODI_EXCEL_FILE_REPO and select the file
» In Topology Navigator, add a Microsoft Excel data server with the following
» From the File main menu, select Save.
» Add a physical schema to this data server. Leave the default values in the
» In the Context tab of the physical schema, click Add.
» In the new line, select the context that will be used for reverse engineering and
» In the Reverse-Engineer Tab, set the following parameters:
» In the toolbar menu, click Reverse-Engineer.
» Technology-Specific Requirements Installation and Configuration
» Reverse-engineer a Data Model
» Loading Data from an ANSI SQL-92 Compliant Technology
» Loading Data to an ANSI SQL-92 Compliant Technology
» Integrating Data in an ANSI SQL-92 Compliant Technology
» System Requirements Installation and Configuration
» Technologic Specific Requirements Installation and Configuration
» Creating a Physical Schema for XML
» Reverse-Engineering an XML Model
» Synchronizing XML File and Schema
» Loading Data from an XML Schema
» Loading Data to an XML Schema
» Detect the Errors Coming from XML Common Errors
» Creating a Complex File Physical Schema
» Designing an Interface Oracle Fusion Middleware Online Documentation Library
» Using the BULK INSERT Command
» Using Linked Servers Technology Specific Requirements
» Creating a Microsoft SQL Server Physical Schema
» Create a Microsoft SQL Server Model
» Reverse-engineer a Microsoft SQL Server Model
» Loading Data from Microsoft SQL Server
» Integrating Data in Microsoft SQL Server
» Creating a Microsoft Excel Data Server
» Creating a Microsoft Excel Physical Schema
» Setting up Data Quality Setting Up an Integration Project
» Create a Microsoft Excel Model
» Reverse-engineer a Microsoft Excel Model
» Loading Data from Microsoft Excel
» Loading Data to Microsoft Excel
» Decoding Error Messages Common Problems and Solutions
» Specific Requirements Oracle Fusion Middleware Online Documentation Library
» Creating a Netezza Physical Schema
» Reverse-engineer a Netezza Model
» Loading Data from Netezza Loading Data to Netezza
» Creating a Teradata Physical Schema
» Reverse-engineer a Teradata Model
» Loading Data from Teradata Loading Data to Teradata
» Integrating Data in Teradata
» Primary Indexes and Statistics
» Support for Teradata Utilities Support for Named Pipes Optimized Management of Temporary Tables
» Creating a Hypersonic SQL Data Server
» Creating a Hypersonic SQL Physical Schema
» Setting up Changed Data Capture Setting up Data Quality Designing an Interface
» Introduction Oracle Fusion Middleware Online Documentation Library
» Concepts Knowledge Modules Oracle Fusion Middleware Online Documentation Library
» Creating a DB2400 Physical Schema
» Reverse-engineer an IBM DB2400 Model
» Setting up Trigger-Based CDC
» CDCRTVJRN Program Details Setting up Log-Based CDC
» Using the CDC with the Native Journals
» Problems While Reading Journals
» Loading Data from IBM DB2 for iSeries
» Loading Data to IBM DB2 for iSeries
» Integrating Data in IBM DB2 for iSeries
» Installing the Run-Time Agent on iSeries
» Using Client Access Alternative Connectivity Methods for iSeries
» Change the driver and URL to your AS400 server with the following information:
» Set the following java properties for the java machine the run-time agent deployed
» Troubleshooting Error messages Troubleshooting
» Connection Errors Common Problems and Solutions
» Integrating Data in Oracle BI
» Extracts the OBIEE Metadata from a OBIEE Instance
» Using the Lineage Lineage Lifecycle
» Installation Overview Installing the Lineage in an OBIEE Server
» Requirements Installing the Lineage in an OBIEE Server
» Post-Installation Tasks Installing the Lineage in an OBIEE Server
» Exporting the OBIEE Repository Documentation to a Text File
» Exporting the OBIEE Web Catalog Report to a Text File
» Refreshing the OBIEE Lineage From Existing Exports
» Configuring the Scripts Automating the Lineage Tasks
» Automating Lineage Deployment Automating Lineage Refresh
» Viewing Execution Statistics Viewing and Filtering Lineage Data
» Using the Dashboard Using the Lineage in OBIEE Dashboards
» Using Lineage and Hierarchy Using Contextual Lineage
» Reverse-engineer an Essbase Model
» Loading Metadata Designing an Interface
» Loading Data Designing an Interface
» Data Extraction Methods for Essbase
» Extracting Essbase Data Extracting Data
» Extracting Members from Metadata
» Creating an Hyperion Financial Management Data Server
» Creating an Hyperion Financial Management Physical Schema
» Create an Financial Management Model
» Reverse-Engineer an Financial Management Model
» Extracting Financial Management Data
» Extracting Members from Member Lists
» Data Store Tables Oracle Fusion Middleware Online Documentation Library
» Creating an Hyperion Planning Data Server
» Creating an Hyperion Planning Physical Schema
» Reverse-engineer a Planning Model
» Log on to Planning Web. Select Administration Data Load Administration.
» Accounts Datastore Tables and Data Load Columns
» Employee Datastore Tables and Data Load Columns
» Entities Datastore Tables and Data Load Columns
» User-Defined Dimensions Datastore Tables and Data Load Columns
» Attribute Dimensions Datastore Tables and Data Load Columns
» JMS Message Structure Concepts
» Creating a JMS Physical Schema
» Create a JMS Model Defining the JMS Datastores
» Loading Data from a JMS Source Integrating Data in a JMS Target
» Declaring JMS Properties Using JMS Properties
» Using Property Values as Source Data
» Setting Properties when Sending a Message
» Creating a JMS XML Physical Schema
» Reverse-Engineering a JMS XML Model
» Loading Data from a JMS XML Source Integrating Data in a JMS XML Target
» Creating a Physical Schema for LDAP
» Reverse-Engineering an LDAP Model
» Loading Data from an LDAP Directory
» Loading Data to an LDAP Directory
» Integrating Data in an LDAP Directory
» Setting Up an Integration Project Troubleshooting
» Creating a TimesTen Physical Schema
» Reverse-engineer a TimesTen Model
» Setting Up an Integration Project Setting up Data Quality
» Integrating Data in TimesTen
» Create an Attunity Stream Model Reverse-engineer an Attunity Stream Model
» Setting Up an Integration Project Designing an Interface Using the LKM Attunity to SQL
» Overview of the GoldeGate CDC Process
» Create the Staging Physical Schema
» Define the Source Data Server
» Create the Source Physical Schema
» Create the Replicated Tables
» Set Up an Integration Project
» Configure CDC for the Replicated Tables
» Configure and Start Oracle GoldenGate Processes
» Design Interfaces Using Replicated Data
» Initial Load Method Advanced Configuration
» Tuning Replication Performances Advanced Configuration
» One Source Multiple Staging Configuration
» Cross Reference Table Structures
» Loading Phase LKM Overview of the SOA XREF KM Process
» Defining the Topology Working with XREF using the SOA Cross References KMs
Show more