WebSphere Message Broker Services

In This Section:

Smooth Start

Is your company just starting with WebSphere Message Broker?

When properly implemented, Message Broker can act as an Advanced Enterprise Service Bus (ESB) by performing the data transformation, endpoint routing, and protocol conversion necessary to link the real applications and services that make up your IT infrastructure into a intercommunicating whole without creating dependence on the internals of the applications. Our experience will get your implementation off on the right foot with a clean base configuration and a well-established set of best practice policies and procedures.

Smooth Start deliverables:

  • WebSphere Message Broker will be installed on any of the WebSphere Message Broker supported systems - AIX, HP-UX, Linux, Windows, or zSeries
  • A WebSphere Message Broker Configuration Manager will be configured to support a single Broker Domain including logging, security, backup and recovery mechanisms.
  • A WebSphere Message Broker will be configured to support application connections via the WMB supported protocols including JMS (provider(s) of your choice), WebSphere MQ, HTTP, SCADA, etc.
  • A set of execution groups meeting your requirements will be created and configured on your broker system.
  • Optional: A WebSphere Message Broker User Name Server will be configured to support a single Broker Domain including publish and subscribe security if appropriate for your broker requirements.
  • The WebSphere Message Broker Toolkit will be installed and configured on up to 10 standard developer/administrator systems. Subject to system constraints and your ownership of the appropriate software, these Toolkit systems may share an Eclipse shell with any of the following products: WebSphere Integration Developer; Rational Application Developer; and WebSphere MQ Explorer
  • Eclipse Source Control Plug-ins will be installed on all WebSphere Message Broker Toolkit systems to connect the toolkits to any supported source control manager you own including, but not limited to Rational Clear Case, CVS, PVCS, and Microsoft Visual Source Safe
  • WebSphere MQ Channels will be created and tested between each of the configured systems.
  • The installation and configuration will be tested using standard IBM sample programs.
  • Procedures will be established for creating projects and the underlying objects in the WebSphere Message Broker Toolkit.
  • Procedures will be established for deploying code to the WebSphere Message Broker.
  • The MQSoftware Consultant will provide knowledge transfer related to WebSphere Message Broker to your administrators, architects, and developers.

Smooth Start prerequisites:

  • WebSphere Message Broker software purchased and delivered
  • Systems with the appropriate hardware and software resources for WebSphere Message Broker. If you are uncertain of this, see the MQSoftware Installation Planning Engagement.
  • Systems that will communicate have basic network connectivity; typically TCP, but SNA, DECNET, NETBIOS, and IPX are also acceptable.
  • A System Administrator for each of the systems will be available to provide appropriate administrative level logins.
  • Future Message Broker administrators are available for knowledge transfer.

Duration: +3 days depending upon the number of systems to be configured.

A rough formula is:
2 Days for groundwork, toolkit installs, and knowledge transfer, policy establishment, etc.
1 Day for source control linkage
½ Day per Windows system
1 Day per UNIX or Linux.
2 Days per z/OS LPAR