WebSphere Process Server Services

In This Section:

Smooth Start

Is your company just starting with WebSphere Process Server? When properly implemented, Process Server can act as a powerful service orchestration engine, invoking and managing services and human tasks according to models created using Business Process Execution Language (BPEL). Because Process Server runs on top of WebSphere Application Server Network Deploy, a considerable amount of Java Enterprise Edition (JEE) configuration and experience are necessary to get started. An experienced MQSoftware 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:

  • WebSphere Process Server will be installed on any of the WebSphere Process Server supported systems (AIX, HP-UX, Linux, Windows, zSeries)
  • A WebSphere Process Server 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 Process Server Implementation Planning consulting package.
  • (Optional) The WebSphere Process Server runtime will be configured to connect to an external ESB (e.g. WebSphere Message Broker), if any or to use the supplied Basic WebSphere ESB. Connections to up to 10 external WebSphere MQ Queue Managers may also be defined if required.
  • The WebSphere Integration Developer (WID, the WPS 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 Plugins will be installed in all WebSphere Integration Developer systems to connect the toolkits to any supported source control manager that 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 Process Server.
  • The MQSoftware Consultant will provide knowledge transfer related to WebSphere Process Server to your administrators, architects, and developers.

Smooth Start prerequisites:

  • You have purchased the WebSphere Process Server software and it will be delivered by the time the project begins.
  • You have systems with the appropriate hardware and software resources for WebSphere Process Server (if you are uncertain of this, see the MQSoftware Implementation Planning Engagment).
  • 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 Process Server 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