By default, the ScribbleSubscriber application connects to the broker by using the same connection settings
as the ScribblePublisher application. However, you can change the connection settings if you want:
click the Connect icon and edit the default values.
Click and drag your mouse pointer in the ScribblePublisher window and watch your drawing appear,
inverted, in the ScribbleSubscriber window.
Things to try
Start another instance of the ScribbleSubscriber application. When you create a drawing in the
ScribblePublisher window, your drawing is displayed in both instances of ScribbleSubscriber.
Modify the message flow to connect the MQOutput nodes to the Out and NoMatch terminals of the Publication node.
Redeploy the message flow. Start a ScribblePublisher but not a ScribbleSubscriber. As you move your mouse to draw in the
ScribblePublisher canvas, messages are propagated to the MQOutput node that is connected to the NoMatch terminal.
Using WebSphere MQ Explorer, observe these messages accumulating on the associated queue.
Using the scribble sample on a remote system
The Scribble sample uses a remote (Client) connection to connect to the WebSphere MQ queue manager.
Consequently, it is possible to use the ScribblePublisher and ScribbleSubscriber applications to exercise the
ScribblePublish message flow running on a remote system.
To run Scribble on a remote system:
Ensure that the required WebSphere MQ resources are defined on the remote queue manager:
QLOCAL name="SCRIBBLE_PUBLICATION"
QLOCAL name="SYSTEM.JMS.ADMIN.QUEUE"
QLOCAL name="SYSTEM.JMS.PS.STATUS.QUEUE"
QLOCAL name="SYSTEM.JMS.REPORT.QUEUE"
QLOCAL name="SYSTEM.JMS.MODEL.QUEUE"
QLOCAL name="SYSTEM.JMS.ND.SUBSCRIBER.QUEUE"
QLOCAL name="SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
QLOCAL name="SYSTEM.JMS.D.SUBSCRIBER.QUEUE"
QLOCAL name="SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE"
Channel name="SCRIBBLE_SVRCONN" type="SVRCONN"
A TCP/IP listener
Deploy the scribble.bar BAR file to an execution group on the remote integration node.
Start a ScribblePublisher and configure the host name, port, and queue manager name to match those on the remote system.