- WebSphere MQ Everyplace administration using administration messages
- Administration request message
- Administration reply message
- Administration console window
- Reply-to queue window
- Action window
- Reply window
- WebSphere MQ Everyplace administration scenario
- Branch to central routing
- Central to branch routing
- Queue manager connections
- Client to server connections
- Local queue
- Home-server queue
- WebSphere MQ bridge queue
- Creating an Administrator Handle for a new Queue Manager
- Creating an Administrator Handle for an existing Queue Manager
- Start queue manager Java example
- Create queue manager C example
- Creating the QueueAdminMsg object
- Deleting a queue manager in Java
- Deleting a queue manager in C
- Create a local queue
- Create a local queue in C
- Deleting a queue in Java
- Deleting a queue in C
- Adding an alias to a queue in Java
- Adding an alias to a queue in C
- Obtaining a list of aliases in C
- Removing an alias in Java
- Removing an alias in C
- Updating the propeties of a queue in Java
- Updating the propeties of a queue in C
- Inquiring on a queue in Java
- Inquiring on a queue in C
- Remote queue
- Home-server queue
- Store-and-forward queue
- Bridge object hierarchy
- Configuration example
- Message flow from WebSphere MQ Everyplace to WebSphere MQ
- A host and the WebSphere MQ Everyplace resources on it.
- A host and the WebSphere MQ Everyplace resources on it: 'dispersed' form.
- A simple local message put.
- LocalQueue@LocalQM with an alias of 'QueueAlias'.
- A message being placed on a matching alias.
- Defining a queue manager alias.
- Addressing messages to a queue manager alias.
- Resolving the queue manager alias and the queue alias.
- Local and remote queue managers with a definition and listener pair.
- A remote queue reference.
- Message resolution for a put.
- Message resolution for a put
- A message route entity.
- Using aliases on the remote queue.
- Message resolution for a put to a remote queue, using a Queue alias defined on TargetQM
- Message route entity of messages put to TargetQueueAlias on TargetQM
- Creating parallel routes between source and destination.
- Resolving the synchronous route.
- Resolving the asynchronous route.
- A pair of push message routes.
- A typical pushing S&F queue system.
- Routing of a message put to LocalQM and addressed to TargetQ@TargetQM
- A multi message route.
- How routes using remote queue definitions take precedence over store-and-forward queue routes
- Pushing S&F queues chained together.
- Transporting messages via an intermediate S&F queue.
- A chain of store and forward queues.
- A home server queue configuration.
- A home server queue pulling messages.
- An abstract pull message route.
- Administering queue managers that do not have listener capability.
- Via connections
- Message flow using a via connection
- Via connections expressed using message route schema
- Queue manager aliases and fail-over.
- Routing traffic using a "server" alias
- Routing traffic to the backup server, using a "server" alias
- Choosing between message routes.
- Connecting WebSphere MQ Everyplace and WebSphere MQ queue managers.
- Creating a remote queue on WebSphere MQ.
- Bridge listener pulling from a WebSphere MQ Everyplace transmit queue
- A single pull message route.
- A multiple pull message route.
- Multiple pull route, expressed using message route schema
- Pushing messages to WebSphere MQ.
- Messages travelling across a remote queue definition.
- Simplified view of route pushing messages to WebSphere MQ
- A client communicating with WebSphere MQ.
- Simplified pull routes from WebSphere MQ through a WebSphere MQ Everyplace gateway to a WebSphere MQ Everyplace device style queue manager
- Pushing messages using a via connection.
- Pushing messages to WebSphere MQ
- Simplified view showing routes which push messages from a device style WebSphere MQ Everyplace queue manager to a WebSphere MQ queue manager
- The WebSphere administrative console
- Specifying Web module properties
- Adding files to the application
- Adding web comopnents
- Specifying component type and class name
- Specifying a URL to map to your servlet
- Saving the file
- Install enterprise application
- Installing your component as a standalone module
- Specifying an applilcation name
- Information dialog
- Starting the web module
- Information dialog success message
© IBM Corporation 2002, 2003. All Rights Reserved