Services Overview

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |   17.10 This feature was updated in 17.10.

Journey Manager comes with services that are software modules configured to perform specific business-related functionality, usually by executing GroovyGroovy is a powerful scripting language which runs on the Java Virtual Machine. Across theTemenos Journey Manager platform, Groovy is used to create services in Manager. These services are primarily used to create plug-in style systems that interact with Manager. scripts. Services are often used to call external systems and services hosted on premise or on cloud. Manager supports the AmazonAmazon Web Services (AWS) is a comprehensive, evolving cloud computing platform provided by Amazon. It provides a mix of infrastructure as a service (IaaS), platform as a service (PaaS) and packaged software as a service (SaaS) offerings. or AzureMicrosoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers. clouds.

You can use services to implement the typical client onboarding solutions, such as:

A customer onboarding journey may use the following Manager's services:

A typical customer acquisition application, which uses Manager's services, is shown below:

Manager defines service categories to distinguish between services. Manager can have hundreds of services plus several versions of each service, so it's important to group services correctly.

A service category can be one of the following:

Each service has a service type, which defines what functionality it implements, for example, virus scanning. There can be multiple services per every service type. However, only one of them can be set as the default service for each type. You can define your own service types and create corresponding services to implement specific requirements, for example, to notify customers via SMS, using Fluent Groovy API.

Services can be defined for an organization, so they are not visible to other organizations and their forms.

Services can have various parameters, which you can customize to control their run-time behavior.

Some services require a service connection, such as the AWS SQS service connection, to communicate with external systems and services.

You can migrate existing services from one environment to another to improve your development process.

As services may be complex in their implementations, it can be difficult and time consuming for you to troubleshoot any errors associated with forms that use these services. Manager provides you with a quick way to access service logging information, using Groovy Service Log, where you can find some key service stats generated during its execution.

Forms use services extensively to process user input and fetch all required data, which is a big part of complex customer onboarding journeys. More often than not, you may want to use Transact functions to call services from Maestro forms.

Manager allows you to configure services that are used by a form. Additionally, you have the option of enabling or disabling Transact Functions when building a TM form version in Maestro editor. However, you must be aware that enabling Transact Functions limits the range of services available to the form, which is illustrated below.

Services available to a form with Transact Functions disabled and enabled

Next, learn how to view all services.