My Oracle Support Banner

EAI issue with the MSMQ transport (Doc ID 544229.1)

Last updated on JUNE 21, 2023

Applies to:

Siebel System Software - Version 7.5.3 SIA [16157] and later
z*OBSOLETE: Microsoft Windows 2000
Version: 7.5.3 [16157] Pub Sect

Database: Microsoft SQL Server 2000 SP 1

Application Server OS: Microsoft Windows 2000 Advanced Server SP 1

Database Server OS: Microsoft Windows 2000 Advanced Server SP 1




Symptoms

All these tests were done through the Workflow Simulator. The error message we received was 'Unable to open MSMQ "XXXX\eeee\private$\SECURITY"' . However, since we can connect to an MSMQ remote private queue in the shared domain, this SR does not seem to apply to us. (perhaps it was fixed with 7.5.3?)

Normally we could accomplish a remote queue write by installing MSMQ Client on the server where our Siebel integration processes was running, and we have done so to write to normal MSMQ queues (remote, private). However, to reach a remote MSMQ-T server we have to install MSMQ Server (instead of client) on the server where our Siebel integration process runs. Unfortunately, as soon as we do this, the only queue we can write to is a local queue on that server.

In point form:

-Siebel Server with MSMQ Client ... to ... MSMQ (remote, private)    PASS
-Siebel Server with MSMQ Client ... to ... MSMQ-T            FAIL
-Siebel Server with MSMQ Server ... to ...MSMQ (remote, private)    FAIL
-Siebel Server with MSMQ Server ... to ...MSMQ-T            FAIL
-Siebel Server with MSMQ Server ... to ... MSMQ (local, private)        PASS

One of the main questions we're asking ourselves is "Why doesn't Siebel do anything with the 'MsmqQueueMachineName' parameter it asks for?". Because it seems to us that the only 2 ways Siebel can locate a server queue is a) if the Siebel Server has an MSMQ Client which specifically points to a Server housing the specified queue or b) if the Siebel Server has an MSMQ client on it which locally houses the specified queue. If this is the case, why do workflows or subsystem profiles even bother asking for the machine name parameter? Also, if this is the case, our current solution proposal is in jeopardy because we cannot use MSMQ Client to point directly to an MSMQ-T queue.

This leads me to believe that I'm likely missing something basic about connecting to a remote MSMQ...

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
 Message 1

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.