WebSphere Enterprise Service Bus Services

In This Section:

Smooth Start

Is your company starting with WebSphere Enterprise Service Bus (WESB)? When properly implemented, WESB can loosely couple your endpoint and orchestration services into an intercommunicating whole by performing data transformation (XML-XML), protocol conversion (JMS ←→ HTTP) and endpoint routing. An experienced MQSoftware consultant can 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:

  • WESB will be installed on any of the WebSphere Enterprise Service Bus supported systems - AIX, HP-UX, Solaris, Linux, Windows, zSeries
  • A WebSphere Enterprise Service Bus runtime environment will be configured including logging, security, and backup/recovery either in a standalone or federated configuration according to your requirements. If you are uncertain of your requirements, see the MQSoftware Enterprise Service Bus Implementation Planning consulting package.
  • Optional: Connections to up to 10 external WebSphere MQ Queue Managers may be defined
  • The WebSphere Integration Developer (WID, the WESB development environment) 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 WID systems may share an Eclipse shell with any of the following products: WebSphere Message Broker Toolkit; Rational Application Developer; and WebSphere MQ Explorer
  • Eclipse Source Control Plug-ins will be installed in all WebSphere Integration Developer 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
  • 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 Integration Developer.
  • Procedures will be established for deploying code to the WebSphere Enterprise Service Bus.
  • The MQSoftware Consultant will provide knowledge transfer related to WebSphere Enterprise Service Bus to your administrators, architects, and developers.

Smooth Start prerequisites:

  • You have purchased the WebSphere Enterprise Service Bus software and it will be delivered by the time the project begins.
  • You have systems with the appropriate hardware and software resources for WebSphere Enterprise Service Bus (if you are uncertain of this, see the MQSoftware Implementation 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 Enterprise Service Bus 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, knowledge transfer, policy establishment
1 Day for source control linkage
1 Day per Windows system
1 Day per UNIX or Linux system
2 Days per z/OS LPAR