6 keys to a successful migration away from CA Lisa

We have helped our customers migrate away from CA Lisa and have found these 6 items to be crucial to a successful project plan:

1. A well-designed and successful POC that includes clearly defined scope, roles, and responsibilities

2. Pick the right teams and projects to start with

3. Retrospectives after each team adopts to drive adjustments and fine-tuning

4. Identify key metrics to report on to upper management

5. Roll out strategy that includes

6. Manage the delayed adoption of lagging cohort

If you are exploring migrating away from CA Lisa we would be happy to do a 20-minute Zoom webinar for your team sharing our experience on how to do a successful migration. Please reach out to us by replying to this email, filling in the contact form, or calling +44 20 3239 7753.

Codebase improvements

The last 3 months have been busy at Traffic Parrot. We have made a number of improvements: we have released three new versions 5.24.9 to 5.25.0 that introduced several new features including defining multiple response messages per one Native IBM® MQ mapping and using multiple native IBM® MQ virtual services in one instance. We have also fixed several bugs.

gRPC tips

Are you using gRPC? Here is how you can simulate dependent gRPC services using Traffic Parrot to allow your team to work in parallel and hence cut time to market.

Traffic Parrot 5.26.3 released, what's new?

We have just released version 5.26.3. Here is a list of the changes that came with the release:

Features

• Added a new helper to allow calculating and formatting date offsets in responses e.g. {{ dateOffset (jsonPath request.body '$.date_field') add=true format='yyyy-MM-dd' days=1 }}
• Added support for accessing a standard set of runtime properties in plugins so that e.g. plugins can be supplied with configuration files at runtime that are placed in virtual service specific or global shared directories

Fixes

• Improved support for handlebars partial template files:
  • The root for partials now takes into account the directory specified in trafficparrot.virtualservice.trafficFilesRootUrl=file:.
  • The root for partials when using virtual services is the named directory scenarios/ScenarioName/*.hbs