Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | 24.04This feature was updated in 24.04
Manager allows you to import a TPac as a ZIP file, which is an Exchange package that provides some specific functionality that you require for various onboarding form applications.
You can also use this functionality to:
Check the list of Exchange packages to find which one you need for your requirements and then request it as a ZIP file from the Client Services team.
You can import a service using one of following options:
To import a TPac:
You can check the Audit Log and Error Log for successful and failed import operations respectively, whilst the Import Log shows all import operations.
The Journey Manager SDK Maven plugin provides the tm-sdk:tpac-deploy goal to import an Exchange package.
The Journey Manager REST API provides the endpoint URL to import an Exchange package.
To call this REST API, you need:
http(s)://{JM_SERVER}/manager/secure/rest/archive/v1/
--header ‘Authorization: Basic <USE-NAME-AND-PASSWORD-BASE64-ENCODED>’
- an HTTP header containing 'username:password'
encoded as Base64Base64 is a binary to a text encoding scheme that represents binary data in an American Standard Code for Information Interchange (ASCII) string format..
--form ‘archiveFile=@“/Users/my-tpac.zip”’
- a path to an archive file to be imported.
--form ‘importOptions=“OVERRIDE_EXISTING_ASSETS”’
- a comma-separated list of import options to perform. The option names are the same as described in the Import Using UI section but they use an underscore, for example, OVERRIDE_EXISTING_ASSETS
for Override Existing Assets.
200 OK
status code.
curl --location --request PUT ‘https://{JM_SERVER}/manager/secure/rest/archive/v1/’ \
--header ‘Authorization: Basic <USE-NAME-AND-PASSWORD-BASE64-ENCODED>’ \
--form ‘archiveFile=@“/Users/my-tpac.zip”’ \
--form ‘importOptions=“OVERRIDE_EXISTING_ASSETS,PRESERVE_SERVICE_CONNECTIONS”’
Next, learn how to view all installed TPacs.