Академический Документы
Профессиональный Документы
Культура Документы
Ralph Bateman
ralph@uk.ibm.com
Assumptions
Deployed
Configuration Resources
Manager Broker
Execution Group
Message Broker Explorer (IS02)
Performance Monitor
f Easily view CPU, IO and other metrics
Configuration Manager Proxy
▪ Comprehensive Java API for administering broker domains:
import com.ibm.broker.config.proxy.*;
Used for administering brokers, execution groups, message flows, dictionaries (and other deployed message
flow dependencies), subscriptions, the publish/subscribe topology, collectives, the event log, topics hierarchy
and the Configuration Manager
The Message Broker Toolkit Administration perspective, IS02 and various commandline utilities are
visualizations of this API.
MDB
WebSphere
Business
Monitor
Objectives
Moving to production
Infrastructure changes
Problem Determination
f Message Flow Defects
f Broker Problems
Recovery
Separation of Concerns - User Roles
Application Developer Administrator
BAR
Knows the message flow logic Doesn’t know the message flow logic
No knowledge of production environment Knowledge of production environment
Minimizing the Cost of Administration
Before Deployment
f Deployment Descriptors
After Deployment
f Reviewing version information
f Configurable Services
f Trace Nodes
f LocalEnvironment
f Additional Products eg. WSRR, Adapters
Advanced Tools
f Backup and Restore
f Inter-process Communication
f Synchronization and Adoption
Moving to Production - Configuration Tweaks
Use keywords to embed other information (e.g. Author, subflow versions, CVS $id$)
f Use ‘Version’ property or embed eyecatchers in your files
f Eyecatcher form is “$MQSI key = value MQSI$”
▪ The EndpointLookup node can be used to set up the LocalEnvironment based on the contents of
WebSphere Service Registry and Repository (WSRR)
WSRR
Advanced Administration
Backup and Restore
Inter-process Communication
Holds unprocessed
Queues messages from the broker
and CMP applications
Registry
Holds configuration
information set by
Repository
mqsicreateconfigmgr
Holds all other
configuration
information!
Config Data
Admin
CMP Manager Flow
Agent
Engine
Important Queues:
f SYSTEM.BROKER.CONFIG.QUEUE (CMP to CM)
f SYSTEM.BROKER.CONFIG.REPLY (CM to CMP)
f SYSTEM.BROKER.ADMIN.QUEUE (CM to Admin Agent)
f SYSTEM.BROKER.ADMIN.REPLY (Admin Agent to CM)
f SYSTEM.BROKER.EXECUTIONGROUP.QUEUE (Admin Agent to EG)
f SYSTEM.BROKER.EXECUTIONGROUP.REPLY (EG to Admin Agent)
Improve PD - How Deployment Works
SYSTEM.BROKER. SYSTEM.BROKER. SYSTEM.BROKER.
CONFIG.QUEUE ADMIN.QUEUE EXECUTIONGROUP.QUEUE
2. Config Manager applies overrides and converts BAR file to an internal message format.
3. Internal deployment message sent to SYSTEM.BROKER.ADMIN.QUEUE. The Config Manager Generates a BIP1520
(deployment initiated) message, which is sent to the CMP.
4. Admin agent receives message, sends execution group information onto the correct DFE by writing to
SYSTEM.BROKER.EXECUTIONGROUP.QUEUE.
5. DFE picks up message and processes message. Generates a BIP4040 if all is well.
Can be disabled for all or selected brokers using the CMP API
Exerciser
Coping With Infrastructure Changes –
Broker Adoption
The V6.1 Configuration Manager is able to adopt
previously deployed brokers
Use
f if your Configuration Manager repository is destroyed
(and backups are not available!)
f If you need to restructure your domain
f Broker’s should still be owned by only one active
Configuration Manager
Support Information
http://www.ibm.com/software/integration/wbimessagebroker/support/
For those with a taste for more…
Session Date/Time
1102
Introduction to WebSphere Message Broker
Mon 1:30 - 2:30
1162
Administration of your z/OS MB (w/o the toolkit) Tues 1:30 - 2:30
1198
MQ and MB with WSRR on z/OS
f Session 1162
WebSphere Message Broker: Administration of your Message
Broker
Backup charts
Command-line – three types
Message Configuration
Brokers E
Manager
Toolkit G
▪ MQ Configuration
▪ Control access to the Configuration Manager and broker’s queues and queue manager:
▪ Who should have access to the Configuration Manager’s queues and queue manager?
▪ Who should have access to the broker’s queue manager? And broker system queues?
▪ Use SSL between MBT and CM (and between Config Manager and brokers if necessary)
▪ Consider using the same queue manager for both broker and Config Manager
▪ This will minimize MQ administration, but having multiple CMs may increase administration cost
▪ mqsideploy –cancel (only if there is no chance that the broker could have
picked up the deployment message)
▪ Also:
▪ Documentation, mqseries.net, Tech docs, IBM Education Assistant, IBM
Service etc.