B2B deployment methodology overview - IBM Websphere

The B2B deployment methodology is divided into eight distinct phases with knowledgetransfer throughout the project life cycle

Phase execution flow

Phase execution flow

Knowledge transfer and training

Training and knowledge transfer need to encompass the entire project; it is important to identify the project representatives at the start of the project so that a plan can be put in place to allow ample time for training prior to the production deployment phase of the project. All of the personnel that will maintain the solution must be trained and must participate in many phases of the project to obtain as much knowledge about the specific deployment as possible.

Phase tasks
In this phase:

  • Recommend training classes and provide class schedules and synopses to theproject sponsor.
  • Recommend appropriate books and provide information about how to gain access to the books.
  • Provide guidance to personnel during each phase of the project.

Deliverable
This phase is ongoing throughout the project, and the key deliverable associated with it is the training plan that is developed during the planning phase. It is designedto provide a roadmap to get personnel up to speed as fast as possible on the B2B technology being used.

Skill sets and resource requirements
The skill sets required for this phase are:

  • IT infrastructure knowledge, including network, connection, and data security.
  • Expert knowledge of IBM B2B and integration solutions.
  • Expert knowledge of High Availability concepts.
  • Knowledge of the data center infrastructure, hardware, and software that aredesignated for the B2B project.
  • Knowledge of other IBM products related to B2B and application integration (You might need to bring in a specialist. )

Discovery
The Discovery phase is where the business and security requirements are reviewed andrevised, the scope of the project and critical success factors are defined and agreedupon, the existing infrastructure and environment are reviewed, software and hardware distribution models are discussed, and roles and responsibilities are identified. This phase consists of meetings with the business owners (typically, the project sponsors) and the technical personnel who maintain the current applications and network environment. At the end of this phase, all hardware and software needed for the solution must be identified and procured. We advise that you first perform this phase prior to communicating any effort estimate. All of the discovery work must be completed prior to moving forward; this task is considered a key milestone in the project.

Phase tasks
The phase tasks include:

  • Schedule a deployment assessment meeting with the business and technical project participants. This meeting can be a single meeting or can be broken up into separate meetings. This meeting is used to gather the requirements and to introduce eachteam member.
  • Create the deployment assessment presentation and agenda.
  • Create a roles and responsibilities worksheet.
  • Create the requirements and scope documents.

Deliverables
After completion of this phase, you need to be ready to deliver:

  • Meeting agenda presentation.

    Detailed requirements document, which includes a summary of what was discovered during the meetings, including existing environment information:

    • Detailed definition of the business requirements.
    • Detailed definition of the security requirements.
    • Hardware and software requirements based on the distribution model and capacity estimates.
  • Detailed scope document.
  • Roles and responsibilities document.

Skill sets and resource requirements
The skill sets and resources required for this phase are:

  • Project planning skills and experience.
  • IT infrastructure knowledge, including network, connection, and data security.
  • Expert knowledge of IBM B2B and integration solutions.
  • Expert knowledge of High Availability concepts.
  • Knowledge of the data center infrastructure, hardware, and software that aredesignated for the B2B project.
  • Knowledge of other IBM Products related to B2B and application integration (You might need to bring in a specialist. )

Planning
The Planning phase takes all of the information that was learned during the Discoveryphase as input into all of the plans needed to successfully deploy the B2B solution. This phase is used to build a technology deployment strategy that meets the key objectives for partner connectivity, security, integration, protocols, data validation and transformation, and so forth. The deployment strategy can include the deployment of additional hardware and software to fully meet all of the business requirements. During this phase, additional information is typically discovered that changes the project scope and schedule; it is important to mplement change control to ensure that all changes are documented andagreed upon by the project sponsors.

Phase tasks
The phase tasks include:

  • Analyze the requirements and scope documents to provide content for each plan.
  • Schedule follow-up meetings as needed.
  • Implement change control and revise scope and schedule as needed.
  • Create a project plan and time line(This task is sometimes is done in the Discovery phase).
  • Create physical and logical architectural diagrams.
  • Create a deployment plan.
  • Create a development plan and schedule if applicable.
  • Create a failover plan and strategy if implementing High Availability.
  • Create a disaster recover (DR) plan and strategy if implementing a DR environment.
  • Create a data archive/backup plan and strategy if applicable.
  • Create a testing plan.
  • Create a training plan.
  • Create a Partner Ramping or Partner Onboarding plan.

Deliverables
Deliverables resulting from this phase include:

  • Detailed project plan defining all project tasks and time line (This task is sometimes is done in the Discovery phase)

Detailed deployment plan, which includes:

  • Existing environment overview and diagram.
  • Proposed environment overview and diagram.
  • Software requirements and dependencies.
  • Customization requirements.
  • Requirements compared to functionality gap analysis.
  • Migration consideration for existing data.
  • Deployment considerations.

Detailed development plan, which includes:

  • Development requirements summary.
  • Development schedule and project plan.
  • Development effort estimate.
  • Conceptual design.
  • Functional design.
  • Development test plan.
  • User documentation:New features and functionality, installation andconfiguration, and so forth.
  • Issues log.

Detailed testing plan, which includes:

  • System testing (installation testing and basic trading).
  • Functional testing (end-to-end document trading scenarios with integration).
  • Stress and volume testing(Verify that the proposed hardware and software are sufficient to handle current and future(two year projection) transaction volumes. )In certain cases, additional appliances, software, or hardware will need to be added tomeet your throughput needs.
  • High Availability (HA) failover testing if HA is implemented.
  • Disaster recovery testing if DR is implemented.
  • New functionality testing (if custom code is being added).
  • Transformation testing if transformation maps are being used.
  • Integration testing: Test connectivity to the back-end systems.

Detailed training plan, which includes:

  • List of personnel identified as requiring training.
  • List of classes for the individuals to attend and complete electronically.
  • Information about how to access relevant books related to the hardware andsoftware being used for this project.
  • Knowledge transfer recommendations and whether to use IBM Business Partners or consultants for one-on-one training to provide your team with the maximum benefit from a subject matter expert’s knowledge.

Detailed Partner Ramping plan, which includes:

  • Prioritized list of trading partners and their IDs.
  • Document flows for each partner.
  • Certificate information for each partner.
  • Ramping schedule with effort estimates.
  • Integration requirements for each partner (for example, translation, validation, andso forth).

Skill sets and resource requirements
Identify the necessary skills and resources:

  • Understanding of the functional and non-functional requirements related to theproject.
  • IT infrastructure knowledge, including network, connection, and data security.
  • Knowledge of IBM B2B and integration solutions.
  • Knowledge of electronic data interchange (EDI) and mapping functions; can include knowledge of a variety of mapping tools.
  • Knowledge of various Enterprise Application Integration (EAI) applications forintegrating to the back-end systems.
  • Knowledge of database administration and SQL.
  • Knowledge of High Availability concepts.
  • Project planning skills and experience.
  • Knowledge of other IBM products related to business integration (You might need to bring in a specialist. )

Installation
The Installation phase is designed to deliver a fully functional development and testenvironment to support the Customization, Testing, and Production Deployment phases of the project. It utilizes the information in the deployment plan from the Planning phase to determine how components are deployed and distributed in the customer’s network.

Phase tasks
The tasks in this phase include:

  • Review the deployment plan and revise if needed.
  • Document all of the installation inputs that are needed to complete related software installations.
  • Install each environment utilizing the deployment plan to guide you through theinstallation and configuration process. (Implementation can include the installation of many applications, such as WebSphere Application Server, WebSphere MQ, WebSphere Transformation Extender, WebSphere Message Broker, WebSphere Process Server, WebSphere Adapters, and so forth. )
  • Verify component installation and network connectivity between each component and system (Verify network connections through firewalls, routers, switches, proxies, load balancers, and so forth. ).

Deliverables
The deliverables resulting from this phase include:

  • Revised deployment plan if needed.
  • Completed installation input document for each environment.
  • Installation and configuration of all environments.

Skill sets and resourcerequirements
The required skills and resources from this phase include:

  • IT infrastructure knowledge, including network, connection, and data security.
  • Experience installing and configuring B2B and application integration solutions.
  • Knowledge of other IBM products related to business integration (You might need to bring in a specialist. ).
  • Excellent troubleshooting skills.

Customization

The Customization phase is designed to deliver functionality that the core products do not include. Customization is done by utilizing the application programming interfaces (APIs), exit frameworks, mapping tools, (Extensible Stylesheet Language Transformation (XSLT), and so forth(for examplecustom messaging protocols, validation of custom document types, custom transports, custom XML, RosettaNet Partner Interface Processes (PIPs), translationmaps, and so forth).

It utilizes the information in the development plan from the Planning phase to determine what customizations are required to meet the customers’ needs. This phase typically runs after the installation of the development environment performed in the Installation phase; however, in many cases, development is done on each developer’s workstation utilizing their own local installation of the software. If this situation is the case, this phase can run in parallel to the Installation and Test phases.

In this phase, follow a reputable development management process. There are many processes available but few are geared for the relatively short development cycles that you encounter during customer-driven development. A good example of a short cycledevelopment process is the Scrum Agile software development process.

Go to the following Web site for more information about Scrum:

Phase tasks
The tasks include:

  • Review the development plan and revise if needed.
  • Utilize the requirements document to create a functional design document.
  • Create custom code based on the functional design document.

Deliverables
The deliverables resulting from this phase are:

  • Revised development plan and schedule.
  • Functional design document with estimated effort.
  • Issues log template.
  • Completed functionality that can be utilized in IBM integration products to provide a complete solution.

Skill sets and resource requirements
Required skills and resources include:

  • Java development experience.
  • Experience with EDI data sets.
  • Experience with document type definition (DTD) and XML Schema development.
  • XLST development experience.
  • Knowledge of Internet and B2B messaging protocols (File Transfer Protocol(FTP), Hypertext Transfer Protocol(HTTP), Simple Mail Transfer Protocol(SMTP), SecureSockets Layer (SSL), AS1, AS2, AS3, RosettaNet, ebXML, and so forth).
  • Knowledge of database administration and SQL.
  • Knowledge of WebSphere MQ.
  • Knowledge of other IBM products related to business integration (You might need to bring in a specialist. )

Testing

The Testing phase is designed to provide installation testing to verify the solution functions as required and complete system testing, which is conducted according to the customer’s real-world trading scenarios. The Testing phase needs to include functional testing of any customizations that were performed in the Customization phase and integration testing to ensure that documents are flowing properly from end-to-end. Performance testing is also performed in this phase to confirm that the production hardware is capable of handling the throughput requirements. If the environment is being set up for High Availability, additional testing will be needed to ensure that failover works as expected. This phase will utilize the test plan as a guide for running the scenarios and recording the results.

Phase tasks
The tasks include:

  • Review and revise the test plan if needed.
  • Execute the test plan and record the results.
  • Perform performance testing to assist in appropriately sizing the productionenvironment.
  • Perform failover testing when implementing a High Availability environment.

Deliverables
The deliverables that result from this phase are:

  • Revised test plan with recorded test results
  • Completed testing based on the scenarios in the test plan
  • Updated environment sizing recommendations based on the performance testing

Skill sets and resource requirements
The required skill sets and resources are:

  • Knowledge of IBM B2B and integration solutions
  • Quality assurance testing experience
  • Knowledge of Internet and B2B messaging protocols (HTTP, FTP, SMTP, SSL, AS1, AS2, AS3, RosettaNet, ebXML, and so forth)
  • Knowledge of other IBM products related to business integration (You might need to bring in a specialist. )

Production Deployment

The Production Deployment phase is designed to provide the customer with anenvironment, which is completely configured and tested, that can be used in a production capacity. Typically, the test environment is locked and copied or moved into production. A production deployment might have partners already configured for trading prior to the move to production, and additional partners can be configured based on the PartnerRamping plan.

Phase tasks
The tasks are:

  • Review and revise the production deployment section of the deployment plan ifneeded.
  • Revise the installation inputs document for the production environment if needed.
  • Create the production environment from the environment installed in the Planningphase.
  • Verify component installation and network connectivity between each component(Verify network connections through firewalls, routers, switches, proxies, load balancers, and so forth. ).

Deliverables
The resulting deliverables are:

  • Revised deployment plan, if needed.
  • Revised installation inputs document, if needed.
  • Fully functional production environment.

Skill sets and resource requirements
The required skills and resources are:

  • IT infrastructure knowledge, including network, connection, and data security.
  • Experience installing and configuring IBM WebSphere Integration products.
  • Knowledge of other IBM products related to business integration(You might need to bring in a specialist. ).
  • Excellent troubleshooting skills.

Partner Ramping

The Partner Ramping phase follows the Production Deployment phase and is used toconnect partners based on the Partner Ramping plan, which was created in the Discovery phase. This phase is also used to build a Partner Ramping strategy to provide the customer with a guideline to follow for deploying future partners; the strategy is created if the customer needs a long-term strategy for adding partners to the hub.

Phase tasks
The tasks are:

  • Schedule a trading partner review meeting with the project sponsors. This meeting is intended to allow you to verify that all trading partners are accounted for in the ramping plan and to get the each partner assigned with a priority. In most cases, you will want to force rank the partners so you can build a schedule connecting to the highest priority partners first.
  • Create a trading Partner Ramping strategy or process document.
  • Revise the trading Partner Ramping plan if needed.
  • Connect trading partners based on the trading partner plan and strategy, whichincludes building integration targets and gateways as needed.

Deliverables
The resulting deliverables are:

  • Detailed Partner Ramping strategy document, which includes:
  • Connection process flow:
    • Interoperability matrix of interoperable products.
    • Strategy for connecting small partners to the hub.
    • Partner information form template.
  • Connection to trading partners(Many customers consider this step to be part of the daily operational tasks that their own B2B staff will perform and will only require minimal support from IBM services when ramping the partners)

Skill sets and resource requirements
Required skills and resources are:

  • Experience configuring IBM WebSphere Integration products.
  • Knowledge of Internet and B2B messaging protocols (HTTP, FTP, SMTP, SSL, AS1, AS2, AS3, RosettaNet, ebXML, and so forth)
  • Knowledge of other IBM Products related to business integration (You might need to bring in a specialist. ).
  • Excellent troubleshooting skills.

Support

The Support phase follows the Production Deployment phase and usually runs in parallel to the Partner Ramping phase. The Support phase is where IBM can provide post production deployment support on-site for a minimum of two weeks to ensure that the B2B personnel are equipped to handle the day-to-day support requirements of all of the deployedenvironments. This phase is also used to create a support process for internal customers and trading partners to report B2B-related issues. In many cases, additional time is spent providing advanced problem determination tips and tricks to your personnel.

Phase tasks
The tasks in this phase are:

  • Provide ramping support to ensure efficient partner connectivity.
  • Transfer knowledge to the customer’s personnel about monitoring B2B transactions and the best practices for problem determination.
  • Assist in defining a support process and flow (how customers get both internal and external help when problems occur, what number to call, what e-mail address to us, to what the service level agreement (SLA) is the B2B support team willing to commit, and so forth).

Deliverables
The resulting deliverables are:

  • Documented support and issue resolution process.
  • Ongoing support transferred to the customer.

Skill sets and resource requirements
The required skills and resources are:

  • Experience configuring IBM WebSphere Integration products.
  • Excellent troubleshooting skills.
  • Excellent communications skills.
  • Knowledge of Internet and B2B messaging protocols (HTTP, FTP, SMTP, SSL, AS1, AS2, AS3, RosettaNet, ebXML, and so forth).
  • Knowledge of other IBM products related to business integration (You might need to bring in a specialist. ).

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Websphere Topics