Migracions de MB

Creo que lo mejor para el sistema de pre-produccion es crear el broker con su base de datos DB2, y no migrar nada. Una vez testeados los flujos, exporta todo (flujos y mensajes), se importan en pre-produccion y se hace deploy. En V5 y V6 basta con pasar el bar file de un entorno a otro.
Hace mucho escribí esto; creo que todavia se aplica a V2.1: IC04v21.pdf

All the Message Broker V5.0 or 5.1 broker development resources can be used "as is" in the Message Broker V6.0 Toolkit with the exception of user-defined extensions and mapping files, which require further migration.

Migrating to MB v6, SG24-7198-00.

• pre-requisites

• migrating the Toolkit :
  • install v6 toolkit
  • backup workspace
  • migrate any v5 mappings (mqsimigratemfmaps)
  • create a new workspace and import v5 data or connect directly to v5 workspace
  • v5 message flows are automatically converted to a v6 format when you first save them. This format cannot be read by the v5 toolkit.

• migrating the Configuration Manager in situ
  • install v6
  • stop v5 CM
  • mqsimigratecomponents
  • start v6 CM

• migrating the Configuration Manager to another machine that has DB2 installed
  • install v6 on new machine
  • create v6 CM, pointing it at existing CM's (DB2) data source
  • start v6 CM - DB2 on v6 machine is used to migrate DB2 data automatically
  • start deploy to all brokers so that the v6 CM can subscribe to broker status messages

• migrating a Broker
  Each part of the broker's configuration can be migrated separately.
  Upgraded database drivers : odbc.ini changes required on UNIX.
  • message flows
  • user defined nodes
  • message sets
  • Broker Archive Files
  • New Era Rules and Formats

MB v6 Migration.ppt

Migrating to MB v6, SG24-7198-00, 27.1, page 330 [356/620]

You can use the script /tmp/output.txt command to make a typescript of everything displayed on your terminal to the specified file (in this case, to /tmp/output.txt) on UNIX systems. The script ends when the forked shell exits.

• databases :
  • broker(s) database(s)
  • Configuration Manager database
  • New Era Of Networks database

  Use mqsilist + mqsistop + DB tools.

• Universally Unique ID (UUID)
  [Unix machines] In the /var/mqsi directory, issue the command tar cvf mqsiconfig.tar /var/mqsi
  This creates a tar file called mqsiconfig.tar that contains the contents of the /var/mqsi directory structure.

• message brokers Toolkit :
  • workspace
    Using Toolkit, select all projects, then File and Export into a Zip file. Then, copy to a secure external source location.
  • user-defined nodes/parsers

• preparing workspace resources for migration :
  • migrate user-defined nodes
  • download required SupportPacs
  • get third party resources for v6

• migrate tooling resources

  Populate the Message Broker V6.0 Toolkit workspace with the contents of the workspace backup zip file, rather than directly using the old workspace directory.
  Using Toolkit, select File, Import, Existing Project into Workspace.

url

Configuration Manager maintains the broker domain configuration, interfacing between the Toolkit and a set of executing brokers.

The Configuration Manager acts as the central repository for broker domain components, communicating with other components in the domain using MQ. It also deploys to the broker domain as a result of actions initiated through the Toolkit, and reports the resultant status messages back to the Event Log.

• mqsilist -a
  This lists all components that have been created on the system.

• mqsimigratecomponents ConfigMgr -c
  Premigration check to determine whether the component can be safely migrated

• mqsimigratecomponents ConfigMgr
  Causes the Configuration Manager's queues, registry, and file system information to migrate from Message Broker V5.0 to Message Broker V6.0.

• mqsimigratecomponents ConfigMgr -v
  post-migration check to ensure that the migration completed successfully and to confirm that correct queues exist and the registry is in the correct format.

• mqsistart ConfigMgr

  When you start the Configuration Manager for the first time after completing the migration process, it detects the domain information held in the DB2 of the Business Integration Message Broker V5.0 Configuration Manager and migrates it to the internal repository of the Message Broker V6.0 Configuration Manager.

  In this way, Message Broker V6.0 Configuration Manager thus controls the same broker domain configuration that Business Integration Message Broker V5.0 Configuration Manager used to control.

  Migrating to MB v6, SG24-7198-00, 21.1.1, page 392 [418/620]

  In order to associate all brokers in the domain with the new Configuration Manager, so that the brokers publish their status messages to the correct queue manager, a complete topology deploy is required on the second computer. Deploy the topology using either the Message Brokers Toolkit or the command-line interface. When the topology deploy has completed re-subscribing to the brokers in the domain, the brokers are managed by the new Configuration Manager on the new system.

  url

url

url

• migration preparation
  • review existing installation
    • dspmq - dislay MQ components
    • mqsilist - dislay MB components
    • mqsilist broker_name - display broker(s) details (execution groups)
    • verify DB is available
  • review logs
    • MQ : AMQERR01. url, url.
    • MB : see /etc/syslog.conf file for a line like user.info /var/log/user.log
    • DB2 : see .odbc.ini - url, url.
  • backup broker configuration
  • update .profile
  • update ODBC settings

• migrate broker :
  • logon with user including mqsiprofile
  • mqsimigratecomponents -c broker_name - run a pre-migration check on the broker
  • mqsimigratecomponents broker_name - migrate the broker
  • mqsimigratecomponents -v broker_name - run a post-migration check on the broker

• validate the broker migration
  • mqsistart broker_name
  • mqsilist -a
  • mqsilist broker_name - the command should display the same list of the execution groups as before migration.

• validate the migration : verify log files.

Migrating to MB v6, SG24-7198-00, 24.1, page 448 [474/620]

After completing the migration to Message Broker V6.0, perform verification tasks such as:

• Verify the components - list, start and stop the following:
  • Configuration Manager
  • User Name Server
  • Brokers

• Verify the development environment by:
  • Starting the Message Brokers Toolkit
  • Assigning and deploying the resources to brokers

• Check if the migrated message flows and message sets are working as expected

• Review the logs for problems

Migrating to MB v6, SG24-7198-00, 27.1, page 496 [522/620]

• DB2 UDB v 8.2
• MQ v 6.0

url

url

Resolving problems that occur when migrating or importing resources

Problem You delete the physical broker component before removing it from the broker domain in the toolkit. Now when you attempt to delete and add it back within the toolkit you are getting BIP1506E. This message indicates that the qmgr is already associated with another broker (the one previously deleted).

Cause The broker was physically deleted before it was removed from the toolkit broker domain, this was the reason for the incorrect data in the configmgr database.

Solution Launch the Config Manager Proxy API Exerciser:

1. Connect to the configmgr by specifying the host, listener port, and config manager's qmgr
2. Right click PubSubTopology
3. Select Remove References to a Previously Deleted Broker
4. Specify the broker name.
5. Add the broker to the domain.

url

To start the Configuration Manager Proxy API Exerciser (on Windows), click

Start > IBM WebSphere Message Brokers 6.0 > Java Programming APIs > Configuration Manager Proxy API Exerciser

url url

(1) Make sure Oracle is running :

altogether with its listener :

(2) Make sure in .odbc.ini (usualy at /var/mqsi/odbc/) you have the appropiate driver for Oracle :

Install CSD 03, and verify JVM 1.4 is used

To cancel the deploy operation, either :

• (a) right-click the broker in the Message Brokers Toolkit and select the Cancel Deployment option,
• (b) use mqsideploy with the -c option,
• (c) use the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application.

Qué s'ha de borrar ?

Si hacemos un mqsicreateexecutiongroup y recibimos este mensaje, Broker 'BKDESA01' was not found in the Configuration Manager repository.

Pregunta : cómo ver lo que hay en el repositorio ? (desde una command line / shell de AIX )