MQSeries.net :: View topic

udaya_isampalli · Posted: Thu Aug 16, 2007 9:24 pm Post subject:

Hi,
I Need some clarifications in Message Broker. Can you please provide some inputs
Bellow are some of the doubts

1. While accessing the Database from compute node or Database node can we use the 'Table Name' dynamically? i.e., while writing the select or update or insert statement in place of "Database.TableName" can i use the Table name from input Root?

2. While creating the message model from business requirement which logical property of simple element cannot be specified?
is it " the minimum number of occurance of element" or " Type of element" or "default value of element" or "length of element"?

3. While testing some message flows running on a remote system. What configuration step needs to be taken in order to use the Message Brokers Toolkit to retrieve messages from the broker queues? is it
"A cluster receiver channel must be created on the remote queue manager" or
"The developer must configure the queue manager, hostname, port number and channel name in the Dequeue Message dialog" or
"A channel named SYSTEM.BKR.CONFIG must exist on the remote queue manager" ?

4. While debuging a JavaCompute Node. The code for this node is in a separate Java project in the Toolkit workspace. In order for the debugger to step into the code, which of the following must the developer configure
" The Source pane of the Message Broker Debug configuration panel" or
"The Toolkit Java Builder to include the source when compiling" or
"The BAR file to include the source code" or
"The JAVA_SRC variable in the Broker service user's environment" ?

5. An enterprise that is heavily invested in their IBM zSeries mainframe and traditional COBOL/DB2 development has installed WebSphere Message Broker on their mainframe to help them move their legacy applications into a Service Oriented Architecture. Why should they consider retraining their developers to build message flows using Java instead of ESQL becuase of
" Java is the only language to use for SOA development" or
"Java is more powerful and reliable than ESQL" or
"Java on the mainframe can reduce licensing costs using zAAP" or
"ESQL is cumbersome to learn and hard to version control" ?

6. While embeding an HL7 record into an XML message for routing purposes. The HL7 message can contain any valid printable ASCII character. In order to ensure that the XML message is parseable by any XML parser and the HL7 record is still valid, the developer should embed the record in:
"simple XML element with XML special characters converted into Entities" or
"simple XML element containing a CDATA section with no processing of the HL7 record" or
"MRM-XMLNS element of base64binary type with Element Decoding property set to base64" or
"MRM-XML element of xsd:binary type with Interpret Element Value property set to HL7 Service String"

any kind of input are highly helpfull.

regards
Uday