Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Simphony R&A 20.1 JSON export API delivery profile setup 1
- Thread starter Manu P
- Start date
-
1
- #2
Adding a Delivery Profile
Specify delivery through SFTP or HTTPS, define destination settings such as the server location for SFTP or the URL for HTTPS, specify authentication details. A delivery profile must be added before adding an export schedule.
Required system privileges: Export Schedules, Add/Edit/View/Delete Delivery Profiles, and either View Schedules or Add/Edit/View/Delete Schedules.
Additional system privilege to transfer ownership of the delivery profile: Transfer Ownership of Delivery Profiles.
You need to select a delivery profile when you add an export schedule. Add the delivery profile before adding the export schedule.
In Reporting and Analytics, click the side navigation menu, click Reports, click Exports, click Schedules, and then click Manage Delivery Profiles.
On the Manage Delivery Profiles page, click Add Delivery Profile.
Enter a profile name and specify if the profile is public or private.
Only the owner of a private delivery profile can add it to a schedule or change the assignment in a schedule.
Select the delivery type.
For delivery through SFTP, specify the destination server and folder path on the server. If you authenticate with a certificate, paste the certificate in the SSH Private Key text box. If you edit the profile at a later time, the key value does not show in the text box, only text that mentions a key exists shows in the text box. To change the public key, paste the new public key in the text box and then click Save. If you authenticate with credentials, specify the user name and password.
For delivery through posting to a URL, specify the URL and then specify header parameters. Include header attributes in the post using token. Enter line breaks between each header parameter
Specify delivery through SFTP or HTTPS, define destination settings such as the server location for SFTP or the URL for HTTPS, specify authentication details. A delivery profile must be added before adding an export schedule.
Required system privileges: Export Schedules, Add/Edit/View/Delete Delivery Profiles, and either View Schedules or Add/Edit/View/Delete Schedules.
Additional system privilege to transfer ownership of the delivery profile: Transfer Ownership of Delivery Profiles.
You need to select a delivery profile when you add an export schedule. Add the delivery profile before adding the export schedule.
In Reporting and Analytics, click the side navigation menu, click Reports, click Exports, click Schedules, and then click Manage Delivery Profiles.
On the Manage Delivery Profiles page, click Add Delivery Profile.
Enter a profile name and specify if the profile is public or private.
Only the owner of a private delivery profile can add it to a schedule or change the assignment in a schedule.
Select the delivery type.
For delivery through SFTP, specify the destination server and folder path on the server. If you authenticate with a certificate, paste the certificate in the SSH Private Key text box. If you edit the profile at a later time, the key value does not show in the text box, only text that mentions a key exists shows in the text box. To change the public key, paste the new public key in the text box and then click Save. If you authenticate with credentials, specify the user name and password.
For delivery through posting to a URL, specify the URL and then specify header parameters. Include header attributes in the post using token. Enter line breaks between each header parameter
- Thread starter
- #3
Hi Mike,
Thank you so much for the detailed steps
I will follow the same to configure
I am a little confused with the last line about header parameters. Could you show me an example of the header parameter how it looks like if you have any?
I do have this
Content-type: application/json; charset=utf-8
Thank you so much for the detailed steps
I will follow the same to configure
I am a little confused with the last line about header parameters. Could you show me an example of the header parameter how it looks like if you have any?
I do have this
Content-type: application/json; charset=utf-8
- Status