WebSphere MQ Workflow Services
In This Section:
Smooth Start
Is your company starting with WebSphere MQ Workflow? When properly implemented, Workflow Server can act as a powerful service orchestration engine, invoking and managing services and human tasks according to models created by business analysts using Flow Definition Language (FDL). Let MQSoftware’s experience 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 MQ Workflow will be installed on any of the WebSphere MQ Workflow supported systems - AIX, HP-UX, Linux, Windows, zSeries.
- A WebSphere MQ Workflow 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 MQ Workflow Implementation Planning consulting package.
- Optional - the WebSphere MQ Workflow runtime will be configured to connect to an external ESB e.g. WebSphere Message Broker. Connections for up to 10 external WebSphere MQ Queue Managers may also be defined.
- The WebSphere MQ Workflow Buildtime, the MQWF development environment, will be installed and configured for up to 10 standard developer/administrator systems.
- Model Import/Export procedures will be defined including linkage 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 MQ Workflow Buildtime.
- Procedures will be established for deploying code to the WebSphere MQ Workflow runtime.
- The MQSoftware Consultant will provide knowledge transfer related to WebSphere MQ Workflow to your administrators, architects, and developers.
Smooth Start prerequisites:
- WebSphere MQ Workflow software purchased and delivered.
- Systems with the appropriate hardware and software resources for WebSphere MQ Workflow. 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 MQ Workflow 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 - Buildtime installs, knowledge transfer, policy establishment etc.
- 1 Day for source control linkage
- 1 Day per Windows system
- 1 Day per UNIX or Linux system
- 2 Days per z/OS LPAR