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 scheduled jobs, which were previously exported.
You can only import scheduled jobs, which execute services of the Scheduled Service Job type. You can't import scheduled jobs, which execute Core Services.
Use this functionality to:
You can import a scheduled job using one of following options:
To import a scheduled job:
There are no import options to select, so every import will override the existing scheduled job.
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:archive-deploy goal to import a scheduled job. For example, set archive.file=my-scheduled-job.zip
in the build.properties
file and run mvn initialize tm-sdk:archive-deploy
to import a scheduled job.
The Journey Manager REST API provides the endpoint URL to import a scheduled job.
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-scheduled-job.zip”’
- a path to an archive file to be imported.
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-scheduled-job.zip”’
You can also update an existing scheduled job using the Configuration Service API.
Next, learn how to view scheduled job history.