How to create a mirth channel utilizing rest API.
I want export channel messages to ftp server or external drive. I thing we can export messages via rest API. Could you any one help on this..
api mirth-connect
add a comment |
I want export channel messages to ftp server or external drive. I thing we can export messages via rest API. Could you any one help on this..
api mirth-connect
Thanks for your update.I have created a separate channel and I can able to send mirth logs to the external drive which is FTP server using file writer connection type(destination) Now I want to export channel messages ( particularly one or more channel) to an external drive using Rest API. I can able to access the rest API interface(10.X.X.X:8443/api), and there selected endpoint /channels/{channelId}/messages/_export to export messages. but got the Unsupported Media Type (415). I do not know proper steps to make automate this job. now I hope you got a picture.
– Rajkapoor Mohamed
Nov 23 at 8:50
add a comment |
I want export channel messages to ftp server or external drive. I thing we can export messages via rest API. Could you any one help on this..
api mirth-connect
I want export channel messages to ftp server or external drive. I thing we can export messages via rest API. Could you any one help on this..
api mirth-connect
api mirth-connect
asked Nov 22 at 20:07
Rajkapoor Mohamed
61
61
Thanks for your update.I have created a separate channel and I can able to send mirth logs to the external drive which is FTP server using file writer connection type(destination) Now I want to export channel messages ( particularly one or more channel) to an external drive using Rest API. I can able to access the rest API interface(10.X.X.X:8443/api), and there selected endpoint /channels/{channelId}/messages/_export to export messages. but got the Unsupported Media Type (415). I do not know proper steps to make automate this job. now I hope you got a picture.
– Rajkapoor Mohamed
Nov 23 at 8:50
add a comment |
Thanks for your update.I have created a separate channel and I can able to send mirth logs to the external drive which is FTP server using file writer connection type(destination) Now I want to export channel messages ( particularly one or more channel) to an external drive using Rest API. I can able to access the rest API interface(10.X.X.X:8443/api), and there selected endpoint /channels/{channelId}/messages/_export to export messages. but got the Unsupported Media Type (415). I do not know proper steps to make automate this job. now I hope you got a picture.
– Rajkapoor Mohamed
Nov 23 at 8:50
Thanks for your update.I have created a separate channel and I can able to send mirth logs to the external drive which is FTP server using file writer connection type(destination) Now I want to export channel messages ( particularly one or more channel) to an external drive using Rest API. I can able to access the rest API interface(10.X.X.X:8443/api), and there selected endpoint /channels/{channelId}/messages/_export to export messages. but got the Unsupported Media Type (415). I do not know proper steps to make automate this job. now I hope you got a picture.
– Rajkapoor Mohamed
Nov 23 at 8:50
Thanks for your update.I have created a separate channel and I can able to send mirth logs to the external drive which is FTP server using file writer connection type(destination) Now I want to export channel messages ( particularly one or more channel) to an external drive using Rest API. I can able to access the rest API interface(10.X.X.X:8443/api), and there selected endpoint /channels/{channelId}/messages/_export to export messages. but got the Unsupported Media Type (415). I do not know proper steps to make automate this job. now I hope you got a picture.
– Rajkapoor Mohamed
Nov 23 at 8:50
add a comment |
2 Answers
2
active
oldest
votes
If you want to send messages to a REST API, you can use the HTTP Sender
destination connector type.
If your REST API Endpoint requires any special headers or authentication, you will need to configure this appropriately (such as by setting variables in the Destination Transformer). Don't forget to put something in the "Content" box at the bottom of the screen - this usually has a value such as ${message.transformedData}
or ${message.rawData}
.
If you want to send messages to an FTP server, you can use the File Writer
destination connector type. Again, make sure you put something such as ${message.transformedData}
in the "Template" field.
add a comment |
The POST /channels/{channelId}/messages/_export
endpoint is to export messages to files on the server filesystem. When the client does an export to the local file system, it basically writes the results of GET /channels/{channelId}/messages
with one file per message and attachments included. See Source.
Possibly the most effective way to get all your processed messages offsite is to just take a database backup.
The data pruner also has an option to archive messages to disk as they are pruned, and those files could be picked up and sent offsite if desired.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437475%2fhow-to-create-a-mirth-channel-utilizing-rest-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you want to send messages to a REST API, you can use the HTTP Sender
destination connector type.
If your REST API Endpoint requires any special headers or authentication, you will need to configure this appropriately (such as by setting variables in the Destination Transformer). Don't forget to put something in the "Content" box at the bottom of the screen - this usually has a value such as ${message.transformedData}
or ${message.rawData}
.
If you want to send messages to an FTP server, you can use the File Writer
destination connector type. Again, make sure you put something such as ${message.transformedData}
in the "Template" field.
add a comment |
If you want to send messages to a REST API, you can use the HTTP Sender
destination connector type.
If your REST API Endpoint requires any special headers or authentication, you will need to configure this appropriately (such as by setting variables in the Destination Transformer). Don't forget to put something in the "Content" box at the bottom of the screen - this usually has a value such as ${message.transformedData}
or ${message.rawData}
.
If you want to send messages to an FTP server, you can use the File Writer
destination connector type. Again, make sure you put something such as ${message.transformedData}
in the "Template" field.
add a comment |
If you want to send messages to a REST API, you can use the HTTP Sender
destination connector type.
If your REST API Endpoint requires any special headers or authentication, you will need to configure this appropriately (such as by setting variables in the Destination Transformer). Don't forget to put something in the "Content" box at the bottom of the screen - this usually has a value such as ${message.transformedData}
or ${message.rawData}
.
If you want to send messages to an FTP server, you can use the File Writer
destination connector type. Again, make sure you put something such as ${message.transformedData}
in the "Template" field.
If you want to send messages to a REST API, you can use the HTTP Sender
destination connector type.
If your REST API Endpoint requires any special headers or authentication, you will need to configure this appropriately (such as by setting variables in the Destination Transformer). Don't forget to put something in the "Content" box at the bottom of the screen - this usually has a value such as ${message.transformedData}
or ${message.rawData}
.
If you want to send messages to an FTP server, you can use the File Writer
destination connector type. Again, make sure you put something such as ${message.transformedData}
in the "Template" field.
answered Nov 22 at 23:25
Daniel Elkington
14526
14526
add a comment |
add a comment |
The POST /channels/{channelId}/messages/_export
endpoint is to export messages to files on the server filesystem. When the client does an export to the local file system, it basically writes the results of GET /channels/{channelId}/messages
with one file per message and attachments included. See Source.
Possibly the most effective way to get all your processed messages offsite is to just take a database backup.
The data pruner also has an option to archive messages to disk as they are pruned, and those files could be picked up and sent offsite if desired.
add a comment |
The POST /channels/{channelId}/messages/_export
endpoint is to export messages to files on the server filesystem. When the client does an export to the local file system, it basically writes the results of GET /channels/{channelId}/messages
with one file per message and attachments included. See Source.
Possibly the most effective way to get all your processed messages offsite is to just take a database backup.
The data pruner also has an option to archive messages to disk as they are pruned, and those files could be picked up and sent offsite if desired.
add a comment |
The POST /channels/{channelId}/messages/_export
endpoint is to export messages to files on the server filesystem. When the client does an export to the local file system, it basically writes the results of GET /channels/{channelId}/messages
with one file per message and attachments included. See Source.
Possibly the most effective way to get all your processed messages offsite is to just take a database backup.
The data pruner also has an option to archive messages to disk as they are pruned, and those files could be picked up and sent offsite if desired.
The POST /channels/{channelId}/messages/_export
endpoint is to export messages to files on the server filesystem. When the client does an export to the local file system, it basically writes the results of GET /channels/{channelId}/messages
with one file per message and attachments included. See Source.
Possibly the most effective way to get all your processed messages offsite is to just take a database backup.
The data pruner also has an option to archive messages to disk as they are pruned, and those files could be picked up and sent offsite if desired.
answered Nov 24 at 7:08
Tony G-R
1355
1355
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437475%2fhow-to-create-a-mirth-channel-utilizing-rest-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Thanks for your update.I have created a separate channel and I can able to send mirth logs to the external drive which is FTP server using file writer connection type(destination) Now I want to export channel messages ( particularly one or more channel) to an external drive using Rest API. I can able to access the rest API interface(10.X.X.X:8443/api), and there selected endpoint /channels/{channelId}/messages/_export to export messages. but got the Unsupported Media Type (415). I do not know proper steps to make automate this job. now I hope you got a picture.
– Rajkapoor Mohamed
Nov 23 at 8:50