WBI

• Based on MQSeries' messaging and queuing capabilities, the MQSeries Integrator is a real-time, intelligent, rules-based message routing and dynamic message content transformation and formatting system that allows you to integrate all types of applications and systems into robust, flexible and scalable information networks.

• MQSeries Integrator (MQSI) software enables integration of applications and systems into robust, flexible and scalable information networks. Based on MQSeries messaging and queuing capabilities, the MQSeries Integrator is a real-time, intelligent rules-based message routing and dynamic message content transformation and formatting system. Along with this functionality, preconfigured templates for major packaged applications and e-business extensions will also be provided.

• MQSeries Integrator and MQSeries Workflow rely on MQSeries. MQSeries Integrator intercepts MQSeries messages transforming and routing the message contents based upon information stored in a rules database.

• MQSI is an anonymous publish/subscribe architecture that essentially contains three parts:
  • Transport
  • Formatter
    The meta-data formatting engine allows the translation of "anything to anything."
  • Rules/Routing Engine
    The rules and formatting engine has been benchmarked at over 1000 messages per second (medium sized Solaris server used)

• For the user, the main components of the MQSeries Integrator are:
  • A database
  • Formatter GUI
  • Rules GUI
  • The Rules Daemon (also called rules processor or rules engine)
  • Configuration files
  • Various tools/utilities
  • Queues managed by MQSeries

               .---------------.       .--------------------.      .-----------.
               | Formatter GUI |  <--- | DB connection file | ---> | Rules GUI |
               .---------------.       .--------------------.      .-----------.
                      |                                                 |
                      .------------------>.<----------------------------.
                                          |
       Development                        |
                                          V
                                   .-----------------.
            ---------------------  |  MQSI database  | ---------------------
                                   .-----------------.
                                          |
       Runtime                            |
                                          V
            .--------------.       .----------------.      .-----.
            | Rules daemon | --->  | Rules daemon   | ---> | log |
            | cfg file     |       | mqsiruleng.exe |      .-----.
            .--------------.       .----------------.
  
  

  The MQSeries Integrator database contains input and output formats and rules on how they are used to map data from an incoming message to one or more outgoing messages.

  At development time you define formats and rules. This is done with two programs (graphical user interfaces):

  • Formatter GUI
  • Rules GUI
  
  Both programs require a database connection file (sqlsvses.cfg) to access the database.
  You use the Formatter GUI to define input and output formats, that is, how input and output messages are structured.
  With the Rules GUI you define how input formats are mapped to output formats and to what queue they are put.
  You can also add fields to a message using literal values or values you calculate from fields in the input message. It is also possible to substitute values in the input message with different ones in the output message.

  At run time, the NEON Rules Daemon, also known as rules processor, uses the information in the database to process incoming messages. The rules processor needs information provided in a rules processor configuration file. You can have several instances of the rules processor running, each using a different configuration file.
  The rules processor configuration file is important. It contains, for example, the name of the default application group and message type. Notice that this is the MQSI message type and not the MQSeries message type in the message header MQMD.
  An application group is a container for messages. For example, all messages regarding payroll applications can belong to one application group and messages concerning sales to another. Message types are input formats defined with the Formatter GUI.
  Each instance of the rules processor works with one application group; and for each application group you can have one default message. Also, in Version 1.0, you can have only one input queue per rules processor instance.
  How does the MQSI process (input) messages other than the default one? The application group and the message type must be specified in the message. To do this the MQSI header is added to the message. That means, a message the rules processor processes, can have one of two formats:

  • MQSeries Header + Data
  • MQSeries Header + MQSI Header + Data
  
  Of course, the program that sends the message must provide the MQSI header.

Using the MQSeries Integrator Version 1.0 , SG24-5386-00

Llibres MQI :

• GC34-5599 = MQI V2 Introduction and Planning
• GC34-5600 = MQI V2 Installation
• SC34-5602 = MQI V2 Using the Control Center
• SC34-5792 = MQI V2 Adminstration Guide

These can be existing MQSeries-enabled applications and need not be aware of WebSphere MQ Integrator; in this case, the message flows set the correct configuration values to handle the messages. Alternatively, the application can prefix the user data of the message with a WebSphere MQ Integrator header (MQRFH or MQRFH2) to control the way the broker handles the message.

WebSphere MQ Integrator Deployment and Migration, SG24-6509-00

If the message has an MQRFH or MQRFH2 header, the domain that is identified in the header (either in Format or the name/value data) determines the parser that is associated with this message.

MB v 6.0 Message Flows, page 11, [19/1020].

url

IBM Integration Bus (IIB) - formerly known as WebSphere Message Broker - is an enterprise service bus (ESB) providing connectivity and universal data transformation for service-oriented architecture (SOA) and non-SOA environments.

• WebSphere Message Broker enables information packaged as messages to flow between different business applications, ranging from large legacy systems through to unmanned devices such as sensors on pipelines.

  There are two ways in which WebSphere Message Broker can act on messages.

  • Message routing - messages can be routed from sender to recipient based on the content of the message.
  • Message transformation - messages can be transformed before being delivered.

    Before a message flow node can operate on an incoming message, it must understand the structure of that message.

    • Some messages contain a definition of their own structure and format. These are known as self-defining messages. Self-defining messages can handled without the need for additional information about structure and format.
    • Other messages do not contain information about their structure and format. To process them, a message definition of their structure must be created and made available.

  WS MB v 6.0 technical overview - url

• WebSphere Message Broker delivers an advanced Enterprise Service Bus providing connectivity and universal data transformation for both standard and non-standards based applications and services to power your Service Oriented Architecture

• Transforms and enriches in-flight information to provide a level of intermediation between applications that use different message structures and formats

• Enriches and distributes real-time information from disparate sources of information through a network of access points, and provides a powerful new means to unify organizations

• Integrates with multiple sources of data such as databases, application and files to perform any type of data manipulation including logging, updating and merging.

• Simplifies the integration of existing applications with web services, by transforming and routing SOAP messages, as well as logging of Web Services transactions

• WebSphere Message Broker includes the functionality of WebSphere Event Broker. WebSphere Event Broker is available as a seperately orderable product for customers requiring publish and subscribe capabilities and other distribution capabilities using multiple protocols without the powerful and adaptable transformation features provided by WebSphere Message Broker.

• Also available as WebSphere Message Broker with Rules and Formatter Extension, which extends the capabilities of the Message Broker to offer continuity and compatibility for existing WebSphere MQ Integrator v2.1 customers who require IBM Rules and Formatter nodes

• WBI-MB v5, también conocido como MQ Integrator, es un broker EAI (Enterprise Aplication Integration), es decir un motor de ejecución de flujos - Angel Hernandez Bravo.

• Message Broker es un sistema de multiprocesos (execution groups) y multithreads (message flows) que requiren multiples procesadores para sacar ventaja de la capacidad de proceso en paralelo. Los message flows típicos de broker son CPU bound, o sea no comparten la CPU facilmente. - Vicente.

licensing :

• developer - free
• standard - all features, limited resources
• express - basic set of features, low requirements
• scale - basic features, high capacity requirements
• remote adapter deployment - integration with EIS
• websphere message broker - full environment

Broker
The broker is the component that represents WebSphere Business Integration Message Brokers at runtime. A broker is a system service on Windows platforms ( a daemon process on UNIX platforms or a started process on z/OS platforms ) that controls processes that run message flows.

(Broker) Domain
Brokers are grouped together in broker domains. The brokers in a single broker domain share a common configuration that is defined in the Configuration Manager.

A broker domain is one or more brokers that share a common configuration, together with the single Configuration Manager that controls them.

Configuration Manager
The Configuration Manager manages the broker domain and is the interface between the Message Brokers Toolkit and the brokers in the broker domain. The Configuration Manager is the interface between the workbench, the configuration repository, and an executing set of brokers.

Toolkit
Application developers work in separate instances of the Message Brokers Toolkit to develop message sets and message flows. The Message Brokers Toolkit also communicates with one or more Configuration Managers, and is used to manage broker domains.

Message set
A message set project is a specialized project (container) in which you create and maintain all the resources associated with exactly one message set. The content of a message set project is a single message set folder, the name of which provides the name of the message set. Additionally the user can create his own folders within the message set project.
A message set is a container; a logical grouping of messages and associated message resources (elements, types, groups, etc).

Message flows
Message flows are programs that provide the logic that the broker uses to process messages from business applications.

Execution group
Execution groups enable message flows within the broker to be grouped together. Each broker contains a default execution group, and more execution groups can be created as long as unique names are given to them within the broker. Each execution group is a separate operating system process so that the contents of an execution group remain separate from the contents of another execution group within the same broker, which can be useful for isolating pieces of information for security.

DataBases

• Message Broker requires a database for each broker, where it stores configuration and control information. which is also known as the broker's local persistent store.

• The Configuration Manager also stores configuration and control information in its database, which is known as the internal configuration repository.

WBI-MB Basics, SG24-7090, page 4 [18 of 262]

To connect to a broker, you can user a ".broker" file (old ".config"), whose contents is:

It can be used in "mqsicreateexecutiongroup" command, after "-n" flag.

IS02 = MB Explorer plug-in

Top

MB Flows, SG24-5386-00, page 531, 541/556

Broker archive file
The archive format is called the broker archive or bar file, and is the unit of deployment to the broker. It can contain any number of compiled message flow (.cmf) and message set (dictionary) files, and a single deployment descriptor. The bar file is a zip-format file that is used by both people, such as an administrator manually configuring archive deployment, and by automation, such as the rapid application development (RAD) component. The deployment descriptor is an XML format file that resides in the META-INF folder of the zip file, is called Broker.xml, and can be modified using a text editor or shell script. [detalls] As a zip-format archive, the broker archive file can also contain any additional files you need. The .cmf and dictionary are replaced with identical names to those in the bar file; the remaining bar file content is added and any other content in the execution group is left undisturbed.

messagebroker Message Flows, page 532 [542 of 556]

Remove Override configurable property values if you want to customize and keep the BAR file.

Abrir la perspectiva "Broker Application Development", y el flujo. Se ve algún error (una marca roja en el flujo, a la izquierda) ? En el cuadrante inferior derecho, hay un tab, "Problems". Darle click y se verá la lista de problemas no resueltos.

El fichero ".log" del directorio ".metadata" (en el workspace) puede tener información útil.

También están los logs del Bar File Editor (User / Service Log; tab abajo, a la derecha).

• mqsicreateconfigmgr [params]
• mqsistart cfgmgr_name
• for all required Brokers do :
  • mqsicreatedb [params]
  • mqsicreatebroker [params]
  • mqsistart broker_name

• mqsilist
• for every Broker in List do mqsistop broker_name & mqsideletebroker broker_name

  Kill BIPSERVICES if it does not end in few minutes ...

• mqsistop cfgmgr_name & mqsideleteconfigmgr cfgmgr_name
• for all DB do mqsideletedb db_name
• dspmq
• for every Qmgr in List do endmqm -i qmgr_name & dltmqm qmgr_name

When considering the storage usage of message flows, then the main process to monitor is the DataFlowEngine. The bipservice process is a very small process that monitors (and restarts if necessary) the bipbroker process. The bipbroker process is designed to monitor and administrate the execution groups. It performs such functions as handling deploy requests and communicating with the Configuration Manager. It does not process any message flows, but its size is governed by the size of the deploy requests that are being received. The biphttplistener process is only used when webservice functionality is being used (when the HTTPInput, HTTPRequest and HTTPReply nodes are in use). Therefore, if the message flows deployed do not contain such resources, then this should not increase by any significant amount.

url

Top

Create an ODBC connection for the broker database:

1. Open Control Panel - Administrative Tools - Data Sources (ODBC).
2. In the ODBC Data Source Administrator, select the "System DSN" tab, and click Add.
3. Select IBM DB2 ODBC DRIVER from the list of driver options that are displayed in the Create New Data Source dialog.
4. Click Finish.
5. From the pull-down list, select the WBRKBKDB database in the Database alias field.
6. Enter the same name in the Data source name field. A description can be added to indicate the purpose of the database, but this is optional.
7. Click OK to complete adding an ODBC reference for this database.
8. Close the ODBC Data Source Administrator.

MB Basics, SG24-7090-00, page 136, 151/262.

When you define a data source for Oracle, choose the driver:

Complete these steps to configure the driver:

1. Enter the DSN name, description, and server name (where the server name is the "Service Name" that resolves to a "Connect Descriptor", for example through a mapping in the TSNAMES.ORA file).
2. Select the appropriate Oracle client version from the drop-down list.
3. Ensure that the Enable SQLDescribeParam box is checked. This parameter is on the Advanced tab of the driver settings.
4. Create a new registry subkey for each of your DSNs that reference an Oracle database. Use REGEDIT to navigate to the correct location:
   HKEY_LOCAL_MACHINE SOFTWARE ODBC ODBC.INI
5. Right-click the DSN, and select New > String Value. Specify WorkArounds for the string, and set the value to 536870912.

"Configuring an ODBC data source on Windows" (v 6.0) url url url

WS MB v 6.0, "Configuration, Administration and Security", page 94 [102/474]

Documentació ODBC DataDirect & Trouble Shoot (ivtestlib).

Trassa ODBC (AIX) :

Emir:

Top

To configure the JDBC, all we have to do is to create a new configurable service

Here DB2_LA is the name which developer will use to make a JDBC connection to the database in the java Compute node, as:

Now lets see how to configure DB2 with the Broker. If you run the command

you will be able to see that the console returns some configuration data in which you will identify the Connection URL Format :

We will have to add this parameters to our JDBC connection too, so lets start with the commands.

We have to create the security profile so that the broker uses it to authenticate with the database:

Once the security profile is created, we have to attach this to our JDBC:

Now we just need to set the database name post number host number...etc

To add the connection url:

To add the database name host name port number:

By this time you should be able to identify that the -n is the name of the property and -v is the value of the property...

At the end your configuration parameters should look like

After setting up all the parameters in place, all that we have to do is to just run the flow. If it throws an exception the primary things you have to check are:

• JAR folder has to contain Common.jar ,db2jcc.jar ,db2jcc_license.jar
• the security Profile credentials are actually valid and configured correctly
• you are able to make a JDBC connection to the database via a Java Program
• you dit screw up the connection url format

Screwing up the connection URL format:
DO NOT REPLACE THE [USER] OR [DATABASE NAME] OR ANY OTHER THINGS PLACED IN THE [] BRACKETS... THE BROKER WILL DO THIS FOR YOU.
If you still have a problem take a startup trace and try to debug it by searching for DB2_LA and reading the adjacent text

url

The Oracle database administrator controls user access to Oracle databases. The WebSphere Message Broker does not provide any special commands to administer an Oracle database.

MB v6, "Configuration, Administration and Security", page 29 [37/474]

When you create a broker, the database tables required by that component are created in the default schema associated with the user ID used to access that database. You specify this user ID on the create command (mqsicreatebroker). For Oracle, the default behavior is for the schema name to default to the user ID used to access the database.

MB v6, "Configuration, Administration and Security"

WebSphere MQ Integrator Broker does not demand a particular schema or set of tablespaces for keeping broker information. When you create a broker, the tables are created in the database with an ownership defined by the user identifier specified on the command line (the user ID must already be known to the database).

MQI Broker for Solaris, v 2.1, "Installation Guide", page 71, tip7ac05.pdf

The Oracle user ID that you use to store broker information needs the privileges: connect, resource, and create table. For example, the following is sufficient:

and optionally:

MQI Broker for Solaris, v 2.1, "Installation Guide", page 72, tip7ac05.pdf

SC :

To authorize access to an Oracle database:

1. Logon to the database using SQL*Plus as the Oracle DBA (database administrator).
2. Modify the privileges of the user ID that you have specified for database connection to ensure that the broker can successfully access the database. The user ID needs quota in its tablespaces and sufficient privilege to allow the creation of, and updates to, the broker tables:
   GRANT CREATE SESSION TO dbid; GRANT CREATE TABLE TO dbid;

MB v6, "Configuration, Administration and Security", page 104 [112/474]

SQLPLUSW (Win Cmd Line) or sqlplus (AIX)

Comando para crear usuarios desde SQLplus (usr=nom@sid) :

Per a crear un usuari, ens cal saber el nom i tamany del TABLESPACE ...

El "grupo" creado por Oracle es ... ora_dba (Win) or dba (AIX).

Obtenim que els Tablespaces han de ser DAT i NDX, de 2 GB i 1GB respectivament.

Llibre ?

• WS MQI Deployment and Integration, SG24-6509.pdf
  See 4.4, page 138 ("Creating and configuring the broker") + Appendix "C" (Oracle 8i installation and configuration on Solaris)

• WebSphere MQ Integrator Solaris Installation Guide

• MB v 6.0, "Configuration, Administration and Security"

El driver de Oracle es v 10.02.00.01 - quina versió de ODBC requereix ?
La versió de ODBC es 2.8.2 : HKLM/Software/Microsoft/DataAccess

Oracle FAQs

For the installed database drivers for Oracle, entries that contain driver locations and parameters are created under the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI

For Event Log information, an entry is added under the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\BIPv600

Start a listener as a background task by using WebSphere MQ Services:

• a. Click Start -> Programs -> IBM WebSphere MQ -> WebSphere MQ Services
• b. Expand the left pane and select the queue manager WBRK_CONFIG_QM to display its services in the right pane.
• c. If the listener is displayed, right-click it and click All Tasks -> Start. This starts the listener. If the listener is not displayed:
• d. Right-click the queue manager and click New -> Listener. A new listener is created with (default) transport type TCP and (default) port number 1414.
• e. Right-click the new listener and click Start. This starts the listener.

MB v 6.0 Configuration, Administration and Security, page 157, 165/474.

Before you start, you must complete the following tasks:

• Creating a Configuration Manager
• Create and start a listener for the Configuration Manager

Create a domain connection in the workbench using the Create a New Domain Connection wizard. Enter a set of parameters to create a .configmgr file. The parameters contained within the .configmgr file are used to connect to the Configuration Manager, where you can view and edit your broker domain.

To create a domain connection:

1. Switch to the Broker Administration perspective.
2. Right-click in the Domains view, and click New Domain
3. In the Create a New Domain Connection wizard, enter:
   • The name of the WebSphere MQ queue manager that the Configuration Manager is using. This property is mandatory.
   • The host name or IP address of the machine on which the Configuration Manager is running (the default is localhost). This property is mandatory.
   • The TCP port on which the WebSphere MQ queue manager is listening (the default is 1414). This property must be a valid positive number.

   You can configure several domain connections in your workspace. Each domain connection has to address a different Configuration Manager, which needs to have a different WebSphere MQ queue manager, host name, or TCP port number. An error message is displayed in the wizard, if you try to create a second broker domain using the same queue manager, host name, and port number.

4. Click Next to begin the domain connection to the Configuration Manager. You cannot connect to a Version 2.1 Configuration Manager. An error is thrown, and you will not be able to populate the domain with brokers or topics, or connect to it using the workbench.
5. If you click Cancel, the Create a New Domain Connection wizard closes and a forced disconnection from the domain occurs.
6. After the domain connection has been made, enter:
   • The name of your Server Project. This is the container for your domain connection. If you have not already created a server project, you can specify the name of a new project here. The server project is created with the domain connection.
   • The Connection Name. This is the name you give to the .configmgr file that contains the parameters to connect to the Configuration Manager.

7. Click Finish to create the domain connection. The new domain connection is added to the Broker Administration Navigator view, under Domain Connections. Here the server project holds the .configmgr domain connection file. The view of the broker domain is displayed in the Domains view.

MB v 5.0 Configuration, Administration and Security, page 75, 83/288.

MB v 6.0 Configuration, Administration and Security, page 181, 189/474.

Before you start, you must have completed the following tasks:

• Create a physical broker.
• Connect to the broker domain.

Adding a broker to the broker topology creates a reference to the broker in the configuration repository; it does not create the physical broker. When you add a broker, be sure to use the same name that you used to create the broker.

To add a broker to a broker domain:

1. Switch to the Broker Administration perspective.
2. Right-click in the Domains view, and click New Broker.
3. In the Create a Broker wizard:
   • a. Select the broker domain to which you want to add the broker. If the selected broker domain is not connected, you are prompted to connect to the domain. Click OK. If you click Cancel at this prompt, the wizard remains open.
   • b. Enter the name of the broker.
   • c. Enter the name of the WebSphere MQ queue manager that the broker uses.

   Note:
   1) If the WebSphere MQ queue manager is on a separate machine, make sure that you have performed the steps listed in "Connecting components"
   2) You can associate a WebSphere MQ queue manager with only one broker, even if the brokers are in different broker domains.

4. Click Next.
5. Optional: Enter a short or long description for the broker.
6. Click Finish to add the broker to the broker domain.
7. You are, by default, prompted to deploy the updated publish/subscribe topology configuration.
   You only need to deploy the topology (either Complete or Delta) if you are using publish/subscribe and want to share publications or subscriptions.
   If you are not using publish/subscribe, click None. A deployment now (to associate the broker with the Configuration Manager), is not necessary; the broker is automatically associated with the Configuration Manager the first time a bar file is deployed.
   You can set user preferences so that you are not prompted to deploy the publish/subscribe topology. Instead, you can choose for either a complete or delta deployment to be performed automatically. Alternatively, if you are not using publish/subscribe, you might prefer to set the preference so that no automatic deployment takes place.

In the Domains view, the broker is added to the broker domain and a default execution group is added to the broker. Adding a broker to the broker topology creates security ACL groups, which give the user ID full control of the broker and its default execution group. These ACL groups exist until this broker is removed from the broker domain. This means that the user ID can be removed from the mqbr* groups, but the user still has the full control access level for the broker and its default execution group.

Next: Continue to add further execution groups to the broker if necessary. Then create, modify, or reuse message flows, message sets and other required files, and add them to the broker archive for deploying to the broker.

MB v 5.0 Configuration, Administration and Security, page 77, 85/288.

MB v 6.0 Configuration, Administration and Security, page 184, 192/474.

Para hacerlo desde una command line se utiliza el comando mqsicreateexecutiongroup con la opción -f. Una vez ejecutado este comando ya se pueden realizar los despliegues con el comando mqsideploy. También veremos que en el Toolkit aparece el broker en el dominio.

La sintáxis es la siguiente:

Por ejemplo:

Creating a message flow project
A message flow project is a container for message flows; you must create a project before you can create a message flow.

MB v 6.0 Message Flows, page 123, [131/1020].

Creating a message flow
Create a message flow to specify how to process messages in the broker. You can create any number of message flows and deploy them to one or more brokers.

MB v 6.0 Message Flows, page 126, [134/1020].

Deployment overview
Deployment is the process of transferring data to an execution group on a broker so that it can take effect in the broker domain. For deploying message flows and associated resources, the data is packaged in a broker archive (bar) file before being sent to the Configuration Manager, from where it is unpackaged and distributed appropriately.

MB v 6.0 Message Flows, page 419, [427/1020].

"Default WebSphere MQ resources created during configuration", page 98 [107/118], MB V 5 R 0 "Installation".

When you issue the command mqsicreatebroker, it grants put and get authority on your behalf to the group mqbrkrs for the following queues:

When you issue the command mqsicreateconfigmgr, it grants put and get authority on your behalf to the group mqbrkrs for the following queues:

"Securing WS MQ resources", page 2 [10/88], MB V 5 R 0 "Application Programming".

Used to display actual values.

The list of properties for an Execution Group is :

The list of properties for all services is {*** very large on v7 ***}:

Per exemple, per canviar el port on escolta el Debug, ferem servir :

Per canviar el tamany del Heap de la JVM :

This value must be in the range 16 777 216 to 8 589 934 592. Initial value = 134 217 728

Com es veuen les properties actuals ?
Use the mqsireportproperties command to display properties that relate to a broker or its associated configurable services.

url, url

Per exemple, per veure el Heap que té una JVM, ferem :

Per veure el mínim i el màxim a la vegada :

url (player)

Verify :

• that the broker environment is set up correctly; for example, that the installed level of JavaT is supported.
• MQ queues are defined and accessible.
• ODBC environment (if specified) is configured correctly.

url

• Installation and configuration
  • The number of prerequisite products has been reduced
    • WebSphere MQ V5.3.0.1 or later.
    • ODBC drivers for Cloudscape
  • The configuration manager no longer requires a database, because an embedded database is now provided.
  • The configuration wizard has been improved.

• Migration
  • There is now a single command, mqsimigratecomponents, to migrate components rather than the multiple commands in previous versions of the product.
  • A key improvement is the ability for multiple versions of the product to coexist in a single operating system image.

• Transformation technology
  • ESQL enhancements
  • Java Compute Node
  • JMS Input/Output Node
  • Mapping Node
  • MQGET Node
  • Timer Control Nodes
  • XSLT enhancements

• Message processing
  • The performance of parsing and streaming has been significantly improved to allow greater throughput, especially of large messages.
  • Pre-built message definitions are supplied for some common industry message formats such as SOAP envelope, SAP IDoc header, and MIME header.
  • A new WSDL importer is provided to simplify the calling of Web services from within flows. A new MIME parser is provided to allow the parsing of SOAP with Attachment, RosettaNet, and TLOG messages.
  • Most of the remaining XML schema restrictions are now lifted
  • There are improvements to the COBOL and C importers
  • The IDOC parser is now better integrated in to the development toolkit. An IDOC domain parser is provided.

• Performance

• Web services support
  • WSDL generation is more flexible, and WSDL can also be imported to create a corresponding message model.
  • A WSDL validator allows verification that Web services comply with the Web service Interoperability (WS-I) Basic Profile.
  • Support is included for SOAP 1.1 and SOAP 1.2.
  • SOAP with Attachments (SwA) is supported via a new MIME domain.

• Administration and management
  • All resources deployed can be tagged to version, author, and other useful information in addition to the standard complied time and deployment time attributes.
  • A number of new and extended command line utilities are provided
  • Improvements have been made to multiple commands, such as mqsideploy, mqsilist, and mqsicreatebroker.
  • A new Java administration API enables a program to control broker domains through a remote interface known as the Configuration Manager Proxy.
  • You can now restart the broker database without having to stop and restart the broker.

• Security
  • Communication between the toolkit and configuration manager has been extended to allow the use of SSL for added security.
  • The HTTP transport has been extended to support HTTPS to allow added privacy and security.

• Additional improvements
  • Platform support
    • The Configuration Manager is supported on all of the broker platforms including z/OS, UNIX, Linux, and Windows. This combined with the Configuration Manager Proxy API provides greater flexibility to the way you configure and manage your MB components.

    • You can install the development toolkit on Linux in addition to Windows.

    • Database support on Linux Intel is extended to include Oracle, in addition to DB2 Universal Database.

  • Tooling

    The development toolkit in which message flow development, debugging, deployment and some operational management take place is now based on the latest release of Rational Application Developer and Eclipse. As part of this upgrade, new XML editors are provided.

  • MB on z/OS
    • You can now customise the JCL files that are used to create and start the broker, configuration manager, and user name server on z/OS, using an ISPF edit macro.

    • STDOUT and STDERROR for each of the broker, configuration manager, user name server, and any commands that are run is now directed to the JES Spool rather than to the HFS. This means that it is possible to monitor progress of broker-related jobs in real time though the job log.

  • Publish/subscribe

    MB V6 now supports the PGM multicast protocol. There are two implementations available: PGM/IP, and PGM UDP encapsulated.

• llibre "basiks"
• korreus
• kurs Lourdes

Para el desarrollo de los procesos de MB se usa el MB Toolkit. Consta de dos partes :

• entorno de desarrollo de WSAD Integration Edition
• conjunto de plugins de MB que se instalan adicionalmente

Al arrancar el entorno de desarrollo, se debe seleccionar una de las perspectivas :

• desarrollo de Aplicaciones de intermediario
• administración de intermediarios

Al obrir el Toolkit per primer cop, hem de fer :

• 1-o : crear un Dominio
  *** Abrir Navegador de la Administración de Intermediarios ***
  Dominio := brokers conectados al CfgMgr ;
• 2-o : conectar Toolkit al CfgMgr (agregar Broker al Dominio)
  Right-click on Topology + "New" Broker

• Archivo -> Nuevo -> Proyecto de flujo de mensajes
• Nombre del proyecto
• Directorio para el proyecto

El flujo de mensajes es el componente que contiene la lógica del flujo a ejecutar.

• Archivo -> Nuevo -> Flujo de mensajes
• Nombre del flujo
• Nombre del proyecto

• Abrir perspectiva "administración de intermediarios"
• Archivo -> Nuevo -> Otros
• Seleccionar "Message Brokers" en el menu de la izquierda
• Seleccionar "Archivo de datos antiguos de intermediario"
• Escoger el boton verde "Añadir"
• Se crea "nom.bar"
• Difundir "nom.bar" : Servidores + "nom.bar" + "Difundir"

Por ejemplo, para modificar "Aditional Instances" :

• descomprimir el BAR
• editar Broker.xml
• usar mqsiapplybaroverride.bat

• wmbt.exe -cleanup
• wmbt.exe -???
• cambiar lenguaje por defecto en la toolkits.
  Editar el fichero eclipse.ini e introducir la entrada:
  -Duser:language=EN

Top

• change SYSTEM.DEFAULT.LOCAL.QUEUE max msg size to 100 MB.
• set al Transmit Queues to trigger the Sender channel.
• MQ log has to be bigger than 1 MB for minimum deploy.
• user wbrkadm has to be in mqm group; user oracle has to be in mqbrkrs group.
• Use wmqiusr user : You cannot run WSBIMB using the default Administrator account

  WSBIMB Basics RedBook, SC24-7090-00, page 49

  Before you install WebSphere Message Broker runtime components or the Message Broker Toolkit, you must log on with a user ID that has Administrator authority, that is not the Administrator ID.

  MB Installation Guide, GC34-6621-02, page 49 [67/176]

• Broker Event Log
• if Broker reports (Java) OutOfMemory, then use mqsichangeconfigmgr -j 512
• to turn "off" Domain security, use mqsichangeconfigmgr -l 0

• mqsilist
• mqsistop for each Broker
• mqsideletebroker BrokerName -q
• mqsistop CfgMgrName
• mqsideleteconfigmgr -n
• mqsideletedb all database names
• delete queue managers
• delete .metadata at Eclipse directory

WSBIMB Basics RedBook, SC24-7090-00, page 217

• delete HKLM\software\ibm\WebSphereMQIntegrator\2\TKT01BK\ registry key
• delete c:\Documents and Settings\All Users\Application Data\IBM\MQSI\components\TKT01BK\
• restart Guindous

Display broker JVM heap size

Display Execution Group JVM heap size

Modify and restart broker:

Changing the max JVM heap size for the broker and execution group

Top

There are two recommended mechanisms that let you run multiple copies of a message flow within a Message Broker. These are the use of the Additional Instances attribute and the assignment of a message flow to more than one execution group.

The number of instances for a message flow has to be specified in at the message flow level in the relevant Broker Archive (BAR). To do this:

• select the BAR in the Broker Administration Navigator Perspective in the Toolkit to change the number of instances for a particular message flow
• select the Configure tab, required message flow, and specify the number of instances required in the Additional Instances box
• deploy the BAR to the broker to make the changes effective

developerWorks Dunn

Details here, as max=256

As it is already set in the BAR file, you can use "mqsiapplybaroverride(bar)" and then "mqsideploy(bar)".

Top

• [1] create a common message header (as part of the payload) that is always logged
• [1] always test end-to-end performance early
• [1] when performance is key, select the best performing transformation option; ESQL first, then XSLT.
• [1] MB uses "on-demand" parsing, so header has to have all required info to maximize performance.
• [1] place infrastucture logic (as security, logging levels, client application identity) in a header which is separate from the body of a message.
• [1] if there is no canonical format, then the MB is being used for point-to-point integration, which increases cost to add new requestors and providers.
•   always check "Event Viewer" for MQ resources missing (defined to MB flow).
• [coding] mandatory use of "Version"
• [coding] do not place TRACE node in the middle of the flow
• [coding] be prepared for multi-threading the flow
• [other] do not use DEBUG - use User Trace only

Links :

• [1] SSDW 2.3 ESB Best Practices v0 r2.ppt [\\WS-BI-MB\RedBooks_MB_and_Best_Practices]
• [2] 2268_Designing for Performance.ppt [\\WS-BI-MB\RedBooks_MB_and_Best_Practices]
• [3] WebSphere Message Broker V6 Best Practices Guide: Bullet Proofing Message Flows (Draft)
• [4] Improve the performance of your message flow - Dunn : mqsitraceanalyse.pl !
• [5] Message Broker development and deployment best practices [+ resources]
• [6] TMM19, \\SWU\BCN_WSTC_2008\

Mind there are MQ Best Practices also ...

mqsibackupconfigmgr requirements :

• CM should be stopped. No bid deal, add mqsitop to the script.
• But it also wants there to be no deploys in progress.

How to recover a damaged CM

Can't use "create new CM" + "adopt broker(s)", because ...
Broker adoption and synchronization doesn't quite discover everything about a running broker: particularly, it doesn't synchronize deployed artefacts that aren't message flows (i.e. dictionaries, JARs, XSL and adapter connection files).

See Running the broker domain management sample :

So your output is:

• a series of scripts generated by MS03 to rebuild the qmgrs.
• from version control a list of changes/additions to the relevant qm.ini
• a list of brokers (broker name) source config mgr proxy/version control
• a list of execution groups (names) per broker: source config mgr proxy/version control
• a list of bar files per execution group/per broker: source config mgr proxy/version control
• a list of collectives with their members : source config mgr proxy/version control
• a list of topics : source config mgr proxy/version control
• a list of durable subscriptions per broker : source config mgr proxy/version control

Your list of operations for recreating the environment would be:

• ready the hardware with OS and Software (MQ, Message Broker, DB)
• create the qmgrs (should be from version control)
• rebuild the qmgrs (MS03 from version control) + changes (qm.ini)
• restore permissions on mq running the setmqaut scripts from version control (source:MS03)
• recreate the brokers and config mgr using scripts from version control
• add the brokers to the domain using scripts from version control
• recreate the execution groups using the config mgr proxy and scripts (version control)
• recreate the permissions on the config mgr using scripts from version control (mqsicreateaclentry)
• redeploy the bar files using the config mgr proxy and scripts from version control
• redeploy the topics using the config mgr proxy and scripts from version control
• recreate and redeploy the collectives using the config mgr proxy and scripts from version control
• restoring the durable subscriptions

V7:

An interesting variation:

On Windows, the local error log is the Windows Event log (Application view).
On UNIX, the local error log is the syslog. Where syslog messages are sent depends on how you configure your UNIX system. See /etc/syslog.conf
On z/OS, the local error log is the operator console.

MB v5 R0 Diagnostics, page 113 [121 of 152]

[hlh] /var/wbimb/user.log

AIX, cat /etc/syslog.conf :

"Linux and UNIX systems: Configuring the syslog daemon", Troubleshooting, page 114 [122/188]

Top

Sample:

Setup MB envir : "c:\Program Files\IBM\MQSI\6.0\bin\mqsiprofile.cmd"

Top

MB (installation) troubleShooting :

• nivel del MQ, del Broker y del Toolkit
• FDCs de MQ, errores de MQ en AMQERRnn.LOG, errores de Broker en el syslog
• developerWorks Jun Tao Cui article - "performing health checks for MQ and MB"
• SG24-7283 pdf - managing WebSphere Message Broker resources in a production environment
• abend file generated in MQSI_WORKPATH/errors directory when EG terminates on a severe error {WMB_troubleshooting.pdf, Prasad Imandi}
• MB Must Gather

See also flow troubleshooting

Top

Need a tool to generate it .. starting with the MB log ...

This icon starts this BAT

Used to

• deploy
• create/delete execution groups
• start/stopmessage flows
• display and manage a broker domain
• write, save, run and replay configuration scripts

As Verifying WebSphere Message Broker V6 without using the toolkit.

See Customizing the CMP API Exerciser and Secrets of the Configuration Manager in WebSphere Message Broker V6.

Descr (player)

• Version.
• Fix packs applied.
• Interim fixes applied.
• A list of the components installed. Include details of the number of machines and their operating systems, the number of brokers and the machine on which they are running, and the existence and details of any User Name Servers.
• The .zip file obtained by exporting your workspace and appropriate message flows and message sets. This action is performed from the Workbench or Control Center.
• Details of the operation that you were performing, the results that occurred, and the results you were expecting.
• A sample of the messages being used when the problem arose.

Must Gather info

Open Information Center and enter "Configuration manager proxy samples" search argument ...

Developing applications, samples

• si tenim un node d'entrada MQ, s'hi fa un MQget() amb timeout de 5 segons. Aquest valor es pot canviar ?
• you can have started "Resources Statistics" on a given flow or resource, and forgotten. Is there any way to display the status os the statistics on all EG's ?
• a flow can have multiple instances in a given deployment. How to know how many instances does a specific flow have running in a given execution group ?

• a flow can have multiple instances in a given deployment. How to know how many additional instances of a flow can I deploy in a given execution group ?
  • com mirar quins requeriments de memoria te un fluxe ?
  • com mirar quina disponibilitat de memoria te un grup d'execucio ?

• Jason parser for MB

• Es pot treure el fitxer BAR de un broker i posar-lo en un fitxer ?

• Com es defineix la ubicació del Log de MB sota SuSE ?
  Mentre ho trobem, fer servir /var/log/messages !

• Quines característiques té la base de dades del Broker ? Resposta
  Nom de la/les taula/es, tipus d'accés, etc [remember indy]

• Criteri per ficar un fluxe en un grup d'execució o crear-ne un altre

• De un fitxer.mset surt : o be un fitxer.dictionary (MRM domain) o un fitxer.xsdzip (XMLNSC domain)

• Com fer que un BAR no inclogui JAR files, que fan que el BAR passi de 15 KB a 2 MB !

• Criteri per fer servir un sol Broker o fer-ne servir dos ?
  Resposta : administració

• Hem fet mqsiCreateConfigMgr i mqsiCreateBroker sense UNS. Després volem fer servir el UNS. Després de CreateUserNameServer n'hi ha prou amb fer mqsiChangeConfigMgr -s i mqsiChangeBroker -s ?
  Resposta : yes

• Un Broker pot compartir gestor de cues amb en CfgMgr. Si ens cal UNS (user name server), pot fer servir el mateix gestor ?
  Resposta : yes

• Com crear un Execution Group des una Command Line ?
  Resposta : mqsicreateexecutiongroup.bat

• Si el contingut de un Domini el coneix només que el seu CfgMgr ...
  Poden dos CfgMgr's incorporar el mateix Broker ? No
  Pot un Broker formar part de 2 dominis ? No

  El UUID es genera quan el Broker entra en un domini, és a dir, s'assigna a un Cfg Mgr.

• BIP1536: the CM was unable to register for internal subscriptions with the broker ...
  Causa : el usuari amb el que corre el CfgMgr no es el mateix que el usuari del Broker.

• Como saber :
  • que brokers tiene un CM en su dominio ?
    Usar GUI del Toolkit para conectar al CfgMgr.
  • a que dominio (nombre CM) pertenece un broker ?
    No se puede.

• Per on surt un "println" ?

  Para ver la salida the System.out.println hay que modificar el Broker Service:

  1. Start -> Control Panel -> Administrative Tools -> Services
  2. Right-click en el servicio de Broker ("IBM WebSphere Message Broker component <broker>") -> Properties
  3. Log On -> Seleccionar "Logon as Local System Account"
  4. Seleccionar "Allow service to interact with desktop"

  En 6.1 va a ser distinto: el Broker crea un fichero "console.txt" en MQSI_WORKPATH.

• Es pot importar un fitxer ".xsd" al MB ? ( as ICS )
  Es pot fer servir un ODA (Object Discovery Agent) amb un Adapter per MB ?

• Com fer servir textes identificatius / versionat des ESQL

  $MQSI keyword = value MQSI$

• Com fer servir UPD's ?

  url

• "BIP2580E" =
  Resposta : url, from FAQs : This error occurs if the datasource name is blank in a Node that interacts with a database.

  Solution : set "Origen de Datos" of the Compute node !

• com saber de quina cua arriba un missatge a un fluxe ?
  Resposta : llegir InputRoot.MQMD.SourceQueue [Tania]

  Quins altres camps té InputRoot.MQMD ?
  Resposta : llista de propietats accessibles

• al instalar el Toolkit 6.0.0.1, en escollir "Nombre de directorio", si es posa "llarg", diu La via de acceso del directorio debe tener menos de 48 caracteres Why ?

• com es fa servir el CMP, Configuration Manager Proxy ?
  CMP is an application programming interface that your applications can use to control broker domains through a remote interface to the Configuration Manager.

  CMP Programming, page 3, 11/56.

  Interactive mode (-i flag) : INST_DIR\sample\ConfigManagerProxy\StartDomainInfo.bat c:\myConfigMgr.configmgr -i Stop : Ctrl+"C"

• com saber la versió de un fluxe que corre en un Execution Group (console command) - mqsireadbar -b BARFILENAME (windows & Linux only)
  [VMsag] Directory of C:\Program Files\IBM\MessageBrokersToolkit\6.0\eclipse mqsicreatebar.exe mqsicreatemsgdefs.exe mqsicreatemsgdefsfromwsdl.exe mqsimigratemfmaps.exe mqsimigratemsgflows.exe mqsimigratemsgsets.exe mqsireadbar.exe

  La sortida té aquesta forma :

  > mqsireadbar -b AE_ADD_RMV_HDR.bar Archivo BAR: AE_ADD_RMV_HDR.bar Entrada de BAR: AE_RMV_HDR_RFH2.cmf Fecha y hora de modificación: 27-dic-2006 12:05:12 Entrada de BAR: AE_ADD_HDR_RFH2.cmf Fecha y hora de modificación: 27-dic-2006 12:05:12

• com fer que un node de trassa de dins un fluxe no tregui cap trassa en el entorn de producció ? (*)

  Compte MB v 6.1 :
  Another new runtime property in MB V6.1, exposed through the Configuration Manager Proxy and the mqsichangetrace command, is a toggle to enable and disable trace nodes in a message flow or execution group.

• com saber la versió del MB ? (as DB2LEVEL or MQVER or JAVA -VERSION) : mqsiservice -v

• com saber quin Queue Manager fa servir un Broker determinat ? mqsilist llista parelles MB - MQ.

• com saber si una instalació fa servir Name Server ? Surt llistat amb mqsilist.

• com saber quins Grups de Execució te un Broker determinat ? mqsilist BrokerName els llista

• com saber quins Fluxes hi ha en un Grup d'Execució de un Broker determinat ? mqsilist BrokerName -e NomGrupExecucio els llista

• com saber quina Base de Dades fa servir un Broker ?
  Creo que la base de datos del Config Mgr tiene que ser DB2. Te sugiero abrir un command line prompt, 'db2cmd', 'DB2 LIST SYSTEM ODBC DATA SOURCES'. Te va a dar la lista de bases de datos registradas con ODBC. Tal vez por el nombre puedas reconocer cuales son del CM y Broker. Otro lugar para buscar seria el Registry. HKLM -> Software -> IBM : mira en los registros de integrator.

  Y en Oracle ? Y en AIX ? Nos es transparente !

• Com se sap si estem fent servir Derby ?
  Si al crear el Config Manager NO ES POSA nom de Base de Dades, es fera servir derby.
  C:\Program Files\IBM\MQSI\6.0> mqsilist BIP8099I: DbInstMgr: DatabaseInstanceMgr6 - BIP8099I: Broker: GAS_BROKER - QM_MB BIP8099I: ConfigMgr: GAS_MB - QM_MB

  Aixo es reflecteix en aquest camp buid :

  HKLM\Software\IBM\WebSphereMQIntegrator\2\GAS_MB\CurrentVersion\DataBaseName = " " ;

  Using Derby (under Windows)

• Com veure les caraterístiques del Derby ?
  C:\Program Files\IBM\MQSI\6.0> mqsilist DatabaseInstanceMgr6 BIP9814I: DB2GAS - DB2 - N/A BIP8071I: Successful command completion.

• com es fa per a que els noms de les cues de entrada i/o de sortida de un fluxe no s'hagin de escriure en el propi fluxe (as MQinput node), sino s'agafin de un fitxer extern ?

  Com fer que un fluxe agafi uns parametres (noms de cues, per exemple) en un entorn (desenvolupament) o uns altres en un altre entorn (producció) ?

  Solució : deployment descriptor : mqsiapplybaroverride

  url, refers to url; url.

• s'han de desplegar tots els fluxes després de migrar de versió ? No : eren a la BD del CM (tots) i a la dels broker (cadascun els seus).

• al "Event Log" hi ha un missatge "Component Integrity Check failed" - que es ?
  Puc executar aquesta utilitat des una Command Line ?
  mqsistop <brokername> + mqsistart <brokername>
  Mirar si hi ha algun flag per fer "només" la verificació ...

• quines característiques ha de tenir el Usuari especificat al crear el Cfg_Mgr i/o un Broker amb "-i usuari -a clau" ?

• les caraterístiques que posem, per exemple amb mqsichangeconfigmgr -j 512, com es poden veure (els seus valor actuals) ?

  Emir : HKLM -> Software -> IBM -> WebSphereMQIntegrator -> ConfigMgr :
  NTDomainAware & MaxJVMHeapSize !

  I en AIX ? /var/mqsi60/registry/<nom broker>/CurrentVersion

  mqsireportproperties

• desplegament RAD ?

• WSAD goes rational ?

• com s'instala messages.html ?

• com es llegeix un "Abend" i/o un Dump de WSBIMB\errors ?

• que és "MRM domain" ? MRM = message repository manager

  MRM enables messages that are not self-defining to be parsed for use by the broker. MRM allows definition of "Custom Wire Formats". CWF

• com ficar més memoria per aplicacions al W2003 ?

  boot.ini + /3GB

• JVM : n'hi ha una per Execution Group. Quanta memoria agafa cadascuna, per defecte ?

  Resposta : on v6.0 this is 256Mb for the broker component.

  Si tenim Out Of Memory, - Heap Size -, podem fer servir mqsichangeproperties !

• com aconseguir que un fluxe tingui el mínim de ocupació de memoria possible ?

• si faig servir sub-fluxes, es comparteixen dins un grup d'execució ? o cada "deploy" porta la seva copia ?
  No hi ha SF al RunTime ! Només a TKT ...

• What is the difference between an ESB and Message Broker ?

• cursos i preguntes : url

• Tracking a message with user exits in MB
• Managing WebSphere Message Broker Resources in a Production Environment [pdf, redbook]
• MB v 6.1 Administration (player).
• modeling tagged fixed length data in WMB ; mqseries.net
• MB utility trace

• In the spotlight
• Planned maintenance
• Education
• General self-help resources

In the spotlight
1. IBM WebSphere Message Broker V6.1 Software Announcement Letter
WebSphere Message Broker V6.1 is the solution for clients who need an Enterprise Service Bus (ESB) that delivers connectivity and transformation across heterogeneous IT environments.
http://www.ibm.com/support/docview.wss?acss=wmb121007rs=849&uid=swg27011128
2. Problems and solutions when migrating to WebSphere Message Broker V6.0 and V6.1
Provided to help customers get the latest information when performing a migration from a previous version of the product.
http://www.ibm.com/support/docview.wss?acss=wmb121007rs=849&uid=swg21255570
3. IBM Remote Agent Controller description and answers
Describes the RAC and answers some common questions.
http://www.ibm.com/support/docview.wss?acss=wmb121007rs=849&uid=swg21181268
4. SupportPacs:
a. IA9O: WebSphere Message Broker - SOAPEnvelope and SOAPExtract nodes
This SupportPac includes two new nodes, the SOAPExtract node and the SOAPEnvelope node. They can be used to simplify the processing of SOAP messages in WebSphere Message Broker.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg24014070
b. IA0F: WebSphere Message Broker - IDoc parser for SAP tools update
Tools to help with the creation of message sets for use with the inbuilt IDoc parser of WebSphere Message Broker V6.0.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg24000623
c. IA9Y: WebSphere Message Broker Toolkit - Map to ESQL Plug-In
This SupportPac provides an Eclipse Plug-In for the WebSphere Message Broker Toolkit, which converts a message mapping file (extension .msgmap) into ESQL for use in a Compute node.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg24017156
d. IA9Z: WebSphere Message Broker - Job Execution Node
Invoke operating system commands , Windows batch files, Unix shell scripts from within the message flow. User may also want to schedule the jobs at specific Time/interval/frequency.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg24017225
5. Monitoring message flow performance with the WebSphere Message Broker Explorer Accounting and Statistics facility
The new WebSphere Message Broker Accounting and Statistics facility can help you monitor message flow performance and resource usage of a broker or execution group at the message flow, node, or terminal level, and can thus be a tremendous help in solving performance and resource utilization problems.
http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html?ca=dnb-wmb121007
6. IBM Thread and Monitor Dump Analyzer for Java Technology
A tool that allows identification of hangs, deadlocks, resource contention, and bottlenecks in Java threads.
http://www.alphaworks.ibm.com/tech/jca?Open&ca=dnb-wmb121007
7. Integrating WebSphere DataPower XML Security Gateway XS40 with WebSphere Message Broker
A WebSphere DataPower XML Security Gateway XS40 can add a number of benefits to a WebSphere Message Broker environment. This article shows how the DataPower XS40 enhances a Message Broker flow with WS-Security, with security of the connection to Message B roker provided by HTTPS. The DataPower XS40 protects the SOAP messages sent to and produced by Message Broker via WS-Security encryption of the SOAP body. You can also use the WebSphere DataPower Integration Appliance XI50, which has the same functional c apabilities plus additional integration features.
http://www.ibm.com/developerworks/websphere/library/techarticles/0710_crocker/0710_crocker.html?ca=dnb-wmb121007
8. Redbooks publication (draft): Using WebSphere Message Broker as an ESB with WebSphere Process Server
The purpose of this book is to point out the ESB capabilities of WebSphere Message Broker and how they can be leveraged with WebSphere Process Server.
http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg247527.html?Open&acss=wmb121007

Planned maintenance
1. Fix Pack links
This provides links to the latest available maintenance for the Message Broker family products.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg27006041
a. Download 5.0.0.10 the latest Fix Pack for V5.0
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg21268586
b. Download 6.0.0.6 the latest Fix Pack for V6.0
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg21288996
2. Recommended fixes for WebSphere Message Broker Toolkit
Recommended fixes is a comprehensive list of recommended updates for WebSphere Message Broker Toolkit.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg27009742
3. Detailed system requirements
Identifies the supported software options by operating system for the WebSphere Message Broker products.
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg27006551

Education 1. IBM Education Assistant content for WebSphere Message Broker
Access tutorials, and resource links to help you successfully use IBM products.
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.wmb_v6/wmb/6.0/Overview.html&acss=wmb121007
2. Course list: WebSphere Message Broker
Select a course for description, schedule, and enrollment information, or see a list of all course categories.
http://www.ibm.com/developerworks/websphere/education/enablement/curriculum/c-wmessage.html?ca=dnb-wmb121007
3. Technical Exchange Webcasts
Take full advantage of your product. Join us as technical experts share their knowledge and then answer your questions. Visit this site often to see upcoming topics and to review previously recorded webcasts.
http://www.ibm.com/software/websphere/support/supp_tech.html?acss=wmb121007
a. Webcast replay: WebSphere Message Broker - Common Problems and How to Resolve Them
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg27010913
b. Webcast replay: Advanced ESB : Using Publish and Subscribe with WMB
http://www.ibm.com/support/docview.wss?acss=wbm121007&rs=849&uid=swg27011177
4. developerWorks WebSphere Message Broker zone
Access the developerWorks page for downloads, learning resources and more.
http://www.ibm.com/developerworks/websphere/zones/businessintegration/wmb.html?ca=dnb-wmb121007
5. Information Center
http://www.ibm.com/software/integration/wbimessagebroker/library/?acss=wmb121007
6. Redbooks
http://www.ibm.com/support/search.wss?acss=wmb121007&rs=849&tc=SSKM8N+SS3GH2,%20SSKMAB&rank=8&dc=DA4A20+DA700&dtm
7. Service/Debug Trace Instructions
http://www.ibm.com/support/docview.wss?acss=wmb121007&rs=849&uid=swg21177321
8. Configuring syslogs
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.eb.doc/an04230_.htm&acss=wmb121007

General self-help resources
Here are some other ways that you can access WebSphere Message Broker self-help support information on the Web:
1. Support Page
Primary support resources for WebSphere Message Broker.
http://www.ibm.com/software/integration/wbimessagebroker/support/?acss=wmb121007
2. IBM Software Support Online Resources
Find out how online software support tools and resources can save you time, keep you informed, provide training, and help streamline your support experience! For example, learn how to use the Electronic Service Request (ESR) tool to manage PMRs online.
http://www.ibm.com/software/websphere/support/d2w.html?acss=wmb121007
3. IBM Support Assistant (ISA) Version 3
Download the IBM Support Assistant (ISA) Version 3, a free cross-product client application that increases your capacity for self-help.
http://www.ibm.com/software/support/isa/?acss=wmb121007
4. IBM Software Support Toolbar
This is a stand-alone application that allows you to easily search IBM.com for all types of software support content plus organizes the major areas of not only Software support, but the individual brand support sites into a concise application.
http://www.ibm.com/software/support/toolbar/?acss=wmb121007
5. IBM Software Support RSS Product feeds
These RSS feeds allow you to stay up-to-date with the latest content created for specific IBM Software products.
http://www.ibm.com/software/support/rss/websphere/849.xml?rss=s849&ca=rsswebsphere&acss=wmb121007
6. IBM Software Support Lifecycle page
The IBM Software Support Lifecycle policy specifies the length of time support will be available for IBM software.
http://www.ibm.com/software/support/lifecycle/?acss=wmb121007

Top

• FTM
• Gartner "Magic Quadrant for B2B Gateway Providers" [\\WS-BI-MB\Arquitectura, ESB]
• BizTalk - producte de la competencia, uSoft.
• TIBCO

• ESB developer resources page
  Technical resources to help you use WebSphere ESB as a flexible connectivity infrastructure for integrating applications and services to support an SOA.
• ESB product page
  Product descriptions, product news, training information, support information, and more.
• ESB information center
  All WebSphere ESB documentation, with conceptual, task, and reference information on installing, configuring, and using WebSphere ESB.
• WebSphere ESB documentation library
  ESB product manuals.
• ESB FAQs
  Basic questions and answers about the new WebSphere ESB product and its relationship to other WebSphere products.
• ESB support
  A searchable database of support problems and their solutions, plus downloads, fixes, and problem tracking.