System and method for supporting a complex message header in a transactional middleware machine environment

A flexible transactional data structure can be used to store message header in a transactional middleware machine environment. The flexible transactional data structure can have dynamic numbers of fields and is accessible via specified IDs. The message header can include a first data structure that stores address information for accessing a client using a first message queue, and a second data structure that stores address information for accessing a client using a second message queue. The first type of server operates to use only the first data structure to obtain the address information for accessing the client using the first message queue. The second type of server operates to obtain a key from the first data structure first, and then use the key to obtain from the second data structure the address information for accessing the client using the second message queue.

SYSTEM AND METHOD FOR SUPPORTING DIFFERENT MESSAGE QUEUES IN A TRANSACTIONAL MIDDLEWARE MACHINE ENVIRONMENT

A system and method can support different message queues in a transactional middleware machine environment. The transactional middleware machine environment includes an advertized table that comprises a first queue table and a second queue table, with the first queue table storing address information for a first message queue and the second queue table storing address information for a second message queue. The advertized table is further adaptive to be used by a first transactional client to locate a transactional service provided by a transactional server. The first transactional client operates to look up the first queue table for a key that indicates the address information of the transactional service that is stored in the second queue table. 1. A system for supporting different message queues in a transactional middleware machine environment , comprising:an advertized table that comprises a first queue table and a second queue table, wherein the first queue table stores address information for a first message queue and the second queue table stores address information for a second message queue,wherein the advertized table is adaptive to be used by a first transactional client to locate a transactional service provided by a transactional server, andwherein the first transactional client operates to look up the first queue table for a key that indicates the address information of the transactional service that is stored in the second queue table.2. The system of claim 1 , wherein said transactional server listens to both the first message queue and the second message queue.3. The system of claim 1 , wherein the first transactional client operates to send a message to the transactional server via the second message queue claim 1 , based on the address information of the transactional service stored in the second queue table.4. The system of claim 1 , wherein the advertized table is adaptive to be used by a second transactional client to locate a transactional ...

System and method for supporting a complex message header in a transactional middleware machine environment

A flexible transactional data structure can be used to store message header in a transactional middleware machine environment. The flexible transactional data structure can have dynamic numbers of fields and is accessible via specified IDs. The message header can include a first data structure that stores address information for accessing a client using a first message queue, and a second data structure that stores address information for accessing a client using a second message queue. The first type of server operates to use only the first data structure to obtain the address information for accessing the client using the first message queue. The second type of server operates to obtain a key from the first data structure first, and then use the key to obtain from the second data structure the address information for accessing the client using the second message queue.

System and method for supporting a complex message header in a transactional middleware machine environment

System and method for supporting different message queues in a transactional middleware machine environment

System and method for supporting different message queues in a transactional middleware machine environment

A system and method can support different message queues in a transactional middleware machine environment. The transactional middleware machine environment includes an advertized table that comprises a first queue table and a second queue table, with the first queue table storing address information for a first message queue and the second queue table storing address information for a second message queue. The advertized table is further adaptive to be used by a first transactional client to locate a transactional service provided by a transactional server. The first transactional client operates to look up the first queue table for a key that indicates the address information of the transactional service that is stored in the second queue table.

[UNK]

A system and method can support different message queues in a transactional middleware machine environment. The transactional middleware machine environment includes an advertized table that comprises a first queue table and a second queue table with the first queue table storing address information for a first message queue and the second queue table storing address information for a second message queue. The advertized table is further adaptive to be used by a first transactional client to locate a transactional service provided by a transactional server. The first transactional client operates to look up the first queue table for a key that indicates the address information of the transactional service that is stored in the second queue table.

System and method for supporting a complex message header in a transactional middleware machine environment

A flexible transactional data structure can be used to store message header in a transactional middleware machine environment. The flexible transactional data structure can have dynamic numbers of fields and is accessible via specified IDs. The message header can include a first data structure that stores address information for accessing a client using a first message queue, and a second data structure that stores address information for accessing a client using a second message queue. The first type of server operates to use only the first data structure to obtain the address information for accessing the client using the first message queue. The second type of server operates to obtain a key from the first data structure first, and then use the key to obtain from the second data structure the address information for accessing the client using the second message queue.